Stop Gathering Requirements

Requirements Management Articles

The concept of “gathering requirements” comes from the premise that there are requirements out there someplace that the business analyst has to find. But do users or stakeholders really have requirements? In this article, Steve Blais says that users don’t have requirements, so business analysts have to stop gathering requirements. His opinion is that user have business problem to solve. Requirements are defined or created by the business analyst as a possible solution to a business problem. The requirements document is the representation of the complete and accurate statement of what must be done to solve the business problem.

software requirements group
Articles Knowledge

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 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-2022 Martinig & Associates