Document Number:
Version number: 1.0 level:
Document Name: Detailed Design Manual Project Name: Project Lead:
Write: 2003-04-16 Approval:
Design unit: Document modification information table modification time repair the content modified man's note
{Software function name} Detailed design manual
Identification number: Version: 0.1 Previous Version: Status: Draft | Review | Initial Version | Revision Release Date: March 25, 2003
Abstract Brief description of the content modification history version of the document, the author modified the content review number 0.1 Zhou Baozhen draft
Contents 1. Overview 62. System Structure 63. Data Structure 64. Detailed Description of Functional Modules 65. Time Limits (Optional) 76. Storage Restrictions (Optional) 77. Drop Table 7
1. Overview Description Detailed Design The software function content that will be implemented, and the subsystem associated with it. If a graphic design tool is used, you must specify the full path name of the module generated by the Graphic Design tool. 2. The system structure describes the software system function module (and submodules), including name, marking, and hierarchy relationship. And provide indexing and practical commissioning maintenance guides. In the system structure diagram, you want to include the description of the data and the access method (read, write, increase, deletion, modification, etc.) for data storage. The content of the symbol is explained (eg modules, parameters, storage calls, etc.). 3. The data structure is described in detail on the data structure in the system. 4. Detailed description of the function module Detailed description of the function module and sub-module in the system, to describe information: Module name said Main function description Name of the input parameters of the module , data type, order , Format, etc. Name of the output parameters of the module , data type, order, format, and error message, etc. Process and function call Data reference (global, local) Module processing flow (using flow chart, judgment table, etc. and complement the text description) Graphical user interface design (explain the interface format in the form of chart, Location, type, agreement, etc. of the interface elements, For operation and steps, the necessary descriptions are performed. If the prototype of the system or module is established , Need to explain the location of the function module in the prototype) Interface (in a graphical manner, the upper module belonging to this module and subordinate module belonging to this module, Description Parametric assignment method, Description Direct " Associated data structure) Assumptions and restrictions (describing the assumptions and restrictions accepted by this module) Pseudo code 5. Time limit (optional) Time limit is only related to the external constraints of the module (Internal time is a design problem). Time demand in the early decision of the software life cycle. However, some environmental factors (operating systems, language) will inevitably have a certain impact on time requirements. The time issues and restrictions that are taken from the detailed design process should be described in this chapter. Such as: The function of performing a lookup must be completed within 100 milliseconds. 6. Storage restrictions (optional) The system should be decided in the early days of the software lifecycle. However, the storage problems and restrictions of detailed design leads should be described in this chapter. Storage restriction issues include problems and memory restrictions for persistent storage restrictions of data. 7. Retrospective Table Detailed Design Documentation Section Summary Design Demand Number Requirements Number
