top - download
⟦01c1cacfd⟧ Wang Wps File
Length: 13602 (0x3522)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN70.08«
Derivation
└─⟦84647c47a⟧ Bits:30005817 8" Wang WCS floppy, CR 0014A
└─ ⟦this⟧ »~ORPHAN70.08«
WangText
…02…SD/STD/008
…02…SVO/800814…02……02…A-#
SOFTWARE DOCUMENTATION STANDARD
…02…DRAFT…02…GENERAL
A̲P̲P̲E̲N̲D̲I̲X̲ ̲A̲
1. G̲E̲N̲E̲R̲A̲L̲
a. Purpose Statement
b. Project References
c. Terms and Abbreviations
2. S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
a. Program Description
b. Program Functions
c. Accuracy and Validity
d. Timing e. Flexibility
3. E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
a. Support Software Environment
b. Interfaces
c. Storage d. Security
e. Cntrols
4. D̲E̲S̲I̲G̲N̲ ̲D̲E̲T̲A̲I̲L̲S̲
a. Program Operating Procedures
b. Inputs c. Outputs d. Data
Environment
e. Storage Allocation
f. Data Retention
g. Program Relationships
h. Program Logic
T̲A̲B̲L̲E̲ ̲A̲.̲1̲
The above table lists all the sections into which the
content of a software module (program) specification
shall be organized.
The following contains a description of the content
of each section.
A.1 G̲E̲N̲E̲R̲A̲L̲
a) Purpose Statement. Describe the purpose of the
Program Specification (PS) using the following
as a guide:
The objective of this Program Specification for
(Projet Name) (Project number) is to describe the
program design in sufficient detail to permit the
programmer/coder to produce a program.
b) Project References. This paragraph should summarize
the references applicable to the history and development
o the project. Specify the general nature of the
computer programs (tactical, inventory control,
war gaming, management information, etc) to be
developed and state its purpose and uses. Indicate
the project sponsor, user, and operating centre(s)
whih will run the completed computer programs.
List all applicable documents and specify their
source or author, reference number, title and security
classification. As a minimum, include the following:
(1) Functional Description/Requirement Specifcation.
(2) Associated System/Subsystem Specifications.
(3) Related Program Specifications.
(4) Other pertinent documentation or significant
correspondence not specified in the Functional
Description.
c) Terms and Abbreviations. List orinclude in an appendix
any terms, definitions, or acronyms unique to this
document and subject to interpretation. Do not
include item names or data codes.
A.2 S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲ ̲
a) Program Description. This paragraph should describe
the program to provide a frame of reference for
the remainder of the document. It should sumarize
the system requirements and refer to the documentation
of higher order systems/subsystems and related
programs, as required.
b) Program Functions. Describe the functions of the
program. Note, if a program does not in itself
satisfy systemor subsystem functions, state how
the aggregate of programs completely satisfies
the functions. Although the descriptions of the
functions may be refined and more detailed, they
must relate to the subsystem or system functions
and be stated in sucha manner that program environment
can be related to them.
c) Accuracy and Validity. Describe the requirements
for program accuracy. Changes in the accuracy requirements
from the next higher order document will be explicitly
identified. Accuracy rquirements for mathematical
calculations, input and output data must be considered.
d) Timing. Describe any timing requirements placed
on the program. Changes in the timing requirements
from the next higher order document should be identified.
Th following requirements should be considered:…86…1
…02… …02… …02… …02…
…02…
(1) Throughput time.
(2) Response time to queries and for updates of
data files.
(3) Response time of major program functions.
(4) Sequential relationships of program fuctions
and data flows.
(5) Priorities imposed by inputs or changes in
modes of operation.
(6) Requirements for varying traffic loads.
(7) Sequencing and interleaving programs and systems
(including the ability to interrupt a program
withou loss of data).
(8) Transfer time required for I/O devices (disk,
drum, tape, etc.)
(9) Internal processing time.
e) Flexibility. Describe any requirements for the
program to deal with changing systems, e.g. operational
changes, and interacion with new or improved programs.
Identify those components and procedures which
may be subject to change.
A.3 E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
Specify the current environment of the system and indicate
any changes from what is described in the System/Susystem
Specifications.…86…1 …02… …02… …02… …02…
…02…
a) Support Software Environment. Describe support
software which will interact with the computer
programs being developed. Provide the nomenclature
and documentation references ofeach such system,
subsystem, and program for both support and test
software. Indicate which languages (compiler, assembler,
program, query, etc) and operating system will
be used. Discuss the nature, status and implementation
date of any changes tosupport software which will
impact on the computer programs being developed.
b) Interfaces. Describe the interfaces with other
applications computer programs, including those
of other operational capabilities or military organizations.
These indiidual interfaces should include the following:
(1) Types of interface, such as operator control
of a terminal or program interfaces with other
programs.
(2) Operational implications of data transfer,
including security requirements.
(3) Reuirements for data transfer to and from the
subject program (including data content, sequence,
timing, format, volume and processing), and
characteristics of communications media/systems
used.
(4) Formats of interchanged data.
(5) Interface pocedures, including telecommunications
considerations.
(6) Interface equipment.
(7) Data conversion requirements.
c) Storage. Describe the requirements and usage for
both internal and auxiliary program storage. Provide
the following informaion for the various storage
media for each program:…86…1 …02… …02… …02… …02…
…02…
(1) Internal storage, number of words/auxiliary
core bank or bytes/auxiliary core bank, number
of banks.
(2) Drum storage, number of words/field, number
of fields, drum, numbe of drum assemblies.
(3) Disk storage, number or words/zone or bytes/cylinder,
number of zones/disk or cylinders/disk, number
of disks/disk unit, number of disk units.
(4) Tape storage, number of adapters, number of
tape drives/adapter, numbe of tapes.
In addition, allocate the machine storage into
permanent and temporary areas.
d. Security. Describe the computer program, its classified
components, the inputs, outputs, and the data bases.
e. Controls. Include in this paragraphprogram controls
such as record counts, accumulated counts, batch
controls, etc. State if no specific controls are
to be established at the program level.
A.4 D̲E̲S̲I̲G̲N̲ ̲D̲E̲T̲A̲I̲L̲S̲
a) Program Operating Procedures. Delineate any special
requirments necessary for the implementation of
system operating procedures, and discuss how the
executive support programs interact with the other
programs.
b) Inputs. Describe in detail each type of input applicable
to the program. This description may be with the
program or subprogram. Type each input according
to its use in the prgram (such as parameter, data
type A, B, etc.) and provide the following information
as applicable:
(1) Title and tag
(2) Number of items
(3) Item description to include number and
type of characters (numeric, alpha, decimal,
signed, unigned), range of values, accuracy
requirements.
(4) Means of entry and initiation procedures;
e.g., typewriter, card, tape, sensor, internal.
(5) Length of input including special handling
requirements due to variations in length.
(6) Epected volume and frequency including
special handling (such as queueing and
priority handling) for high density periods.
(7) Priority; e.g. routine, emergency.
(8) Disposition other than processing, such
as logging, hard copy reproduction f input,
storage location, and custodian.
(9) Security classification of input and individual
items.
(10 Flexibility, such as capability of omitting
or adding items.
(11) Requirements for timeliness.
(12) Throughput time.
(13) Specal handling, such as specification
of special control cards.
This paragraph should provide examples of prepared
inputs and preparation forms, such as input creation
sheets and communication message forms.…86…1 …02…
…02… …02… …02… …02…
c) Outputs. This paragraph should describe each type
of output applicable to the program. This description
may be by the program or subprograms. Categorise
each output by type (suh as quality control, data
type A, B, etc.) and provide the following information
as applicable:
(1) Title and tag.
(2) Format to include headings, line spacing,
arrangement, totals, etc.
(3) Number of items.
(4) Describe each item roviding number and
type of characters (alpha, numeric, symbol,
etc) range of values, accuracy requirements,
supporting background information (e.g.
maps) which will be presented.
(5) Include the criteria for data selection
for display, e.g., slection of a maintenance
report may be on the basis of active records
in a file of aircraft type and aircraft
usage.
(6) Describe plots or graphic displays and
include the coordinates and symbols to
be used, type of graphic technique (i.e.,
poits or continuous), number of curves
per sheet, etc.
(7) Preprinted form requirements.
(8) Means of display; e.g., VDU, printer, typewriter,
projector, alarm type.
(9) Length of output, including special handling
requirements due to varitions in length
(such as pages of printout, feet of paper
tape, etc.).
(10) Expected volume and frequency, including
special handling (such as queuing and priority)
for high density periods.…86…1 …02… …02…
…02… …02… …02…
(11) Priority, e.g., routine, emergency.
(12) Timing requirements, e.g., response time.
(13) Program recipients and their use of displays;
e.g., notification, trends, or brefings.
(14) Disposition, including logging, film and
hard copy printout reproduction and storage,
number of copies required for distribution,
place of storage, person responsible for
permanent copy, retention period, and special
handling requirments because of bulk, classification,
or timing.
(15) Security classification of output and individual
items.
(16) Explanation of symbols.
(17) Conditional and status indicators (code
and conditional definition). Include examples
of progrm outputs.
d) Data Environment. Provide a detailed description
of the files, tables, dictionaries, program interrelationship
with the tables, storage allocation, intermediate
data structures, and data retention requirements
to include as applicabe:
(1) Title and tag.
(2) Content description.
(3) Parameter - start and end of file.
(4) Number of records or entries.
(5) Record parameter - start and end of record.
(6) Relationship of each record to the common
data base.
(7) Storage, to include type and amount required
and, if known, beginning and ending addresses.…86…1
…02… …02… …02… …02…
…02…
(8) Normal file order; other orders if required
for special purpose.
(9) Classification.
e) Storage Allocation. Describe the allocation of
internal and auxiliary storage a follows:
(1) Storage media.
(2) Available storage on each medium.
(3) Addresses of available storage.
(4) Erasable working storage.
f) Data Retention. Describe requirements for data
retention as follows:
(1) Historic informaton to include collection
of data to be retained, format, storage
medium, and time parameters.
(2) Data for periodic reports; e.g., time retained
after report generation for summary reports.
(3) Data for summary reports such as time retainedafter
summary report.
g) Program Relationships. Interrelationships of a
program with the data base(s) should be described
to show how those files and tables are used in
each program function.…86…1 …02… …02… …02… …02…
…02…
h) Program Logic. Logical flow may be presented primarily
in the form of flow charts or structured design
diagrams (when structured programming is used to
code programs). A narratve presentation, when appropriate,
should be used to supplement the charts/diagrams.
All charts/diagrams should be keyed to the higher-order
charts in the SS, if applicable, or the FD. Provide
a detailed description of the processing performed
by te program. For each program function, in paragraph
2b of the PS, describe the operation of the program
and include the algorithmic or logic data manipulations
and decision processes involved. Conditions being
tested for purposes of branching, the mthods for
identifying error conditions, and the resulting
actions of the program should be explained in detail.
