Reviewing Requirements for Testability

software requirements group

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 a good thing. In his article, Richard Ellison share some best practices to reviewing requirements for testability from the point of view of a software tester.

His main advice is that the software testers should review requirements before the formal reviews and send questions to the business analyst in advance. Unanswered questions should be written down to have a reference point to get clarification with the larger team. He recommends documenting everything in requirements review meetings. He uses a spreadsheet and lists the requirement number and the comments. If a new requirement will be added, an additional row in the spreadsheet is added with the comments about the new requirement. You can add a second column to identify as testable or not.

Read the complete article about the best practices to review requirements for testability on http://www.softwaretestingmagazine.com/knowledge/best-practices-reviewing-requirements-for-testability/

Requirements Management Articles
Articles Knowledge

User Stories for Both Requirements and Testing

User stories are a technique taken from the agile development playbook that can easily be applied in traditional systems development and maintenance. User stories help you document needs in a structured way, from the users’ perspective. They’re a good basis for test cases, so as to support integrated requirements management and testing. In this article, […]

Read More
Requirements Management Articles
Articles Knowledge

Understanding 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 More
Requirements Management Blogs
Blogs Knowledge

Find Missing Requirements

This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.

Read More

Copyright © 2009-2021 Martinig & Associates