Co-Op Student Evaluation Project

Meeting Minutes - 2/8/05

• General Notes
• Email System Comments
• Usability Comments
• Iteration 2 Plan
• Questions for Next Meeting
• To-Do

• Data migration
  We might want to look into an automated way of getting the information from the co-op database, where it is entered when students register for co-op, to our database. This is currently a manual process.
• We are planning on meeting on the first monday of next quarter with all of our stakeholders to give them an overview of Iteration 2.
• When we look into reporting, we should make sure that we give the users as much flexibility as possible on what information is stored in the report.

• We might want to give administrators a page to see all of the department email templates.
• Possibly support different email types.
• It was remarked that this system could possibly be a way for departments to get a hold of all of the students in that department that are currently on co-op.
• We should probably log information (especially date) when email messages are sent to students.

• Additional visual indicators for validated questions
  On top of coloring the question in red, we need another way to specify that a question needs to be filled out upon validation. Having it only show up in red may make it impossible for somebody that is color-blind to notice it.
• Need some sort of visual cue for required fields
  We should indicate that all of the questions are required if that is the case, or individual indicators on required questions if not all of them are required.
• Need to reverse the likart question numbering (from 1->5 to 5->1).
• Show date on "View Submitted Form" page
  We should show the date of the submitted form somewhere in the table on the "View Submitted Forms" page. The date could be an extra field in the table, or could possibly replace the "view" link.
• All of the student information on the same page
  All of the student information (pending and saved forms, past student and employer evaluations) should be on the same page, rather than split up into two pages as they are now.
• We need to make sure that we get information from the eventual users of the system as to how the system should work.

• We aim to complete all of the existing bugs in Bugzilla.
• We are also planning on doing the majority of the required and/or desired refactoring in this phase, as well as polishing up the existing system.
• Need to make sure that everybody comments any uncommented code they may have left in the first iteration.
• Both he form generation component and the ability for students to change their information should be fully functionaly and tested by the end of this iteration.

• Need to send Dr. Contomanolis an electronic version of his sample form by the end of the week.