top - download
⟦8c8251142⟧ Wang Wps File
Length: 11244 (0x2bec)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN50.00«
Derivation
└─⟦17da89677⟧ Bits:30006229 8" Wang WCS floppy, CR 0126A
└─ ⟦this⟧ »~ORPHAN50.00«
WangText
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
7 ACCEPTANCE TEST PROGRAM PLAN .......................
7.1 GENERAL ........................................
7.1.1 Verification Procedures ....................
7.1.2 Product Assurance Provisions ...............
7.13 First Article Qualification Tests ..........
7.2 FACTORY QUALIFICATION AND PROVING TEST .........
7.2.1 Hardware Functional Verificaiton ...........
7.2.2 Environmental Verification .................
7.2.3 Sofare Functional Verification ............
7.2.4 MPF Subsystem Verification .................
7.2.5 Reliability and Maintainability Verification
7.2.5.1 Hardware Reliabilty Verification .......
7.2.5.2 Softare Reiability Verification .......
7.2.5.3 Hardware Maintainability Verification
..
7.2.5.4 Softare Maintainability Verification
...
7.3 FACTORY POST PRODUCTION TEST .....................
7.4 ON SITE TESTS ...................................
7.4.1 Provisional Site Acceptance Test ...........
7.4.2 Subnetwork Test ............................
7.4.3 Overall System Acceptance Test ..............
…86…1 …02… …02… …02… …02…
7. A̲C̲C̲E̲P̲T̲A̲N̲C̲E̲ ̲T̲E̲S̲T̲ ̲P̲R̲O̲G̲R̲A̲M̲ ̲P̲L̲A̲N̲.
7.1 G̲e̲n̲e̲r̲a̲l̲
The test program for the MPF subsystem has the objective
to provide a systematic, incremental verification of
the subsystem's compiance with all baseline requirements.
The objective of the test program is accomplished by
means of the existing, general Christian Rovsing A/S
Product Assurance provisions supplemented with the
specific test activities outlined in this section.
The overall test program will be described in a Test
Plan in accordance with ACE MANUAL No. 96-1-1, Annex
I ADP Standard 007-3. The Test Plan will contain a
list of the tests to be performed, test objectives,
methods and criterias. The Test Pla will further contain
the schedule and time phasing of the tests
7.1.1 V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
Throughout the test program all verification will be
accomplished by using approved procedures describing
the actions, objectives and required testresults for
each test segment. A method will be provided for recording
the actual test results and for comparing them with
the required test results. These procedures will be
prepared and approved prior to the test operation.
Verification at an level or category will be performed
by one of the following methods:
a. 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 an item or of the documentation associated with
an ite.
b. A̲n̲a̲l̲y̲s̲i̲s̲
This method is a non-functional verification, such
as reduction or translation of data, review of
analytical data or review of performance from a
detailed test.
c. T̲e̲s̲t̲/̲D̲e̲m̲o̲n̲s̲t̲r̲a̲t̲i̲o̲n̲
This method is a functional verification f hardware
and/or software such that measurements and observations
of correct operation can be made. A test is where
the element of verification is instrumented, measured
or displayed directly. A demonstration is where
the element of verificationis logically obvious,
as being a necessary constraint to some other result,
but is not itself displayed.
7.1.2 P̲r̲o̲d̲u̲c̲t̲ ̲A̲s̲s̲u̲r̲a̲n̲c̲e̲ ̲P̲r̲o̲v̲i̲s̲i̲o̲n̲s̲
All products manufactured by Christian Rovsing A/S
are subject to the provisions of the company's Qualiy
Assurance Program. This program is compliant with
AQAP-1: "Nato Quality Control System Requirements for
Industri".
7.1.3 F̲i̲r̲s̲t̲ ̲A̲r̲t̲i̲c̲l̲e̲ ̲Q̲u̲a̲l̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲T̲e̲s̲t̲s̲ ̲(̲F̲A̲Q̲T̲)̲
All the hardware items included in this proposal either
have previously been approved or are now being approved
by NATO for use on he CAMPS program as part of a CAMPS
First Article Qualification Program.
As the hardware requirements for the CROSSFOX MPF equipment
are identical to those for the CAMPS equipment it is
assumed that no additional FAQT is necessary. The
FAQT docuentation from the CAMPS program will be provided
on customer request.
7.2 F̲A̲C̲T̲O̲R̲Y̲ ̲Q̲U̲A̲L̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲A̲N̲D̲ ̲P̲R̲O̲V̲I̲N̲G̲ ̲T̲E̲S̲T̲ ̲(̲F̲Q̲T̲)̲
The objective of this test is to verify that the MPF
subsystem hardware and software have been designed
and manufactured in ccordance with the functional,
environmental, operational and reliability requirements
specified. The verification activity will be performed
in compliance with the IFB as follows.
7.2.1 H̲a̲r̲d̲w̲a̲r̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
When the first MPF subystem hardware has been integrated
a functional verification will be performed. The verification
will consist of interface requirements and functional
hardware requirements.
7.2.2 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲a̲l̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
After completion of the functional hardware verification
a verification of all environmental requirements will
be performed.
7.2.3 S̲o̲f̲t̲w̲a̲r̲e̲ ̲F̲u̲c̲t̲i̲o̲n̲a̲l̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This activity will consist of a verification of the
Operating System functions including security features
contained herein. Further, all functions provided
by the application software will be verified.
7.2.4 M̲P̲F̲ ̲S̲u̲b̲s̲y̲t̲e̲m̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲
This verification will be performed under simulated,
operational conditions by means of a Standard Test
Environment simulator.
The test simulator will be used for simulation of external
interfaces of the MPF subsystem.
The test imulator will be able to generate pseudorandom
MPF input traffic, which is representative of the specified
operational message traffic. The generated message
traffic load will be at least 0.5 Erlang for low speed
channels and 0.3 Erlang for mediumspeed channels.
The simulation will include message traffic corruption
by transmission media failure and noise.
The objective of the MPF Subsystem verifiation is to
verify the operational requirements and to provide
a demonstration of the softare reliability. The software
reliability will e assessed by monitoring the Mean
time between Discovery of Software Defects (MDSD).
The acceptance criteria for the MPF Subsystem verification
is an accumulated test time of 240 hours, with no more
than one failure during the 240 hours.
7.2.5 e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲ ̲a̲n̲d̲ ̲M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The objective of this verification is to demonstrate
compliance with the reliability and maintainability
characteristics specified in the IFB, para 4.5.
7.2.5.1 H̲a̲r̲d̲w̲a̲r̲e̲ ̲R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Th hardware reliability verification will be provided
by calculations of reliability figures in accordance
with the principles described in MIL HDBK 217: "Reliability
Prediction of Electronic Equipment".
Reliability figures have been calculated fo all units
contained in the MPF subsystem. The calculated values
show that no unit has a predicted MTBF value lower
than 17000 hours. Due to the high predicted reliability
values no test verification of MTBF values is planned.
However, the hardwre reliability will be monitored
throughout the development, test and warranty period
by means of the Failure Reporting System described
in section 6.4.
7.2.5.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The software reliability will be assessed by monitoring
if the MDSD during the 240 hours accumulated test time
of the MPF Subsystem Veriication.
7.2.5.3 H̲a̲r̲d̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
A set of maintenance and diagnostics (M&D) programs
will be provided as tools for corrective maintenance
actions.
A demonstration of the M&D program capabilities will
provide verificatio of the predicted MTTR values.
Preventive maintenance procedures will be provided
in a maintenance manual.
7.2.5.4 S̲o̲f̲t̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
A set of utility programs, editor, compiler, linker
and debugger will be provided as toos for software
maintenance.
A demonstration of the utility program capabilities
will provide verification of the software maintainability.
7.3 F̲A̲C̲T̲O̲R̲Y̲ ̲P̲O̲S̲T̲ ̲P̲R̲O̲D̲U̲C̲T̲I̲O̲N̲ ̲T̲E̲S̲T̲ ̲(̲F̲P̲P̲T̲)̲
The objective of this test is to provide a final verification
of the actual site equipment configuration before shipment
from the factory.
Before shipment to site the complete MPF subsystem
is assembled at the factory and the functional verification
of hardware and software is performed with a customer
approved subset of the FQT test procedure.
7.4 O̲N̲ ̲S̲I̲T̲E̲ ̲T̲E̲S̲T̲S̲
7.4.1 P̲r̲o̲v̲i̲s̲i̲o̲a̲l̲ ̲S̲i̲t̲e̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲
The objective of this test is to verify that all equipment
contained in the MPF subsystem have been correctly
installed.
The verification will consist of execution of the functional
hardware and software test.
7.4.2 S̲b̲n̲e̲t̲w̲o̲r̲k̲ ̲T̲e̲s̲t̲
The objective of these tests are to verify the functions
of the subnetwork consisting of the MPF subsystem interfaced
to the:
o SNT category iii
- NICS TARE Network
- Ship-to-Shore Stations
- Broadcast Stations
o SNT category iv
- Alternate MPF
The test will consist of a complete verification of
all functions to be provided by the subnetwork.
7.4.3 O̲v̲e̲r̲a̲l̲l̲ ̲S̲y̲s̲t̲e̲m̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲T̲e̲s̲t̲
After completion of all individual subnetwork tests an overall
sytem test shall be performed.
The objective of the overall system test is to demonstrate
that the delivered system will provide the required
functions, facilities and softare reliabiity.
The test shall be performed by continuous operation
of the MPF system for a period of 90 days without "Software
failures".
The concept "Software failure" will be defined in the
Acceptance Test Plan.
We are prepared to divide the overall ystem test into
two subtests. The first subtest will consist of a
complete functional test. Test procedures will be
specified by the contractor and shall be agreed by
the purchaser.
Initially all functions shall be exercised one by one,
subsequnt…02…Zunctional testing shall be performed by execution
of functions in parallel.
Any deviation from the specified functional requirements
shall be corrected and all functions affected by the
corrections shall be retested.
After completion of the functional subtest the final
operational subtest can be initiated. The test scenarios
and procedures for the operational test shall be prepared
by the purhaser together with the contractor.
The operational test shall be successfully performed
by exercising the complete CROSS FOX network over 3
periods each lasting at least 10 days.
Any software modifications required to comply with
operational ad security requirements shall have to
be made and demonstrated by the contractor before the
final accpetnce of the software
