what is prototype model(in S.T.L.C)? What is architecture of prototype model?

1.Test Strategy& Analysis
2.Test case design
3.Test Execution
4.Test Log preparation
5.Defect tracking
6.Final report


Explain different Prototype Models Types.
There are four types of Prototype Models based on their development planning:
The Patch-Up Prototype,
Nonoperational Prototype,
First-of-a-Series Prototype and
Selected Features Prototype.
What are advantages of Prototype Model?
Creating software using the prototype model also has its benefits. One of the key advantages a prototype modeled software has is the time frame of development. Instead of concentrating on documentation, more effort is placed in creating the actual software. This way, the actual software could be released in advance. The work on prototype models could also be spread to others since there are practically no stages of work in this model. Everyone has to work on the same thing and at the same time, reducing man hours in creating a software. The work will even be faster and efficient if developers will collaborate more regarding the status of a specific function and develop the necessary adjustments in time for the integration.

Another advantage of having a prototype modeled software is that the software is created using lots of user feedbacks. In every prototype created, users could give their honest opinion about the software. If something is unfavorable, it can be changed. Slowly the program is created with the customer in mind.
What are Disadvantages of Prototype Model ?
Implementing the prototype model for creating software has disadvantages. Since its being built out of concept, most of the models presented in the early stage are not complete. Usually they lack flaws that developers still need to work on them again and again. Since the prototype changes from time to time, it’s a nightmare to create a document for this software. There are many things that are removed, changed and added in a single update of the prototype and documenting each of them has been proven difficult.

There is also a great temptation for most developers to create a prototype and stick to it even though it has flaws. Since prototypes are not yet complete software programs, there is always a possibility of a designer flaw. When flawed software is implemented, it could mean losses of important resources.

Lastly, integration could be very difficult for a prototype model. This often happens when other programs are already stable. The prototype software is released and integrated to the company’s suite of software. But if there’s something wrong the prototype, changes are required not only with the software. It’s also possible that the stable software should be changed in order for them to be integrated properly.