An application lives or dies by its ability to allow users to achieve the goals that drive the creation of (or purchase of) the software.
Requirements / Software requirements specification / Testing
Posted on:
How To Deal With Untestable Requirements – Rewrite Them
The premise behind the rule that requirements must be testable is driven by the goal of avoiding ambiguous language in your requirements. Statements like “the application must have a clean user interface†or “search response times must be fast†are also untestable, but more because of language than anything else.
Process Improvement / Requirements / Testing
Posted on:
Requirements and Software Development Process and Where Bugs Come From
[Ed: This post was retitled, edited, and updated as Where bugs come from due to recurring issues for some readers with accessing this page. Please read the updated version (there are some revisions to the content and new links to other content). Thanks]
Requirements / Slightly off-topic / UX
Posted on:
Concept Maps – Great Tool for Eating the Elephant (Brainstorming Ideas for a New Product)
Concept mapping is a tool I use for the brainstorming process of defining a product’s specification. IHMC developed the concept mapping software that we show in this article