Practitioner in Requirements Engineering - Self-paced

Course subjects

1. Define Requirements Approach and Project Scope

• Defining requirements and understanding their role in business change

• The Requirements Engineering Framework and its application

• Factors influencing the requirements approach and project scope

• Understanding Project Initiation Documents (PID) / Terms of Reference (ToR)

2. Elicit Requirements

• Understanding tacit vs explicit knowledge

• Techniques for eliciting tacit knowledge: Observation, Storytelling, Prototyping

• Key elicitation techniques:

  • Interviews, Workshops, Document Analysis, Prototyping

• Choosing the right elicitation technique for Agile and Linear projects

3. Record Requirements (Documentation)

• Categories of requirements: Business vs Solution (Functional and Non-functional)

• The role of documentation in maintaining consistency and traceability

• Text-based and diagrammatic documentation styles

• Using a Requirements Catalogue and User Stories for effective documentation

4. Build Models and Prototypes to Represent Requirements

• The role of modelling in requirements engineering

• Preparing UML Use Case Diagrams and Class Diagrams

• Using a CRUD Matrix for data requirements

• Prototyping to elaborate and validate requirements

5. Collaborate and Communicate with Stakeholders to Clarify Requirements

• Identifying key stakeholder roles in Requirements Engineering

• Understanding the requirements validation process

• Formal vs informal requirements validation approaches

• Validating requirements in Agile and Waterfall environments

6. Analyse, Prioritise, and Assure the Quality of Requirements

• Applying the MoSCoW technique for prioritisation

• Using filters and quality criteria (INVEST, clarity, consistency, relevance)

• Techniques for business rules analysis

• Ensuring requirements are testable and align with business goals

7. Conduct User Analysis and Profiling

• Techniques for user role analysis and persona creation

• The purpose of Customer Journey Mapping

• How user analysis supports requirement validation and solution design

8. Requirements Management and Traceability

• The importance of requirements traceability

• Key elements of requirements management:

  • Identification, Ownership, Change Control, Version Control

• Approaches to horizontal and vertical traceability

• Implementing change control processes