Course Overview
Requirements Engineering is an essential business analysis skill. Being able to pinpoint your consumers’ expectations for a newly introduced or modified existing product is key to the success of the completed solution.
Based around a Requirements Engineering framework, this course will teach you a range of techniques for elicitation, analysis, documentation, and managing requirements. All with the help of a detailed case study that allows you to practice applying the techniques you learn. Some of the key areas we’ll look at include requirements categorization, prioritization and documentation, traceability and management of changes to requirements, and use case modelling and stories.
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. Through a given business scenario, this open-book exam puts your knowledge of Requirements Engineering techniques to the test.
What you’ll learn
All with the help of a detailed case study that allows you to practice applying the techniques you learn. Some of the key areas we’ll look at include requirements categorization, prioritization and documentation, traceability and management of changes to requirements, and use case modelling and stories.
Target audiences
- The course is designed mainly for practising business analysts but is also suitable for others such as business change practitioners, project managers and enterprise architects who wish to gain an insight into this aspect of the business analysis process.
Curriculum
- 1 Section
- 11 Lessons
- 3 Days
- Topics11
- 1.1Rationale for requirements engineering Definition of a ‘requirement’ and requirements hierarchies Knowledge types Requirements engineering framework: linear and Agile development
- 1.2The role of the analyst Stakeholders in requirements engineering Roles and responsibilities
- 1.3Requirements planning and management Planning for requirements engineering The business context and business case: linear and Agile development Project initiation
- 1.4Requirements elicitation Interviews: preparing and conducting Workshop: planning and facilitating; roles and responsibilities Techniques to elicit information and document workshop results
- 1.5Requirements 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
- 1.6Requirements analysis Organising requirements Ordering and refining a backlog for Agile development Assessing feasibility and aligning requirements with business goals Prioritising requirements using MOSCOW Checking requirements against quality criteria Requirements testability and defining acceptance criteria Identifying and resolving requirements conflicts
- 1.7Documenting requirements Types and hierarchy of requirements Documentation formats: user stories, use cases and requirements catalogue Applicability to linear and Agile development
- 1.8Modelling requirements Context diagrams Modelling functions: use case diagrams for scope definition/re-definition Modelling data: class models Cross-checking use cases against class models
- 1.9Requirements validation Stakeholder responsibilities in requirements validation Requirements validation in linear and Agile development
- 1.10Requirements management 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
- 1.11Delivering the requirements Approaches to solution delivery Linear and iterative development approaches Post deployment and benefits confirmation
Instructor
