A prototyping model uses Continuous user interaction by interacting with user they collect a requirement in early stage to produce a prototype.The Prototype is used to obtain the System requirement specification and can be throw away after the SRS is build.Then appropirate life cycle model is chosen for build a actual product after user accepts the SRS.
 |
| Prototype Model |
Prototype Model Follows some activities that are:
- The software development organisation interact with customer to collect their requirements.
- Based on the requirements collected from customer respective team would go ahead and start designing the prototype which needs to be enhanced towards meeting requirement.
- Development of the prototype would happen after designing done.In Development of the prototype we have couple go approaches and it follows,
- Static Prototype:
- Working with a static and operational specific stuffs such as Word Documents, Images.etc..
- Dynamic ProtoType:
- This type of prototype is mainly focuses on the prototypes in which requirements would keep on changing.Dynamic prototype deals with two of its subtype.
- Thick Client
- Thin Client
- Thick Client:
- The Application which you are going to make thru is non browser based and something which can accessed only thru operating system such as windows,mac OS would fall under the category of Thick client (Example:- Adobe,Calculator,Gtalk,IRCTC).
- Thin Client:
- The application which you are going make thru is only supported by a browser then that application development of prototype would fall under Thin Client.
On Every prototype the implementation of the product goes only after getting approval from the customer on the same.
Prototype are two types,
- Through away Prototype: Also known as Rapid Prototype:
- This prototype can adopted with both Static and Dynamic prototype.this prototype would go till customer satisfies.They develop a prototype which is equal to the final product indeed.
- Evolutionary Prototype:
- Case1
- The Customer will be asking software company to come up with well build prototype based n the requirements collected from customer in the early phases,This to clarify how good the understanding of the company which has collected the requirements.
- Case2
- The software company goes to customer place with a proper deck of the prototype in which they involves and present it before the customer.So that Customer would be having clear idea what has been understood by the company and what needs to be enhanced to the existing module.
What is the Advantages of Prototype model?
- The Possibilities of a piece of software getting rejected by a customer is very minimal
- The Customer will have feel of how the final product would be in very initial stage itself
- There will not be any communication gap between software development company and customer in-terms of meeting requirement
- A software company which has developed a prototype for one customer can be reused for another customer too.
What is the DisAdvantages of Prototype Model?
- Software development company would need to spend pretty high cost in developing the prototype.Its too expensive for the software development company.
- If a Business Analyst (BA) fails to collect requirement properly then the time taken for the prototype would be more than it requires.
- Testing would not happen in all the phases. It would happen only after coding done, this may lead to have a product which does not meet requirements and buy more time too.
0 comments:
Post a Comment