Summary Design Manual:
The specification is a summary of the actual phase of work, it should illustrate the functional allocation, module division, overall structure, input and output and interface design, operation design, data structure design, and error processing design, etc., provide the basis for detailed design. 1 Introduction 1.1 Write: Clave the purpose of writing a summary design manual, indicating the reader object. 1.2 Project Background: Should include ● Project commission units, development units, and competent authorities ● The software system is related to other systems. 1.3 Definition: Lists the willingness of the definitions and abbreviations of the dedicated terms used in this document. 1.4 References: ● List the author, title, number, publishing date, publishing unit or data source ● Project approved planning task book, contract or superior aircraft; project development plan; demand specifications; test plan (Premier Draft); User Operation Manual ● The standards or specifications used by the documentation are used. 2 Task Overview 2.1 Target 2.2 Demand Overview 2.3 Conditions and Restrictions 3 Overall Design 3.2 Overall Structure and Module External Design 3.3 Function Allocation: Indicates the relationship between the functions and program structure. 4 Interface Design 4.1 External Interface: Includes user interface, software interface and hardware interface. 4.2 Internal Interface: Interface between modules. 5 Data Structure Design 6 Logical Structure Design All Documents Unified Cover Formats are shown in the next page. 7 Physical Structure Design 8 Data Structure and Procedure Relationship 9 Operation Design 9.1 Operation Module Combination 9.2 Running 9.3 Running Time 10 Error Processing Design 10.1 Error Output Information 10.2 Error Processing Countermeasures: Settings, Performance Downgrading, Recovery, and Reproduction . 11 Safety Confidential Design 12 Maintenance Design Instructions for facilities for easy maintenance, such as maintenance modules.
