Business Analysis.md

https://github.com/ReqEng-Analysis/Ashlynn_Glitz-Glitter_Boutique/blob/main/BusinessAnalysis.md

Business Requirement Specification (BRS)

The Business Requirements Specification, or BRS, is a document that specifies how a proposed software or system will contribute to meeting the business objectives of a company. The specification document details topics related to the proposed software or system such as scope, functions of the product, features of the product, etc.

Reading Notes

Some notes may be similar to the texts that are cited.

SWEBOKwiki Business or Mission Analysis

https://www.sebokwiki.org/wiki/Business_or_Mission_Analysis

SoI: system of interest

• The starting point of engineering an SoI is understanding the requirements needed for the system
• Must look at the problem from every perspective

Mission Analysis (MA): part of concept definition activities; the set of systems engineering activities in which the problem space and the need of the business or enterprise and stakeholders are closely examined, identified, and characterized

• Occurs before any formal def of SoI is developed
• Focuses on the identification of the primary purposes of the solution
• Purpose: to understand a mission/market problem or opportunity, analyze the solution space, and initiate the life cycle of potential solutions that address the problem or take advantage of an opportunity.
• Focused on defining the problem space

Concept of Operations (ConOps): at the organization level, addresses the leadership's intended way of operating the organization. ConOps document serves as a basis for the organization to direct the overall characteristics of future business and systems. Operational Concept (OpsCon): (operational focus) ConOps informs OpsCon, drafted by business management in MA activity and refined by stakeholders; OpsCon doc describes what the system will do (not how) and why. Used to communicate overall quantitative and qualitative system characteristics to every organizational level (user, acquirer, supplier, etc)

• Most enterprises re-evaluate their strategy with respect to their mission, vision, and positioning to accomplish their goals

29148-2018 6.2 Business or Mission Analysis Process

https://ieeexplore.ieee.org/document/8559686

Purpose

• The purpose of the Business or Mission Analysis process is to define the business or mission problem or opportunity, characterize the solution space, and determine potential solution class(es) that could address a problem or take advantage of an opportunity.

Preparation

• Review identified problems and opportunities in the organization strategy with respect to desired organization goals or objectives.
• Define the business or mission analysis strategy
• Identify and plan for the necessary enabling systems or services needed to support business or mission analysis
• Obtain or acquire access to the enabling systems or services to be used

Define the Problem or Opportunity Space

• Analyze the problems and opportunities in the context of relevant trade-space factors.
• Analyze customer complaints, problems, and opportunities in the context of relevant trade-space factors.
• Define the mission, business, or operational problem or opportunity

Characterize the solutions space

• Define preliminary operational concepts and other concepts in life cycle stages
• Identify candidate alternative solution classes that span the potential solution space

Evaluate alternative solution classes

• Assess each alternative solution class
• Select the preferred alternative solutions class(es).

Manage the Business or Mission Analysis

• Maintain traceability of business or mission analysis
• Provide key [artifacts and] information items that have been selected for baselines

29148-2018 8.2.2 BRS example outline

https://ieeexplore.ieee.org/document/8559686

Check the link for example outline.

29148-2018 9.3 Business Requirements Specification (BRS) content

https://ieeexplore.ieee.org/document/8559686

Purpose

• Should describe how the proposed system will contribute to meeting business objectives

Scope

• Identify the business domain name
• Define the range of business activities included in the business domain concern. The scope can be defined in terms of divisions in the organization and external entities that related directly to the business activities
• Describing the scope of the system being developed or changed

Overview

• Describe major internal divisions and external entities of the business domain concerned and how they are interrelated

The Business Analysis Process: 8 Steps to Being an Effective Business Analyst

(Only the first 4 Steps) https://www.bridging-the-gap.com/business-analysis-process/

1. Get Oriented

• It is important to clarify the scope, requirements, and business objectives as quickly as possible
• That doesn't mean getting knee-deep into the detailed requirements right away
• Take time to get oriented, this will ensure you are not only moving quickly but also able to be an effective and confident contributor to the project

Responsibilities

• Clarify your role as a BA to ensure we are creating deliverables that meet stakeholder needs
• Determine primary stakeholders to engage in defining the project's business objectives and scope, consult early in the project
• Understand project history
• Understand existing systems and business processes

2. Discover the Primary Business Objectives

• Uncovering and getting agreement on the business needs early in a project and before the scope is defined is the quickest path forward to a successful project.

Key responsibilities

• Discovering the why behind the project from primary stakeholders
• Reconciling conflicting expectations so the project is done with a shared understanding of business objectives
• Ensuring the business objectives are clear and actionable to provide the project team with momentum and context while defining the scope and, later on, the detailed requirements.

3. Define Scope

• Scope makes the business needs tangible in such a way that multiple project team participants can envision their contribution to the project and the implementation

Responsibilities:

• Defining a solution approach to determine the nature and extent of tech and business process changes to be made as part of implementing the solution
• Drafting a scope statement and reviewing it with business and tech stakeholders to ensure clarity
• Confirming the business case to ensure that it still makes sense for your organization to invest in the project

4. Formulate Your Business Analysis Plan

• The business analysis plan will bring clarity to the BA process that will be used to successfully define the detailed requirements for this project.
• In the absence of defining a credible and realistic plan, a set of expectations may be defined for you.

Responsibilities

• Choosing the most appropriate types of BA deliverables
• Defining the specific list of BA deliverables that will completely cover the scope of the project & identify stakeholders who will take part in the creation and validation of each deliverable
• Identify timelines for completing BA deliverables

Research / Information Literacy

https://sites.google.com/site/profvanselow/success/research

It is important to conduct thoughtful research from credible sources to formulate a better understanding of the topic at hand.

"Software Requirements" Weigers book Ch. 4 The business analyst

• Business analyst(BA): The individual who has the primary responsibility to elicit, analyze, document, and validate the needs of the project stakeholders.
• BAs are grown from diverse backgrounds of education and work experience, so they will likely have gaps in their knowledge and skill sets.
• In agile, the function of a BA might not be done by someone who is called a BA. Though, the functions of a BA are still needed. A product owner may perform some of a traditional BA's tasks.
• BA has the major responsibility for creating a collaborative relationship amongst the various individuals working on the project.

BA tasks

• Define business requirements
• Plan the requirement approach
• Identify project stakeholders and user classes
• Elicit requirements
• Analyze requirements
• Document requirements
• Communicate requirements
• Lead requirements validation
• Facilitate requirements prioritization
• Manage requirements

Essential analyst skills

• Listening skills
• Interviewing and questioning skills
• Thinking on your feet
• Analytical skills
• Systems thinking skills
• Learning skills
• Facilitation skills
• Leadership skills
• Observational skills
• Communication skills
• Organizational skills
• Modeling skills
• Interpersonal skills
• Creativity

"Software Requirements" Weigers book Ch. 5 Establishing the business requirements

• Business requirements issues must be resolved prior to constructing the functional and non-functional requirements of a project.
• Business requirements set the stage for the benefits the business hopes to achieve by taking on the project.
• Product vision: succinctly describes the ultimate product that will achieve the business objectives.
• Project Scope: identifies what portion of the ultimate product vision the current project or development iteration will address.
• Vision & Scope doc: collects the business requirements into a single deliverable that sets the stage for the subsequent development work.
• Ensure that the scope is kept in focus, it can be changed, especially if it aids in moving the project forward in the right direction.

My Business Analysis

• I first collected credible information regarding the implications of the system. It is important to understand the key features and the best methods of implementing said features.
• After, I identified and analyzed the key components needed for the system, I ensured to assess the credibility of the information gathered throughout the research and discovery phase.