Difference between revisions of "BBB Seneca Integration Use Cases"
(→Calendar) |
|||
Line 46: | Line 46: | ||
Logs out the user | Logs out the user | ||
===Calendar=== | ===Calendar=== | ||
− | * | + | * Students can manage their meeting through the calendar tool, see Calendar Use Case |
− | |||
− | |||
− | |||
==General User== | ==General User== |
Revision as of 13:24, 6 June 2013
Contents
User Specific Use Cases
Super Admin
- All Administrator rights applies
Add Administrator
Administrator
User Management
- Add user
- add usecase
- Ban User
- add usecase
- User Activation
- add usecase
Professor Management
Subject Management
Department Management
- Admin can manually add/remove a user to/from her department.
- add usecase
Professor
Section Management
- Add students to section
- Create Lecture Schedule
- Edit Lecture
- Including check to propagate changes to whole schedule
Calendar Management
- Display Calendar
- Filter Calendar
Meeting Management
- See General User Meeting Use Cases
Student
Logs and have the following available:
Settings
User Settings
User can modify Nickname and set up an alternate email address (only if they are authenticated through Directory Service)
Meeting settings
Activate silent mode, (if activated user will not receive notifications when the user is added to a meeting)
Log out
Logs out the user
Calendar
- Students can manage their meeting through the calendar tool, see Calendar Use Case
General User
Meeting Management
- Create Meeting
- Edit Meeting
- Start Meeting/Lecture
Calendar Management
- Display Calendar
- Filter Calendar
Non-LDAP User
- Change Password
- Reset Password
- Change Email
Meeting Attendance Page
Search Organization Directory Service Users (LDAP)
Search Non-Organization users
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