What prototyping technique shows a sequence or navigations through a series of images or illustrations?

In the PMBOK® Guide and the PMI Guide to Business Analysis, prototyping is a method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.

Why Choice A is correct:

Visual Sequence: Storyboarding is a prototyping technique that uses a sequence of images or illustrations to show how a user would navigate through a system or how a business process flows.

UX and Flow: It is particularly effective for explaining the " user journey. " Instead of showing a single static screen, it shows the progression (Step 1 - > Step 2 - > Step 3), making it easier for stakeholders to visualize the logic and transitions of the solution.

Low Fidelity: It is often a low-fidelity technique (hand-drawn or simple digital sketches), which allows for quick changes and iterative feedback without a heavy investment in coding.

Analysis of other options:

B (Wireframes): While wireframes are a type of prototype, they usually represent a single static page or screen layout. They show the structural elements (buttons, text boxes, headers) but do not inherently show a " sequence or navigation " unless they are linked together in a more advanced interactive prototype.

C (Data simulation): This is a technical technique used to test how a system handles specific data inputs or volumes. It does not use images or illustrations to show a user interface or navigation flow.

D (Report prototyping): This focuses specifically on the layout, data fields, and formatting of an output document (like a PDF or Dashboard report). It does not show a navigational sequence through a software application.

Key Concept: The Project Management Institute (PMI) emphasizes that Storyboarding (Choice A) is a powerful communication tool. By showing the navigation through a series of images, the project team can identify gaps in logic or " dead ends " in the user experience early in the requirements phase, preventing costly rework during the development phase.