top - download
⟦7fc2b0522⟧ Wang Wps File
Length: 58143 (0xe31f)
Types: Wang Wps File
Notes: PC/TPL/001 (3)
Names: »3334A «
Derivation
└─⟦f6f93b0e6⟧ Bits:30006245 8" Wang WCS floppy, CR 0245A
└─ ⟦this⟧ »3334A «
WangText
…11……00……00……00……00…(…0a……00……00…(…0b…(…05…'…0f…'…02…'…05…'…06…&…08…&…0d…&
%…09…%…0d…%…02…%…07…$…0b…$…0e…$
#…09…#…0f……86…1 …02… …02… …02…
…02…PC/TPL/001
…02…BHE/830211…02……02…#
PROTOCOL CONVERTER
TEST PLAN…02…KPL/820723…02… PC
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
Page
1 GENERAL ........................................
1
1.1 PURPOSE ....................................
1
1.2 REFERENCED DOCUMENTS .......................
2
1.3 APPLICABLE DOCUMENTS .......................
3
1.4 TERMS ......................................
4
1.5 ABBREVIATION ...............................
5
2 PRETEST ACTIVITY ...............................
6
2.1 HARDWARE PRETEST ACTIVITY ..................
6
2.2 SOFTWARE PRETEST ACTIVITY ..................
6
2.2.1 AMOS Debugger ..........................
7
2.2.2 Programmed Procedure Trace Facility ....
7
2.2.3 Test Drivers ...........................
7
3 TEST PLAN ......................................
8
3.1 SYSTEM DESCRIPTION .........................
8
3.1.1 CAMPS/SCARS ............................
8
3.1.2 CCIS ...................................
8
3.2 TEST SCHEDULES .............................
9
3.2.1 Acceptance Tests .......................
9
3.2.2 Test Reports ...........................
11
3.3 TEST PHASES ................................
12
3.3.1 In-Plant COMSEC Verification ...........
13
3.3.2 Factory Acceptance Test ................
14
3.3.2.1 Milestone Chart. FAT. ................
14
3.3.2.2 Equipment Requirement ..............
14
3.3.2.3 SW Requirement .....................
14
3.3.2.4 Personnel Requirements .............
17
3.3.2.5 Security ...........................
17
3.3.2.6 Responsibilities ...................
17
3.3.3 Preliminary Acceptance Test ............
18
3.3.3.1 Milestone Chart.PAT. ...............
18
3.3.3.2 Equipment Requirement ..............
18
3.3.3.3 SW Requirement .....................
21
3.3.3.4 Personnel Requirements .............
21
3.3.3.5 Security ...........................
22
3.3.3.6 Responsibilities ...................
22
Page
3.3.4 Security Certification Test ............
22
3.3.5 Provisional Acceptance Test, CAMPS .....
23
3.3.5.1 Milestone Chart. PSAT ..............
23
3.3.5.2 Equipment Requirement ..............
23
3.3.5.3 SW Requirement .....................
26
3.3.5.4 Personnel Requirements .............
26
3.3.5.5 Security ...........................
27
3.3.5.6 Responsibilities ...................
27
3.3.6 Provisional Acceptance Test, SCARS .....
28
3.3.6.1 Milestone Chart.PSAT ...............
28
3.3.6.2 Equipment Requirement ..............
28
3.3.6.3 SW Requirement .....................
31
3.3.6.4 Personnel Requirements .............
31
3.3.6.5 Security ...........................
32
3.3.6.6 Responsibilities ...................
32
3.3.7 On-Site COMSEC Verification ............
32
4 TEST SPECIFICATION AND EVALUATION ..............
33
4.1 TEST SPECIFICATION .........................
33
4.1.1 Requirement Mapping ....................
35
4.1.2 System Functions .......................
39
4.2 VERIFICATION METHODS AND CONSTRAINTS .......
42
4.2.1 Verification Method Terms ..............
42
4.2.2 System Verification Conditions .........
42
4.2.2.1 Conditions at FAT ..................
42
4.2.2.2 Conditions at PAT ..................
42
4.2.2.3 Conditions at PSAT .................
43
4.2.3 Extent of System Verification ..........
43
4.2.4 Data Recording .........................
43
4.2.5 System Verification Constraints ........
43
4.3 VERIFICATION EVALUATION ....................
44
4.3.1 Test Data Criteria .....................
44
4.3.2 Acceptance Criteria ....................
45
4.3.2.1 Accepted ...........................
45
4.3.2.2 Not Accepted .......................
45
4.4 TEST CONTROL ...............................
46
4.4.1 Means of Control .......................
46
4.4.2 Test Data ..............................
46
4.5 TEST DOCUMENTATION OUTLINE .................
47
4.5.1 Test Plan ..............................
47
4.5.2 Test Procedure .........................
47
4.5.3 Test Report ............................
47
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̲
The purpose of the Acceptance Test Plan is:
o To provide an outline of the neccessary
activities required for system acceptance.
o To outline the test schedule.
o To outline the test methodology.
o To define the acceptance criterias for each individual
activity.
o To define, where applicable, the personel-, equipment-,
and software requirements for the individual activity.
o To define the responsibilities for conducting and
coordinating the test activity.
1.2 R̲E̲F̲E̲R̲E̲N̲C̲E̲D̲ ̲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 Vol III A
Rev A, B and C 1981-06-30, 1981-07-15, and
1982-04-28. Burroughs.
or
CPS/ICD/006, 1981-11-10 Christian Rovsing A/S.
4. Remote Terminal Supervisor (GRTS).
Honeywell DD40B rev. 0, July 1976.
5. DINDAC CCTC TR-01, 1978-06-30 and
DINDAC-RCI Protocol Notes, 1982-07-27. CRA.
6. AMSG 720A. January 1977.
7. Protocol Converter, System Specification, issue
2,
Christian Rovsing A/S, 1982-07-14.
1.3 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
a) Protocol Converter contract SHNMO-82-9205-INF
1982-04-29.
b) PC, Project Implementation Plan
PC/PIP/001
1.4 T̲E̲R̲M̲S̲
Acceptance Test: Designates the act whereby SHAPE
will acknowledge that CR has demonstrated,
that the requirements to PC has
been met, to a level set by the
appropriate Acceptance Test Procedure.
End-System: Designates any of the three systems
to which PC is connected, i.e.
CAMPS or SCARS in one end and CCIS
in the other end.
1.5 A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲
ACE Allied Commands Europe
CAMPS Computer Aided Message Processing System
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 Electro Magnetic Interference
End Systems CCIS, CAMPS, or SCARSII
EPROM Erasable Programmable Read-only Memory
FAT Factory Acceptance Test
HW Hardware
I/F Interface
OC Operator's Console
PAT Preliminary Acceptance Test
PC Protocol Converter
PIP Project Implementation Plan
PSAT Provisional Site Acceptance Test
RAM Random Access Memory
RCI Remote Computer Interface (to Honeywell)
SCARS Status & Control Alerting & Reporting
System
SHAPE Supreme Headquarters Allied Powers 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̲ ̲ ̲P̲R̲E̲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 H̲A̲R̲D̲W̲A̲R̲E̲ ̲P̲R̲E̲T̲E̲S̲T̲ ̲A̲C̲T̲I̲V̲I̲T̲Y̲
Since there is no hardware development on the PC project,
the pretest activity is limited to hardware-module
and -assembly burn-in.
All CR80 parts will be used in the PC Test Computer
(which is used to perform the software pretest activity)
for a period of time, to ensure the proper functioning
of the hardware.
A log of operation time and errors will be made for
internal use.
2.2 S̲O̲F̲T̲W̲A̲R̲E̲ ̲P̲R̲E̲T̲E̲S̲T̲ ̲A̲C̲T̲I̲V̲I̲T̲Y̲
Software packages will be tested currently during development.
Tests will be applied at different stages of the software
development. These are:
1) Simple response tests at single package level.
2) Dependence and structure tests at two-packages
level.
3) Function and interface tests on integration level
using simulation of environments.
a) To cover the different levels of test, the following
test tools may be used:
1) AMOS Debugger
2) Programmed Procedure Trace Facility
3) Special Test Drivers
b) Suitably commented hardcopy of the test dumps will
be made to support internal trouble-shooting during
integration.
2.2.1 A̲M̲O̲S̲ ̲D̲e̲b̲u̲g̲g̲e̲r̲
The AMOS Debugger is used to verify the interface output
for a single software package. Commands sent from the
Package Under Test (PUT) are verified using the Debugger.
The output dumps, being the contents of command records,
are compared to the expected output specified in the
PDS.
2.2.2 P̲r̲o̲g̲r̲a̲m̲m̲e̲d̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲T̲r̲a̲c̲e̲ ̲F̲a̲c̲i̲l̲i̲t̲y̲
Register dumps containing each procedure name and register
content at ENTRY and EXIT are used for verification
of correct procedure call structure and parameter transfer
using the CR80 registers.
Furthermore, interface records, intended for transfer
of commands and/or responses to other packages, may
be dumped, as an initial verification of correct package
communication.
In contrast to AMOS Debugger these trace and dump facilities
may be employed by several CR80 processes
(of which some may be dummy) during integration.
The Programmed Procedure Trace and dump Facilities
are monitored by conditional compilation.
2.2.3 T̲e̲s̲t̲ ̲D̲r̲i̲v̲e̲r̲s̲
The test drivers are dummy processes which support
software integration by exercising the timing and response
of the PUT interfaces.
Output dumps (interface records) are used for functional
verification of the PUT's reaction when sending and
receiving data from other packages.
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 for PC-Tests is outlined in
figure 3.1-1.
A PC B
Figure 3.3-1.
PC-Test Configuration
3.1.1 C̲A̲M̲P̲S̲/̲S̲C̲A̲R̲S̲
End-system A is either a CAMPS or a SCARS system or
a suitable system for simulating the interface (PC'')
if endsystems are not available.
End-system A communicates with PC using the X.25 protocol
with messages in E1-format as described in reference
3.
3.1.2 C̲C̲I̲S̲
End-system B is either a CCIS system or a suitable
system for simulating the interface (PC') when CCIS
is not available (In-Plant-tests).
End-system B communicates with PC using the RCI/DINDAC
protocol described in references 4 and 5.
3.2 T̲E̲S̲T̲ ̲S̲C̲H̲E̲D̲U̲L̲E̲S̲
3.2.1 A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲s̲
The dates for start of:
o Factory Acceptance Tests (FATs)
o Preliminary Acceptance Test (PAT)
o Provisional Site Acceptance Tests (PSAT)
are given in Table 3-1.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲T̲E̲S̲T̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲D̲A̲T̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Factory Acceptance Test, site 1 83-05-02
Factory Acceptance Test, site 2 83-05-09
Factory Acceptance Test, site 3 83-05-16
Preliminary Acceptance Test, site 1 83-05-24
Provisional Acceptance Test, site 1 83-06-06 &
83-07-04
Provisional Acceptance Test, site 2 83-06-20
Provisional Acceptance Test, site 3 83-07-11
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TABLE 3-1 ACCEPTANCE TEST SCHEDULE
Figure 3.2-1 gives the Overall Test Schedule, showing
the period of time for each Acceptance Test and making
a reference to the section relevant for each Test.
These sections will give a more detailed plan for each
Test.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TPL TEST LOCA- SITE ̲Y̲E̲A̲R̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲1̲9̲8̲3̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲S̲E̲C̲.̲ ̲ ̲N̲A̲M̲E̲ ̲ ̲ ̲T̲I̲O̲N̲ ̲ ̲ ̲E̲Q̲P̲M̲ ̲ ̲ ̲M̲O̲N̲T̲H̲ ̲ ̲ ̲ ̲ ̲ ̲M̲A̲Y̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲J̲U̲N̲E̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲J̲U̲L̲Y̲ ̲ ̲ ̲ ̲ ̲
̲W̲E̲E̲K̲ ̲ ̲1̲8̲ ̲1̲9̲ ̲2̲0̲ ̲2̲1̲ ̲2̲2̲ ̲2̲3̲ ̲2̲4̲ ̲2̲5̲ ̲2̲6̲
̲2̲7̲ ̲2̲8̲ ̲2̲9̲ ̲ ̲
3.3.1 COMSEC IP 1 X
3.3.2 FAT IP 1 X
3.3.2 FAT IP 2 X
3.3.2 FAT IP 3 X
3.3.3 PAT OS 1 X X
3.3.4 TRWSEC OS 1 X
3.3.5 PSAT,C OS 1 X
3.3.6 PSAT,S OS 1 X
3.3.7 COMSEC OS 1 X
3.3.5 PSAT OS 2 X X
3.3.7 COMSEC OS 2 X
3.3.5 PSAT OS 3 X X
3.3.7 COMSEC OS 3 X
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
NOTE: IP means In-Plant
OS means On-Site
C stands for CAMPS
S stands for SCARS
Figure 3.2-1
Overall Test Schedule
3.2.2 T̲e̲s̲t̲ ̲R̲e̲p̲o̲r̲t̲s̲
The following Test Reports will be prepared (and accepted
by the customer) on the dates listed in Table 3-2.
The Test Reports will be delivered in 6 copies to the
customer within one month from the approval date.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲T̲E̲S̲T̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲D̲E̲L̲I̲V̲E̲R̲Y̲ ̲ ̲ ̲ ̲ ̲
Factory Acceptance Test, site 1 83-05-06
Factory Acceptance Test, site 2 83-05-13
Factory Acceptance Test, site 3 83-05-20
Provisional Acceptance Test, site 1 83-06-17
Provisional Acceptance Test, site 2 83-07-01
Provisional Acceptance Test, site 3 83-07-22
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TABLE 3-2 TEST REPORT SCHEDULE
3.3 T̲E̲S̲T̲ ̲P̲H̲A̲S̲E̲S̲
The PC Acceptance task is divided into following Test
Phases:
1. In-Plant COMSEC Verification
2. Factory Acceptance Test
3. Preliminary Acceptance Test
4. Security Certification Test
5. Provisional Site Acceptance Test, CAMPS
6. Provisional Site Acceptance Test, SCARS
7. On-Site COMSEC Verification
In the following paragraphs each Test Phase is separately
described by
- scope
- milestone-chart
- requirements for equipment
software
personnel
- aspects of security
responsibility
3.3.1 I̲n̲-̲P̲l̲a̲n̲t̲ ̲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-Protected-Rack assembly including fiber-optic
interfaces.
b. Terminal equipment for supervisory and control.
As for the CAMPS programme ACE COMSEC is given admission
to the factory integration site in order to perform
TEMPEST qualification tests on site 1.
The PC equipment will be tested by Purchaser at the
factory. The purchaser will liaise directly with the
national COMSEC authorities where appropriate.
The test measurements will be performed on the EMI-Protected-Rack
mounted equipment. The measurements shall verify compliance
with the requirements specified in the SRS section
7.1.
All equipment which process classified information
in a clear electrical form shall be in compliance with
the SRS section 7.1.
Terminals are delivered with a TEMPEST clearance certification
according to AMSG720A, cf. Reference 2,
p. 61.
3.3.2 F̲a̲c̲t̲o̲r̲y̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲
When the PC hardware, to be installed at sites, has
been integrated at the factory, a functional test of
PC-system will be performed at the factory to verify
that it fulfils the functional specifications in the
SRS.
3.3.2.1 M̲i̲l̲e̲s̲t̲o̲n̲e̲ ̲C̲h̲a̲r̲t̲.̲ ̲F̲A̲T̲.̲
The detailed schedule for the Factory Acceptance Test
is shown in figure 3.3.2-1. The complete test will
take 5 days commencing with one day for orientation
purposes and ending up with one day for preparation
and approval of the Test Report.
3.3.2.2 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
The equipment to be used during the Factory Acceptance
Test is listed in Table 3.3.2-1.
The test configuration is shown in Figure 3.3.2-2.
3.3.2.3 S̲W̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
At the Factory Acceptance Test the software is extended
with parts which makes it possible to simulate the
CCIS link. These software parts are to compensate for
the special CCIS-PC master-slave relationship.
By the help of the above mentioned supporting software
a PC is configured to act as a normal CCIS link in
sending and receiving messages from a normal PC configu-
ration. The CCIS simulating PC is called PC'.
On the CAMPS side of PC a CAMPS configuration is provided
with the abilities to send and receive normal or illegal
messages. (The illegal messages are con-
structed for test purposes). This configuration of
CAMPS is called PC".
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DAY NO.: ̲ ̲ ̲ ̲1̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲2̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲3̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲4̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲5̲ ̲ ̲ ̲ ̲ ̲
EVENT OR 1 2 3 4 1 2 3 4 1 2 3 4
1 2 3 4 1 2 3 4
̲ ̲A̲C̲T̲I̲V̲I̲T̲Y̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
SYSTEMS ̲ ̲ ̲
ORIENTATION
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DOCUMENTATION ̲ ̲ ̲
ORIENTATION
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 1: XXX
NONE-MODE TEST
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 2: XX
MAINTENANCE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 3:
XX
LOCAL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 4:
XXXX
OPERATIONAL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 5:
X
TEST
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PREPARATION OF
̲
̲
̲
TEST REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
APPROVAL OF
̲
̲
̲
̲
TEST REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Figure 3.3.2-1
Milestone Chart, FAT.
EQUIPM.
̲ ̲N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲Q̲u̲a̲n̲t̲i̲t̲y̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲a̲m̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
1 2 (3) Processor Unit
2 1 Adapter Crate
3 1 VDU
4 1 Rack
5 1 CAMPS CONFIGURATION
6 1 TTY-terminal
7 1 Hard Copy Printer
8 1 Photocopier
9 2 Oscilloscope
10 1 Logical Analizer
Table 3.3.2-1
Equipment, FAT.
PC" PC PC" Photo
CAMPS CCIS copier
E5 E1, (E1), E2 E1, E6
E8
E9 E3, E4, E7 E9, E10
Figure 3.3.2-2
Equipment Configuration, FAT.
3.3.2.4 P̲e̲r̲s̲o̲n̲n̲e̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The Factory Acceptance Test will be supervised by CR
test engineers and CR operational staff will assist
in operating the system.
Two operators, one at each end-System, shall be present
on 2., 3. and 4. testday. Two test engineers shall
conduct the test from the first testday to the last
testday. Shape shall offer one or more people with
efficient knowledge of the PC-system and the test procedures
to work through the test and with Charge to approve
or disapprove the effectuated teststeps and the Test
Report.
3.3.2.5 S̲e̲c̲u̲r̲i̲t̲y̲
During the Factory Acceptance Test no security actions
shall be taken, different from the actions during the
PC development period.
3.3.2.6 R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
It is the responsibility of CR to conduct the testing
of PC. So CR shall start and stop each step of the
test procedures. Shape will have the responsibility
of filling in the test step formulas classifying each
step with following marks:
r: right (noting)
n: note (discrepancy note list)
f: failure (defect note list)
3.3.3 P̲r̲e̲l̲i̲m̲i̲n̲a̲r̲y̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲
When the PC-system has been installed at Site 1 (SHAPE)
CR will conduct a functional test of PC when connected
to CCIS. The Preliminary Acceptance Test (PAT) will
be performed immediately after the installation of
the PC.
The test is performed to verify the operation of the
PC-CCIS link.
PAT will be based on prestored test messages to be
sent from the CAMPS/SCARS side and SHAPE supplied test
messages to be sent from the CCIS system.
3.3.3.1 M̲i̲l̲e̲s̲t̲o̲n̲e̲ ̲C̲h̲a̲r̲t̲.̲P̲A̲T̲.̲
The detailed schedule for the Preliminary Acceptance
Test is shown in Figure 3.3.3-1. The complete test
will take 5 days commencing with one day for orientation
purposes and ending up with one day for preparation
and approval for the Test Report.
3.3.3.2 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
The equipment to be used during the Preliminary Acceptance
Test is listed in Table 3.3.3-1.
The test configuration is shown in Figure 3.3.3-1.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DAY NO.: ̲ ̲ ̲ ̲1̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲2̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲3̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲4̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲5̲ ̲ ̲ ̲ ̲ ̲
̲ ̲E̲V̲E̲N̲T̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲ ̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲
̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲
SYSTEMS ̲ ̲ ̲
ORIENTATION
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DOCUMENTATION ̲ ̲ ̲
ORIENTATION
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 1: X
NONE-MODE TEST
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 2: XX
MAINTENANCE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 3: XX
LOCAL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 4:
XXXXX
OPERATIONAL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 5:
XX
TEST
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
APPROVAL OF
̲
̲
̲
̲
̲
̲
̲
̲
TEST
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Figure 3.3.3-1
Milestone Chart, PAT.
EQUIPM.
̲ ̲N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲Q̲u̲a̲n̲t̲i̲t̲y̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲a̲m̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
1 2 (3) Processor Unit
2 1 Adapter Crate
3 1 VDU
4 1 Rack
5 1 CAMPS CONFIGURATION
6 1 TTY-terminal
7 1 Hard Copy Printer
8 1 Photocopier
9 2 Oscilloscope
10 1 Logical Analizer
Table 3.3.3-1
Equipment, PAT.
PC" PC
CAMPS CCIS
E5 E1, (E1),(E1) E6
E2, E3, E4, E7,
E9 E9, E10
…01…Figure 3.3.3-1
Equipment Configuration. PAT.
3.3.3.3 S̲W̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
At the Preliminary Acceptance Test the CCIS-link simulator
from the Factory Acceptance Test is substituted with
a real CCIS-system. The CCIS-link shall be able to
send normal messages of all types:
Transactions:
a) Narrative messages
b) Data messages
c) VDU displays
d) Comments
Transparent service messages:
e) Transaction acknowledgement messages
f) Channel Check messages
g) Final number messages.
CCIS-to-PC Service messages:
h) Bust
i) No-message.
On the CAMPS side of PC a CAMPS configuration shall
be available for sending and receiving all normal messages
mentioned above from a) to g). The PC reactions upon
illegal messages shall be approved at the Factory Acceptance
Test.
3.3.3.4 P̲e̲r̲s̲o̲n̲n̲e̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The Preliminary Acceptance Test will be supervised
by CR test engineers and SHAPE operational staff will
assist in operating end-systems.
Two operators (SHAPE), one at each end-system, shall
be present 2., 3. and 4. testday.
Two testengineers (CR) shall conduct the test from
the first testday to the last testday.
Further, Shape shall offer one or more people with
efficient knowledge of the PC-system and the test procedures
to work through the test. Charge shall be available
for approving or disapproving the effectuated teststeps
and the Test Report.
3.3.3.5 S̲e̲c̲u̲r̲i̲t̲y̲
During the Preliminary Acceptance Test SHAPE shall
be in charge in all matters concerning on-site security.
Therefore CR expects a set of rules to be delivered
from SHAPE 14 days before the test shall commence.
3.3.3.6 R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
It is the responsibility of CR to conduct the testing
of the PC-System. SHAPE will follow the teststeps and
fill in classification marks for each step. Following
marks shall be used:
r - right (approved)
n - note (discrepancy)
f - failure (defect)
3.3.4 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̲
Security Certification Test is performed at SHAPE's
initiative by TRW. This test shall ensure that the
equipment and the installation of PC 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.
3.3.5 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̲,̲ ̲C̲A̲M̲P̲S̲
When the PC-system has been installed at sites CR will
conduct a functional test of PC when connected to CCIS
and CAMPS. The Provisional Site Acceptance Test (PSAT)
will be performed immediately following the Preliminary
Acceptance Test. The test is performed to verify the
functioning of the PC when connected to CCIS and CAMPS.
PSAT will be based on prestored test messages to be
sent from the CAMPS/SCARS side and SHAPE supplied test
messages to be sent from the CCIS system.
3.3.5.1 M̲i̲l̲e̲s̲t̲o̲n̲e̲ ̲C̲h̲a̲r̲t̲.̲ ̲P̲S̲A̲T̲
The detailed schedule for the Provisional Site Acceptance
Test is shown in figure 3.3.5-1. The complete test
will take 5 days commencing with one day for orientation
purposes and ending up with one day for preparation
and approval for the Test Report.
3.3.5.2 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
The equipment to be used during the Provisional Acceptance
Test is listed in Table 3.3.5-1.
The test configuration is shown in Figure 3.3.5-1.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DAY NO.: ̲ ̲ ̲ ̲1̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲2̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲3̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲4̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲5̲ ̲ ̲ ̲ ̲ ̲
̲ ̲E̲V̲E̲N̲T̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲ ̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲
̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲
SYSTEMS ̲ ̲ ̲
ORIENTATION
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DOCUMENTATION ̲ ̲ ̲
ORIENTATION
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 1: X
NONE-MODE TEST
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 2: XX
MAINTENANCE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 3: XX
LOCAL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 4:
XXXXX
OPERATIONAL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 5:
XX
TEST
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PREPARATION OF
̲
̲
̲
TEST REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
APPROVAL OF
̲
̲
̲
̲
TEST REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Figure 3.3.5-1
Milestone Chart, PSAT, CAMPS.
EQUIPM.
̲ ̲N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲Q̲u̲a̲n̲t̲i̲t̲y̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲a̲m̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
1 2 (3) Processor Unit
2 1 Adapter Crate
3 1 VDU
4 1 Rack
5 1 CAMPS CONFIGURATION
6 1 TTY-terminal
7 1 Hard Copy Printer
8 1 Photocopier
9 2 Oscilloscope
10 1 Logical Analizer
Table 3.3.5-1
Equipment, PSAT.
PC" PC
CAMPS CCIS
E5 E1, (E1),(E1) E6
E2, E3, E4, E7,
E9 E9, E10
Figure 3.3.3-1
Equipment Configuration. PSAT, CAMPS.
3.3.5.3 S̲W̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
At the Provisional Site Acceptance Test the CCIS-link
simulator from the Factory Acceptance Test is substituted
with a real CCIS-system. The CCIS-link shall be able
to send normal messages of all types:
Transactions:
a) Narrative messages
b) Data messages
c) VDU displays
d) Comments
Transparent service messages:
e) Transaction acknowledgement messages
f) Channel Check messages
g) Final number messages.
CCIS-to-PC Service messages:
h) Bust
i) No-message.
On the CAMPS side of PC a CAMPS configuration shall
be available for sending and receiving all normal messages
mentioned above from a) to g). The PC reactions upon
illegal messages shall be approved at the Factory Acceptance
Test.
3.3.5.4 P̲e̲r̲s̲o̲n̲n̲e̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The Provisional Site Acceptance Test will be supervised
by CR test engineers and SHAPE operational staff will
assist in operating end-systems.
Two operators (SHAPE), one at each end-system, shall
be present 2., 3. and 4. testday.
Two testengineers (CR) shall conduct the test from
the first testday to the last testday.
Further, Shape shall offer one or more people with
efficient knowledge of the PC-system and the test procedures
to work through the test. Charge shall be available
for approving or disapproving the effectuated teststeps
and the Test Report.
3.3.5.5 S̲e̲c̲u̲r̲i̲t̲y̲
During the Provisional Site Acceptance Test SHAPE shall
be in charge in all matters concerning on-site security.
Therefore CR expects a set of rules to be delivered
from SHAPE 14 days before the test shall commence.
3.3.5.6 R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
It is the responsibility of CR to conduct the testing
of the PC-System. SHAPE will follow the teststeps and
fill in classification marks for each step. Following
marks shall be used:
r - right (approved)
n - note (discrepancy)
f - failure (defect)
3.3.6 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̲,̲ ̲S̲C̲A̲R̲S̲
When the SCARS-system is ready at Site 1 (SHAPE) CR
will conduct a functional test of PC when connected
to SCARS. The Provisional Site Acceptance Test (PSAT)
will be performed following the PSAT, CAMPS of the
PC-system. The test is performed to verify the functioning
of the PC-SCARS link.
PSAT will be based on SCARS messages to be sent from
the SCARS side and SHAPE supplied test messages to
be sent from the CCIS system.
3.3.6.1 M̲i̲l̲e̲s̲t̲o̲n̲e̲ ̲C̲h̲a̲r̲t̲.̲P̲S̲A̲T̲
The detailed schedule for the Provisional Acceptance
Site Test is shown in Figure 3.3.6-1. The complete
test will take 5 days commencing with one day for orientation
purposes and ending up with one day for preparation
and approval for the Test Report.
3.3.6.2 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
The equipment to be used during the Provisional Acceptance
Test is listed in Table 3.3.6-1.
The test configuration is shown in Figure 3.3.6-1.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DAY NO.: ̲ ̲ ̲ ̲1̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲2̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲3̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲4̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲5̲ ̲ ̲ ̲ ̲ ̲
̲ ̲E̲V̲E̲N̲T̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲ ̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲
̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲ ̲ ̲1̲ ̲2̲ ̲3̲ ̲4̲
SYSTEMS ̲ ̲ ̲
ORIENTATION
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DOCUMENTATION ̲ ̲ ̲
ORIENTATION
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 1: X
NONE-MODE TEST
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 2: XX
MAINTENANCE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 3: XX
LOCAL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 4:
XXXXX
OPERATIONAL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GROUP 5:
XX
TEST
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PREPARATION OF
̲
̲
̲
TEST REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
APPROVAL OF
̲
̲
̲
̲
TEST REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Figure 3.3.6-1
Milestone Chart, PSAT, SCARS.
EQUIPM.
̲ ̲N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲Q̲u̲a̲n̲t̲i̲t̲y̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲a̲m̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
1 2 (3) Processor Unit
2 1 Adapter Crate
3 1 VDU
4 1 Rack
5 1 SCARS CONFIGURATION
6 1 TTY-terminal
7 1 Hard Copy Printer
8 1 Photocopier
9 2 Oscilloscope
10 1 Logical Analizer
Table 3.3.6-1
Equipment, PSAT.
PC" PC
SCARS CCIS
E5 E1, (E1),(E1) E6
E2, E3, E4, E7,
E9 E9, E10
Figure 3.3.6-1
Equipment Configuration. PSAT, SCARS:
3.3.6.3 S̲W̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
At the Provisional Site Acceptance Test the CCIS-link
simulator from the factory Acceptance Test is substituted
with a real CCIS-system. The CCIS-link shall be able
to send normal messages of all types:
Transactions:
a) Narrative messages
b) Data messages
c) VDU displays
d) Comments
Transparent service messages:
e) Transaction acknowledgement messages
f) Channel Check messages
g) Final number messages.
CCIS-to-PC Service messages:
h) Bust
i) No-message.
On the SCARS side of PC a SCARS configuration shall
be available for sending and receiving all normal messages
mentioned above from a) to g). The PC reactions upon
illegal messages shall be approved at the Factory Acceptance
Test (by a CAMPS simulation).
3.3.6.4 P̲e̲r̲s̲o̲n̲n̲e̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The Provisional Site Acceptance Test will be supervised
by CR test engineers and SHAPE operational staff will
assist in operating end-systems.
Two operators (SHAPE), one at each end-system, shall
be present 2., 3. and 4. testday.
Two testengineers (CR) shall conduct the test from
the first testday to the last testday.
Further, Shape shall offer one or more people with
efficient knowledge of the PC-system and the test procedures
to work through the test. Charge shall be available
for approving or disapproving the effectuated teststeps
and the Test Report.
3.3.6.5 S̲e̲c̲u̲r̲i̲t̲y̲
During the Provisional Site Acceptance Test SHAPE shall
be in charge in all matters concerning on-site security.
Therefore CR expects a set of rules to be delivered
from SHAPE 14 days before the test shall commence.
3.3.6.6 R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
It is the responsibility of CR to conduct the testing
of the PC-System. SHAPE will follow the teststeps and
fill in classification marks for each step. Following
marks shall be used:
r - right (approved)
n - note (discrepancy)
f - failure (defect)
3.3.7 O̲n̲-̲S̲i̲t̲e̲ ̲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 operational system
and its environment complies with the security requirements
stated in the SRS, section 7 and related documents
listed there.
4̲ ̲ ̲T̲E̲S̲T̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲A̲N̲D̲ ̲E̲V̲A̲L̲U̲A̲T̲I̲O̲N̲
4.1 T̲E̲S̲T̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
The test shall be conducted on the PC and end-systems
equipment. (Refer to section 3.3).
Execution of the In-Plant Functional Test shall be
performed by the CR Test engineer.
Execution of the On-site Functional Test shall be performed
by the Site Operational staff under CR's supervision.
A SHAPE representative shall be appointed as Test Witness
for the verification.
Any reported departure from the specified system functions
shall be logged in Test Report and evaluated by the
test supervisor.
Table 4-1 shows the lay-out of Test Procedure records
to be specified in the Test Procedures.
Each Test Procedure record may contain one or more
references to 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 execution.
It is foreseen that each functional Test Phase will
require availability of each applicable combination
of end-systems for 40 hours distributed throughout
the test periods (see Figure 3.2-1). Time for test
shall primarily be allocated 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 "Discrepancy Note" if applicable.
(Refer to section 4.3.2).
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DATE : 82-07-25
TEST ITEM : (name of function under test)
TEST NO. : FAT 1
REFERENCES : Appendix of FAT 1 Test Report
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
STEP ACTIONS & INPUTS EXPECTED RESULTS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1 Masterclear system
on CPU/SCM module (M) on VDU
2 Type: "INIT" on OC (L) on VDU
(expected contents
of
a data dump +
reference)
3 Type: "LOGON CCIS
SHAPE PASW CAMPS" (0) on VDU
(further results)
. ................... .....................
. .................. .....................
. ................... .....................
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
COMMENTS: TEST WITNESSES:
Example showing lay-out ..................
of Test Procedure record ..................
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Figure 4.1-1
SAMPLE TEST PROCEDURE RECORD
4.1.1 R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲ ̲M̲a̲p̲p̲i̲n̲g̲
This section contains a listing of the PC requirements
as stated in the SRS table of contents.
For each of the listed requirements a cross reference
is made indicating the planned verification method.
For each requirement which is plannes to be verified
it is further indicated in which Test the verification
is planned to take place.
Figure 4.1-2 shows the hierarchy of the PC Acceptance
and gives the numbers of the Tests.
A more detailed mapping of stated requirements onto
Test Groups, Functions and Cases are stated in the
PC/TPR/001 section 3.3, with the Function/Test Matrix,
section 3.4 as guide.
PC
ACCEPT
IN ON Test
PLANT SITE Locations
TEST TEST
FAT PAT PSAT
1 2 3 4 5 6 7
COMSEC CAMPS CCIS TRWSEC CAMPS SCARS COMSEC
ON INTF. INTF. ON CCIS CCIS ON
Tests
EQUIPM. EQUIPM. FUNCT. FUNCT. INSTAL.
Phases
Figure 4.1-2
Test Plan Hiearchy
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
VERIF. TEST
PHASE
METHOD
Requirement A B C D 1 2 3 4 5 6 7
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
2. Technical Overview X
2.1 System Overview, Location and Purpose X
2.2 Connectivity and Mode of Operation X X X
2.3 Circuit Usage Flexibility X X X
2.4 Facilities and Functions X X X X X X
2.5 Installation X
2.6 Equipment Configuration X
2.7 Message and Data Handling X X X X X
2.8 Control X X X X X X X X X
2.9 Security X X X X
X
2.10 Software X
2.11 Supervisor and Control Function X X X
2.12 Implementation and Testing X
3. Technical Requirements X
3.1 Equipment to Be Provided X
3.1.1 General X X X X X X
3.1.2 Integration of SHAPE Supplied Equipment X X X X X X
3.1.3 Performance and Interface Characteristics X
of SHAPE Supplied Equipment
3.1.4 Quantities of Equipment to Be Supplied X
by SHAPE
3.1.5 Interchange Circuits - Electrical X
Characteristics
3.1.6 Equipment to Be Provided by CR X
3.2 Communication Links between Systems X
3.2.1 Mode of Operation X X X X X X
3.2.2 Baud Rates X
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
VERIF. TEST
PHASE
METHOD
Requirement A B C D 1 2 3 4 5 6 7
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
3.3 Transaction Interchange Requirements X
3.3.1 Messages, Types and Formats X X X X X X
3.3.2 Transaction Characteristics X X X X X X
3.3.3 Format Definition Parameters
3.3.4 Format Control X X X X X
3.3.5 Precedence and Preemption X X X X X
3.3.6 Converter Performance Requirements X
3.3.7 Alphabet X X
3.3.8 Traffic Control X X X X X
3.4 Converter Requirements X
3.4.1 Converter Characteristics X
3.4.1.1 Configuration X
3.4.1.2 Interactive Operation X X X X X X
3.4.2 Assistance Facilities and Functions X X X X X
3.4.3 System Initialization X X X X X X
3.4.4 Recovery X X X X X X
3.4.5 Reconfiguration X X X X X
3.4.6 Maintenance Requirements X X X X X X
3.4.7 Interface Characteristics X X X X X X
4.1.2 S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
With reference to PC SDS, the functions of the following
headings may be used as verification during the Tests.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Section
No. Function
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2. SUMMARY OF REQUIREMENTS ...................
2.1 SYSTEM DESCRIPTION ........................
2.1.1 End Systems Survey ........................
2.1.1.1 CAMPS/SCARS Protocols .....................
2.1.1.1.1 Transaction Flow ..........................
2.1.1.1.2 Transaction Acknowledgement ...............
2.1.1.1.3 Transaction Error Handling ................
2.1.1.1.4 Preemption ................................
2.1.1.1.5 Transaction Sequence Control ..............
2.1.1.1.6 Service Messages ..........................
2.1.1.1.7 System Constants ..........................
2.1.1.2 CCIS Protocols ............................
2.1.1.2.1 Transaction Flow ..........................
2.1.1.2.2 Transaction Acknowledgement ...............
2.1.1.2.3 Transaction Error Handling ................
2.1.1.2.4 Preemption ................................
2.1.1.2.5 Transaction Sequence Control ..............
2.1.1.2.6 Service Messages ..........................
2.1.1.2.7 Transaction Override ......................
2.1.1.2.8 System Constants ..........................
2.1.2 Message Structure .........................
2.1.2.1 Message Type ..............................
2.1.2.2 Message Format ............................
2.1.2.3 Alphabet ..................................
2.1.2.4 Message Length ............................
2.1.3 CAMPS/SCARS Message Fragmentation .........
2.1.3.1 Frame Structure ...........................
2.1.4 CCIS Message Fragmentation ................
2.1.4.1 Segment Structure .........................
2.1.4.2 Frame Structure ...........................
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Section
No. Function
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.2 SYSTEM FUNCTIONS ..........................
2.2.1 System Control ............................
2.2.1.1 System Modes ..............................
2.2.2 Message Processing ........................
2.2.2.1 Transaction Flow ..........................
2.2.2.2 Transaction Acknowledgement ...............
2.2.3 Transaction Precedence Handling ...........
2.2.2.4 Transaction Sequence Control ..............
2.2.2.5 Service Messages ..........................
2.2.2.6 Protocol Functions ........................
2.2.2.7 Message Control Field Conversion ..........
2.2.3 Initialization and Close Down .............
2.2.3.1 Initialization ............................
2.2.3.2 Close Down ................................
2.2.4 Error Detection and Error Handling ........
2.2.4.1 Unrecoverable Errors ......................
2.2.4.2 Frame Transmission Errors .................
2.2.4.3 Message Control Errors ....................
2.2.5 Recovery ..................................
2.2.6 Statistics Collection .....................
2.2.7 Security ..................................
2.3 CHARACTERISTICS ...........................
2.3.1 Timing ....................................
2.3.2 Throughput ................................
2.3.3 Flexibility ...............................
4. SOFTWARE SYSTEM DESIGN ....................
4.1 SOFTWARE SYSTEM DESCRIPTION ...............
4.1.1 Functional Specification ..................
4.1.1.1 System Modes and Commands .................
4.1.1.2 Maintenance Mode ..........................
4.1.1.3 Local Mode ................................
4.1.1.4 Operational Mode ..........................
4.1.1.5 Test Mode .................................
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Section
No. Function
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
4.1.2 Software Specification ....................
4.1.3 Data Flow and Control Logic ...............
4.1.3.1 Message Data Flow .........................
4.1.3.2 Control Logic .............................
4.1.4 Common Data ...............................
4.1.4.1 PC Message Buffer .........................
4.1.4.1.1 Message Descriptor ........................
4.1.4.1.2 Message Text ..............................
4.1.5 Interfaces ................................
4.1.5.1 Operator Interface ........................
4.1.5.1.1 Prompt ....................................
4.1.5.1.2 Command Syntax ............................
4.1.5.1.3 Syntax Error Messages .....................
4.2 PACKAGE SPECIFICATIONS ....................
4.2.1 Command Interpreter (CI) ..................
4.2.2 Traffic Controller (TRC) ..................
4.2.3 CAMPS/SCARS Protocol Adapter (CSPA) .......
4.2.4 CAMPS/SCARS Low Level Protocols (CSLP)
....
4.2.5 CCIS Protocol Adapter (CPA) ...............
4.2.6 CCIS Low Level Protocols (CLP) ............
4.2.7 Maintenance Controller (MAC) ..............
4.2.8 System Generator and Initializer (SGI)
....
4.2 V̲E̲R̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲M̲E̲T̲H̲O̲D̲S̲ ̲A̲N̲D̲ ̲C̲O̲N̲S̲T̲R̲A̲I̲N̲T̲S̲
4.2.1 V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲M̲e̲t̲h̲o̲d̲ ̲T̲e̲r̲m̲s̲
The keeping of the requirements will be verified by
one of the following methods:
a) N̲o̲t̲ ̲A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲: No action will be taken.
b) E̲x̲a̲m̲i̲n̲a̲t̲i̲o̲n̲: This method is a non-functional verification,
such as visual inspection of the physical characteristics
of the item or of the documentation associated
with the item.
c) A̲n̲a̲l̲y̲s̲i̲s̲: This method is a non-functional verification,
such as deduction or translation of data, review
of analytical data, or performance of a detailed
analysis.
d) T̲e̲s̲t̲/̲D̲e̲m̲o̲n̲s̲t̲r̲a̲t̲i̲o̲n̲: This method is a functional
verification, such as actual operation wherein
the element of verification is instrumented, measured,
or displayed directly (test) or where the element
of verification is logically obvious, as the result
of some other verification, but not itself displayed
(demonstration).
4.2.2 S̲y̲s̲t̲e̲m̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲s̲
4.2.2.1 C̲o̲n̲d̲i̲t̲i̲o̲n̲s̲ ̲a̲t̲ ̲F̲A̲T̲
The verification will be conducted on a Protocol Converter
at the CR-factory in Ballerup by a CR Test Engineer.
The input data from the CAMPS side is a representative
batch of messages varying in type, precedence and classification
(refer to section 3.3.1). On the CCIS side where the
link is simulated, the same set of messages are to
be used for the verification.
4.2.2.2 C̲o̲n̲d̲i̲t̲i̲o̲n̲s̲ ̲a̲t̲ ̲P̲A̲T̲
The Preliminary Site Acceptance Test at SHAPE will
concentrate upon verification of the PC-CCIS interface
and the function of the Protocol Converter. The verification
will use the built-in Test Messages present in the
Protocol Converter together with the SHAPE supplied
Test Messages from the CCIS-system.
4.2.2.3 C̲o̲n̲d̲i̲t̲i̲o̲n̲s̲ ̲a̲t̲ ̲P̲S̲A̲T̲
The Protocol Converter shall be connected to both the
CCIS-system and the CAMPS-system and a functional verification
of the PC shall be performed.
4.2.3 E̲x̲t̲e̲n̲t̲ ̲o̲f̲ ̲S̲y̲s̲t̲e̲m̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The Protocol Converter is verified by means of two
sets of Test Messages. One is generated from the CAMPS
side of PC and the other is generated from the CCIS
side.
The Test Data-Set varies the parameters:
o Station Channel Identifier
o Message Type
o Message Precedence
o Message Classification
in such a way that one parameter varies at a time between
all its legal values plus one (an error-parameter)
while all other values are kept fixed.
4.2.4 D̲a̲t̲a̲ ̲R̲e̲c̲o̲r̲d̲i̲n̲g̲
For the verification of the PC functions, it will be
necessary to maintain three detailed logs of activities:
o Messages sent and received on CAMPS/SCARS
o Messages sent and received on CCIS
o Messages sent and received on PC
These logs are to be verified by the Operational Staff
and the supervisor after the printing.
4.2.5 S̲y̲s̲t̲e̲m̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲C̲o̲n̲s̲t̲r̲a̲i̲n̲t̲s̲
Execution of the verification in the FAT and PAT will
not be performed under operational equipment environment
conditions, and therefore the verification will not
provide any prove of conformance to throughput and
timing requirements. In the PSAT case, these verifications
are incorporated.
4.3 V̲E̲R̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲E̲V̲A̲L̲U̲A̲T̲I̲O̲N̲
Test evaluation is performed by the operational staff
participating in test execution. The evaluation shall
be based on comparison of the actual system response
to the expected response. Any discovered departure
from the specified system functions must immediately
be reported to the test supervisor, who will determine
if any impact is caused on the continued test execution.
This determination shall be based on the test criteria
definitions.
4.3.1 T̲e̲s̲t̲ ̲D̲a̲t̲a̲ ̲C̲r̲i̲t̲e̲r̲i̲a̲
The evaluation of test results are to be founded on
espected test results. For each Test Step a requirement
shall be fulfilled. If the test results equal the expected
results the verification is succeeded.
The tolerance of the test results depends on the verification
method:
T̲y̲p̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲a̲m̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲T̲o̲l̲e̲r̲a̲n̲c̲e̲ ̲ ̲ ̲
̲ ̲
A not applicable
B examination requirement
C analysis requirement
D demo/test expected results
…06…1 …02… …02… …02… …02…
The samples are given for each Test Case. The Test
Data can be classified in following types:
o Input
data
o Input
commands
o Output
data
o Output
notification
The types of Test Data are explained in section 4.4.2.
4.3.2 A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲C̲r̲i̲t̲e̲r̲i̲a̲
4.3.2.1 A̲c̲c̲e̲p̲t̲e̲d̲
If the PC is accepted SHAPE will sign a Provisional
Site Acceptance Protocol containing, if applicable,
a mutually agreed discrepancy list showing the agreed
date for clearance of each listed discrepancy.
The date of signature of the Provisional Acceptance
Protocol marks the date of the Provisional Acceptance
of the Site.
"Discrepancies" shall mean a non-compliance which does
not prevent completion of the provisional site acceptance.
However, any discrepancies existing at the time of
signing the Provisional Site Acceptance Protocol will
be listed in the protocol and dates for correction
of each will also be included.
4.3.2.2 N̲o̲t̲ ̲A̲c̲c̲e̲p̲t̲e̲d̲
If the PC is not accepted SHAPE will deliver to CR
in writing a "Notice of Defects" listing the defects
which prevented provisional acceptance of the site.
If SHAPE delivers a "Notice of Defects" then the date
on which SHAPE signs a "Correction of Defects Notice"
shall be the date of the Provisional Site Acceptance.
"Defects", as referred to above, means any non-compliance
with the contract by CR which prevents the normal operation
of the site.
4.4 T̲E̲S̲T̲ ̲C̲O̲N̲T̲R̲O̲L̲
4.4.1 M̲e̲a̲n̲s̲ ̲o̲f̲ ̲C̲o̲n̲t̲r̲o̲l̲
The tests will mainly be controlled by manual insertion
of input i.e. use of the Command Language on the Maintenance
VDU.
However, some semi-automatic means may be established,
eighter by using the build-in Test Messages or by SHAPE
supplied test messages supported by programs in the
end-systems.
4.4.2 T̲e̲s̲t̲ ̲D̲a̲t̲a̲
a) I̲n̲p̲u̲t̲ ̲D̲a̲t̲a̲ shall be chosen to exercise the worst
case effects on the system using a minimum of data
types and values.
b) I̲n̲p̲u̲t̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲ shall be used to control the system
under test.
c) O̲u̲t̲p̲u̲t̲ ̲D̲a̲t̲a̲ shall be compared to the expected results
of the test and approved as a part of the procedure.
d) O̲u̲t̲p̲u̲t̲ ̲N̲o̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ shall be given in form of prompts
or comments on the Maintenance VDU.
4.5 T̲E̲S̲T̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲A̲T̲I̲O̲N̲ ̲O̲U̲T̲L̲I̲N̲E̲
The documentation describing the PC Acceptance activi-
ties is divided into the following parts:
o Test Plan
o Test Procedure
o Test Reports
The documentation to be supplied by CR is indicated
in Table 4-1.
4.5.1 T̲e̲s̲t̲ ̲P̲l̲a̲n̲
The Test Plan document covers all PC Acceptance activities.
The structure of this document is guided by the Annex
I of the ADP 007-3.
4.5.2 T̲e̲s̲t̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
The Test Procedure document shall cover all PC Acceptance
activities, by giving more details to the Test Plan:
a) The Test Procedure Hierarchy
b) Detailed cross-reference between requirements and
Test Steps
c) Step-by-step test procedure.
4.5.3 T̲e̲s̲t̲ ̲R̲e̲p̲o̲r̲t̲
The Test Reports will be the Test Step Forms (copies
of Step-by-step procedures from the Test Procedure
document) with the Test Logs and Discrepancy Notes
as Annexes. All signed by the Test Witnesses.
Test Test Test Test
NOTE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲P̲l̲a̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲P̲r̲o̲c̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲R̲e̲p̲o̲r̲t̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1 X 1
2 X X X
3 X X
4 X 1
5 X X X
6 X X X
7 X 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Note 1: SHAPE is supplying all specific plans, procedures
and reports for the security verification.
Table 4-1
PC Acceptance Documentation
