I am developing a database for the Attendance system in my university, I've created a blue print somehow and sketched out the entities on the paper. But still I'm a little bit confused about the tables, that might be there should be more number of tables should be available in my database. I'm sharing my concept kindly help me out in filtering my design further.
This System is only for the Attendance for the students in the university, so I have made the following tables in my database.
1. Teachers. a)id b)name c)designation d)courses_assigned 2. Students. a)id b)name c)roll_no d)courses_registered e)Rfid_tag_id f)attendance % g)registeration_Status h)username i)password j)attendance marked(Boolean) 3. Admin/Users. (Will it be good to make them seperately?) a)id b)username c)password 4. Courses. a)id b)course_name c)credit_hours d)teachers_teaching e)semester
Is that enough? or some more entity or table should be present in my design?
Can someone help me out regarding to the constraints? or Relationships between the tables?