Requirements

Sitewide Requirements

1. Required: user’s name should be shown on top of sidebar
2. Required: pages the user is allowed to access should be visible on sidebar
3. Required: Login / Logout functionality
4. Required: Department Head user can add and remove users from the department (account creation)
5. Desired: currently selected page should be highlighted (see issue #9)
6. Desired: USC logo in top left corner
7. Aspirational: user’s profile picture is shown by name on sidebar
8. Aspirational: user can pin or sort sidebar items in an order of their choice

Login Page Requirements

1. Required: Enter email address
2. Required: Enter password
3. Required: Login button that leads to main dashboard
4. Desired: “Remember me” login
5. Desired: “Forgot Password” functionality
6. Aspirational: DUO Authentication login (rather than our own login system)

Grants and Publications Page Requirements

1. Required: Connects to backend to pull Grant Information
2. Required: Connects to backend to pull Publication Information
3. Required: Displays Grant Information
4. Required: Displays Publication Information
5. Desired: Functionality to expand Grant Information into a full page
6. Desired: Functionality to expand Publication Information into a full page

Dashboard Page Requirements

1. Required: Show a summary of information for each component (Student Evaluations, Team Member Assessments, Grants and Publications, and Department Analytics)
2. Required: Redirect users to each of these components when they click the expand button
3. Desired: Allow users to customize what information is shown on each card through an edit menu
4. Desired: Allow users to rearrange / resize cards

Account Settings Requirements

1. Required (if we implement our own username/password system): Allow users to change their password
2. Desired: Allow users to edit the name that is displayed on the website
3. Desired: Allow users to change their profile picture

Student Evaluations Page Requirements

1. Required: user can see all classes they have taught
2. Required: users can see the courses separated by year
3. Desired: user can see currently teaching classes
4. Desired: user can see an average of course evals (percentage wise)
5. Desired: user can filter what courses are shown by the year/semester they taught that course

Detailed Course Info Page Requirements

1. Required: users can see an average of evals in each class
2. Required: users can see specific year averages for each class
3. Desired: users can see specific feedback from what students have written in different sections
4. Desired: users can see a chart of how performance has changed over the years

Analytics Page Requirements

1. Required: user must be able to select his and other classes
2. Required: user can see a table populated with his information as it compares to other teachers’
3. Desired: user can see a graph populated with his info as it relates to other teachers’
4. Desired: user can select time frame over which he’d like to view the data
5. Desired: user can few (anonymous) statistics about other teachers teaching his course (mean, std, etc.)

Team Assessments Page Requirements

1. Required: User authority-level based viewership rights (as described in the wiki)
2. Required: connects to backend to pull team member’s names, assessments, further details.
3. Required: displays team member’s names, ratings, assessments links sorted by team member type (as show in design drawings)
4. Required: Expanded view shows available student assessments if user clicks on “View Student Evaluations”
5. Desired: Expansion button that allows full screen view of one sub-category of team members.
6. Desired: sorts the view within each subcategory by a selected metric (for example, avg student grade, or professor avg rating). Aspirational: color coding badges (like green for 90+, yellow for 80+, orange for 70+, red for 60+).

Data Upload Page Requirements

1. Required: Ability to upload course evaluations
2. Required: ability to upload one’s Grants
3. Required: Ability to upload one’s Publications