CPRE study guide
CPRE · Work through your exam, one topic at a time.
The CPRE (Certified Professional for Requirements Engineering) is a certification programme offered by IREB e.V., the International Requirements Engineering Board, an independent non-profit organisation that develops certification programmes for requirements engineering and digital design. According to IREB, the CPRE training content teaches candidates how to handle requirements in a targeted and confident way, in both classic and agile environments, and the certificate is recognised worldwide. IREB reports 1,200 trainings per year across 106 countries and 95,000 certificates issued, which reflects how widely the credential is used in hiring and project staffing. The CPRE is aimed at professionals who elicit, document, model, validate and manage requirements - business analysts, systems and software engineers, product owners, project managers and testers moving into a requirements role. The exam tests understanding of the requirements engineering process, stakeholder involvement, requirements documentation and specification techniques, modelling, quality criteria, validation and verification, and requirements management including traceability and change handling; IREB also positions the material for agile contexts. Preparation typically combines a training course from a recognised training provider with self-study of the CPRE syllabus, using worked examples and practising the terminology so you can apply concepts to scenario-based questions rather than just recall definitions. Topics on this exam: Requirements Engineering (CPRE training content; official domain breakdown not stated in source). The CPRE study guide has 1 section and about 491 words.
01Requirements Engineering (CPRE foundation content)
This section covers the domain this exam names: Requirements Engineering at CPRE foundation level. Items test whether you can separate requirement types, select an elicitation technique that fits the situation, judge documentation against quality criteria, and explain how requirements are controlled once a baseline exists. A requirement is a need perceived by a stakeholder plus its documented representation; the need and the document are not the same artefact. Stakeholder requirements state what a stakeholder needs in their working context; system requirements state what the system must provide at its boundary.
491 words, about 2 minMore study resources for CPRE
- Practice questionsIn requirements engineering, which characteristic distinguishes a requirement from a mere wish or goal statement?
- FlashcardsRequirement. A statement describing a capability or property that a system must have, or a condition it must satisfy, derived from stakeholder needs and expressed so it can be verified.
- Cheat sheetFour core activities per IREB/CPRE framing: elicitation, documentation, validation and negotiation, and management (change plus traceability); each activity runs iteratively, not once in sequence.
- Key termsStakeholder. A person or group with an interest in a system because they affect it, are affected by it, or depend on it to meet their own goals and responsibilities.
- Study planDefine requirements engineering in your own words and distinguish it from project management, design, and testing, citing at least three boundary criteria.
- Common mistakesCandidates often arrive from PMP, agile, or product-owner backgrounds and default to familiar process language; the CPRE syllabus is narrower and more definitional, with specific terms for elicitation, documentation, validation, and management that do not map onto generic PM vocabulary.
- Exam-day guideBring the original, unexpired ID that exactly matches the name on your exam registration.