Requirements express conditions that any acceptable solution should meet. Business requirements specify end-user conditions regarding the functionality, performance or usability of the solution. System specifications define technological conditions such as operating system, programming language, database, hardware configuration, etc.
Prioritized requirements
If you don't know where your going, any road will get you there. . .
Business requirements clearly define the business need
Requirements form the basis for testing
Prioritized requirements ensure that the most important dimensions are realized first
Enables requirements tracing
Conscious, up-front effort reduces rework and revisions
Requirements need to be defined by the business owners to ensure that they get the technology support they need
When should you gather prioritized requirements?
You should gather and prioritize requirements before you start to develop the solution. Requirements gathering is an ongoing activity that starts before the project is initiated and ends, if ever, when the solution is taken out of production. The challenge is to gather the right level of requirements at each phase of the project and to be aware that they are subject to change.
Who should gather prioritized requirements?
Business analysts, system analysts and developers and end users need to work together to express and prioritize business and technical requirements that are clear, compatible and comprehensive.
Our e-Coaching offer is a cost-effective alternative for small groups to learn these and
other business systems analysis techniques at their own workplace or for follow-up after a
training seminar
Requirements Solutions Group offers training as well as
web-based and
on-site consulting services to support a wide range of activities within the system development life cycle all targeted exclusively to the Business Analyst, Requirements Engineer and the Subject Matter Expert.
You can also visit our
bookstore for the newest publications in the business systems analysis field
Identify Requirement Components
Every business requirement expresses or implies
a set of technical or system requirements. By identifying these
technical requirements, you will increase your understanding of
the business needs and avoid many misinterpretations.
To identify technical requirements, examine every business requirement
and extract the following types of requirements:
Business
Requirement Example:
Functional Requirement
(Action oriented)
What actions, steps or tasks have to be completed to satisfy
this requirement?
Use verb - object format.
Business
Requirement: The processing of a customer order with less than
50 items should be intuitively obvious and take no more than 1 hour
using the current hardware platform.
enter
order check
customer credit verify
item availability count
items track
processing time ..............
Informational Requirement (Data oriented)
The data necessary for a function to work. This encompasses such
varied concepts as entities, reports, screens, data elements,
metadata, etc.
Business
Requirement: The processing of a customer order with less than
50 items should be intuitively obvious and take no more than 1 hour
using the current hardware platform.
customer
data order
window date/time
stamp item
data number
of items per order ..............
Performance Requirement (Number oriented)
A measurable dimension of the system. An objective test should
exist to determine whether the product meets expectations. This
implies numbers.
Business
Requirement: The processing of a customer order with less than
50 items should be intuitively obvious and take no more than 1 hour
using the current hardware platform.
less than 1 hour processing time for 1 order of 50 items ..............
Constraining Requirement (Limit oriented)
A limit on how the functions will be performed. Forces external
to the project mandate these rules but they affect the operation
of the system.
Business
Requirement: The processing of a customer order with less than
50 items should be intuitively obvious and take no more than 1 hour
using the current hardware platform.
current
hardware platform ..............
Subjective Requirement (Feeling oriented)
Aspects of the requirements that depend on how someone "feels"
or interprets a word.
Business
Requirement: The processing of a customer order with less than
50 items should be intuitively obvious and take no more than 1 hour
using the current hardware platform.
Pick
any uneven number below ten as a baseline (3, 5, 7 or 9).
Larger numbers enable refined differences but are
typically more difficult to assign.
Every
requirement is assigned the default priority which is in the center
of your baseline
Example: 2 for a baseline
of 3 5 for a baseline
of 9 ......
For
every requirement that you want to assign a higher priority, you
must select another requirement that will be assigned an offsetting
lower priority.
The average priority will always be the center of
your baseline.
Example:
Start Prioritization (Baseline 5)
Priority
1 (HI)
Priority
2
Priority
3
Priority
4
Priority
5 (LOW)
add sales tax select
billing cycle view bill
on Internet combine
bill select
language GUI application select
payment method help desk invoice
customer 5 sec response
time multimedia
support
Example: Result
of Prioritization (Baseline 5)
Priority
1 (HI)
Priority
2
Priority
3
Priority
4
Priority
5 (LOW)
add sales tax invoice
customer
select payment method
select
billing cycle combine
bill GUI application help
desk 5 sec
response time