Information Technology Reference
In-Depth Information
Configuration Management
Quality Assurance
Software Development
Project Management
Procedure
Methods
Tool Requirements
FIGURE 2.2
V-Model.
V-Model
7
is a software development process, which can be presumed to be the
extension of the Waterfall Model. Instead of moving down in a linear way, the
process steps are bent upward after the coding phase, to form the typical V shape.
The V-Model demonstrates the relationships between each phase of the development
life cycle and its associated phase of testing.
The V-Model is structured into functional parts, so-called
submodels
,asshown
in Figure 2.2. They comprise software development (SWD), quality assurance (QA),
configuration management (CM), and project management (PM). These four sub-
models are interconnected closely and mutually influence one another by exchange
of products/results.
PM
plans, monitors, and informs the submodels SWD, QA, and CM.
SWD
develops the system or software.
QA
submits quality requirements to the submodels SWD, CM, and PM, test
cases, and criteria and unsures the products and the compliance of standards.
CM
administers the generated products.
The V-Model describes in detail the interfaces between the submodels SWD
and QA, as software quality can only be ensured by the consequent application of
quality assurance measures and by checking if they are complied with standards.
Of particular relevance for software is the
criticality
, that is, the classification of
software with respect to reliability and security. In the V-Model, this is considered a
quality requirement and is precisely regulated. Mechanisms are proposed to how the
expenditure for development and assessment can be adapted to the different levels of
criticality of the software.
7
V-Model
(software
development).
(2008,
July
7).
In
Wikipedia.
the
Free
Encyclopedia.
Retrieved
13:01,
July
14,
2008.
http://en.wikipedia.org/w/index.php?title
=
V-Model %28software
development%29&oldid
=
224145058.
Search WWH ::
Custom Search