Rapid design feedback: How does system prototyping primarily help during analysis and design of an information system?

Introduction / Context:
Prototyping creates an early, simplified version of a system to validate requirements, user interface flows, and core behaviors. It accelerates learning by showing stakeholders something concrete rather than abstract documents. This reduces the risk of building the wrong product and improves communication across roles.

Given Data / Assumptions:

• Users need to visualize screens and interactions to give actionable feedback.
• Developers benefit from experimenting with logic and constraints early.
• The prototype may be throwaway or evolutionary.

Concept / Approach:
A good prototype supports two-way learning: it communicates quickly to users what the final system might look like and how it behaves, and it helps programmers understand flows, data validation, and algorithmic edge cases. This combination tightens the feedback loop between business and technical teams, leading to better requirements and more feasible designs before heavy investment in full-scale development.

Step-by-Step Solution:

Verification / Alternative check:
Agile and iterative methods routinely employ prototypes, wireframes, or MVPs to validate assumptions with users and to derisk technical approaches for developers.

Why Other Options Are Wrong:
Option (b) alone omits the developer learning benefit; (a) alone omits crucial user validation; (c) narrows the audience improperly.

Common Pitfalls:
Treating prototypes as production-ready; failing to mark assumptions; not involving actual end users in feedback sessions.

Final Answer:
Both (a) and (b)