Database structure suggestion for a student management system [closed]

Question

I am currently working on a research, uhmm, prolly will create an application out of it, the system is an "intern management system" . My question is how will you structure your database if you are in my shoes?

but before answering, take a look at this, this is what's on my mind

table : users
fields :
   user_id, username, password, firstname, middlename, lastname

table : roles
fields :
   role_id, role_name

table : *user_role*
fields :
   user_id, role_id

foreign keys:

• user_id reference users(user_id)
• role_id reference roles(role_id)

table : status
fields :
   status_id, status_name

table : *user_status*
fields :
   user_id, status_id

foreign keys:

• user_id *reference* users(user_id)
• status *reference* status(status_id)

the above is the current structure of my database, any suggestion on the above? how about if i am going to add the users a field of college and course

if he is on college of engineering, or in college of business ad . . and so on and so forth, the college of engineering has many courses within it, how do i handle that kind of situation, should i just create a table called colleges, courses, then college_courses and lastly a table called user_college_course? what do you think?

Answer 1

colleges, courses, then college_courses and lastly a table called user_college_course?

This looks good, Assuming a course can be offered at more than one college.

Same Question for the user_status table, can a user have more that one status? If yes, you need a filed to specify what the Status is of.. (and maybe another Table Status_Type)