top - download
⟦df8131c0c⟧ Wang Wps File
Length: 5317 (0x14c5)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN04.00«
Derivation
└─⟦84f7719fc⟧ Bits:30006031 8" Wang WCS floppy, CR 0385A
└─ ⟦this⟧ »~ORPHAN04.00«
WangText
2.6.2.5 P̲a̲c̲k̲a̲g̲e̲ ̲D̲e̲s̲i̲g̲n̲ ̲S̲t̲a̲n̲d̲a̲r̲d̲
The following pages are an example of a normal package
design process.
4̲ ̲ ̲P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲I̲G̲N̲
(4.1) P̲A̲C̲K̲A̲G̲E̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
Section 4.1 of the packae specification has at package
level the same mission as chapter 4 in the SDS at system
level.
In total 4.1 gives the concurrent and sequential processing
within the package with clear definition of the role
of each sub-package which are describe more detailed
in section 4.2.x.
(4.1.1) F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This should be the first step in the analysis. The
package functions desolved in section 2.2.1 and 2.2.2
should be broken down to the level functional which
justifies allocatio of the subpackages described further
in section 4.2.x.
̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
A B C
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Common functions
Where common functions exist within a package the functional
break-down shall be continued to the level where all
common functions can be isolated.
(4.1.2) S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This section describes the allocation of functions
onto processes, shared procedures (between two processes),
monitor procedures (only for CSF, SSC, and DAMOS) or
co-routines.
Based on the above software component types sub-packages
shall be defned.
For each of the sub-packages the following elements
shall be contained.
1) Functions allocated to the subpackage (refer 4.1.1).
2) Software structure which corresponds with the functional
break-down of section 4.1.1.
The software strucure shall be presented by a chart
which shows the software break-down. (Similar to chart
presented in section 4.1.1).
(4.1.3) D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
Data flow and control logic related to major transaction
within a package shall be descrbed to the sub-package
level.
The functional flow must give the normal flow (as 2.2)
and the special flow (2.3).
The tools to document flow/logic are block diagrams
for process synchronization/communication and HIPO
for sequential processing.
(4.1.4) C̲o̲m̲m̲o̲n̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲ ̲(̲I̲n̲t̲e̲r̲n̲a̲l̲)̲
This should identify common data element (but not give
detailed layout in order to make 4.1.5 more readable).
(4.1.5) E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
This should identify data shared with other packages
which are defined in Data Def. Doc.
(4.1.6) I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The section shall define externa interfaces as well
as software package to package interfaces (excl. DAMOS,
IOC, CSF, and MMS). At minimum shall be references
to the appropriate ICDs shall be included.
Sub-package interfaces shall, furthermore, be identified
but not specified i details, as this shall take place
in section 4.2.x.5.
G̲e̲n̲e̲r̲a̲l̲ ̲C̲o̲m̲m̲m̲e̲n̲t̲s̲ ̲t̲o̲ ̲4̲.̲1̲.̲4̲,̲ ̲4̲.̲1̲.̲5̲,̲ ̲a̲n̲d̲ ̲4̲.̲1̲.̲6̲
In order to obtain a selfcontained and readable document
it may be necessary to include detailed information
in section 4.1.4 - 4.1.6. It shall owever be emphasized
that the master source for definition of data and package
interfaces are the AMSS data definition document and
the AMSS software interface control document.
(4.2.x) S̲u̲b̲-̲p̲a̲c̲k̲a̲g̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲s̲
This section shall expand thesubpackage design, as
described in section 4.1 to a level where all modules
(less than 250 source statements, refer SRS) are identified
and the functions defined.
(4.2.x.1) F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This section shall contain a functional brea-down to
such a level that all SW modules can be identified
taken all functional areas defined in section 2.2 and
4.1.1 into account.
(4.2.x.2) S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This section shall contain a description which identifies
all software components to be implemented (Refer 4.1.2).
(4.2.x.3) D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲l̲ ̲L̲o̲g̲i̲c̲
Data flow and control logic related to major transactions
within a subpackage shall be described.
The mandatory tool to specify flow/logic is HIPO for
sequential processing. Where functions are made up
of complex algorithms or decisionsthe HIPO charts may
be supplemented by flowgrams, structured pseudocode
and/or decision table.
Where concurrent processing exist blockdiagrams shall
be used to specify communication between software components.
(4.2.x.4) S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
Thi section shall define data which are pertinent to
the sub-package only. Package data or common data shall
be defined in 4.1.4 and 4.1.5.
(4.2.x.5) I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
This section shall specify interfaces between subpackages
within the package. Packag interfaces or external interfaces
shall be defined in the appropriate ICDs and referenced/defined
in section 4.1.6.
2.6. C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
Configuration Control is described in Volume II, section
7.3
2.6.4 P̲r̲o̲j̲e̲c̲t̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
An Automated Project Management System including critical
path analysis is available on the CR16 and can be offered
as an option.
