| 1. Introduction
1. 1 purpose of writing "to clarify the purpose of writing a summary design specification, indicating the reader object." 】
1. 2 Project Background "should be included. A The project's entrusted units, development units and competent departments. b The relationship between the software system and its F1 system. 】
1. 3 definition "lists the definitions and acronyms of the specialized terms used in this document. 】
1. 4 References "lists the author, title, number, date of publication, publication unit or source of the information, which may be Mao Kua: A. Approval of the project's approved plan of assignment, contract or superior authority; B. Project development Plan, C. Demand specification said ear book; d. Test plan (first draft), E. User manual (first draft), F. The materials referenced in the document, the standards or specifications adopted. 】
2. Task Overview
2. 1 goals
2. 2 Operating Environment
2. 3 Requirements Overview
2. 4 Conditions and limitations
3. Overall Design
3. 1 Processing Flow
3. 2 overall structure and module exterior design
3. 3 Functional Distribution "indicates the relationship between functions and the structure of the program. 】
4. Interface Design
4. 1 external interface "includes user interface, software interface and hardware interface. 】
4. interface between the 2 internal interface "modules. 】
5. Data Structure Design
5. 1 Logical Structure Design
5. 2 Physical Structure Design
5. 3 The relationship between data structure and program
6. Run the design
6. 1 combination of running modules
6. 2 Operation Control
6. 3 Run time
7. Error Handling design
7. 1 Error Output information
7. 2 error handling countermeasures "such as setting up fallback, performance degradation, recovery, and restart. 】
8. Security and confidentiality design
9. Maintenance Design
"Description is for the convenience of maintenance work facilities, such as maintenance modules. 】
|
