BA Chapter 2: Business Analysis Key Concepts


This chapter provides business analysts with a basic understanding of the core ideas necessary for understanding and implementing the BABOK Guide in practice of business analysis.

The following are the five main key concepts of the chapter summarized in quick understanding:
1.       Business Analysis Core Concept Model™ (BACCM™): Describes basic concept for business analysis profession. Irrespective of the perspective, industry, methodology, or the organization level the six terms most business analysis used here are
·        Change: Transformation in response to a need
·        Need: Problem or opportunity to be addressed - motivate stakeholders to act.
·        Solution: Uniquely satisfying one or more needs - resolves problem faced by stakeholders and allow stakeholders to take advantage of an opportunity.
·        Stakeholder: Group or individual responding to the change, need, or the solution.
·        Value: Realized returns, gains, and improvements - decreases in value in the form of losses, risks, and costs.
·        Context: The context is the focus relevant to the change. These can include elements like attitudes, behaviors, beliefs, competitors, culture, demographics, goals, governments, infrastructure, languages, losses, processes, products, projects, sales, seasons, terminology, technology, weather etc.
Each of this term is fundamental to the practice of business analysis.
2.       Key Terms: Importance of essential keyword are highlighted here, and these includes Business Analysis, Business Analysis Information, Design, Enterprise, Organization, Plan, Requirement, Risk
3.       Requirements Classification Schema: identifies types of requirements that can assist business analysts and other stakeholders in grouping business requirements. These includes
·         Business requirements includes (statements of goals, objectives, and outcomes)
·         Stakeholder requirements includes (stakeholders need)
·          
·         Solution requirements (capabilities and qualities of a solution that meets the stakeholder requirements)
·         functional requirements (capabilities that a solution must have) and non-functional like quality of service requirements.
·         Transition requirements: capabilities that the solution must have in order to facilitate transition from the current to future state.

4.       Stakeholders: These are the role players associated with the business analysis activities within the anticipated change. interact with business analysts directly or indirectly - participate in the execution of that task associated to the stakeholder.
5.       Requirements and Designs: uniquely identify the importance of requirements and designs as they relate to business analysis. Eliciting, analyzing, validating, and managing requirements - level of responsibility for design varies based on the situation in which the business analyst works.

Comments

  1. Dalsher Singh VirkSeptember 11, 2019 at 11:04 PM

    I would like to focus on the Business Analysis Core Concept model and give my own views on the matter with respect to Wawanesa Insurance company. These concepts each relate to one another, build a powerful foundation for analysis, guide decision-making, and can be evaluated iteratively for projects.
    • BAs at Wawanesa Collect, document, and analyze workflows, as well as develop business process models(understand the CONTEXT) after consultation with STAKEHOLDERS(customer, domain subject matter expert, end user, implementation subject matter expert, operational support, project manager, regulator, sponsor, supplier and testers).
    • They Interview system stakeholders and record results, requirements, and recommendations(Basically their NEEDS).
    • They analyze process gaps and information flow obstacles or system issues and identify opportunities for improvement. Prepare and present related material to project teams, steering committees, and/or stakeholder organizations(SOLUTION).
    • Translate business needs into high-level technical requirements and establish recommendations(CHANGE) for improvements in system effectiveness and efficiency(add VALUE).

    ReplyDelete
  2. Yogesh JaglanSeptember 11, 2019 at 11:08 PM

    Planning – It describes a set of events, the dependencies among the events the expected sequence. Some of the points to plan a particular project -:

    • Powerful features and robust functionality
    • Impressive, modern user interface
    • Excellent support team and quick to respond
    • Powerful online tool to work productively
    • Seamless integrations
    • Easy to use system
    • Chat, manage tasks, and share files
    • Free unlimited posts, users, and storage
    • Communicate efficiently with your whole team



    ReplyDelete
  3. Amanjot kaur chahalSeptember 11, 2019 at 11:20 PM

    I would like to highlight the requirement classification scheme with respect to Wawanesa . This responsibility applies to personal information that we transfer to service providers located in Canada as well as to those located in other countries.
    • Wawanesa Company protects the information in a manner that is consistent with our Personal Information Protection Policy and security practices, as well as applicable law. Use the information only for purposes that we have authorized, and for which you have provided your consent.
    • To ensure that your personal information continues to be protected in such circumstances, we contractually require our service providers to ensure that any service providers to whom they transfer our customers' personal information will maintain a comparable level of protection of that personal information.


    In this step, my focus is on requirements and design of Wawanesa. We may transfer your personal information to service providers outside of Canada for one or more of the following purposes:
    • communicating with you;
    • underwriting risks on a prudent basis;
    • investigating and paying claims;
    • detecting and preventing fraud;
    • offering and providing property and casualty insurance products and services to you;
    • compiling statistics and analyzing business results;
    • acting as required or authorized by law; and
    • processing or storing information in connection with any of these purposes.

    ReplyDelete

Post a Comment

Popular posts from this blog

BR Chapter 12: Fit Criteria and Rationale

A satisfying viewpoint (among a large number) of Kent Beck's eXtreme Programming system is its emphasis on composing experiments before composing the code. The experiment characterizes the measuring stick that the executed code must match. The fit model is pretty much something very similar: It is a measuring stick for the necessity. By adding a fit rule to the necessity, you are, basically, composing its experiment. In the event that you are utilizing client stories, at that point we firmly propose that you give specific consideration to the explanation given for the usefulness. This is pretty much equivalent to the justification, and is a significant supporter of winding up with the right item. Composing experiments on the back of the story card ought to accomplish a similar reason as the fit standard we talk about here.  For each of the non-practical necessities yielded by the blog, we presently propose determining the fitting fit rule, affirming it with the partner, and compo...
Read more

BA Chapter 9: Underlying Competencies

Image
Underlying Competencies are a description of the behaviours, characteristics, knowledge, and personal qualities that support the practice of business analysis. BABOK® defines 6 key groups of competencies that a BA is expected to possess. Each competency group constitutes of multiple sub competencies which are as discussed below: (Source: https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/1287/Developing-a-Competency-Model-for-Business-Analysts.aspx) 1.      Analytical Thinking and Problem Solving : These skills are required for business analysts to analyze problems and opportunities effectively, identify which changes may deliver the most value, and work with stakeholders to understand the impact of those changes. Analytical Thinking and Problem-Solving core competencies include: ·            Creative Thinking ·           Decision Making ·  ...
Read more

BR Chapter 6: Scenarios

Image
At this stage of the requirements process, the business analyst has identified the business events as well as the business use case which we referred to as BUC and these correspond to the business events.   Below are some of the techniques the Business Analyst can use to communicate requirements to the stakeholders: Scenarios The Business Analyst can use Scenarios to model and record the BUCs. A scenario is an outline of a plot, or a postulated sequence of steps - it tells the story of a business use case.   The scenario is a neutral medium, and one that is both simple and understandable to all stakeholders.  A business analyst would use a scenario like this to elicit, and then describe, a business use case to its interested stakeholders. The BUC is a discrete amount of functionality; it happens in its own time frame and can be considered separately from other parts of the work’s functionality. The BA model a scenario and use it to reach a...
Read more