Difference between revisions of "BBB Seneca Integration Use Cases"

From CDOT Wiki
Jump to: navigation, search
(total change)
Line 1: Line 1:
=User Specific Use Cases=
==Super Admin==
=General User Page=
*All Administrator rights applies
=Student Page=
===Add Administrator===
=Professor Page=
=Admin Page=
=Super Admin Page=
=User Settings=
===User Management===
=Manage Professors=
* Add user
=Manage System Subjects=
*: add usecase
=Manage Users=
* Ban User
=System Settings=
*: add usecase
=Manage Departments=
* User Activation
=Manage Department=
*: add usecase
=Class Settings=
===Professor Management===
===Subject Management===
===Department Management===
* Admin can manually add/remove a user to/from her department.
*: add usecase
===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
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
* 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=
=Common Use Cases=

Revision as of 15:01, 6 June 2013


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



  • User logs in to the system through a the login page with a userid and password in two steps:
    1. 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.
    2. 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.


  • 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