requirements and Constraints
Benefits. This is the first process that:
- Confirms structural attributes of software
functionality, usability, reliability, supportability,
etc.) with the user
- Places the "User Concerns List" here in the process to capture user concerns
earlier rather than later
- Applies a unique RPIPR model for interviewing…
First build trust…then, gather requirements: Rapport, Process, Interview, Process, Rapport
- Allows the BA to understand true needs to avoid biasing
needs with technology
and essential tools of this crucial step in requirements gathering including
those as shown in the following chart, lay the foundation for
the success or failure of project plans.
"Without a method [like
this], the user giveth and the developer taketh away."
- Steve Bender
This WEBinar will go deeper into the strategies and tools
used in Steps 2 and 3 of the High Quality Requirements Model.
According to a
survey by Compuware-RQNG, only 27
percent of BAs think their organizations have adopted tools to make them more
Statement of Requirements
User Concerns List
Implementation Requirements (Constraints)
Implementation Reqts List
The High Quality Requirements Model is a six step requirements gathering process useful for end users, business
analysts, and developers. By means of its structure, it
automatically assures mission-based, needs-based
that are not solutions-driven.
The BA as facilitator. What is unique about this WEBinar is that it will explain
a process that
emphasizes the role of the BA as a facilitator.
Are you a hybrid creature expected to move with ease between the worlds of business and technology?
Conducted: Wed., Feb. 7, 2007
Want all 4 WEBinars in the series at a group discount?
If so, click
Note: for more detail on the key learning objectives of the
full course go to Requirements