Difference between revisions of "BBB Seneca Integration Use Cases"
(→Authentication) |
(total change) |
||
Line 1: | Line 1: | ||
− | = | + | =Authentication= |
− | == | + | =General User Page= |
− | + | =Student Page= | |
− | == | + | =Professor Page= |
− | + | =Admin Page= | |
− | + | =Super Admin Page= | |
− | + | =User Settings= | |
− | + | =Manage Professors= | |
− | + | =Manage System Subjects= | |
− | + | =Manage Users= | |
− | + | =System Settings= | |
− | + | =Manage Departments= | |
− | + | =Manage Department= | |
− | + | =Class Settings= | |
− | |||
− | |||
− | |||
− | == | ||
− | |||
− | = | ||
− | |||
− | |||
− | |||
− | |||
− | = | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | = | ||
− | |||
− | |||
− | |||
− | == | ||
− | |||
− | = | ||
− | |||
− | |||
− | |||
− | == | ||
− | |||
− | |||
− | |||
− | |||
− | == | ||
− | |||
− | |||
− | |||
− | = | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=Common Use Cases= | =Common Use Cases= |
Revision as of 14:01, 6 June 2013
Contents
Authentication
General User Page
Student Page
Professor Page
Admin Page
Super Admin Page
User Settings
Manage Professors
Manage System Subjects
Manage Users
System Settings
Manage Departments
Manage Department
Class Settings
Common Use Cases
Authentication
Login
- User logs in to the system through a the login page with a userid and password in two steps:
- Directory Service Authentication
- User is checked against the directory service, if found the user is authenticated and the department of the user is updated in the database.
- Local Authentication
- If the user is not found in the directory service, the user will be checked against the local users table, authenticated and logged in.
- Directory Service Authentication
Calendar
- Meetings can get created by clicking on the empty space on a day which bring the use to the Create meeting use case.
- Display Calendar
- Filter Calendar