Business analysts, business change specialists, systems analysts and anyone who is involved in gathering, analysing, documenting and managing requirements. Requirements Engineering is also a Core module on the BCS (ISEB) International Diploma in Business Analysis.
Requirements Engineering is a valuable tool in the hands of the expert business analyst, whatever the project or product development lifecycle. It involves drilling down past surface discussion into tacit knowledge. Teams willing to embrace effective requirements practices, pinpointing consumer expectations for a newly introduced or modified existing product, will achieve better outcomes.
Based around a Requirements Engineering framework, this course teaches a range of techniques for elicitation, analysis, documentation and managing requirements. A detailed case study used throughout the course allows you to practise each technique as you learn. Key areas include: requirements categorisation; prioritisation and documentation; traceability and management of changes to requirements and use case modelling and stories.
The course will be presented by one of our expert training consultants pictured below. Every member of our Requirements Engineering training team offers substantial experience of business analysis projects and applying Requirements Engineering techniques.
To give you an overview of what you’ll learn, here’s a quick guide to the three days of the course.
- Rationale for Requirements Engineering.
- Stakeholders in Requirements Engineering.
- Requirements planning and management.
- Interviews and workshops.
- Elicitation techniques.
- Documenting the requirements.
- Modelling the requirements.
- Organising and categorising requirements.
- Feasibility checking.
- Prioritising requirements.
- Reviewing the requirements.
- Scenarios and prototyping.
- Managing requirements.
- Validating requirements.
- Delivering the requirements.
For virtual courses a printed copy of the latest edition of the comprehensive course manual will be sent to your home address in good time for the start of your course. Our delegates tell us that having access to a physical document is beneficial as both a reference document and for taking notes during the course. In addition, a link will be emailed to you to enable you to access an electronic copy of the same comprehensive manual for convenient future reference.
Yes. During this three day course you’ll receive all the training you need to prepare for the BCS Requirements Engineering certificate examination, which is held on the final afternoon of the course. A pass means you’re another step closer to achieving the BCS International Diploma in Business Analysis – the de facto certification for practicing business analysts. One last thing this course is also approved as consistent with the IIBA BABoK version 3.0 and enables participants to develop SFIA skills BUAN and REQM.
At present, due to the Covid-19 crisis, the exam is not available in a classroom environment. However, for delegates attending a virtual or online course, the exam may be taken using the BCS online proctoring service. This exam consists of 40 multiple-choice questions with a pass mark of 25/40.
If this course is part of your BCS Diploma in Business Analysis programme you have a choice of further modules which include the other Core BA Diploma module, Business Analysis Practice. Candidates who have already completed the Core modules can take one Practitioner specialism, which includes Benefits Management and Business Acceptance, Systems Modelling Techniques, Modelling Business Processes, Systems Development Essentials or Data Management Essentials. Before taking the Oral exam, candidates must also pass one of the Foundation Specialisms; in Business Analysis, IS Project Management, Business Change or Commercial Awareness. The structure of the certification is shown here.
Requirements Engineering (a three-day course)
Rationale for requirements engineering
- Definition of a ‘requirement’ and requirements hierarchies.
- Knowledge types.
- Requirements engineering framework: linear and Agile development.
The role of the analyst
- Stakeholders in requirements engineering.
- Roles and responsibilities.
Requirements planning and management
- Planning for requirements engineering.
- The business context and business case: linear and Agile development.
- Project initiation.
- Interviews: preparing and conducting.
- Workshop: planning and facilitating; roles and responsibilities.
- Techniques to elicit information and document workshop results.
Requirements elicitation – supplementary techniques
- Observation and focus groups.
- Quantitative elicitation techniques: including surveys and document analysis.
- Scenario analysis.
- Throwaway versus evolutionary prototyping: rationale and risks.
- Suitability of elicitation techniques.
- Organising requirements.
- Ordering and refining a backlog for Agile development.
- Assessing feasibility and aligning requirements with bu.siness goals.
- Prioritising requirements using MOSCOW.
- Checking requirements against quality criteria.
- Requirements testability and defining acceptance criteria.
- Identifying and resolving requirements conflicts.
- Types and hierarchy of requirements.
- Documentation formats: user stories, use cases and requirements catalogue.
- Applicability to linear and Agile development.
- Context diagrams.
- Modelling functions: use case diagrams for scope definition/re-definition.
- Modelling data: class models.
- Cross-checking use cases against class models.
- Stakeholder responsibilities in requirements validation.
- Requirements validation in linear and Agile development.
- Requirements management in Agile development
- Change through collaboration and iteration.
- Requirements management in linear development
- Version and change control.
- Requirements traceability.
- Requirements engineering support tools.
- Requirements re-use and patterns.
Delivering the requirements
- Approaches to solution delivery.
- Linear and iterative development approaches.
- Post deployment and benefits confirmation.
©Assist Knowledge Development Ltd.