Chapter 2 - Business Analysis Key Concept

Chapter 2: Business Analysis Key 
Concept
Submitted By: Aishveen Kaur Gill

Ques: What is Business Analysis?

Ans: Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. Business analysis is the discipline of recognizing business needs and findings solutions to various business problems. In simpler words, it is a set of tasks and techniques which work as a connection between stakeholders. These help them to understand organization's structure, policies, and operations, they can also recommend solutions to help the business reach its goals. 

Business analysis is about understanding how your organization functions to fulfill its purposes. It entails defining the abilities the firm needs to provide products to the external stakeholders.

Ques: What is BACCM?

Ans: Business Analysis Core Concept Model(BACCM) is a conceptual framework of six core concepts critical to the business analysis profession. Understanding how each core concept relates to the other five core concepts will help you to see the system as a whole, know what question to ask and understand stakeholder motivation.

The six core concepts are:

Change: Transforming from one state to another.  Your goal is to prevent harmful change and promote potentially beneficial change.

Need: Something of potential value to an organization. A need might not be actionable until it becomes a requirement. A requirement is a usual representation of a need.

Solution: A solution might exist but not be identified or implemented. A design is a usable representation of a solution.

Stakeholder: Someone who has a relationship with the change or any of the other core concepts. They can be involved at many different levels. A good practice is to think about stakeholders in relation to value. The triangle of Value, Change and stakeholder allow you to integrate loss and prospect theory to better understand stakeholder motivation.

Value: Value is a much deeper concept than most people think. It goes beyond money. Isolate and explore what you mean by "value" and what the money will be used for.

Context: The background and environment in which you’re functioning.  The context influences the other concept items.

Ques: What is Business Analysis requirements classification schema?

Ans:  

1) Business Requirements- High- level statements of the goals, objectives, or needs of an organization. They usually describes opportunities that an organization wants to realise or problems that they want to solve. Often stated in a business case. 

2) Stakeholder requirements- Mid-level statements of the needs of a particular stakeholder or group of stakeholders. They usually describe how someone wants to interact with the intended solution. Often acting as a mid-point between the high-level business requirements and more detailed solution requirements.

3) Solution requirements- A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed documents.

Functional requirements- Usually detailed statements of capabilities, behavior, and

information that the solution will need. Examples include formatting text, calculating a number, modulating a signal.

             Non-functional requirements - Usually detailed statements of the conditions under which the solution must remain effective, qualities that the solution must have or it must operate. Example: reliability, test-ability, maintainability, availability.  

4)  Transition requirements- Usually, detailed statements of capabilities or behavior required only to enable the  transition from the current state of the enterprise to the desired future state, but that will thereafter no longer be required. Examples include recruitment, role changes, education, migration of data from one system to another.

Ques: What is Stakeholder analysis? And list of Stakeholders involved in Business Analysis.

Ans: Stakeholder Analysis is the process of identifying project stakeholders, how their needs may impact the project, and the contributions that the stakeholders will make to the requirements elicitation process.  Projects typically have a large number of stakeholders from many different areas of the organization.  Based on each stakeholder’s position and responsibilities, the level of their involvement and their importance to the project will vary.

List of Stakeholders:
1. Government
2. Employees
3. Customers
4. Suppliers
5. Creditors
6. Community
7. Trade Unions
8. Owners
9. Investors

Stakeholders	Stakeholder’s Concerns
Government	Taxation, VAT, employment, truthful reporting, legalities
Employees	Rates of pay, job security, respect, truthful communication, appreciation, recognition
Customers	Value, quality, customer care, ethical products.
Suppliers	Providers of product and services used in the end product for the customer
Creditors	Credit score, new contracts, liquidity.
Community	Jobs, involvement, environmental protection, shares, truthful communication.
Trade unions	Quality, worker protection, jobs.
Owners	Profitability, longevity, market share, market standing, succession planning, capital raising, growth
Investors	Return on investment, income

Ques: How do Business Analyst analyze Business Requirements?

Ans:   The Business Analysis Requirements Analysis & Design Definition knowledge describes the tasks that business analysts perform to structure and organize requirements discovered during elicitation activities, specify and model requirements and designs, validate and verify information, identify solution options that meet business needs, and estimate the potential value that could be realized for each solution options.
These two areas are often mixed because the focus shift is constant: Usually, a requirement (the need) leads to a design (the solution) which in turn may drive the discovery and analysis of more requirements.

Requirements	Designs
View six months sales data across multiple organizational units in a single view.	A sketch of dashboard.
Reduce amount of time required to pick and pack a customer’s order.	Process model.
Record and access a medial patient’s history.	Screen mock-up showing specific data field.
Develop business strategy, goals and objectives for a new business.	Screen mock-up showing specific data field.
Provide information in English and French.	Prototype with text displayed in English and French.

As shown in the figure below, the Requirements and Design cycle in Business Analysis can be complex and recursive. The Business Requirements gathering is followed by Stakeholder Requirements, Solution Requirements and Transition Requirement, and all these types of requirements may require some sort of Design (e.g. Process model, Screen mock-up, Prototype, etc.) to validate them or generate other requirements from them.
Business Analyst and Designers are not rivaling. Sometimes the same Design techniques are used to eliciting, modelling, and analyzing requirements. That is why a Business Analyst must know design techniques too e work closely with Designers, contributing to an initial design level, so both approaches can satisfy the customer’s need, serving as a secure foundation for software development.