What does system prototyping primarily help verify?

System prototyping primarily helps verify customer requirements and design feasibility by allowing stakeholders to interact with an early version of the system. This hands-on approach enables users and developers to explore the system's functionalities, ensuring that the end product aligns with customer expectations.

When a prototype is developed, it brings the abstract specifications to life, making it easier for stakeholders to identify gaps, misunderstandings, or additional needs that weren't clear during initial discussions. Through this iterative process, feedback can be gathered and incorporated early in the development lifecycle, reducing the risk of costly changes later on.

This dynamic means that not only can requirements be confirmed more reliably, but the practicality of the proposed design can also be assessed based on actual user interaction with the prototype. This is crucial for aligning the system design with user needs, ensuring that the final version will be both useful and usable.

Other options, while relevant in their contexts, do not capture the primary purpose of system prototyping in the same way. For instance, while securing performance or adhering to budgetary constraints are important, they do not fundamentally address the verification of user needs and design viability that prototyping is specifically intended for.