IREB CPRE Advanced Level – Requirements Management – preparation for the certification exam

Why take this course

If you hold an IREB CPRE Foundation Level certificate and want to advance your career, this training is perfect for you. You’ll explore advanced aspects of requirements management and gain the essential knowledge needed to take the Practitioner certification exam. This will provide you with a solid foundation for further professional growth and earn you a lifetime, globally recognized certificate.

What you'll learn

• You’ll be introduced to advanced requirements management practices according to the IREB standard.
• You’ll learn the principles of building a requirements information model.
• You’ll master prioritization methods, such as two-criterion classification and the 100-dollar technique.
• You’ll learn to manage requirements versions, changes, and traceability in projects.
• You’ll be introduced to methods for reporting and managing requirements engineering processes, including in Agile projects.
• You’ll prepare for the CPRE Advanced Level certification exam by learning its format and rules

Prerequisites

• Knowledge of the concepts and issues discussed in the IREB CPRE entry level syllabus;
• At least 1 year of experience in software development projects in an analyst or similar role;
• For those taking the IREB Advanced Level exam, holding the IREB CPRE Foundation Level certification.

Who is this course for

This training is intended for system and business analysts, software engineers, and system engineers. It is ideal for individuals who already hold an IREB CPRE Foundation Level certificate and are planning to advance their careers. At least one year of experience in software development projects in an analyst or similar role is required.

Training scope

Day 1

What is Requirements Management?

• Definition of Requirements Management
• Tasks in Requirements Management
• Goals and benefits of requirements management
• Requirements Management Plan
• Relevant standards

Requirements Information Model

• Basics and forms of presentation
• Creating a Requirements Information Model
• Assigning attributes and requirements views
• Goals of attribute assignment
• Using the attribute schema
• Designing the attribute schema
• Managing changes in attribute schemas
• Goals and types of views
• Defining views and associated risks
• Optimizing the attribute population and creating views

Day 2

Requirements Evaluation and Prioritization

• Principles of evaluation
• Requirements prioritization
• Ad-hoc prioritization techniques
• Two-criterion classification
• The 100-dollar technique
• Analytical prioritization techniques
• Combinations of prioritization techniques

Version and Change Management

• Requirements versioning
• Version control for requirements and requirements documents
• Requirements configuration
• Requirements baseline version
• Requirements branching
• Managing changes in requirements
• Causes, sources, and schedule for requirements changes
• Types of changes in requirements
• Analysis and documentation of requirements stability
• The change management process

Requirements Traceability

• Reasons for requirements traceability
• What requirements traceability means
• Why tracing requirements and artifacts is important
• Different traceability views
• Types of relationships for traceability relationships
• Forms of presentation for traceability relationships
• Explicit and implicit traceability documentation
• Bidirectional and unidirectional traceability relationships
• Developing a strategy for project-specific traceability
• Creating and using specific traceability models
• The process of defining a specific traceability model
• Using a specific traceability model
• Metrics for evaluating implemented traceability
• Challenges in tracing non-textual artifacts

Day 3

Managing Variants for Requirements

• Using requirements variants
• Forms of explicit documentation for variants and their evaluation
• Feature modeling

Reporting in Requirements Management

• Goals and benefits of reporting in requirements management
• Establishing a reporting system in Requirements Management
• Interfaces
• Report content
• Guidelines for developing and using reports
• The process of defining a report
• Key indicators in Requirements Engineering
• Key indicators in Requirements Management
• Deriving key indicators using the Goal-Question-Metric method
• Risks and problems associated with reporting

Managing Requirements Engineering Processes

• Requirements Engineering as a process
• Parameters of the Requirements Engineering process
• Documenting the Requirements Engineering process
• Monitoring and controlling the Requirements Engineering process
• Process improvement in Requirements Engineering

Requirements Management in Agile Projects

• Requirements Management in Agile Projects
• Mapping RM activities to activities in Scrum

Using Tools in Requirements Management

• The role of tools in Requirements Management
• Basic procedure for tool selection
• Data exchange between Requirements Management tools