Story writing is usually taught now as a singsong “As a I want so that .” The writer should then immediately document acceptance criteria in the form of a constraint list or automated acceptance tests. Many consider it poor form to create a story that someone outside the team can’t understand from its documentation alone. In this article Paul Dupuy explains that an ideal user story’s documentation should be nothing more than a short, memory-jarring name.
Modern software development approaches like Agile and Scrum support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development (BDD) or Specification by Example, checking the fact that you will be able to actually test your requirements is […]
Read More
This article is an extract of the “Complete Systems Analysis” written by James and Suzanne Robertson. It explains the basics of analysis models and emphasize that the important thing to remember is that modeling tools are complementary. Each shows one aspect of the system. Together, they make a complete working model of the system.
Read More
This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
Read MoreCopyright © 2009-2022 Martinig & Associates