@ the modaiity is | if an occurrence of the relationship is mandatory. Differentiate between waterfall and incremental model. (any four points) Sr. No Waterfall Model Incremental Model Traditional model which activities follow sequentially Incremental model delivers series of releases called increments. caste Users explicit prescription of requirements is essential at the start of development Prescription of each increment is essential at the start. Additional functions and features can be added in subsequent increment Time consuming model and hence customer must have patience. Customers get quick releases with each increment and hence scope for feedback and improvement Waterfall model is inappropriate for applications in which customer requirements keep changing. Model combines the elements of waterfall model in an iterative fashion. Hence can accommodate changes during development Development team size is large Development team size is small If technical errors in the development go undetected, project may be delayed or in case of major blunders results can be disastrous Due to incremental nature, technical risks are reduced. Advantage of prompt delivery to users without hastle. If any error occurred in any level it will affect outcome of all other subsequent levels. If any error occurred can be rectify in next increment. 11/26 Backtracking is tedious as one has to restart project. Backtracking can be done for uncovered errors in next increment.| Answer any ONE of the following: “With neat diagram , explain RAD model with its advantages and disadvantages.(2 each) Rapid application on Development (RAD) is a moder software process model that ‘emphasizes a short development cycle, The RAD Model is a “high-speed” adaptation of the waterfall model, in which rapid development is achieved by using a component based Construction approach. If requirements are well understood and project scope is Considered, the RAD process enables a development team to create a “Fully Functional System’ within a very short period of time (e.g. 60 to 90 days). One of the distinet features of RAD model is the possibility of cross life cycle activities which will be assigned to teams, teams #1 0 team fn leading to each module getting developed almost simultaneously. This approach is very useful if the business application requirements are ‘modularized as funetion to be completed by individual teams and finally to integrate into ‘complete system. As such compared to waterfall model the team will be of larger size to function with proper coordination. RAD model distributes the analysis and Construction phases into a series of shor iterative development cycles. The activities of teach phase per team are Business modeling, Data modeling and process modeling. This, model is useful for projects with possibility of modularization. RAD may foil if ‘modulasization is difficult, This model should be used if domain experts are available With relevant business knowledge. Communication works to understand the business ( eee MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION, asec 001- 2008 Certs) WINTER~ 16 EXAMINATION Model Answer Subject Code: 175: problem and the information characteristics that the software must accommodate. Planning is essential because multiple software teams’ work is parallel on different system functions, Modeling encompasses three major phases ~ business modeling, data ‘modeling and process modeling- and establishes design representations that serve as the basis for RAD's construction activity. Construction emphasizes the use of pre-existing. software components and the application of automatic code generation. Finally, deployment establishes a basis for subsequent iterations, if required, Advantages: 1. Changing requirements can be accommodated and progress can be measured, 2. Powerful RAD tools can reduce development time. 43. Productivity with small team in short development time and quick reviews, risk control increases reusability of components, better quality 4, Risk of new approach only modularized systems are recommended through RAD. 5, Suitable for scalable component based systems. LimitationyDisadvantages: I. RAD model success depends on strong technical team expertise and skills. 2. Highly skilled developers needed with modeling skills. 3. User involvement throughout life cycle, If developers & customers are not committed to the rapid fire activities necessary 10 complete the System in a much-abbreviated time frame, RAD projects will fail. 4, May not be appropriate for very large scale systems where the technical risks are high,reve mt uae ther Aldo mae wh id + Baie psig tse guess oy, ‘ete deem teach parm i mane, ‘tere eto em. -TeeSeon Pai KISS Keep Simple tpi Alege soul ea ple pst inlet Ta ‘eating ere) drole) mated +z nt ors hole dca in he ee of sini 1+ Sino bss mein “uk a dey” In at taten fle io ugh an wt ver mail ern ‘yt. ‘Te Third Prince Maan the Vien ‘yum il weuen awl eeay wear re be 8 Seton + Hang yomer nc white ‘Tee Foerih Principe: Wht You Prats Others We Conse Always spc deg pleat yeep mi hat tometer lcd vary oe + These fr any po oft depen pov ge + ose at desig. Aig geen ogre) Cee it + Scnmoe my aves ghd ou rea at es Tern Pepe: Be Ope tothe Pte ‘+ Acjtem vit gifting ha me + Trends eg wars st at rn + Tedisco. ie ses a Beja conse Ales awa an peur fal posible ers by aap een the pa ‘Te Sia Pini Pes Abad or Rea 1 Tepe of dead deg ea hector ects Ping he! for ee es host rete el ‘foun mat oagoer ahem re ey cima Te Seventh ene Tn! "Peng comple ih oe tn am aye ‘ms er 1+ Won you ta batsmen yous mre ey do ‘Yous pan noe shat a “+ youn stot some ntl > weg bm + apie iri me grT ‘Attempt any Five of the folowing: TM ‘iteren * Into activities, high quality i achieved trough good design, ‘but the manufacturing phase for hardware can itodce quality problems hat are nonexistent (o eal comected for software Both actives ae dependent on people but the relationship teween people applied and work accomplished is entirely siren, 1 Softvare costs ar concentrate in engineering. This means that software projects cannot be managed af they were manufacturing projects 2, Software doesn't “wear ou.” eed 7 a ae ae eee ‘acon ima ste tears |e « ——o 1+ The idealized curve as sown in above figure ia gros ‘oversimplifcatin of actual failure model for software However, the implication i clear— software doestt wear out uti des detrioete! ‘This contradiction can best be explained by considering he “actual curve shown ia Figure Daring its life, software wil undergo change (intenance). As changes are made ts key that some new defects willbe inroduced. causing the failure rate curve to spike a shown in Figure. 1 Bofors the curve can eur othe orginal steady-state ure rae, another change is requested, causing the curve to spike ‘again. Slowly, the minimum failure ae bevel begins to ise—the Software is detenorating due to change. 43. Although the industry is moving toward component-based ‘construction, most software continues o be exsom bul ‘+The reusable componoms have bee created so thatthe engineer «can cncentate onthe Wuly innovative element oa desig tht is the parts ofthe design tht represent something n=, 1 Inthe softare worl is something tht has ony beguo to be ‘chieved ona broad scale. A software component shouldbe ‘O It is easier to test and debug during a smaller iteration. In this model customer can respond to each built. Lowers initial delivery cost. Easier to manage risk because risky pieces are identified and handled during it’d iteration.Vv 0 0 1.1k views ‘e identified and handled during it'd iteration. Disadvantages of Incremental model:- Needs good planning and design. Needs a clear and complete definition of the whole system before it can be broken down and built incrementally. Total cost is higher than waterfall. When to use the Incremental model:- This model can be used when the requirements of the complete system are clearly defined and understood. Major requirements must be defined; however, some details can evolve with time. There is a need to get a product to the market early. Anew technology is being used. Resources with needed skill set are not available. There are some high risk features and goals. rar COcnitT293 views Prototype Model: The basic idea in Prototype model is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is developed based on the currently known requirements. Prototype model is a software development model. By using this prototype, the client can get an “actual feel” of the system, since the interactions with prototype can enable the client to better understand the requirements of the desired system. Prototyping is an attractive idea for complicated and large systems for which there is no manual process or existing system to help determining the requirements. Diagram of Prototype model: Am of a Doe [tes] Sone row so] | a < Eagar Patt |g. Refiong ‘Cosomer | Prone eatoanon Prototyping Mode! ee ee ee eeeAdvantages of Prototype model: « Users are actively involved in the @) development Since in this methodology a working 1 model of the system is provided, the users get a better understanding of the 293 system being developed. views « Errors can be detected much earlier. * Quicker user feedback is available leading to better solutions. « Missing functionality can be identified easily * Confusing or difficult functions can be identified as Requirements validation, Quick implementation of, incomplete, but functional, application. Disadvantages of Prototype model: ¢ Leads to implementing and then repairing way of building systems. Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond original plans. Incomplete application may cause application not to be used as the full system was designed « Incomplete or inadequate problem