For the development of the app, which I named WritersHelp, I decided to use the Prototype Model because of the advantages that this model offers. Users will be actively involved in the development of the product. The goal is to create a  working model, so the users get a better understanding of the system being developed. Errors can be detected much earlier, rapid user feedback is available leading to better solutions, missing functionality can be identified easily, and confusing or difficult functions can be identified (Whitten and Bentley, 2007).

​

The basic idea is that instead of having a rigid system that impedes a design or coding to proceed, a prototype is built to understand the requirements based on the currently known requirements. By using this prototype, the client can become comfortable with the system, since the use with the prototype allows the user to better understand the requirements of the desired system. The prototype is usually not a complete system and many of the details are not built into the prototype. The goal is to provide a system with overall functionality. The diagrams below depict the phases in the development of a prototype.

Designers explore multiple ways to solve the same problem, testing them with users to determine the ideal path forward. Each of these prototypes incrementally gets better and allows the designer to improve the overall interactions with the software throughout the process based on testing (McElroy, 2017).

(Below is a sample of my product)