IREB-IT-CQ03 Sample Questions & Answers
Documentation practices, from natural-language to template-based work products, dominate the exam, ahead of eliciting requirements and resolving conflicts, managing them over their life cycle, the discipline's purpose and principles, process structure, and tool support.
Launch the full IREB-IT-CQ03 simulator →Showing 10 of 20 free samples.
- Question 1Advanced
Fundamental Principles of Requirements Engineering · Context: Systems cannot be understood in isolation (L2)
True or False: In Requirements Engineering, the 'system boundary' defines the parts of the environment that are relevant for understanding the system, while the 'context boundary' separates the system itself from its environment.
Show answer & explanation
Correct answer: B
The statement has the definitions reversed. The 'system boundary' separates the system from its environment (the context). The 'context boundary' separates the RE-relevant part of the environment from the rest of the world that is considered irrelevant.
- Question 2Intermediate
Practices for Requirements Elaboration · Elicitation of Requirements (L2)
A team is developing a smartphone app for tourists. The product owner wants to discover features that would surprise and delight users, which are not typically requested or expected. According to the Kano model, the team is trying to identify 'Delighters'. Which elicitation technique is most suitable for discovering this type of requirement?
Show answer & explanation
Correct answer: C
Delighters (or excitement factors) are features that users do not expect and often cannot articulate. Gathering techniques like surveys are better for identifying Satisfiers (performance factors). To uncover innovative Delighters, creativity-focused techniques like brainstorming, prototyping, and storyboarding are required to explore new possibilities beyond the users' current frame of reference.
- Question 3Advanced
Practices for Requirements Elaboration · Validation of Requirements (L2)
Case Study
A mid-sized regional airline, 'AirConnect', wants to develop a new mobile application for flight booking and management. Their current system is a web-only portal that is not mobile-friendly. The primary business goal is to increase direct bookings by 25% and improve customer satisfaction.
The project team has identified several key stakeholder groups: travelers (end-users), marketing department, IT operations, and the company's executive board. The marketing team insists on a highly interactive, visually rich user interface with promotional pop-ups. The IT operations team is concerned about performance and the load on their legacy backend systems. The executive board has set a strict, non-negotiable deadline of 6 months for the first release.
Given the tight deadline, the need to balance conflicting stakeholder interests (visuals vs. performance), and the fact that this is a customer-facing application for a broad, non-technical user base, the lead requirements engineer must choose an appropriate approach for validating the UI/UX requirements before development begins.
Which validation technique would be most effective in this situation to quickly gather user feedback and align stakeholder expectations?
Show answer & explanation
Correct answer: B
Given the conflicting views on UI and the non-technical nature of many stakeholders (travelers, marketing), a visual and interactive prototype is far more effective than a text-based document. An exploratory prototype (like a mock-up) allows for rapid feedback on the user experience, helps resolve the visual vs. performance debate by making it tangible, and can be created quickly to respect the tight deadline. Formal inspections are time-consuming and less effective for validating user interface feel and flow.
- Question 4Beginner
Work Products and Documentation Practices · Glossaries (L2)
A project is creating a requirements specification document. The team has decided to create a central document that defines all context-specific terms, acronyms, and abbreviations to ensure a shared understanding among all stakeholders. What is this work product called?
Show answer & explanation
Correct answer: C
A glossary is a central collection of definitions for context-specific terms, abbreviations, and acronyms. Its primary purpose is to create a shared understanding and ensure consistent use of terminology throughout the project.
- Question 5Intermediate
Management Practices for Requirements · Life Cycle Management (L2)
A team is defining a life cycle model for their requirements. They need to represent the different stages a requirement can be in, such as 'Drafted', 'In Review', 'Approved', and 'Implemented'. Which diagram is most suitable for visualizing these states and the valid transitions between them?
Show answer & explanation
Correct answer: B
A State Machine Diagram (or Statechart) is specifically designed to model the behavior of an object, showing its various states and the events that trigger transitions from one state to another. This is a perfect fit for defining a requirement's life cycle. The diagram below shows a simple example.
stateDiagram-v2 [*] --> Drafted Drafted --> InReview : submitForReview InReview --> Approved : accept InReview --> Drafted : reject Approved --> Implemented : startImplementation Implemented --> Closed : verify Approved --> Canceled : cancel - Question 6Beginner
Management Practices for Requirements · Attributes and Views (L2)
What is the primary purpose of defining views for a set of requirements?
Show answer & explanation
Correct answer: B
Views are used to filter and sort the total set of requirements to show only the information that is currently of interest to a particular audience (e.g., showing only high-priority requirements for managers, or only technical constraints for developers). This helps manage complexity and improve communication.
- Question 7Beginner
Fundamental Principles of Requirements Engineering · Value-orientation: Requirements are a means to an end (L2)
According to the RE principle of 'Value-orientation', the effort spent on documenting a requirement should be proportional to its benefit.
Show answer & explanation
Correct answer: A
The principle of Value-orientation states that requirements are a means to an end, not an end in themselves. The value of a requirement is its benefit minus its cost (eliciting, documenting, etc.). Therefore, it is logical to invest more effort in high-value requirements and less effort in low-value ones.
- Question 8Beginner
Practices for Requirements Elaboration · Sources for Requirements (L3)
A project is in the early stages of defining a new inventory management system. The requirements engineer needs to identify all individuals who will be impacted by the new system, including warehouse staff, procurement managers, and finance department personnel who will use system reports. The engineer compiles a document with their names, roles, and interests in the project. What is this document officially called?
Show answer & explanation
Correct answer: C
A Stakeholder List is the work product used to document identified stakeholders and relevant information about them, such as their name, function/role, interests, and relevance to the project. This is a fundamental step in identifying sources for requirements.
- Question 9Intermediate
Work Products and Documentation Practices · Specify an individual requirement and a user story using a phrase template (L3)
A requirements engineer must specify a requirement using a phrase template to ensure consistency and clarity. The requirement is for a user of a library system to be able to search for books. Using the common user story format, how should this requirement be written?
Show answer & explanation
Correct answer: C
The standard user story phrase template is 'As a [type of user], I want [some goal], so that [some reason/benefit]'. This format clearly identifies the user, the required action, and the value/motivation behind the requirement, which is a key advantage of template-based requirements.
- Question 10IntermediateSelect 3
Work Products and Documentation Practices · Understand the advantages and limitations of modeling in RE (L2)
Which of the following are considered advantages of model-based work products over purely natural-language-based work products? (Select THREE)
Show answer & explanation
Correct answers: B, C, E
Visual models excel at showing how different parts of a system relate to one another, which can be difficult to describe clearly in text.
Formal modeling languages like UML have precise rules, which leave less room for misinterpretation compared to the inherent flexibility and ambiguity of natural language.
Models are abstractions. A class diagram focuses on structure, an activity diagram on flow. This separation of concerns helps stakeholders understand one aspect at a time without being overwhelmed.
Ready for the real thing?
The full IREB-IT-CQ03 simulator has every exam-style question, timed mode, and instant scoring.