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.
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.
This course is recommended for people who already have some experience in gathering and documenting requirements and who need to formalise their skills. Typical attendance includes:
Current and prospective Business Analysts looking to improve their hands-on requirements engineering skills.
Business Analysts looking to accredit their skills for recognition among employers, clients and peers.
BAs of any level looking to achieve the BCS International Diploma in Business Analysis.
Anyone seeking an understanding of what constitutes quality requirements
This course is not recommended for people with no previous experience. If you are a new business analyst or you would like to become a business analyst we recommend our Fundamentals of Business Analysis training course, which provides more in-depth training covering the complete role of the business analyst.
Upon completion of the course
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
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
Attendance on the Business Analysis Foundation course or equivalent knowledge and experience.
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.
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'
Knowledge types – tacit and non-tacit.
Observation - formal/informal, shadowing.
Special purpose records.
Understanding the applicability of techniques.
Use of Models in Requirements Engineering
The purpose of modelling requirements:
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.
Documentation styles and levels of definition.
Prioritising and packaging requirements for delivery.
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.