Year End Sale is ON. Save up to $350 and Get 2 Months Extra Access!
mainlogo google-rating trustpilot-rating mail call call-button cart

Everything You Wanted to Know About Requirements Analysis

Purpose, Techniques and Tasks.

Purpose of requirements analysis

The purpose of requirements analysis is to specify requirements at a level that allows developers to develop systems according to stakeholder needs. Developers need detailed level requirements to construct solutions. Poor requirements analysis can result in large number of requirement changes!

Requirements analysis uses multiple techniques. The most popular ones are:

  1. Business rules analysis
  2. Concept modelling
  3. Data dictionary
  4. Data flow diagrams
  5. Data mining
  6. Data modelling
  7. Glossary
  8. Interface analysis
  9. Non-functional requirements analysis
  10. Process analysis
  11. Process modelling
  12. Prototyping
  13. Sequence diagrams
  14. State modelling
  15. Use cases and scenarios
  16. User stories
Computer and phone
Computer and phone

 

 

Organize requirements

Purpose: To organize requirements into appropriate requirements levels and categories.

Stakeholders: Domain SME, End user, Implementation SME, and Project manager.

Inputs

  1. Confirmed requirements
  2. Organization process assets

Elements

Organize requirements according to type of requirement (Functional, non-functional, constraint), level of requirement (High level vs. detailed).

Outputs

  1. Organized requirements.

Tools and Techniques

Functional decomposition, Requirements templates.

Prioritize requirements

Purpose: To ensure project efforts focus on the most critical requirements.

Stakeholders: Sponsor*, Domain SME*, Implementation SME*, Regulator, and Project manager*.

Inputs

  1. Business need
  2. Business case
  3. Organized requirements
  4. Requirement prioritization guidelines
  5. Stakeholder list, roles, and responsibilities

Elements

  1. Enhance requirements attributes.
  2. Prioritize requirements.
  3. Manage requirements prioritization challenges.

Outputs

  1. Prioritized requirements

Tools and Techniques:

Ranking, Decision analysis, Risk analysis, MoSCoW analysis, Time-boxing, Budgeting and Voting

Computer and phone
Computer and phone

 

 

Model and elaborate requirements

Purpose: To model and elaborate prioritized requirements using a combination of matrices, diagrams, and mathematical formulas.

Stakeholders: Domain SME.

Inputs

  1. Prioritized requirements

Elements

  1. Elaborate requirements.
  2. Model requirements.

Outputs

  1. Modeled requirements

Tools and Techniques:

Data flow diagram, Functional decomposition, Interface analysis, Non-functional requirements analysis, Organization modelling, Process modelling, Prototyping, Scenarios and use cases, State diagrams, and User stories, Matrix model, Use case specifications, Flow charts, Decision tables, Activity diagram.

Prepare requirements packages

Purpose:

To package set of requirements in an appropriate manner for effective stakeholder communication.

Stakeholders: Primary responsibility of Business Analyst.

Inputs
1. Business analysis communication plan.
2. Organizational process assets.
3. Requirements.
4. Requirements structure.

Elements

1. Prepare work products, and deliverables.

Outputs

1. Requirements package.

Tools and Techniques:

Requirements documentation templates

Computer and phone
Computer and phone

 

 

Verify requirements

Purpose:

To ensure requirements and packages meet necessary standards of quality. To identify defects in the requirements before presenting to other stakeholders.

Stakeholders: Primary responsibility of Business Analyst.

Inputs

1. Packaged requirements
2. Requirements quality criteria.

Elements

1. Review requirements.
2. Update requirements based on review.

Outputs

1. Verified requirements

Tools and Techniques:

Requirements review checklist, Commenting, Inspection, Prototyping, Peer review, Structured walkthrough.