Scribd
Upload
446 views

RADD - Requirement Analysis and Design Definition

This document describes the tasks involved in requirements analysis and design definition. It involves specifying, verifying, validating requirements and defining the requirements architecture. Design options are defined by allocating requirements to solution components. Potential value is analyzed for each design option and the most viable solution is recommended. The tasks follow an iterative process from initial needs exploration to recommending solutions that meet those needs.

Uploaded by

Sourabh Bhattacharya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
446 views

RADD - Requirement Analysis and Design Definition

This document describes the tasks involved in requirements analysis and design definition. It involves specifying, verifying, validating requirements and defining the requirements architecture. Design options are defined by allocating requirements to solution components. Potential value is analyzed for each design option and the most viable solution is recommended. The tasks follow an iterative process from initial needs exploration to recommending solutions that meet those needs.

Uploaded by

Sourabh Bhattacharya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Requirements Analysis and Design Defini on

Tasks
1. Specify and Model Requirements
2. Verify Requirements
3. Validate Requirements
4. Define Requirements Architecture
5. Define Design op ons
6. Analyze poten al value and Recommend solu ons

Requirement Analysis and Design Defini on describes the tasks that the BA performs
1. Structure and organize the requirements discovered during elicita on ac vi es
2. Specify and Model requirements and designs
3. Validate and Verify the informa on
4. Iden fy solu on op ons that meets the business needs
5. Es mate the poten al value that could be realized for each solu on op ons.

Covers incremental and itera ve ac vi es ranging from the ini al concept and
explora on of the need through the transforma on of those needs into par cular
recommend solu on
This is the core knowledge area of the Business Analysis

BACCM in RADD
1. Need – Analyze the needs to recommend a solu on that meets the needs.
2. Change – Transform elicita on results into requirements and design to define
change.
3. Solu on – Define solu on op ons and recommend the most viable solu on.
4. Context – Model and describe the context in formats that are understandable
and usable by stakeholder groups.
5. Value – Analyze and quan fy the poten al value of the solu on op ons.
6. Stakeholder – Tailor the requirements and designs so that they are
understandable and usable by stakeholder groups.
Task 1 – Specify and Model Requirements

Purpose – the purpose of this Task is to analyze, synthesize and refine elicita on
results into a set of requirements and design.
Inputs – Elicita on Results (any state)
Focus of this Task – Understanding the Need
Output – Requirements (Specified and Modelled)
Elements
1. Modelling Format
a. Matrix
b. Designs
Model Categories
 People and Roles
 Ra onale
 Ac vity Flow
 Capability
 Data and Informa on

2. Analyze Requirements – Breaking down or decomposing the requirements


3. Requirements and A ributes
4. Level of Abstrac on – Presen ng requirements differently as per the audience.
Guidelines and Tools
1. Modelling nota ons and standards
2. Modelling Tools
3. Requirements Architecture
4. Requirement Lice Cycle Management
5. Solu on Scope

Task 2 - Verify Requirements


Purpose – The purpose of this task is to ensure that the requirements and the design
specifica ons and models meet the Quality Standards and are usable for the purpose.
Input – Requirements (Specified and Modelled)
Focus of this Task – Verifying the Requirements
Output – Requirements (Verified)
Elements:
1. Characteris cs of Requirements and Design Quality
a. Atomic
b. Complete
c. Consistent
d. Concise
e. Feasible
f. Unambiguous
g. Testable
h. Priori zed
i. Understandable
2. Verifica on ac vi es
a. Performed Itera vely throughout the requirements
b. Requirements are verified for the following
i. Compliance with organiza onal standards
ii. Correct usage of modelling nota ons and templates
iii. Consistency between the models
iv. Understandable terminology for stakeholders
3. Checklists
a. Used for Quality control when verifying
b. Include a set of quality elements that business analyst uses to verify
requirements.
Guidelines and Tools:
 Requirement Life Cycle Management Tools.

Task 3 - Validate Requirements


Purpose – Requirement Valida on is an ongoing process to ensure that the
stakeholders, solu on and transi on requirements align to the business
requirements. It also validate the designs to ensure they sa sfy the stated
requirements.
Input – Requirements (Specified and Modelled)
Focus of this Task – Requirements Valida on
Output – Requirements (Validated)
Elements –
 Iden fy Assump ons
 Define Measurable Evalua on criteria
 Evaluate Alignment with Solu on scope
Guidelines and Tools –
 Business Objec ves
 Future State Descrip on
 Poten al value
 Solu on Scope

Task 4 - Define Requirements Architecture


Purpose – The purpose of the Define Requirement Architecture task is to ensure that
the requirements collec vely support one another to fully achieve the objec ves.
Input –
 Informa on Management Approach
 Requirements (Any state)
 Solu on Scope
Task – Define Requirements Architecture
Output – Requirements Architecture
Elements –
 Requirement Viewpoints and views
o User views
o Business Views
o Technical View
o Sales Viewpoint
o Customer Support Viewpoint
o Management Viewpoint
 Template Architecture – Architectural framework used a template to start
defining the architecture.
 Completeness – An architecture helps ensuring that a set of requirements is
complete.
 Relate and Verify Requirements Rela onship
o Defined
o Necessary
o Correct
o Unambiguous
o Consistent
 Business Analysis Informa on Architecture – Structure of the business analysis
informa on is known as informa on architecture
Guidelines and Tools –
 Architecture Management So ware
 Legal/Regulatory Informa on
 Methodologies and Frameworks

Task 5 - Define Design op ons


Purpose – The purpose of this task is to define the solu on approach, iden fy
opportuni es to improve the business, allocate requirements across solu on
components, and represent design op ons.
Input –
 Change Strategy
 Requirements (validated, priori zed)
 Requirements Architecture
Task – Define Design op ons
Output – Design op ons
Elements –
1. Define solu on approaches
a. Create
b. Purchase
c. Combina on of both
2. Iden fy improvement opportuni es
a. Increase efficiencies
b. Improve access to informa on
c. Iden fy addi onal capabili es
3. Requirements alloca on – The process of assigning the requirements to
solu on components and releases
4. Describe design op ons
a. Design op ons are developed considering the desired future state.
b. Solu on performance measures are defined for each solu on op on.
Guidelines and Tools –
 Exis ng Solu ons
 Future State Descrip on
 Requirements (Traced)
 Solu on Scope

Task 6- Analyze poten al value and Recommend solu ons


Purpose – The purpose of this task is to es mate the poten al value for each design
op on and establish which one is the most appropriate to meet the enterprise
requirements.
Input –
 Poten al value
 Design op ons
Task – Analyze poten al value and recommend solu on
Output – Solu on recommenda on
Elements –
1. Expected Benefits – Describe the posi ve value that a solu on is intended to
deliver to the stakeholder.
2. Expected Costs – Include any poten al nega ve value associated value with a
solu on
3. Determine Value – The Poten al value of a solu on is based on the expected
benefits and costs. The BA considers the poten al value from the point of view
of the stakeholders.
4. Assess Design Op ons and Recommend Solu ons.
a. Available Resources
b. Constraints on the solu on
c. Dependencies between requirements
d. Proposed vendors
e. Dependencies on other ini a ves
f. Corporate culture
g. Cash flow for investment
Guidelines and Tools -
1. Business Objec ves
2. Current State Descrip on
3. Future State Descrip on
4. Risk Analysis Results
5. Solu on Scope

You might also like