CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Prototypes (wireframes, mockups, interactive models) make abstract requirements concrete and testable. Stakeholders can react to a visual representation, catching misunderstandings before costly development begins — a core BA validation technique.

**Why not A:** A prototype is not simply a code sample distributed to the development team. Code samples are reference implementations or snippets intended to demonstrate coding patterns. Prototypes are preliminary models of a solution created to explore, validate, or communicate requirements with stakeholders, and they may not involve code at all.

**Why not B:** A legal patent prototype is a concept from intellectual property law, not from business analysis or solution design. In the BA context, a prototype is a working or visual model used to elicit feedback, validate assumptions, and refine requirements before committing to full development. It has no legal filing dimension.

**Why not C:** A prototype is not a fully functional first iteration of the product. Prototypes are intentionally incomplete and are designed to explore specific aspects of a solution, test assumptions, or communicate concepts. Describing a prototype as fully functional confuses it with a minimum viable product or an initial release, both of which carry a higher commitment to completeness.