|
|
# Use Case 1 - Create new task
|
|
|
|
|
|
|
|
|
| Name | Create new task |
|
|
|
| ------ | ------ |
|
|
|
| Actor | Local user|
|
|
|
| Pre-conditions| Local user successfully syncs with the database|
|
|
|
| | A category exists |
|
|
|
| Post-conditions | A new task has been created |
|
|
|
| Basic path | 1. Local user clicks “New Task” button |
|
|
|
| | 2. Local user fills inn necessary information |
|
|
|
| | 3. Local user presses “Save” button |
|
|
|
| Exception | 2.1 Local user doesn’t fill inn task name |
|
|
|
| | 2.2 Local user doesn’t fill inn start- and end-date |
|
|
|
| | 2.3 Local user doesn’t choose category |
|
|
|
| Additional information | The following has to be chosen to create a task: |
|
|
|
| | - Task name |
|
|
|
| | - Start- and end-date |
|
|
|
| | - Category |
|
|
|
|
|
|
<br />
|
|
|
|
|
|
|
|
|
# Use Case 2 - Edit task
|
|
|
|
|
|
| Name | Edit a task |
|
|
|
| ------ | ------ |
|
|
|
| Actor | Local user|
|
|
|
| Pre-conditions| Local user successfully syncs with the database|
|
|
|
| | Task exists |
|
|
|
| Post-conditions | An active task has been edited |
|
|
|
| Basic path | 1. Local user clicks on a specific task to see it’s details |
|
|
|
| | 2. Local user clicks on the “Edit” button |
|
|
|
| | 3. Local user makes the changes |
|
|
|
| | 4. Local user clicks the “Save” button |
|
|
|
| Exception | 3.1 The task name has been changed to blank |
|
|
|
| | 3.2 The dates has been changed to blank |
|
|
|
| Additional information | |
|
|
|
|
|
|
<br />
|
|
|
|
|
|
|
|
|
# Use Case 3 - Complete task
|
|
|
|
|
|
| Name | Complete a task |
|
|
|
| ------ | ------ |
|
|
|
| Actor | Local user |
|
|
|
| Pre-conditions| Local user successfully syncs with the database |
|
|
|
| | Task exists |
|
|
|
| Post-conditions | An active task has changed status to completed |
|
|
|
| Basic path | 1. Clicks on the “Complete” button of the task |
|
|
|
| Alternative path | 1. Clicks on the task to see the details |
|
|
|
| | 2. Clicks on “Complete” button |
|
|
|
| Exception | |
|
|
|
| Additional information | A completed task can not be reactivated |
|
|
|
|
|
|
<br />
|
|
|
|
|
|
|
|
|
# Use Case 3 - Delete completed task
|
|
|
|
|
|
| Name | Delete a completed task |
|
|
|
| ------ | ------ |
|
|
|
| Actor | Local user |
|
|
|
| Pre-conditions| Local user successfully syncs with the database |
|
|
|
| | Task has been completed |
|
|
|
| Post-conditions | A completed task has been deleted |
|
|
|
| Basic path | 1. Navigate to the “Completed tasks” page |
|
|
|
| | 2. Clicks on the “Delete task” button for a specific task |
|
|
|
| Alternative path | 1. Click on “Completed Tasks” at the navbar |
|
|
|
| | 2. Click on a specific task to see the details |
|
|
|
| | 3. Click on the “delete” button |
|
|
|
| Exception | |
|
|
|
| Additional information | |
|
|
|
|
|
|
<br />
|
|
|
|
|
|
|
|
|
# Use Case 4 - Delete task
|
|
|
|
|
|
| Name | Delete a task |
|
|
|
| ------ | ------ |
|
|
|
| Actor | Local user |
|
|
|
| Pre-conditions| Local user successfully syncs with the database |
|
|
|
| | Task exists |
|
|
|
| Post-conditions | An active task has been deleted |
|
|
|
| Basic path | 1. Clicks on the “delete” button of a specific task |
|
|
|
| Alternative path | 1. Clicks on a specific task to see the details |
|
|
|
| | 2. Clicks on the “delete” button |
|
|
|
| Exception | |
|
|
|
| Additional information | |
|
|
|
|
|
|
<br />
|
|
|
|
|
|
|
|
|
# Use Case 5 - Create new category
|
|
|
|
|
|
| Name | Create a new category |
|
|
|
| ------ | ------ |
|
|
|
| Actor | Local user |
|
|
|
| Pre-conditions| Local user successfully syncs with the database |
|
|
|
| | Category exists |
|
|
|
| Post-conditions | A new category has been created |
|
|
|
| Basic path | 1. Navigate to the Category page |
|
|
|
| | 2. Click the “New category” button |
|
|
|
| | 3. Fill in information |
|
|
|
| | 4. Click the “Save” button |
|
|
|
| Exception | 3.1 The category name can not be blank |
|
|
|
| | |
|
|
|
| Additional information | |
|
|
|
|
|
|
<br />
|
|
|
|
|
|
|
|
|
# Use Case 6 - Edit category
|
|
|
|
|
|
| Name | Edit a category |
|
|
|
| ------ | ------ |
|
|
|
| Actor | Local user |
|
|
|
| Pre-conditions| Local user successfully syncs with the database |
|
|
|
| | Category exists |
|
|
|
| Post-conditions | A category has been edited |
|
|
|
| Basic path | 1. Navigate to the Category page |
|
|
|
| | 2. Click on a specific category to see the details |
|
|
|
| | 3. Click the “Edit” button |
|
|
|
| | 4. Make changes |
|
|
|
| | 5. Click on the “Save” button |
|
|
|
| Exception | 4.1 The category name can not be blank |
|
|
|
| | 4.1 The category name can not be blank |
|
|
|
| Additional information | |
|
|
|
|
|
|
<br />
|
|
|
|
|
|
|
|
|
# Use Case 7 - Delete category
|
|
|
|
|
|
| Name | Delete a category |
|
|
|
| ------ | ------ |
|
|
|
| Actor | Local user |
|
|
|
| Pre-conditions| Local user successfully syncs with the database |
|
|
|
| | Category exists |
|
|
|
| Post-conditions | A category has been deleted |
|
|
|
| Basic path | 1. Navigate to the Category page |
|
|
|
| | 2. Click on the “delete” button |
|
|
|
| Alternative path | 1. Navigate to the Category page |
|
|
|
| | 2. Click on a specific category to see the details |
|
|
|
| | 3. Click the “Delete” button |
|
|
|
| Exception | |
|
|
|
| Additional information | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|