2.0  DCN/ICN PILOT PROGRAM TESTING ENVIRONMENT

The DCN/ICN pilot program testing environment includes the pilot program, local area network sites, the Internet and the DCN/ICN Management Operations Control Center (MOCC).

2.1  Introduction

The environment for testing includes both a Local Area Network (LAN) client/server environment (shown in Figure 1.2-2), and a Wide Area Network (WAN) with clients at Pilot Program Sites and other remote sites connected to the Internet to access servers located at the MOCC. As part of the pilot program test planning environment, we conducted a risk analysis; identified test levels and a test strategy; identified specific test methods, participating organizations, facilities, personnel and equipment; and developed a top level test schedule.

2.2  Risk Analysis

A preliminary risk analysis of the DCN/ICN has identified three risk areas related to the provision of information and collaboration services to DCN/ICN pilot program participants:

· Security.
· Performance.
· Information Content Accuracy and Currency.

Appendix C summarizes the security risk analysis and the corresponding Security Architecture to mitigate the security risks. Reference [DCN/ICN, 96d] documents an earlier DCN/ICN security analysis that was used in formulating our Security Architecture. Appendix C, Performance Requirements, in reference [DCN/ICN, 96a] documents our initial risk analysis of the Internet network performance.

Information content accuracy and currency are vital to the information services of the DCN/ICN. We conducted a risk analysis as part of the DCN/ICN information services requirements analysis, following the ManTech-WVA TAOC Software Process Planning Guidebook, and summarized this analysis in Figure 2.2-1. We then conducted a more detailed risk analysis related to test planning as shown in Figure 2.2-2.

Figure 2.2-1  Software Requirements Process Model

Figure 2.2-2  Software Test Phase Process Model

Table 2.2-1  DCN/ICN Information Services and Content Sources

An information content source will be recorded in the information services database along with the date of last update for each record in each table.

Verification of content will be conducted with the information content source summarized in Table 2.2-1 by any of the following methods:

· On-line Registration of Information by Point of Contact.
· Electronic Mail from Point of Contact.
· Facsimile from Point of Contact.
· Periodic Inspection of Internet Uniform Resource Location (URL) of Information Source.

MOCC operations personnel will verify the currency of information by contacting the points of contact for each information source. MOCC operations personnel will verify the accuracy of hypertext links through web site management tools that check hypertext links.

2.3  Test Levels and Strategy

Overall implementation/testing strategy consists of a building block approach which first provides core services such as Electronic Mail (E-Mail), E-Mail directory services, electronic discussion groups, document conferencing/annotations, and repository directories. The types and levels of services to be provided are shown in Figure 2.3-1.

Figure 2.3-1  DCN/ICN Types and Levels of Service

Core services testing will begin with a single DoD Pilot Program site (NSWC CD; Bethesda, MD) with local and remote users. Client workstations shall be qualified for DCN/ICN Pilot Program use by checking candidate workstations with a DCN/ICN qualification matrix shown in Appendix A. A site survey assessment shall be performed prior to pilot program initiation at a site using a site survey assessment tool included in Appendix B. Test strategies include: positive and negative test strategies; black box testing for COTS configuration items; and black and white box testing for Developmental Items (DEV) as well as Dynamic and Static testing for DEV items as summarized in Figure 2.3-2.

Figure 2.3-2  Test Strategies for COTS and Developmental Items

2.4  Test Methods

DCN/ICN test methods include the following:

· COTS/Developmental Item Configuration Item Tests within the MOCC Environment.
· Functional Tests by DCN/ICN Service Area.
· Interface Tests (e.g., Web Client and Web Server; Web Server and Oracle Relational Database).
· Performance Tests for Multi-Media Collaboration Services (e.g., audio, desktop video, text, chat, guided web navigation).
· Pilot Program Site User Comments and feedback via Help Desk and DCN/ICN Test Newsgroup.

2.5  Participating Organizations

The pilot program participating organizations and personnel include the following:

· Pilot Program Organization such as a DoD Program Management Office (e.g., NSWC, CD).
· Authorized Support Contractors/Consultants (independent systems/software engineers).
· DoD CALS Office (observers).
· CALS/IDE Virtual Enterprise MOCC Installation and Test Personnel.

2.6  Facilities

The facilities for the DCN/ICN include facilities for local operations control centers at subscriber organization sites (multiple users) as well as the MOCC facility. A detailed description of the MOCC facility and network configuration is provided in this Implementation Plan [DCN/ICN, 96b]. A brief description of the MOCC network configuration is provided in the System Overview (paragraph 1.2). Local facilities are dictated by subscriber organization needs. Single subscribers do not need a local operations control center since Internet network access and technical support is handled by the subscriber's Internet Access Provider.

2.6.1  Subscriber Facilities

The subscriber will need computer and local communication facilities to connect to the Internet though an Enterprise connection or through a third party Internet Access Provider (IAP).

2.6.2  Management Operations Control Center Facility

Facilities for the MOCC will include office space (approximately 6500 square feet); office furniture [workstation furniture for 8 personnel in the first year (Phase I) and 16 personnel in the second year (Phase II)]; and telephone system (voice mail, call forwarding, call-waiting) for management, technical, and Hot Line Service Desks personnel. A preliminary design layout for the MOCC is shown in Figure 2.6.2-1.

Figure 2.6.2-1  Preliminary Facility Layout for the MOCC

2.7  Personnel

Personnel requirements for the Local Operations Control Center are dictated by the local organization needs. During the first year 6-10 DoD Program Offices will be supported. During the second year 15-20 DoD/International Program Offices or virtual organizations shall be supported.

2.7.1  Subscriber Personnel

Personnel include local system administration, and, optionally, network security personnel at each node that depends on the size and complexity of the subscriber's information infrastructure. A rule of thumb is one system administrator per 25 end-users.

2.7.2  Management Operations Control Center Personnel

Estimated staffing requirements for the MOCC for the first two years of operation are highlighted in Table 2.7.2-1 "Manpower Staffing Plan (Year 1)" and "Table 2.7.2-2 Manpower Staffing Plan (Year 2)." Operations and technical transfer personnel will participate in the pilot program testing.

Table 2.7.2-1  Manpower Staffing Plan (Year 1)

Table 2.7.2-2  Manpower Staffing Plan (Year 2)

2.8  Equipment

The equipment for the implementation and test of the DCN/ICN includes end-user terminals or workstations, Internet servers, and related Internet communications equipment, including automated facsimile servers and voice-mail systems. In addition, equipment for the MOCC is needed to provide DCN/ICN wide help desk and system administration services. The hardware and software are specified in the Preliminary DCN/ICN Pilot Program Test Software and Equipment Report [DCN/ICN 97c].

2.9  Test Schedule and Resources

A preliminary pilot program implementation and testing schedule is shown in Table 2.9-1.

Table 2.9-1  Preliminary Pilot Program Installation and Test Activity Schedule