Chapter 9. Verification, Validation, Testing and Operation

  1. Mark Norris1 and
  2. Steve Pretty2

Published Online: 5 OCT 2001

DOI: 10.1002/0470841494.ch9

Designing the Total Area Network: Intranets, VPNs and Enterprise Networks Explained

Designing the Total Area Network: Intranets, VPNs and Enterprise Networks Explained

How to Cite

Norris, M. and Pretty, S. (2001) Verification, Validation, Testing and Operation, in Designing the Total Area Network: Intranets, VPNs and Enterprise Networks Explained, John Wiley & Sons, Ltd, Chichester, UK. doi: 10.1002/0470841494.ch9

Author Information

  1. 1

    Norwest Communications, UK

  2. 2

    BT, UK

Publication History

  1. Published Online: 5 OCT 2001

Book Series:

  1. Wiley–BT Series

ISBN Information

Print ISBN: 9780471851950

Online ISBN: 9780470841495

SEARCH

Keywords:

  • conformance statement;
  • risk assessment;
  • throughput;
  • blocking;
  • availability;
  • components;
  • testbed;
  • integration

Summary

This section explains what sort of checks the designer can and should do as a design evolves in order to make sure that it is fit for the purpose. This process of validation, verification and testing can begin at a very early stage, as the customer requirements are being put together. Methods for validating requirements and verifying design options are explained in this chapter.

Once a design is complete, checking that all is well moves from being a logical activity to a physical one. Testing is never complete as any network evolves (both through intent and accident) as it is used. So mechanisms for problem and issue management need to be put in place to handle this. There are reasons why and times when a designer may get involved in network troubleshooting. This is when the network is exhibiting unexpected behaviour that cannot be explained by any known failure mechanism.

A methodical approach to investigating the problem is explained