BCS Certificate in Requirements Engineering
The requirements engineering training course follows the official BCS syllabus for Requirements Engineering that leads to BCS accredited examination. There are no prerequisites to attending the course - it is intended for people needing to develop their understanding of requirements engineering.
Requirements Engineering Course
The course uses trainers with real world experience to ensure that delegates receive practical information that will be usable immediately on requirements projects and improving requirements engineering processes.
The format of the exam is a one hour, open book written exam, based on a business scenario. The pass mark is 50%.
Requirements Engineering Course Outline
Session 1 - Introduction to Requirements Engineering
The session proposes a working definition of a requirement and considers the essence and origin of requirements in a business context. A framework for managing requirements process is provided.
Session 2 - Hierarchy of Requirements
The session provides an approach to structuring requirements. Starting from business goals we consider types of requirement and different levels of detail for requirements.
Session 3 - Stakeholders in the Requirements Process
Stakeholders are the owners of the business problems and opportunities giving rise to the need for requirements. It is essential that they are identified and involved throughout the requirements project from elicitation to testing. This session considers how to identify and involve the different types of stakeholder who are relevant to a project.
Session 4 - Requirements Elicitation
The session examines various types of elicitation techniques and the context in which they are to be applied. We also provide real-world practical guidance in how to use the technique to gain maximum advantage from it.
Session 5 - Use of Models in Requirements Engineering
Models can be a vital element in eliciting, analysing and documenting requirements. They can also be a precursor to creating prototypes in order for the requirements analyst and for the business stakeholder to agree what is really needed. This session considers modelling of process and of data.
Session 6 - Requirements Documentation
The session relates documentation to the purpose of the requirements, demonstrating that one size does not suit all situations. We consider forms of documentation from the informal to the formal and provide guidelines for determining an approach that is right free given situation.
Session 7 - Requirements Analysis
Requirements must be analysed to ensure that they are well formed, that they represent what the business needs and that they are usable by the developers and testers of the intended product. This session shows how.
Session 8 - Requirements Validation
It is essential to review and validate requirements to ensure that they are fit for purpose. This session considers some approaches based around requirements reviews.
Session 9 - Requirements management
If requirements are not properly managed and controlled, the value of all other requirements activities is likely to be reduced or nullified. This session considers approaches to version control, management of scope and traceability. We also consider the use of software tools to support the requirements process.