Comprehensive and Detailed Explanation From Exact Extract:
Requirements attributes capture structured information about each requirement. Rationale records why it exists. Source identifies where it came from (stakeholder, document, meeting). Traceability is a broader property, not a single attribute, enabling links to origins and realizations. The dependency attribute explicitly documents relationships between requirements, such as "Req A depends on Req B". It shows where a requirement's implementation requires others (enabler requirements) to be implemented first. Thus, dependency is the attribute used to represent such implementation dependencies.

Comprehensive and Detailed Explanation From Exact Extract:
The handbook advises that a glossary be centrally managed by an identified owner or small team to ensure consistency and controlled updates; decentralised ownership easily leads to divergence, so A is wrong. To realize its benefits, glossary use must be mandatory-documents should be checked against it-so B is incorrect. Everyday words that receive a special meaning in the project (e.g., "customer", "case") must be included, so C also fails. Therefore, the only correct choice is that all other statements are wrong.

Comprehensive and Detailed Explanation From Exact Extract:
CPRE describes typical facet combinations. Participatory RE involves close collaboration between customer stakeholders and the development team, as seen in agile projects. It is inherently iterative-requirements emerge and evolve through sprints-and explorative, because understanding deepens over time. It is also customer-specific: the system is built primarily for one customer organization. Prescriptive processes, in contrast, aim at fixed upfront specifications and are more aligned with contractual or market-oriented product development. Hence, the correct facet combination for participatory RE is explorative, iterative and customer- specific (option A).