Chapter 5: Planning for Software Project Risks 123 (Web site domain)
Chapter 5: Planning for Software Project Risks 123 Figure 5-5: The V model uses a series of tests for each completed phase to move the project forward. Using the V model This model is called the V model because, well, because the progression of the project forms a V. Look at Figure 5-5; see the V? This is a risk-averse development model because the completion of each phase prompts a corresponding test phase. Before the project moves forward, the test must be passed. This model is technically an expansion of the waterfall model, with added verification and testing. Like the waterfall model, each phase creates documentation of what s been completed in the project. Here s a breakdown of the V model progression: 1. Set the project requirements. The project requirements are identified and agreed upon by the project manager, the project sponsor, and other key stakeholders. 2. Design the architecture. The requirements are decomposed into functions and system components, and the project estimates for time and costs are updated. The refined estimates must be approved by the customer or the project s management team before the project moves forward. Requirements Phase Architectural Design Phase Detailed Design Phase Implementation System Test Phase Integration Test Phase Unit Test Phase Requirements Functional Specs Design Specs Code Unit Test Records Integration Test Records System Test Records verifies verifies verifies
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision j2ee hosting services