In this business analysis training, you will learn Requirement Management. Topics covered in this session are: • Requirements Management • Requirement Prioritization • MoSCoW Analysis • Time Boxing • Voting Technique • Verifying and Validating Requirements • Verifying Requirements • Validate Requirements • Key Requirements Management Practices • The Requirements Baseline • Requirements Version Management • Requirements Change Control • Impact Analysis of Requirements • Requirements Attributes • Requirements status tracking • Requirements Traceability • Requirements Traceability Matrix For more information, visit this link: https://www.mindsmapped.com/courses/business-analysis/business-analyst-training-for-beginners/

1. Page 0Classification: Restricted
Business Analysis
Training
Requirement Management

2. Page 1Classification: Restricted
Agenda
•Requirements Management
• Requirement Prioritization
• MoSCoW Analysis
• Time Boxing
• Voting Technique
• Verifying and Validating Requirements
• Verifying Requirements
• Validate Requirements
• Key Requirements Management Practices
• The Requirements Baseline
• Requirements Version Management
• Requirements Change Control
• Impact Analysis of Requirements
• Requirements Attributes
• Requirements status tracking
• Requirements Traceability
• Requirements Traceability Matrix

3. Page 2Classification: Restricted
Components of Requirements Engineering

4. Page 3Classification: Restricted
Key Requirements Management Practices
• Create a requirements baseline.
• Manage version of requirements documents.
• Adopt and enforce a change control process.
• Perform requirements change impact analysis.
• Store requirement attributes.
• Track the status of each requirement.
• Trace requirements into designs, code, and tests.
• Store requirements in a requirements management tool.

5. Page 4Classification: Restricted
The Requirements Baseline

6. Page 5Classification: Restricted
Requirements Version Management

7. Page 6Classification: Restricted
Requirements Change Control

8. Page 7Classification: Restricted
Possible Change Request Statuses

9. Page 8Classification: Restricted
A Change Control System

10. Page 9Classification: Restricted
Change Control Board

11. Page 10Classification: Restricted
Impact Analysis for Requirements Changes-1

12. Page 11Classification: Restricted
Impact Analysis for Requirements Changes-2

13. Page 12Classification: Restricted
Impact Analysis for Requirements Changes-3

14. Page 13Classification: Restricted
Requirements Attributes

15. Page 14Classification: Restricted
Requirements Status Tracking-1

16. Page 15Classification: Restricted
Requirements Status Tracking-2

17. Page 16Classification: Restricted
Requirements Traceability

18. Page 17Classification: Restricted
• The purpose of the Requirements Traceability Matrix is to ensure that all
requirements defined for a system are tested.
• The requirements traceability matrix is usually developed in
concurrence with the initial list of requirements (functional
requirements documents)
Requirement Traceability matrix

19. Page 18Classification: Restricted
RTM Example

20. Page 19Classification: Restricted
Where Traceability Links Might Come From?

21. Page 20Classification: Restricted
Requirements Management Best Practices

22. Page 21Classification: Restricted
Thank you