《RapidApplicationDevelopment》由会员分享，可在线阅读，更多相关《RapidApplicationDevelopment（16页珍藏版）》请在金锄头文库上搜索。
1、Rapid Application Development(RAD) BY: T.N. Patikitrikorala(030271)C.I Arambewela(030030)Software Engineering Assignment 1Development Methodology lRAD (Rapid application development)lJAD (Joint Application Development ) Methodology that involves the client or end user in the design and development o
2、f an application, through a succession of collaborative workshops called JAD sessions. Compressing the analysis, design, build, and test phases into a series of short, iterative development cycles.Iterative Development ProcesslTwo types of ModellIncremental deliverySpecification, Design, and impleme
3、ntationare broken in to series of increments and done in turn.lSpiral developmentProcess is represented as a spiral. Each loop of the spiral show a phase of software processes (e.g.: feasibility , requirement gathering).An Iterative Development process CycleIterative Development Process modelAdvanta
4、ges of using Iterative processlUser engagement with system.lUsers of the system have to provide feedback to the development team for the each increments they . lAccelerated delivery of customer.lNormally early increments are high priority Functions, so customers a get value from the system early in
5、its development also can specify changes. Fundamental Characteristics of RADlProcess specification ,design and implantation is done Concurrently.lSystem development is done in a Series of increments.lUser interfaces are often developed using Interactive development systems. (RAD uses specialized too
6、ls that support interface development)Problems addressed by RADlWith conventional methods, there is a long delay before the customer gets to see any results.lWith conventional methods, development can take so long that the customers business has fundamentally changed by the time the system is ready
7、for use.lWith conventional methods, there is nothing until 100% of the process is finished, then 100% of the software is delivered.Why should we use RAD?lto converge early toward a design acceptable to the customer and feasible for the developerslto limit a projects exposure to the forces of changel
8、to save development time, possibly at the expense of economy or product qualitylYou should NOT use RAD to lto prevent cost overrunslto prevent runaway schedules Tradeoffs faced in RADlTradeoffs between Schedule, Product and economy is inevitablelRAD focuses on Schedule more, thus Product quality and
9、 Economy must be traded off What cannot be achieved through RAD?A Product with lthe fewest possible defectslthe highest possible level of customer satisfactionlthe lowest development costsWhen to use RADlThe application will be run standalone.lMajor use can be made of preexisting componentslPerforma
10、nce is not critical.lProduct distribution will be narrow (in-house).lReliability is not critical.lSystem can be split into several independent modules.When not to use RADlApplication must interoperate with existing programs.lFew plug-in components are available.lOptimal performance is required.lProd
11、uct development cant take advantage of high-end tools (e.g., 4GLs).lProduct distribution will be wide (mass market).Advantages of RADlEarly visibilitylGreatly reduced manual coding lIncreased user involvement lPossibly fewer defects lPossibly reduced cost lShorter development cycles lStandardized lo
12、ok and feel Disadvantages of RADlBuying corporate software components could be costlylApplication is less efficient and less preciselMay accidentally empower a return to the uncontrolled practices of the early days of software developmentlMore defects possiblelReduced featureslReliance on third-part
13、y components may .lsacrifice needed functionalityladd unneeded functionalitylcreate legal problemslStandardized look and feellSuccessful efforts difficult to repeatAnd finally. An brief overview of the essential aspects!lToolslPeoplelMethodologylManagementReferenceslSoftware Engineering Sommerville; seventh edition; Pearson Education. Chapters 4,7. lhttp:/csweb.cs.bgsu.edu/maner/domains/RAD.htmlhttp:/www.dacs.dtic.mil/awareness/newsletters/technews2-1/rad.htmllhttp:/sysdev.ucdavis.edu/WEBADM/document/rad_toc.htm
