A Validation Strategy for Networks

To define a vaiidation strategy, we first must consider the current status of the system. If the system has already been installed, the validation will be retrospective if it is a new network, proceed with prospective validation. This chapter considers a prospective approach to vaiidation however, most of the concepts can aiso be used for retrospective vaiidation. It should be noted here that retrospective validation is usuaiiy a much more expensive and timely task compared to prospective validation. It has been suggested that retrospective vaiidation can be in excess of five times more expensive than prospective vaiidation [4]. 

Now that the kind of validation to be performed on the system has been defined, it is necessary to clarify the scope of the system. Agreeing on the scope is extremeiy important for two reasons (1) We can adopt the appropriate variant of the V model life cycle depending on the use of different 

The contents of a LAN design specification are outlined below. It is strongly recommended that the design specification include a map of the network and the systems interconnections. 

A series of drawings showing the exact location of all network equipment and cables In this subsection should be attached, as minimum, 

Below is a definition of which sections should be included in the WAN design specification. Due to the particular objects of the design, diagrams and drawings are strongly recommended to define WAN. 

---