Requirements

Analysis and Design

Definition
Chapter Study Group
Learning Materials
2015, International Institute of Business Analysis™
(IIBA®).

Permission is granted to IIBA Chapters to use and

modify this content to support chapter activities.

All other rights reserved.

2
Study Session Schedule
Session Date Chapters Topics
1 Jan 25 1&2 Introduction and BA Key Concepts

2 Feb 15 3 Business Analysis Planning and Monitoring

3 Mar 15 4 Elicitation and Collaboration

4 Apr 12 5 Requirements Life Cycle Management

5 May 17 6 Strategy Analysis

6 Jun 14 7 Requirements Analysis and Design Definition

7 Jul 12 8 Solution Evaluation

8 Sep 13 9 Underlying Competencies & Perspectives

9 Oct 11 10 Techniques

10 Nov 1 11 Jeopardy Game and Mock Exam

3
AGENDA
• (6:00 – 6:10) Review of Chapter 6 (10 minutes)
• (6:10 – 6:35) 7.1 Specify and Model Requirements (25 minutes)

• (6:35 – 6:55) 7.2 Verify Requirements (20 minutes)

• (6:55 – 7:15) 7.3 Validate Requirements (20 minutes)

• (7:15 – 7:30) Break (15 minutes)

• (7:30 – 7:50) 7.4 Define Requirements Architecture (20 minutes)
• (7:50 – 8:10) 7.5 Define Design Options (20 minutes)
• (8:10 – 8:30) 7.6 Analyze Potential Value and Recommend
Solutions (20 minutes)

• (8:30 – 8:45) Group practice Strategy Analysis 4

INTRODUCTION
• Chapter 7 of BABOK v3

• Consists of tasks performed to:

• Describe requirements using analytical techniques
• Ensure requirements and designs are internally consistent and high
quality
• Ensure requirements and designs deliver business value
• Structure requirements and designs so they cohesively support the
business purpose
• Identify potential solutions
• Recommend the solution that provides the greatest overall value

Requirements Analysis and Design Definition 5

INTRODUCTION
• 7.1 Specify and Model Requirements

• 7.2 Verify Requirements

• 7.3 Validate Requirements

• 7.4 Define Requirements Architecture

• 7.5 Define Design Options

• 7.6 Analyze Potential Value and Recommend Solutions

Requirements Analysis and Design Definition 6

INTRODUCTION

Requirements Analysis and Design Definition 7

INTRODUCTION

Requirements Analysis and Design Definition 8

INTRODUCTION - APPLYING THE BUSINESS
ANALYSIS CORE CONCEPT MODEL

Core Concept Usage in Requirements Analysis & Design Definition

Change Use requirements and designs to define the change
Need Analyze needs to recommend a solution that meets those
needs
Solution Define solution options and recommend one that is most
likely to address the need
Stakeholder Tailor requirements and designs so they are understandable
by stakeholder groups
Value Analyze and determine the potential value of each solution
option
Context Model an describe the context in ways that are
understandable by all stakeholders

Requirements Analysis and Design Definition 9

7.1 Specify and Model
Requirements
7.1 SPECIFY AND MODEL REQUIREMENTS

• Purpose
• Analyze information derived from stakeholders.
trkeb/tawlef
• Synthesize information derived from stakeholders.
• Refine information derived from stakeholders.

• Description
• Describes the practices for analyzing information elicited from
stakeholders.
• Where focused on understanding needs, outputs are REQUIREMENTS
• Where focused on specifying solutions, outputs are DESIGNS
• Includes capturing information about attributes or metadata about the
requirements.
• Specifying and modelling activities relate to all requirement types.

Requirements Analysis and Design Definition 11

7.1 SPECIFY AND MODEL REQUIREMENTS

Requirements Analysis and Design Definition 12

Requirements vs Designs

Requirements Designs
View six months sales data across A sketch of a dashboard.
multiple organizational units in a single
view.
Reduce amount of time required to pick Process model.
and pack a customer order.
Record and access a medical patient’s Screen mock-up showing specific data
history. fields.
Develop business strategy, goals, and Screen mock-up showing specific data
objectives for a new business. fields.
Provide information in English and Prototype with text displayed in
French English and French.

13
7.1 SPECIFY AND MODEL REQUIREMENTS
• Elicitation Results (any state)
• Begin with eliciting input from stakeholders.
• May be iterative, sequential or concurrent.
• Driven by audience and audience capabilities
• May require expansion or clarification.

1.
Inputs

Requirements Analysis and Design Definition 14

7.1 SPECIFY AND MODEL REQUIREMENTS
• Model Requirements
• Models are descriptive and visual.
• Provide support for analysis and communication and
understanding.
• Confirm knowledge and knowledge gaps.
• Modeling formats include:
• Matrices
2.
• Diagrams
Elements
• Model categories include:
• People and Roles
• Rationale
• Activity flow
• Capability
• Data and information
Requirements Analysis and Design Definition 15
7.1 SPECIFY AND MODEL REQUIREMENTS
• Analyze requirements
• Process of decomposing information into smaller
pieces to understand and address:
• Any changes to meet business needs
• What should stay the same to meet the business needs
• What is missing to meet the business needs
2. • What is unnecessary or superfluous to meet the business
needs
Elements • Constraints and assumptions that impact the business
needs

Requirements Analysis and Design Definition 16

7.1 SPECIFY AND MODEL REQUIREMENTS
quality
• Represent requirements and attributes
classify reqs
• Explicitly represent and articulate requirements.
• Must show characteristics of requirements
• Must show design qualities
• Requirements may differ based on stakeholders.
• Typical to have multiple points of view – hence multiple
2. requirements
• Express as multiple views
Elements
• BAs must maintain integrity and meaning of all
requirements across all stakeholders

Requirements Analysis and Design Definition 17

7.1 SPECIFY AND MODEL REQUIREMENTS
• Implement the appropriate levels of
abstraction
• Level of detail varies.
• Based upon audience
• Based upon type of requirement
• Not all stakeholders require full requirements.
2. • May provide different viewpoints based on
Elements stakeholder audience.
• Business analysis approach and selected model
may influence abstraction views.

Requirements Analysis and Design Definition 18

7.1 SPECIFY AND MODEL REQUIREMENTS
• Modelling and Notation / Standards
• Provides syntax and commonality. standard templates

• Right information and right level and context.

• Modelling tools
• Software tools may improve ease of visual
3. representation.
Guidelines
• Requirements architecture
and Tools
• Ensure models are consistent and complete.

Requirements Analysis and Design Definition 19

7.1 SPECIFY AND MODEL REQUIREMENTS
• Requirements life cycle management tools
• Software that facilitates recording, viewing, reporting
storing and sharing of work product.

• Solution scope
• The ‘guardrails’ that keep you and your stakeholders on
track. 7rasa/ soor
3.
Guidelines
and Tools

Requirements Analysis and Design Definition 20

7.1 SPECIFY AND MODEL REQUIREMENTS
• Acceptance and evaluation criteria
• Represent the criteria attributes for acceptance.

capability
• Business capability analysis
• Represents the features and functions that the enterprise
is capable of.
4.
• Business model canvas rationale
Techniques
• Provides one-page view of business drivers for
requirements.

Requirements Analysis and Design Definition 21

7.1 SPECIFY AND MODEL REQUIREMENTS
• Business rules analysis rationale

• Used to analyze business rules with requirements.

• Concept modelling data

• Defines terms and relationships important to the

requirements and the enterprise.
4.
• Data dictionary data
Techniques
• Used to list attributes of data elements.

Requirements Analysis and Design Definition 22

7.1 SPECIFY AND MODEL REQUIREMENTS
• Data flow diagrams data

• Visualize data flow requirements – helps stakeholders

“see” the data flow.

• Data modelling data

• Visualization of how data will be used in systems.

4.
• Decision modelling activity flow
Techniques
• Visualization of decisions required to enable process or
tasks.

Requirements Analysis and Design Definition 23

7.1 SPECIFY AND MODEL REQUIREMENTS
capability
• Functional decomposition
• Reduce to constituent component requirements.

• Glossary data

• Provide meaning of business and system terms.

4. • Interface analysis data

Techniques • Identify and validate inputs and outputs of process

or system solution.

Requirements Analysis and Design Definition 24

7.1 SPECIFY AND MODEL REQUIREMENTS
• Non-functional requirements analysis capability

• Define and analyze service quality of service attributes.

• Organizational modelling people

• Model roles and responsibilities and communications

lines within enterprise.
4.
• Process modelling activity flow
Techniques
• Visualization of steps required to complete a process or
task.

Requirements Analysis and Design Definition 25

7.1 SPECIFY AND MODEL REQUIREMENTS
• Prototyping capability

• An aid for stakeholders to “see” what the process or

system will “look” like.

• Roles and permissions matrix people

• Provide separation of duties (SoD) and other relevant

information about work effort and interfaces using the
4. solution.
Techniques
• Root cause analysis rationale

• Provides understanding of root cause requiring solution.

Requirements Analysis and Design Definition 26

7.1 SPECIFY AND MODEL REQUIREMENTS
• Scope modelling rationale

• Visualization of the “guardrails” of the solution.

• Sequence diagram activity flow

• Visualization of process steps and their interactions.

4. • Stakeholder list, map, or personas people

Techniques • List of stakeholders, their relationships and their

characteristics.

Requirements Analysis and Design Definition 27

7.1 SPECIFY AND MODEL REQUIREMENTS
• State modelling data

• Visualization of different states of solution based upon

events throughout solution life cycle.

• Use cases and scenarios activity flow

• Describe behaviors of people and systems acting with

the solution or system.
4.
Techniques • User stories activity flow

• Describe what people do or react to when using the

solution.

Requirements Analysis and Design Definition 28

7.1 SPECIFY AND MODEL REQUIREMENTS
• All stakeholders are key at this step for
definition
• BAs may perform this step alone, or
• Engage stakeholder groups
• Engage individual stakeholders

5. • Key information
Stakeholders • Current operating state
• Desired operating state
• Gaps between the states

Requirements Analysis and Design Definition 29

7.1 SPECIFY AND MODEL REQUIREMENTS
• Requirements (specified and modeled)
• Requirement /Design specifications:
• Ensure complete specifications metrics + diagrams

• Requirement / Design models:

• Provide models, as required to “see” and to explain
requirements
6. • Provide stakeholders the ability to “see” solution

Outputs

Requirements Analysis and Design Definition 30

7.2 Verify Requirements
7.2 VERIFY REQUIREMENTS
• Purpose
• Confirm that requirements and designs meet quality criteria.

• Description ready for validation

• Ensures correct definition of requirements and designs.

• Check point for BA and stakeholders before validation.
• Provides basis for further work.
• Validates fitness for use. based on the stackholder who gonna use it.

• Validates use of formal and informal notations.

Requirements Analysis and Design Definition 35

7.2 VERIFY REQUIREMENTS

Requirements Analysis and Design Definition 36

7.2 VERIFY REQUIREMENTS
• Requirements (specified and modelled)
• Requirements, designs or combinations are
• Well documented
• Well written
• Matrices and models correctly expressed

1.
Inputs

Requirements Analysis and Design Definition 37

7.2 VERIFY REQUIREMENTS
• Characteristics of Requirements and Designs
Quality
• Atomic
• Self-contained
• Capable of being independently understood
• Complete
2. • Sufficient to guide further work
Elements • Appropriate level of detail to continue work
• May differ based upon perspective or methodology
• Point in life cycle
• Consistent
• Aligned with identified needs of stakeholders
• Does not conflict with other requirements

Requirements Analysis and Design Definition 38

7.2 VERIFY REQUIREMENTS
• Characteristics of Requirements and Designs
Quality
• Concise mogez

• No extraneous or unnecessary detail or content

• Feasible
• Reasonable and possible within
2. • risk tolerance
Elements • Schedule and budget
• Ability to investigate further
• Unambiguous
• Clearly stated to demonstrate that it does or does not
meet associated need

Requirements Analysis and Design Definition 39

7.2 VERIFY REQUIREMENTS
• Characteristics of Requirements and Designs
Quality
• Testable
• Able to verify requirement or design fulfillment tanfez/ ta7qeq
• Acceptable levels of fulfillment depend on level of
abstraction of requirement or design

2. • Prioritized
• Ranked or grouped in terms of importance and value
Elements
• Understandable
• Uses common terminology understood by audience

Requirements Analysis and Design Definition 40

7.2 VERIFY REQUIREMENTS
• Verification Activities
• Typically performed iteratively
• Includes:
• Checking for compliance with organizational performance
standards such as right tools, right methods
• Checking for correct use of modelling, notation,
templates, forms
2.
• Checking for completeness within each model
Elements • Comparing models against other relevant models
• Checking for elements mentioned in one but missing
from others
• Ensuring terminology is understandable and consistent
• Adding examples where clarification is needed

Requirements Analysis and Design Definition 41

7.2 VERIFY REQUIREMENTS
• Checklists
• Used for quality control.
• May include:
• Standard set of qualifying elements
• May be specifically developed to capture issues of
importance
2. • Designed to ensure that important items are included.
Elements • Ensures that important requirements are included in
designs and solution.

Requirements Analysis and Design Definition 42

7.2 VERIFY REQUIREMENTS
• Requirements Life Cycle Management Tools
• Software tools that facilitate:
• Recording
• Organizing
• Storing
• sharing
3.
Guidelines
and Tools

Requirements Analysis and Design Definition 43

7.2 VERIFY REQUIREMENTS
• Acceptance and evaluation criteria
• Represent the criteria attributes for acceptance.

• Item Tracking
• Ensure that any issues identified are managed and
resolved.
4.
• Metrics and Key Performance Indicators (KPIs)
Techniques
• How to evaluate quality of requirements.

• Reviews
• Inspect requirements documentation to identify
requirements not of acceptable quality.

Requirements Analysis and Design Definition 44

7.2 VERIFY REQUIREMENTS
• All stakeholders are key at this step for definition
• BAs may perform this step alone, or
• Engage stakeholder groups
• Engage individual stakeholders

5.
Stakeholders

Requirements Analysis and Design Definition 45

7.2 VERIFY REQUIREMENTS
• Requirements (verified)
• Verified set of requirements:
• Quality sufficient to move to next step
• Verified set of designs:
• Quality sufficient to move to next step

6.
Outputs

Requirements Analysis and Design Definition 46

7.3 Validate Requirements
7.3 VALIDATE REQUIREMENTS
• Purpose
• Ensure that requirements and designs align to business requirements.
• Ensure that requirements and designs satisfy the requirements.

• Description
• Ongoing process to ensure:
• Stakeholder alignment with business requirements
• Solution and transition designs align to business requirements
• Designs satisfy the requirements
• Need to understand what desired future state looks like for
stakeholders. after their needs have been met
• Overall goal is to achieve stakeholder’s desired future state.
• Conflicting needs should be exposed during this step.
Requirements Analysis and Design Definition 51
7.3 VALIDATE REQUIREMENTS

Requirements Analysis and Design Definition 52

7.3 VALIDATE REQUIREMENTS
• Requirements (specified and modeled)
• Any requirements can be validated.
• Any designs can be validated.
• Any requirements and designs can be validated
while in process or as completed.
• Validation cannot conclude until all requirements are
finished
1. completely verified.
Inputs

Requirements Analysis and Design Definition 53

7.3 VALIDATE REQUIREMENTS
• Identify Assumptions if the product unprecedented (mat3mlsh zayo 2bl
kda)
sabeqa
• New requirements do not have precedents.
• Need to list and validated assumptions made assume benefits and risks.
• Stakeholder responses
• Customer responses
• May be difficult to identify root cause.
2. • List cause assumptions even if not root cause
Elements • List variables that may cause assumptions
• Identify and quantify risks associated with assumptions.

Requirements Analysis and Design Definition 54

7.3 VALIDATE REQUIREMENTS
• Define Measurable Evaluation Criteria
• Define metrics for expected benefits.
• Often not defined as part of requirements gathering
• What does “good” look like
• Define the evaluation criteria to identify appropriate
metrics.
2. • Baseline metrics based on current state.
Elements • Target metrics based on desired future state.
• Base on business objectives
• Other measurement of success

Requirements Analysis and Design Definition 55

7.3 VALIDATE REQUIREMENTS
• Evaluate Alignment with Solution Scope
• Requirement may provide benefit to a stakeholder but
not provide overall alignment to desired future state.
• Need to view benefit vis-à-vis alignment to desired
state.
• Consider eliminating or modifying those that do not align

2. • Consider altering the desired future state

Elements • If design cannot be validated:

• Likely some benefit was missed
• Likely some requirement was missed or miscommunicated
• Design may need to change

Requirements Analysis and Design Definition 56

7.3 VALIDATE REQUIREMENTS
• Business Objectives
• Ensure the requirements deliver desired business benefits.

• Future State Description

• Align requirements to desired future state.
• Solution delivers desired business benefits.
3.
Guidelines • Potential Value
and Tools • To be used as a benchmark against value delivered by
requirements.

• Solution Scope
• Ensure that requirements in scope provide desired benefit.

Requirements Analysis and Design Definition 57

7.3 VALIDATE REQUIREMENTS
• Acceptance and Evaluation Criteria
• Describe quality metrics that must be met for
acceptance.

• Document Analysis
• Identify documented business needs to validate
requirements.
4.
Techniques • Financial Analysis
• Define financial benefits associated with requirements.

• Item Tracking
• Ensure that identified problems are tracked, managed
and resolved.

Requirements Analysis and Design Definition 58

7.3 VALIDATE REQUIREMENTS
• Metrics and Key Performance Indicators (KPIs)
• Select appropriate performance measures for:
• Solution
• Solution component
• Requirement

4. • Reviews
Techniques • Confirm whether stakeholder agrees or not that needs
are met.

• Risk Analysis Management

• Identify possible scenarios that would alter benefit
delivered by a requirement.

Requirements Analysis and Design Definition 59

7.3 VALIDATE REQUIREMENTS
• All stakeholders are key at this step for definition
• BAs have primary responsibility along with:
• Stakeholder groups
• Engaged individual stakeholders

5.
Stakeholders

Requirements Analysis and Design Definition 60

7.3 VALIDATE REQUIREMENTS
• Requirements (validated)
• Validated requirements:
• Can be demonstrated to deliver benefits to stakeholders
• Aligned with business goals and objectives of the change
• Requirements that cannot be validated either:
• Do not benefit the organization
6. • Do not fall within the scope
Outputs

Requirements Analysis and Design Definition 61

7.4 Define Requirements
Architecture
7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Purpose
• Requirements collectively support each other.
• Requirements fully achieve the business objectives.

• Description
• Represents the structure of all requirements of a change.
• Fits the individual models and specifications together.
• Form a WHOLE
• Used to:
• Understand which models are appropriate for domain
• Organize requirements into structures relevant to stakeholders
• Illustrates how requirements interact and relate
• Allow for trade-off decisions
Requirements Analysis and Design Definition 66
7.4 DEFINE REQUIREMENTS ARCHITECTURE

Requirements Analysis and Design Definition 67

7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Information Management Approach

• Defines how the business analysis information is:
• Stored
• Accessed

• Requirements (any state)

1. • Every requirement stated at least/only once.
Inputs • Incorporated into requirements architecture.
• Allows entirety to be viewed and evaluated

• Solution Scope
• Review to ensure alignment with boundaries of
desired solution.

Requirements Analysis and Design Definition 68

7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Requirements Viewpoints and Views

• Set of conventions define how requirements are
presented and related.
• Provide templates for different stakeholder groups
• May include standards and guidelines for
• Model types used
2. • Attributes included and used
• Model notations used
Elements
• Analytical approaches used to identify and relate
• No single viewpoint can represent all viewpoints.
• Each viewpoint may use different models, notations, etc.
• Collection of viewpoints makes an architecture.

Requirements Analysis and Design Definition 69

7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Template Architectures
• Framework is a collection of viewpoints.
• Standard across:
• An industry
• A sector
• Organization
2. • May be populated with domain specific information.
Elements • May provide a more complete picture

• Completeness
• Ensures completeness of requirements.
• Must be able to be understood by all audiences.
• Cohesive and tells a full story.

Requirements Analysis and Design Definition 70

7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Relate and Verify Requirements Relationships

• Requirements may be related to each other.
• BAs study and analyze to define relationships.
• See 5.1 Trace Requirements
• Requirements relationships must satisfy quality criteria:
• Defined – relationship does exist and is expressed
2. • Necessary – to understand requirements holistically
Elements • Correct – relationship described does exist
• Unambiguous – do not link elements in more than one or
conflicting manner
• Consistent – described in the same manner, same set of
standard descriptions per viewpoints

Requirements Analysis and Design Definition 71

7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Business Analysis Information Architecture

• Structure of business analysis information is also an
information architecture.
• See Section 3.3 Plan Business Analysis Information
Management
• Component of requirements architecture:
• Describes how all business analysis relates
2.
• Defines relationships for types of information
Elements
• Requirements
• Designs
• Types of models
• Elicitation results
• Verify relationships are complete.

Requirements Analysis and Design Definition 72

7.4 DEFINE REQUIREMENTS ARCHITECTURE
• Architecture Management Software
• Can help to manage:
• Volume, Complexity, Versions

• Legal / Regulatory Information

• Legislative rules that must be followed may impact
requirements architecture or outputs
3.
• Contractual or standard-based rules may impact as well
Guidelines
and Tools • Methodologies and Frameworks
• Predetermined set of models and relationships between
models
• Represent different viewpoints

Requirements Analysis and Design Definition 73

7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Data Modelling
• Describe requirement structure relationship to data.

• Functional Decomposition
• Used to breakdown into relevant elements.
• Organizational unit, Product, Scope, Other elements
4.
Techniques • Interviews
• Define requirements structures collaboratively.

• Organizational Modelling
• Understand various organizational relationships to
develop relevant viewpoints.

Requirements Analysis and Design Definition 74

7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Scope Modelling
• Identify elements and boundaries of requirements
architecture.

• Workshops
• Used to define boundaries collectively.
4.
Techniques

Requirements Analysis and Design Definition 75

7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Domain Subject Matter Expert,

Implementation Subject Matter Expert,
Project Manager, Sponsor, Tester
• May assist in:
• Defining requirements architecture
• Confirming requirements architecture
5.
Stakeholders • Other Stakeholders
• May assist in assessing completeness of
requirements.

Requirements Analysis and Design Definition 76

7.4 DEFINE REQUIREMENTS ARCHITECTURE

• Requirements Architecture
• Competed requirements
• Completed interrelationships
• Contextual information as required
mortbet bemo7twa mo3yn hashtags:
Complete reqs
Define relationships with
6. descriptions
Arch: Multi viewpoints based on
Outputs the target stackholders .. use
suitable models/ standards/
templates.

Requirements Analysis and Design Definition 77

7.5 Define Design Options
7.5 DEFINE DESIGN OPTIONS
(Solution Approach)
• Purpose
• Define solution approach.
• Identify opportunities to improve the business.
• Allocate requirements across solution components.
• Represent design options to meet desired future state.

• Description
• There may be more than one design option.
• Design options are tactical not strategic
• BAs must assess solution options, and:
• Their ability to meet customer requirements
• The trade-offs represented by each solution
• As the initiative progresses designs may evolve.
Requirements Analysis and Design Definition 82
7.5 DEFINE DESIGN OPTIONS

Requirements Analysis and Design Definition 83

7.5 DEFINE DESIGN OPTIONS
• Change Strategy
• Describes approach to follow to transition.
• May have impact on design decisions.

• Requirements (validated, prioritized)

• Only validated requirements are considered in
1. design options.
Inputs • Prioritized requirements aid in suggesting design
options.
• Highest priorities have more weight in design

• Requirements Architecture
• Complete set of requirements and relationships.
• Define design options that can address holistically

Requirements Analysis and Design Definition 84

7.5 DEFINE DESIGN OPTIONS
• Define Solution Approaches
• Describes whether the solution components will be:
• Purchased, Created, Hybrid
• BAs assess merits of each approach for each design.
• Solution approaches include:
• Create – assembled, constructed, developed
2. • Purchase – selected from offerings that fulfill requirements
Elements • Combination of both – includes both creation and purchase
• Consideration of integration elements is extremely
important.

Requirements Analysis and Design Definition 85

7.5 DEFINE DESIGN OPTIONS
• Identify Improvement Opportunities
• Opportunities to improve the business may occur
during analysis and design.
• Increase efficiencies
• Automate or simplify
• Reengineering or sharing processes
2. • Changing responsibilities
• Outsourcing
Elements
• Improve Access to Information
• Provide greater amounts of clear data and information
• Identify Additional Capabilities
• Capabilities that may have potential to provide future
value

Requirements Analysis and Design Definition 86

7.5 DEFINE DESIGN OPTIONS
• Requirements Allocation
• Assigns requirements to solution components and
releases to best achieve desired state.
• Trade-offs need to be considered
• Must maximize value.
• May be allocated between:
2. • Organizational units
Elements • Job functions
• Solution components or releases of solution
• Begins when solution approach is determined.
• Continues throughout the initiative.

Requirements Analysis and Design Definition 87

7.5 DEFINE DESIGN OPTIONS
• Describe Design Options
• Investigated and developed while considering desired
future state.
• Ensures that design option is valid.
• Solution performance measures are defined for each
design option.

2. • Design options consist of many design components.

• Business policies and business rules
Elements
• Business processes to be performed and managed
• People who operate and maintain the solution
• Operational business decisions
• Software applications and components used in solution
• Organizational structures, including interactions between
organization, customers, suppliers

Requirements Analysis and Design Definition 88

7.5 DEFINE DESIGN OPTIONS
• Existing Solutions
• Current in use products or services may be a component
of eventual solution.

• Future State Description

• Articulates future state of enterprise that designs will be
part of.
3.
• Helps ensure that design details are viable.
Guidelines
and Tools • Requirements (traced)
• Define design options that best fulfill requirements.

• Solution Scope
• Defines boundaries when selecting viable design options.

Requirements Analysis and Design Definition 89

7.5 DEFINE DESIGN OPTIONS
• Benchmarking and Market Analysis
• Used to identify and analyze existing solutions and
market trends.

• Brainstorming
• Used to help identify Improvement opportunities and
design options.
4.
Techniques • Document Analysis
• Used to provide information needed to describe
design options and design elements.

• Interviews
• Used to help identify Improvement opportunities and
design options.
Requirements Analysis and Design Definition 90
7.5 DEFINE DESIGN OPTIONS
• Lessons Learned
• Used to help identify opportunities for improvement.

• Mind Mapping
• Used to identify and explore possible design options.

4. • Root Cause Analysis

Techniques • Used to understand underlying cause of problems being
addressed.
• Allows proposed solutions to address problems.

• Survey or Questionnaire
• Used to help identify Improvement opportunities and
design options.

Requirements Analysis and Design Definition 91

7.5 DEFINE DESIGN OPTIONS
• Vendor Assessment
• Used to couple 3rd party offering with vendor.
• Ensure viability of vendor
• Ensure appropriateness of solutions
• Develop and maintain healthy relationships

4. • Workshops
Techniques • Used to identify improvement opportunities and
design options.

Requirements Analysis and Design Definition 92

7.5 DEFINE DESIGN OPTIONS
• Domain Subject Expert
• Provides expertise in terms of design options.
• Helps assess benefits of solution alternatives.

• Implementation Subject Matter Expert

• Provides expertise in terms of design options.
5. • Provides input about solution constraints and costs.
Stakeholders
• Operational Support
• Help evaluate difficulty and cost of integrating
proposed solution with existing systems.

Requirements Analysis and Design Definition 93

7.5 DEFINE DESIGN OPTIONS
• Project Manager
• Plans and manages solution definition process.
• Solution scope
• Risks

• Supplier
5. • Provides information on functionality associated with
Stakeholders a particular design option.

Requirements Analysis and Design Definition 94

7.5 DEFINE DESIGN OPTIONS
• Design Options
• Describe various ways to satisfy requirements in a
context.
• May include:
• Solution approach
• Potential improvement opportunities
6. • Components that define the solution options
Outputs

Requirements Analysis and Design Definition 95

 7.6 Analyze
Potential Value and
Recommend Solution
7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Purpose
• Estimate potential value of each design option.
• Establish which potential solution is most appropriate.

• Description
• Describes how to estimate and model potential value delivered by:
• A set of requirements
• Designs or design options
• Process is iterative.
• May be a planned event or triggered by a modification or change.
• Includes consideration of uncertainty in estimates.

Requirements Analysis and Design Definition 100

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Description
• Value can be described in terms of:
• Finance
• Reputation
• Impact on marketplace
• May include increase or decrease in value or a mix.
• Options are evaluated by comparing options of one design to another.
• Each option has a mix of pros / cons
• There may be no BEST option or there may be a clear winner
• Where no best option
• May need to work several concurrently to make further determinations
• All options may be rejected

Requirements Analysis and Design Definition 101

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION

Requirements Analysis and Design Definition 102

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Potential Value
• Can be used as a benchmark against which value
for a design may be evaluated.

• Design Options
• Need to be evaluated one against another to
recommend one option for solution.
1.
Inputs

Requirements Analysis and Design Definition 103

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Expected Benefits
• Describe positive value a solution is intended to deliver.
• Value can include:
• Benefits
• Reduced risk
• Compliance with business policies and regulations
2. • Improved user experience
Elements • Other positive outcomes
• Can be calculated at:
• Single requirement
• Grouping of requirements
• Benefits often realized over a long period of time.

Requirements Analysis and Design Definition 104

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Expected Costs
• Include:
• Any potential negative value
• Cost to acquire the solution
• Negative effects on stakeholders
• Cost to maintain over time

2. • Costs may include:

• Timeline
Elements
• Effort
• Purchase and / or implementation costs
• Operating costs
• Maintenance costs
• Physical resources
• Information resources
• Human resources
Requirements Analysis and Design Definition 105
7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Expected Costs
• Costs for a design option consider cumulative costs
of design components.
• Must consider opportunity costs.
• Alternative results that might have been achieved if:
• Resources dedicated to one solution were otherwise
dedicated
2.
• Funds dedicated to one design were otherwise
Elements dedicated
• Opportunity cost of any design is equal to the value of
the best opportunity NOT selected.

Requirements Analysis and Design Definition 106

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Determine Value
• Potential value to a stakeholder is based on:
• Benefits to stakeholder
• Costs to stakeholder
• Value to enterprise typically outweighs value to any
single stakeholder.
2. • Potential value is uncertain.
Elements • Estimates of costs and benefits take into account
• Degree of uncertainty at time of estimates

Requirements Analysis and Design Definition 107

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Assess Design Options and Recommend Solution
• Each design option is assessed based on potential value
to be delivered.
• May need to reevaluate if no clear benefits
• As costs and effort are understood for each design option
analysts.
• Evaluate each design option to ensure that it represents best
2. trade-offs
Elements • Factors include:
• Available resources – may be limitations
• Constraints on the solution – regulatory or business
• Dependencies between requirements – some may provide limited
value but are needed for higher value requirements to be implemented

Requirements Analysis and Design Definition 108

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Assess Design Options and Recommend
Solution
• Other considerations include:
• Relationships with proposed vendors
• Dependencies on other initiatives
• Corporate culture

2. • Sufficient cash flow

Elements • BAs recommend option or options deemed most

valuable.
• Possible that none of the options are recommended

Requirements Analysis and Design Definition 109

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Business Objectives
• Used to calculate expected benefit.

• Current State Description

• Provides context for work.
• Can be used to identify and quantify value to be derived.
3.
Guidelines • Future State Description
and Tools • Describe desired future state.
• Ensure that design options are appropriate.

Requirements Analysis and Design Definition 110

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Risk Analysis Results
• Level of risk associated with design options.

• Solution Scope
• Define scope of proposed solution.
• Ensure scope is within boundaries.
3.
Guidelines
and Tools

Requirements Analysis and Design Definition 111

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Acceptance and Evaluation Criteria
• Express requirements in form of acceptance criteria
makes them most useful when evaluating proposed
solutions.
• Helps determine if solution meets defined business needs

• Backlog Management
4. • Used to sequence potential value.
Techniques • Brainstorming
• Identify potential benefits in collaborative manner.

• Business Cases
• Used to assess recommendations against goals and
objectives.

Requirements Analysis and Design Definition 112

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Business Model Canvas
• Tool to help understand strategy and initiatives.

• Decision Analysis
• Supports assessment and ranking of design options.

4. • Estimation
Techniques • Forecasts costs and efforts in order to estimate value.

• Financial Analysis
• Evaluate financial return of different options.
• Choose the best possible ROI.

Requirements Analysis and Design Definition 113

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Focus Groups
• Get stakeholder inputs on:
• Which design option best meets needs
• Evaluate small stakeholder group value expectations

• Interviews
4. • Get stakeholder inputs on:
Techniques • Which design option best meets needs
• Evaluate small stakeholder group value expectations

• Metrics and Key Performance Indicators (KPIs)

• Create and evaluate measurements used in defining
value.

Requirements Analysis and Design Definition 114

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Risk Analysis and Management
• Identify and manage risks that could affect potential
value.

• Survey or Questionnaire
• Get stakeholder input on which designs best met
requirements and value expectations.
4.
• SWOT Analysis
Techniques
• Identify areas of strengths and weaknesses that will
impact value of solutions.

• Workshops
• Get stakeholder input on which designs best met
requirements and value expectations.

Requirements Analysis and Design Definition 115

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Customer
• Represents market segments affected.
• Involved in analyzing benefits and costs.

• Domain Subject Matter Expert

• Use expert domain knowledge to:
5. • Analyze potential benefits and value
Stakeholders
• End User
• Insight into potential value of solution.

• Implementation Subject Matter Expert

• Provide expertise in implementing design option.
• To identify potential risks and costs
Requirements Analysis and Design Definition 116
7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Project Manager
• Manage selection process to ensure:
• Awareness of potential impacts and risks

• Regulator
• Involved in risk evaluation concerning possible
5. regulatory requirements.
Stakeholders • May find constraints due to regulatory requirements.

• Sponsor
• Approves expenditure of resources and funds.
• Final approval of solution and delivery quality.

Requirements Analysis and Design Definition 117

7.6 ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION
• Solution Recommendation
• Identifies suggested, most appropriate solution.
• Solution should maximize value provided

6.
Outputs

Requirements Analysis and Design Definition 118