Please enable JavaScript.
Coggle requires JavaScript to display documents.
Potential data design - Coggle Diagram
Potential data design
Sessions
Session ID - the unique identifier of the session. This attribute/value will be an auto incrementing value within the SQL database, and will be used to generate SQL queries to manipulate individual sessions
Mentor ID - the identification number of the mentor who is tutoring within the session. Note that this attribute may be null, as if a mentor has not yet accepted a session proposed by a user, then this attribute (of the SQL table) will not have a defined value
Start time - the time at which the session starts. This attribute is implemented within the data design to ensure students and mentors know the exact time and date at which the session occurs
-
Subject - the subject being tutored in within the session. This data may be used by administrator and mentors users to investigate what subject is most in demand, and which subjects may require further tutoring, more resources, more mentors, etc.
-
Status - the status of the session. That is, whether or not it has been completed, is underway, is to be completed, or has been cancelled entirely
Present - that is, whether or not the student (proposer) has attended the session they have proposed. This value is determined by the mentor of the session once the session is complete, and is null up until this point in time
Notes - written notes that the mentor has compiled for the session. These notes will be uploaded to the system retrospectively, and can only be manipulated by the mentor. Students may then see these notes once they have been uploaded, so as to keep track of what academic material was covered within the session, what to remember from the session, etc.
-
-
-
Users
Username - the user's designated user name. For admins and mentors, this will be self-determined, whereas students must select a username linked to their existing student number, as only students of the College should be able to register for the Peer Mentor Manager system. This will be verified by ensuring student's proposed username (proposed in the registration process) exists within an existing 'userbase' table provided by the College. Note that for students their username will be their full, unedited student number (e.g. s1120201, as opposed to 120201)
-
-
-
Email - the user's email. Note that the email a user provides within the registration process will be used to implement a 2 factor authentication system (2FA), whereby users will be sent a verification code which they will then enter within the registration page to ensure that they really do have access to the email they have specified. Use of this 2FA system increases the security of the system overall, as malicious users may not be able to register accounts on other individuals behalf (as, presumably, they will not have access to said individual's email account)
Mentors
Mentor ID - the mentor's unique identification number. Note that this number is separate to a user's username
Blue card name - the name associated with a mentor's blue card. Note that - as per the system requirements - mentors must obtain and provide evidence of a blue card in order to begin tutoring within the Peer Mentoring system. This, from a security standpoint, prevents those old boys (or even just random members of the public) from tutoring students without proper qualification to do so
Blue card number - the number associated with a mentor's provided blue card. When registering/verifying their account, mentors will have to provide details of their blue card (name, number, expiry date)
Blue card expiry date - the expiry date of a mentor's provided blue card. This particular attribute exists within the data design to ensure mentors that are not qualified to tutor students of the College (i.e., do not have a blue card) are not allowed to partake in the Peer Mentoring system
Blue card present status - has the user provided their blue card to the Peer Mentor Manager system yet
Students
Student ID - a student's ID. Note that this will not be an auto incrementing value, but rather the student's student number (with 's' and the first digit removed)
Year - the student's year/cohort. Note that this will value will change from year to year, and could likely be manipulated by use of an SQL query
House - a student's house. Note that students will not have to provide this information to the system. Rather, by simply providing their student number, the userbase - which contains data relating to a student's house, PC group, etc. - can be used to import data into the system
Pastoral care group - the student's pastoral care group. This data could be used to determine tutoring participation across various pastoral care groups of the College
Mentor subjects
Mentor ID - The unique identification number of each mentor, used to ensure the Peer Mentor Manager system is able to display mentors with session proposals that are relevant to their field of expertise. For example, if a mentor is only able to provide tutoring for those subjects belonging to the field of STEM, then they should not be provided with session proposals for humanities or arts subjects
Subject - the particular subject that the mentor is able to provide tutoring services for. For instance, if the tutor is able to tutor Year 9 Mathematics, this attribute will have value 'Mathematics'
Year - that is, the year of subject the mentor is able to teach. For example, if a mentor is able to provide tutoring services for Year 9 Mathematics students, this attribute will have value '9'