Which of the following is an example of a requirements viewpoint?

A requirements viewpoint establishes the conventions and standards for how requirements are represented and organized for a particular audience or purpose. Use cases are a specific, standardized modelling technique used to describe how an actor interacts with a solution to achieve a goal. They provide a structured format for capturing functional requirements from a user's perspective, thereby serving as a classic example of a requirements viewpoint.

B. Mind map: This is a brainstorming and information organization technique used to capture ideas, not a standardized viewpoint for formally representing requirements.
C. Expert judgement: This is a form of elicitation used to gather information from a subject matter expert, not a method for structuring or representing requirements.
D. Item tracking: This is a management technique used to monitor and manage issues, actions, or defects throughout a project, not a format for requirements representation.

1. IIBA

A Guide to the Business Analysis Body of Knowledge (BABOK Guide)

Version 3

2015.

Section 7.4.4.3 (Viewpoints and Views): Defines a viewpoint as "a set of conventions that define how requirements will be represented

how these representations will be organized

and how they will be related." It further states

"For example

a business process viewpoint may be comprised of a set of models

such as process models

use cases

and business rules..." This directly links use cases to the concept of a viewpoint.

Section 10.47 (Use Cases and Scenarios): Describes use cases as a technique to model the interactions between actors and a solution

confirming their role as a requirements representation format.

Section 10.29 (Mind Mapping): Classifies mind mapping as a technique to "articulate and capture thoughts

ideas

and information

" distinguishing it from a formal requirements viewpoint.

Section 10.26 (Item Tracking): Defines this as a technique to "capture and assign responsibility for issues and stakeholder concerns

" positioning it as a management tool rather than a requirements representation model.