Chapter 5: Planning for Software Project Risks 119 (Web site developers)
Chapter 5: Planning for Software Project Risks 119 You can find dozens of software development models. Each of them has pros and cons, but one thing is always true: Whichever model you use must be accepted and followed by everyone, from the management team to the project team and the stakeholders. It doesn t do anyone much good to have a model and not follow it. The following sections describe the most popular software models on a continuum from risk-enriched models (high-risk approaches) to risk-averse models (relatively risk-free approaches). There s no such thing as an organization that doesn t have a software development model. Even if it s patched together and made up as the project moves along, it s a model. The point of any model is to reduce the risk of failure. Using the waterfall model If you ve ever taken a programming class, you ve encountered the classic waterfall approach to programming. In case you were lucky, and never had to take a programming class, here s the deal: The waterfall model uses a series of phases to move the project along. Each phase creates a deliverable, usually a document that captures what the phase has accomplished. Figure 5-3 shows the progression of the model. Concept Phase Requirements Phase High-Level Design Detailed Design Phase Implementation Phase Testing Phase Project Release Figure 5-3: The waterfall model follows a series of phases to reach completion.
Note: In case you are looking for affordable webhost to host and run your servlet application check Vision ecommerce web hosting services