Work in progress

Target release
EpicUsers will have role based access to the flecsimo system
Document status
DRAFT
Document owner

Ralf Banning

Designer

Ralf Banning

Developers
QA

Goals

  • Controlled access to the flecsimo system.
  • Easy management of student groups (per semester / course / location).

Background and strategic fit

Ssee Why flecsimo?

Assumptions

  • The system has to distinguish roles at least for technical administrators, lecturers and participants.

Requirements (Use Cases)

#TitleUse CaseImportanceNotes
UA-1Add a UserA new users is added to the systemMust Have
  • This is an abstract use case which may have several instantiations, e.g. for self-registration or manual setup by an adminsitrator
  • For the first release it is sufficient to have a manual process
UA-2Manage UsersThe Administrator changes user roles, user information or other parametersMust Have
UA-2Manage Rights and RolesThe Administrator manages rights and roles in the systemMust Have
UA-2User Log InA User log in to the systemMust Have
UA-3Forgot PasswordA User requests to reset his or her password.OptionalThis is optional but very important for the operations.

User interaction and design

Use Case: Log in

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome
Which roles will be needed in detail?

Which rights have to be defined - how they will be implemented?


Do we need a role for each actors specification in the use case model?

Not Doing