Description

Description

Achieving the BCS Certificate in Requirements Engineering demonstrates your capability to enhance project delivery through superior requirements management. This course provides a comprehensive framework for requirements engineering, covering the entire lifecycle from developing the business case to delivering well-documented and well-structured requirements. High-quality requirements are pivotal in ensuring the successful delivery of top-notch products and projects.

Moreover, successful completion of this course prepares you to sit for the BCS Requirements Engineering exam upon completion.

Training Objectives

• Link requirements backward to the business case and forward to the delivered product
• process or service.
• Identify the roles and responsibilities of key stakeholders in the requirements engineering process.
• Describe the use of tools to support Requirements Engineering.
• Apply the Requirements Validation process.

Course Outline

• Module 1: Introduction to Requirements Engineering<br />
• Framework for Requirements Engineering<
• Identifying the Requirements Engineering rationale<br />
• Planning and estimating requirements<br />
• Identifying the business rationale and inputs<br />
• Crafting the business case<br />
• Creating the Terms of Reference or Project Initiation Document (PID)<br />
• Building the Requirements<
• Categorizing requirements within the hierarchy<br />
• General business requirements, including legal and business policy<br />
• Technical policy requirements<br />
• Functional requirements<br />
• Non-functional requirements<br />
• Stakeholders in the Requirements Process<
• Project Stakeholders<br />
• Business Stakeholders<br />
• External stakeholders<
• Module 2: Requirements Elicitation<br />
• Types of knowledge<
• Explicit knowledge and ignorance<br />
• Identifying tacit knowledge and ignorance<br />
• Eliciting requirements from stakeholders<
• Planning elicitation meetings<br />
• Choosing the right people to interview<br />
• Applying elicitation techniques<
• Selecting the best interview methodology<br />
• Constructing questions that deliver results<
• Module 3: Requirements Engineering Modeling Techniques<br />
• Why model requirements?<
• Generating questions<br />
• Defining business rules<br />
• Cross-checking for consistency and completeness<br />
• Modeling the business context for the system<
• Developing a model to represent system processing requirements<br />
• Interpreting a data model<
• Module 4: Documenting Your Requirements<br />
• Documentation styles and levels of definition<
• Writing standard requirements<br />
• Employing user stories and use cases<br />
• Creating a Requirements Catalog<
• Identifying necessary attributes<br />
• Writing a requirements description<br />
• Non-functional requirements<
• Module 5: Requirements Analysis<br />
• Prioritizing and packaging requirements for delivery<
• Analyzing and prioritizing business needs<br />
• Allocating requirements<br />
• Organizing requirements<
• Optimizing business value<br />
• Evaluating dependencies between requirements<br />
• Ensuring well-formed requirements<
• Removing overlapping requirements<br />
• Identifying and negotiating conflicts between requirements<br />
• Removing ambiguity<br />
• Ensuring feasibility and testability<br />
• Prototyping requirements<br />
• Verifying requirements<
• Module 6: Validating Requirements<br />
• Applying validation skills<
• Selecting the best validation methods<br />
• Validation checklists<br />
• Types of reviews<
• Reviews, walk-throughs and inspections<br />
• Stakeholders and their areas of concern<
• Module 7: Requirements Management<br />
• Dealing with changing requirements<
• Types of changes<br />
• Frequency and magnitude of changes<br />
• The importance of traceability<
• Vertical traceability (to business objectives)<br />
• Horizontal traceability (from origin to deliver)<br />
• Traceability and ownership