Database Scope and Requirements. Requirements and Assumptions

Transcription

1 Table of Contents Table of Contents... 2 Database Scope and Requirements... 3 Requirements and Assumptions... 3 Entity-Relationship Model... 5 Relational Model... 7 Relational Model Normalized... 8 Database Schema in MySQL Database Records SQL Queries Views Procedures, Triggers and Transaction Graphical User Interface References Appendix A

2 Database Scope and Requirements Database purpose: The database will provide functionality for course/instructor evaluation by the student. The collected statistical data will provide important feedback from students about the courses that are taught by the instructors. Database domain: The main users of the database are Students, who will answer the survey questions, and the Administrator/Instructor, who will create, modify and add the survey questions. Key entities: Submission, Question, Instructor, Course, Student, College, Department Assumptions: The Administrator/Instructor should be able to access and create reports based on previous survey submissions. Requirements and Assumptions Functional requirements: 1. The systems shall not allow multiple submissions by the same student for the same course. 2. In order to take the survey the student shall have to be enrolled in the class. 3. Each survey submission shall have a timestamp. 4. The system shall require that the Instructor provide a unique student ID, a full name, his/her classification and department for each student enrolled in a course. This information shall only be kept track of for the system to prevent the student from taking the same survey again, but the student s identity shall not be displayed or be available to the Instructor to ensure privacy and anonymity of the survey. 5. The system shall include the following student s classifications: graduate, senior, junior, sophomore, freshmen. 6. The system shall include departments, such as Mechanical Engineering, Computer Science, Education, Economics, and Management. The system shall keep track of which college any given department belongs to. 7. The following colleges shall be included but can be expanded: business, education, engineering, health sciences, liberal arts, nursing, and science. 8. The course shall have a unique CRN; course s name, number, term, year, section, and department the course belongs to shall be recorded. 9. The instructor shall have a unique employee ID; instructor s address, username, password, title, first, last and middle name shall be recorded. 10. Each question shall have a question text where the question and available answers are saved. 11. Each question shall have a category corresponding to the area being evaluated (Course, Instructor, TA, Facilities/Labs, Student). 3

3 12. Each question shall have a number, by which different questions that belong to the same submission shall be identified. 13. The following types of questions shall be included: scale, opinion, multiple choice, and expected grade. 14. The survey questions evaluating performances shall have a Scale (from Very Poor, Poor, Satisfactory, Good, to Excellent) consistent throughout the entire survey, where only one answer can be chosen. 15. The survey questions asking for student s Opinion shall have a text area, where the student s answer can be typed in and submitted. 16. The survey questions of type Multiple Choice shall allow a student to choose one answer from a list of options. 17. The survey questions of type Expected Grade shall allow a student to choose a letter which stands for the grade that he/she expects to receive for the class. 18. The data in the database shall allow the Instructor to: a. acquire reports that shall show the percentage of answers to each question; b. acquire reports that shall show the evaluation of a specific instructor, department, college, or average by the students. Nonfunctional requirements: 1. Student s information should be anonymous. Assumptions: 1. The Instructor shall create a survey by choosing among existing questions, or creating new questions. 2. We assume that the system is used properly, for example, each course shall be linked to its corresponding instructor. 4

4 Entity-Relationship Model 5

5 Additional Comments: 1. To identify which question belongs to which submission, we will use CRN and student ID in the primary key set for both the question and the submission. There cannot exist more than 1 copy of a CRN and a student ID combination for each submission. However, because there can be several questions in the same submission, a question number is also used in the primary key set of Question entity to distinguish between different questions of the same submission. 2. The student ID is used as an attribute in the Submission entity in order to prevent the same students from making more than 1 submission for the same course/instructor. However, even though the student ID, just like the password for the Instructor, is sensitive information that is used in the database queries, it can be made encrypted. Additionally, a View will also be created to extract all the information that the instructor needs for the reports, but without the student ID, thus making the student ID anonymous for the instructor. 3. The Scale, Opinion, Multiple Choice and Expected Grade are in an isa relationship with the weak entity Question, therefore, they inherit the primary keys of Question and do not require their own. See figure 4.32, p. 170 [5]. 6

6 Relational Model Object-oriented approach is used to translate the isa relationships into relational model. We used merging relations technique for most relations where cardinality was equal 1. This way, there will be no need to create separate tables for relations; information about them is already included. Student(studentID, firstname, lastname, middleinitial, classification) EnrolledIn(studentID, CRN) College(collegeName,deanName) Department(departmentName, chairname, collegename) Submission(studentID, CRN, date) Course(CRN, term, year, section, coursename, coursenumber, departmentname) Instructor(employeeID, username, password, title, firstname, lastname, middleinitial, ) Teaches (employeeid, CRN) Question(studentID, CRN, questionnumber, category, questiontext) Scale(studentID, CRN, questionnumber, value, category, questiontext) Opinion(studentID, CRN, questionnumber, text, category, questiontext) MultipleChoice(studentID, CRN, questionnumber, options, category, questiontext) ExpectedGrade(studentID, CRN, questionnumber, letter, category, questiontext) 7

7 Relational Model Normalized The following functional dependencies are found in the relational model: Student(studentID, firstname, lastname, middleinitial, classification) FD1 studentid-> firstname, lastname, middleinitial, classification EnrolledIn(studentID, CRN) College(collegeName,deanName) FD2 collegename ->deanname Department(departmentName, chairname, collegename) FD3 departmentname -> chairname, collegename Submission(studentID, CRN, date) FD4 studentid.crn-> date Course(CRN, term, year, section, coursename, coursenumber, departmentname) FD5 CRN-> term, year, section, coursename, coursenumber, departmentname Instructor(employeeID, username, password, title, firstname, lastname, middleinitial, ) FD6 employeeid-> username, password, title, firstname, lastname, middleinitial, Teaches (employeeid, CRN) Question(studentID, CRN, questionnumber, category, questiontext) FD7 studentid.crn. questionnumber -> category, questiontext Scale(studentID, CRN, questionnumber, value, category, questiontext) FD8 studentid.crn. questionnumber -> value, category, questiontext Opinion(studentID, CRN, questionnumber, text, category, questiontext) FD9 studentid.crn. questionnumber -> text, category, questiontext MultipleChoice(studentID, CRN, questionnumber, options, category, questiontext) FD10 studentid.crn. questionnumber -> options, category, questiontext ExpectedGrade(studentID, CRN, questionnumber, letter, category, questiontext) 8

8 Comments: FD11 studentid.crn. questionnumber -> letter, category, questiontext Even though such attributes as deanname and chairname can be divided into first name and last name attributes, it is unnecessary as they will only be used as atomic values for reports (see requirement #18). Our conclusion is that our relational model is in the 3NF, as all attributes contain atomic values, all nonprime attributes are functionally dependent on the full set of attributes composing their corresponding primary key, and every non-prime attribute is directly dependent on the primary key. 9

9 Database Schema in MySQL The following database schema is used to create a JoAnJo-db database in MySQL: CREATE TABLE IF NOT EXISTS cs_aidominguez.student ( studentid INT(8) NOT NULL, firstname VARCHAR(20), lastname VARCHAR(35), middleinitial VARCHAR(1), classification VARCHAR(10), departmentname VARCHAR(40), PRIMARY KEY (studentid)); CREATE TABLE IF NOT EXISTS cs_aidominguez.enrolledin ( studentid INT(8) NOT NULL, CRN INT(5) NOT NULL, PRIMARY KEY (studentid,crn), CONSTRAINT foreign_key_to_studentid_from_student_enrolledin FOREIGN KEY (studentid) REFERENCES cs_aidominguez.student (studentid) CONSTRAINT foreign_key_to_crn_from_course_enrolledin FOREIGN KEY (CRN) REFERENCES cs_aidominguez.course (CRN) ON DELETE NO ACTION ON UPDATE NO ACTION); CREATE TABLE IF NOT EXISTS cs_aidominguez.college ( 10

10 collegename VARCHAR(50) NOT NULL, deanname VARCHAR(50), PRIMARY KEY (collegename)); CREATE TABLE IF NOT EXISTS cs_aidominguez.department ( departmentname VARCHAR(40) NOT NULL, chairname VARCHAR(50), collegename VARCHAR(50), PRIMARY KEY (departmentname), CONSTRAINT foreign_key_to_collegename_from_college_department FOREIGN KEY (collegename) REFERENCES cs_aidominguez.college (collegename) ON DELETE NO ACTION ON UPDATE NO ACTION); CREATE TABLE IF NOT EXISTS cs_aidominguez.submission ( studentid INT(8) NOT NULL, CRN INT(5) NOT NULL, date DATE, employeeid INT(10), PRIMARY KEY (studentid,crn), CONSTRAINT foreign_key_to_studentid_from_student_submission FOREIGN KEY (studentid) REFERENCES cs_aidominguez.student (studentid) CONSTRAINT foreign_key_to_crn_from_course_submission 11

11 FOREIGN KEY (CRN) REFERENCES cs_aidominguez.course (CRN) ON DELETE NO ACTION ON UPDATE NO ACTION); CREATE TABLE IF NOT EXISTS cs_aidominguez.course ( CRN INT(5) NOT NULL, term VARCHAR(10), year YEAR, section VARCHAR(5), coursename VARCHAR (100), coursenumber VARCHAR (7), departmentname VARCHAR(40), PRIMARY KEY (CRN), CONSTRAINT foreign_key_to_departmentname_from_department_course FOREIGN KEY (departmentname) REFERENCES cs_aidominguez.department (departmentname) ON DELETE NO ACTION ON UPDATE NO ACTION); CREATE TABLE IF NOT EXISTS cs_aidominguez.instructor ( employeeid VARCHAR(10) NOT NULL, username VARCHAR(30), password VARCHAR(30), title VARCHAR(20), firstname VARCHAR(20), lastname VARCHAR(35), 12

12 middleinitial VARCHAR(1), VARCHAR(40), PRIMARY KEY (employeeid), UNIQUE (username)); CREATE TABLE IF NOT EXISTS cs_aidominguez.teaches ( employeeid VARCHAR(10) NOT NULL, CRN INT(5) NOT NULL, PRIMARY KEY (employeeid,crn), CONSTRAINT foreign_key_to_crn_from_course_teaches FOREIGN KEY (CRN) REFERENCES cs_adominguez.course (CRN) CONSTRAINT foreign_key_to_employeeid_from_instructor_teaches FOREIGN KEY (employeeid) REFERENCES cs_aidominguez.instructor (employeeid) ON DELETE NO ACTION ON UPDATE NO ACTION); CREATE TABLE IF NOT EXISTS cs_aidominguez. Question ( studentid INT(8) NOT NULL, CRN INT(5) NOT NULL, questionnumber INT(10) NOT NULL, category VARCHAR(15), questiontext VARCHAR(1000), PRIMARY KEY (studentid,crn, questionnumber), 13

13 CONSTRAINT foreign_key_to_studentid_from_submission_question FOREIGN KEY (studentid) REFERENCES cs_aidominguez.submission (studentid) CONSTRAINT foreign_key_to_crn_from_submission_question FOREIGN KEY (CRN) REFERENCES cs_aidominguez.submission (CRN) ON DELETE NO ACTION ON UPDATE NO ACTION); CREATE TABLE IF NOT EXISTS cs_aidominguez.scale ( studentid INT(8), CRN INT(5), questionnumber INT(10) NOT NULL, value VARCHAR(12), category VARCHAR(15), questiontext VARCHAR(1000), PRIMARY KEY (studentid,crn, questionnumber), CONSTRAINT foreign_key_to_studentid_from_question_scale FOREIGN KEY (studentid) REFERENCES cs_aidominguez.question (studentid) CONSTRAINT foreign_key_to_crn_from_question_scale FOREIGN KEY (CRN) REFERENCES cs_aidominguez.question (CRN) 14

14 CONSTRAINT foreign_key_to_category_from_question_scale FOREIGN KEY (category) REFERENCES cs_aidominguez.question (category) CONSTRAINT foreign_key_to_questiontext_from_question_scale FOREIGN KEY (questiontext) REFERENCES cs_aidominguez.question (questiontext) CONSTRAINT foreign_key_to_questionnumber_from_question_scale FOREIGN KEY (questionnumber) REFERENCES cs_aidominguez.question (questionnumber) ON DELETE NO ACTION ON UPDATE NO ACTION); CREATE TABLE IF NOT EXISTS cs_aidominguez.opinion ( studentid INT(8) NOT NULL, CRN INT(5) NOT NULL, questionnumber INT(10) NOT NULL, text VARCHAR(1000), category VARCHAR(15), questiontext VARCHAR(1000), PRIMARY KEY (studentid,crn, questionnumber), CONSTRAINT foreign_key_to_studentid_from_question_opinion FOREIGN KEY (studentid) REFERENCES cs_aidominguez.question (studentid) 15

15 CONSTRAINT foreign_key_to_crn_from_question_opinion FOREIGN KEY (CRN) REFERENCES cs_aidominguez.question (CRN) CONSTRAINT foreign_key_to_category_from_question_opinion FOREIGN KEY (category) REFERENCES cs_aidominguez.question (category) CONSTRAINT foreign_key_to_questiontext_from_question_opinion FOREIGN KEY (questiontext) REFERENCES cs_aidominguez.question (questiontext) CONSTRAINT foreign_key_to_questionnumber_from_question_opinion FOREIGN KEY (questionnumber) REFERENCES cs_aidominguez.question (questionnumber) ON DELETE NO ACTION ON UPDATE NO ACTION); CREATE TABLE IF NOT EXISTS cs_aidominguez.multiplechoice ( studentid INT(8) NOT NULL, CRN INT(5) NOT NULL, questionnumber INT(10) NOT NULL, options VARCHAR(1000), category VARCHAR(15), questiontext VARCHAR(1000), PRIMARY KEY (studentid,crn, questionnumber), 16

16 CONSTRAINT foreign_key_studentid_from_question_multiplechoice FOREIGN KEY (studentid) REFERENCES cs_aidominguez.question (studentid) CONSTRAINT foreign_key_to_crn_from_question_multiplechoice FOREIGN KEY (CRN) REFERENCES cs_aidominguez.question (CRN) CONSTRAINT foreign_key_to_category_from_question_multiplechoice FOREIGN KEY (category) REFERENCES cs_aidominguez.question (category) CONSTRAINT foreign_key_to_questiontext_from_question_multiplechoice FOREIGN KEY (questiontext) REFERENCES cs_aidominguez.question (questiontext) CONSTRAINT foreign_key_to_questionnumber_from_question_multiplechoice FOREIGN KEY (questionnumber) REFERENCES cs_aidominguez.question (questionnumber) ON DELETE NO ACTION ON UPDATE NO ACTION); CREATE TABLE IF NOT EXISTS cs_aidominguez.expectedgrade ( studentid INT(8) NOT NULL, CRN INT(5) NOT NULL, questionnumber INT(10) NOT NULL, 17

17 letter VARCHAR(1), category VARCHAR(15), questiontext VARCHAR(1000), PRIMARY KEY (studentid,crn, questionnumber), CONSTRAINT foreign_key_to_studentid_from_question_expectedgrade FOREIGN KEY (studentid) REFERENCES cs_aidominguez.question (studentid) CONSTRAINT foreign_key_to_crn_from_question_expectedgrade FOREIGN KEY (CRN) REFERENCES cs_aidominguez.question (CRN) CONSTRAINT foreign_key_to_category_from_question_expectedgrade FOREIGN KEY (category) REFERENCES cs_aidominguez.question (category) CONSTRAINT foreign_key_to_questiontext_from_question_expectedgrade FOREIGN KEY (questiontext) REFERENCES cs_aidominguez.question (questiontext) CONSTRAINT foreign_key_to_questionnumber_from_question_expectedgrade FOREIGN KEY (questionnumber) REFERENCES cs_aidominguez.question (questionnumber) ON DELETE NO ACTION ON UPDATE NO ACTION); 18

18 BelongsTo Database Records CRN Department Name Computer Science Computer Science Education College College Name Engineering Education Business Dean Name Richard Schoerphoerster Josefina Tinajero Robert Nachtmann Course CRN term year section Course Name Spring Intro to Computer Science Spring Data Structures Spring Intro to Education Department Name Computer Science Course Number CS 1401 Computer CS 2401 Science Education ED 1301 Department Departmentt Name Chair Name College Name Computer Science Nigel Ward Engineering Mechanical Engineering Ahsan Choudhuri Engineering Management John Hadjimarcour Business EnrolledIn Student ID CRN

19 ExpectedGrade Student ID CRN Question Letter Category Question Text Number I Student The final grade I expect in this course is: B Student The final grade I expect in this course is: A Student The final grade I expect in this course is: Instructor Employee Username Password Title First Last Middle ID Name Name Initial Mr. John Cheney M jbgood17@hotmail.com longpre skate01 Mr. Luc Longpre longpre@utep.edu Mrs. Cynthia Wheeler P cwheeler@utep.edu MultipleChoice Student ID CRN Question Option Category Question Text Number B Student Classification: A)Graduate B)Senior C)Junior D)Sophomore E)Freshman C C Student Classification: A)Graduate B)Senior C)Junior D)Sophomore E)Freshman A Student Classification: A)Graduate B)Senior C)Junior D)Sophomore E)Freshman 20

20 Opinion Student ID CRN Question Text Category Question Text Number Not available during most office hours TA What is your opinion of the TA: Very organized! TA What is your opinion of the Very knowledgable TA TA: What is your opinion of the TA: Question Student ID CRN Question Category Question Text Question Type Number Instructor Rate the Scale effectiveness for the instructor in stimulating your interests in the subject: Student The final grade I expect in this Expected Grade course is: Lab Rate the state of lab materials: Scale Scale Student ID CRN Question Evaluation Category Question Text Number Satisfactory Instructor Rate the effectiveness for the instructor in stimulating your interests in the subject: Good Labe Rate the state of lab materials: 21

21 Good Instructor Rate the effectiveness for the instructor in stimulating your interests in the subject: Student Student ID First Name Last Name Middle Name Classification Department Name Andrea Dominguez Sophomore Computer Science Alla Dove Junior Computer Science George Anderson P Junior Mechanical Engineering Submission Student ID CRN Date Teaches Employee ID CRN SQL Queries $sql = "SELECT * FROM Submission WHERE studentid = '$_POST[studentID]' AND CRN = '$_POST[CRN]'"; if(mysql_num_rows(mysql_query($sql, $connection)) == 0){ $_SESSION['CRN'] = $_POST['CRN']; $_SESSION['studentID'] = $_POST['studentID']; header("location: SubmitEvaluation.php"); 22

22 }else{ echo "Already made submission"; } This query can be traced to functional requirement 1; $sql2 = "SELECT * FROM EnrolledIn WHERE studentid = '$_POST[studentID]' AND CRN = '$_POST[CRN]'"; if(mysql_num_rows(mysql_query($sql2, $connection)) == 0){ ) echo "Student not enrolled in course"; This query can be traced to functional requirement 2 $sql = "INSERT INTO Submission VALUES('$_SESSION[studentID]', '$_SESSION[CRN]', '$todaysdate')"; This query can be traced to functional requirement 3 $sql = "INSERT INTO Student VALUES('$_POST[studentID]', '$_POST[firstName]', '$_POST[lastName]', '$_POST[middleInitial]','$_POST[classification]', '$_POST[departmentName]')"; This query can be traced to functional requirements 4 and 5 $sql2 = "INSERT INTO Course VALUES ('$_POST[CRN]', '$_POST[term]', '$_POST[year]', '$_POST[section]', '$_POST[courseName]', '$_POST[departmentName]', '$_POST[courseNumber]')"; This query can be traced to functional requirement 8 $sql = "INSERT INTO Instructor VALUES('$_POST[employeeID]', '$_POST[username]', '$_POST[password]', '$_POST[title]', '$_POST[firstName]', $_POST[lastName]', '$_POST[middleInitial]', '$_POST[ ]')"; This query can be traced to functional requirement 9 $sql = "INSERT INTO Question VALUES('0', '$_SESSION[CRN]', $questioncode, '$_POST[category]', '$_POST[text]', '$_POST[type]')"; This query can be traced to functional requirement 10, 11, 12, 13 23

23 $sql = "INSERT INTO Scale VALUES('$_SESSION[studentID]', '$_SESSION[CRN]', '$row[questionnumber]', '$_POST[$questionNumber]', '$row[category]', '$row[questiontext]')"; This query can be traced to functional requirement 14 $sql = "INSERT INTO Opinion VALUES('$_SESSION[studentID]', '$_SESSION[CRN]', '$row[questionnumber]', '$_POST[$questionNumber]', '$row[category]', '$row[questiontext]')"; This query can be traced to functional requirement 15 $sql = "INSERT INTO MultipleChoice VALUES('$_SESSION[studentID]', '$_SESSION[CRN]', '$row[questionnumber]', '$_POST[$questionNumber]', '$row[category]', '$row[questiontext]')"; This query can be traced to functional requirement 16 $sql = "INSERT INTO ExpectedGrade VALUES('$_SESSION[studentID]', '$_SESSION[CRN]', '$row[questionnumber]', '$_POST[$questionNumber]', '$row[category]', '$row[questiontext]')"; This query can be traced to functional requirement 17 Views 1. The following view gives an Instructor all results for the course (CRN) he/she teaches. It allows the instructor to see all answers to all questions for the given CRN, without viewing the IDs of the students who submitted the evaluations. The view can be traced to the functional requirements #5 and #18, as well as #9, #11 and #12. CREATE VIEW AnswersPerCRN AS SELECT value, category, questiontext FROM Scale WHERE CRN='13279' UNION SELECT text, category, questiontext FROM Opinion WHERE CRN='13279' UNION SELECT options, category, questiontext FROM MultipleChoice WHERE CRN='13279' UNION SELECT letter, category, questiontext FROM ExpectedGrade WHERE CRN='13279'; One of the ways to use this view would be in the following query, which allows sorting the results by the question s category (Course, Instructor, TA, Facilities/Labs, Grading): SELECT * FROM cs_akdove.answerspercrn ORDER BY category; 2. The following view can be used to display information about all courses taught during or after year The view can also be used for retrieving reports and therefore, can be traced to the functional requirement #12. 24

24 CREATE VIEW coursesbeforeyear AS SELECT * FROM Course WHERE year>2012; Procedures, Triggers and Transaction \d// 1. Procedure: The following procedure can be used to fill up the Course table with courses. Written this way, the procedure accepts the parameters passed in the following order: CRN, term, year, section, course name, course number, department name. The procedure can be traced to the functional requirement #9. CREATE PROCEDURE AddCourses( BEGIN IN newcrn INT(5), IN newterm VARCHAR(10), IN newyear year(4), IN newsection VARCHAR(5), IN newcoursename VARCHAR(100), IN newcoursenumber VARCHAR (7), IN newdepartmentname VARCHAR(40) ) INSERT INTO Course(CRN, term, year, section, coursename, coursenumber, departmentname) VALUES (newcrn, newterm, newyear, newsection, newcoursename, newcoursenumber, newdepartmentname); END \d; An example query for this procedure would be: call AddCourses('12345','Fall','2012','1','Database Management', 'CS 4342','Computer Science'); 25

25 \d// 2. Trigger: The following trigger can be used to make sure that the user is aware if he/she starts adding departments before any colleges are added to the database. Since we don't have privileges to create triggers (error: Access denied; you need the SUPER privilege for this operation), it was not possible to test this trigger. The trigger can be traced to the functional requirement #7. CREATE TRIGGER onupdate BEFORE INSERT on Department.collegeName FOR EACH ROW BEGIN IF (SELECT COUNT(collegeName) FROM College)=0 THEN = 'No colleges have been added at this point. Please make sure to add colleges before you add departments.'; END IF; END \d; \d// 3. Transaction: The following transaction can be used if we want to add instructors accounts manually (as opposed to them registering in the system through the website) and add the courses they teach at the same time. START TRANSACTION; INSERT INTO Instructor(employeeID, username, password, title, firstname,lastname,middleinitial, ) VALUES ('id1234','nvillanuevarosales','password','dr. ', 'Natalia','Villanueva Rosales','','nvillanuevarosales@utep.edu'); INSERT INTO Course(CRN, term, year, section, coursename, coursenumber, departmentname) 26

26 COMMIT; \d; VALUES ('67890','Fall','2012','1','Database Management', 'CS 4342','Computer Science'); Graphical User Interface Once the instructor has created their account, which include a username and password, their information will be saved in the Instructor table. Then they can use their username and password to log into the system and will be taken to the page shown above. From here the user can select the Update Information button to update their information on the Instructor table. The user can also select add course which will update the Course and Teaches table with the information they provide. The user can also add the CRN in any of the four text boxes provided and selecting the different options will lead to different outcomes. When add students is selected, the user can provide information for students attending the given course. This will update the Student and Enrolled in Table. Selecting delete course will remove the course from the system as well as any questions associated with that course. Rows are removed from the Course, EnrolledIn, Question, and Teaches table. Selecting Update question will allow the user to manage questions associated with a certain course. The table Question is updated with the information the user provides. Selecting view submissions will show the user student submissions to the questions provided with the students information being left out due to student privacy. 27

27 References [1]. Codex-M Company. 7 MySQL Command-line Tool Tips. March 01, [2]. Codex-M Company. Creating a New MySQL Table and Configuration MySQL. May 03, [3]. Media Temple, Inc. Using SSH in PuTTY (Windows). [4]. UTC. MySQL Commands. July 25, Updated January 21, [5]. Ullman Jefferey D, Widom Jennifer; A First Course in Database Systems. Third Edition; Prentice Hall Press. 28