Professional Training

Online course dates

The courses run as one full day (9-5) and four half (9-1) days. Monday to Friday.

Prerequisites

Participants will be expected to have reviewed Chapters 5,10,11 and 12 from the BCS publication BCS Business Analysis, Paul, Yeates & Cadle (4th Edition).

Course Objectives

On completion of the Requirement Engineering
course, delegates will be able to:
Explain The Requirements Engineering (RE) framework, and its application in a business context
Use a hierarchy of requirements
Recognise the roles and responsibilities of key stakeholders in the RE framework
Understand the use of a range of requirements elicitation techniques and their relevance to business situations
Analyse, prioritise and organise elicited requirements
Document requirements
Identify problems with requirements and explain how requirements documentation may be improved
Create a model of the features required from a system
Interpret a model of the data requirements for an information system
Describe the principles of Requirements Management and explain the importance of managing requirements
Describe the use of tools to support Requirements Engineering
Explain the process and stakeholders involved in Requirements Validation

Who should attend

This Practitioner certificate is relevant to those involved in any Requirements Engineering activities. This includes Business Analysts, Product Owners, Business Managers and their staff, Business Change Managers, Project Managers, Quality Assurance, or any stakeholder roles on business change projects who require good quality requirements.
The course is also aimed at individuals who would like to achieve the internationally recognised BCS Certificate in Requirements Engineering, on their path to achieving the BCS International Diploma in Business Analysis.

Define Requirements Approach and Project Scope

Define the term “Requirements”
Describe the Requirements Engineering framework
Factors in adapting the approach
Contents of a Project Initiation Document /Terms of Reference (ToR)

Elicit Requirements

Explain the different knowledge types
Identify a technique to articulate tacit knowledge
Explain the use, advantages and disadvantages of elicitation techniques
Identify an appropriate technique to elicit requirements
Explain the suitability of elicitation techniques for Agile and linear development approaches

Record Requirements

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 of an information system
Describe the purpose of modelling in requirements engineering
Prepare a UML use case diagram
Prepare a UML Class diagram
Explain the use of a CRUD matrix
Explain the use of prototyping to elaborate requirements

Collaborate and Communicate with Stakeholders to Clarify Requirements

Describe the responsibilities of the actors in Requirements Engineering
Describe the purpose of requirements validation
Describe the rationale for various approaches to requirements validation
Demonstrate how Agile requirements are validated
Demonstrate how formal 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
Identify techniques used to analyse Business Rules
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 approach to achieving requirements traceability
Explain the rationale for requirements management
Define the elements of requirements management and the links between them
Define 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

Exam Format

Certification is dependent on achieving the Pass Mark of 25/40 correctly answered Multiple-Choice Exam questions. The Exam is paper-based, closed-book, and has a duration of 60 minutes. Additional time is available under certain circumstances, which are outlined on the BCS website. Once you have registered for this course, the BCS Exams Office will contact you to explain how you can schedule your online exam.

Recommended Follow-on Courses

Related courses that are also needed to earn the BCS International Diploma in Business Analysis:
BCS Certificate in Business Analysis Practice
BCS Certificate in Business Analysis Foundation
BCS Certificate in Modelling Business Processes

The BCS offers you full flexibility when choosing the sequence in which you achieve these certificates. In general, we recommend that you attend the Foundation Certificate in Business Analysis after completion of the other three BCS certificates, if intending to sit the International Diploma exam. We are happy to discuss your specific training needs to advise on your optimal learning pathway.