You are on page 1of 18
MANAGEMENT INFORMATION SYSTEM ||IPROTOTYPE MODEL WHAT IS PROTOTYPE MODEL? * Prototype Model is a software development model in which a prototype is built, tested, and reworked until an acceptable prototype is achieved. * A prototype is a preliminary or first model of something, such as a machine, it is a model or sample of a product made for the client's evaluation and feedback regarding the desired finishing product. After studying the prototype, the client can decide on the features they need in the desired product. } TYPES OF PROTOTYPE MODEL RAPID THROWAWAY PROTOTYPING In this method, a developed prototype need not necessarily be a part of the ultimately accepted prototype. Customer feedback helps in preventing unnecessary design faults and hence, the final prototype developed is of better quality. EVOLUTIONARY PROTOTYPING The prototype developed initially is incrementally refined on the basis of customer feedback till it finally gets accepted.it offers a better approach which saves time as well as effort. A 4 Ml } TYPES OF PROTOTYPE MODEL INCREMENTAL PROTOTYPING The final expected product is broken into different small pieces of prototypes and developed individually. In the end, when all individual pieces are properly developed, then the different prototypes are collectively merged into a single final product in their predefined order. EXTREME PROTOTYPING This method is mainly used for web development. It consists of three sequential independent phases: |.Basic protoype presented on HTML 2.Functional screens made with simulated data 3.Alll services are associated with fi product. 4 Ml FLOWCHART [_] [eB] ~~ REQUIREMENT GATHERING 4! REFINEMENT => QUICK desicn — SUGGESTION BUILD PROTOTYPE INCORPORATION \_customer EVALUATION OF ey PROTOTYPE ACCEPTANCE BY CUSTOMER \ > IMPLEMENTATION \ sy testinc MAINTENANCE REQUIREMENT GATHERING Let's take an example where we are a software developing company ABC, and our client is an automobile company for which atarefeannused (tallevelooiooscnarelion the system are defined in detail and the their management so we further enquired users of the system are interviewed to land analyzed their requirements, know what is their expectations from the ee oa aceite eae Oooo ‘ : they want on the software — system so that their needs can be fulfilled. Sees Se and different models available + The price range of the vehicles + Employee details A prototype model starts with requirement analysis. In this phase, the requirements of QUICK DESIGN Quick design is not like system design, it is more like a rough design and a blueprint of the solution created after considering customer reviews, it acts as a working model and involves 2 tools- * Build a prototype - It is a stage where a preplanned work converts into a realistic prototype. This prototype has all the necessary requirements of the proposed system. * Refine requirements and incorporate customer suggestion -The users thoroughly evaluates the first prototype and note its strengths and weaknesses, what needs to be added and what should be removed. The developer collects and analyses the remarks from the users, BUILDING PROTOTYPE AND CUSTOMER EVALUATION [_| In this step, a prototype is made customer evaluation of the prototype The using the information from the prototype developed is then presented to previous step. It is a small the customer and the other important working model of the software stakeholders in the project. The feedback is product being built, collected in an organized manner and used for further enhancements in the product under development. wt > ACCEPTANCE BY CUSTOMER ‘The feedback and the review comments are] |Suppose we are developing discussed during this stage and some] _| software fora Retail shop owner, negotiations happen with the customer basedon| who is not satisfied with the factors like — time and budget constraints and the technical feasibility of the actual implementation. The changes accepted are again incorporated in the new Prototype developed and the cycle repeats until the customer expectations are met. layout of the billing will give feedback on the changes required until the desired output is obtained. Design _| 5] x| Once the client finalizes a prototype, on the basis of that prototype, the final product is designed and developed. This developed product is tested by the testing team and if it is ready to go LIVE, the product is deployed and is available for end-user. = SKETCH LOw-FI HI-FI 3 IMPLEMENTATION Once the final system is developed based on the final prototype, it is thoroughly tested and deployed to production. The system undergoes routine maintenance for minimizing downtime and prevents large- scale failures. Suppose the customer is an NGO we need to develop a software once the final prototype model is finalized by the customer. It is tested and sent for final production. Updates are made from time to time for the smooth functioning of the organization. Testing is a process of making sure that the program performs the intended task. Once the system is designed it should be tested for validity. During this phase, the system is used experimentally to ensure that the software does not fail and it will work according to its specification. It is tested with special test data. Suppose the customer is an employee of a corporate company who needs a prototype software for analyzing the company data. The testing parts involves the testing of coded software using testing cases to ensure there are no remaining bugs or errors. The functionality is tested again to ensure that all the customer requirements are fulfilled or not. MAINTANENCE It is the process of incorporating changes in the implemented existing system. * Enhancement: Adding new functions or additional capabilities to the system. * Adaptation: Customizing the software to run in anew environment. * Correction: Correcting the bugs in the existing software. The maintenance step ensures that the employee is satisfied with the prototype as it works the same as it previously used to. MEDITECH-MEDICAL INFORMATION TECHNOLOGY, INC Ge MEDITECH has been a leading software vendor in the health care informatics industry for 40 years. It is the flagship product used at General Hospital and is described as the number one health ere vendor in the united | MEDITECH States with approximately 25% market share. All Meditech platforms are certified EMR/EHR systems. MEDITECH-MEDICAL INFORMATION TECHNOLOGY, INC Ge REQUIREMENT GATHERING In the first stage, meditech founders pappalardo and marble took their mumps programming language and started the company in 1969, so during that period they conducted surveys among various patients, doctors, nurses etc, and understood what is their need and expectations and accordingly planned on how to design the system QUICK DESIGN So, after that they started to design the system and released a software which was still in its development stages which is termed as a prototype. they gave the software acess to selected hospitals and their staff and patients. after sometime they collected the feedback from those who used the software MEDITECH-MEDICAL INFORMATION TECHNOLOGY, INC Ge REFINING PROTOTYPE After analysing their feedbacks and technical glitches, the founders took steps to work on their suggestions and released a Meditech Interpretive Information System (MIS) Language. generally this refinement process keeps on going in a loop till customers are satisfied with the product. in this case their iis language was accepted by the customers IMPLEMENTATION AND TESTING The final prototpe is thoroughly tested and deployed to production, The system undergoes routine maintenance for minimizing downtime and prevents .Testing is a process of making sure that the program performs the intended task, so in this case the task was that the patients electronic health recorded is being established which could be viewd by anyone when necessary. MEDITECH-MEDICAL INFORMATION TECHNOLOGY, INC Qe MAINTANENCE Meditech has brought many changes. developing various modules of software for the health industry like they released a pharmacy system, followed in the next 10 years by modules for payroll, radiology, account payable, blood bank, nursing, and materials management. Many other subsystems for the health care industry followed. MANAGEMENT INFORMATION SYSTEM 7a oe b-6 vd YFIO1®S be THANK YOU PRESENTED BY- IRISHA TANEJA(2K2!/BBA60) KHUSHI JAIN(2k21/BBA/72) PRASHASTI VERMA(2K2!/BBA/102) RIBHAV MANGLA(2K21/BBA/I18) SYEDA SABA QUASAR(2K21/BBA/153)

You might also like