GB8567--88
Database Design Specification
1 Introduction
High-quality databases play an important role in big data processing programs or systems. Therefore, there are many requirements and regulations for database design. First, the database must have good maintainability and flexibility, and the database algorithm logic must also be optimized, so that resources can be effectively used and data processing time can be shortened.
1.1 Writing Purpose
As there are more and more computers and more computer data are generated, the original storage methods cannot meet the needs of data storage. Therefore, databases are used to store various records. In addition, databases can save a lot of resources, such as manpower, time, and space.
The intended readers of the Database Design Manual are designers and developers.
1.2 Background
Database Name: change_sys
System name: Data room Charging System
System Project Task Author: Professor mi Xinjiang
User: all teachers and students of Langfang Normal University
The computing station (center) for installing the software and the database: Library Reading Room, school data room
1.3 Glossary
The data dictionary uses the following format:
01. database design materials
02. Stored SQL Program
03. User Permissions
04. User Name
05. User statistics
06. Column Default Value
07. Integrity of constraints
08. permissions granted to users and Roles
1.4 references
List related references:
Requirement design specification-Xu lingbo
Summary design specification-Xu lingbo
1.5 selected Database Management System
SQL sever20008
1.6 database security and confidentiality
The login database has a Windows identity and SQL sever identity authentication. Generally, the SQL sever identity authentication is selected, and its login has a password verification, so the security can be ensured.
1.7 database backup and recovery
The Database supports data backup and data recovery.
2. Detailed Database Design
Note: This section describes how database design meets user needs in the real world. It is an entity-level design.
2.1 requirement analysis 2.1.1 system function Diagram
System Functions |
Average user |
Operator |
Administrator |
Query balance |
√ |
√ |
√ |
View Machine Records |
√ |
√ |
√ |
Query recharge records |
√ |
√ |
√ |
Query computer statistics |
√ |
√ |
√ |
Change Password |
√ |
√ |
√ |
Exit |
√ |
√ |
√ |
Register |
|
√ |
√ |
Recharge |
|
√ |
√ |
Card return |
|
√ |
√ |
Checkout |
|
|
√ |
Add basic data |
|
|
√ |
2.1.2 system flowchart
2.2 Database concept design 2.2.1 database E-R Design
2.2.2 description of E-R Design Drawing
Database E-R entity table
Entity name |
Entity description |
Administrator |
With the highest administrative permissions, You can query the work records of all users. The administrator sets basic data and bills the computer bills every week. |
Operator |
Register the operator on the machine to manage the machine records of general users. |
Average user |
Swipe the card to go to and from the machine, query machine records, and view statistics. |
Work records |
Record user's machine records |
Bill |
Records users' On-machine consumption records |
2.3 database Logic Design
|
|
Average user |
Operator |
Administrator |
Basicdata |
Basic data table |
|
|
√ |
Cancelcar |
Card return table |
|
√ |
|
Checkday |
Daily checkout table |
|
|
√ |
Checkweek |
Weekly checkout table |
|
|
√ |
Line-info |
Computer record table |
|
√ |
|
Onwork-info |
Instructor on duty Worksheet |
|
√ |
|
Recharge-info |
Recharge record table |
|
√ |
|
Student-info |
Student Information Registration Form |
√ |
|
|
User-info |
User information table |
√ |
√ |
√ |
Worklog-info |
Work log table |
|
√ |
|
2.4 Physical Structure Design
Basicdata table:
Canclecard table:
Checkweek table:
Line-info table:
Onwork-info table:
Recharge-info table:
Student-info table ::
Checkday table: