The prototyping model has the sequence:
(A) Customer Evaluation
(B) Quick design
(C) Requirements
(D) Implement
(E) Design

Explanation

The prototyping model always begins by gathering the Requirements (C), even if they are vague and incomplete. A Quick design (B) is then prepared, which focuses only on the parts of the software visible to the user, and this design is turned into a working prototype during Implement (D). The prototype is handed to the user for Customer Evaluation (A), whose feedback refines the requirements; only when the requirements are stable does the team move to the full engineering Design (E) of the real product. Hence the order is (C) → (B) → (D) → (A) → (E). The other sequences are wrong because they evaluate or design before anything has been built, which is impossible in a prototype-driven cycle.