It can be termed as a process of creating an incomplete model for future’s complete featured software. The process includes identification of the basic requirements, developing initial prototypes, gather reviews of the customers, revise and enhance. Prototyping is mostly exercised in projects where risk is involved. The aim is to eliminate an element of any serious risk in the project. The processing methodology is mostly used when a rapid development is essential.
It will solve many issues related to the software and the end users. This usually engages interviews involving a number of users from all the departments or phases of the existing system. If there is any misunderstanding between the end user and the customer is present, all of them are exposed. It will help in finding the missing services and will help us to identify the confusing services. A system is available early on in the process. It serves to provide the foundation for deriving a working system specification. User Interface (UI) that can support end user’s training and testing of the software at the same time. That will enable us in developing software according to our needs and requirements completely. Quicker user feedback leads to the better solution. Along with the development our end using staff would be given a training session as well.
Some of the problems that I think we could face are insufficient analysis. This can lead to ignore enhanced solutions, preparation of incomplete specifications or the conversion of limited prototypes into poorly engineered final projects that are hard to maintain. The user may have some confusion regarding the finished system as they may think that this is a prototype and actual system would be more refined one. In this methodology, the developer could misunderstand the user’s objective.