Prototype Model
- 1. PROTOTYPE MODEL Presented By Aijaz Ahmad Software Engineering Bca 2nd year (3rd semester)
- 2. PROTOTYPE MODEL • Prototype model is working model of Software with same limited functionality. • In prototype model, we do not develop the full Software, firstly we develop a prototype of the Software means we include some most favorable functions. • After this the Software is handed over the customer and the customer will use the prototype product and check any possible short coming problems. • If any problem in the product or customer is not satisfied of the product than we removed problems in the product or we create a new version of prototype of the product.
- 3. STEPS OF PROTOTYPE MODEL • Requirement gathering and analysis. In this phase, the requirements of the system are defined in detail. During the process, the users of the system are interviewed to know what is their expectation from the system. • Quick design. The second phase is a preliminary design or a quick design. In this stage, a simple design of the system is created. However, it is not a complete design. It gives a brief idea of the system to the user. The quick design helps in developing the prototype. • Build a Prototype. In this phase, an actual prototype is designed based on the information gathered from quick design. It is a small working model of the required system. • Refining prototype If the user is not happy with the current prototype, you need to refine the prototype according to the user's feedback and suggestions
- 4. WHEN WE USE PROTOTYPE MODEL • Prototype model should be used when the desired system needs to have a lot of interaction with the end users. • Unclear requirements when requirements are not properly understand. • Complicated and larger system. • Unclear solution.
- 5. ADVANTAGES OF PROTOTYPE MODEL • The customers get to see the partial product early in the life cycle. This ensures a greater level of customer satisfaction and comfort. • New requirements can be easily accommodated as there is scope for refinement. • Missing functionalities can be easily figured out. • Errors can be detected much earlier thereby saving a lot of effort and cost, besides enhancing the quality of the software. • The developed prototype can be reused by the developer for more complicated projects in the future.
- 6. DISADVANTAGES • It is time consuming process. • There may be too much variation in requirements each time the prototype is evaluated by the customer. • Poor Documentation due to continuously changing customer requirements. • It is very difficult for developers to accommodate all the changes demanded by the customer. • After seeing an early prototype, the customers sometimes demand the actual product to be delivered soon.