What elicitation technique is being utilized when developers create a mock-up for stakeholders to visualize the new product?

The technique being used is prototyping, which involves creating a preliminary model or mock-up of a product to give stakeholders a tangible representation of how the final product may look and function. This visual aid is crucial for facilitating discussions, gathering feedback, and refining requirements based on real user interactions with the mock-up.

By using prototypes, developers and stakeholders can explore the user interface, functionality, and overall design of the product in a more interactive way. Stakeholders can articulate their preferences and concerns based on the prototype, which helps ensure that the final product meets their expectations and needs. This iterative process of feedback and refinement is a core advantage of prototyping, making it an essential technique in requirements elicitation.

Other techniques, such as brainstorming, involve generating ideas in a group to explore possibilities but do not necessarily create a visual representation. Hands-on focus may suggest direct interaction but lacks the structured model that a prototype provides. Use case reviews focus on documenting scenarios in which users interact with the system, making it more analytical than visual. Prototyping, therefore, stands out as the most effective technique for visualizing and refining product concepts.