First, Introduction
1.1 Purpose of writing
database table structure Design is a very important part of the whole project development, a good database design, can improve the development efficiency, convenient system maintenance, and for the future expansion of the function of the project left room. We write this document description, from all aspects of the student Curriculum management Small assistant system database design planning, using it to guide the system in various aspects of the database, for the system development programmer, system analyst to provide benchmark documents. We also want to write data design specifications, specification data name, data range, data code and so on. This document is the basis of the project team's joint operations, with the development of norms, program modules and project members between the interface rules, data methods, we have a common working language, a common work platform, so that the entire software development work can be coordinated and orderly.
1.2 Writing the background
1) name of the system to be developed: Windows-based curriculum management assistant system;
2) The task of this project is proposed by the teacher to guide the students to discuss the results of the joint;
3) Developer: Chaizhanhao, Liu Shuo, Ho Junjun, Pan, Zhang Jiaxi, Zhu Jie
4) Users: University students, teachers, etc.
Second, the external design
2.1 Identifiers and states
For contact purposes, specify the code, name, or identifier used to uniquely identify the database, and additional descriptive information is also given. If the database belongs to an experiment, is still under test, or is temporarily used, it is to explain this feature and its effective time range.
2.2 Programs that use it
Course Management Assistant
2.3 The development environment of this system is
Database: My SQL 5.7,
Compiler: Visual Studio compiler,
Operating systems: Microsoft Windows 10,
Assistive software: Photoshop, etc.
Data items used in this project: In terms of name, scope, type, etc. see Data dictionary.
2.4 Support Software
My SQL 5.7,vs2015 Compiler, Windows 10 operating system, Power Designer12.
Third, structural design
3.1 Conceptual structure Design
Clearly and correctly describe the data forms and linkages reflected in this database:
3.2 Logical Structure Design
3.2.1 Database Design specification
Database naming rules: Db_ database name, the first letter of each English word capitalized;
Table naming rules: Table name _info, the first letter of each English word capitalized;
Field naming rules: The first letter of each English word is capitalized;
Field time format: All time formats are in the form of the 2008-12-20 23:23:02
3.3 Physical Structure Design
3.3.1 Data Sheet design
See Data dictionary.
3.3.2 design of data access
Index the code of the relationship that often occurs in the query, and the code that frequently connects to it;
For highly updated relational models, there are no indexes defined, such as student users, and we don't discuss the design of storage locations because of the immaturity of the technology.
Iv. Functional Data requirements
1. Input of basic information of administrator, including user name and password;
2. Input of teachers ' user information, including user name, password, name, gender, age, courses offered, etc.;
3. Input of basic information of student user, including user name, password, name, gender, age, student number, achievement, participating course, etc.;
4. User basic information inquiries, changes, including name, gender, etc.;
5. The input of the course information, including the course name, category, school hours, class time, basic requirements, etc.
6. Inquiry of course information, including course name, class, class, time, basic requirements, etc.
7. Input of grade information, including student's name, Examinee's number, examination subject, achievement;
8. Information on the results of the inquiry, including the student's name, examination subjects, scores;
9. Admin management, including create student, teacher user information, delete and modify user information he. Add, modify, and delete course information;
V. Use of Design
4.1 Data Dictionary Design
4.1.1. Administrator Form
Table 1 Administrator Form
Column Name |
Data type |
Allow empty |
Default value |
Note |
Manname |
VARCHAR |
N |
|
User name |
manpasswd |
VARCHAR |
N |
|
Password |
Role |
VARCHAR |
N |
|
Role |
4.1.2. Teacher Forms
Table 2 Teacher Forms
Column Name |
Data type |
Allow empty |
Default value |
Note |
Tchname |
VARCHAR |
N |
|
User name |
tchpasswd |
VARCHAR |
N |
|
Password |
Role |
VARCHAR |
N |
|
Role |
Tchsign |
VARCHAR |
N |
|
Number |
Tchclass |
VARCHAR |
N |
|
Course |
Tchsex |
VARCHAR |
N |
|
Gender |
Tchborn |
VARCHAR |
N |
|
Date of birth |
Tchhometown |
VARCHAR |
Y |
|
Hometown |
4.1.3. Student Forms
Table 3 Student Forms
Column Name |
Data type |
Allow empty |
Default value |
Note |
Stuname |
VARCHAR |
N |
|
User name |
stupasswd |
VARCHAR |
N |
|
Password |
Role |
VARCHAR |
N |
|
Role |
Stuxuehao |
VARCHAR |
N |
|
School Number |
Stugrade |
VARCHAR |
Y |
|
Results |
Stumajor |
VARCHAR |
N |
|
Course of participation |
Stusex |
VARCHAR |
N |
|
Gender |
Stuborn |
VARCHAR |
N |
|
Date of birth |
Stuhometown |
VARCHAR |
Y |
|
Hometown |
4.2 Data structure Design
Table 4 Data Structure
Data structure Name |
Property |
Administrator |
User name, password, and role |
Teachers |
Username, password, character, number, course, gender, date of birth, home |
Students |
Username, password, character, school number, score, course, gender, date of birth, hometown |
4.3 Secure and confidential design
The database is the basis of the management system and usually holds important store operating information and customer information. Due to financial management, the integrity and security of the data is particularly important. Once the data in the system is lost, it will take a long time to recover, and sometimes even the information system has to be restarted from the system initialization stage. Daily data backup is an important means to ensure the security of the system. Data backup needs to be done in strict accordance with the pre-established backup and recovery strategy, and to implement backup registration and inspection measures. In addition, the system sets the user's identity to identify whether it is a legitimate user, and requires legitimate users to set their password, to ensure that the user identity is not compromised; The system sets different access levels for different data, restricts access to the data categories and content that can be queried by users, and sets different permissions for different users to distinguish different users. such as the District store chief and the clerk. Specific system configuration should be based on the actual operation of the system to make further adjustments.
"Software Engineering" 02 groups of software engineering team Project--Curriculum Management Assistant Database design document