top - download
⟦275838685⟧ Wang Wps File
Length: 5828 (0x16c4)
Types: Wang Wps File
Notes: SOFTWARE STAND. MANUAL
Names: »0081A «
Derivation
└─⟦83a4a04d1⟧ Bits:30005815 8" Wang WCS floppy, CR 0002A
└─ ⟦this⟧ »0081A «
WangText
…02…SD/STM/003
…02…SVO/800711…02……02…#
SOFTWARE ENGINEERING 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
…02…4 SUMMARY OF STANDARDS ..................... 5
…02……02…4.1 DESIGN GUIDELINE ..................... 5
…02……02…4.2 DESIGN GUIDELINE ..................... 6
…02……02…4.3 UDF STANDARD ......................... 7
…02……02…4.4 SOFTWARE PROBLEM HANDLING STANDARD ... 8
…02…5 DISTRIBUTION ............................. 7
1̲ ̲ ̲S̲C̲O̲P̲E̲
The Software Engineering Standard Manual describes
the standards and procedures which apply to software
development in the System Division (SD) of Christian
Rovsing A/S. The Manual is established in accordance
with Software Quality Assurance Plan SD/PLN/003.
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 software products developed
in the division 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 software 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 and the System Engineering
Departments.
Changes may be proposed by anyone concerned but only
such changes approved by both the above mentioned parties
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 Systems Division.
2̲ ̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲D̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
Quality Assurance Plan CPS/QAP/001
ADP-standard 007-3
HIPO-A Design Aid and Documentation Technique GC20-1851-1.
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̲
1 Software Terminology Standard
SD/STD/009
2 Software Design Guidelines
SD/STD/005
3 UDF Standard
SD/STD/006
4 PROBLEM HANDLING STANDARD
SD/STD/007
5 Software Subsystem Documentation Standard
SD/STD/013
6 Software Module/Package Documentation Standard
SD/STD/008
7 SOURCE CODE LAYOUT STANDARD
SD/STD/014
8 SWELL PROGRAMMING STANDARD
SD/STD/015
9 SOFTWARE INSPECTION STANDARD
TBD
10 SOFTWARE VERIFICATION STANDARD
SD/STD/012
11 SOFTWARE TEST PROCEDURE STANDARD
SD/STD/011
12 SOFTWARE TEST REPORT STANDARD
TBD
4̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲S̲
4.1 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̲
TBD
4.2 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 frame work 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. The form and organisation of
the 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 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.3 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… 1…02…CONTROL INFO
…02……02… 2…02…ACTIONS AND PROBLEMS
…02……02… 3…02…NOTES
…02……02… 4…02…FUNCTIONAL CAPABILITIES
…02……02… 5…02…REQUIREMENTS
…02……02… 6…02…INTERFACES
…02……02… 7…02…DESIGN
…02……02… 8…02…CODE
…02……02… 9…02…TEST SPECIFICATIONS AND PROCEDURES
…02……02…10…02…TEST RESULTS
…02……02…11…02…SUPPORT TOOLS
…02……02…12…02…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.
4.4 S̲O̲F̲T̲W̲A̲R̲E̲ ̲P̲R̲O̲B̲L̲E̲M̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲ ̲
TBD.
4.5 Software Subsystem Documentation Standard
SD/STD/013
4.6 Software Module/Package Documentation Standard
SD/STD/008
4.7 SOURCE CODE LAYOUT STANDARD
SD/STD/014
4.8 SWELL PROGRAMMING STANDARD
SD/STD/015
4.9 SOFTWARE INSPECTION STANDARD
TBD
4.10 SOFTWARE VERIFICATION STANDARD
SD/STD/012
4.11 SOFTWARE TEST PROCEDURE STANDARD
SD/STD/011
4.12 SOFTWARE TEST REPORT STANDARD
TBD
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:
TBD
