top - download
⟦47da6f51c⟧ Wang Wps File
Length: 16669 (0x411d)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN21.08«
Derivation
└─⟦f6f93b0e6⟧ Bits:30006245 8" Wang WCS floppy, CR 0245A
└─ ⟦this⟧ »~ORPHAN21.08«
WangText
…02…PC/TPL/001
PROTOCOL CONVERTER TEST PLAN…02…KPL/820802…02……02…#
CONTRACT SHNMO-82-9205-INF
…02……02…PC
TABLE OF CONTENTS
Page
1 GENERAL .......................................
1
1.1 Purpose and Scope...........................
1
1.2 Applicable Documents .....................
1
1.3 Terms ad Abbreviations ....................
3
2 DEVELOPMENT TEST ACTIVITY ......................
4
2.1 Pretest Activity ...........................
4
2.2 Pretest Activity Results ...................
4
3 TEST PLAN .....................................
5
3.1 System Description .........................
5
3.2 Test Schedules .............................
5
4 TEST SPECIFICATIONS ............................
8
4.1 Factory Acceptance Tests ...................
8
4.1.1 COMSEC Verification .................... 8
4.1.2 Functional Tests .......................
8
4.2 Preliminary Site Acceptance Test ...........
11
4.2.1 Security Certification Test ............
11
4.2.2 Functional Tests ......................
11
4.3 Provisional Site Acceptance Tests ..........
12
4.3.1 COMSEC Verification ....................
12
4.3.2 Functional Tests .......................
12
4.3.2.1 Site 1 Provisional Acceptance Test..
12
4.3.2.2 Site 2 Provisional Acceptance Test.. 13
4.3.2.3 Site 3 Provisional Acceptance Test..
13
5 FINAL ACCEPTANCE ...............................
14
1. G̲E̲N̲E̲R̲A̲L̲
This Test Plan comprises the baseline for acceptance
test of the Protocol Converter to be developed under
SHNMO contract 82-9205-INF.
1.1 P̲u̲r̲p̲o̲s̲e̲ ̲a̲n̲d̲ ̲S̲c̲o̲p̲e̲
Test pla objectives are:
(a) To provide guidance and instructions for the
management and technical personnel throughout the
test period.
(b) To provide the user with an orderly schedule of
test events.
(c) To specify the equipment and organizatinal requirements,
and the methodology of testing.
A brief description of pretest methods are included
for completeness.
A comprehensive plan for system evaluation and records
of test input and expected outputs will be included
in a separate docment entitled "TEST PROCEDURES".
1.2 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
1. Protocol Converter contract SHNMO-82-9205-INF.
1982-04-29
2. System Requirement Specification (SRS).
Appendix G of Reference 1.1982-04-29.
3. SCARS II System Design Baseline ol III A
Rev A and B 1981-06-30, 1981-07-15. Burroughs.
or
CPS/ICD/006, 1981-11-10 Christian Rovsing A/S.…86…1
…02… …02… …02… …02…
4. Functional Description for the SCARS, CAMPS, ACCIS
interface. 1981-02-05. As appendix E to Reference
3.
5. Remote Terminal Supervisor (GRTS).
Honeywell DD40B rev.0, July 176.
6. DINDAC CCTC TR-01, 1978-06-30.
7. ACE Security Directive 70-1.
1979-08-31 with change 2 dated 1981-02-06.
8. ACE ADP Standards Manual 96-1-1, part no.007-3
1980-01-14.
9. AMSG 720A. January 1977
10. AMSG 719B. September 1976
1. AQAP 1, 13
12 MIL-STD188C. 1969-11-24
13 WWMCCS ADP Telecom Standard Engineering Practices,
DCA November 1979.
14 Control wires and functions for WWMCCS-PC link
(delivery by SHAPE on or before 3.May 1982).
15. X25 LAP(CAMPS) Product Specfication.
CSS-MIC/0422/PSP/1027. 1982-05-28.Chr.Rovsing A/S
16 Protocol Converter, Project Implementation Plan,
issue 2, Christian Rovsing A/S, 1982-07-21.
17 Protocol Converter, System Specification, issue
1,
Christian Rovsing A/S, 1982-0714.
1.3 T̲e̲r̲m̲s̲ ̲a̲n̲d̲ ̲A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
This section defines the terms and abbreviations to
be used in this document.
ACE Allied Commands Europe
CAMPS Computer Aided Message ProcessingSystem
CCIS Command and Control Information System
CR Christian Rovsing A/S
CR80 CR80 minicomputer (Christian Rovsing)
DINDAC autoDIN-wwmccs Direct Access Communications
module
DN355 Honeywell front-end processor
EMI Rack (Anti)-Electroagnetic Interference Rack
End Systems CCIS, CAMPS, or SCARSII
EPROM Erasable Progammable Read-only Memory
FAT Factory Acceptance Test
HW Hardware
I/F Interface
OC Operator's Console
PC Protocol Converter
PIP Project Implementaton Plan
Prov.AT Provisional Acceptance Test
Prel.AT Preliminary Acceptance Test
RAM Random Access Memory
RCI Remote Computer Interface (to Honeywell)
SCARS Status & Control Alerting & Reporting System
SHAPE Supreme Headquarters AlliedPowers Europe
SRS System Requirement Specification
SW Software
SWELL Software Engineering Low Level Language
TRC Traffic Controller
VDU Visual Display Unit
WWMCCS World Wide Military Command & Control System
2. D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲T̲E̲S̲T̲ ̲A̲C̲T̲I̲V̲I̲T̲Y̲
This chapter describes the informal tests performed
concurrently with the PC software development.
2.1 P̲r̲e̲t̲e̲s̲t̲ ̲A̲c̲t̲i̲v̲i̲t̲y̲
Software components will b tested currently during
development.
The functions of the individual software components
will be verified by means of the general CR80 debugging
and special facilities for inspecting the general registers
at entry and exit from SWELL procedures.Register dumps
at the operators console will contain the procedure
name together with the words ENTRY and EXIT. These
dumps may be switched on and off by SWELL conditional
compilation of the statements generating the dumps.
Data structures may bedumped as well at critical points
for verification of the semantics of the SW component.
Also semaphore protected areas for message headers
and message information can be dumped for verification
of the correct use of these buffers. This feature i
eventually excluded totally to meet the demands for
secure handling of classified information.
2.2 P̲r̲e̲t̲e̲s̲t̲ ̲A̲c̲t̲i̲v̲i̲t̲y̲ ̲R̲e̲s̲u̲l̲t̲s̲
The record of results obtained during the development
tests should be available for each SW component tested.
The recod should preferably consist of a suitably commented
hardcopy of the test results to support trouble-shooting
during integration of SW into larger entities.
3. T̲E̲S̲T̲ ̲P̲L̲A̲N̲
3.1 S̲y̲s̲t̲e̲m̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The configuration under test is outlined in Fig.3-1.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
A PC B
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Fig.3-1 General PC Test Configuration
System A is a CAMPS, SCARSII system, or a suitable
system for simulating the CAMPS/PC interface if CAMPS
is not available. 'A' communicaes with PC using the
X.25 protocol with messages in E1 format as described
in Reference 3.
System B is a Honeywell 6000 computer equipped with
a DN355 front-end computer. 'B' communicates with PC
using the RCI/DINDAC protocol described in referenes
5 & 6. System B is often refered to as CCIS. For FAT
system B will have to be simulated on PC equipment
due to unavailability of CCIS for this test.
3.2 T̲e̲s̲t̲ ̲S̲c̲h̲e̲d̲u̲l̲e̲s̲
Acceptance tests will be performed according to the
schedule given in Tabl 3-1.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TEST DATE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
Factory Acceptance Test, site 1 83-01-30
Factory Acceptance Test, site 2 83-02-15
Factory Acceptance Test, site 3 83-02-28
Preliminary Acceptance Test, site 183-02-15
Provisional Acceptance Test, site 1 83-03-15
&
83-06-01
Provisional Acceptance Test, site 2 83-05-15
Provisional Acceptance Test, site 3 83-06-15
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Table 3-1 Accepance Test Schedule
…06…1 …02… …02… …02… …02…
The Provisional Acceptance Test at site 1 will commence
on 83-03-15 with a test of PC connected to CAMPS and
CCIS. Provisional Acceptance Test of SCARSII-PC-CIS
will take place on 83-06-01. See Reference 1, p.25.
The following Test Reports will be prepared and delivered
to the customer in 6 copies.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
TEST DATE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Factory Acceptance Test, site 1 83-01-30
Factory Acceptance Test, site 2 83-02-15
Factory Acceptance Test, site 3 83-02-28
Provisional Acceptance Test, site 1 83-0415
Provisional Acceptance Test, site 2 83-05-31
Provisional Acceptance Test, site 3 83-06-30
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Table 3-2 Test Report Schedule…86…1 …02… …02… …02… …02…
4. T̲E̲S̲T̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲S̲
This section describes the test configurations and
provides an overview of test methods to be used during
the tests. Detailed test procedures will be issue spearately.
4.1 F̲a̲c̲t̲o̲r̲y̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲s̲
The FAT's consist of:
a. COMSEC verification for site 1
b. Functional test of HW and SW
4.1.1 C̲o̲m̲s̲e̲c̲ ̲v̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
COMSEC verification of equipment is divided into two
categories:
a. EMI rack ssembly including opto-electrical
interfaces
b. Terminal equipment for supervisory and control
As for the CAMPS programme ACE COMSEC is given admission
to the factory integration in order to perform TEMPEST
qualification tests o site 1.
Terminals are delivered with a TEMPEST clearance certification
according to AMSG720A, cf. Reference 2, p 61.
4.1.2 F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲T̲E̲S̲T̲S̲
The general test configuration is outlined in Fig.
3-1. For the Factory Acceptance Tests system A is
CAMPS or a CAMPS simulator if CAMPS is not available.
For FAT, system B in Fig.3-1 is a Protocol Converter
suitably modified for simulating the CCIS side.
PC hardware is tested using the CPU-, RAM-, and LTU-test
options included in the PC 'Maintenance Controller'
SW package described in Reference 17, section 4.1.2.
For each site te FAT is conducted according to the
test procedures.
The test procedures will identify by name and number
the item under test. Test procedures must contain a
general description of how the system is prepared for
the test. Special requirements fortest system preparation
will be stated along with each test procedure.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
DATE : 82-07-25
TEST ITEM : name of function under test
TEST No. : FAT 1
REFERENCES : App. 1 of FAT Test Report
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲
STEP ACTIONS & INPUTS EXPECTED RESULTS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲
…06…1 …02… …02… …02…
1 Masterclear system
on CPU/SCM module
M
on
OC
2 Type:"INIT" on OC
L on OC
expected contents of
a data dump+reference 3 Type:
"LOGON
CCIS
SHAPE PASW CAMPS"
0 on OC
further results
. ................ ..................
. ................. ..................
. ................. ..................
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲
COMMENTS: TEST WITNESSES:
Example showing lay-out
of test procedure recor ..................
..................
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
Table 4-1 Sample Test Procedure Record
Table 4-1 shows the lay-out of test procedure records
to be specified in the Test Procedures.
Each component test procedure record will typically
contain one or more references o hardcopy dumps. For
the particular example shown in Table 4-1 these dumps
could be data structures from which it may be verified,
that the SW function under test has recognized the
input parameters correctly before they are passed on
for the exection.
4.2 P̲r̲e̲l̲i̲m̲i̲n̲a̲r̲y̲ ̲S̲i̲t̲e̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲
This test has a twofold purpose:
a. SHAPE conducted Security Certification Test
b. Functional test of PC when connected to CCIS
This test will be performed on site 1 immediately following
the instllation of the PC.
The test configuration is given in Fig.3-1 with no
connection between system A and PC, and system B equal
to CCIS.
4.2.1 S̲e̲c̲u̲r̲i̲t̲y̲ ̲C̲e̲r̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲T̲e̲s̲t̲
This test is conducted by SHAPE to ensure that the
equipment and the instalation of it is compliant with
the requirements listed in the System Requirements
Specification. Cf. Reference 2, section 7.
Inspection and measurements performed during the Security
Test must not delay the CR functional tests.
4.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲T̲s̲t̲s̲
Thest tests are performed to verify the operation of
the PC-CCIS link.
The tests will be based on prestored PC test messages
and SHAPE supplied test messages sent from the CCIS
SYSTEM
Test procedures specifying the CCIS-PC will be issued
along with test procedures for FAT and Prov.AT.
4.3 P̲r̲o̲v̲i̲s̲i̲o̲n̲a̲l̲ ̲S̲i̲t̲e̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲s̲
The Provisional site Acceptance Test consists of:
a. Functional Tests
b. On-site COMSEC Verification
4.3.1 C̲O̲M̲S̲E̲C̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The COMSEC verification will be performed by ACE COMSEC
personnel after each PC has passed the functional tests.
COMSEC tests shall verify that the perational system
and its environment complies with the security requirements
stated in the SRS, section 7 and related documents
listed there.
4.3.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲T̲e̲s̲t̲s̲
These tests are conducted in accordance with the Test
Procedures. SHAPE is oblied to provide relevant equipment
and adequate personnel for running the tests.
It is foreseen that the functional tests will require
availability of each applicable combination of end-systems
for five full days. Time for test shall primarily be
alocated during prime working hours.
At the expiry of the test period for each combination
of end-systems, CR will issue a test report. At the
same time the purchaser will issue a 'Notice of Defects'
or a 'Descrepancy Note' if applicable.
4.3.2.1S̲i̲t̲e̲ ̲1̲ ̲P̲r̲o̲v̲i̲s̲i̲o̲n̲a̲l̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲
This test will be performed in two tempi as stated
in Table 3-1. The test configuration used in the first
test is shown in Fig.3-1 with systems A and B equal
to CAMPS and CCIS, respectively.
In the second test, system A is SCARSII and B is CCIS
as before. Prov.AT is scheduled to 83-06-01. SCARSII
must be available for test no later than 83-06-01.If
this is not possibl PC-SCARSII may optionally be tested
starting on 83-08-15, cf. Reference 1, P53.
Duration of the CAMPS-PC-CCIS Prov.AT is estimated
to one month starting on 83-03-15. Prov.AT of the SCARSII-PC-CCIS
configuration is scheduled to start on 83-06-01 nd
last 14 days.
4.3.2.2 S̲i̲t̲e̲ ̲2̲ ̲P̲r̲o̲v̲i̲s̲i̲o̲n̲a̲l̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲
This test is schedules to start on 83-05-15 and last
for two weeks.
First week is allocated test of the configuration CAMPS-PC-CCIS.
The following week is used for testing SCARSII-P-CCIS.
The optional use of having the OC connected to either
one of the configurations while on-line will be tested
during Prov.AT on site 2.
4.3.2.3 S̲i̲t̲e̲ ̲3̲ ̲P̲r̲o̲v̲i̲s̲i̲o̲n̲a̲l̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲
This test assumes the availability of an operational
CAMPS ad CCIS.
Scheduled start of this test is 83-06-15. The estimated
duration is two weeks.
Test procedures are identical to the ones used during
the first half of the Prov.AT for site 2, i.e. only
the CAMPS-PC-CCIS configuration exists on site 3.
5. F̲I̲N̲A̲L̲ ̲A̲C̲C̲E̲P̲T̲A̲N̲C̲E̲
Final Acceptance of the PC is the acknowledgement by
SHAPE that each site has been found in compliance with
the requirements, and that CR has lived up to its arrenty
obligations.
Final Acceptance is schedules to 84-08-30.
