top - download
⟦32b8f06d0⟧ Wang Wps File
Length: 8561 (0x2171)
Types: Wang Wps File
Notes: CPS/STM/001
Names: »0146A «
Derivation
└─⟦26e1ab804⟧ Bits:30005814 8" Wang WCS floppy, CR 0001A
└─ ⟦this⟧ »0146A «
WangText
…02…CPS/STM/001
…02…SVO/810429…02……02…#
CAMPS STANDARD MANUAL
…02……02…GENERAL
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
…02…1 SCOPE..................................... 4
…02……02…1.1 PURPOSE............................... 4
…02……02…1.2 RESPONSIBILITY........................ 4
…02……02…1.3 ORIGIN OF STANDARDS................... 4
…02…2 REFERENCED DOCUMENTS ..................... 5
…02…3 LIST OF APPLICABLE STANDARDS.............. 5
3.1 HARDWARE ENGINEERING, DESIGN AND
PRODUCTION .......................... 5
3.2 SOFTWARE ENGINEERING ................ 6
3.3 SYSTEM ENGINEERING AND CONFIGURATION
MANAGEMENT .......................... 7
…02…4 SUMMARY OF STANDARDS ..................... 7
4.B.A. SOFTWARE TERMINOLOGY STANDARD..........8 4.B.B.
DESIGN
GUIDELINE
...................
8
…02……02…4.B.C. UDF STANDARD........................ 8
…02…5 DISTRIBUTION ............................. 10
1̲ ̲ ̲S̲C̲O̲P̲E̲
The CAMPS Standard Manual describes the standards and
procedures which apply to system, hardware, software
and document development in the CAMPS project. The
Manual is established in accordance with Quality Assurance
Plan CPS/QAP/001.
1.1 P̲U̲R̲P̲O̲S̲E̲
It is the purpose of this manual to describe in details
the standards to which all products developed in the
project must comply, as well as all procedures to be
used during the development.
The manual will be organized in independent sections
each describing one particular aspect of project development.
1.2 R̲E̲S̲P̲O̲N̲S̲I̲B̲I̲L̲I̲T̲Y̲
This manual is established under the joint responsibility
of the Quality Assurance Department and the Project
Management.
Changes may be proposed by anyone concerned but only
such changes approved by both the above mentioned parties
and the customers Quality Assurance representative
will become effective.
1.3 O̲R̲I̲G̲I̲N̲ ̲O̲F̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲S̲
Standards and procedures to be contained in this manual
may be:
- designed originally for inclusion here
- designed for use elsewhere but approved as applicable
to the CAMPS Project
2̲ ̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲D̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
AQAP-1
AQAP-6
AQAP-13
CPS/QAP/001
NGTS 40
NGTS 45
NGTS 50
ACE DIRECTIVE 0007-3
MIL-STD-1521
3̲ ̲ ̲L̲I̲S̲T̲ ̲O̲F̲ ̲A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲S̲
The manual is divided into three volumes A, B, and
C with the contents listed below.
3.1 H̲A̲R̲D̲W̲A̲R̲E̲ ̲E̲N̲G̲I̲N̲E̲E̲R̲I̲N̲G̲,̲ ̲D̲E̲S̲I̲G̲N̲,̲ ̲A̲N̲D̲ ̲P̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
A-A CR80 DESIGN RETNINGSLINIER.
CSD/010/EPR/0004 ISSUE 1 791127
A-B CR80 DESIGN RETNINGSLINIER DERATING.
CSD/010/EPR/0005 ISSUE 1 791204
A-C NGTS 40 (COMMENTED)
A-D NGTS 45 (COMMENTED)
A-E NGTS 50 (COMMENTED)
A-F Extract of SRS - Construction Requirement
A-G Control and Calibration of Measuring and
Test Equipment
SD/STD/016 Issue 1 810219
A-H Indgangskontrol Standard (in preparation)
ST/STD/017
3.2 S̲O̲F̲T̲W̲A̲R̲E̲ ̲E̲N̲G̲I̲N̲E̲E̲R̲I̲N̲G̲
B-A Software Terminology Standard
SD/STD/009 Issue 1 801020
B-B Software Design Guidelines
SD/STD/005 Issue 1 801020
B-C UDF Standard
SD/STD/006 Issue 1 801020
B-D Software Subsystem Documentation Standard
SD/STD/013 Issue 1 801020
B-E Software Module/Package Documentation Standard
SD/STD/008 Issue 1.1 810422
B-F SOURCE CODE LAYOUT STANDARD (In preparation)
SD/STD/014
B-G SOFTWARE VERIFICATION GUIDELINES (In preparation)
SD/STD/012
B-H SOFTWARE TEST PROCEDURE STANDARD (Planned)
SD/STD/011
B-I SOFTWARE TEST REPORT STANDARD (Planned)
TBD
B-K SWELL PROGRAMMING STANDARD (In preparation)
SD/STD/015
B-L SOFTWARE INSPECTION STANDARD (Planned)
TBD
B-M EXTRACT OF SRS - SOFTWARE ENGINEERING REQUIREMENTS
B-N CAMPS SYSTEM DESIGN SPECIFICATION STANDARD
CPS/STD/002 Issue 1 801103
3.3 S̲Y̲S̲T̲E̲M̲ ̲E̲N̲G̲I̲N̲E̲E̲R̲I̲N̲G̲ ̲A̲N̲D̲ ̲C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲ ̲M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲
C-A Problem Handling Standard
SD/STD/007 Issue 1 801120
C-B DESIGN REVIEWS
ED/SPC/0001 Issue 1 800716
C-1 Tegningsstandard
ASD-STAN-004 Issue 2 790215
C-O Configuration Item Identification Standard
SD/STD/001 Issue 1 800923
C-P Document Layout Standard
SD/STD/002 Issue 1 800923
C-R Configuration Change Control Standard
SD/STD/003 Issue 1 801020
C-S Document Control Centre Standard
SD/STD/004 ISSUE 1 800923
4̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲S̲
"The majority of this section is TBD the following
are examples of intended content."
4.B.A. S̲O̲F̲T̲W̲A̲R̲E̲ ̲T̲E̲R̲M̲I̲N̲O̲L̲O̲G̲Y̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲
Contains a collection of Software Terms together with
a definition of their meaning.
The collection consists of a selection of general industry
standard terms as well as all terms which are given
a special definition within the company.
Terms which are given a special meaning within a project
are not contained but are deferred to the project specifications.
4.B.B. D̲E̲S̲I̲G̲N̲ ̲G̲U̲I̲D̲E̲L̲I̲N̲E̲
The Design Guideline does not define a specific design
methodology, but establishes a framework within which
software designers are given as much freedom as possible,
considering the outcome of different designs must fit
together and form a working system. The guideline
emphasizes the following points:
a) Software design must result in a documentation
which is complete. In form and organisation the
software design documents must be according to
the standards.
b) During the design as well as during other development
phases the UDF concept defined in the UDF standard
must be used.
c) Design shall be made in the Top-down mode resulting
in hierarchy of units where the lowest level shall
be an input to coding.
d) The design shall use "Structured Design" technics
resulting in modules with a high cohesion factor
and a low coupling level.
e) The design shall be kept simple, visible and free
of "tricks" and "smartness".
4.B.C. U̲D̲F̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲
The UDF Standard prescribes the use of a Unit Development
Folder as a tool in software development. The standard
contain the following demands:
a) All material produced as part of the development
of a software unit shall be collected in the UDF.
b) The UDF shall be organized in 12 sections each
containing one particular part of the material.
The sections are:
…02……02……02… 1 - CONTROL INFO
…02……02……02… 2 - ACTIONS/PROBLEMS
…02……02……02… 3 - NOTES
…02……02……02… 4 - FUNCTIONAL CAPABILITIES
…02……02……02… 5 - REQUIREMENTS
…02……02……02… 6 - INTERFACES
…02……02……02… 7 - DESIGN
…02……02……02… 8 - CODE
…02……02……02… 9 - TEST SPECIFICATIONS AND PROCEDURES
…02……02……02… 10 - TEST RESULTS
…02……02……02… 11 - SUPPORT TOOLS
…02……02……02… 12 - AUDIT REPORTS
c) The UDF shall be kept at the site of development
and always be up to date and complete.
d) The UDF shall always be open for Audits performed
by project management, Quality Assurance and Customer
Representative.
…86…1 …02… …02… …02… …02…
5 D̲I̲S̲T̲R̲I̲B̲U̲T̲I̲O̲N̲
A number of copies of this Manual will have an official
status and their availability and updating will be
controlled by The Configuration Management.
One person will be assigned responsible for each copy
as listed:
C̲O̲P̲Y̲ V̲O̲L̲U̲M̲E̲S̲ P̲L̲A̲C̲E̲ R̲E̲S̲P̲O̲N̲S̲I̲B̲L̲E̲
1 A-B-C QA Department SVO
2 A-B-C Project Manager GJ
3 A-B-C Systems Engineering Manager FE
4 A-B-C ILS Department Manager OE
5 A-B-C Software Management KNN
6 A-B-C Hardware Management BHB
7 A-B-C GQAR
8 A-B-C Configuration Manager KFL
9 A-B-C ILS Transportation KM
10 A-B-C ILS Maintenance FC
11 A-B-C ILS Training LU
12 A-B-C Systems Engineering Group TDJ
13 A---C Hardware Engineering Group SRA
14 --B-C S/W Package Group FH
SSC
15 --B-C S/W Package Group HKI
IOC-SAR-LOG-STP
16 --B-C S/W Package Group OKH
CSF-SFM-TMP
17 --B-C S/W Package Group BBC
TEP
18 --B-C S/W Package Group KNB
THP-MDP
19 A-B-C Christian Rovsing Corp. HMA
