Database Design Manual (GB8567 - 88)
1 Introduction
1.1 Writing
Description Writing the purpose of this database design specification, pointing out the expected readers.
1.2 background
Description:
a. Name of the name of the database to be developed and the name of the software system using this database;
b. List the task of the software system development project, users, and computing stations (centers) that will install the software and this database.
1.3 definition
List the definitions of the special terms used in this document, the original phrase of the first alphanumeric word.
1.4 Reference
List the relevant references:
a. The approved planned task book or contract of this project is approved by the superior authority;
b. Other published files belonging to this item;
C. The documents referenced by each of this document include the software development standards to be used.
List the title, file number, publishing date, and publishing unit of these files, indicating that the source of these files can be obtained.
2 external design
2.1 identifier and status
Contact, detailed descriptions for uniquely identifying the code, name, or identifier of the database, and additional descriptive information is also given. If the database is still in the experiment, it is still used in the test or temporarily used, then this feature and its effective time range.
2.2 Using its program
List all applications that will be used or access this database, give each name and version number for each of these applications.
2.3 agreed
Statement a programmer or a system analyst in order to use this database, it needs to be understood, and the identification is agreed, for example, different versions of the database to identify different versions of the database and used to identify each text volume in the library, record, data items. Naming convention, etc.
2.4 Specialized guidance
To prepare for this database, engage in this database, maintenance personnel provide special guidance, such as the format and criterion of the data that will be sent to the database, sending the database operation procedures and steps for generating, modifying, updating Or use the operation guidance of these data volumes. If these guidances are very long, list the names and sectors of the file information that can be reflected.
2.5 Support Software
Briefly introduce the support software directly related to this database, such as database management systems, storage location programs, and programs for loading, generating, modifying, and updating databases. Note Name, version number, and primary functionality of these software, such as the type of data model used, allowed data capacity, etc. List the title, number, and source of these technical files for these support software.
3 structure design
3.1 Concept Structure Design
Description This database reflects the original data of the entities, attributes, and the relationship between the real world, including each data item, record, system, identifier, definition, type, metrics, and value domain, definition, type, metrics, and value domain. Establish each user view of this database.
3.2 Logical Structure Design
Note The above-mentioned raw data is decomposed, and the database global logical structure is reorganized, including the determined keyword and attribute, re-determine the record structure and the scrip structure, the interrelationship between the established various documents, formation Database Administrator view of this database.
3.3 Physical Structure Design
Establish a system programmer view, including:
a. The arrangement of data in memory, including the design of the indexing area, buffer;
b. Organizations used by the exemplary equipment and the organizational space, including the organization and division of the index area, data blocks;
C. How to access data.
4 use design
4.1 Data Dictionary Design
Various items involved in database design, such as data items, records, systems, text, patterns, submodels, etc., to explain their identifiers, synonymous names and related information. The basic considerations for this data dictionary design are required in this section.
4.2 Safety Confidential Design
Description In the design of the database, how to distinguish between different visits, different access types, and different data objects, the database security confidential design considerations obtained separately.
