Resolving requirements conflicts and inaccuracies,
Steps 4, 5, & 6
Benefits of this WEBinar:
- Understand the balance between the costs and the benefits of the new requirement
- Resolve technical conflicts between what users want and what is economically achievable with technology
- Use risk assessment to properly balance benefits with hidden costs and risks
- Balance structural software characteristics to minimize software failure
- Resolve emotional conflicts between different groups that sometimes arise
- Verify requirements with various models and measurements to prove requirements are correct
- Minimize high cost of erroneous requirements
- Prevent propagation of incorrectly installed (and otherwise correct) requirements
This WEBinar (rqts conflicts) will go deeper into the strategies and tools
used in the final Steps 4, 5, and 6 the Quality Requirements Model. (See
table below.)
| Step |
Phase |
Deliverable |
Tools |
| 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 |
The Requirements Model is a 6 step requirements gathering process useful for end users, business
analysts, and developers. By means of its structure, it
automatically assures mission-based, needs-based
requirements
that are not solutions-driven.
Resolving Conflicts and
Trade-offs
What to do—without playing the “You-bet-your
-job-game” - when, for example:
-
Users can’t agree and are scrimmaging
-
Business analysts are ignoring customer
input
-
Customers are ignoring business analysts
-
Powerful people
are skirting
or manipulating
the priority-setting process
…and other requirements gathering people-related
problems?
Answer: Agree on a process to
resolve these conflicts like the process we'll
demonstrate in this WEBinar.
Verifying Requirements
The objective of Step 5 - Verify Requirements
is to ensure that the requirements in the Statement of
Requirements do, in fact, not only meet the
business need but are also defect-free.
Important Points about Validating Requirements
Many of the tools in this step ought to be
carried out by or with the assistance of the
customer.
The more tools that are used, the higher the
quality of the requirements.
Defects During Requirements Definition
The following are defects that frequently occur
during the requirements definition phase because
they are inadequate or partially missing:
- Operating rules (or information)
- Performance Criteria
- Environment information
- System mission information
Validating
Requirements, Step 6
This WEBinar will describe important techniques to quality control check the accuracy of the
Final Requirements Statements before they are distributed. In addition, important techniques will be shown to insure that these correct, QC'ed requirements are correctly installed.
Conducted: Wed., Mar 7, 2007
Want all 4 WEBinars in the series at a group discount?
If so, click here.
On demand recording
More Detail
Note: for more detail on the key learning objectives of the
full course go to Requirements
Gathering.
|
