gb8567--88
Database Design Manual
1 Introduction
High-quality database in the process of processing big data in the program or system is very important, so there are many requirements and provisions for database design. First of all, the database should have a good maintainability, flexibility, and the database of the algorithm logic must also have a certain degree of optimization, so that resources can be effectively utilized, and the processing time of the data will be shortened.
1.1 Purpose of writing
Due to more and more people on the machine, resulting in more and more data on the computer, the original way of preservation can not meet the needs of data storage, so use a database to store various records. And the database can save a lot of resources, such as manpower, time, space and so on.
The intended audience for the database design specification is the designer, the developer.
1.2 Background
Name of the database: Change_sys
System name: Computer room charge system
Task author of the system project: Professor Mi Nue-jiang
User: All teachers and students of Langfang Normal University
Install the software and the computing station of this database (center): library reading room, school room
1.3 Terminology Definitions
The data dictionary takes the following format:
01. Database Design Information
02. Stored SQL Programs
03. User Rights
04. User's name
05. User Statistics
06. Default values for columns
07. The integrity of the constraint information
08. Permissions granted to users and roles
1.4 References
List the relevant references:
Demand Design Manual--ankylitis bo
Outline Design Manual--ankylitis bo
1.5 Selected database management system
SQL sever20008
1.6 Security and confidentiality of databases
Login database has Windows identity and SQL Sever authentication, generally choose SQL Sever authentication, its login has password authentication, so security can be guaranteed.
1.7 Backup and recovery of databases
The database has the functions of data backup and data recovery.
2 detailed design of the database
Note: This section from the real world to consider how the database design to meet the needs of users, is the entity-level design.
2.1 Requirements Analysis 2.1.1 system function diagram
System functions |
General users |
Operator |
Administrator |
Check balance |
√ |
√ |
√ |
View on-Machine record |
√ |
√ |
√ |
Check Recharge Records |
√ |
√ |
√ |
Query on-Machine statistics |
√ |
√ |
√ |
Change Password |
√ |
√ |
√ |
Exit |
√ |
√ |
√ |
Registered |
|
√ |
√ |
Recharge |
|
√ |
√ |
Return card |
|
√ |
√ |
Checkout |
|
|
√ |
Add basic data |
|
|
√ |
2.1.2 System Flowchart
2.2 Database Conceptual Design 2.2.1 Database e-r design diagram
2.2.2 E-r Design Diagram description
Database e-r Entity Table
entity name |
Entity Description |
Admin |
has the highest administrative rights, can query all user's work record, the administrator sets up the basic data, and every week to check the bill on the machine. |
operator |
The operator of the machine will be registered to manage the general user's computer record. |
General user |
Swipe up and down, query on machine record, view statistics. |
Work history |
Record the user's machine record |
Billing |
Record user's on-machine consumption record |
2.3 Database Logic Design
|
|
General users |
Operator |
Administrator |
Basicdata |
Basic Data Sheet |
|
|
√ |
Cancelcar |
Return Card Form |
|
√ |
|
Checkday |
Daily Checkout Form |
|
|
√ |
Checkweek |
Weekly Checkout Form |
|
|
√ |
Line-info |
On-Machine record table |
|
√ |
|
Onwork-info |
On duty Teacher's work table |
|
√ |
|
Recharge-info |
Recharge Record Form |
|
√ |
|
Student-info |
Student Information Registration Form |
√ |
|
|
User-info |
User Information table |
√ |
√ |
√ |
Worklog-info |
Weekday 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: