Overview of requirements model
How often have you
heard, "I'll know it when I see it."? This WEBinar concentrates on a process model of
requirements gathering. Many of us are tired of implementing wants rather than
needs, working with opinions rather than facts, and proposed solutions
rather than real issues identified through problem identification.
Statistically, the distribution of requirements defects is
as follows: 10% extra requirements,
30% incorrect requirements, and 60% missing requirements. This
WEBinar will introduce a process to eliminate these
defects.
"There's no sense being exact about
something if you don't even know what you're talking about. "
-- John von Neumann
The focus is a six (6) step
requirements gathering process useful for end users, business
analysts, and developers. The model's structure automatically assures mission-based, needs-based requirements
that are not solutions-driven and so thorough as to not miss
any requirements. Background for the
structure, and explanation of the steps will be included.
Here is a chart that explains the phase, deliverable and
tools of each of the six steps. Join us!
Step |
Phase |
Deliverable |
Tools |
1 |
Identify
Business Needs |
User Statement
of Reqts |
Process Charts
Problem Statement
Requirements User List
Critical Success Factors
Problem Stmt
User Stmt of Reqts |
2 |
Analyze Bus.
Reqts |
Preliminary
Stmt of Reqts |
Modeling/Prototyping
Quality Survey
System Characteristics
User Concerns List
Interview Questionnaire |
3 |
Analyze
Implementation Reqts |
Quality
Criteria
Control Analysis
Implementation List |
4 |
Resolve
Conflicts & Trade-offs |
Final
Stmt of Reqts |
JAD
Cost/Benefit Analysis
Risk Analysis
Conflict Matrix |
5 |
Verify Reqts |
Measures
Model Balancing
Walkthroughs, Reviews
User Rating |
6 |
Validate
Reqts |
Reverse
Engineering
Reqts Tracing
Testing |
Conducted December 6, 2006
Want all 4 WEBinars in the series at a group
discount?
If so, click here.
On Demand REcording
Key Objectives
Note: For more detail on the key learning objectives of the
full course go to Requirements
Gathering. |