——_— aes 1.5.1 Prototyping Model The Prototyping Model is a software development model that involves the creation of a p ary version of the software, called a prototype, which is used to gather feedback and refine requirements before the final version of the software is developed. The prototype is developed based on initial © scanned with OKEN ScannerSoftware Engi irements and design specications and is used to obtain feedback from stakeholders, Setbacks thon used to refine the requirements and design specifications before the final v eFSioy the softwares developed, The Prototyping Model issuable for projects where requirements ar, well understood or are likely to change during development and where stakeholder involvemen, the development process is high. = Me is Prototype? Bxplain with examples, A prototype isa preliminary version of a product or system that is used to test an the final version is developed. In software development, prototypes are often from stakeholders and refine requirements before the final version of the so! Here are some examples of prototypes in different fields: 1. Product Design: A company wants to develo} refine its design befor, used to gather feedbac, ftware is developed, P anew type of bicycle helmet. They createa prototype that includes basic features such as size, shape, and materials. The prototype is tested by cyclist to father feedback and refine the design before the final version ofthe helmet is developed 2, Architecture: An architect wants to design a new building for a client. They create a Prototype that includes basic features such as size, shape, and layout. The prototype is tested by the clien to gather feedback and refine the design before construction begins on the final version of the building. 3. Automotive Design: A car manufacturer wants to develoy a prototype that includes basic features such as size, is tested by drivers to gather feedback and refine the version of the car. Pa new type of electric car: They create shape, and battery capacity. The prototype design before production begins on the final ‘4. Software Development: company wants to develop a new mobile app for their customers They Greate @ Prototype that includes basic features such a user interface design and functionality. The Prototype is tested by customers to gather feedback and refine requirements before development begins on the final version of the app: ° . ‘The Prototyping Model is a software development model(that involves the creation of a preliminary version of the software, called a prototype, which is used te gather feedback and refine requirements ‘before the final version of the software is developed. ‘The prototyping 1 : Prototype Development and-Itesati Development: Pratotype Development focuses on creating and refining the prototype to ensure rear he Sakehalders' expectations, while iterative Development falleve sky lassical or iterati Waterfall model, including stages like design, implementation, testing, deploymebt, and maintena® to deliver a quality software, at tate le a: sivapli ied version at of prrdtte ct /sy tes WS udag dived peer ee 5 bul @ mate 4p FCs Goto feedboel belae Dt tal An at ; CE OSs © scanned with OKEN Scanner used‘gonpoad peuyy a4 Jo uo paseq ad&ior0.d | oe aats 07 saamyra) 1ey40dU] 380 pur ypeqpaay apiao. 1 addyoyoad aty Jo asodnd of au, :pauyap AIny aq 10U qeseuaél at AsnuapL Aoyy, “suai. oisian umop-padduns e Aipensn st adAorosd au, “uBisap yomb ayy air ayy spying wear quaudojadap ayy ? ed4o70.1g ay) Supjmg > ‘squawiouyad Joyzany 10) ionpo.d ayy Jo woReyuasasdas 2q/3ue} & ssopjoyaxers | padojaaap Appinb aq 01 yfnoua ojduys aq pue pinoys ufisop ot, ‘swautazinbas pasoyred axp uo p joinb ev sawwos9 tied) juourdojanap ay, : UBIsaq yoInd -q adfonoud jentuy ue pling 0) VoReULIOsU! YBNoUe soYRe8 Aout soyioads ayy ing “ayeuonsuny pue seanzalqo bos aremyos arp aZéfeue pue 399I]09 01 1943080) adojaaap ‘afters sup uf: sisAqeuy pue Sujsoyje9 juouosmbay “E dAioi01d won saad, stop lo%ax/e3 48 oY] SJaU If aINSUA Oy ay out ayy UO SNI0} “stuauiaambas pur vai wo sasnaoy aseyd Siy,,¢ jeudoyesag adfyowosg *T yor pue Bury jopow SupdAyor044 wy sofleas 10 saseyd 9°T 24nBtd Proceaonuren \ quaudodog quaudojeaag anes] uonequourajdiy saworsns £4 aouendasoy speapaed pue wonenjeag Juouousod pue uones2iI @ scanned with OKEN ScannerSoftware Engineerting focusing on the core functionality and ser interface. The goal is to create a wo; that can demonstrate the key features to stakeholders and users for their e 4. Evaluation and Feedback : The prototype Is presented to stakeholders users for evaluation, They provide feedback on the functionality, usabili of the prototype. Their input is essential for identifying issues, gaps, and Poten, improvements. king, Vallation, and poten, Y, aNd doy ¢. Iteration and Refinement : The development team reviews the fe necessary changes to the prototype. They may need to modify th features, or remove unnecessary ones based on the input received. TI ~-Continues until the prototype meets the stakeholders’ expectations a 2, Iterative Development: Once the prototype is finalized, the to the Iterative Development phase, which includes the stage or iterative waterfall model, a. Design Phase : With the approved Prototype, the development team creates a detai design for the final product, incorporating all the desired features, optimizations, » improvements identified during the prototyping process. This design serves asa bluepr for the implementation phase, ensuring that the final product meets the stakeholde, expectations, a >. Implementation : The development team starts implementing the ful Product by translating the design into source code. ‘They ensure that al and functionality are included, Testing : After the implementation is complete, thesoftward) goes through a rigora testing phase. This includes unit testing, integration testing, system testing, and w ‘acceptance testing. The goal is to i identify and fix any bugs, performance issues, inconsistencies before deployment. = 4. Deployment : After the software has been thoroughly tested and all issues have be resolved, it is deployed and made available to end-users, This may involve installingt software on users’ machines; distributing it through app stores, or making it accessit via web browsers, edback and ma, e design,add 5, is iterative prog, nd requirement, development process transi, s commonly found in the class, Maintenance :\The development team continues to monitor the software, providi updates, bug fixes, and support as nected ‘They may also gather feedback from users identify areas for improvement and plarfuture enhancements, An example use case for prototyping model could be developinga new mobile app foran e-commerce compa ‘The company has identified that they need an app to improve thelr customer experience but they ae nots what features should be included int They decide to use prototyping model to develop an initial version of app to gather feedback from customers and refine requirements before developing the final version, In the requirements gathering phase, the development team works with stakeholders to identify in equirements for the app. Based on these requirements, a preliminary design specification is created for prototype, © scanned with OKEN Scanneriow 1 esign phase, a simple mockup of th cpreroPE ip of the app is create pees ros asic ates Such a produit stings anda Font ce eee «construction phase, developers use rapid applicati mn nthe prot : : ipid application develo, of the app. TI a pment tools to qui i erent versions Of pp. This may involve creating multiple prototypes with iter sry loan! test ro gui feedback rom customers different Features or [pavantages ‘of Prototyping Model 4, continuous Refinement : The prototyping model allows for ongoing improvement ‘of requirements juirements throughout the development process: 2, Stakeholder ¢: Ieencourages ative participation fom stake are met and expectations aligned. +holders, ensuring their needs 4, Barlylssue Identification The model helps detect and addressissues costly changes later in the development process. 4, Faster Time-to-Market : Quick feedback and iteration eycles enable reduced time-to-market forthe final product. 5, Cost Reduction : Barly issu become more expefisive to fi & enhanced Communication : The mode developers, stakeholders, and users. 7, User-centric Development: By actively involving users in the de' trode results ina more user-centric and satisfactory final product. Involvement carly, reducing risk and avoiding identification helps minimize costs by addressing problems before they | fosters better understanding and collaboration between syelopment process, the prototyping, er] Disadvantages of Prototyping Model Zinereased Costs; The prototyping model cl the time and resources Spent on creating and refining prototypes: model is most e zene Risk Identification : The prototyping wove development starts Iemay not be suitable for Projects with rs be identified be the development process. an expanding list of features 0 increase development costs due to sfective for projects with risks that can ks that occur later in feedback from stakeholders can lead to _ AGoove Creep : The constant ‘changes, making it challenging to manage the project scope and stay on schedule. : The rapid prototyping approach might result in Jess thorough potentially causing issues or missed requirements In the final |_ 4 Insufficient Requirement Analysis analysis of the software requirements, product. - Mr to choose Prototyping Model? The prototyping model is most suitable for softwar: + Unclear Requirements : When the projec' prototyping can help in clarifying and refining the + High User Involvement : Ifa project benefits fro the development process, the prototyping model encou's stakeholders, and developers. under the following conditions: ‘e development projects +t requirements are aml well-defined, ese requirements through m strong user engagementand input throughout fllaboration between SETS: © scanned with OKEN Scanner“AraATjap [eJUaWIa.19U! pure ‘UOHoNpal ASHI ‘JUouTaaoaul Jowoysnd ‘Atqrayg syioddns yey) quauidojaaap aremyos 0} yoeoidde [njzamod e SI [apo a9AD ast] Areuomnyoag ayy, | ‘Squeurazinbe. pue suoneedxa Jasn yim susie jonpo.d [euy ay} IBY} Samsua sjuauysn{pe Axessaoou Suppeul pue yeqpaaj Jaw0ysnd Supesodioout jo ssas0id aaneiall SITY, ‘a{npowul yea Uo yoeqpaey aplAoid pure matAad 0} wWayy SUIMoTpe ‘eum eye BuO JaUIO}SNd ay] 0} pasaaljap aie SJUSWIIAIU! aSay,], ‘AALMIOS AY} JO UOTS.1BA aya{duios asou e o7uI pues wat? st uolaays jNpold [LIU] BY, ‘Se|NPOU 18470 ay} WO.Y Sa2[A1as paaU JOU Op JEU} asolpy ae wry ‘wiaisAs ay) Jo safnpout aoo ay) sdojaaap ysay wes} juawdoyaaap ay, ‘paraatjap pue paynnsuod Ayyequawa.19ul aq Ued Jey} Sa[NpOUl [elaAas 0JUI UMOP UayYO.1 SAY oie squawermbal aremyos ay “spaau SuLajoaa YIM sya[o1d 10J ao}oyp [eap! ue I BupyeU ‘s.10}9ej 1940 PUe yoeqpeay Jest 03 anp sjuewiaimnbes aremyos ur saSueyp sayepoumwoore poyjeuu SITY, “ew JeA0 JOUUeUT jequautetout e ul Wasfs ay] BSULIaAIap SaAjOAU! [apow 9]IA) ayrr] AreuoNNOAT o4L quaurdojeaap azemyos J sjapOll feyUautas9Uy pur [[eJ.19yeM SAT eAaI] JO UOTEUIGUIOD B SI [EPO 2194) AIT Axewonn[ond ou j2pow Aapuoiynjorg 2°S°T @ scanned with OKEN ScannerSottwore Engineers ch that combines erative sw soars development spp te sa, trem moe ett star, Ths model perlary usta for eee ea change fun oF Whe ter GedN pay a signet role shaping the Bhar ee in fae sofarinnaternr neds ning anapndng pon henna bared enue eeck altar eangtoacomplte si palhedsohieegee a volutes, ede prometes eb, custome invlvoment isk reduction The Evolutionary Mode consists of several phases that heh that the final software product is user-friendly and me Ip guide the development, ets customer requireme: phases or stages in evolutionary model are shown below: 1. Rough Requirement Analysis and 5 Process, ensyr, ents. The diffe, Pecification : The first stage involves basicneeds and requirements ofthe software project. This includes discussing with custome, sathering their ideas, and creating a rough outline of what the software shocys do. 2. Identify the Core and other parts to be Developed Incrementally : team breaks down the soft understanding, process involves planning, uilding, and testing the core part until it meets t desired level of quality and functionality. 4. Collect Customer Feedback : the team shares it with the his helps identify any necessat changes or improvements to better meet the customer's needs 5. Deliver the Core or Base Partto the Custo1 to customer feedback, it is delivered to the Develop the Next Identified Features using an Iterative Waterfall Model : The team move on to develop the next set of features or functionalities, They continue to use the iterativ waterfall mode! to plan, design, build, and test each feature, 7. Repeating Feedback and Development Loop : The Process of collecting customer feedbact modifying requirements, and developing new features Continues in a loop until all the desire! features have been added to the ‘software, mer : Once the core parthas been refined accordit customer as a foundation for the final product. | the focus shifts to maintaini ¥y bugs, performance issues, volves providing ongoii 1. Flexibili evolving 2. Custom develop) 3. Risk Re Aikeltho 4, Increm develo} 5. Easier errors 6. Impre custor 7. Bette resou © scanned with OKEN ScannerEEE Rough Requirement Analysis & Specification Identify the core and other parts to be developed incrementally eee Develop the core part using an iterative waterfall model a Collect Customer Feedback and Modify the Requirements Delivery of the Next version to the Customer Develop the Next Identified Features using an Iterative Waterfall Model a 7 All features complete en, Maintenance and Updates Figure 1.7 Phases or Stages in Evolutionary Model Advantages of Evolutionary Model Flexibility : The model easily adapts to changing requirements, making it ideal for projects with evolving needs or uncertain specifications. . Customer Involvement : The model encourages regular customer feedback throughout the development process, ensuring the software aligns with user expectations and requirements. Risk Reduction : Identifying and addressing issues early in the development process minimizes the likelihood of major problems arising later in the project. Incremental Delivery : The delivery of smaller increments builds cus! development team’s ability to meet project goals and deliver a high-quality product. 5. Easier Error Detection : The iterative nature of the model allows for early detection and resolution of| 3, tomer confidence in the * errors, leading to a more robust and stable final product. 6. Improved User Satisfaction : By incorporating user feedback and mo customer needs, the final product is more likely to satisfy user requirements. sdifying the software based on ter utilization of| 7. Better Resource Allocation : The incremental development approach allows or el esources, as developers can focus on specific modules or features ata time. © scanned with OKEN ScannerDisadvantages of Evolutionary Model = — Tnadequate Planning : rs a ig The modeTs enbiiy can sometines ead to insudent planing wih: op repre sncapiset ‘whi gop represents phase of cause issues in project management and th resource allocation Scope Creep : The continuous feed a c jus feedback loop may lead to ft can vary from press ioP een rae 1 lead to frequent changes In Fequlrements, x project scope to expand and potentially delay the project: aan wat is Spiral on Customer Feedback : The model relies ‘heavily on ct > ‘lear, or timely, affecting the development process. mn : Due to the iterative and be updated as frequently, process may require more resources sustomer feedback, which may _the Spiral Models 50 vail model ant ed by Dr! do 3, Dependency always be available, 4. Incomplete Documentatio! may be overlooked or may not 5. Higher Costs : The iterative development higher costs compared to other models: 6. Complex Management : Managing the iterative pro challenging, requiring strong. project management skills. ‘ot be suitable for projects with well-defined and 7, Limited Applicability + The model may n requirements or when theres. Timited scope for customer involvement durin development. — tern cetetionary Motel? <= tionary Model shou re not wel fers to receive the prod twas introdu evelopment meth ‘adaptive nature of the model, documenay, reading to inconsistencies. and time, leading cess and constant changes in requirements a ‘The Spiral Model consis fe Fanning {ladensty Obiect ig situations: Snd Constratnts) ‘The Evol! Id be considered in the followin change during development. 4, Requirements 2 41 understood or may uct in increments rather than waiting forthe fll produ 2. The customer pref fo be developed and delivered: {eis easier to find modules for incremental implementation. 43, The project is large and JL The customer wants t0 Start using different features as and when they are delivered. vs When there isa need for Benen risk management by identifying issues early on the developmet ae process. «6. when there isa need for Ft" time-to-market by adding features incrementally 7, When there isa need for improved quality by incorporating feedback from stakeholders and vs Throughout tne dove Op ets rocess. = Eval -nmants of the Cla8*" (es © scanned with OKEN Scanner