The set of techniques which combine to comprise a very effective and efficient requirements analysis methodology is described below:
a. Stakeholder Identification. The objective of stakeholder identification is to identify stakeholders who are potential “owners” of requirements, or who can facilitate effective communication relating to requirements. These stakeholders
are subsequently encouraged to make input into the definition of the requirements, are consulted regarding requirements issues, and are invited to “sign-off” on their subsets of requirements.
b. Document Review. Documents, if any, which contain or relate to intended use, requirements, and goals are examined, with a view to identifying key issues that should be resolved with stakeholders before requirements analysis proceeds too
far. This review provides input into the planning for conduct of the requirements analysis.
c. Context Flow Analysis. This analysis tracks the state of the world outside of the system on a whole of life basis, from system cradle to system grave. All requirements of the system originate in these contexts, with one class of exception. Stakeholders are mapped to the contexts, often resulting in the identification of additional stakeholders. The main work
product of this analysis is subsequently used to structure analysis work, checks and dialog with stakeholders. See Figure 2.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| Requirements Analysis that Works 171115.pdf | application/pdf | 335.71 KB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
Innumerable studies have concluded that requirements problems are the single biggest contributor to cost overruns, schedule slippages and loss of capability in systems and software projects. Cost impacts alone of 10%, 20%, 50%, 80% and more are regularly reported by practitioners and researchers. And yet, the cost of making substantial improvements in requirements quality is considerably lower than these cost impacts, typically 0.1 – 2% of total development cost - if appropriate skills and methods are applied. Requirements analysis (the capture and validation of requirements through analysis of the problem domain) provides the tools for transforming the inadequate to the adequate, requirements-wise.