Audience
This qualification has been designed to provide valuable learning for those in roles such as business analyst, business architect, business systems analyst, data analyst, enterprise analyst, management consultant, process analyst, product manager, product owner, project manager, and systems analyst.
This certificate provides value for candidates in entry-level, associate and management level roles.
Prerequisites
There are no prerequisites for entry to the examination.
Duration
3 Days.
Course Objectives
Upon achievement of the certificate, candidates will be able to demonstrate a practical understanding of how to:
- Collaborate with stakeholders to ensure requirements align with business objectives
- Elicit different types of requirements and the associated documentation
- Analyse and validate requirements
- Ensure and manage requirement quality and change
Course Content
Define Requirements Approach and Project Scope
Define the term “Requirements"
Describe the Requirements Engineering Framework
Explain factors to be considered in adapting the approach to requirements engineering
Describe the contents of a project initiation document (PID)/terms of reference (ToR)
Elicit Requirements
Explain different knowledge types
Identify a technique to articulate tacit knowledge
Explain the use, advantages and disadvantages of the following elicitation techniques
Identify an appropriate technique to elicit requirements
Explain the suitability of elicitation techniques for Agile and linear development approaches
Record Requirements (Documentation)
Identify and describe the categories of requirement
Explain the importance of documentation
Identify the key documentation styles
Explain the characteristics documented for requirements in a requirements catalogue
Explain the key underlying principles and standard format of a user story
Build Models and Prototypes to Represent the Requirements
Explain the rationale for modelling the functional requirements (processing and data) of an information system
Describe the purpose of modelling in requirements engineering
Explain the use of a CRUD matrix
Collaborate and Communicate with Stakeholders to Clarify Requirements
Describe the responsibilities of the actors (stakeholder roles) in Requirements Engineering
Describe the purpose of requirements validation
Describe the rationale for various approaches to requirements validation, informal and formal review
Demonstrate how Agile requirements are validated
Analyse, Prioritise and Assure the Quality of Requirements
Explain the purpose of analysing requirements
Apply the MoSCoW technique to prioritise requirements
Interpret individual requirements - applying filters and quality criteria
Identify the purposes of Slicing Requirements (Agile/Linear)
Identify techniques used to analyse Business Rules
Constraints
Operational Guidance
Data models
CRUD matrices
Activity diagrams
Business process models
Explain the importance of testability
Conduct User analysis and Profiling
Describe techniques used to analyse roles
Explain the purpose of a Customer Journey Map
Requirements Management and Traceability
Explain the rationale and the approach to achieving requirements traceability
Explain the rationale for requirements management
Define the elements of requirements management and the links between them
Explain the use of a change control process
Describe the elements of a version control process
Explain the use and advantages of different forms of traceability