TaskManager

Task manager requirments

Developing GPLS style is demonstated by implementing a prototype for a simple task managment system. Here the nature of tasks to be managed is defined and the requirments of the manager application.

Tasks

• A task can have sub task.
• Unless a task is the root it has a parent task.
• Tasks are either in a done or not done state. Task in done state has a boolean property named done with value true. For a task in the not done state the value is false.
• A non leaf task is in the done state if all its sub tasks are else it is in the not done state.
• Only leaf tasks can have their done status changed directly by the end user.
• A task have a name (a property named name of string type).
• A task may have notes; Each note has a title (string property) and optionally some textual content.

Use cases

The following use cases defines what is required by the manager:

1. Creating a task.
2. Changing the name of a task.
3. Changing the done state of a leaf task.
4. Deleting a sub task.
5. Adding a note to a task.
6. Deleting a task’s note.