Summary design manual
1 Introduction
1.1 Writing
Description Writing the purpose of this profile design manual, pointing out the expected readers.
1.2 background
Description:
a. The name of the software system is developed;
b. List this item's task proposal, developer, user, and computing station (center) that will run the software.
1.3 definition
List the definitions of the specimen used in this document and the original phrase of the foreign letter group word.
1.4 Reference
List the relevant references, such as:
a. The approved planning task book or contract of the project, the approval of the superior authority;
b. Other issued documents belonging to this project;
c. Files, information, information, including the software development standards you want. List the title, file number, publishing date, and publishing units of these files, indicating that the source of these files can be obtained.
2 overall design
2.1 demand regulations
Note The functional performance requirements of the main input and output projects of the system, detailed description can be found in Appendix C.
2.2 Operation Environment
Briefly illustrate the provisions of the operating environment (including hardware environment and support environments) of the system, detailed description, see Appendix C.
2.3 Basic design concepts and process flows
Describe the basic design concepts and process flows of the system, try to use the form of the chart.
2.4 structure
In the form of a list and block diagram, the division of the system element (each layer module, subroutine, utility, etc.) of the system is to indicate the identifier and function of each system element, and the control between each element is given. And controlled relationship.
2.5 Relationship between functional and program
This article uses a matrix diagram to illustrate the allocation relationship between various functional requirements:
Program 1 Program 2 ... Program n function requirements 1 √
Functional requirements 2
√
......
Functional demand N
√
√
2.6 manual processing process
The artificial processing process (if any) has to be included during the operation of the software system.
2.7 I have not yet been issued
Note The designers believe that the designers believe that the designers must solve before the system is completed.
3 interface design
3.1 User Interface
The commands will be provided to the user and their syntax structure, and the answer information of the software.
3.2 External interface
Note The arrangements of all interfaces of the system are included in the interface between software and hardware, and the interface relationship between the system and the support software.
3.3 Internal interface
Describe the arrangement between the interfaces between the various system elements within the system.
4 operation design
4.1 Operation module combination
Note The combination of various operating modules caused by the system is applied to different external operations, indicating that the internal modules and support software over each run.
4.2 Running Control
Description Method and operation steps of each of the external operational controls.
4.3 Running time
Note Each run module combination will occupy the time of various resources.
5 system data structure design
5.1 Type of logical structure design
Given the name, identifier of each data structure used in this system, each data item, the logo, the record, the text, and the level of the identification, definition, length, and the interaction between the levels between them. .
5.2 Points of physical structure design
A physical relationship (index, device, storage area), design considerations, design considerations, design considerations, design considerations, design considerations (indexes, devices, storage areas), design considerations (indexes, devices, storage areas), design considerations (indexes, devices, storage areas), design considerations (indexes, devices, storage areas), design considerations (indexes, devices, storage areas), design considerations (indexes, devices, storage areas), design considerations.
5.3 Relationship between data structure and procedures
Describe the form of each data structure and access to these data structures:
6 system error handling design
6.1 error message
The form, meaning and processing method of the system output information when each possible error or fault occurs is said to be in a list.
6.2 Remedy
Note Workarounds that may be taken after the failure, including:
a. Backup Technique Description Preparation Techniques Adopted, when the original system data is lost, the established and initiated technique, for example, periodically record the disk information to the tape is a backup technology for disk media;
b. Equipment Technical Description Preparation Techniques Adopted, use another system or method of another efficiency to obtain some parts of the desired result, such as an automatic system's marking technology can be manual records of manual operation and data ; C. Recovery and Reacture Technical Description The recovery re-start technology will be used, so that the software will resume from the fault point or to re-run the software from the beginning.
6.3 System maintenance design
Description For the convenience of system maintenance, the arrangements made in the program internal design include specifically arranged inspection and maintenance of the system in the program. The correspondence between the various programs can be used in the form of a matrix map;
