Requirements engineering course teaching how to capture and document high-quality requirements by means of a systematic process. Delegates learn key techniques for eliciting, analysing, documenting, validating, and managing requirements.
Statistics show that on average 71% of projects fail or are challenged (miss deadline, exceed budget or don’t deliver to specification) depending on industry sector.
Capturing and documenting high-quality requirements has been proven to reduce project failure more than any other single element in the business-project life-cycle. Whether you are developing your product internally, or putting the specifications out to tender, high-quality requirements documentation will save you money, time and sub-optimal implementations.
Our Requirements engineering course is ideal for anyone who wishes to understand the issues around requirements, and improve the quality of the requirements they produce. Typical delegates include:
- Business analysts.
- Management, including project managers, program managers and portfolio managers.
- Testing, development and procurement teams.
Delegates learn how to:
- Cover all potential needs by applying a wide range of elicitation techniques.
- Effectively analyse your elicited requirements by using a range of modelling and prioritisation techniques.
- Clearly document your requirements as questions, statements, use cases or user stories.
- Structure your requirements to reflect the needs of your stakeholders.
- Convey requirements in a clear, concise and engaging manner.
- Employ a range of templates for each method of requirements documentation.
- Use configuration management and change control to ensure the quality of your requirements.
This course teaches a systematic requirements process based on best practice recommendations from the International Institute of Business Analysis (IIBA), the British Computer Society (BCS), and the Software Engineering Body of Knowledge (SWEBOK).
Requirements engineering training is available on-request only, i.e. one-to-one training or a ‘closed’ course for your group. We don’t currently offer scheduled (public) Requirements engineering courses. This approach means that we can tailor your training to your exact business needs. The course is structured so that your proposals can be integrated into the course flow.
We can host the training at one of our centres, or your venue anywhere in the UK.
The standard course duration is three days, but we offer the option of a cut-down, two-day course focusing on the topics that are most important to you.
Requirements engineering courses are hosted by highly experienced instructors, who have held senior authoring/writing roles in business. For further details, see Expert trainers.
How will I learn?
Training combines lecture, demonstration and hands-on practice.
Exercises provide activity-based experience and help build delegates’ confidence writing requirements. These exercises can be tailored to deal with issues specific to your business.
You have ample opportunity to discuss specific requirements with the trainer.
Training guide and certificate
Course delegates receive:
- A training guide, to refer to throughout the course and to use as a refresher back in the work-place.
- Job aids and roadmaps to use post-course.
- An e-certificate confirming successful course completion. Click here to see an example of the certificate you receive.
After course support
Following Requirements engineering training, delegates are entitled to 30 days’ email support from their trainer to help with any post-course issues. For further details, see Support.
Standard course times are 9.30am–4.30pm.
As we’d be hosting this course for you/your group, there’s usually flexibility to change these to suit you, e.g. start or end 30 minutes earlier or later.
Payment for requirements engineering training training can be made bank transfer or card. View training course payment options.
We accept purchase orders from UK-registered companies.
Cancellations and postponements
If an on-request Requirements engineering course booking is cancelled giving less than 20 working days’ notice, a cancellation fee is payable. View cancellation terms.
If an on-request Requirements engineering course booking is postponed giving less than 20 working days’ notice, a postponement fee is payable. View postponement terms.
Terms and conditions
Requirements engineering courses are hosted by Peter Dillon-Parkin and Crow Dillon-Parkin.
Peter has thirty years’ experience in the IT industry in roles that have included Programmer, Author, Trainer, Business Analyst, Senior Manager and Education Management Consultant.
Peter’s technical authoring career began when, as a systems manager, he was asked to write a portable data terminal manual for sales reps. The reps learned how to use the new equipment, and Peter had found his niche.
He has written, designed and project-managed everything from printed manuals and technical specifications to online help and computer-based training materials, specialising in writing for an international audience. An expert in document automation and information re-purposing, he uses templates to avoid endlessly reinventing the wheel when producing documents.
Peter develops and teaches a wide range of technical and business writing training courses. Clients for whom Peter has recently consultancy services and training to include Learning Tree International, The Guardian, Canon Europe, the BBC, the MoD and the UN.
Crow has thirty years’ experience in technical authoring, and writing for business in the wider sense.
Her love of language, combined with a natural pickiness and attention to detail, has been put to good use in a variety of editing, writing, management and training roles.
Crow is a highly-experienced learning specialist who believes strongly in empowering authors through training. Clients for whom she has developed and delivered technical and business communication skills training include FW Pharma Systems, the Open College, the BBC, and Fitness First.
Crow has two degrees and a Certificate in Education. She is currently working on a range of books based on the writing courses she has developed.
- What are requirements?
- Why do we need requirements?
- Where do we use requirements
- The business analysis process model
The requirements engineering process
Activity: elicit a requirement
This activity focuses on eliciting a requirement from a member of another team, and documenting it. This will prove to be surprisingly difficult to do accurately, as people have a tendency to say what they want, but not necessarily what metrics they will judge it by, or any of the non-functional (quality) elements of the requirement. This will give us a basis for understanding what we mean by “high-quality.”
Eliciting high-quality requirements
- What did we miss?
- Functional versus non-functional requirements
- Tacit knowledge and ignorance
- Interviews and workshops
- Quantitative analysis
- Document analysis
Investigation techniques to elicit tacit knowledge
- Ethnographic studies
- Protocol analysis
Activity: identifying your stakeholders
This activity focuses on identifying typical project stakeholders with all the problems and issues that come with them. This will give us a basis for understanding how we work with stakeholders.
Working with stakeholders
- The Stakeholder Communication Model
- Conducting interviews, workshops, and focus groups
- Common areas:
- Serial summarisation
- The interview process
- Tools and techniques for requirements workshops
- Divergent and convergent thinking
- VAKOG – maximizing audience attention
- Brainstorming, brain writing, affinity diagramming
- Using prototypes to elicit emergent needs
Analysing the elicited requirements
- Creating use case diagrams
- Modelling the “as-is” and “to-be” processes
- Prioritisation by value or for delivery
- Prioritisation using time boxing
- Checking value with value stream mapping
Activity: analysing elicited requirements
This activity will use case diagrams, and an example request from the business user, to analyse how many things the business user is asking for, and how they might be best documented.
Activity: modelling the “as-is” process
Creating a cross-functional process map
This activity focuses on creating a cross functional process map from a given description of a process to note where there are problems – missing functionality, disconnects, bottlenecks – or time issues that we need to take note of.
The Requirements Documentation Model
- Using questions: requirements in requests for information
- The formal approach: requirements as statements
- Using formal and informal (agile) approaches: Iterating with use cases
- The fully agile approach: user stories
- Selecting how to document your requirements
Using requirements templates to fast-track requirements documentation
- Formal templates
- Agile templates
Activity: documenting requirements
Creating written requirements for your “to-be” process.
This activity focuses on using the cross-functional process map developed earlier in the course as a source of requirements to be documented. Each team will use the different methods and templates from the Requirements Documentation Model.
Verifying requirements quality
- What can we check?
- Verifying requirements by class of requirement
- Using ISO/IEC/IEEE 29148 as a standard for well-formed requirements
- Converting use cases into test scripts
Activity: checking your requirements
In this activity, we will use the requirements generated in the previous segment of the course to apply the methods discussed in Verifying Requirements Quality. Depending on the type of documentation method that each group has decided to use for their requirements, different problems will emerge, which is exactly what this stage of the process is intended to identify.
Activity: working with your own documents
In this activity we work with the students to deal with real world problems that usually surface after the requirements are documented, focusing on whether requirements are:
- Implementation independent
- Clear and concise
Validating the requirements
- Validation methods and techniques
- Signing off the baselined requirements
The Requirements Management Model
- Introducing configuration management
- The value of traceability in the management model
- Implementing a Change Control Board (CCB)
- Assessing impact and cost of requirements changes
- Delivering the requirements documentation