Back V-Model Afrikaans نموذج V Arabic Model V Catalan V-Modell German Método en V Spanish مدل-وی Persian V-malli Finnish Cycle en V French Model V ID V-Model Italian
| Part of a series on |
| Software development |
|---|
The V-model is a graphical representation of a systems development lifecycle. It is used to produce rigorous development lifecycle models and project management models. The V-model falls into three broad categories, the German V-Modell, a general testing model, and the US government standard.[2]
The V-model summarizes the main steps to be taken in conjunction with the corresponding deliverables within computerized system validation framework, or project life cycle development. It describes the activities to be performed and the results that have to be produced during product development.
The left side of the "V" represents the decomposition of requirements, and the creation of system specifications. The right side of the "V" represents an integration of parts and their validation.[3][4][5][6][7] However, requirements need to be validated first against the higher level requirements or user needs. Furthermore, there is also something as validation of system models. This can partially be done on the left side also. To claim that validation only occurs on the right side may not be correct. The easiest way is to say that verification is always against the requirements (technical terms) and validation is always against the real world or the user's needs. The aerospace standard RTCA DO-178B states that requirements are validated—confirmed to be true—and the end product is verified to ensure it satisfies those requirements.
Validation can be expressed with the query "Are you building the right thing?" and verification with "Are you building it right?"
- ^ Clarus Concept of Operations Archived 2009-07-05 at the Wayback Machine, Publication No. FHWA-JPO-05-072, Federal Highway Administration (FHWA), 2005.
- ^ "The Dangerous & Seductive V Model" Archived 2019-09-15 at the Wayback Machine, accessed January 9, 2013.
- ^ Cite error: The named reference
VPMwas invoked but never defined (see the help page). - ^ Cite error: The named reference
INCOSEwas invoked but never defined (see the help page). - ^ Forsberg, K., Mooz, H. (1998). "System Engineering for Faster, Cheaper, Better" (PDF). Center of Systems Management. Archived from the original (PDF) on April 20, 2003.
{{cite journal}}: Cite journal requires|journal=(help)CS1 maint: multiple names: authors list (link) - ^ "The SE VEE". SEOR, George Mason University. Archived from the original on October 18, 2007. Retrieved May 26, 2007.
- ^ Forsberg, K. and Mooz, H., "The Relationship of Systems Engineering to the Project Cycle" Archived 2009-02-27 at the Wayback Machine, First Annual Symposium of the National Council On Systems Engineering (NCOSE), October 1991