Functional and non functional requirements

Group 19 - Co-op Academic Program Manager Perspective

Functional requirements

• The CO-OP-ERATOR system should also allow the co-op academic program manager to obtain a list of students that qualify as “problematic”.
• The academic program manager should be able to view what criteria are causing the student to be deemed “problematic”
• View the co-op internship evaluation submitted by an employer or a student
• Identify courses which are marked as the most or the least valuable within the current curriculum from a co-op perspective.
• In addition, the co-op program manager should be able to adjudicate the successful completion of a co-op term in case if some important documentation is missing (e.g. the employer does not submit the student evaluation form).
• A Co-op term instructor should view student evaluation forms, view the co-op internship evaluation form, and gets access to all reports during the co-op term (in myCourses).
• co-op term instructor shall be able to grade the student in myCourses (e.g. pass/fail or letter grade).
• Login shall be required after 1 hour of inactivity
• The system shall retain written fields upon the refreshing or failing of the coop evaluation page

Non-functional

• Co-op-erator response time is less than 3 seconds for 90% of the time.
• The co-op-erator shall include a secure authentication procedure to ensure that only administrators gain access.
• All ECE department employees shall be able to use all system functions within one hour of training. After this training, the average number of errors made shall not exceed one per hour of system use