V-Shaped SDLC Model
Jump to navigation
Jump to search
A V-Shaped SDLC Model is a systems development lifecycle model that ...
- Example(s):
- Counter-Example(s):
- See: Systems Development Lifecycle, Computerized System Validation.
References
2020
- (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/V-Model Retrieved:2020-10-2.
- 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. [1] 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 creation of system specifications. The right side of the "V" represents integration of parts and their validation. [2] 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 (e.g. FEM). This can partially be done at the left side also. To claim that validation only occurs at the right side may not be correct. The easiest way is to say that verification is always against the requirements (technical terms) and validation always against the real world or the user 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 by the query "Are you building the right thing?" and verification by "Are you building it right?" ...
- 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. [1] 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 creation of system specifications. The right side of the "V" represents integration of parts and their validation. [2] 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 (e.g. FEM). This can partially be done at the left side also. To claim that validation only occurs at the right side may not be correct. The easiest way is to say that verification is always against the requirements (technical terms) and validation always against the real world or the user 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.
- ↑ "The Dangerous & Seductive V Model", accessed January 9, 2013.
- ↑ Forsberg, K. and Mooz, H., "The Relationship of Systems Engineering to the Project Cycle" , First Annual Symposium of the National Council On Systems Engineering (NCOSE), October 1991