|
|
|
|
3.5 DEVELOP PROGRAM SPECIFICATION
For each lowest-level function identified in the System/Subsystem Specifications, prepare a detailed program specification. Develop in detail and document the functions, timing requirements, interfaces, input and output reports, and the accuracy and validity requirements. Include the following activities:
- 3.5.1 Describe the Functions of the Software Units
- 3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units
- 3.5.3 Describe Timing Requirements Placed on Software Units
- 3.5.4 Describe Support Software
- 3.5.5 Describe Interfaces With Other Application Software
- 3.5.6 Describe Storage Requirements
- 3.5.7 Describe the Degree of Security Required
- 3.5.8 Describe the Input and Output Data and Reports
- 3.5.9 Define the Data Retention Period
- 3.5.10 Describe the Logic of Each Software Unit
- 3.5.11 Prepare the Program Specifications Document
Table 3-5 defines the roles and responsibilities of key personnel for
developing program specifications.
|
Table 3-5. Roles and
Responsibilities for Developing |
|
|
Role |
Responsibility |
|
Project Manager |
Coordinates development of Program Specifications. Coordinates capacity planning with Operations. |
|
User |
Reviews preparation of Program Specifications. |
|
Developer |
Prepares Program Specifications. |
|
Quality Assurance |
Reviews Program Specifications for adherence to standards. |
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.1 Describe the Functions of the Software Units
Describe the functions that each program is expected to perform,
encompassing a level of detail that will allow the program to be coded in
software units. The functions should be taken directly from the corresponding
sections of both the Functional Requirements Document and the System/Subsystem
Specifications.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units
Describe the data accuracy requirements and data validity requirements imposed
on each software unit. Data accuracy may include identifying any mathematical
calculations to be performed by a program. Data validation identifies the edit
and error routines to be run on the data, such as ensuring that an all-numeric
field contains only numbers and no alphabetic or special characters.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.3 Describe Timing Requirements Placed on Software Units
Describe the timing requirements imposed on each software unit under varying
conditions such as throughput time, response time to queries and updates of
data files, response time of major program functions, sequential relationships
of program functions and data flows, priorities imposed by types of input and
change in modes of operation, timing requirements for the range of traffic load
under varying operational conditions, and input/output transfer time required
for disk and tape.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.4 Describe Support Software
Provide a description of the support software with which each software unit
must interact. Include support software, test software, and security software,
if needed. Provide the correct name, description, and documentation references
of each such software system, subsystem, and program. Included must be a
reference to the language (compiler, assembler, program, query) and to the
operating system to be used. If the operation of the software units to be
developed is dependent on forthcoming changes to other software, identify and
discuss the nature, status, and anticipated availability date of such changes.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.5 Describe Interfaces With Other Application Software
Describe the interfaces with other application software, including those
from other operational organizations. For each interface, include the following
information: type of interface, such as operator control of a terminal or
program interfaces with other programs; description of operational implications
of data transfer, including security considerations; data transfer requirements
to and from the subject program (including data content, sequence, timing,
format, volume, and processing); current formats of interchanged data;
interface procedures, including telecommunications considerations; interface
equipment; and data conversion requirements.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.6 Describe Storage Requirements
Describe the data storage requirements, including internal storage requirements, use of internal storage and auxiliary storage such as tape and disk, and the estimated quantity of storage required for each. Each program must consider the following types of information for the various storage media:
- Internal: Describe and illustrate the use of internal storage areas, including indexing and working areas. Briefly state the equipment constraints and design considerations that affect the use of internal storage.
- Device: List by device type all peripheral storage required and any constraints imposed on storage requirements by each storage device. State requirements for permanent and temporary storage, including overlays.
- Offline: Describe
the form, media, and storage requirements of all offline storage.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.7 Describe the Degree of Security Required
Determine the security classifications of the data used by the programs and
the degree of security required for the algorithms. Determine if the data is
always in a sensitive state. If the data becomes sensitive upon the occurrence
of specific events, describe those events. Specify the operational environment
that must exist when sensitive data of the system/subsystem are being
processed.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.8 Describe the Input and Output Data and Reports
Describe the input and output data and reports. For inputs, provide
information about the characteristics of each input to the program such as file
name, format and type of data; validation criteria; volume, frequency, and
means of entry; source document and its disposition; and security and privacy
considerations. For output, provide file name, report format, selection
criteria for display or output, output media, and disposition of products.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.9 Define the Data Retention Period
Determine the period of time the system/subsystem is required to retain its
data and include this retention period in the program specifications for each
of the data files used and/or created by the system.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.10 Describe the Logic of Each Software Unit
Describe the logic of each software unit in the Program Specifications.
Present the logical flow in graphical format showing the hierarchical
arrangement of the software units and their interfaces. Supplement the graphic
with pseudo-code and English language narrative explanations. Explain in detail
the methods for identifying error conditions and the resulting actions of the
program.
|
3.5.2 Describe Accuracy and Validity Characteristics Imposed on Software Units |
3.5.11 Prepare the Program Specifications Document
The development team prepares the Program Specifications document in accordance with SBA SDM documentation standards.
Update the requirements traceability matrix to reflect the allocation of
requirements to software units.
|
|
|
