Getting the important business needs out of the requirements gathering process should be the goal of every business analyst. In this article, Karl Wiegers discusses the benefits of asking open-ended questions during requirements specification. They are especially useful to discover exceptions to the normal process behaviour. You are then able to determine and describe how the system should detect and respond to an error. The last question he asks during a requirements elicitation meeting is: “Is there anything else I should be asking you?”
Asking Open-Ended Questions
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