top - download
⟦ca3de672c⟧ Wang Wps File
Length: 6126 (0x17ee)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN43.03«
Derivation
└─⟦84647c47a⟧ Bits:30005817 8" Wang WCS floppy, CR 0014A
└─ ⟦this⟧ »~ORPHAN43.03«
WangText
the entire process section to the edge of the entire output section. Frequently, a
wide arrow is used for emphasis here. This is particularly useful for overview diagrams.
i) Arrows may cross over each other or may join to
show that they point to the same process step number.
Crossing arrows should be kept to a minimum. Many
times they can be avoide by rearranging the data
items, enclosing data items within a box (data
group), leaving space between process steps, or
using keyed data arrows (see below). The following
example shows crossing arrows.
From the above, a user can tell that the arrow
to step 1 is from FLDA and FLDC, and that the arrow
to step 2 crosses the other arrow and is from data
FLDB.
j) It is more difficlt to illustrate crossing arrows
with data reference arrows......... 5
B.4 PROCESS SECTION ..........................
17
A̲P̲P̲E̲N̲D̲I̲X̲ ̲C̲
A̲P̲P̲E̲N̲D̲I̲X̲ ̲D̲
D.1 BIT LEVEL DIAGRAMS .......................
1
D.2 WORD LEVEL DIAGRAMS ......................
1
D.3 CHARACTER LEVEL DIAGRAMS ................
2…86…1 …02… …02… …02… …02…
1̲ ̲ ̲S̲C̲O̲P̲E̲
This standard is a derivative of software standard
man- ual SD/STM/003 and has the same scope and applicability.
2̲ ̲ ̲P̲U̲R̲P̲O̲S̲E̲
This standard describes the organsation and layout
to be used for documents containing specification of
Software units of module or lower levels (see system
design guideline for definition of module level).
3̲ ̲ ̲O̲R̲G̲A̲N̲I̲S̲A̲T̲I̲O̲N̲
3.1 S̲Y̲N̲O̲P̲S̲I̲S̲
The content of Software module pecifications shall
be organized as described in NATO's ADP standard 007-3
annex D. This standard is found as Appendix A
3.1.2 T̲a̲y̲l̲o̲r̲i̲n̲g̲ ̲o̲f̲ ̲S̲y̲n̲o̲p̲s̲i̲s̲
Software modules may vary considerably in size, complexity
and content, therefore, this synopis may need some
tayloring to adapt it to the actual case.
Some of the paragraphs in the synopsis may be redundant
as no information exists which fits in them. They
shall be kept in the Table of Contents but marked "Not
Applicable".
Informationmay exist which does not fit directly into
any paragraph. In this case an interpretation of the
synopsis must be made to find the best fit. Invention
of new paragraphs or rearranging shall be avoided unless
absolutely necessary.…86…1 …02… …02… …02… …02…
3.2 L̲A̲Y̲O̲U̲T̲
The editorial style of all documents shall be as described
in Document Layout Standard SD/STD/002.
3.3 C̲O̲N̲T̲E̲N̲T̲
The main content of all parts of the specification
hall be narrative descriptions written in plain English
language.
3.3.1 L̲a̲n̲g̲u̲a̲g̲e̲ ̲S̲t̲y̲l̲e̲
The paramount consideraion in a specification is its
technical essence, and this should be presented in
a language free of vague and ambiquous terms and usig
the simplest words and phrases which convey the intended
meaning. Inclusion of essential information shall
be complete, either by direct statements or by reference
to other documents. Consistency in terminology and
organization of material willcontribute to the specification's
clarity and usefulness. Sentences shall be as short
and concise as possible. Punctuation should aid in
reading and prevent misreading. Well-planned word
order requires a minimum of punctuation. When extensive
pnctuation is necessary for clarity, the sentence(s)
shall be rewritten. Sentences with compound clauses
shall be converted into short and concise separate
sentences.
3.3.2 D̲i̲a̲g̲r̲a̲m̲s̲
A series of diagramtic aids shall be used extensively
to enhace the understandability of the text. These
aids, their form and use will be described in detail
in chapter 4.
Note that although diagrams in some cases may constitute
the major part of a section they shall still be considered
an aid for the tex and never a replacement of it.…86…1
…02… …02… …02… …02…
4̲ ̲ ̲D̲I̲A̲G̲R̲A̲M̲S̲
4.1 H̲I̲E̲R̲A̲R̲C̲H̲I̲C̲A̲L̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲ ̲C̲H̲A̲R̲T̲
A major point in describing the processing of a software
module is the breakdown of the processing into subprocesses
which agai may be broken down into sub-subprocesses
through several levels.
To describe the interrelationship between the partial
processes and define their level in the breakdown hierarchy
an overview chart shall be used.
An example of an overview chartis shown in fig. 1.
In this chart each partial process is represented by
a box containing a descriptive title of the process
and a reference to the paragraph in which it is further
described.
4.2 I̲N̲P̲U̲T̲ ̲-̲ ̲P̲R̲O̲C̲E̲S̲S̲ ̲-̲ ̲O̲U̲T̲P̲U̲T̲ ̲C̲H̲A̲R̲T̲S̲
For each of the partial processes defined in the overview
chart shall be produced a chart showing the relation
between the inputs, the outputs and the subprocesses
within the process.
The standard for those charts are shown in Appendix
B which is an extract from IBM's HIPO manual.
Note that the following restriction to the normal HIPO
concept must be adhered to:
- The process box sall only contain a listing of
the subprocesses, ordered as closely as possible
to the sequence in which they will be performed.
- No attempt shall be made to show the logic relation
or control flow between subprocesses.
4.3 F̲L̲O̲W̲G̲R̲A̲M̲S̲
For eac of the partial processes defined in the overview
chart shall be produced a flowgram showing the logical
interrelation between the subprocesses.
These flowgrams shall be produced in accordance with
the rules given in Appendix C. (In preliminary ssue
is used an offprint of an article in Electronic design).
4.4 D̲A̲T̲A̲ ̲C̲H̲A̲R̲T̲S̲
In the sections of specification containing data descriptions,
this is mainly
section 3b Interfaces
3c Storage
4b Inputs
4c Outputs
shall be used Data Charts to show the layout of data
items of any complexity higher than single words or
simple arrays.
These Data Charts shall have a format as shown in Appendix
D.…86…1 …02… …02… …02… …02…
