They provide feedback to the developers regarding the prototype: what is correct, what needs to be modified, what is missing, what is not needed, etc. Based on the feedback, the prototype is modified to incorporate some of the suggested changes that can be done easily, and then the users and the clients are again allowed to use the system. This cycle repeats until, in the judgment of the prototypes and analyst.
Based on the feedback, the initial requirements are modified to produce that final requirements specification, which is then used to develop the production quality system.
Figure Illustrates the steps carried out in the prototyping model. These steps are listed below. Requirements gathering and analysis: A prototyping model begins with requirements analysis and the requirements of the system are defined in detail. The user is interviewed in order to know the requirements of the system. Quick design: When requirements are known, a preliminary design or quick design for the system is created. It is not a detailed design and includes only the important aspects of the system, which gives an idea of the system to the user.
A quick design helps in developing the prototype. Build prototype: Information gathered from quick design is modified to form the first prototype, which represents the working model of the required system.
User evaluation: Next, the proposed system is presented to the user for thorough evaluation of the prototype to recognize its strengths and weaknesses such as what is to be added or removed. Comments and suggestions are collected from the users and provided to the developer. Refining prototype: Once the user evaluates the prototype and if he is not satisfied, the current prototype is refined according to the requirements.
That is, a new prototype is developed with the additional information provided by the user. The new prototype is evaluated just like the previous prototype. This process continues until all the requirements specified by the user are met. A prototyping model starts with requirement 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.
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.
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. In this stage, the proposed system is presented to the client for an initial evaluation. It helps to find out the strength and weakness of the working model.
Comment and suggestion are collected from the customer and provided to the developer. This phase will not over until all the requirements specified by the user are met. Once the user is satisfied with the developed prototype, a final system is developed based on the approved final prototype. Accelerated Delivery of the System — Software change is required in the change of business speed.
Fast delivery and usability is more important than description of long-term software maintainability functionality. Skip to content. Change Language. Related Articles. Table of Contents. Improve Article. Save Article. Like Article.
0コメント