university of waterloo quest (student view)dberry/html.documentation/walker/hua.pdf · university...

Software Requirements Specifications (SRS):

University of Waterloo QUEST (Student View) Version: 1.0 (SRS for CS 445 Assignment 5)

Prepared For:

Daniel M. Berry

University Of Waterloo

CS 445 (Fall 2008)

Prepared by:

Abeer Rahman (# 20184511)

Graeme McLean (# 20206909)

Xiaoyin Yang (# 20269163)

Zheng Hua (# 20202528)

Last Modified: December 24, 2008

Authors: Abeer Rahman, Graeme McLean, Xiaoyin Yang, Zheng Hua November 7, 2008

Software Requirements Specifications for Quest v1.0 i

Preface This section outlines the changes to the functionality described in this document as to the actual implementation of University of Waterloo’s Quest system as of November 2008. For academics, new additions to Quest include features to order official transcript and an academic advisement tool. The academic advisement tool includes functions to display suggested courses for future term, credits complete and credits needed based on the student’s academic plan. Functionality for final exam schedule is modified to display, within Quest, the selected courses rather than using external link. A new use case that allows the student to request for a proctor is added to the DE section. For Finances, there are three new use cases: requesting a hard copy of a term bill by mail, requesting additional T2202A (tuition tax) forms by mail, and setting up direct deposit for funds owed to student by the University. The three use cases themselves, screen shots which are affected by the use cases (including simply adding a couple of links to existing screens), and increased security due to the addition of credit card and banking information are changes resulting from these additions. The security requirement for 128 bit encryption arises from the addition of credit card payment for these services. Also note that direct deposit most likely does not exist even outside Quest as of now (but is certainly technologically reasonable). For Personal portfolio, interfaces for viewing and updating contact information have been changed. It makes it easier for students to use these two functions.


Software Requirements Specifications for Quest v1.0 ii

Table of Contents

1 Introduction ................................................................................................................. 1 1.1 Purpose ............................................................................................................................................................ 1 1.2 Scope ............................................................................................................................................................... 1 1.3 Definitions, acronyms, abbreviations, and notations ....................................................................................... 1

1.3.1 Data Dictionary ............................................................................................................................................. 1 1.3.2 Glossary ........................................................................................................................................................ 2

1.4 References ....................................................................................................................................................... 3 1.5 Overview ......................................................................................................................................................... 3

2 General Description .................................................................................................... 4 2.1 Product Perspective ......................................................................................................................................... 4 2.2 Product Functions ............................................................................................................................................ 4 2.3 User Characteristics ......................................................................................................................................... 5 2.4 General Constraints ......................................................................................................................................... 5 2.5 Assumptions and dependencies ....................................................................................................................... 5

3 Specific Requirements ................................................................................................. 6 3.1 Functional Requirements ................................................................................................................................. 6

3.1.1 Cross-Application .................................................................................................................................. 6 3.1.2 Academics............................................................................................................................................ 10 3.1.3 Finances ............................................................................................................................................... 48 3.1.4 Personal Portfolio ................................................................................................................................ 62

3.2 Non-Functional Requirements ...................................................................................................................... 70 3.2.1 Performance ......................................................................................................................................... 70 3.2.2 Usability ............................................................................................................................................... 70 3.2.3 Efficiency ............................................................................................................................................. 70 3.2.4 Reliability ............................................................................................................................................ 70 3.2.5 Security ................................................................................................................................................ 70 3.2.6 Maintainability ..................................................................................................................................... 71

3.3 External interface requirements ..................................................................................................................... 71 3.3.1 User interfaces ..................................................................................................................................... 71 3.3.2 Hardware interfaces ............................................................................................................................. 71 3.3.3 Software interfaces .............................................................................................................................. 71 3.3.4 Communication interfaces ................................................................................................................... 71

Appendix A Quest overall functionality ............................................................... 72

Appendix B Use Cases for Quest .......................................................................... 73

Appendix C Traceability Document ..................................................................... 75

Software Requirements Specifications for Quest v1.0 iii

List of Figures

Figure 1 - Quest home page screenshot ......................................................................................................................... 6 Figure 2 - Sequence Diagram for Generating External Link ......................................................................................... 9 Figure 3 - Academics home page ................................................................................................................................ 10 Figure 4 - Course Catalog Search screen ..................................................................................................................... 11 Figure 5 - Sequence Diagram for viewing information about a course ....................................................................... 12 Figure 6 - Sequence Diagram for viewing schedules of classes .................................................................................. 13 Figure 7 - Class Search Details screen ......................................................................................................................... 14 Figure 8 - Sequence Diagram for viewing the final exam schedule ............................................................................ 15 Figure 9 - Sequence Diagram for viewing grades ....................................................................................................... 16 Figure 10 - Sequence Diagram for ordering transcript ................................................................................................ 17 Figure 11 - Enroll in a Class Page ............................................................................................................................... 18 Figure 12 - Class Schedule Page ................................................................................................................................. 19 Figure 13 - Weekly Schedule Page .............................................................................................................................. 20 Figure 14 - Sequence Diagram of UC: View enrollment appointment ........................................................................ 21 Figure 15 - Sequence Diagram of UC: Add class ........................................................................................................ 23 Figure 16 - Sequence Diagram for dropping or updating a class ................................................................................. 24 Figure 17 - Sequence Diagram of UC: Swap class ...................................................................................................... 25 Figure 18 - Sequence Diagram of UC: Search for classes available for add ............................................................... 27 Figure 19 - Sequence Diagram of UC: View class schedule ....................................................................................... 28 Figure 20 - Sequence Diagram of UC: View weekly schedule ................................................................................... 29 Figure 21 - Future Course Offering Search Page ......................................................................................................... 30 Figure 22 - Sequence Diagram of UC: Add course to pre-enrollment list ................................................................... 31 Figure 23 - Sequence Diagram of UC: Drop course from pre-enrollment list ............................................................. 32 Figure 24 - Sequence Diagram of UC: Change priority and preference for course ..................................................... 33 Figure 25 - Sequence Diagram for viewing pre-enrollment results ............................................................................. 35 Figure 26 - Sequence Diagram of UC: View future term course offerings ................................................................. 36 Figure 27 - Sequence Diagram of UC: View suggested courses based on academic plan .......................................... 37 Figure 28 - Sequence Diagram of UC: View credits completed .................................................................................. 38 Figure 29 - Sequence Diagram of UC: View Credits needed ...................................................................................... 39 Figure 30 - DE View Course Material Page ................................................................................................................ 40 Figure 31 – DE View Assignment page ...................................................................................................................... 41 Figure 32 - DE View Examination Centre Page .......................................................................................................... 42 Figure 33 - Sequence Diagram of UC: Change exam centre ....................................................................................... 43 Figure 34 - Sequence Diagram of UC: View exam schedule ...................................................................................... 44 Figure 35 - Sequence Diagram of UC: View course materials information ................................................................ 45 Figure 36 - Sequence Diagram of UC: View assignment information ........................................................................ 46 Figure 37 - Sequence Diagram of UC: View assignment information ........................................................................ 47 Figure 38 – Finances Home Page Screenshot .............................................................................................................. 48 Figure 39 - Use Case Diagram for Quest Finance Section .......................................................................................... 49 Figure 40 – List of Terms for Which Student Has Account Information Screenshot .................................................. 50 Figure 41 – Account Term Summary Screenshot ........................................................................................................ 50 Figure 42 – Account Term Details Screenshot ............................................................................................................ 51 Figure 43 – Setup Direct Deposit Page Screenshot ..................................................................................................... 51 Figure 44 – Request Additional T2202A Forms Page Screenshot .............................................................................. 52 Figure 45 – T2202A Request Confirmation Screen Screenshot .................................................................................. 52 Figure 46 – Sequence Diagram for Viewing Account Summary for Term ................................................................. 54 Figure 47 – Sequence Diagram For Viewing Account Details For Specific Term ...................................................... 55 Figure 48 – Sequence Diagram For E-mailing Account Details as PDF ..................................................................... 56 Figure 49 – Sequence Diagram For Ordering Account Details By Mail ..................................................................... 57 Figure 50 – Sequence Diagram For Ordering Additional T2202A Forms .................................................................. 58


Software Requirements Specifications for Quest v1.0 iv

Figure 51 – Sequence Diagram For Setting Up Direct Deposit ................................................................................... 59 Figure 52 – List of Years Student Has Financial Aid Information Screenshot ............................................................ 60 Figure 53 – Financial Aid Yearly Details Screenshot.................................................................................................. 60 Figure 54 – Sequence Diagram For Viewing Financial Aid For Year......................................................................... 61 Figure 55 - Personal Portfolia page ............................................................................................................................. 62 Figure 56 - Use Case for Personal Portfolio ................................................................................................................ 62 Figure 57 - Demographic Information page ................................................................................................................ 64 Figure 58 – View Contact Information page ............................................................................................................... 65 Figure 59 - Update Contact In formations pages ......................................................................................................... 67 Figure 60 - Sequence Diagram for updating contact information ................................................................................ 68 Figure 61 - Holds page ................................................................................................................................................ 69


Software Requirements Specifications for Quest v1.0 1

1 Introduction

This document is a complete product requirement specification for the University of Waterloo Quest

System. This document contains all information regarding requirements placed on Quest by the customer

(the University of Waterloo) arranged by the features of Quest. Unless otherwise stated, this document

should supersede other documents which exist for Quest.

1.1 Purpose

The purpose of this document is to detail the requirements placed on the Quest system and serves as a

contract between the developers and the University of Waterloo as to what is expected of Quest and how

students need to be able to interact with Quest. The intended audience is both the customer (University of

Waterloo) and the developers.

1.2 Scope

This document covers the details of the Quest system, including the behavioural, functional, and non-

functional requirements for student view. This document describes only the Quest software, as Quest is

meant to run in modern web browsers on a modern PC, so the hardware is not part of the system being

described. The detail shall be in the various tasks a student can perform on the Quest system.

1.3 Definitions, acronyms, abbreviations, and notations

1.3.1 Data Dictionary The following table describes the data that are used in this document.

Term Definitions

Academic Advisement Tool

A tool that helps student to enroll in courses based on student’s academic plan.

Academic Plan A set of courses required to obtain a degree, minor or option. Account balance = Total money owed to university by student + total money paid to student by

university (refunds, etc.) – total money paid to university by student – total money owed to student by university (refunds, etc.). A positive balance means the student owes money to the university, a negative balance means the



university owes money to the student. A balance of 0 means both sides have paid their fees.

Class Schedule A list of classes enrolled for a specified term. Credit The numerical value that student receives upon completion of a course. DE Distant Education Enrollment Appointment

A period of time set for student to enroll in courses before open enrollment. Enrollment appointments are usually a few days.

Fees Any money charged by the University to the student Financial aid Money given to the student by the University or government based on financial

need (government loans, grants, and bursaries). Private sector financial aid (such as bank student loans) is not part of definition for purposes of this document.

Student awards Money given to the student as an award for achievement (scholarships). Private sector awards are not included in the definition for the purposes of this document.

Term A standard 4 month school period (either September – December, or, January-April, or May – August)

Transcript Document displaying student’s academic record through University Unofficial Transcript

An overview of a student’s academic performance while in University, which cannot be used for any official means.

Weekly Schedule A list of classes enrolled with detailed time and location for a selected week.

1.3.2 Glossary The following table describes the definitions that are used in this document.

Term Definitions

Academics Section of Quest to view and enrol in courses, view schedules, view grades, generate unofficial transcripts, and other academic functions

Class Scheduled offering of a course Course A set course code, course name, and rough curriculum to base classes off of Database The underlying layer of storage for Quest. This document does not deliver a

database design. Direct deposit A method for University to directly deposit money owed to student in their bank

accounts once given some basic account information by student. Enrollment A process designed to add, drop and update classes for future term. Finances Section of Quest to view tuition fees, payment information, financial aid,

request forms by mail, and setup direct deposit Hold A hold is a notice that appears on a student’s account. For example, if a student

owe fees, such as library fees, or have committed an academic offence, then the student may find a hold placed on his/her account. It may restrict his/her privileges such as requesting transcripts or enrolling in courses.

institution When student has not used Quest for a period of time, Quest automatically logs out.

Jobmine A system for managing co-op students (job searching, matching, ranking, etc.) Personal Portfolio

Section of Quest to view and edit student’s personal information such as addresses and phone numbers

Pre-enrollment A process that allows for adding courses before the enrolment period.



Registrar’s Office The University office responsible for managing all academics records (transcripts, grades, proof of enrolment, etc.)

Session timeout A session timeout occurs Student A student is any student who is currently enrolled in university Student Accounts The University office responsible for collecting and processing fees owed by

students. Student Awards and Financial Aid Office

The University office responsible for all student awards and financial aid administration (OSAP, grants, loans, scholarships, etc.)

T2202A Tuition tax forms for a student in Canada. Must be provided as proof of tuition fee payment and University enrolment for Canadian Revenue Agency

Transcipt UC Use Case User name UW Angel A system for managing University courses (assignment posting, marks, class

discussions, etc.) UWdir The University of Waterloo Campus Directory is a database of information of

faculty, staff, and students. It provides authentication for Quest (as well as other University of Waterloo online services).

Session manager

The document uses the Unified Modelling Language (2.0) as the basis language for design.

1.4 References

Quest Glossary of Terms: http://www.quest.uwaterloo.ca/help/glossary.html

1.5 Overview

In the rest of this document, Section 2 gives a general description of Quest, and identifies all assumptions

and constraints placed upon it. Sections use case diagrams, and sequence diagrams, organized by feature

type. Section 3 exposes the specific requirements of Quest demanded by the customer via use cases, class

diagrams, use case diagrams, and sequence diagrams, organized by feature typealso provides non-

functional user requirements, as well as user, hardware, software and communication interfaces.



2 General Description The University of Waterloo requires a Web based system, known as Quest, to allow students only (for the

purposes of this document) to perform the administrative tasks discussed in Section 3 online.

The Quest system is a Web based system with the following major groups of functionality available to

students:

• Personal Portfolio: View and edit student’s personal information such as addresses and phone

numbers.

• Finances: View tuition fees, payment information, financial aid, request forms by mail, and setup

direct deposit.

• Academics: View and enroll in courses, view schedules, view grades, generate unofficial

transcripts, and perform other academic functions.

2.1 Product Perspective

The Quest system is Web based and intended to run in all of the major Web browsers (specifically

Firefox, Internet Explorer, Safari, and Opera). There is no hardware component to Quest, as it should run

on any modern (capable of running Windows 98 or higher) PC, which belongs to the student and not to

the Quest system. Quest is used by students for functionality that would otherwise need to be done at the

central administration offices (Registrar’s Office, Student Accounts, and the Financial Aid Office in

particular). Activities that do not directly concern these offices, such as class assignments or co-op job

postings, are generally to be performed outside of Quest (possibly using other systems such as UW Angel

and Jobmine).

2.2 Product Functions

The main function of Quest is to automate University administrative features which were previously done

manually. These functions fall into three main groups: academics, financials, and personal profile.



2.3 User Characteristics

The user from this document’s perspective is a current University of Waterloo student. The student is

assumed to be competent enough with computers to log into and navigate Quest. Quest needs to be

intuitive enough that new users can figure interaction out easily without any specific training.

The software is used by current students of University of Waterloo (for the purposes of this document). In

order to use Quest, the student needs a UWDir userID and password to access Quest.

2.4 General Constraints No constraints defined.

2.5 Assumptions and dependencies

The following assumptions are made:

• The student’s computer is relatively modern (while Quest should work on any computer made this

decade or even earlier, success cannot be guaranteed on very old computers such as Pentium 1’s).

• the student is using one of the supported web browsers and is able to connect at an acceptable speed

(28k modem or higher)

• Not all students log on at same time (server is not set up for this load)

• Other systems, such as UWDir, are running and functioning correctly

• Student’s computer supports typing in English and reading English characters



3 Specific Requirements

3.1 Functional Requirements Quest provides functionality for maintaining a student’s personal, academic and financial records at the

university. The overall functionalities of Quest and its associations are provided in Appendix A (Quest

overall functionality). An exhaustive list of all the use cases supported by Quest is provided in Appendix

B (Use Cases for Quest).

3.1.1 Cross-Application

Figure 1 - Quest home page screenshot

This section is for features which are not specific to any one section of Quest. The features either apply to

Quest as a whole or can be used by any section of Quest.

Security

Quest must utilize 128 bit encryption, particularly since it now allows students to enter credit card and

banking information.

Login / Logoff



This section deals with Login and Logoff functions in Quest. Student needs UWdir user ID and password

to login to Quest. Quest has its service hours. Student can only access Quest within its service hours. If

student has used an incorrect password 3-5 times within a short period of time, Quest automatically locks

his/her Quest access for 24 hours. Quest also has session times out.

Quest provides links to UWdir page for student who has the following requirements: 1) student who uses

Quest first time needs to activate his/her user ID and password 2) student wants to change his/her

password 3) student lost his/her password

UC1: Log into Quest

Goal: To log into Quest

Pre-condition: UWdir user ID and password are required to login to Quest within its service

hours

Post-condition: Student is logged into Quest

System: Session Manager

Actor: Student

Process Description:

1. Open Quest Login page

2. Enter UWdir user ID and password

3. Clicks on “Submit” button

Alternatives: [none]

Exceptions:

1. Student tries to log into Quest within its service hours. Login failed. Quest displays a warning

message

2. Student enters wrong UWdir user ID or password. Login failed. Quest displays a warning

message

UC2: Log out of Quest

Goal: To log out of Quest

Pre-condition: Student already logged into Quest

Post-condition: Student is logged out of Quest


Actor: Student




1. Clicks on Sign Out button


Exceptions: Session times out also do log out of Quest.

UC3: System lock out

Goal: To lock out Quest access

Pre-condition: Student has used an incorrect password 3-5 times within a short period of time

Post-condition: Quest automatically locks actor’s Quest access for 24 hours.


Actor: Student

Process Description: [none]


Exceptions: [none]

External Link Generator

This is a general description of the process used to open links that lead outside of Quest. These links are

scattered throughout Quest in all sections, and may lead to parts of the University of Waterloo website, or

even entirely external organizations such as OSAP or the major banks.

UC4: Open External Link

Goal: To open link outside of Quest

Pre-condition: Student is logged into Quest

Post-condition: The link is opened in a new window

System: Quest

Actors: Student


1. When any page with external link is loading, Quest generates the link with the browser

instructions of what site to go to and to open in a new window and displays on the

specific page.

2. Student clicks link and link opens in new window on their computer (Quest is not

informed of this action)


Exceptions:



2. Student’s browser prevents opening a new link (pop-up blocking, etc.). Quest must assume the

student is able to deal with this situation (allowing popup or similar action), as Quest cannot act at

this point. In the worst case, it may appear to the student that clicking the link does nothing.

Figure 2 - Sequence Diagram for Generating External Link

-



3.1.2 Academics

The Academics feature is responsible for organizing the student’s academic information. The Academic

feature allows students to add or drop courses and view grades. The Academics home page is displayed

below.

Figure 3 - Academics home page

The Academics section is divided up into several functions, depending on functionality provided by

Quest.

Course Catalogue and Course Schedules



This section deals with producing course information. Quest interfaces with the list of courses offered

from which students are allowed to enrol (or pre-enrol). Course information includes details such as:

course name, course code, lecturer, and timings for the course.

Figure 4 - Course Catalog Search screen

UC5: View Information about a course

Goal: To view information about a course

Pre-condition: Student is logged into Quest and is currently on the Academics home page

Post-condition: The information regarding the course is displayed.

System: Quest

Actors: Student


1. Student clicks on the course search button.

2. Quest displays the course search page.

3. Student types in the name of the course and the course code, and clicks “Search”.

Alternatives:

Course exists in the database.

4. Quest retrieves course information, and displays the information.

Course does not exist in the database

4. Quest indicates that the course does exist in the database.



Exceptions: [none]

Figure 5 - Sequence Diagram for viewing information about a course

UC6: View Schedule of Classes

Goal: To view the schedule of a course being offered

Pre-condition: Student is logged into Quest, course exists in the database

Post-condition: Schedule information of a course is displayed

System: Quest

Actors: Student


1. Student clicks on the “schedule” for the selected course.

2. Quest retrieves lists the schedules for the course.


Exceptions: [none]



Figure 6 - Sequence Diagram for viewing schedules of classes



Figure 7 - Class Search Details screen

UC7: View final examination schedule

Goal: To view the final exam schedule

Pre-condition: None

Post-condition: Student has the final examination schedule for the courses he/she is currently

enrolled in.

System: Quest

Actors: Student


1. Student clicks on the “Final Examination” link.



2. Student selects term and clicks the “Search” button.

3. Quest displays “Final Examination” schedule for the selected term.


Exceptions: [none]

Figure 8 - Sequence Diagram for viewing the final exam schedule

Academic Record

UC8: View grades for a specified term

Goal: To view grades for a particular term

Pre-condition: None

Post-condition: The grades are displayed for the selected term

System: Quest

Actors: Student


1. Student clicks on “View Grades” link.

2. Quest displays list of terms in which the student was enrolled in the university as a

student (that is, a term with one or more courses).

3. Student clicks on the term of choice.



4. Quest retrieves final grades for the courses student was enrolled in for the selected term

Exceptions: [none]

Figure 9 - Sequence Diagram for viewing grades

UC9: View unofficial transcript

Goal: To view his/her unofficial transcript

Pre-condition: None

Post-condition: Student is displayed his/her unofficial transcript

System: Quest

Actors: Student


1. Student clicks on “View Unofficial transcript”

2. Quest provides options for selected “Graduate” or “Undergraduate” transcript.

3. Student selects “Undergraduate” and clicks on [OK].


Exceptions: [none]



UC10: Order official transcript

Goal: To order official transcript

Pre-condition: None

Post-condition: Request for ordering the transcript has been sent

System: Quest

Actors: Student


1. Student clicks on “Order Official transcript”

2. Quest provides options for selected “Graduate” or “Undergraduate” transcript.

3. Student selects “Undergraduate” and clicks on [OK].


Exceptions: [none]

Figure 10 - Sequence Diagram for ordering transcript



Enrollment

The enrollment section of the Quest system is designed for course enrollment. In this section, the student

is allowed to use features such as view enrollment appointment, add a class and drop a class.

Figure 11 - Enroll in a Class Page



Figure 12 - Class Schedule Page



Figure 13 - Weekly Schedule Page

For use cases in this section, assume the precondition: student is logged on to Quest at the Academics

screen.



UC11: View enrollment appointment

Goal: To view the enrollment appointment information for a term.

Precondition: A term is selected.

Postcondition: The enrollment appointment information is displayed for the selected term.

System: Course Enroller

Actors: Student

Overview: This use case describes what happens when the student tries to view an

enrolment appointment.


1. Student clicks on the “View Enrollment Appointment” link.

2. Student clicks on a term.

3. Course Enroller displays enrollment appointment information for the selected term.

Exceptions: [none]

Figure 14 - Sequence Diagram of UC: View enrollment appointment



UC12: Add class

Goal: To add one or more classes to a course schedule.

Precondition: A term is selected during its enrollment period.

Postcondition: One or more classes are added to the course schedule.


Actors: Student

Overview: This use case describes what happens when the student tries to add one or more

classes.

Related Use Cases: Drop class, Swap class, Lookup Class


1. Student clicks the “Add Classes” link.

2. Student enters class number for a class.

3. Student clicks the “submit” button.

4. Course Enroller displays the updated course schedule with the class added.

Exceptions:

A class cannot be added due to conflict or error

a) Course Enroller displays error message saying the course cannot be added with

reason



Figure 15 - Sequence Diagram of UC: Add class

UC13: Drop or update class

Goal: To drop one or more classes.

Precondition: A term is selected with at least one class enrolled.

Postcondition: One or more classes are dropped.


Actors: Student

Overview: This use case describes what happens when the student tries to drop one or more

classes.

Related Use Cases: Add class, Swap class


1. Student selects “drop” from a drop-down list for a class

2. Student presses the “submit” button.



3. Course enroller displays the updated course schedule.

Alternatives:

1. Student selects “drop to waitlist” from a drop-down list for a class.

1. Student selects “update” from a drop-down list for a class.

Exceptions: [none]

Figure 16 - Sequence Diagram for dropping or updating a class

UC14: Swap class

Goal: To swap one or more enrolled classes.

Precondition: A term is selected during its enrollment period with at least one class enrolled.

Postcondition: One or more classes are swapped.


Actors: Student

Overview: This use case describes what happens when the student tries to swap one or more

classes.



Related Use Cases: Add class


1. Student clicks the “Swap Classes” link.

2. Student enters class number for a class to be swapped.

3. Student clicks the “Submit” button.

4. Course enroller displays the updated course schedule.

Exceptions:

1. The entered class number already exists in the course schedule

a) Quest displays error message saying the class cannot be swapped.

Figure 17- Sequence Diagram of UC: Swap class



UC15: Search for classes available for add

Goal: To search classes offered for the selected term.

Precondition: In the process of adding or swapping class for a term.

Postcondition: A list of classes is displayed.


Actors: Student

Overview: This use case describes what happens when the student tries to search for classes

to add to the course schedule.

Related Use Cases: Add class, Swap class


1. Student clicks the “search” button beside the class number field to enter class search

page.

2. Student enters search criteria in the text boxes.

3. Student presses the “search” button.

4. Course Enroller displays a list of classes.

Exceptions:

1. Search criteria doesn’t match any results

a) No classes are displayed.



Figure 18 - Sequence Diagram of UC: Search for classes available for add

UC16: View class schedule

Goal: To view the class schedule of a term.

Precondition: None

Postcondition: Class schedule is displayed for the selected term.


Actors: Student


1. Student clicks on the “View Class Schedule” link.

2. Student selects a term.

3. Course Enroller displays class schedule for the selected term.

Exceptions: [none]



Figure 19 - Sequence Diagram of UC: View class schedule

UC17: View weekly schedule

Goal: To view the weekly schedule.

Precondition: None

Postcondition: Weekly schedule is displayed.


Actors: Student


1. Student clicks on the “View My Weekly Schedule” link.

2. Course Enroller displays weekly schedule for the current week.

Alternatives:

3. Student enters a date in the “As of Date” text box.

4. Student presses the “Go” button.

5. Course Enroller displays weekly schedule for the week containing the entered date.



Exceptions: [none]

Figure 20 - Sequence Diagram of UC: View weekly schedule

Pre-Enrollment

This section is used for pre-enrollment that allows the student to choose courses for a future term. The

student can add or drop courses, change course preferences, view pre-enrolled course selection, and view

pre-enrollment results.



Figure 21 - Future Course Offering Search Page


screen.

UC18: Add course to pre-enrollment list

Goal: To add course to the pre-enrollment list.

Precondition: At pre-enrollment page. A term is selected during its pre-enrollment time period.

Postcondition: One or more courses are added to the pre-enrollment list.

System: Pre-Enroller

Actors: Student

Overview: This use case describes what happens when the student tries to add courses to the

pre-enrollment list.


1. Student clicks the “Add Course” link.

2. Student enters a course code.

3. Student sets the course’s priority.

4. Student selects scheduling preference for the course.

5. Student presses the “Submit” button.

6. Pre-Enroller displays the updated pre-enrollment list.

Exceptions:

The course entered is not offered for the selected term



a) Quest displays message saying the course cannot be added.

Figure 22 - Sequence Diagram of UC: Add course to pre-enrollment list

UC19: Drop course from pre-enrollment list

Goal: To drop one or more courses from the pre-enrollment list

Precondition: A term is selected during its pre-enrollment time period with at least one course

in the pre-enrollment list.

Postcondition: One or more courses are dropped from the pre-enrollment list

System: Pre-enroller

Actors: Student

Overview: This use case describes what happens when the student tries to drop courses from

the pre-enrollment list.

Related Use Cases: Add course to the pre-enrollment list


1. Student clicks the “Delete” button

2. Student clicks the “Submit” Button




Exceptions: [one]

Figure 23 - Sequence Diagram of UC: Drop course from pre-enrollment list

UC20: Change priority and preferences for course

Goal: To change priority and preferences for course



Postcondition: The priority and the preferences are changed for one or more courses.

System: Pre-Enroller

Actors: Student

Overview: This use case describes what happens when the student change priority and

preferences for one or more pre-enrolled courses.

Related Use Cases: Add course to the pre-enrollment list




1. Student selects a priority value from the drop-down list of a course

2. Student selects a preference for the course


Exceptions:

Priority already selected for other courses.

a) Quest displays message saying the priority cannot be set.

Figure 24 - Sequence Diagram of UC: Change priority and preference for course

UC21: View pre-enrolled course selection

Goal: To view pre-enrolled course selection for the selected term.



Postcondition: Pre-enrolled course selection is displayed for the selected term.


Actors: Student

Overview: This use case describes what happens when the student tries to view pre-enrolled

course selection for a term.

Related Use Cases: Add course to the pre-enrollment list, Drop course from pre-enrollment list


1. Student clicks on the “View My Future Term Course Selection” link



2. Student select a term

3. Pre-Enroller displays pre-enrolled courses for the selected term.

Exceptions: [none]

UC22: View pre-enrollment results

Goal: To view pre-enrollment results for the selected term.

Precondition: A term is selected where at least one course was pre-enrolled.

Postcondition: Pre-enrollment results are displayed for the selected term.


Actors: Student

Overview: This use case describes what happens when the student tries to view pre-

enrollment results for a term.



1. Student clicks on the “View My pre-enrollment Results” link

2. Student selects a term

3. Pre-Enroller displays pre-enrollment results for the selected term.

Exceptions: [none]



Figure 25 - Sequence Diagram for viewing pre-enrollment results

UC23: View future term course offerings

Goal: To view courses offered for the future term.

Precondition: None

Postcondition: A list of course offered for the future term is displayed.


Actors: Student

Overview: This use case describes what happens when the student tries to view future term

course offerings



1. Student clicks on the “View Future Term Course Offerings – All Courses” link

2. Pre-Enroller displays a list of all of the courses offered for the future term.

Alternatives:

1. Student clicks on the “View Future Term Course Offerings – By Subject” link

2. Student enters term and subject



3. Pre-Enroller displays a list of all of the courses offered for the selected term with the

entered subject.

Exceptions: [none]

Figure 26 - Sequence Diagram of UC: View future term course offerings


This section of the Quest system is designed for advising student for course enrollment. In this section,

the student is allowed to view suggested courses for future term, view completed credits and view credits

needed based on student’s academic plan.


screen.

UC24: View suggested courses based on academic plan



Goal: To view suggested courses for the future term.

Precondition: None

Postcondition: Suggested courses are displayed for the future term.

System: Academic advisement tool

Actors: Student



1. Student clicks on the “View My Suggested Courses” link.

2. Academic advisement tool displays suggested courses for the future term based on

Student’s academic plan.

Exceptions: [none]

Figure 27 - Sequence Diagram of UC: View suggested courses based on academic plan

UC25: View credits completed

Goal: To view credits student completed.

Precondition: None

Postcondition: Credits student completed are displayed.


Actors: Student

Related Use Cases: View suggested courses based on academic plan


1. Student clicks on the “View Credits Completed” link

2. Academic advisement tool displays credits student completed.

Exceptions: [none]



Figure 28 - Sequence Diagram of UC: View credits completed

UC26: View credits needed

Goal: To view credits student need based on student’s academic plan.

Precondition: None

Postcondition: Credits student needs are displayed.


Actors: Student

Related Use Cases: View suggested courses based on academic plan, View credits completed


1. Student clicks on the “View Credits Needed” link

2. Academic advisement tool displays credits student needs based on student’s academic

plan.

Exceptions: [none]



Figure 29 - Sequence Diagram of UC: View Credits needed

Distant Education

This section manages the distant education course information of the student. In this section, the student

can set the exam centre for a DE course, view exam schedule, view course material information and view

assignment information.



Figure 30 - DE View Course Material Page



Figure 31 – DE View Assignment page



Figure 32 - DE View Examination Centre Page


screen.

UC27: Change exam centre

Goal: To select an exam location for DE course.

Precondition: The student is currently enrolled in at least one DE course.

Postcondition: An exam centre is changed

System: DE Controller

Actors: Student

Overview: This use case describes what happens when the student tries to select an exam

centre for DE course

Related Use Cases: View exam schedule

Process Description

1. Student clicks on the “View/Change Exam Schedule Details” link


3. Student chooses a course



4. Student selects a value from the drop-down list of exam centres

5. Press the “save changes” button.

6. DE Controller displays the changed exam centre for the selected DE course.

Exceptions: [none]

Figure 33 - Sequence Diagram of UC: Change exam centre

UC28: View exam schedule

Goal: To view the exam schedule for DE course.

Precondition: The student is enrolled in at least one DE course.

Postcondition: Exam schedule is displayed for the selected DE course.


Actors: Student

Overview: This use case describes what happens when the student tries to view the exam

schedule for a DE course.

Related Use Cases: Change exam centre

Process Description

1. Student clicks on the “View/Change Exam Schedule Details” link.




3. Student chooses a DE course.

4. DE Controller displays the exam schedule details for the selected DE course.

Exceptions: [none]

Figure 34 - Sequence Diagram of UC: View exam schedule

UC29: View course material information

Goal: To view the course material information for the selected DE course.


Postcondition: Course material information is displayed for the selected DE course.


Actors: Student

Overview: This use case describes what happens when the student tries to view the course

material information for a DE course.

Related Use Cases: View exam schedule details

Process Description

1. Student clicks on the “View Materials Information” link.


3. Student chooses a DE course



4. DE Controller displays the material information for the selected DE course.

Exceptions: [none]

Figure 35 - Sequence Diagram of UC: View course materials information

UC30: View assignment information

Goal: To view the assignment information for the selected DE course.


Postcondition: Assignment information is displayed for the selected DE course.


Actors: Student

Overview: This use case describes what happens when the student tries to view the DE

assignment information.

Related Use Cases: View exam schedule details, View materials information

Process Description

1. Student clicks on the “View Assignment Information” link.





4. Student clicks the “View All” link.

5. DE Controller displays assignment information on all assignments for the selected

course.

Alternatives:

4. Student chooses an assignment

5. DE controller displays assignment information for the selected assignment.

Exceptions: [none]

Figure 36 - Sequence Diagram of UC: View assignment information

UC31: Request for proctor

Goal: To request a proctor for a DE course final examination.


Postcondition: A proctor request is submitted.


Actors: Student

Related Use Cases: View exam schedule details

Process Description



1. Student clicks on the “Request Proctor” link



4. Student selects a location.

5. Student clicks on the “Submit” button.

6. DE Controller displays the submitted request.

Exceptions: [none]

Figure 37 - Sequence Diagram of UC: View assignment information



3.1.3 Finances

Figure 38 – Finances Home Page Screenshot

The finances section of Quest allows students to view their tuition and other fees, view financial aid, and

perform requests - e-mailing account details, requesting hard copy of account details, setting up direct

deposit and requesting additional tax forms. There are a number of links to outside of Quest, such as fee

payment instructions (see Section 3.INSERT HERE). There is no way to pay fees or apply for financial

aid within Quest, and the section of Quest exists primarily to view information already on file with the

University with some support for sending requests to the University. The finances section is the

University’s official method of sending term fees to students since this function is no longer done in paper

format by default. Navigating to the Finances home page simply involves selecting the “Finances” link

on the main page of Quest.



Figure 39 - Use Case Diagram for Quest Finance Section

The Finances section is divided into two major groups of functionality: account and financial aid. The

Financial Aid section exists for student awards and financial aid. All other account information belongs in

the Account section.

Account Summary

This section deals with the student’s financial account, including charges and payments. No online

payment for fees currently exists. There is only payment for mailing a hard copy of account summary or

T2202A forms.

.



Figure 40 – List of Terms for Which Student Has Account Information Screenshot

Figure 41 – Account Term Summary Screenshot



Figure 42 – Account Term Details Screenshot

Figure 43 – Setup Direct Deposit Page Screenshot



Figure 44 – Request Additional T2202A Forms Page Screenshot

Figure 45 – T2202A Request Confirmation Screen Screenshot



UC32: View financial summary for specified term

Goal: To view financial summary for a specified term

Pre-condition: Student is logged into Quest

Post-condition: Financial summary for specified term is displayed

System: Financial Management

Actors: Student


1. Student clicks on the Account Summary link

2. Quest displays a list of all terms in which the student has been enrolled in the University.

Fall and winter terms are displayed regardless of whether or not the student has fees to

pay that term, including when on co-op, while spring terms are only displayed for terms

when the student has fees such as tuition. The institution and balance for each term are

also displayed, as well as an overall balance (balance for all terms).

3. Student selects the term for which they wish to view information

4. Quest displays summary for the term, including student personal information, fee status,

charge activity, payment activity, financial aid activity, and the term balance


Exceptions:

2. Quest finds no terms to display (this may happen for a new student whose fees have not

yet been posted). The student cannot do anything useful in this section at this time and

should manually return to the Finances Section or Quest home screen.



Figure 46 – Sequence Diagram for Viewing Account Summary for Term

UC33: View account details for specific term

Goal: To view financial details for a specific term

Pre-condition: Student is logged into Quest; the term exists with summary page loaded. Starts

at the end of use case 32.

Post-condition: Financial details are displayed for a specific term


Actors: Student


1. On the term summary page, the student clicks the “View Account Detail” link.

2. Quest displays a detailed breakdown of fees and payments for the term as well as fee

payment information and links.


Exceptions: [none]



Figure 47 – Sequence Diagram For Viewing Account Details For Specific Term

UC34: E-mail account details sent to e-mail address as PDF

Goal: To have Account Details e-mailed as PDF

Pre-condition: Student is logged into Quest, term exists with account detail page loaded. Starts

at the end of use case 33.

Post-condition: Term details e-mailed to student as PDF


Actors: Student


1. Student clicks the “Email” button on the term account details page

2. Quest displays a page for student to enter and submit their e-mail address and

3. Student enters e-mail address into text box and clicks the “Send” button

4. Quest sends the term account summary as a PDF to the entered address and refreshes the

page on the student’s computer. Quest is not concerned if the e-mail address is valid or

not.

Student may enter another e-mail address and send again, or navigate back to the previous page or Quest

home screen


Exceptions: [none]



Figure 48 – Sequence Diagram For E-mailing Account Details as PDF

UC35: Request Account Details By Mail (Hard Copy)

Goal: To inform Registrar’s Office of student’s order for hard copy of account details

and charge the student’s credit card a specified fee.

Pre-condition: Student is logged into Quest, term exists with account detail page loaded.

Registrar’s office has set the fee.

Post-condition: Registrar’s office receives instruction to send hard copy of account details.

Student’s credit card is charged specified amount.


Actors: Student


1. Student clicks the “Mail Hard Copy” button on the term account details page

2. Quest displays a page for student to enter a mailing address to send the hard copy, a

billing address to verify credit card information, as well as credit card information to pay

for the hard copy. Their mailing address from the personal portfolio is entered into both

the mailing and billing input boxes by default, but may be modified.

3. Student optionally changes their address and must enter credit card information, and then

submits using 128 bit encryption.

4. Quest validates and charges student’s credit card.

5. Quest sends an instruction to registrar office staff to send the hard copy and displays a

success message to the student with links back to other sections of Quest.




Exceptions:

4. Credit card validation or charge fails, Quest displays an error message with credit card

fields to allow student to re-enter information. The student may either navigate away from the

page (ending the use case) or resubmit with new credit card information Quest and step 4 is

repeated.

Figure 49 – Sequence Diagram For Ordering Account Details By Mail

UC36: Request Additional T2202A forms

Goal: To inform Registrar’s Office of student’s order for additional copies of T2202A

tuition tax forms and charge the student’s credit card a specified fee.

Pre-condition: Student is logged into Quest on Finances home page. Registrar’s office has

entered fee.

Post-condition: Registrar’s office receives instruction to send two additional T2202A forms to

student. Student’s credit card is charged specified fee.


Actors: Student


1. Student clicks the “Request Additional Tuition Tax Forms” link on the main Finances

Page

2. Quest displays a page for student to enter a mailing address to send the forms, a billing

address to verify credit card information, credit card information to pay for the forms, and



the number of forms to order. Each form contains 2 T2202A slips. The student’s mailing

address from the personal portfolio is entered into both the mailing and billing input

boxes by default

3. Student optionally changes their address and enters credit card information, and then

submits using 128 bit encryption.

4. Quest charges student’s credit card

5. Quest sends an instruction to registrar office staff to send the forms and displays a

success message to the student with links back to other sections of Quest.


Exceptions:

4. Credit card validation or charge fails, Quest displays an error message with credit card

fields to allow student to re-enter information. The student may either navigate away from the

page (ending the use case) or resubmit with new credit card information and step 4 is repeated.

Figure 50 – Sequence Diagram For Ordering Additional T2202A Forms

UC37: Set Up Direct Deposit For Money Owed To Student

Goal: To store direct deposit information so money owed to student (dental plan

refunds are one example) may be directly deposited into student’s bank account

rather than sending a cheque by mail.

Pre-condition: Student is logged into Quest on Finances home page.

Post-condition: Direct deposit information is stored to be used later for automatic refunds (refund

itself is outside of student view).




Actors: Student


1. Student clicks the “Set Up Direct Deposit” link on the main Finances page

2. Quest displays a page for student to enter bank account information required for direct

deposit. All information is available from bottom of cheque.

3. Student enters information and clicks submit

4. Quest validates information, stores in database, and displays a success message with links

back to previous parts of Quest


Exceptions:

4. Validation fails, Quest displays an error message with fields to allow student to re-enter

information. The student may either navigate away from the page (ending the use case) or

resubmit with new information and step 4 is repeated. Quest cannot guarantee information is

different than last submit.

Figure 51 – Sequence Diagram For Setting Up Direct Deposit



Financial Aid

This section deals with any financial aid and awards the student receives for University, organized by

calendar year.

Figure 52 – List of Years Student Has Financial Aid Information Screenshot

Figure 53 – Financial Aid Yearly Details Screenshot



UC38: View financial aid for calendar year

Goal: To view financial aid for calendar year

Pre-condition: Student is logged into Quest on the Finances home screen

Post-condition: Financial aid information for the year is displayed


Actors: Student


1. Student clicks on the “View My Financial Aid” link

2. Quest displays a list of all calendar years the student received or will receive financial aid

3. Student selects a year

4. Quest displays financial aid information for the term, including all individual awards and

amounts broken down by term, as well as if the aid is already paid or only anticipated.

OSAP and financial aid reference materials and external links are also displayed.


Exceptions:

2. Quest finds no terms to display. This happens if student has never received and has no

anticipated financial aid. No terms will be available for student to click, so they should click links to

return to Finance section or Quest home screen.

Figure 54 – Sequence Diagram For Viewing Financial Aid For Year



3.1.4 Personal Portfolio

This section deals with student’s personal portfolio. Quest provides the functionality to student to view

his/her demographic information, contact information, service holds. Quest also provides the functionality

to student to update his/her contact information.

Figure 55 - Personal Portfolia page

Figure 56 -Use Case for Personal Portfolio



UC39: View demographic information

Goal: To view a summary of student’s personal information

Student is logged

Pre-condition: Student is logged into Quest on the Personal Portfolio page

Post-condition: Demographic information is displayed

System: Personal Portfolio controller

Actors: Student


1. Student clicks on “Demographic ”Summary button on Personal Portfolio page

2. Quest retrieves student’s demographic information

Quest displays the following details

A) Student Name

B) ID

C) Gender

D) Date of Birth

E) Birth Country

F) Marital Status

G) National Identification Number

H) Citizenship Information

I) Visa or Permit Data


Exceptions: [none]



Figure 57 - Demographic Information page

UC40: View contact information

Goal: To view a summary of student contact information


Post-condition: Contact information is displayed


Actors: Student


1. Student clicks on “View Contact Information” button on Personal Portfolio page.

2. Quest retrieves a summary of student’s contact information.

Quest displays the following details:

A) Names

B) Addresses



C) Phone Numbers (Home, Cellular, Mailing)

D) Email Address

E) Emergency Contacts


Exceptions: [none]

Figure 58 – View Contact Information page

UC41: Update contact information

Goal: To update student’s contact information

Pre-condition: Student is logged into Quest on the Personal Portfolio page. The original contact

information in Fig 58 displays accordingly in Update contact information pages.

Post-condition: Update contact information interface is displayed


Actors: Student




1. Student selects contact information he/she wants to update

2. Quest retrieves the selected contact information

3. Student edits the original information or add new information

4. Student clicks on “Save” button to submit updated information to Quest

5. Quest update information automatically


Exceptions:

1. Student wants to change name. Quest provides the functionality for student to require a name

change form. Student needs to complete the form and submit to the registrar’s office or the

graduate studies office.

2. Student wants to change email address. Quest provides the functionality to change email

addresses via UWdir. Student needs user ID and password to access UWdir. Changes will not

be reflected on the page until the next business day.

The following screens display the update screens.



Figure 59 - Update Contact In formations pages



Figure 60 - Sequence Diagram for updating contact information

UC42: View service holds

Goal: To view service holds on student record


Post-condition: Service holds are displayed


Actors: Student


1. Student selects “Holds” button

2. Quest retrieves holds information


Exceptions: There is no service holds on student record. Then Quest displays a notice

instead of holds information.



Figure 61 - Holds page



3.2 Non-Functional Requirements

3.2.1 Performance

As students will be using all sorts of computers with various internet connections, Quest needs to perform

well on any computer Pentium II (or equivalent) or higher with a 28k modem or higher on a wide range of

web browsers (see functional requirements for officially supported browsers) including working as well

as possible on unsupported browsers.

3.2.2 Usability

Quest must not require any formal training for students. Navigation must be intuitive and picked up in

minutes. A help document must exist but should not need to be consulted by most users or on a regular

basis.

3.2.3 Efficiency

Quest must not consume many computing resources on the client’s computer due to the need for a smooth

performing application even on older computers (see Performance). On the server side, it needs to be

efficient enough so that thousands of students can use Quest at any one time such as during enrolment

periods.

3.2.4 Reliability

Quest needs to aim for 99.5% of scheduled uptime because critical functions such as viewing fees and

enrolling in courses must be done through Quest. Quest going down for a long period of time could cause

major problems for the University (for example, students not being able to view fees may lead to not

paying tuition or University having to send out paper fees to almost 30,000 students).

3.2.5 Security

Quest must be highly secure. It includes student’s grades and personal information (including SIN

number) and accounts must be safe from others. It also now allows credit card and banking information to

be entered in some area. Security must be adequate to ensure that data cannot be modified from outside of



the UI such as directly accessing the marks database, and that user can only enter Quest with their own

account. Additional strict security measures are specified in the Functional Requirements.

3.2.6 Maintainability

As Quest being down for an extended period could cause havoc for the University, modifications and bug

fixes must be able to be made very quickly. Maintainable code is very important for this reason.

3.3 External interface requirements

3.3.1 User interfaces

1. All interaction between the student and Quest is to be through a graphical user interface (GUI).

2. All features are to be accessed through buttons that are to appear in structured menus.

3. The student is to communicate to Quest through the use of a mouse and keyboard.

3.3.2 Hardware interfaces Not applicable.

3.3.3 Software interfaces Browser requirements: The Quest website is best viewed with

• Microsoft Internet Explorer 5.5 or later

• Netscape Navigator 6 or later

• Opera 1.0 or later

• Safari 2.0 or later

• A screen resolution of 1024 x 768 or higher (although lower resolutions will work, it may be an

annoying user experience).

The Web browser must be configured to accept cookies.

3.3.4 Communication interfaces Not applicable.



Appendix A Quest overall functionality



Appendix B Use Cases for Quest

Quest Use Cases



Quest Use Cases (continued)



Appendix C Traceability Document

Category Name Description Related Use Cases

Log in / Log out

Log into Quest To log into Quest UC1 Log out of Quest To log out of Quest UC2 Systems lock out To lock out Quest access UC3

General Open External Link To open an external link UC4 Course catalogue

Course information To view information about a course UC5 Schedule of classes To view the schedule of a course

being offered UC6

Final examination schedule To view the final exam schedule UC7 Academic Record

View grades To view grades for a particular term UC8 Transcripts To view student’s unofficial transcript UC9

To order student’s official transcript UC10 Enrollment Enrollment appointment To view the enrollment appointment

information for a term UC11

Add class To add one or more classes to a course schedule

UC12

Drop/Update Class To drop one or more classes UC13 Swap Class To swap one or more enrolled classes UC14 Seach for classes available for add

To search classes offered for the selected term

UC15

View class schedule To view the class schedule of a term UC16 View weekly schedule To view the weekly schedule UC17

Pre-Enrollment

Add course to pre-enrollment list

To add course to the pre-enrollment list

UC18

Drop course from pre-enrollment list

To drop one or more courses from the pre-enrollment list

UC19

Change priority and preferences for course

To change priority and preferences for course

UC20

View pre-enrolled course selection

To view pre-enrolled course selection for the selected term

UC21

View pre-enrollment results To view pre-enrollment results for the selected term

UC22

View future term course offerings

To view courses offered for the future term

UC23


View suggested courses based on academic plan

To view suggested courses for the future term

UC24

View credits completed according to academic plan checklist

To view credits student completed UC25

View credits needed according to academic plan checklist

To view credits student need based on student’s academic plan

UC26

Distance Change exam centre To select an exam location for DE UC27



Education course View exam schedule To view the exam schedule for DE

course UC28

View course material information

To view the course material information for the selected DE course

UC29

View assignment information

To view the assignment information for the selected DE course

Uc30

Request for proctor To request a proctor for a DE course final examination

UC31

Finances View financial summary for specified term

To view financial summary for a specified term

UC32

View account details for specific term

To view financial details for a specific term

UC33

Email account details sent to e-mail address as PDF

To have Account Details e-mailed as PDF

UC34

Request Accout Details by Mail (hard copy)

To inform Registrar’s Office of student’s order for hard copy of account details and charge the student’s credit card a specified fee.

UC35

Request Additional T2202A forms

To inform Registrar’s Office of student’s order for additional copies of T2202A tuition tax forms and charge the student’s credit card a specified fee.

UC36

Set up Direct Deposit for Money Owed to Student

To store direct deposit information so money owed to student (dental plan refunds are one example) may be directly deposited into student’s bank account rather than sending a cheque by mail.

UC37

Financial Aid View financial aid for calendar year To view financial aid for calendar year UC38

Personal Portfolio

View demographic information

To view a summary of student's personal information

UC39

View contact information To view a summary of student's contact information

UC40

Update contact information To update student's contact information

UC40 UC41

View service holds To view service holds on student record

UC42

university of waterloo quest (student view)dberry/html.documentation/walker/hua.pdf · university...

Documents