Specify and Model Requirements and Designs

Specify and Model Requirements and Designs

Purpose or Need
To analyze, synthesize, and refine elicitation results into requirements and designs.

Value Solution

Requirements and designs specification and Requirements and designs which are specified
analysis provides a basis for discussion with and modelled in the form of text, matrices, and
stakeholders to reach a conclusion about diagrams.
solution options.

Techniques Stakeholder

Frequently used techniques: Typically involves any stakeholders that

– Acceptance and Evaluation Criteria; could have relevant knowledge or experience
– Data Modelling; to participate in these activities.
– Interface Analysis;
– Use Cases and Scenarios;
– User Stories.
Refer to the BABOK Guide v3 for the
complete list of techniques.

Description of Change
Specify and Model Requirements and Designs describes a set of requirements or designs in enough detail using
suitable analytical techniques.

Reference (Guidelines and Tools) Task Inputs and Outputs

The following resources, if they exist, can be
used to transform the inputs into the outputs: Input Task Output or Deliverable

– Modelling Notations/Standards; Elicitation

Specify and Model Requirements Designs
– Modelling Tools; Results
Requirements and
Designs
(Specified and
Modelled)
(Specified and
Modelled)
– Requirements Architecture;
– Requirements Life Cycle Management Tools;
– Solution Scope.

Consider...
This task is about capturing important business information that can be effectively reviewed and communicated to build
a shared understanding of the desired future changes. This is important for different types of initiatives.
Example: Creating models that represent different views of the enterprise can be used to support the ongoing
delivery of value.
See BABOK Guide – 11.4 The Business Architecture Perspective
Certifications: ECBA, CCBA, CBAP – Refer to the BABOK® Guide for study purposes

© 2022 International Institute of Business Analysis.

 Verify Requirements and Designs
Verify Requirements and Designs
Purpose or Need
To ensure that requirements and designs specifications and models meet quality standards and
are usable for the purpose they serve.

Value Solution

Verification ensures that the requirements and Requirements and designs of sufficient quality
designs have been defined correctly, are ready that can be used as a basis for further work.
for validation, and provides the information
needed for further work to be performed.

Techniques Stakeholder

Frequently used techniques: Typically involves subject matter experts

– Acceptance and Evaluation Criteria; and any additional stakeholders with
– Item Tracking; relevant knowledge or experience to verify
– Metrics and KPIs; requirements and designs.
– Reviews.
Refer to the BABOK Guide v3 for the
complete list of techniques.

Description of Change
Verify Requirements ensures that a set of requirements or designs has been developed in enough detail to be
usable by a particular stakeholder, is internally consistent, and is of high quality.

Reference (Guidelines and Tools) Task Inputs and Outputs

The following resources, if they exist, can be
used to transform the inputs into the outputs: Input Task Output or Deliverable

– Requirements Life Cycle Requirements Designs Verify

Requirements Designs
Management Tools. (Specified and
Modelled)
(Specified and
Modelled)
Requirements
and Designs
(Verified) (Verified)

Consider...
The appropriate level of verifying requirements and design can improve the quality of outcomes and reduce the
amount of rework.
Example: Consider a custom software build for a client requesting a new inventory management system. Ongoing
verification with relevant experts ensures high-quality requirements and designs which can be used to develop the
desired software with increased confidence.
See BABOK Guide – 11.3 The Information Technology Perspective
Certifications: ECBA, CCBA, CBAP – Refer to the BABOK® Guide for study purposes

© 2022 International Institute of Business Analysis.

 Validate Requirements and Designs
Purpose or Need
To ensure that all requirements and designs align with the business requirements and support the delivery
of needed value.

Value Solution

Having stakeholders validate the Validated requirements and designs that

requirements and designs will ensure that are aligned with the business goals and
requirements and designs will deliver value. objectives of the change, and will deliver
value to stakeholders.

Techniques Stakeholder

Frequently used techniques: Typically involves subject matter experts

– Acceptance and Evaluation Criteria; and any additional stakeholders with
– Financial Analysis; relevant knowledge or experience to validate
– Item Tracking; requirements and designs.
– Metrics and KPIs;
– Reviews.
Refer to the BABOK Guide v3 for the
complete list of techniques.

Description of Change
Validate Requirements ensures that stakeholder, solution, and transition requirements align to the business
requirements, that the designs satisfy the requirements, and that both requirements and designs deliver
business value and support the organization’s goals and objectives.

Reference (Guidelines and Tools) Task Inputs and Outputs

The following resources, if they exist, can be
used to transform the inputs into the outputs: Input Task Output or Deliverable

– Business Objectives; Requirements Designs Validate

Requirements Designs
– Future State Description; (Specified and (Specified and Requirements
(Validated) (Validated)
Modelled) Modelled) and Designs
– Potential Value;
– Solution Scope.

Consider...
Every type of initiative requires validation of the outcomes produced. Depending on the approach taken, this can be
ongoing throughout the work or at milestone deliveries.
Example: When using adaptive approaches for developing new products, validation occurs through frequent customer
feedback sessions.
See Guide to Product Ownership Analysis – Sec 5.6 Learn Fast
Certifications: ECBA, CCBA, CBAP – Refer to the BABOK® Guide for study purposes

© 2022 International Institute of Business Analysis.

 Define Requirements Architecture
Purpose or Need
To ensure that the requirements and designs collectively support one another to achieve the objectives fully.

Value Solution

A requirements architecture ensures that Defined requirements architecture that shows

all requirements and designs form a single the interrelationships among requirements and
whole that supports the overall business designs.
objectives and produces a useful outcome for
stakeholders.

Techniques Stakeholder

Frequently used techniques: Different stakeholders may assist in

– Data Modelling; defining and confirming as well as assessing
– Functional Decomposition; the completeness of the requirements
– Process Modelling; architecture.
– Scope Modelling;
– Workshops.
Refer to the BABOK Guide v3 for the
complete list of techniques.

Description of Change
Define Requirements Architecture structures all requirements and designs so that they support the overall
business purpose for a change and that they work effectively as a cohesive whole.

Reference (Guidelines and Tools) Task Inputs and Outputs

The following resources, if they exist, can be
used to transform the inputs into the outputs: Input Task Output or Deliverable

– Architecture Management Software; Information Define

Requirements
– Legal/Regulatory Information; Requirements Management Solution Scope Requirements
Architecture
Approach Architecture
– Methodologies and Frameworks.

Consider...
This can be a rigorous process for large scale predictive initiatives or most often (but not always) less rigorous for
adaptive initiatives.
Example: Creating enterprise models that can be used for ongoing value delivery often use commercially available or
industry standardized reference models.
See BABOK Guide – 11.4 The Business Architecture Perspective
Certifications: ECBA, CCBA, CBAP – Refer to the BABOK® Guide for study purposes

© 2022 International Institute of Business Analysis.

 Define Design Options
Purpose or Need
To define the solution approach, identify opportunities to improve the business, allocate requirements across
solution components, and represent design options that achieve the desired future state.

Value Solution

An understanding of the potential of the Defined design options to satisfy the

future state. business need.

Techniques Stakeholder

Frequently used techniques: Typically involves project managers,

– Brainstorming; implementation subject matter experts,
– Document Analysis; operational support, and any additional
– Mind Mapping; stakeholders identified.
– Root Cause Analysis;
– Vendor Assessment.
Refer to the BABOK Guide v3 for the
complete list of techniques.

Description of Change
Define Design Options identifies, explores, and describes different ways of meeting the business need. Possible
solution approaches include creating (I.e. building), purchasing (I.e. buying), or a combination of both.

Reference (Guidelines and Tools) Task Inputs and Outputs

The following resources, if they exist, can be
used to transform the inputs into the outputs: Input Task Output or Deliverable

– Existing Solutions; Requirements

Requirements Define Design
– Future State Description; (Validated, Change Strategy
Architecture Options
Design Options
Prioritized)
– Requirements (Traced);
– Solution Scope.

Consider...
Avoid deciding on the ideal solution design too early, and remember that the best designs often emerge from ongoing
conversations with customers to better understand context and needs.
Example: There are factors to consider when redesigning an end-to-end business process. The process redesign team
will typically identify options that can be discussed with business experts.
See BABOK Guide – 11.5 The Business Process Management Perspective
Certifications: ECBA, CCBA, CBAP – Refer to the BABOK® Guide for study purposes

© 2022 International Institute of Business Analysis.

 Analyze Potential Value and Recommend Solution
Purpose or Need
To estimate the potential value for each design option and to establish which one is most appropriate to
meet the enterprise’s requirements.

Value Solution

To identify and recommend the solution Recommendation of the most appropriate

option that delivers the greatest overall solution based on an evaluation of all defined
potential value. design options.

Techniques Stakeholder

Frequently used techniques: Typically involves sponsors, project managers,

– Acceptance and Evaluation Criteria; subject matter experts, customers, users, and
– Estimation; any additional stakeholders identified.
– Financial Analysis;
– Metrics and KPIs;
– Risk Analysis and Management.
Refer to the BABOK Guide v3 for the
complete list of techniques.

Description of Change
Analyze Potential Value and Recommend Solution assesses the business value of a potential solution and
compares options, including trade-offs. Each option has a mix of advantages and disadvantages to consider.
The potential value of a solution to a stakeholder is based on the benefits delivered by that solution, associated
costs, and identified constraints.

Reference (Guidelines and Tools) Task Inputs and Outputs

The following resources, if they exist, can be
used to transform the inputs into the outputs: Input Task Output or Deliverable

– Business Objectives; Analyze Potential

Value and Solution
– Current State Description; Potential Value Design Options
Recommend Recommendation
– Future State Description; Solution

– Risk Analysis Results;

– Solution Scope.

Consider...
There’s rarely one correct answer or one perfect solution. Every team needs to find methods for determining what to
recommend as the best way forward.
Example: When deciding on how best to address a business challenge, data teams often use criteria to evaluate
recommendations from analytic results that are best aligned with business needs.
See Guide to Business Data Analytics – 2.5.1 Recommend Actions
Certifications: ECBA, CCBA, CBAP – Refer to the BABOK® Guide for study purposes

© 2022 International Institute of Business Analysis.