Chapter 2 Business Analytics Key Concepts Flashcards
The Business Analysis Core Concept Model
Change, Need, Solution, Stakeholder, Value, Context
Change (BACCM)
act of transformation in response to a need. Works to improve performance of an enterprise deliberately and controlled.
· What are the kinds of changes we are doing?
Need (BACCM)
problem or opportunity to be addressed. Can cause changes by motivating stakeholders to act.
· What are the needs we are trying to satisfy?
Solution (BACCM)
specific way of satisfying one or more needs in a context by resolving a problem faced by stakeholders/enabling stakeholders to take advantage of opportunity.
· What are the solutions we are creating/changing?
Stakeholder (BACCM)
group or individual with relationship to the change/need/solution.
a. Grouped based on relationship to needs, changes, solutions
· Who are the stakeholders involved?
Value (BACCM)
worth, importance, or usefulness of something to a stakeholder within a context. Can bee seen as potential or realized returns, gains, and improvements. Possible to have a decrease in value in form of losses, risks, and costs.
a. Tangible value- directly measurable often has significant monetary component
b. Intangible value- measured indirectly often has motivational component, such as a company’s reputation or employee morale.
c. Value can be assessed in absolute terms, but in many cases is assessed in relative terms.
· What do stakeholders consider to be of value?
Context (BACCM)
circumstances that influence, are influenced by, and provide understanding of the change. Context is everything relevant to the change that is within the environment.
a. Includes attitudes, behaviors, beliefs, competitors, culture, demographics etc.
· What are the contexts that we and the solution are in?
Business Analysis Information
broad and diverse sets of information business analysts analyze, transform, and report.
Information of any kind, any level of detail that is used as input or is an output of business analysis work.
Design
usable representation of a solution.
· Focuses on understanding how value might be realized by a solution if built.
• Can vary widely depending on the circumstances.
Enterprise
system of one or more organizations and solutions they use to pursue a shared set of common goals.
• Solutions are also organizational capabilities
· Can be processes, tools or information
• Boundaries can be defined relative to the change.
NOT constrained by boundaries of a legal entity, organization, or org. unit.
Organization
autonomous group of people under management of single individual/board working towards common goals/objectives
• Often have clearly defined boundary.
• Operate on continuous basis.
Plan
proposal for doing or achieving something.
• Describe set of events, dependencies among the events, expected sequence, schedule, results or outcomes etc.
Requirement
usable representation of a need.
• Focus on understanding what kind of value could be delivered if a requirement is fulfilled.
Risk- effect of uncertainty on the value of a change, solution, the enterprise.
• Ba collab. w/stakeholders to identify, assess, and prioritize risks/deal with risks by altering conditions/events leading to uncertainty.
Requirements Classification Schema
Business Requirements
Stakeholder Requirements
Solution Requirements
Transition Requirements
Business Requirements
statements of goals, objectives, and outcomes that describe why a change has been initiated.
Stakeholder Requirements
describe needs of stakeholders that must be met in order to achieve the business requirements.
Solution Requirements
describe capabilities/qualities of a solution that meets the stakeholder requirements. Can be divides into 2 sub categories:
· Functional Requirements- capabilities a solution must have in terms of the behavior and information that the solution will manage.
Non-Functional requirements (quality of service requirements)- describe conditions under which a solution must remain effective or qualities that a solution must have.
Transition Requirements
capabilities that solution must have and conditions solution must meet to facilitate transition from current state to the future state.
· Not needed once change is complete.
Stakeholders
ndividual/group ba interacts with directly/indirectly.
• Any stakeholder can be a source of requirements, assumptions or constraints.
Business Analyst
stakeholder in all business analysis activities. Responsible/accountable for execution of these activities.
• Sometimes responsible for performing activities that fall under another stakeholder role.
Customer
may use products/services produced by enterprise and have contractual/moral rights enterprise is obligated to meet.
Domain Subject Matter Expert
individual with in-depth knowledge of topic relevant to business need/solution scope.
• Filled by people who may be end users or people who have in depth knowledge of the solution.
End User
stakeholders who directly interact with solution
Implementation Subject Matter Expert
stakeholder who has specialized knowledge regarding implementation of one or more solution components.
Operational Support
responsible for day-to-day management/maintenance of system/product.
Project Manager
responsible for managing work required to deliver solution that meets business need.
• Ensuring projects objectives are met
Regulator
responsible for definition/enforcement of standards.
Sponsor
initiating the effort to define a business need and develop a solution that meets that need.
Supplier
stakeholder outside boundary of given organization/org. unit.
Tester
responsible for determining how to verify solution meets the requirements defined by ba + conducting the verification process.
