Check our Scheduled Business Analysis Training Classes
Print Course Description (pdf)
Buy It ($59)
This nugget (Rule 5) presents techniques for improving the measurability of a requirement statement (whether you wrote the original or not) which increases the probability that the developers will understand – and deliver – what you ask for. A powerful by-product of this rule is that when you ask how will you measure or know that a requirement has been achieved, it reveals additional information about the requirement.
Table of Contents
- Learning Objectives
- Rules for a “Good” Requirement Sentence
- Why You Need Measurable Requirements
- Business Requirements are Complex
- Effective Requirements Are Specific
- Evaluating Functional Requirements
- Finding the Functional Elements
- Exercise: Finding Functions
- Documenting Functional Elements
- Performance Requirements Defined
- Evaluating Performance Requirements
- Common Qualitative Performance Requirements
- Exercise: Quantitative versus Qualitative Performance Requirements
- Finding Performance Requirements
- Translating Performance into Functional Requirements
- Exercise: Discovering Performance-related Functions
- Evaluating Informational Requirements
- Finding Informational Elements
- Documenting Informational Elements
- Managing Informational Elements
- Exercise: Finding Informational Requirements
- Defining the Accuracy of Informational Elements
- Exercise: Establshing Application-based Accuracy
- Evaluating Constraining Requirements
- Finding Constraining Requirements
- Exercise: Finding Constraining Requirements
- Summary: Rules for Effective Requirement
- Exercie: Final Exam
- Rules for Effective Business Requirements
- Where To From Here?
- Identify and define functional and informational elements.
- Improve the measurability of its functional and informational content.
- Differentiate between quantitative and qualitative measures.
- Revise subjective qualities to increase their measurability.
- Extract business rules and external constraints from the business requirements.
90+ minutes

Testers
Software QA
Business System Analysts
Subject Matter Experts
System Analysts
User liaison personnel
Anyone who would like to understand their customer’s needs