CPRE-FL_Syll_3.0 Exam Preparation Material | IREB Foundation Level (CPRE FL)

Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The handbook lists several key factors for tailoring RE processes: degree of shared understanding between stakeholders and team, available time and budget, trust, system complexity, criticality and volatility of requirements. High volatility and low shared understanding typically call for more iterative and rigorous RE. Limited time and budget favour lightweight approaches. The sheer number of requirements may affect workload but is not considered a primary factor in deciding process facets such as linear vs. iterative or customer-specific vs. market-oriented.
Thus, “quantity of requirements” is not one of the main influencing factors.

Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
In the Kano model, the x-axis represents implementation of a requirement and the y-axis customer satisfaction. Dissatisfiers (basic needs) cause strong dissatisfaction when absent but don’t increase satisfaction much when fulfilled; their curve is steep in the negative quadrant, flattening as implementation increases―this matches curve
C. Satisfiers have roughly linear behaviour: the more fully implemented, the more satisfied customers are―curve
B. Delighters have little effect when absent but produce high satisfaction when present; their curve is flat near the origin and rises sharply at higher implementation―curve
A. Hence mapping ACDelighters, BCSatisfiers, CCDissatisfiers is correct.

Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The syllabus distinguishes categories of RE tools: office tools (general purpose), documentation of knowledge about requirements (e.g., wikis, requirements repositories), management of requirements (for traceability, attributes, baselines), management of RE process (workflow and task support) and others. Office tools can be used but have significant limitations―especially for traceability―so A is overstated. Requirements-management tools deal with requirements objects and links, not workflow (C). Process-management tools handle workflow (B). Documentation tools, such as wikis or collaborative repositories, support sharing and collaboratively editing requirements knowledge, which makes D correct.

Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Natural-language guidelines advise using active voice and a clear subject. The requirement currently focuses on the “option to change font color” being “displayed” rather than on what the system shall do, and includes spelling errors. Rewriting it as “The system Alfa shall display an option to change font color in its main menu” uses active voice, clarifies responsibility and fits recommended phrase templates. No universal quantifiers like “always” or “all” are present, no specific condition is needed, and there are no problematic nominalizations. Thus the primary defect is the passive, object-centred phrasing.