Requirements Analysis Techniques

Introduction

Which requirements analysis technique should I use? Which one is the best for my project? 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.

Requirements Analysis Techniques Covered

	Data	External Agents (or actors)	Processes	Business Rules
Stakeholder Requirements	ERD Capability & Process Text Template Context Level Dataflow Diagram	Capability & Process Text Template Context Level Dataflow Diagram	Capability & Process Text Template Functional Decomposition Diagram Flowchart User Story	Decision Table Decision Tree Decision Model™ Text Statements ERD Capability & Process Text Template
Functional Requirements	ERD Entity & Attribute Templates Capability & Process Text Templates Prototype Flowchart Use Case Description	Use Case Diagram Flowchart (Swimlane, BPMN, UML Activity Diagram) Prototypes	Use Case Diagram Use Case Description Prototype Flowchart	Decision Table Decision Tree Decision Model™ Text Statements ERD Use Case Description Flowchart Capability & Process Text Template
Technical Requirements	Prototype ERD User Interface Specification	Interface Diagram User Interface Specification User Permissions	User Interface Specification Program Specification System Flows Design Documentation	Decision Table Decision Tree Decision Model™ ERD

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

Student Profile

This course is designed for Business Analysts, Project Managers, Business Systems Analysts, Product Managers, Product Owners, System Architect, Process Engineers, Requirements Engineers or any member of the project team.

Is this course for you?

Not sure if this course is a good fit for your needs? Take our self-assessment!

Prerequisites

There are no prerequisites to attend this course.

Course Materials

Each student will receive a copy of the course documentation prepared by Netmind.

Methodology

Interactive workshops allow students to practice requirements analysis techniques as they learn. It is compatible with the standards described in the BABOK® IIBA Guide and the PMI-PBA certification. This course can be taught independently or as part of our 4-day Essential Skills for Business Analysis course.

Accreditation

A certificate of attendance will be issued to students who attend the course for at least 75% of the duration.

Certification

This course is included in our Business Analysis Certification Program. By attending this course, students earn credit towards the BA Associate and BA Certified certifications, as well as credit towards the Business Rules Badge, Data Analysis Badge, Functional Analysis Badge, and Process Analysis Badge.

Additionally, students will earn 7 credit hours for their attendance.

Course Outline

Introduction
1. Describe requirements and the importance of requirements analysis
2. Provide guidance on how requirements analysis techniques are applicable within any methodology
3. Compare and contrast the requirements analysis perspectives: what vs how and AS IS vs TO BE
Breaking Down Requirements into Core Components
1. Define the four core components that make up all requirements
  1. Data
  2. Process
  3. External Agent/Actor
  4. Business Rules
2. Describe what the core components describe
3. Identify the importance of core components to your requirements audience
Using Analysis Techniques to Your Advantage
1. Describe how particular analysis techniques:
  1. Drive quality analysis
  2. Communicate requirements perspectives effectively
2. Go beyond documenting requirements solely with text – describe how diagrams and models can also be used for analysis
3. Compare and contrast the different requirements analysis techniques:
  1. Context Data Flow Diagram
  2. Decomposition Diagram
  3. Entity Relationship Diagram
  4. Glossary
  5. Decision Tables and Decision Models
  6. Workflow Diagramming/Flowcharts
  7. Use Case Modeling
  8. User Stories
  9. Prototyping
4. Create the right analysis approach based on your stakeholder’s learning style
5. Confirm the analyzed requirements with stakeholders
Course Summary
1. Bringing it all together
2. Develop an Action Plan with next steps on the student’s current project
Appendix – Overview of Application Development Methodologies
1. Discuss various methodologies for application development and their history.
2. Learn which models are used in each methodology:
  1. Waterfall
  2. Agile
  3. Iterative
  4. Prototyping
  5. Incremental Development
  6. Spiral/RUP
  7. RAD
  8. Extreme Programming (XP)
  9. Object Oriented Methodologies
  10. IDEF

Custom Classes

Jan 29, 2020
9:00 - 5:00 EST
Live Virtual

This session is highly interactive utilizing the latest Adobe® Connect technology. It enables students the opportunity to collaborate with other students and receive instructor feedback in breakout sessions. Additional details will be forwarded to you 2 weeks prior to class with login details. To optimize you and your classmates experience, we recommend that you use a headset during class.

“This class environment was excellent and well organized. I wasn’t sure how smoothly things would go with a virtual training, but it felt just like being in a classroom.”

Requirements Analysis Techniques

Introduction