1.1 The purpose of the preparation
Note the preparation of the detailed design specification of the purpose, pointing out that the expected audience.
a. To be the name of the development of software systems;
b. Mission of the project sponsors, developers, users and run the program System Center.
This document sets out the specialized terminology used in the definition and foreign language, the first letter of the original word phrases.
Together with the relevant reference materials, such as:
a. The project plan approved mission or book contract, approval of higher authorities;
b. Belong to this project have been published in other documents;
c. Throughout this document reference to the documents, including the use of software development standards. These documents are listed in the title, document number, publication date and publishing units, be able to obtain these documents indicate the source.
2 procedures for the system structure
Using a series of charts listing the procedures of each system (including in each module and subroutine) the name, identifier and their structural relationship between the level.
3 procedure 1 (identifier) Design Description
From the beginning of this chapter, one by one to give all levels of each of the programs in design considerations. Give the following outline is aimed at the general situation. For a specific module, in particular, are relatively low-level modules or subroutines, which are often a lot of entries and it belongs on a layer of modules corresponding to the contents of the same entry, in which case, as long as easy to illustrate this that can be.
3.1 Procedure Description
Give a brief description of the procedure, that arrangements for the design of the main purpose of the significance of this procedure, and also the characteristics of this procedure (the case of permanent or non-resident memory? Whether the subroutine? Men are available or can not be men of ? whether coverage requirements? are the order of treatment or concurrent treatment Pu ... .. etc.).
Shows that the procedure should have the function, to be used in IPO plans (that is, deal with one input output Figure 1) form.
Description of the procedure all the performance requirements, including accuracy, flexibility and time characteristics of the request.
Transfusion of 3.4 people
Give for each entry features, including the name, logo, data types and formats, data values of the effective range, enter approach. Quantity and frequency, input media, input data sources and security conditions and so on.
Output of 3.5
Give an output of each of the properties, including the name, logo, data types and formats, data values of the effective range, output format, quantity and frequency, the output media, graphics and symbols on the output of the note, security conditions and so on.
Detailed description of the procedures for the selected algorithm, the specific formula and calculation steps.
3.7 flow logic
Graph (for example, flow chart, determine the table, etc.) with the necessary instructions to express the logical flow of this procedure.
Using the form of plans of this program belongs on a layer of modules and is part of the process under a layer of modules, subroutines, parameter assignment and the call that way to illustrate this procedure directly related to the data structure (database, data text volume).
3.9 Storage allocation
According to the needs of the present procedure of storage allocation.
3.10 Notes Design
Note in this program prepare arrangements for the Notes, such as:
a. Increase at the first module of the Notes;
b. Increase in the branching point of the Notes; on the function of each variable, scope, default conditions by the addition of the Notes;
d. On the use of logic by the addition of the Notes and so on.
Description of the program is running in the restricted conditions.
3.12 Test Plan
Description of this procedure monomer testing schemes, including the testing of the technical requirements, input data, expected results, scheduling, personnel functions, equipment conditions and pile driver modules, etc..
3.13 unresolved questions
In the design of this procedure has not yet been resolved and the designers think in the software prior to the completion of the problem to be solved.
4 Procedure 2 (identifier) Design Description
3 similar manner to illustrate the first two procedures as well as the first N A process design considerations .