Requirements

Engineering (RE)
DR. AMIRUZZAMAN

Introduction
Understand, analyze and document what customer requires.

Basis of RE (Hull, Jackson & Dick, 2011) :

Project planning
Risk management
Acceptance testing
Trade off
Change control

Requirement
From Pohl and Rupp (2015):

(1) A condition or capability needed by a user to solve a problem or achieve an

objective
(2) A condition or capability that must met or possessed by a system or system
component to satisfy a contract, standard, specification, or other formally
imposed documents.
(3) A documented representation of condition or capability as in (1) or (2).

Stakeholder
From Pohl and Rupp (2015):

A stakeholder of a system is a person or an organization that has an (direct or

indirect) influence on the requirements of the system.

A stakeholder is someone who likes your work

True

False

Requirements Engineering (RE)

From Pohl and Rupp (2015):

(1) Requirements engineering is a systematic and disciplined approach to the

specification and management of requirements with following goals:
(1.1) Knowing the relevant requirements, achieving a consensus among the
stakeholders about these requirements, documenting them according to given
standards, and managing them systematically.
(1.2) Understanding and documenting the stakeholders desires and needs, the
specifying and managing requirements to minimize the risk of delivering a system
that does not meet the stakeholders desires and needs.

Core activities of RE
From Pohl and Rupp (2015):
Elicitation
Documentation
Validation and negotiation
Management

In win-win negotiation, the customer's needs are

met even though the developer's need may not be.
True

False

Characteristics of a Requirements Engineer

From Pohl and Rupp (2015):
Analytic thinking
Empathy
Communication skills
Conflict resolution skills
Moderation skills
Self-confidence
Persuasiveness

Types of requirements
From Pohl and Rupp (2015):
Functional requirement
Quality requirement
Constraint

Functional requirement
From Pohl and Rupp (2015):

A functional requirement is a requirement concerning a result of behavior that

shall be provided by a function of the system.

Quality requirement
From Pohl and Rupp (2015):

A quality requirement is a requirement that pertains to a quality concern that is

not covered by functional requirements.

Constraint
From Pohl and Rupp (2015):

A constraint is a requirement that limits the solution space beyond what is

necessary for meeting the given functional requirements and quality
requirements.

Problems with RE
From Hull, Jackson and Dick (2011):

Requirements either poorly organized, poorly expressed, weakly related to

stakeholders, changing too rapidly or unnecessary; unrealistic expectations.
Management problems of resources failure to have enough money, and lack of
support or failure to impose proper discipline and planning; many of these arise
from poor requirements control.
Politics which contributes to the first two problems.

Reasons for project failure

From Hull, Jackson and Dick
(2011):

Project success factors

From Hull, Jackson and Dick
(2011):

References
Hull, E., Jackson, K., & Dick, J. (2011). Requirements engineering. Springer Science
& Business Media.
Pohl, K., & Rupp, C. (2015). Requirements engineering fundamentals: a study guide
for the certified professional for requirements engineering exam-foundation level-IREB
compliant. Rocky Nook, Inc.