V-Shaped Software Development Life Cycle Model

Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis on verification and validation. Testing is discussed, designed & planned in early phases. Testing phases are considered in parallel to designing.

V-Shaped Software Life Cycle Model Project and requirement planning Product requirement &specification analysis Architecture or High level Design Detailed Design Coding Unit Testing Integration & Testing System & Acceptance Testing Production, Operation & Maintenance

Phases : Project and requirements planning : Determine system requirements and allocate resources Product requirements and specification analysis : Software problem, specification of external behavior Architecture or high level design : Software functions.

Detailed design : Defines and documents algorithm. Coding: Algorithm into software. Unit testing : Checks each code module. Integration & testing : Interconnects sets of module.

System and acceptance testing : Entire software in its actual hardware environment. Production, Operation & Maintenance : Enhancements and corrections. Acceptance testing : Allows the user to test.

Strengths : Matching the test phase with development process. Verification and validation of all internal and external deliverables. Definition of requirements before designing. Designing the software before building. Track progress accurately using timeline. Easy to use.

Weakness : Does not handles : –Concurrent events. –Iterations of phases. –Dynamic changes in requirements. –Risk analysis Requirements are tested too late.

When to use : Addition of iteration loops. Requirements are available up-front. Knowledge of implementation, technology and staffing is available. For system that requires high reliability.