Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by ISQI
Exam Format
Registration
Validity
Skills this practice test covers
- Classify a requirement as a functional requirement, a quality requirement or a constraint.
- Write user stories with a phrase template and use cases with a form template.
- Specify data with a UML class diagram and a business process with a UML activity diagram.
- Choose elicitation techniques with the Kano model in mind, and resolve conflicts between stakeholders.
- Configure a requirements engineering process as linear or iterative, prescriptive or explorative, and customer-specific or market-oriented.
- Manage requirements with life cycle states, versions, baselines, traceability and prioritization.
Explore related topics
IREB-IT-CQ03 exam content
7 domains · 54 topics · 226 of 230 questions sorted by domain
Introduction and Overview of Requirements Engineering8 questions
This chapter sets out what RE is, why it adds value and where requirements occur. It separates functional requirements, quality requirements and constraints, and it names typical symptoms of inadequate RE, such as missing, unclear or incorrect requirements.
Skills tested
- Sort requirements into system, stakeholder, user, domain and business requirements.
- Name the major RE tasks: elicitation, documentation, validation and management.
- Explain the value of RE, such as a lower risk of developing the wrong system.
- Describe the Requirements Engineer as a role that business analysts, product owners and developers can play.
Questions by topic
- Remember the fundamental terminology (L1)2
- Enumerate symptoms of inadequate RE (L1)2
- Understand the different kinds of requirements (L2)4
Fundamental Principles of Requirements Engineering30 questions
IREB lists nine principles that apply to every RE task, from value-orientation to systematic and disciplined work. Candidates name each principle and explain why it matters, for example why non-validated requirements are useless.
Skills tested
- Recite the nine principles with the short statement that goes with each one.
- Explain why the value of a requirement is its benefit minus the cost of handling it.
- Separate problems, requirements and solutions when thinking, communicating and documenting.
- Name what enables shared understanding, such as mutual trust, and what blocks it, such as high team turnover.
- Balance the two goals of the evolution principle: permit requirements to change and keep them stable.
Questions by topic
- Context: Systems cannot be understood in isolation (L2)5
- Value-orientation: Requirements are a means to an end (L2)4
- Problem – Requirement – Solution: An inevitably intertwined triple (L2)4
- Innovation: More of the same is not enough (L2)3
- Evolution: Changing requirements are no accident, but the normal case (L2)3
- Systematic and disciplined work: We can't do without in RE (L2)3
- Shared understanding: Successful systems development is impossible without a common basis (L2)5
- Validation: Non-validated requirements are useless (L2)3
Work Products and Documentation Practices73 questions
IREB gives this chapter the most teaching time, and several of its objectives ask candidates to apply the material. Candidates write requirements in natural language and with templates, read and draw simple UML models, and check work products against quality criteria such as unambiguous and verifiable.
Skills tested
- Write an individual requirement and a user story with a phrase template, and a use case with a form template.
- Specify a domain with a UML class diagram and a business process with a UML activity diagram.
- Avoid natural-language pitfalls such as incomplete conditions, unspecific nouns and careless universal quantifiers.
- Tell temporary, evolving and durable work products apart by their life span.
- Build and maintain a glossary that marks synonyms and avoids homonyms.
Official topics
- Work Products in Requirements Engineering
- Natural-Language-Based Work Products
- Template-Based Work Products
- Model-Based Work Products
- Glossaries
- Requirements Documents and Documentation Structures
- Prototypes in Requirements Engineering
- Quality Criteria for Work Products and Requirements
Practices for Requirements Elaboration41 questions
This chapter is about finding requirements and reaching agreement on them. Candidates identify stakeholders, documents and systems as sources, choose elicitation techniques with the Kano model in mind, resolve conflicts and validate the results.
Skills tested
- Determine the system boundary and write a stakeholder list with roles, relevance and availability.
- Pick gathering techniques or design and idea-generating techniques to suit the situation.
- Identify a conflict type, such as a data, interest or value conflict, and choose a resolution technique.
- Validate requirements with walkthroughs, inspections or exploratory techniques such as A/B testing.
Questions by topic
- Resolving Conflicts regarding Requirements (L2)4
- Elicitation of Requirements (L2)5
- Validation of Requirements (L2)5
- Sources for Requirements (L3)3
- Understand how to choose a proper elicitation technique for a given situation (L2)3
- Remember the different types of conflict (L1)3
- Understand how to apply appropriate techniques for requirements validation (L2)5
- Remember the relevant sources for the system to be created (L1)2
- Identify stakeholders and write a stakeholder list (L3)4
- Understand why requirements documents need to be validated (L2)3
- Understand how to apply appropriate conflict resolution techniques (L2)3
- Understand how the Kano model can help to elicit the right requirements (L2)1
Process and Working Structure20 questions
No single RE process fits every project, so candidates learn to configure one. They analyze the influencing factors, then decide along three facets: linear or iterative, prescriptive or explorative, and customer-specific or market-oriented.
Skills tested
- Analyze influencing factors such as stakeholder availability and the volatility of requirements.
- Match a project to a participatory, contractual or product-oriented RE process.
- Follow the five steps for configuring an RE process, from influencing factors to practices.
Questions by topic
- Configuring a Requirements Engineering Process (L3)3
- Requirements Engineering Process Facets (L2)5
- Influencing Factors (L2)2
- For simple system and development settings, select and apply an appropriate RE process configuration (L3)6
- Understand the steps for configuring an RE process (L2)2
- Understand how and why these factors are influencing (L2)2
Management Practices for Requirements44 questions
Requirements management keeps existing requirements usable for every role in a project. The chapter covers life cycle management, version control, configurations and baselines, attributes and views, traceability, handling change and prioritization.
Skills tested
- Explain why each work product needs a life cycle model with allowed states and transitions.
- Tell a requirements configuration from a baseline, which is stable and change-controlled.
- Combine selective, projective and aggregating views to report on requirements.
- Route a change through a Change Control Board in a linear approach, or through the product backlog in an iterative one.
- Follow the steps for prioritization, from goals and assessment criteria to the chosen technique.
Questions by topic
- Traceability (L1)3
- Life Cycle Management (L2)6
- Attributes and Views (L2)4
- Configurations and Baselines (L1)2
- Handling Change (L1)3
- Prioritization (L1)3
- Know how to handle changes in linear (plan-driven) and agile approaches (L1)3
- Explain what an appropriate set of attributes for requirements looks like in a given project situation (L2)3
- Know the reason for prioritization and know meaningful assessment criteria (L1)3
- Explain the purpose of views and name the different views of requirements (L2)3
- Name reasons for requirements traceability (L1)3
- Explain why requirements work products need a status/life cycle model (L2)2
- Know the use of requirements configurations and baselines (L1)4
- Name different categories of prioritization techniques (L1)2
Tool Support10 questions
The shortest chapter covers RE tools: what they support and how to introduce one. Tools rarely cover every RE activity, so candidates first decide which tasks a tool should support.
Skills tested
- Sort tools by what they support: requirements management, the RE process or documentation of knowledge.
- Plan a tool introduction with pilot projects, defined evaluation criteria and instruction for staff.
- Count all life cycle costs of a tool, not only the license costs.
Questions by topic
- Introducing Tools (L2)2
- Tools in Requirements Engineering (L1)3
- Explain what to consider when introducing RE tools (L2)5
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: a basic knowledge of system development in plan-driven and agile approaches.
- Recommended: some experience in software development, systems engineering or business analysis.
About the IREB-IT-CQ03 exam
IREB-IT-CQ03 is the iSQI exam for the Certified Professional for Requirements Engineering (CPRE) Foundation Level, the entry-level certificate of the International Requirements Engineering Board (IREB). It checks the basics of requirements engineering (RE): how to elicit, document, validate and manage the requirements for a system. In IREB's view, the Requirements Engineer is a role, not a job title, so the exam suits business analysts, product owners, testers and developers alike. Passing the multiple-choice exam earns the certificate, and the certificate does not expire.
The PlanetCert practice test asks the most about Work Products and Documentation Practices, which is also the chapter IREB gives the most teaching time. Every answer has an explanation, which helps where two IREB terms sit close together, such as a configuration and a baseline, or satisfiers and dissatisfiers. Flashcard Mode suits the glossary terms, and Study Mode suits the template and modeling questions. Brainy AI Assistant can explain why a sentence breaks a quality criterion, or which Kano category a requirement belongs to.
How to earn the certification
- Earns
- IREB Certified Professional for Requirements Engineering, Foundation Level (CPRE-FL)Foundation
The CPRE Foundation Level certificate is valid for life and needs no renewal.
How to prepare for IREB-IT-CQ03
- 1
Map the objectives by cognitive level
Each syllabus chapter opens with its educational objectives, marked L1 (know), L2 (understand) or L3 (apply). Start with the L3 objectives, because they ask for written work such as a use case or a class diagram.
- 2
Learn the foundational glossary terms
IREB says every foundational term in its glossary must be known, even when no objective names it. Drill the terms in Flashcard Mode until pairs such as configuration and baseline are easy to tell apart.
- 3
Specify one small system by hand
Pick a simple system, such as a library loan service. Write a stakeholder list, three user stories, one use case with a form template, a UML class diagram and a UML activity diagram, then check each one against the quality criteria.
- 4
Configure two contrasting RE processes
Describe two projects: one outsourced under a fixed contract, and one product built for a market. Decide for each whether its RE process should be linear or iterative, prescriptive or explorative, and customer-specific or market-oriented.
- 5
Close with a timed run
Take the IREB-IT-CQ03 practice test in Timed Mode once every chapter is covered. For each missed question, ask Brainy AI Assistant which IREB definition the right answer rests on.
Start a timed IREB-IT-CQ03run
IREB publishes the CPRE Foundation Level syllabus, handbook, glossary and a practice examination. IREB-accredited training providers teach the matching course.
Who IREB-IT-CQ03 is for
- Business analysts and requirements engineers who want IREB's shared vocabulary for their work.
- Product owners who write user stories and keep a product backlog in order.
- Testers and developers who turn requirements into test cases and code.
- Project managers and domain experts who join elicitation workshops and reviews.
Typical job titles: Requirements engineer · Business analyst · Product owner · Systems analyst · QA analyst · Project manager
IREB-IT-CQ03 glossary
17 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Baseline
- A stable, change-controlled configuration of work products, used for release planning or other delivery milestones.
- Change Control Board
- A group that often decides on requirement changes in linear projects. In an iterative approach, the product owner adds the change to the product backlog instead.
- Constraints
- Requirements that limit the solution space beyond what the functional requirements and quality requirements need.
- Context boundary
- The line that separates the part of a system's environment that matters for RE from the rest of the world.
- Exploratory prototypes
- Prototypes, from wireframes to native prototypes, that are built to clarify or validate requirements and then thrown away.
- Form template
- A form with predefined fields to fill in, for example to write a use case or a measurable quality requirement.
- Glossary
- A central collection of definitions for context-specific terms, everyday terms with a special meaning, abbreviations and acronyms.
- Kano model
- A model that sorts requirements into delighters, satisfiers and dissatisfiers, which helps decide how to elicit them.
- Personas
- Fictional descriptions of typical people that stand in for a stakeholder role when it has too many members or its members are unknown.
- Phrase template
- A predefined sentence structure for writing an individual requirement or a user story.
- Quality requirements
- Requirements about quality concerns that functional requirements do not cover, such as performance, availability, security or reliability.
- Requirements Engineer
- A role, not usually a job title, held by anyone who elicits, documents, validates or manages requirements as part of the job.
- Stakeholder
- A person or organization that influences the requirements for a system or is affected by that system.
- Statechart
- A state machine whose states are broken down into nested or parallel states.
- System boundary
- The line between a system and its surrounding context. It is often unclear at first and can change over time.
- Traceability
- The ability to follow a requirement back to its origin and forward to later work products, such as test cases.
- Work product
- A recorded intermediate or final result of a work process, from a short-lived sketch to a released requirements specification.