Requirements Engineering

4 days


This course has been independently developed but follows the BCS Requirements Engineering syllabus. Course fees do not include the BCS examination. This course is concerned with one of the major areas of business analysis work which is producing a well-organised and clearly-defined set of requirements. The course is structured around a five part framework for Requirements Engineering which is applied to a project initiated by an approved business case. The five elements of the framework are Requirements Elicitation, Requirements Analysis, Requirements Validation, Requirements Documentation and Requirements Management.

At the end of the course, delegates should be able to:

  • Explain the importance of linking requirements to the business case.
  • Describe the roles and responsibilities of key stakeholders in the requirements engineering process.
  • Explain the use of a range of requirements elicitation techniques and the relevance of the techniques 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.


Anyone requiring an understanding of requirements engineering, including business analysts, business managers and their staff, business change managers and project managers.

Skills Gained

  • Describe the roles and responsibilities of key stakeholders in the requirements engineering process
  • Demonstrate the application of a range requirements elicitation techniques
  • Explain the use of requirements elicitation techniques and the relevance of the techniques to given situations
  • Document and prioritise user requirements for an information system
  • Identify problems with requirements and explain how requirements documentation may be improved
  • Create a process/function model of requirements for an information system interpret a model of the data requirements for an information system
  • Explain the importance of linking project objectives and requirements to the Business Case
  • Describe the principles of Requirements Management and explain the importance of managing requirements
  • Describe the use of CASE tools to support Requirements Engineering
  • Explain the principles of Requirements Validation and define an approach to validating requirements


There are no specific pre-requisites for this course. This course is for those wishing to acquire the skill set required for establishing system requirements and those wishing to attain the BCS Business Systems Development Certificate in Requirements Engineering.

Course Outline

  • Introduction to Requirements Engineering
  • Framework for requirements engineering:
  • The business rationale and inputs.
  • Hierarchy of Requirements
  • Building the hierarchy through decomposition of requirements.
  • Categories of requirements within the hierarchy:
  • General business requirements, including legal and business policy.
  • Technical policy requirements.
  • Functional requirements.

Non-functional requirements, including performance, usability, access, security, archiving, back up and recovery, availability, robustness.

  • Stakeholders in the Requirements Process
  • The definition of the term'stakeholder'
  • Project Stakeholders.
  • Business Stakeholders.
  • .
  • Requirements Elicitation
  • Knowledge types – tacit and non-tacit.
  • Elicitation techniques:
  • Interviews.
  • Workshops.
  • Observation - formal/informal, shadowing.
  • Focus groups.
  • Prototyping.
  • Scenarios.
  • Document analysis.
  • Special purpose records.


Understanding the applicability of techniques.

  • Use of Models in Requirements Engineering
  • The purpose of modelling requirements:
  • Generating questions.
  • Cross-checking for consistency and completeness.

Defining business rules.

Modelling the business context for the system using a context diagram that identifies the inputs and outputs of the system.

Developing a model to represent the system processing requirements - use case diagram.

Interpreting a data model based upon the system data requirements - class diagram.

  • Requirements Documentation
  • Documentation styles and levels of definition.
  • Requirements catalogue.
  • Requirements document.
  • Requirements Analysis
  • Prioritising and packaging requirements for delivery.
  • Organising requirements:
  • Requirements filters.

Characteristics of a good requirement.

Prototyping requirements.

Verifying requirements.

  • Requirements Validation
  • Agreeing the requirements document.
  • Types of reviews:
  • Informal reviews.
  • Structured walkthroughs (author-led review).
  • Technical reviews.


Stakeholders and their areas of concern.
  • Requirements Management
  • Dealing with changing requirements.
  • The importance of traceability:
  • Vertical traceability (to business objectives).

Horizontal traceability (from origin to deliver).

Traceability and ownership.

Requirements engineering support tools.

Thinking about Onsite?

If you need training for 3 or more people, you should ask us about onsite training. Putting aside the obvious location benefit, content can be customised to better meet your business objectives and more can be covered than in a public classroom. It's a cost effective option.

Submit an enquiry from any page on this site, and let us know you are interested in the requirements box, or simply mention it when we contact you.

Upcoming Dates

  • GREEN This class is Guaranteed To Run.
  • SPVC - Self-Paced Virtual Class.
  • Click a Date to Enroll.
Course Location Days Cost Date
Onsite4 2000 £2000 2019-05-25