You are on page 1of 76

PHÂN TÍCH KINH DOANH (BA)

Chương 7
PHÂN TÍCH YÊU CẦU &
ĐỊNH NGHĨA THIẾT KẾ
(Requirements Analysis & Design Definition)

02/04/2024

Nguyễn Duy Thanh


(thanhnd@buh.edu.vn)
AGENDA

 Introduction
 Core Concept Model in RADD
 Specify and Model Requirements
 Verify Requirements
 Validate Requirements
 Define Requirements Architecture
 Define Design Options
 Analyze Potential Value and Recommend Solution
HUB - MIS (2024) 2
Knowledge Area Relationships

HUB - MIS (2024) 3


Overview of RADD [6]

1. Specify and Model Requirements


2. Verify Requirements
3. Validate Requirements
4. Define Requirements Architecture
5. Define Design Options
6. Analyze Potential Value and Recommend Solution

HUB - MIS (2024) 4


Business Analysis Value Spectrum

HUB - MIS (2024) 5


Core Concept Model in RADD

HUB - MIS (2024)


HUB - MIS (2024)
7.1 - SPECIFY AND MODEL
REQUIREMENTS

HUB - MIS (2024)


SPECIFY AND MODEL REQUIREMENTS

• Specify and Model Requirements is used to analyze, integrate,


and process elicitation results into requirements and designs; It
is focused on understanding the needs of the organization and
the output of that activity are the requirements

• Purpose: Analyze, synthesize, and refine elicitation results into


requirements and designs

• Description: Specify and Model Requirements describes the


practices for analyzing elicitation results and creating
representations of those results.

HUB - MIS (2024) 9


HUB - MIS (2024)
INPUT

• Elicitation Results (any state): Modelling can begin with any


elicitation result and may lead to the need for more elicitation
to clarify or expand upon requirements.

HUB - MIS (2024) 11


ELEMENTS [4]

• Model Requirements
• Analyze Requirements
• Represent Requirements & Attributes
• Implement the Appropriate Levels of Abstraction

HUB - MIS (2024) 12


GUIDELINES & TOOLS [5]

• Modelling Notations / Standards


• Modelling Tools
• Requirements Architecture
• Requirements Lifecycle Management Tools
• Solution Scope

HUB - MIS (2024) 13


TECHNIQUES [24]
1. Acceptance & Evaluation Criteria 13. Non-Functional Requirements Analysis
2. Business Capability Analysis 14. Organizational Modelling
3. Business Model Canvas 15. Process Modelling
4. Business Rules Analysis 16. Prototyping
5. Concept Modelling 17. Roles & Permission Matrix
6. Data Dictionary 18. Root Cause Analysis
7. Data Flow Diagrams 19. Scope Modelling
8. Data Modelling 20. Sequence Diagrams
9. Decision Modelling 21. Stakeholder List, Map / Personas
10.Functional Decomposition 22. State Modelling
11.Glossary 23. Use Cases & Scenarios
12.Interface Analysis 24. User Stories

HUB - MIS (2024) 14


(6) Data Dictionary (p. 247)

HUB - MIS (2024) 15


Elements

• Data Elements

• Primitive Data Elements

• Composite Elements.

HUB - MIS (2024) 16


(7) Data Flow Diagrams (DFD) (p. 250)

HUB - MIS (2024) 17


Elements

• Externals (Entity, Source, Sink)

• Data Store

• Process

• Data Flow.

HUB - MIS (2024) 18


Data Flow Diagram Gane-Sarson Notation

HUB - MIS (2024) 19


(20) Sequence Diagrams (p. 341)

HUB - MIS (2024) 20


Elements

• Lifeline

• Activation Box

• Message.

HUB - MIS (2024) 21


(22) State Modelling (p. 348)

HUB - MIS (2024) 22


Elements

• State
• State Transition
• State Diagram.

HUB - MIS (2024) 23


State Transition Diagram

HUB - MIS (2024) 24


STAKEHOLDERS

• Any Stakeholders

HUB - MIS (2024) 25


OUTPUTS

• Requirements (specified and modelled): Any combination of


requirements and/or designs in the form of text, matrices, and
diagrams.

HUB - MIS (2024) 26


7.2 - VERIFY REQUIREMENTS

HUB - MIS (2024)


VERIFY REQUIREMENTS

• Requirements Verification is the process of confirming that the


system requirements contain all the necessary elements of
well-written requirements

• Purpose: Ensure that requirements and designs specification


and models meet quality standards and are usable for the
purpose they serve

• Description: Ensure that the requirements and designs have


been defined correctly; It constitutes a check by the business
analyst and key stakeholders to determine that the
requirements and designs are ready for validation.

HUB - MIS (2024) 28


HUB - MIS (2024)
INPUT

• Requirements (specified and modelled): Any requirement,


design, or set of those may be verified to ensure that text is well
structured and that matrices and modelling notation are used
correctly.

HUB - MIS (2024) 30


ELEMENTS [3]

• Characteristics of Requirements and Design Quality


• Verification Activities
• Checklists

HUB - MIS (2024) 31


GUIDELINES & TOOLS

• Requirements Life Cycle Management Tools

HUB - MIS (2024) 32


TECHNIQUES [4]

1.Acceptance & Evaluation Criteria


2.Item Tracking
3.Metrics & Key Performance Indicators (KPIs)
4.Reviews

HUB - MIS (2024) 33


STAKEHOLDERS

• Any Stakeholders

HUB - MIS (2024) 34


OUTPUTS

• Requirements (verified): A set of requirements or designs that


is of sufficient quality to be used as a basis for further work.

HUB - MIS (2024) 35


7.3 - VALIDATE REQUIREMENTS

HUB - MIS (2024)


VALIDATE REQUIREMENTS

• Validation Requirements is the process of confirming the


completeness and correctness of requirements

• Purpose: Ensure that all requirements and designs align to the


business requirements and support the delivery of needed
value

• Description: Validation Requirements is an ongoing process to


ensure that stakeholder, solution and transition requirements
align to the business requirements and that the designs satisfy
the requirements.

HUB - MIS (2024) 37


HUB - MIS (2024)
INPUT

• Requirements (specified and modelled): Any types of


requirements and designs can be validated; Validation activities
may begin before requirements are completely verified.

HUB - MIS (2024) 39


ELEMENTS [3]

• Identify Assumptions
• Define Measurable Evaluation Criteria
• Evaluate Alignment with Solution Scope

HUB - MIS (2024) 40


GUIDELINES & TOOLS [4]

• Business Objectives
• Future State Description
• Potential Value
• Solution scope

HUB - MIS (2024) 41


TECHNIQUES [7]

1.Acceptance & Evaluation Criteria


2.Document Analysis
3.Financial Analysis
4.Item Tracking
5.Metrics & Key Performance Indicators (KPIs)
6.Reviews
7.Risk Analysis & Management

HUB - MIS (2024) 42


STAKEHOLDERS […]

• All Stakeholders

HUB - MIS (2024) 43


OUTPUTS

• Requirements (validated): Validated requirements and designs


are those that can be demonstrated to deliver benefit to
stakeholders and align with the business goals and objectives of
the change.

HUB - MIS (2024) 44


7.4 - DEFINE REQUIREMENTS
ARCHITECTURE

HUB - MIS (2024)


DEFINE REQUIREMENTS ARCHITECTURE

• Define Requirements Architecture is requirements collectively


support one another to fully achieve the objectives

• Purpose: Enrures the structure of all requirements of a change

• Description: Business analysts use requirements architecture to:


– Understand which models are appropriate for domain,
solution scope, and audience
– Organize requirements into structures relevant to different
stakeholders
– Ensure the requirements work together to achieve the
overall objectives.

HUB - MIS (2024) 46


HUB - MIS (2024)
INPUT [3]

• Information Management Approach

• Requirements (any state)

• Solution Scope

HUB - MIS (2024) 48


ELEMENTS [5]

• Requirements Viewpoints and Views


• Template Architecture
• Completeness
• Relate and Verify Requirements Relationships
• Business Analysis Information Architecture

HUB - MIS (2024) 49


GUIDELINES & TOOLS [3]

• Architecture Management Software


• Legal Regulatory Information
• Methodologies and Frameworks

HUB - MIS (2024) 50


TECHNIQUES [6]

1.Data Modelling
2.Functional Decomposition
3.Interviews
4.Organizational Modelling
5.Scope Modelling
6.Workshops

HUB - MIS (2024) 51


(1) Data Modeling (p. 256)

HUB - MIS (2024) 52


Elements

• Entity or Class

• Attribute

• Relationship or Association

• Diagrams (...)

• Metadata.

HUB - MIS (2024) 53


STAKEHOLDERS [6]

• Domain SME
• Implementation SME
• Project Manager
• Sponsor
• Tester
• Any stakeholder

HUB - MIS (2024) 54


OUTPUTS

• Requirements Architecture: The requirements and the


interrelationships among them, as well as any contextual
information that is recorded.

HUB - MIS (2024) 55


7.5 - DEFINE DESIGN OPTIONS

HUB - MIS (2024)


DEFINE DESIGN OPTIONS

• Define Design Options determines the solution approach,


recognize opportunities to enhance the business, assign
requirements across solution elements

• Purpose: It represents design option that achieve the desired


future state

• Description: When designing a solution, there may be one or


more design options identified; Each design option
represents a way to satisfy a set of requirements.

HUB - MIS (2024) 57


HUB - MIS (2024)
INPUT [3]

• Change Strategy

• Requirements (validated, prioritized)

• Requirements Architecture

HUB - MIS (2024) 59


ELEMENTS [4]

• Define Solution Approaches


• Identify Improvement Opportunities
• Requirements Allocation
• Describe Design Options

HUB - MIS (2024) 60


GUIDELINES & TOOLS [4]

• Existing Solutions
• Future State Description
• Requirements (traced)
• Solution Scope

HUB - MIS (2024) 61


TECHNIQUES [10]

1.Benchmarking & Market Analysis


2.Brainstorming
3.Document Analysis
4.Interviews 6. Mind Mapping
5.Lessons Learned 7. Root Cause Analysis
8. Survey or Questionnaire
9. Vendor Assessment
10.Workshops
HUB - MIS (2024) 62
STAKEHOLDERS [5]

• Domain SME
• Implementation SME
• Operational Support
• Project Manager
• Supplier

HUB - MIS (2024) 63


OUTPUTS

• Design Options: Describe various ways to satisfy one or more


needs in a context.

HUB - MIS (2024) 64


7.6 - ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION

HUB - MIS (2024)


ANALYZE POTENTIAL VALUE AND
RECOMMEND SOLUTION

• Analyze Potential Value and Recommend Solution is to


estimate the potential value for each design option

• Purpose: Establish which one is most appropriate to meet the


enterprise’s requirements

• Description: Describes how to estimate the potential value


delivered by a set of requirements, designs or design option;
Design options are evaluated by comparing the potential
value of each option to the other options.

HUB - MIS (2024) 66


HUB - MIS (2024)
INPUT [2]

• Potential Value

• Design Options

HUB - MIS (2024) 68


ELEMENTS [4]

• Expected Benefits
• Expected Costs
• Determine Value
• Assess Design Options and Recommend Solution

HUB - MIS (2024) 69


GUIDELINES & TOOLS [5]

• Business Objectives
• Current State Description:
• Future State Description
• Risk Analysis Results
• Solution Scope

HUB - MIS (2024) 70


TECHNIQUES [15]

1. Acceptance & Evaluation Criteria


2. Backlog Management
3. Brainstorming
4. Business Case 9. Focus Groups
5. Business Model Canvas 10. Interviews
6. Decision Analysis 11. Metrics & Key Performance Indicators (KPI)
7. Estimation 12. Risk Analysis & Management
8. Financial Analysis 13. Survey or Questionnaire
14. SWOT Analysis
15. Workshops
HUB - MIS (2024) 71
STAKEHOLDERS [7]

• Customer
• Domain SME
• End User
• Implementation SME
• Project Manager
• Regulator
• Sponsor

HUB - MIS (2024) 72


OUTPUTS

• Solution Recommendation: Identifies the suggested, most


appropriate solution based on an evaluation of all defined
design options.

HUB - MIS (2024) 73


Chương cuối…

ĐÁNH GIÁ GIẢI PHÁP

You might also like