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
- 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
- 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
- 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:
- Context Data Flow Diagram
- Decomposition Diagram
- Entity Relationship Diagram
- Glossary
- Decision Tables and Decision Models
- Workflow Diagramming/Flowcharts
- Use Case Modeling
- User Stories
- Prototyping
- Create the right analysis approach based on your stakeholder’s learning style
- Confirm the analyzed requirements with stakeholders
- Course Summary
- Bringing it all together
- Develop an Action Plan with next steps on the student’s current project
- 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
