A. Idea-finding.
B. Acceptance-finding.
C. Data-finding.
D. Solution-finding.
A. MOSCOW.
B. SMART.
C. MOST.
D. OSCAR.
A. Environmental.
B. Technological.
C. Legal.
D. Economic.
A. To determine strategy.
B. To prioritise requirements.
C. To define a root definition.
D. To analyse stakeholders.
A. When all stakeholders are agreed on the way forward.
B. When suitably sized rooms are available
C. When time and budget are constrained.
D. When a geographically dispersed set of users needs to be consulted.
A. When the users have had the opportunity to use the software for a period of time.
B. When the deliverables of the system design have been agreed.
C. When the deliverables of the requirements analysis have been agreed.
D. When the software has been completed and has passed system testing
A. A class model.
B. A business activity model.
C. A use case diagram.
D. A swim-lane diagram
A. List of issues/problems.
B. Stakeholder perspectives.
C. Terms of reference.
D. Business case.
A. PESTLE.
B. MOST.
C. CATWOE.
D. SWOT.
A. User acceptance testing.
B. Post-implementation review.
C. Benefits realisation.
D. Implementation.
