Prototype Model
Topic Outline
- Prototype Model
- When using a prototype model
- Requirements
- Quick Design
- Build Prototype
- Customer Evaluation
- Prototype Refinement
- Advantages
- Disadvantages
Prototype Model
It is a software development life cycle model. When the requirements of the system are not known in detail, then a prototype model is used. The prototype is built and tested until the desired prototype is achieved. When the Prototype is built, the customer can understand the requirements of the desired system and provides suggestion and improvements on the prototype. Before developing the actual system, the prototype should be built first.
When Use Prototype Model:
- It is used when the requirements of the system are not defined.
- It is used for developing user interfaces.
Phases of Prototype model are as follow:
Requirements
The prototype model starts with requirement analysis and gathering. In this phase requirements of the system are gathered and defined in detail. Requirements are gathered from the user of the system to know what is their expectations from the system.
Quick Design
In this phase, a simple design of the system is created rather than developed a complete system. This design gives an idea of the system to the user. Simple designs are created when requirements are known.
Build Prototype
In this phase, the prototype is built based on a simple design. The prototype is a small model of an actual or required system. The prototype also represents a rough design of the system.
Customer Evaluation
In this phase, the building prototype is presented to the user for his/her evaluation. Suggestions are collected from the customer. If the customer wants any change in this system, the system is updated.
Prototype Refinement
If the customer is not satisfied with the prototype, you need to again build the prototype according to the customer's suggestions. When the customer is satisfied with the prototype a final system is developed.
Advantages
- It Reduces development time.
- It Reduces development costs.
- It Requires user involvement.
- Results in higher user satisfaction.
- This model is easy to understand.
Disadvantages
- It is a slow process.
- Prototype model is expensive.
- Too many changes can disturb the rhythm of the development team.
- This model is time taking process.
😍
ReplyDelete