Databases
StackOverflow2013
Postsdbo
PODatabase normalization for School Management System
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODatabase normalization for School Management System
    primarykey
    data
    text
    <p>I am creating system for a school management system and come up with the attached database schema.</p> <p><a href="http://oi40.tinypic.com/15x21ig.jpg">Database diagram http://oi40.tinypic.com/15x21ig.jpg</a></p> <p>Following is how the system works:</p> <ol> <li>A school has many students and teachers. It has also many courses(subjects) taught. A grade level can have many courses assigned. These courses in turn will be assigned to the students in that particular grade.</li> <li>The levels of students are categorized into grades and sections. A student can be in Grade 5, but if grade 5 students are huge in number, they are divided into sections. eg: Grade 5 section A, Grade 5 section B.</li> <li>Students are placed in unique classrooms. A classroom will be unique throughout. Classroom of Grade 5 Section A of year 2010 will be different from Classroom of Grade 5 Section A of year 2011.</li> <li>Students are assigned parents. A parent can have more than one student in the school.</li> <li>One or more classrooms can be assigned to a teacher.</li> <li>Attendance for students are taken by their teacher on a daily basis</li> <li>There will be many types of exams. Exam results are stored for each subject (course).</li> </ol> <p>I am a beginner in database normalization and would be glad if anyone could give me some hints if the database looks alright or not.</p> <p>EDIT:</p> <p>Also, there will only be one point of login. In the above case, during login, a user will have to select the type of user from a dropdown list. That dropdown selection will be used to query to respective table to login to the system. Another alternative is to use a common <code>user</code> table, which will store the <code>user_id, email, password, last_login_date, last_login_ip</code> but will store other details in respective tables such as <code>student, parent, teacher</code>. So, what is the preferred/correct way to implement it?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAPC
    1. USWebNovice
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODatabase normalization for School Management System
      1. USaskvictor
      1. VTFavorite
    2. VO
      singulars
      1. PODatabase normalization for School Management System
      1. USblack_belt
      1. VTFavorite
    3. VO
      singulars
      1. PODatabase normalization for School Management System
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHey, students in your school can have only one parent? Rather strange :) Plus, why classroom is assigned only one teacher? Should not it be assigned to the course?
      singulars
      1. PODatabase normalization for School Management System
      1. USTadeck
    2. CO@Tadeck The parent table stores details of an authorized parent, who will be able to view and check the student records. It does not indicate all the parent details of the student. Eg: A father could be issued the parent username/password to check his student. The mother could also use it, but generally only one would be able to do it. As for the classroom, a classroom will only ONE assigned class teacher who fills in the attendance/grades of the students in that particular class.Course refers to Subjects a student studies. Grades will be assigned subjects & classrooms will be assigned grades.
      singulars
      1. PODatabase normalization for School Management System
      1. USWebNovice
    3. CO@Damchey be prepared that things like the 1-authorized-parent rule might change, and your app will be required to deal with it somehow. It might be a good idea to design this so that a student can have any number of authorized guardians - you can then limit the number to 1 on UI level
      singulars
      1. PODatabase normalization for School Management System
      1. USPekka 웃
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload