Clicky

Types of Business Analysis

This page contains definition and basic information about the main types of Business Analysis – High Level Analysis and Detailed Business Analysis.

Types of Business Analysis – High Level and Detailed Analysis

High level analysis document- HLA

One of the main types of Business Analysis is HLA. The purpose of High Level Analysis Document is to collect, analyze, and define high-level needs and features for creation (or upgrading an existing) service/system. It focuses on the capabilities needed by the stakeholders, and the target users, and why these needs exist.

The objective of writing a High level analysis document is to enable agreement among stakeholders, developers, and business representatives. Another purpose of writing a Vision document is to provide a common platform for agreement between the developers themselves.

Main features of the High level analysis documents are:

  • Overview
  • Glossary
  • Problem Statement
  • Stakeholder Profiles
  • Product Features
  • Assumptions, Dependencies and Constraints
  • Solution Alternatives Overview

Stay AS-IS

  • Advantages
  • Disadvantages
  • Impacted Systems
  • Effort Estimation

Outsource system development

  • Description
  • Advantages
  • Disadvantages
  • Impacted Systems
  • Effort Estimation

Internally develop a system

  • Description
  • Advantages
  • Disadvantages
  • Impacted Systems
  • Effort Estimation

Buy a commercial off-the-shelf product and integrate it

  • Description
  • Advantages
  • Disadvantages
  • Impacted Systems
  • Effort Estimation
  • Solution Alternatives Comparison

Detailed Business Analysis – BRD

Detailed Business Analysis is the second of the main types of Business Analysis. The aim of the Detailed business analysis document is to define the business rules, functional requirements, constraints, assumptions and use cases for the projects.

Main features of the Detailed business analysis documents are:

Overview
Acronyms, Abbreviations and Definition
Assumptions and Constraints
Business Rules
Functional requirements

  • Requirement ID
  • Priority
  • Requirement name
  • Requestor
  • Assigned to
  • Description
  • Attachment/Diagram/Example:

Non-Functional Requirements

  • Requirement ID
  • Priority
  • Requirement name
  • Requestor
  • Assigned to
  • Description
  • Attachment/Diagram/Example

Use case

  • Use Case ID
  • Priority
  • Use Case name
  • Requestor
  • Summary
  • Actors
  • Triggers
  • Preconditions
  • Basic Course of Events
  • Alternative Course of Events
  • Exceptions
  • Post conditions:
  • Attachment/Diagram/Exampl

Appendix

See also what is business analysis and business analyst.