Phone: (678) 366-1363 | Toll Free: (866) 675-2125

Requirements Analysis Techniques

Requirements Analysis is the process of breaking down complex topics into lower-level components to expose the details and gain a better understanding of the parts that make up the whole. By breaking it down using effective requirements analysis techniques, you are better able to analyze and discuss different aspects of a topic with your stakeholders, confirm your understanding, and communicate the needs to others in a more logical and thorough manner. Team members need to look at the requirements from different perspectives as well as with varying levels of detail, therefore it’s critical to have strong requirements analysis skills within the team.

 DataExternal Agents
(or actors)
ProcessesBusiness Rules
Business / Stakeholder Requirements
  • Process Text Template

  • ERD
  • Process Text Template

  • Context Level Dataflow Diagram
  • Process Text Template

  • Process Decomp
  • User Story
  • Workflow
  • Decision Table

  • Text Statements
  • ERD
Solution Requirements
  • Process Text Template

  • Prototype
  • ERD
  • Workflow
  • Use Case Description
  • Use Case Diagram

  • Workflow (Swimlane)
  • Prototype
  • Interface Diagram
  • Use Case Diagram

  • Use Case Narrative
  • Prototype
  • Workflow
  • User Interface Specification
  • Program Specification
  • Design Document

  • Decision Table
  • Text Statements
  • ERD
  • Use Case Description
  • Workflow

Poor requirements analysis results in solving the wrong problem, missing requirements, or ineffective communication with critical stakeholders. Excellent requirements analysis provides an effective communication vehicle and allows for collaboration among stakeholders to find and fill-in gaps, clarify requirements, examine alternative solutions, and ultimately develop an excellent product or solution.

Classroom Experience

Interactive workshops allow students to practice the techniques as they learn. It supports the standards outlined in the IIBA BABOK® Guide and PMI-PBA certification. This course can be taken either stand-alone or as part of the 4-day Essential Skills for Business Analysis course.

Learning Objectives

  • Simplify your requirements into four core components that are easier to “consume”
  • Still writing requirements? Instead, identify the most effective diagramming techniques and modeling options to support your software development approach (waterfall, iterative, and agile) and project type
  • Compare analysis techniques to select the technique(s) that will best:
    • support your critical thinking, understanding, and problem solving
    • communicate to stakeholders information to enhance review
  • Minimize confusion and development errors by developing excellent requirements that can be easily understood by distributed or outsourced teams
  • Improve your models and diagrams during analysis by asking the right questions



  • Describe requirements and the importance of requirements analysis
  • Provide guidance on how requirements analysis techniques are applicable within any methodology
  • Compare and contrast the requirements analysis perspectives: what vs how and AS IS vs TO BE
1 hour

Breaking Down Requirements into Core Components

  • Define the four core components that make up all requirements
    • Data
    • Process
    • External Agent/Actor
    • Business Rules
  • Describe what the core components describe
  • Identify the importance of core components to your requirements audience
1 hour
See More…

Using Analysis Techniques to Your Advantage

  • Describe how particular analysis techniques:
    • drive quality analysis
    • communicate requirements perspectives effectively
  • Go beyond documenting requirements solely with text – describe how diagrams and models can also be used for analysis
  • Compare and contrast the different requirements analysis techniques when preparing to communicate with your audience
    • Context Data Flow Diagram
    • Process Decomposition Diagram
    • Entity Relationship Diagram
    • Glossary
    • Decision Tables
    • Workflow Diagramming
    • Use Case Modeling
    • User Stories
    • Prototyping
  • Create the right analysis approach based on your stakeholder’s learning style
  • Confirm the analyzed requirements with stakeholders
4.5 hour

Course Summary

  • Bringing it all together
  • Develop an Action Plan with next steps on the student’s current project
.5 hour

Appendix - Overview of Application Development Methodologies

  • Discuss various methodologies for application development and their history.
  • Learn which models are used in each methodology:
    • Waterfall
    • Agile
    • Iterative
    • Prototyping
    • Incremental Development
    • Spiral/RUP
    • RAD
    • Extreme Programming (XP)
    • Object Oriented Methodologies
    • IDEF