A user story is a high-level requirement of a feature provided from the perspective of a stakeholder. A comprehensive user story has acceptance criteria that cover all possible functional scenarios or conditions needed to satisfy the user requirements. In development and testing terms, this means defining positive and negative scenarios. This article defines what differs between the normal user stories and the comprehensive user stories.
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