Use Case Name Actors Description Pre-condition Post-condition Basic flow Alternate flow 1. 1.

Use Case Name Actors Description Pre-condition Post-condition Basic flow

Login (Authentication and Authorisation) Remote server, User, Staff, Admin Login is used to analyse the authenticity of the user and the priveliges the user gets. NA User is authentic and privilege is given. User is not authentic and is restricted to login.

1. User sends request to remote server for the login page which asks for username and password. 2. User enters username and password and sends request to remote server for authentication. 3. Remote server compares and checks if the user is registered in it's database. 4. If user is registered, the user is deemed authentic and is allowed to log into the service with the privileges of the user. 1. In step 4 if the user is not found in the database, user is redirected to the login page.

Alternate flow

Use Case Name Actors Description

Privileges User, remote server There are three privileges: Admin Staff User Also admin has a number of fine grained privileges that it can assign to staff and users. Internet connection, Login Each actor namely Admin, Staff and User see their respective Dashboard. 1. Admin logs in with it's username and password. 2. If authentic, sees the admin dashboard. In step 1:

Pre-condition Post-condition Basic flow Alternate flow 1

1. Staff logs in with it's username and password. 2. If authentic, sees the staff dashboard. Alternate flow 2 In step 1: 1. User logs in with it's username and password. 2. If authentic, sees the user dashboard. In step 1: If authentication fails, the Admin/Staff/User is redirected to login screen.

Exception

Use Case Name Actors Description Pre-condition Post-condition Basic flow

Add Project Admin, Staff The actor can create a new project. Actor is logged in. A new project is created. 1. Actor clicks on Create project. 2. Actor is presented with a details about the project to fill in. Like project name, company name, logo for the project, description about the project and tags for searching. 3. A new project is created. NA

Alternate flow

Use Case Name Actors Description Pre-condition Post-condition Basic flow

Delete project Admin, Staff The actor deletes a project. Actors must be logged in. 1. Project is deleted. 2. Only an actor with necessary privileges can delete a project. 1. 2. 3. 4. Actor clicks on the Delete project link. A popup window asks for confirmation. Actor clicks Yes. Project is deleted.

Alternate flow

1. In step 3, actor clicks No. 2. In step 4, project is not deleted.

Use Case Name Actors Description Pre-condition

Edit project. Admin, Staff An actor with the necessary privileges can edit a project. 1. The project already exists.

2. Actor with necessary privileges can edit the project. Post-condition Basic flow Alternate flow Project is open and available for editing. 1. Actor clicks on Edit project. 2. Actor edits project. NA.

Use Case Name Actors Description Pre-condition

Add story. Admin, Staff A story is added to an existing project on which the case study is being conducted. 1. Actors are logged in. 2. The project must exist already. 3. Only the actor with necessary privileges can add story. A story is Added. 1. Actor clicks on Add story. 2. Popup window asks about adding a new story in specified format. 3. A file is selected from the computer and Upload is clicked. 4. Story is uploaded and converted in editing format on the app. 1. In step 3, the actor clicks on Cancel and uploading is canceled.

Post-condition Basic flow

Alternate flow

Use Case Name Actors Description Pre-condition

Delete story Admin, Staff An existing story is deleted. 1. Actors are logged in. 2. The project must exist already. 3. Only the actor with necessary privileges can add story. A story is deleted. 1. 2. 3. 4. Actor clicks on Delete story. Popup window asks to confirm the action. Actor clicks Yes. Story is deleted.

Post-condition Basic flow

Alternate flow

1. In step 3, the actor clicks on No. 2. In step 4, project is not deleted.

Use Case Name Actors Description Pre-condition

View story Admin, Staff An existing story is viewed. 1. Actors are logged in.

2. The project must exist already. 3. The story must already exist. Post-condition Basic flow Alternate flow A story is viewed. 1. Actor clicks on View story. 2. Story is viewed in the viewer.

Use Case Name Actors Description Pre-condition

Tag story Admin, Staff Tagging is done on existing story. 1. Actors are logged in. 2. The project must exist already. 3. The story must already exist. A story is tagged. 1. 2. 3. 4. Actor clicks on Decision Point Tag. Decision Point Tag is selected. Actor clicks over the story to tag a decision point. Actor writes on the tag about the decision point.

Post-condition Basic flow

Alternate flow 1

1. In step 1, actor clicks on Actor Tag. 2. In step 2, Actor Tag is selected. 3. In step 3, actor clicks over the story to tag an Actor (name) on the story. 1. 2. 3. 4. In step 1, actor clicks on Reference Question Tag or Note Tag. In step 2, Note Tag is selected. In step 3, actor clicks over the story to tag a Note. In step 4, actor writes a question or references it might like to add to the tag.

Alternate flow 2

Use Case Name Actors Description Pre-condition

Delete tag. Admin, Staff Tagging is done on existing story. 1. 2. 3. 4. Actors are logged in. The project must exist already. The story must already exist. The actor must have necessary privileges to delete a tag (author can delete any tag, collaborator can only delete the tags they have set.

Post-condition Basic flow

A tag on a story is removed. 1. Actor clicks on Cancel icon on tag description. 2. Popup window ask to confirm deletion. 3. Actor clicks on Yes.

4. Tag is removed. Alternate flow 1. In step 3, actor clicks on No. 2. In step 4, tag is not deleted.

Use Case Name Actors Description Pre-condition

Add collaborator. Author (admin, staff) Author chooses its collaborators. 1. Actors are logged in. 2. The project must exist already. 3. Actor must have either created a new project or is editing an existing project. A new collaborator is added to the project. 1. 2. 3. 4. 5. Actor clicks on Add Collaborator. Popup window asks for name of new collaborators. Actor enters new collaborator names. Actor clicks on Share. Collaborators are intimated with a request in their dashboard.

Post-condition Basic flow

Alternate flow

1. In step 3, actor clicks on Cancel. 2. In step 4, adding is cancelled.

Use Case Name Actors Description Pre-condition

Delete (remove) collaborator. Author (admin, staff) Author deletes a collaborator. 1. Actors are logged in. 2. The project must exist already. 3. Actor must have either created a new project or is editing an existing project. 4. There must at least be one collaborator. A collaborator is deleted. 1. 2. 3. 4. Actor clicks on Remove Collaborator. Popup window asks for confirmation of action. Actor clicks on Yes. Collaborator is removed.

Post-condition Basic flow

Alternate flow

3. In step 3, actor clicks on No. 4. In step 4, collaborator is not removed.

Use Case Name Actors Description

Preview project. Author, collaborator. The actors can view the whole project.

Pre-condition

1. Actors are logged in. 2. The project must exist already. 3. Actor must have either created a new project or is editing an existing project. 4. A story must have already be added to the project. The project is previewed. 1. Actor clicks on Preview Project. 2. The whole project is viewed on how it would seem finally.

Post-condition Basic flow Alternate flow

Use Case Name Actors Description Pre-condition

Add Questions. Author (admin, staff), collaborator. Actor adds a question for Users to solve. 1. Actors are logged in. 2. The project must exist already. 3. Actor must have either created a new project or is editing an existing project. 4. A story must have already be added to the project. A new collaborator is added to the project. 1. 2. 3. 4. Actor clicks on Add Question. A popup comes up asking to add a question. User enters the question and clicks Add. A new question is added.

Post-condition Basic flow

Alternate flow

1. In step 3, actor clicks on Cancel. 2. In step 4, adding question is cancelled.

Use Case Name Actors Description Pre-condition

Delete Questions. Author (admin, staff), collaborator. Actor adds a question for Users to solve. 1. Actors are logged in. 2. The project must exist already. 3. Actor must have either created a new project or is editing an existing project. 4. A story must have already be added to the project. 5. The question to be deleted must already exist. 6. Actor must have required privilege. A question is deleted. 1. 2. 3. 4. Actor clicks on Delete Question. A popup comes up asking to confirm action. Actor clicks on Yes. Question is deleted.

Post-condition Basic flow

Alternate flow

1. In step 3, actor clicks on Cancel. 2. In step 4, deleting question is cancelled.

Use Case Name Actors Description Pre-condition

Edit Questions. Author (admin, staff), collaborator. Actor edits a question for Users to solve. 1. Actors are logged in. 2. The project must exist already. 3. Actor must have either created a new project or is editing an existing project. 4. A story must have already be added to the project. 5. The question to be edited must already exist. 6. Actor must have required privilege. A question is updated. 1. Actor clicks on Edit Question. 2. A popup comes up with the existing question asking to edit the question. 3. User edits the question and clicks Update. 4. The question is updated. 1. In step 3, actor clicks on Cancel. 2. In step 4, updating question is cancelled.

Post-condition Basic flow

Alternate flow

Use Case Name Actors Description Pre-condition

Add Question key. Author (admin, staff), collaborator. Actor adds a key to a question. 1. Actors are logged in. 2. The project must exist already. 3. Actor must have either created a new project or is editing an existing project. 4. A story must have already be added to the project. 5. A question must exist. 6. Actor must have required privilege. A question key is added. 1. 2. 3. 4. Actor clicks on Add Question Key. A popup comes up asking to add the question key. User adds the key and clicks Add. The question key is added.

Post-condition Basic flow

Alternate flow

1. In step 3, actor clicks on Cancel. 2. In step 4, action is cancelled.

Use Case Name Actors Description Pre-condition

Delete Question key. Author (admin, staff), collaborator. Actor deletes a key to a question. 1. Actors are logged in. 2. The project must exist already. 3. Actor must have either created a new project or is editing an existing project. 4. A story must have already be added to the project. 5. A question must exist. 6. A question key must exist. 7. Actor must have required privilege. A question key is deleted. 1. Actor clicks on Delete Question Key. 2. A popup comes up with the existing question asking to delete the question key. 3. User adds the key and clicks Yes. 4. The question key is deleted. 1. In step 3, actor clicks on Cancel. 2. In step 4, action is cancelled.

Post-condition Basic flow

Alternate flow

Use Case Name Actors Description Pre-condition

Edit Question key. Author (admin, staff), collaborator. Actor adds a key to a question. 7. Actors are logged in. 8. The project must exist already. 9. Actor must have either created a new project or is editing an existing project. 10. A story must have already be added to the project. 11. A question must exist. 12. A question key must exist. 13. Actor must have required privilege. A question key is edited. 1. Actor clicks on Edit Question Key. 2. A popup comes up with the existing question key asking to edit the question key. 3. User adds the key and clicks Update. 4. The question key is updated. 1. In step 3, actor clicks on Cancel. 2. In step 4, action is cancelled.

Post-condition Basic flow

Alternate flow

Use Case Name Actors

Add Event. Author (admin, staff), collaborator.

Description Pre-condition

Actor adds an event to the project. 1. Actors are logged in. 2. The project must exist already. 3. Actor must have either created a new project or is editing an existing project. 4. A story must have already be added to the project. 5. Actor must have required privilege. An event is added. 1. Actor clicks on Add Event. 2. A popup comes up with the existing question asking to add event name, description of the event, decision points and static files (images, audio, video). 3. User adds the key and clicks Add. 4. An event is added. 1. In step 3, actor clicks on Cancel. 2. In step 4, action is cancelled.

Post-condition Basic flow

Alternate flow