V-MODEL OVERVIEW- Testing is not an isolated event, but an ongoing quality process.
The V-Model framework is a structured testing approach that can be used with any project management or system development methodology. The framework emphasizes quality from the initial requirements stage through the final testing stage. It focuses on testing throughout the development life-cycle, early development of test requirements, and early detection of errors. Each major deliverable in the development process is assessed, verified, validated and tested.
-Verification- Checks that a deliverable is complete (contains all requires information, follows standards)
-Validation- Checks that the deliverables satisfy requirements specified in the previous stage or an earlier stage, and that the business case is met.
-Testing- Ensures that the specification is properly assembled and implemented.
The deliverables of each stage need to be verified and validated to ensure that they are complete and correct. Work proceeds to the next stage in the V-Model when all project deliverables in a stage have met all verification and validation requirements. The process of verification and validation is an attempt to catch as many errors as possible within the development life cycle, otherwise know as “stage containment”. Each successive stage of testing ensures that the specifications defined in the deliverable of the corresponding stage have been implemented. This is achieved by the early development of test requirements.
V-MODEL descriptions-
**Responsibility of developers/project management or business analyst:
1) Business Case- The goal of the business case is to define the opportunity and reasons why management may accept the undertaking of a systems development or enhancement project. These business case objectives and descriptions provide the basis for the business assessment.
2) Business Scope Assessment- The goal of the business assessment is to develop an assessment of the gap between the original business need and the current systems environment, including identification of each affected system. These high level business requirements provide the basis for the conceptual design.
3) Functional Requirements Definition & Functional Design- The goal of the functional design is to develop specific functional and technical requirements for all impacted functionality. The specific functional and technical requirements provide a basis for the detailed design.
4) Detailed (Technical) Design- The goal of the detailed design is to develop detailed program specifications derived from the functional and technical requirements. The detailed program specifications provide the basis for all build activities.
5) Component/Unit Test- The goal of the component test is to code and test changes of an individual module, program, or component, to demonstrate that the work package implements the requirements according to the design specification. The component testing includes unit tests and client/server component testing (more of a technical-test in nature).
**Responsibility of testers and QA management:
6) Application Test- The goal of the application test is to deliver an application of functionally defined set of system components that satisfy all design requirements. That is, by which the pieces of the unit testing functionality are strung together to complete the assembly test process.
7) System Integrated Testing- The goal of the integrated test is to confirm that the working applications, or group of components, can be fully integrated to satisfy functional, technical, and quality requirements. Stress testing is another element that may be performed during this cycle.
8) User Acceptance Testing- The goal of UAT is to confirm that the systems will function within the business environment and deliver all user requirements within that environment. Formal sign-off is included in this stage.
Other issues:
So how will we know when all these deliverables and test information is ready for review and assessment?
In coordination with project management and QA management, a detailed project workplan is developed as part of the
pre-Vmodel tasks. The project workplan lays out a timeline of tasks, due dates, statuses, based on the determined date of
implementation. Weekly meetings with appropriate associates will assure timely completion of their appropriate tasks, and
thus, the V-Model stages will progress properly.
Continue to my resume page
Back to ProcessIT Consulting homepage
