Business Analysis Key Concepts


The Five key concepts of  BABOK 3.0  chapter2 are….
By Liliane Castano Marino

1)     Business Analysis Core Concept Model (BACCM)

BABOK v3 identifies the Business Analysis Core Concept Model (BACCM) that defines the six main elements of business analysis. As follows:

Ø  Change
Ø  Need
Ø  Solution
Ø  Stakeholder
Ø  Value
Ø  Context

That means that every business analysis initiative must always take these elements into account.  They are equally necessary so there is no single concept that should stand out from the rest. These essential concepts can and should be used by the BA practitioner to consider the quality and completeness of the work being done.

2)    Key Terms

Some of the Key terms defined in BABOK v3 are:

Organization - An autonomous group of people under the management of a single individual or council that works to achieve goals and common objectives, including scope, budget, schedule, resources, quality and risk.

Plan - A detailed scheme for doing or achieving something. Usually is composed of a set of events, dependencies, expected sequence, schedule, results or outputs, materials and necessary resources and how stakeholders need to be involved.

3)    Requirements Classification Schema

The requirements classification schema used by the BABOK v3.0 places requirements in one of the following categories:

Business requirements
Stakeholder requirements
Solution requirements
Functional requirements
Non-functional requirements or quality of service requirements
Transition requirements


Business Requirements are the highest level of requirements and represent business objectives, stated by the customer.  Business Requirements define WHAT the business is trying to achieve.  As a result, Business Requirements define WHY a project should be carried out or a solution implemented.   

4)     Stakeholders 

An interested party is a class of people directly or indirectly affected by the initiative.  Stakeholders represent people with whom the business analyst is likely to interact in some way. According to BABOK v3.0, the customer role is included in the generic list of stakeholders because they are the ones who use or will use the product, service or result of the project.  They can be internal or external, in relation to the company that is executing the project

5)     Requirements and Designs

According to BABOK v3.0, business analysts are responsible for eliciting, analyzing, validating and managing requirements.  However, the definition of the design is somehow also recognized as the responsibility of the business analyst. So, even if it is some other role that creates the design, the business analyst must review it final version to ensure that it meets the requirements.
It is important to emphasize that is part of the business analyst role to always ask for ‘why?’.  For example, “why is the requirement or design important to provide value for an organization?”.


Comments

  1. Paramjeet Kaur Toor20 January 2020 at 15:40

    I understand all basic and main concepts of business analysis that include analysis of customer needs, changes that can make business better, finding solutions for problems etc. In addition, requirements are distributed into various group such as business, stakeholder, solutions and transaction requirements that raised at different stages of project. Business requirements represents the objective for initiative the change, stakeholder requirements describe needs of stakeholder, solutions requirements represents the capabilities and quality of solutions that meets the stakeholder requirements and last one is temporary requirement that condition the solutions must meets to transition from current to future state.

    ReplyDelete
  2. Harvinder Singh20 January 2020 at 17:48

    Main concepts are very crucial to understand and with the help of this blog it can be easy to understand. After reading the chapter 2 it is quite easy to understand that how to describe and define business analysis. Business Analysis Core Concept model is very useful for every business as it explain the overview of the business which helps the managers to identify the needs, change and so on.
    As we talk about the requirement, Business requirement and Changes are very important things to give some variation in the work. Business analyst have to very effective on changes as it is concept of business analysis core concept model which is very important. With this the stakeholders is very good term to talk about as it is very important for the projects

    ReplyDelete
  3. Hassan Kamara4 February 2020 at 20:28

    The concepts of chapter 2 were covered very well in this blog. reading it has helped me to gain a further knowledge on the business analysis core concept model. from reading this I learned that customers are a part of stakeholders and that there are other types as well. the types of stakeholders can be both internal and external which is something interesting to me seeing as I thought a stakeholder was just a person and not a whole role. it was interesting to read that the business analyst is responsible for not only analyzing but also managing, eliciting and validating the requirements.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 8 - Starting the Solution by Harvinder Singh

  Chapter 8 Starting the Solution We are transferring from an abstract global to the physical international, from policy to technology, from problem to solution; from purpose to design: we have reached the closing quadrant of the Brown Cow Model, in which will be determined how we are going to enforce the essential business. With a solid know-how of the essence of the business, which means that the real trouble to be solved, it’s time to determine which components of that problem would advantage from being automated. The commercial enterprise analyst juggles many factors to determine the most appropriate product to build. Iterative Development Iterative development is a way of breaking down the software improvement of a large application into smaller chunks. In iterative development, feature code is designed, developed and examined in repeated cycles. With each iteration, additional functions may be designed, advanced and examined till there is a com...
Read more

Chapter 4- Business Use Cases - posted by Chelsia Palta

Understanding the Work  The product you intend to build must improve its owner’s work; it will be installed in the owner’s area of business and will do part of the work. It does not matter which kind of work it is commercial, scientific, embedded real-time, manual, or automated you always have to understand it before you can decide which kind of product will best help with it. Use Cases and Their Scope The term "use case" was coined by Ivar Jacobson back in 1987 as a way to describe an interaction between a system and a user of that system. Jacobson needed to break the system into smaller units, as he felt that object models were not scalable. Thus, to conquer the complexity and largeness of modern systems, he said it was first necessary to partition them into convenient chunks, and that these chunks should be based on the user’s view of the system. The Outside World Adjacent systems behave like any other systems: They contain processes and consume and/or...
Read more

Chapter 11 Non-Functional Requirements by Hassan

Non-Functional Requirements Non-Functional Requirements can be generalized as "what a product/system is supposed to be. these requirements tend to be qualities that the product should have and they should specify how well the product does what it does. the requirements should either make the product usable, fast, reliable, attractive or safe and they should describe the character/ the way the functions should behave. Look and Feel Requirements the look and feel requirements are key to the non-functional requirements and as a BA one must consider them for every project. These requirements can describe how a product/system's desired appearance, mood, spirit or overall style/ appearance. The look and feel requirements can further specify what the product/system intends to appear as and is not a detailed design of the product/system itself. The typical look and feel requirement should be simple to use, professional looking, attractive to its market, consistent with previ...
Read more