Innovation Course Management System Database Design

Innovation Course Management System Database Design

The first step: needs analysis

        Database design must first accurately understand and analyze user requirements (including data processing). Needs analysis is the basis for the entire design process, but also the most difficult and time-consuming step. Needs analysis and accurate if done well, determines the speed and quality of construction of the building in its database. Needs analysis done well, it will cause the entire database design done over again.

       This project is to develop innovative curriculum with teachers in the specialized production of an innovative course management systems. After the requirements analysis for this project, we attach a use case diagram:

 

 

 

Step two: design concept

        The concept design is the key to the entire database design, it is through a comprehensive user needs, summarized and abstract, forming a conceptual model independent of the specific DBMS.

        A bottom-up design method, firstly define the concept of the structure of each topical application, and then integrate them together, to obtain the global conceptual structure. The physical requirements involved in one out analysis, it needs to store data, the constraint data storage structure and reasonable. In the course management system innovation project, an entity involved: students, teachers, teaching assistants and so on. Then the link between the various entities finishing well, to get a global contact structure.

 

 

 

The third step: logical structure design

        Logical structure design concept is to convert the structure into a data model supported by the DBMS, and will be optimized. In the joint efforts of team members, the conceptual design of the contact entities linked table structure, reason clearly attributes of each table, the connection between tables, each table is determined to meet the integrity constraints.

Step Four: Physical Design

        Physical design is a logical data structure model to select the most suitable physical structure of the application environment (including storage structures and access methods).

        First, a detailed analysis of the transaction operation, selection parameters to obtain the desired physical database design (ha, in a step of the first to do it), secondly, to fully understand the RDBMS with internal features, particularly the system provides access The method and storage structures.

 

 

Step five: database implementation

        Using a database administration tool Navicat connection library will be built with MySQL language table statement knock into it. Finalized the following table:

TA Table: Assistants (Assistants)

Curriculum: Class (Class)

Twinning project list: Double (Double)

Job Table: Homework (Homework)

Message table: Message (Message)

Weekly schedule: Plan (Plan)

Team Project Table: Project (Project)

School table: School (School)

Student Table: Student (Student)

Recommended system courseware table: Sys_file (Sys_file)

Teachers upload courseware table: Teacher_file (Teacher_file)

Users Table: User (User)

Di Liu step: summary

The database design, students actively discussed within the group, positive comments, to improve the database. In database design, we have to consider a comprehensive, first design concept model, then generate the physical model.

In the design process should pay attention to:

If there are many relationship between two entities, it should be to eliminate this relationship. Elimination approach is to add a third between the two entities. In this way, the original one-many relationship, now becomes two-to-many relationship. To attribute the original two entities to reasonably allocate to the three entities. Here a third entity, essentially a more complex relationship, which corresponds to a base table. In general, the database design tool does not recognize many to many relationships, but can handle many to many relationship.

Guess you like

Origin www.cnblogs.com/xjf66/p/11819334.html