In this blog post, Glen Alleman explains the concept of capabilities based planning to elicit requirements. You use capabilities is to answer the question “Why is this requirement needed?” Capabilities statements are then used to define the units of measure for program progress which is the most meaningful to the customer. Starting with the Capabilities prevents that requirements gathering process produce list of requirements that are all needed. The blog provides a step-by-step approach for capabilities. Then for each defined capability there needs to be a process and product requirements. The Process Performance Requirements define how the work processes are used to benefit the customer. The Product Performance Requirements define the product specifications and how they are related to the process requirements.
Capabilities Based Planning for Requirements
Reviewing Requirements for Testability
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 MoreUnderstanding System Analysis Models
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 MoreFind Missing Requirements
This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
Read More