Changes

Jump to: navigation, search

BBB Seneca Integration Use Cases

94 bytes added, 14:23, 6 June 2013
no edit summary
=AuthenticationUser Specific Use Cases==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. =Super Admin==
*All Administrator rights applies
===Add Administrator===
==Administrator==
===User Management===
* Add user
*: add usecase
*: 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
*: 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===
* Meetings can get created by clicking on the empty space on a day which bring the use to the Create meeting use case.
* Filter Calendar
==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.

Navigation menu