The system undergoes routine maintenance for minimizing downtime and prevent large-scale failures. Once the final system is developed based on the final prototype, it is thoroughly tested and deployed to production. Once the user is satisfied with the developed prototype, a final system is developed based on the approved final prototype. This phase will not over until all the requirements specified by the user are met. If the user is not happy with the current prototype, you need to refine the prototype according to the user’s feedback and suggestions. Comment and suggestion are collected from the customer and provided to the developer. It helps to find out the strength and weakness of the working model. In this stage, the proposed system is presented to the client for an initial evaluation. It is a small working model of the required system. In this phase, an actual prototype is designed based on the information gathered from quick design. The quick design helps in developing the prototype. It gives a brief idea of the system to the user. In this stage, a simple design of the system is created. The second phase is a preliminary design or a quick design.
During the process, the users of the system are interviewed to know what is their expectation from the system. In this phase, the requirements of the system are defined in detail. Prototyping Model has following six SDLC phases as follow: Step 1: Requirements gathering and analysisĪ prototyping model starts with requirement analysis. It is an iterative, trial and error method which takes place between developer and client. It works best in scenarios where the project’s requirements are not known in detail. It also creates base to produce the final system or software.
Prototyping Model is a software development model in which prototype is built, tested, and reworked until an acceptable prototype is achieved.
0 kommentar(er)
