Civil Engineering Reference
In-Depth Information
the testing of installations deserves attention. In order to fulfil a testing tra-
jectory successfully, it is important to recognise the following:
-
testing of software is a profession;
-
testing is part of the software development process;
-
testing is part of a system of guaranteeing quality;
-
testing is one of the most important management measures in respect of
risk management on software;
-
when a tunnel installation consists of a combination of more than two
systems, then at least three systems must always be tested: firstly system
a, secondly system b and finally the system that brings about a cohesive
functioning of systems a and b together (system c).
Theoretical framework
The importance of testing
The purpose of testing is to objectively show the functioning of a system in
accordance with requirements which are set beforehand. In order to do that,
the characteristics of the product (or system) to be tested must be measur-
able, and in a certain sense that can be difficult: a composed system such as
that at the Westerschelde Tunnel, cannot simply be defined in terms of a
series of product characteristics. Systems also have a certain composed
functionality.
The defining of the characteristics of a product calls for a great deal of insight
into the application.Thus, in the case of a tester, a pump is only a pump when
it is fitted in the proper manner, installed at the correct location, demonstrably
has the right capacity and functions in the agreed manner.The pump in ques-
tion is only adequately tested when the installation at the final location, sus-
tainably provides the prescribed performance in conjunction with other
systems.
Phasing system development and the relationship with testing
In the system development, desires (purposes and functions) are trans-
formed into a functional design. A technical design is drawn up from the
functional design and then the system realisation is dealt with. A much used
model that goes from desire to expectation is also called the V-model. What
is important in this model, is that once it has been defined what the system
must do, it also describes how this can be shown. In other words, within the
V-model the testing trajectory is inextricably linked to the design trajectory.
Fig. 15.11
The V-model
Project phase
Testing phase
Desire
Expectation
Functional design
Acceptance test
Technical design
System test
Programme and
integration test
System realisation
Search WWH ::
Custom Search