BUSINESS ANALYSIS TERMS L1

Business Analyst

Any person performing business analysis activities, regardless of official job title.

Stakeholder

Any individual or group that has an interest in, influence on, or is affected by a project or initiative.

Requirement

A documented need or condition that a solution must meet.

Solution

A way of satisfying a business need, which may include systems, processes, or changes in behavior.

System Analyst

More focus on technical aspects and documentation

Programmer Analyst

Middle ground between system analyst and developer

Business System Analyst

Middle ground between System and Business analysts

Product Owner

In Agile Environment, have wider vision and more accountability

Business Requirements

High level needs describing why a change is required

Stakeholder Requirements

Needs of specific stakeholders or groups

Solution Requirements

Details of what a solution must do

Non Functional Requirements

Quality attributes such as performance or securit

Predictive Approach

A plan driven approach where requirements are defined early

Adaptive Approach

an iterative approach where requirements evolve over time

Stakeholder Identification

The process of recognizing all individuals or groups impacted by a change

Influence

The ability to affect decisons or outcomes

Stakeholder Mapping

classifying stakeholders based on influence and impact

Engagement Strategy

Planned actions to involve stakeholders appropriately

Provlem Focus

concentrating on underlying issues rather thansurface symptoms

Solutioneering

prematurely proporsing solutions without understanding the problem

5 Whys

technique that repeatedly asks why to reach root casue

Problem Statement

A clear description of the issue to be addressed

Fishbone Diagram

A visual tool to categorize possible causes of a problem

Critical Success Factors

Key areas thhat must succeed for objectives to be met

Key Performance Indicators

measruable values used to track performance

Balanced Scorecard

A framework linking objectives to performance measures

Business Case

a document outlining rationale, benefits, costs, and risks of a proposed change

Rewuirements Elicitation

The process of gathering inormation about needs and expectations

Interview

structured conversation to gather detailed information

Workshop

collaborative session to explore and agree on requirements

Observation

Watching users perform tasks to understand real behaviors

Prototyping

Using early models to clarify needs and ideas

Requirements Catalogue

a structured list of document requirements

User Story

a short statement describing a user need and expected value

Acceptance Criteria

conditions that must be met for a requirement to be accepted

Non Functional Requirements

constraints or quality attributes that define how a solution performs

Traceability

Linking requirements to objective and solutions

Change Control

Managing modifications in a structured way

MoSCoW Method

prioritization framework categorizing requirements as Must, Should, Could, Won’t.