Quelle anzeigen

Work in progress

Target release	Release name or number
Epic	Users will have role based access to the flecsimo system
Document status
Document owner	Ralf Banning
Designer	Ralf Banning
Developers	Lead developer
QA	Lead tester

Goals

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

#	Title	Use Case	Importance	Notes
UA-1	Add a User	A new users is added to the system	Must 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-2	Manage Users	The Administrator changes user roles, user information or other parameters	Must Have
UA-2	Manage Rights and Roles	The Administrator manages rights and roles in the system	Must Have
UA-2	User Log In	A User log in to the system	Must Have
UA-3	Forgot Password	A User requests to reset his or her password.	Optional	This is optional but very important for the operations.

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

Question	Outcome
Which roles will be needed in detail?	Communicate the decision reached
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?

List the features discussed which are out of scope or might be revisited in a later release.