BABOK v3 線上讀書會 CH7 20150604 CH7 需求分析與設計定義 時間 20150611(四) pm8:00 工具 YY語音(yy.com/yy7) 頻道 商業分析(76563901)

1. Business Analysis
需求分析與設計定義
Moris, CBAP, PMP, PMI-PBA
2015.06.11
商業分析知識體系 (IIBA BABOK v3)

2. 時程規劃
TopicTopic PagePage DateDate OwnerOwner
Ch1 商業分析概論
Ch2 商業分析主要概念
23 5/7
Ch3 商業分析規劃與監控 32 5/14
Ch4 需求導出與協同合作 23 5/21
Ch5 需求生命週期管理 24 5/28
Ch6 策略分析 33 6/4
Ch7 需求分析與設計定義 30 6/11
Ch8 解決方案評價 22 6/18
Ch11 應用觀點 (Agile, BI, IT) 39/71 6/25
Ch11 應用觀點 (BizArc, BPM) 32/71 7/2
註： Skip Ch9 UC, Ch10 Techniques

3. 7. 需求分析與設計定義
 Specify and Model Requirements
 Verify Requirements
 Validate Requirements
 Define Requirements Architecture
 Define Design Options
 Analyze Potential Value and Recommend
Solution

4. 2.0 與 V3 的差異
BABOK 2.0 BABOK V3
6 Requirements Analysis 7 Requirements Analysis and Design
Definition
6.1 Prioritize Requirements 5.3 Prioritize Requirements
6.2 Organize Requirements 7.4 Define Requirements Architecture
6.3 Specify and Model
Requirements
7.1 Specify and Model Requirements
6.4 Define Assumptions and
Constraints
6.2 Define Future State
6.5 Verify Requirements 7.2 Verify Requirements
6.6 Validate Requirement 7.3 Validate Requirements
N/A 7.5 Define Design Options
N/A 7.6 Analyze Potential Value and
Recommend Solution

5. 核心概念模型
Core Concept During SA, business analysts...
Change transform elicitation results into requirements and designs in
order to define the change.
Need analyze the needs in order to recommend a solution that meets
the needs.
Solution define solution options and recommend the one that is most
likely to address the need and has the most value.
Stakeholder tailor the requirements and designs so that they are
understandable and usable by each stakeholder group.
Value analyze and quantify the potential value of the solution options.
Context model and describe the context in formats that are
understandable and usable by all stakeholders.

6. RA&DD 投入產出
Input Requirements (any state)
3.4 Information Management Approach
4.2, 4.3 Elicitation Results (any state)
6.2 Potential Value
6.4 Change Strategy
6.4 Solution Scope
Tasks 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 Solution
Output 7.1 Requirements (specified and
modelled)
7.2 Requirements (verified)
7.3 Requirements (validated)
7.4 Requirements Architecture
7.5 Design Options
7.6 Solution Recommendation

7. 7.1 說明與建模需求
 Purpose
 to analyze, synthesize, and refine elicitation results
into requirements and designs.
 Specify and Model Requirements
 the practices for analyzing elicitation results and
creating representations of those results
 All business deliverables are referred to as
'requirements'.
 the models used to represent the requirements
 this task also includes capturing information about
attributes or metadata about the requirements.

8. Input-Element-Output
4.2, 4.3 Elicitation Results (any state)
.1 Model Requirements
.2 Analyze Requirements
.3 Represent Requirements and Attributes
.4 Implement the Appropriate Levels of Abstraction
• Requirements (specified and modelled)
Inputs
Elements
Outputs

9. Outputs
 Requirements (specified and modelled)
 any combination of requirements and/or designs in
the form of text, matrices, and diagrams.

10. G&T-Stakeholders-Techniques
• Modelling Notations/Standards
• Modelling Tools
• Requirements Architecture
• Requirements Life Cycle Management Tools
• Solution Scope
• Acceptance and Evaluation Criteria
• Business Capability Analysis
• Business Model Canvas
• Business Rules Analysis
• Concept Modelling
• Data Dictionary
• Data Flow Diagrams
• Data Modelling
• Decision Modelling
• Functional Decomposition
• Glossary
• Interface Analysis
• Non-functional Requirements Analysis
• Organizational Modelling
• Process Modelling
• Prototyping
• Roles and Permissions Matrix
• Root Cause Analysis
• Scope Modelling
• Sequence Diagrams
• Stakeholder List, Map, or Personas
• State Modelling
• Use Cases and Scenarios
• User Stories
• Any Stakeholder
Guideline & Tools
Stakeholders
Techniques

11. 7.2 檢驗需求
 Purpose
 to ensure that requirements and designs
specifications and models meet quality standards and
are usable for the purpose they serve.
 Verify Requirements
 Verifying requirements ensures that the requirements
and designs have been defined correctly.
 A high-quality specification is well written and easily
understood by its intended Audience
 The most important characteristic of quality
requirements and designs is fitness for use.

12. Input-Element-Output
7.1 Requirements (specified and modelled)
.1 Characteristics of Requirements and Design Quality
.2 Verification Activities
.3 Checklists
• Requirements (verified)
Inputs
Elements
Outputs

13. Output
 Requirements (verified)
 a set of requirements or designs that is of sufficient
quality to be used as a basis for further work.

14. G&T-Stakeholders-Techniques
• Requirements Life Cycle Management Tools
• Acceptance and Evaluation Criteria
• Item Tracking
• Metrics and KPIs
• Reviews
• All Stakeholders
Guideline & Tools
Stakeholders
Techniques

15. 7.3 驗證需求
 Purpose
 to ensure that all requirements and designs align to the business
requirements and support the delivery of needed value.
 Requirements validation
 Requirements validation is an ongoing process to ensure that
stakeholder, solution, and transition requirements align to the
business requirements and that the designs satisfy the
requirements.
 Understanding what the desired future state looks like for
stakeholders after their needs have been met is valuable to
business analysts when validating requirements.

16. Input-Element-Output
7.1 Requirements (specified and modelled)
.1 Identify Assumptions
.2 Define Measurable Evaluation Criteria
.3 Evaluate Alignment with Solution Scope
• Requirements (validated)
Inputs
Elements
Outputs

17. Output
 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.
 If a requirement or design cannot be validated, it
either does not benefit the organization, does not fall
within the solution scope, or both.

18. G&T-Stakeholders-Techniques
• Business Objectives
• Future State Description
• Potential Value
• Solution Scope
• Acceptance and Evaluation Criteria
• Document Analysis
• Item Tracking
• Metrics and KPIs
• Reviews
• Risk Analysis and Management
• All Stakeholders
Guideline & Tools
Stakeholders
Techniques

19. 7.4 定義需求架構
 Purpose
 to ensure that the requirements collectively support
one another to fully achieve the objectives.
 Requirements architecture
 the structure of all of the requirements of a change
 Use requirements architecture to
 understand which models are appropriate
 organize requirements into structures
 illustrate how requirements and models interact with
and relate to each other
 ensure the requirements work together
 make trade-off decisions about requirements

20. Input-Element-Output
3.4 Information Management Approach
• Requirements (any state)
6.4 Solution Scope
.1 Requirements Viewpoints
.2 Template Architectures
.3 Completeness
.4 Relate and Verify Requirements Relationships
.5 Business Analysis Information Architecture
• Requirements Architecture
Inputs
Elements
Outputs

21. Output
 Requirements Architecture
 the requirements and the interrelationships among
them, as well as any contextual information that is
recorded.

22. G&T-Stakeholders-Techniques
• Architecture Management Software
• Legal/Regulatory Information
• Methodologies and Frameworks
• Data Modelling
• Functional Decomposition
• Interviews
• Organization Modelling
• Scope Modelling
• Workshops
• Domain SME, Implementation SME,
Project Manager, Sponsor, Tester
• Any Stakeholder
Guideline & Tools
Stakeholders
Techniques

23. 7.5 定義設計選項
 Purpose
 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.
 Designing solution
 there may be one or more design options identified.
 Each design option represents a way to satisfy a set
of requirements
 As a solution is developed, tactical trade-offs may
need to be made among design alternatives

24. Input-Element-Output
6.4 Change Strategy
5.3, 7.3 Requirements (validated, prioritized)
7.4 Requirements Architecture
.1 Define Solution Approaches
.2 Identify Improvement Opportunities
.3 Requirements Allocation
.4 Describe Design Options
• Design Options
Inputs
Elements
Outputs

25. Output
 Design Options
 describe various ways to satisfy one or more needs in
a context. They may include solution approach,
potential improvement opportunities provided by the
option, and the components that define the option.

26. G&T-Stakeholders-Techniques
• Existing Solutions
• Future State Description
• Requirements (traced)
• Solution Scope
• Benchmarking and Market Analysis
• Brainstorming
• Document Analysis
• Interviews
• Lessons Learned
• Root Cause Analysis
• Survey or Questionnaire
• Vendor Assessment
• Workshops
• Domain SME
• Implementation SME
• Operational Support
• Project Manager
• Supplier
Guideline & Tools
Stakeholders
Techniques

27. 7.6 分析潛在價值並建議方案
 Purpose
 to estimate the potential value for each design option
and to establish which one is most appropriate to
meet the enterprise’s requirements.
 Analyze Potential Value
 to estimate and model the potential value delivered by
a set of requirements, designs, or design options
 Recommend Solution
 Each option has a mix of advantages and
disadvantages to consider.
 there may be no best option to recommend, or there
may be a clear best choice.

28. Input-Element-Output
6.2 Potential Value
7.5 Design Options
.1 Expected Benefits
.2 Expected Costs
.3 Determine Value
.4 Assess Design Options and Recommend Solution
• Solution Recommendation
Inputs
Elements
Outputs

29. Output
 Solution Recommendation
 identifies the suggested, most appropriate solution
based on an evaluation of all defined design options.
 The recommended solution should maximize the
value provided to the enterprise.

30. G&T-Stakeholders-Techniques
• Business Objectives
• Current State Description
• Future State Description
• Risk Analysis Results
• Solution Scope
• Acceptance and Evaluation Criteria
• Backlog Management
• Brainstorming
• Business Cases
• Business Model Canvas
• Decision Analysis
• Estimation
• Financial Analysis
• Focus Groups
• Interviews
• Metrics and KPIs
• Risk Analysis and Management
• Survey or Questionnaire
• SWOT Analysis
• Workshops
• Customer
• Domain SME
• End User
• Implementation SME
• Project Manager
• Regulator
• Sponsor
Guideline & Tools
Stakeholders
Techniques

31. 感謝您的參與