Business Analysis Session1

7/31/2019 Business Analysis Session1

1/13

BUSINESS ANALYSIS

DAY-1

Vamsi Mohan V


2/13

AGENDA

(DAY-1) What is Business Analysis?

Key Concepts

Domain Solution

Requirements

Re uirement Classification Business Requirements

Stakeholder Requirements

Solution Requirements

Transition Requirements

Knowledge Areas

Techniques


3/13

What is Business Analysis?

Business analysis is the set of tasks and techniques used to work as a liaison

among stakeholders in order to understand the structure, policies, andoperations of an organization, and to recommend solutions that enable theorganization to achieve its goals.

Business anal sts must anal ze and s nthesize information rovided b a

large number of people who interact with the business, such as customers,staff, IT professionals, and executives. The business analyst is responsible foreliciting the actual needs of stakeholders, not simply their expressed desires.

In many cases, the business analyst will also work to facilitate communication

between organizational units. In particular, business analysts often play acentral role in aligning the needs of business units with the capabilitiesdelivered by information technology, and may serve as a translator betweenthose groups.


4/13

Role of a Business Analyst


5/13

Key Concepts

Domains

A domain is the area undergoing analysis. It may correspond to the boundaries of

an organization or organizational unit, as well as key stakeholders outside thoseboundaries and interactions with those stakeholders.

Solutions

A solution is a set of changes to the current state of an organization that are madein order to enable that organization to meet a business need, solve a problem, ortake advantage of an opportunity. The scope of the solution is usually narrowerthan the scope of the domain within which it is implemented, and will serve as thebasis for the scope of a project to implement that solution or its components.

Business analysis helps organizations define the optimal solution for their needs,given the set of constraints (including time, budget, regulations, and others) underwhich that organization operates.


6/13

Key Concepts

Requirements

A condition or capability needed by a stakeholder to solve a problem or achievean objective.

A condition or capability that must be met or possessed by a solution or solutioncom onent to satisf a contract standard s ecification or other formall im osed

Contd.,

documents.

A documented representation of a condition or capability as in (1) or (2).

A requirement may be unstated, implied by or derived from other requirements, or

directly stated and managed. One of the key objectives of business analysis is toensure that requirements are visible to and understood by all stakeholders.


7/13

Requirements Gap


8/13

Requirement ClassificationBusiness Requirements:

These are higher-level statements of the goals, objectives, or needs of theenterprise. They describe the reasons why a project has been initiated, theobjectives that the project will achieve, and the metrics that will be used tomeasure its success. Business requirements describe needs of theor anization as a whole and not rou s or stakeholders within it. The are

developed and defined through enterprise analysis.

Stakeholder Requirements

These are statements of the needs of a particular stakeholder or class of

stakeholders. They describe the needs that a given stakeholder has andhow that stakeholder will interact with a solution. Stakeholder requirementsserve as a bridge between business requirements and the various classesof solution requirements. They are developed and defined throughrequirements analysis.


9/13

Requirement ClassificationContd.,Solution Requirements

It describe the characteristics of a solution that meet business requirements

and stakeholder requirements. They are developed and defined throughrequirements analysis. They are frequently divided into sub-categories,particularly when the requirements describe a software solution.

1 Functional Re uirements describe the behaviour and information that

the solution will manage. They describe capabilities the system will be ableto perform in terms of behaviours or operationsspecific informationtechnology application actions or responses.

2) Non-functional Requirements capture conditions that do not directly

relate to the behaviour or functionality of the solution, but rather describeenvironmental conditions under which the solution must remain effective orqualities that the systems must have. They are also known as quality orsupplementary requirements. These can include requirements related tocapacity, speed, security, availability and the information architecture and

presentation of the user interface.


10/13

Requirement ClassificationContd.,

Transition Requirements

These requirements describe capabilities that the solution must have in order tofacilitate transition from the current state of the enterprise to a desired futurestate, but that will not be needed once that transition is complete. They aredifferentiated from other re uirements t es because the are alwa s tem orar

in nature and because they cannot be developed until both an existing and newsolution are defined. They typically cover data conversion from existingsystems, skill gaps that must be addressed, and other related changes to reachthe desired future state. They are developed and defined through solutionassessment and validation


11/13

Knowledge Areas


12/13

TechniquesTechniques provide additional information on different ways that a task maybe performed or different forms the output of the task may take. A task mayhave none, one, or more related techniques. A technique must be related to at

least one task.

Some Techniques:

Acceptance and Evaluation Criteria Definitionra nstorm ng

Business Rules AnalysisData Dictionary and GlossaryData Flow DiagramsData ModelingDecision AnalysisDocument Analysis

InterviewsMetrics and Key Performance IndicatorsNon-functional Requirements AnalysisOrganization ModelingProblem TrackingProcess Modeling

Requirements WorkshopsScenarios and Use Cases


13/13

Session Review:

Questions?

I would like to hear from you: please send us your queries [email protected]

Business Analysis Session1

Documents

Transcript of Business Analysis Session1