四川大学软件工程课件 Unit02_2.pptVIP

*/23 Prescriptive Process Models */23 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering */23 The Waterfall Model Pro: the most widely used model; a template for use Con: inflexible to changing customer requirements This is a good model to use when requirements are well understood */23 Incremental Models Incremental Model: delivers software in small but usable pieces, each piece builds on pieces already delivered Rapid Application and Development (RAD) Model: makes heavy use of reusable software components with an extremely short development cycle */23 The Incremental Model delivers software in small but usable pieces, each piece builds on pieces already delivered */23 A software project has significant functionality but big pressure on short time-to-market….. How does the incremental model help to deliver this software by the business deadline? Example: A word-processing software I: basic file management, editing, document production II: more sophisticated editing and document production III: spelling and grammar checking IV: advanced page layout capability */23 The RAD Model The RAD model is a high-speed adaptation of the linear sequential model. Project requirements must be well understood and the project scope tightly constrained Developers can use component-based construction techniques to build a fully functional system in a short time period Pro: may shorten development time significantly Con: the system may not be modularized for use; performance issue; risk issue */23 The RAD Model makes heavy use of reusable software components with an extremely short development cycle */23 Assumptions of using RAD model for software project development: A project can be modularized Major functionality could be delivered in short time Sufficient human resources will be available */23 Evolutionary Models Prototyping Model: good first step when customer has a legitimate need, but is clueless about the detai