view release on metacpan or  search on metacpan

lib/Docs/US_DOD/SDD.pm  view on Meta::CPAN

unit. The SDD may refer to software units by any name(s) consistent
with the design methodology being used.

=head2 4.1.2

Show the static (such as 'consists of') relationship(s)
of the software units. Multiple relationships may be presented,
depending on the selected software design methodology (for example,
in an object-oriented design, this paragraph may present the class
and object structures as well as the module and process architectures
of the CSCI).

=head2 4.1.3

State the purpose of each software unit and identify the
CSCI requirements and CSCI-wide design decisions allocated to
it. (Alternatively, the allocation of requirements may be provided
in 6.a.)

=head2 4.1.4

Identify each software unit's development status/type (such
as new development, existing design or software to be reused as
is, existing design or software to be reengineered, software to
be developed for reuse, software planned for Build N, etc.) For
existing design or software, the description shall provide identifying
information, such as name, version, documentation references,
library, etc.

=head2 4.1.5

Describe the CSCI's (and as applicable, each software unit's)
planned utilization of computer hardware resources (such as processor
capacity, memory capacity, input/output device capacity, auxiliary
storage capacity, and communications/network equipment capacity).
The description shall cover all computer hardware resources included
in resource utilization requirements for the CSCI, in system-level
resource allocations affecting the CSCI, and in resource utilization
measurement planning in the Software Development Plan. If all
utilization data for a given computer hardware resource are presented
in a single location, such as in one SDD, this paragraph may reference
that source. Included for each computer hardware resource shall
be:

=over 4

=item 1

The CSCI requirements or system-level resource allocations
being satisfied

=item 2

The assumptions and conditions on which the utilization
data are based (for example, typical usage, worst-case usage,
assumption of certain events)

=item 3

Any special considerations affecting the utilization (such
as use of virtual memory, overlays, or multiprocessors or the
impacts of operating system overhead, library software, or other
implementation overhead)

=item 4

The units of measure used (such as percentage of processor
capacity, cycles per second, bytes of memory, kilobytes per second)

=item 5

The level(s) at which the estimates or measures will be
made (such as software unit, CSCI, or executable program)

=back

=head2 4.1.6

Identify the program library in which the software that
implements each software unit is to be placed

=head2 4.2 Concept of execution.

This paragraph shall describe the concept of execution among
the software units. It shall include diagrams and descriptions
showing the dynamic relationship of the software units, that is,
how they will interact during CSCI operation, including, as applicable,
flow of execution control, data flow, dynamically controlled sequencing,
state transition diagrams, timing diagrams, priorities among units,
handling of interrupts, timing/sequencing relationships, exception
handling, concurrent execution, dynamic allocation/deallocation,
dynamic creation/deletion of objects, processes, tasks, and other
aspects of dynamic behavior.

=head2 4.3 Interface design.

This paragraph shall be divided into the following subparagraphs
to describe the interface characteristics of the software units.
It shall include both interfaces among the software units and
their interfaces with external entities such as systems, configuration
items, and users. If part or all of this information is contained
in Interface Design Descriptions (IDDs), in section 5 of the SDD,
or elsewhere, these sources may be referenced.

=head2 4.3.1 Interface identification and diagrams.

This paragraph shall state the project-unique identifier
assigned to each interface and shall identify the interfacing
entities (software units, systems, configuration items, users,
etc.) by name, number, version, and documentation references,
as applicable. The identification shall state which entities have
fixed interface characteristics (and therefore impose interface
requirements on interfacing entities) and which are being developed
or modified (thus having interface requirements imposed on them).
One or more interface diagrams shall be provided, as appropriate,
to depict the interfaces.

=head2 4.3.x (Project-unique identifier of interface).

This paragraph (beginning with 4.3.2) shall identify an
interface by project-unique identifier, shall briefly identify