Advanced Topics in

Requirement
Engineering
Agenda:

Recap

Requirement Analysis

Conclusion Q/A

Group Activity
INTRODUCTION
Analysis is the process used to:

• Examine
• Decompose and synthesize information to
further understand it.
• To understand the Features and Capabilities
of the solution.
 • Throughout the analysis domain,
requirements are captured in various
formats and decomposed to obtain the
necessary level of detail.
INTRODUCTI
ON • Similar to elicitation, analysis is performed
using a progressive and iterative approach
to examine the information to lower levels
of detail to develop a set of requirements.
 INTRODUCTION

The iteration and analysis continues until a sufficient level of

requirements needed to formulate the solution is obtained.

ln an adaptive life cycle, elicitation and analysis occur throughout the

project or program as part of defining the initial backlog, grooming the
backlog to refine requirements, and analyzing details for each iteration.

This section describes the processes Success Factors

recognized as good practices in Activities And
requirements analysis, including: Techniques.
1 • Achieving the objectives of
requirements analysis is dependent on
Requirements numerous factors as described in the
following sections.
Analysis
Success – 1.1 Skilled Resources
– 1.2 Communication
Factors – 1.3 Collaboration
1.1 Skilled • Having the correct talent is vital to
conducting meaningful analysis.
Resources
• Once the process has started, there is
little opportunity to train and acquire
the right skill set to effectively perform
analysis.
1.2 • Throughout the analysis, frequent and
timely communication with the project
Communicati team, stakeholders, etc., is key to
improving the quality of the
on requirements.

• This communication helps to further

clarify uncertainties and avoid costly
rework in downstream domains.
1.3 • The success of analysis greatly depends on
establishing a collaborative working relationship
Collaboration between the stakeholders involved in the
requirements effort and the person performing
the analysis.

• This environment enables open and effective

communication that may help the discovery of
stakeholder expectations that should be
examine carefully during the refinement of the
requirements.
2 • Analysis plays a critical role in
confirming that the requirements are
Requirements complete, accurate, and aligned with
the business goals and objectives.
Analysis
Activities • In practice, analysis is performed using
the outputs from requirements
elicitation and includes planning,
analyzing, and documenting results.
2 • 2.1 Plan for Analysis
– 2.1.1 Activities
Requirements • 2.2 Conduct Analysis Activities
– 2.2.1 Identify, Analyze, and Document
Analysis Requirements Attributes
– 2.2.2 Select the Requirements Models
Activities – 2.2.3 Prioritize Requirements
– 2.2.4 Allocate and Derive Requirements
– 2.2.5 Verify Requirements
– 2.2.6 Validate Requirements
• 2.3 Document and Communicate Results
2.1 Plan for • Establishing a strategy for how analysis
will be performed includes determining:
Analysis – what activities and techniques will
be used to yield the greatest benefit
based on what is known about the
project or program.
– Defining which tools to apply
– How the outputs will be
documented.
2.1 Plan for • The activities and techniques executed during
this requirements analysis are governed by the
Analysis requirements management plan.

• However, activities may be refined and adjusted

as more details are discovered throughout the
project.

• Planning for effective requirements analysis also

relies on careful review and consideration of
additional factors
2.1.1 • Evaluate what types of analyses will be
performed and identify the appropriate analysis
Activities techniques and tools to employ.

• Visual models, for example, provide context to

better understand and clearly convey
information.

• It is important to identify existing models in the

organization to leverage as a starting point for
analysis.
2.2 Conduct • Requirements analysis is more than analyzing
information to further:
Analysis – Understand it
– Complete it AND
Activities •
– Improve it
It also involves structuring requirements in
different views to:
– Capture varying perspectives
– Evaluating requirements for certain
attributes And
– Integrating the collective information into
written documentation.
2.2 Conduct • Conducting analysis includes six main
components, which are described in below
Analysis sections.

Activities – 2.2.1 Identify, Analyze, and Document

Requirements Attributes
– 2.2.2 Select the Requirements Models
– 2.2.3 Prioritize Requirements
– 2.2.4 Allocate and Derive Requirements
– 2.2.5 Verify Requirements
– 2.2.6 Validate Requirements
2.1.1 Identify, Analyze, and Document
Requirements Attributes

Requirements attributes are specific characteristics or traits that capture key information
about a requirement, such as the source, owner priority, complexity, rationale, and
status.

Requirements attributes are elicited as requirements are elicited.

This information is used to aid in requirements traceability and monitoring throughout

the project life cycle.

Specifying attributes is critical to the analysis process as the information can be filtered,
sorted, and validated to reveal discrepancies that may require additional analysis.
 A component of analysis is the development of
graphical or text models, which are helpful in finding
gaps in information and identifying extraneous
information.

2.2.2 Requirements are modeled and refined to provide

Select the greater insight and correctness and to elicit additional
information to define the details necessary to build
Requireme the product, service, or result.
nts Models
As some models are better suited for certain
environments, it is important to select requirements
models based on specific characteristics, type of
project, timing, purpose, and level of abstraction.
2.2.3 Prioritize Requirements

Requirements prioritization is an important step in managing product scope

It is used to rank requirements in the order of importance.

It is used to assist key stakeholders in making tradeoffs between requirements and to analyze the relative
value of requirements against one another.

Since it may not be feasible to implement all requirements within the project constraints, prioritization
helps to focus the stakeholders on the most critical requirements based on the prioritization criteria.
2.2.3
Prioritize
Requirements
• It is essential to define the
criteria that will be used in
prioritization, and this is
typically accomplished during
requirements management
planning.
• Common types of criteria
include:
– Value,
– Risk level,
– Complexity,
– Cost, and
– Regulatory constraints.
2.2.3 Prioritize Requirements

• These criteria provide the foundation for continual prioritization as requirements

evolve and change over the project life cycle.

• Several techniques exist that can be used to drive prioritization.

• Some commonly used techniques include MoSCoW, voting, and timeboxing, which are
further described.
2.2.4 Allocate and Derive Requirements

• Requirements Allocation is the process of assigning requirements to functions,

solution components, and organizational entities.
• Requirements are subsequently allocated to specific releases or iterations.
• This activity occurs in the analysis process until in-scope requirements have been
apportioned across the solution.
• Allocation helps assure that the proposed solution will be delivered in a manner and
order that maximize value to the business.
• How requirements are allocated can change the amount of value delivered by the
solution.
2.2.4 Allocate and Derive Requirements

• Deriving Requirements is the process of analyzing requirements into more detail to

extrapolate more granular discrete requirements and remove ambiguity.
• When requirements are broadly defined, they should be progressively elaborated to a
greater level of detail or decomposed into multiple discrete requirements to aid in the
implementation of higher-level requirements or to reduce ambiguity.
• This process results in derived requirements, which are important to confirm that the
required functionality is present.
• It provides the basis for subsequent verification and validation.
 Create a group of 4-5 based Pick a project from next
on your Zodiac signs. slide.

Each member of group have

Break the project into 4-5 to analyse the given module
modules. and draw list of
requirement

Activity time:
Projects
Hospital
Social Networking Car Rental
Management
Platform: System:
System:

Personal Finance
Fitness Tracking Online Music
Management
System: Player:
System:

Employee
Travel Planning
Management
System:
System: