Improved requirements management means improved project delivery. Earning the BCS Certificate in Requirements Engineering shows you have the knowledge and expertise to deliver high-quality, mission-critical products and projects.
This BCS Requirements Engineering course presents an end-to-end requirements engineering framework. From the business case to the delivery of well-documented and well-formed requirements, high-quality requirements are crucial to delivering quality products. In addition, this course prepares you to take the BCS Requirements Engineering exam at the end of the course.
- Experience at the level of:
- Course 211, Business Analysis Introduction: Defining Successful Projects, or
- Course 3507, BCS Foundation Certificate in Business Analysis
- One hour, ‘open book’
- Written, based on a business scenario
- Pass mark is 50%
- If any special testing adjustments should be considered, please contact Customer Service at least two weeks before the event
- International Diploma in Business Analysis
- The BCS, The Chartered Institute for IT, offers this internationally recognised certification, enabling you to take your skills around the world. The four modules required to apply for this certification include one foundation level course, and three practitioner level courses:
- Upon passing your exam, BCS will contact you to activate your membership. Once activated you will be a BCS Associate Member and will have access to the wealth of benefits and support to help you in your career.
- BCS Associate membership provides exclusive access to resources, content and opportunities that will enrich your career.
- Note: This offer is only available once to each exam candidate. Exam candidates who have previously benefited from free Associate Membership will not be eligible for this offer again even if you have taken another qualifying BCS exam.
BCS Certificate in Requirements Engineering Training Delivery Methods
- Train your whole team by bringing this course to your facility
BCS Certificate in Requirements Engineering Training Course Benefits
Link requirements backwards to the business case and forwards to the delivered product, process or serviceIdentify the roles and responsibilities of key stakeholders in the requirements engineering processDescribe the use of tools to support Requirements EngineeringApply the Requirements Validation process
Requirements Engineering Course Outline
Framework for Requirements Engineering
- Identifying the Requirements Engineering rationale
- Planning and estimating requirements
- Identifying the business rationale and inputs
- Crafting the business case
- Creating the Terms of Reference or Project Initiation Document (PID)
Building the Requirements
- Categorising requirements within the hierarchy
- General business requirements, including legal and business policy
- Technical policy requirements
- Functional requirements
- Non-functional requirements
Stakeholders in the Requirements Process
- Project Stakeholders
- Business Stakeholders
- External stakeholders
Types of knowledge
- Explicit knowledge and ignorance
- Identifying tacit knowledge and ignorance
Eliciting requirements from stakeholders
- Planning elicitation meetings
- Choosing the right people to interview
Applying elicitation techniques
- Selecting the best interview methodology
- Constructing questions that deliver results
Why model requirements?
- Generating questions
- Defining business rules
- Cross-checking for consistency and completeness
Modelling the business context for the system
- Developing a model to represent system processing requirements
- Interpreting a data model
Documentation styles and levels of definition
- Writing standard requirements
- Employing user stories and use cases
Creating a Requirements Catalogue
- Identifying necessary attributes
- Writing a requirements description
- Non-functional requirements
Prioritising and packaging requirements for delivery
- Analysing and prioritising business needs
- Allocating requirements
Organising requirements
- Optimising business value
- Evaluating dependencies between requirements
Ensuring well-formed requirements
- Removing overlapping requirements
- Identifying and negotiating conflicts between requirements
- Removing ambiguity
- Ensuring feasibility and testability
- Prototyping requirements
- Verifying requirements
Applying validation skills
- Selecting the best validation methods
- Validation checklists
Types of reviews
- Reviews, walk-throughs and inspections
- Stakeholders and their areas of concern
Dealing with changing requirements
- Types of changes
- Frequency and magnitude of changes
The importance of traceability
- Vertical traceability (to business objectives)
- Horizontal traceability (from origin to deliver)
- Traceability and ownership
