Database Design Manual 1 Introduction
1.1 Purpose of writing
The paper points out the database design of the computer room charge system, and makes the specific design rules for all the logos, logical structure and physical structure used in the database.
Expected Reader: programmer, database administrator. 1.2 background
Description
A Name of the database: Charge_sys
b Name of software system: charge system of computer room
C Task Author: Professor Mi Nue-jiang
D Developer: Information Technology accelerated-10 period cattle relocation
E User: Machine room on duty personnel
F. Install the software and this database of the Computing Station (center): Langfang Normal University room computer 1.3 definition
Grid++report 5.0: Report Designer.
1.4 references
Resources:
A Zhang Haifan "Software Engineering" Beijing Tsinghua University Press
b Li Zhao "database Principle and Application" science Press
C Software Engineering video teaching materials of Harbin Institute of Technology
d. "Jiang Jianling Database Video" Zhejiang University teaching document 2 external design
2.1 Identifiers and states
Name |
Description information |
State |
Basicdata_info |
Basic data information |
Temporarily used |
Cancelcard_info |
Return card information |
In the experiment |
Checkday_info |
Daily Checkout Information |
In the experiment |
Checkweek_info |
Weekly Checkout Information |
In the experiment |
Online_info |
On-Machine information |
In the experiment |
Recharge_info |
Recharge Information |
In the experiment |
Student_info |
Student Information |
Temporarily used |
User_info |
User Information |
Temporarily used |
Worklog_info |
Duty record information |
In the experiment |
2.2 Programs that use itLists all the applications that will use or access this database, given its name and version number for each of these applications.
Name |
Version number |
Computer room charge System |
V1.1.0 |
Excel |
Version 2010 |
Report Designer |
Grid++report 5.0 |
2.3 conventions
State the conventions that a programmer or a system analyst needs to know in order to be able to use this database, such as conventions for identifying different versions of a database and for identifying individual volumes within the library, records, naming conventions for data items, and so on. 2.4 Special Instructions
provide specific guidance to the generation, testing, and maintenance personnel who are preparing to engage in this database, such as the format and standard of data to be fed into the database, the procedures and procedures for sending it into the database, and instructions for generating, modifying, updating or using these data volumes. If the content of these guidelines is lengthy, a list of the names and chapters of the documents to be read is provided. 2.5 support software
Software name |
Version number |
Main function characteristics |
Visual Basic |
6.0 Enterprise Edition |
Visual Advanced Development language |
SQL Server |
2008 |
Establishment and management of database |
3 Structural design
3.1 Conceptual structure design
e-r diagram: declaration: This figure omits the entity attribute
3.2 Logical Structure design
A. Basic data settings (preparation time, at least machine time, fixed user, temporary user, incremental time, minimum amount)
B. Student on-machine record (card number on the machine time off the machine time on the machine date of the machine date balance notes)
C. Teachers on duty (teacher number logon date login time machine name)
D. Student information (registration date for Class Ka, gender)
E. User information (teacher number user name User level registration date Registration Time logoff date logoff time password)
F. Recharge record (card number teacher number Recharge date Recharge time recharge amount Checkout status)
G. Return card record (card number teacher number refund date refund time refund amount checkout status)
H. Daily Checkout list (previous period amount of current consumption this period return card current period of the summary checkout time) 3.3 Physical Structure design
Build a view of the system programmer, including:
A The arrangement of data in memory, including the design of index area and buffer;
b The external memory equipment used and the organization of external memory space, including index area, data block organization and division;
c. Ways to access data. 4 application design
4.1 Data dictionary design
In the database design involves the various items, such as the data item, the record, the system, the text volume, the pattern, the sub-pattern and so on generally must establish the data dictionary, explains their identifier, the synonym name and the related information. The basic considerations for this data dictionary design are described in this section.
Data flow and File description:
login information
Number |
Name |
Alias |
Make up |
Live frequency |
Cardno |
Card number |
|
By student name, Gender, grade, recharge, school number, etc. |
Indefinite |
|
Up and down logging information |
By student name class user name on the machine time date of the machine time date |
100-200 times/day |
, |
Day Checkout form |
Checkday |
By operator, yesterday balance, spending balance, etc. |
1 times per day |
All |
Weekly closing order |
Checkweek |
By operator, last month balance, this month's expenses, this month's balance, etc. |
1 times/month |
+ |
Personnel change information |
|
Consists of the user name, level, login number, and password |
Indeterminate |
Data Item Description:
(1) A description of the data items contained in the upper and lower machine information.
Data item Name |
Storage structure |
Alias |
Range of values |
Date on machine |
Char (10) |
Ondate |
Greater than December 1, 2013 |
Between the machines |
Char (10) |
OnTime |
Greater than December 1, 2013 |
Computer name |
Char (10) |
Computer |
———— |
Off-Machine Date |
Char (10) |
Update |
Greater than December 1, 2013 |
Off-Machine time |
Char (10) |
Uptime |
Greater than December 1, 2013 |
(2) A description of the data items included in the Daily checkout/weekly closing order.
Data item Name |
Storage structure |
Alias |
Range of values |
All amounts |
Numeric (18,0) |
Allcash |
Keep one after the decimal point |
User name |
Char (10) |
Userid |
Within the cross symbol |
Last month balance |
Numeric (18,0) |
Lastmonthcash |
Keep one after the decimal point |
This month's balance |
Numeric (18,0) |
Monthcash |
Keep one after the decimal point |
Balance yesterday |
Numeric (18,0) |
Lastdaycash |
Keep one after the decimal point |
Today's balance |
Numeric (18,0) |
Daycash |
Keep one after the decimal point |
(3) A description of the data items included in the personnel changes.
Data item Name |
Storage structure |
Alias |
Range of values |
Account |
Char (11) |
Userid |
No more than 11 bits |
Password |
Char (10) |
Pwd |
No more than 11 bits |
Level |
Char (10) |
Level |
|
User name |
Char (10) |
UserName |
|
4.2 Secure and confidential design
In the design of the database, how to design the database security by distinguishing different visitors, different types of access and different data objects.
Data |
General users |
Operator |
Administrator |
Student Information Management |
√ |
√ |
√ |
User Information Management |
|
|
√ |
Management of revenue and expenditure accounts |
|
√ |
√ |
System Information Management |
|
|
√ |