Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 2: Business Analysis Key Concepts (2.4 Stakeholders 16 (Customer,…
Chapter 2: Business Analysis Key Concepts
2.1 The Business Analysis Core Concept Model™ 12
It encompasses what business analysis is and
what it means to those performing business analysis tasks
6 core concepts:Change, Need, Solution, Stakeholder, Value, and Context
used to:
• describe the profession and domain of business analysis,
• communicate about business analysis with a common terminology,
• evaluate the relationships of key concepts in business analysis,
• perform better business analysis by holistically evaluating the relationships
among these six concepts, and
• evaluate the impact of these concepts and relationships at any point during
a work effort in order to establish both a foundation and a path forward.
2.2 Key Terms 14
2.3 Requirements Classification Schema 16
Business requirements
Stakeholder requirements
Solution requirements
functional requirements
non-functional requirements or quality of service requirements
Transition requirements:
2.5 Requirements and Designs 19
BA Key activities
key activities of BA
Eliciting,
analyzing,
validating, and
managing requirements
responsible for the definition of design
Requirements are focused on the need
designs are focused on the solution
to transform that request into a requirement
Elicitation and Collaboration (p. 53)
Strategy
Analysis (Chapter 6 - p. 109)
Requirements Analysis and Design Definition (p. 133),
Solution Evaluation (p. 163)
A requirement (or set of
requirements) may be used to define a design. That design may then be used to
elicit additional requirements that are used to define more detailed designs. The
business analyst may hand off requirements and designs to other stakeholders
who may further elaborate on the designs.
question ‘why?’.
2.4 Stakeholders 16
Customer
supplier
sponsor
regulator,
project manager
operational supportt*
implementation subject matter
expert
end user
domain subject matter expert,
business analyst,
Any stakeholder can be a source of requirements, assumptions, or
constraints.