1 Introduction
1.1 Purpose of Preparation
Describe the purpose of preparing this outline design specification, pointing out the intended audience.
1.2 Background
Describe:
a. The name of the software system to be developed;
b. List the task proposer, developer, user, and the computing station (center) that will run the software for this project.
1.3 Definitions
Lists the definitions of the specialized terms used in this document and the original phrases of foreign initialisms.
1.4 References
Relevant reference documents are listed, such as:
a. Approved programs or contracts of the project, and approvals from higher authorities;
b. Other published documents belonging to the project;
c. Documents and information cited in the document, including the software development standards to be used. List the title of these documents, document number, date of publication and publication unit, indicating that the source of these documents can be obtained.
2 Overall Design
2.1 Requirements Specification
Describe the major input and output items, and functional performance requirements for processing of this system, a detailed description of which can be found in Appendix C.
2.1.1 System Functions
2.1.2 System Performance
2.1.2.1 Accuracy
2.1 .2.2.2 Time Characterization Requirements
2.1.2.3 Reliability
2.1.2.4 Flexibility
2.1.3 Input/Output Requirements
2.1.4 Data Management Capability Requirements
2.1.5 Troubleshooting Requirements
2.1.6 Other Specialized Requirements
2.2 Operation Environment
Briefly describe the requirements for the operating environment (including hardware and support environment) of the system, and refer to Appendix C for a detailed description.
2.2.1 Equipment List the hard equipment required to run the software. Describe the newer devices and their specialized functions.
2.2.2 Supporting Software
Lists the supporting software, including the operating system to be used, compiled (or assembled) programs, and test support software.
2.2.3 Interfaces
Describe the interfaces, data communication protocols, etc., between the system and other systems
2.2.4 Controls
Describe the methods and control signals used to control the operation of the system, and describe the sources of these control signals.
2.3 Basic Design Concepts and Processing Flow
Describe the basic design concepts and processing flow of this system, using diagrams wherever possible.
2.4 Structure
Explain the division of system elements (modules, subroutines, utilities, etc.) in the form of lists and block diagrams, briefly describe the identifiers and functions of each system element, and hierarchically give the controlling and controlled relationships between the elements.
2.5 Functional Requirements and Program Relationships
This article uses a matrix diagram to illustrate the realization of each functional requirement and the allocation of each block of the program relationship: E.2.7E.2.7.
2.6 Manual Processes
Describe the manual processes, if any, that have to be included in the working process of this software system.
2.7 Unresolved Issues
Describe each issue that has not been resolved during the outlining process and that the designer believes must be resolved before the system can be completed.
3 Interface Design
3.1 User Interface
Describe the commands that will be made available to the user and their syntactic structure, as well as information about the software's answers.
Describes the definition of the hardware control panels that will be provided to the user for operation.
3.2 External Interfaces
Describes the arrangement of all interfaces between the system and the outside world, including the interface between the software and the hardware, and the relationship between the system and the supporting software.
3.3 Internal Interfaces
Describes the arrangement of interfaces between system elements within the system.
4 Operational Design
4.1 Operational Module Combinations
Describes the various combinations of operational modules that result from the application of different external operational controls to the system, and describes the internal modules and supporting software that are used for each of these operations.
4.2 Operational Controls
Describes the methods and procedures for each type of external operational control.
4.3 Runtime
Describes the amount of time that each combination of runtime modules will occupy various resources.
5 System Data Structure Design
5.1 Logical Structure Design Essentials
Give the name and identifier of each data structure used within the system, as well as the identification, definition, length, and hierarchical or tabular interrelationships between each of the data items, records, volumes, and faculties within them.
5.2 Physical Structure Design Elements
Give the storage requirements for each data item in each data structure used within the system, the access method, the unit of access, the physical relationship of access (indexes, devices, storage areas), design considerations, and confidentiality conditions.
5.3 Relationship of Data Structures to Programs
Describe each data structure and the form in which access to them is provided:
6 Design of System Error Handling
6.1 Error Messages
Describe, in a list format, the form, meaning, and handling of the system's output messages in the event of each possible error or malfunction condition.
6.2 Remedial Measures
Describe the possible workarounds that may be taken after a failure occurs, including:
a. Backup techniques Describe the backup techniques that are intended to be used to create and start up copies that are enabled in the unlikely event that the original system data is lost, e.g., periodic recording of disk information to tape is a backup technique for disk media;
b. Degradation Techniques describes the fallback techniques to be employed to achieve some portion of a desired result using another, less efficient system or method, e.g., a degradation technique for an automated system could be manual operations and manual recording of data;
c. Recovery and Restart Techniques describes the recovery and restart techniques to be used to resume execution of the software from the point of failure or to allow the software to be restarted from the beginning. re-run methodology.
6.3 System Maintenance Design
Describes the arrangements made in the internal design of the program for the convenience of system maintenance, including the arrangement of test points and dedicated modules in the program specifically for the inspection and maintenance of the system. The correspondence between the various programs may take the form of a matrix diagram as follows;