V-Model is the third Traditional Software Development Method (Waterfall is the first one and the Spiral is the second one)
“The V-model is an internationally recognized development standard for IT systems which uniformly and bindingly lays down what has to be done-Procedure, how the tasks are to be performe-Methods and what is to be used to carry this out-Tools.
3 Levels of V-Model:
- Software Lifecycle Process Model.
- Methods to be used.
- Tool Requirements.
Submodels of V-Model:
The V-Model is structured into functional parts, called submodels. These four submodels are closely integrated and mutually influence one another by exchange of products/results. These submodels are as below:
- Project management (PM): plans, controls and informs the SD, QA and CM submodels.
- Software/System development (SD): develops the system or the software.
- Quality Assurance (QA): specifies quality requirements, test cases and criteria, and examines the products and the compliance with the standards.
- Configuration Management (CM): administrates the products generated.
Conventional V-Model represents the development process in the form of a V shape. The right side of the V represents the testing where the systems are validated against the specifications defined on the left side. The meeting point of the V represents the actual development”. Passionate about SAP, 2006.V-Model. [online] Available at: http://passionateaboutsap.com/rmtiwari/main.html?http://passionateaboutsap.com/rmtiwari/Resources/Management/SoftwareDevelopmentLifecycle/V-Model.html [Accessed 11 February 2013].
Passionate about SAP, 2006. [online] Available at: http://passionateaboutsap.com/rmtiwari/main.html?http://passionateaboutsap.com/rmtiwari/Resources/Management/SoftwareDevelopmentLifecycle/V-Model.html