CPRE FL · IREB · Introduction and Overview of Requirements Engineering · Bank updated 2026-10-15
CPRE FL practice questions: Introduction and Overview of Requirements Engineering
5 free questions from 11 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Introduction and Overview of Requirements Engineering section of our CPRE FL bank (11 questions on this area, which carries 6% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
Free: 6 questions in study mode, no card. All 11 Introduction and Overview of Requirements Engineering questions and the full CPRE FL bank: $15 one-time.
1/5 · Introduction and Overview of Requirements Engineering · easy
Which of the following statements correctly reflects the IREB glossary definition of the term 'requirement'?
AA requirement is a description of a feature or design decision for the system, written by the development team in the specification and agreed with the project manager as the binding basis for implementation, effort estimation and acceptance testing.
BA requirement is a test case derived from the functional specification after implementation, stating the input, the expected result and the condition under which the stakeholders accept the system's behavior as correct.
CA requirement is a condition or capability needed by a stakeholder to solve a problem or achieve an objective; a condition or capability a system must possess to satisfy a contract or specification; or a documented representation of either.
DA requirement is a legally binding clause of the contract between customer and supplier, recorded in the contract annex and signed by both parties, that can be changed only through a decision of a formal change-control board.
2/5 · Introduction and Overview of Requirements Engineering
A project team skips systematic requirements elicitation and validation, relying instead on an informal one-page description from a single stakeholder. Six months later, the delivered system is rejected by most users because it fails to support several use cases that other stakeholder groups actually needed. Which consequence of insufficient Requirements Engineering does this scenario most directly illustrate?
AScope creep resulting from continuous negotiation of quality requirements with the customer.
BReduced maintainability of the source code due to poor software architecture decisions.
CExcessive documentation overhead caused by capturing requirements from too many stakeholders.
DLow stakeholder acceptance and costly rework caused by unaddressed stakeholder needs due to incomplete elicitation.
3/5 · Introduction and Overview of Requirements Engineering · hard
A specification states: 'The system must be built on the organization's existing Java-based middleware platform; no other technology may be introduced during the contract period.' According to IREB's classification of requirement types, this statement is best categorized as a:
AFunctional requirement, because it describes a capability the middleware platform must provide to end users.
BAssumption, because it is a condition believed to be true but not yet verified before development starts.
CQuality requirement, because it specifies a technical attribute the system must exhibit at runtime.
DConstraint, because it restricts the solution space (technology choice) independent of the system's functional or quality needs.
4/5 · Introduction and Overview of Requirements Engineering
A junior developer argues: 'Nobody on our team has the job title Requirements Engineer, so we clearly aren't doing requirements engineering.' Which response best reflects the CPRE FL syllabus's view on this claim?
AThe claim is correct specifically in agile contexts, since Scrum forbids assigning any team member responsibility for eliciting or validating requirements.
BThe claim is incorrect because every team automatically performs adequate requirements engineering regardless of which activities are actually carried out.
CThe claim is incorrect: 'Requirements Engineer' typically denotes a role rather than a job title, and business analysts, application specialists, product owners, systems engineers, or even developers commonly act in this role.
DThe claim is correct: only a person formally titled 'Requirements Engineer' is permitted to elicit, document, validate, or manage requirements on a project.
Answer: C. Section 1.5 states that 'Requirements Engineer typically is not a job title, but a role that people play' who elicit, document, validate and/or manage requirements, have in-depth RE knowledge, and bridge the gap between problem and solution — and that in practice this role is performed by business analysts, application specialists, product owners, systems engineers, and even developers.
Source: the IREB CPRE Foundation Level Syllabus v3.3.0 — Introduction and Overview of Requirements Engineering
5/5 · Introduction and Overview of Requirements Engineering
A project manager tells the team to skip requirements engineering entirely and start coding immediately, reasoning that 'our developers are so experienced that what the stakeholders want is obvious to them.' Which statement, according to the CPRE FL syllabus, best identifies the flaw in this reasoning?
AThe flaw only applies to inexperienced teams; the syllabus states that RE is required exclusively for teams that have worked together for less than two years.
BThe reasoning is sound: sufficiently experienced teams are exempt from requirements engineering because their domain knowledge substitutes for structured elicitation.
CThe assumption that requirements are self-evident is itself listed as a typical cause of missing, unclear, or incorrect requirements, alongside rushing straight into building the system, communication problems, and inadequate RE education and skills.
DThere is no flaw, since the syllabus states that RE can be performed just as effectively after development is complete, with no difference in resulting risk.
Other CPRE FL areas
The same kind of free sample for every other section of the CPRE FL bank:
Practise CPRE FL with instant feedback
6 free questions in study mode · no card · full CPRE FL bank with area filters and the error log: $15 one-time · no dumps, no ads.
Start CPRE FL free →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by IREB. CPRE FL and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official IREB materials (as of August 2026); always confirm current details with the vendor before booking.