Throwaway prototypes are built to last and become the final product, whereas evolutionary prototypes are thrown away after initial design phases

Throwaway prototypes are discarded after requirements are defined, whereas evolutionary prototypes are iteratively improved until they become the final product

Evolutionary prototyping requires a written SRS document, while throwaway prototyping skips the SRS entirely

Both prototypes are discarded, but throwaway prototypes are much more expensive to build

To define the exact format, meaning, and structure of data elements

To list the hardware requirements for the software

To provide the implementation code for database tables

To outline the step-by-step user interface design

The administrator shall be able to generate monthly sales reports

The system must allow users to reset their passwords via email

The system must verify that the user is 18 or older during registration

The application must process all credit card transactions in under 2 seconds

To replace all functional and non-functional requirements with strict legal contracts

To provide a lengthy, exhaustive technical blueprint that developers must implement exactly as written

To concisely describe a feature from the user's perspective, acting as a placeholder for collaborative discussions

To capture the exact database schemas, network configurations, and coding frameworks required

The marketing and sales departments

Customers, system analysts, developers, and testers

Only the end-users and product managers

Only the software developers and coding team