SOFTWARE REQUIREMENT ENGINEERING

TOPIC:REQUIREMENT PRIORTIATION

SUBMITTED TO:
MAM MEMONA

DEPARTMENT OF COMPUTER SCIENCE

 CONTENT:
 REQUIREMENT PRIORITIZATION
 TECHNIQUES
 WHO PRIORITIZE THE REQUIREMENT
 NEED OF REQUIREMENT PRIORITIZATION
 REQUIREMENT PRIORITIZATION STRETIGIES
 GOALS OF REQUIREMENT PRIORITIZATION
 ADVANTAGES AND DISADVANTAGES
 REFRENCE
REQUIREMENTS:
“A condition or capability needed by a stakeholder to solve a problem or achieve an objective.”
Requirements are a set of prioritized needs from all the involved stakeholders that form the base for the functionalities or features to be included as a part of the solution

PRIORITIZATION:
Prioritization is the process by which a set of items are ranked in order of importance.

To prioritize is to organize or complete things in order of their

importance. When you do the most important tasks first and then
continue on to tasks of lesser importance
JZ
 REQUIREMENT PRIORITIZATION:

 Requirement prioritization is used in

Software product management for determining which
candidate requirements of a software product should be
included in a certain release.

 Requirements are also prioritized to minimize risk during

development so that the most important or high risk
requirements are implemented first.

 Its basic idea is that for all pairs of (candidate) requirements a

person assesses a value or a cost comparing the one
requirement of a pair with the other.
TECHNIQUES OF REQUIREMENT PRIORTIZATION:

Numerous methods on how to prioritize requirements have been developed.

1. Ranking:

When you rank requirements on an ordinal

scale, you give each one a different numerical
value based on its importance.

2. Numerical Assignment (Grouping):

This method is based on grouping requirements into different
priority groups with each group representing something
stakeholders can relate to.
3. Analytic Hierarchy Process (AHP):

In essence, stakeholders decompose their goal into smaller sub-problems,

which can easily be comprehended and analyzed (in the form of a
hierarchy).

4. Bubble Sort Technique:

To prioritize requirements using bubble sort, you take two
requirements and compare them with each other. If you
find out that one requirement should have greater priority
over the other, you swap them accordingly.
5. Hundred Dollar Method:
This simple method is useful anywhere multiple stakeholders need
to democratically vote on which requirements are the most
important.

6. MoScoW Technique:
Instead of numbers, this method uses four priority groups:
MUST have, SHOULD have, COULD have, and WON'T
have.
The acronym represents the following:
•MUST (Mandatory)
•SHOULD (Of high priority)
•COULD (Preferred but not necessary)
•WOULD (Can be postponed and suggested for future
execution)
WHO PRIORITIZE THE REQUIREMENTS:
Requirements are also prioritized to minimize risk during development so that the most important or high risk requirements are implemented first.
Prioritization must be done in collaboration with the stakeholders (customer, product owner, project sponsor, and users) as early as possible so that alternatives can be explored.
n

 vc
 NEED OF PRIORITIZE THE REQIREMENTS

 Prioritization helps you manage your requirements and

your resources.
 Prioritization also helps manage the unknown
unknowns.
 A key part of requirements management is managing
change.
 With prioritization, you improve communication because
you’re taking the guesswork out of the project.
 Prioritization is also helpful when releasing software in
phases.
 Requirements Prioritization Strategies

 Prioritization Guidance
 Prioritization Goals
 Priority Scales
 Priority Semantics
JHZZ
These topics show you how to prioritize work and improve
your efficiency:
 HOW TO PRIORITIZE WORK?
• Identify Your Goals.
• Create a List of Your Tasks.
• Assess Importance and Urgency
• Measure Value.
• Order Similar Tasks by Effort
• Be Open to Changes.
• Know What to Drop
 HOW DO YOU FOCUS ON YOUR GOAL?
j
 NUMERICL ASSIGNMENT:
ADVANTAGES:
Low complexity with High speed

Cope with large size of requirements

Easy to use
DISADVANTAGES:
Low rate of reliability
Low level of fault tolerance

MoSCoW:
ADVANTAGES:
Easy to use for small size of requirements.
DISADVANTAGES:
Medium complexity with acceptable speed according to requirements
size Not scalable for medium to large size of requirements.

 Priority Groups:
ADVANTAGES:
Easy to use
Reliable results
High level of fault tolerant
DISADVANTAGES:
Medium complexity with acceptable speed according to requirements
size .
Not scalable for medium to large size of requirements.
 Bubble Sort:
ADVANTAGES:
Good in small size of requirements.
Disadvantages:
Not easy to use
High complexity with low speed
Not reliable results
Low level of fault tolerant
Not cope and become very complex with medium to large size of requirements
AHP:
Advantages:
Excellent in small size of requirements


 DISADVANTAGES:
Not easy to use
High complexity with low speed
Not reliable results
Low level of fault tolerant
Not cope and become inefficient with
medium to large size of requirements
Hundred Dollar:
Advantages:
Low complexity with high speed
Easy to use
Disadvantages:
Medium level of reliability
Not cope with large size of requirements


 REFRENCES:
 https://www.slideshare.net/SyedZaidIrshad/requirements-prioritiza
tion-75457661
 https://www.bridging-the-gap.com/requirements-prioritization/
n

 h