Microsoft Word Hardware Reconfiguration Methodology V final2

Laboratory testing

Before considering performing any type of system maintenance-related action on an operational C2 computer system, whether it is an update, upgrade, or manual system maintenance, all actions should first be thoroughly tested. Specifically, tests should be conducted within the confines of a special laboratory environment where tests can be safely performed and evaluated without jeopardizing the stability of the operational network. A laboratory is an exceptional setting for testing patches, bug fixes, updates, upgrades, source code modifications, etc., before they are ever rolled out and made operational. Laboratory testing provides an opportune time and location to perform system reaccreditation and recertification in order to minimize the overall impact that would otherwise be experienced in operational environments. Since the Navy has expressly stated that all changes must be certified and tested, this setting provides a unique opportunity for carrying out these necessities. Once a test system can be reaccredited and recertified in a laboratory setting it can then be safely implemented (barring certain precautionary safeguards) onto operational systems.

In addition, those interested in software degradation and operating system evolution will appreciate the use of such facilities to study and examine how operating systems and their software respond to many changes progressively made over the years. At the same time, some may see laboratory testing as a waste of time, especially in testing small and seemingly innocuous changes. Nevertheless, even small changes made progressively overtime build up and can cause a “snowball effect” which can effectively cause seemingly functional systems to cease functioning.

1. Laboratory

Before proceeding with any laboratory tests, it is important that the testing environment be as similar as possible to the operational environment. The laboratory does not need to have the same number of computers or users. However, the laboratory should utilize the same type of telecommunication equipment used in the operational network such as routers, bridges, uplinks, etc. The physical computer systems should be of the same make and model and those in the operational network as software can respond differently when used on different systems. This is in fact a well-known problem of computer system, particularly hardware dependent software such as kernels and device drivers. In addition, when troubleshooting this will help to isolate software related problems caused by incompatibilities and inconsistencies from hardware issues. Furthermore, the operating systems, applications, services, etc. should be similarly configured as the systems they are meant to represent on the operational network. It is very important that the

systems be as similar as possible in order for laboratory testing to be meaningful and produce useful results.

In addition, similar environments will help to “shake down” test systems and reveal software and hardware bugs before they are encountered in the operational network. Furthermore, a laboratory will help to provide a more realistic environment for system administrators, support staff, and users to test and experiment with the various systems. This will help to determine if applications, databases, files, telecommunication systems, and other various services are equally available, responsive, and functional as they were before any system modifications were made. In the end, all this testing will help to enable a faster and more simplified deployment and transition of the required changes (i.e. updates, etc.) onto an operational setting.

2.