A. Functional requirement.
B. Technical requirement.
C. General requirement.
D. Non-functional requirement.
A. It provides a firm basis for tracking the business benefits and managing their realisation.
B. It quantifies intangible benefits that could not be quantified when the business case was presented.
C. It provides a firm basis for tracking the benefits of making changes to requirements.
D. It is published to shareholders to show that their investment made will result in tangible benefits for the organisation.
A. Allows an analyst to confirm their understanding of requirements.
B. Only suitable for Agile project environments.
C. Enables the elicitation of usability requirements.
D. Suitable for waterfall requirements elicitation.
A. Entities.
B. Actors.
C. System boundaries.
D. Users.