Rough Notes

User makes a task (timestamp, photo group, text)

User can't create a task when offline, but they can view existing ones stored. (View offline, not create offline)

• Tasks can be fulfilled or non-fulfilled

Once fulfilled task can have local, shared, creator access/permission rights.

Resync every login and at set intervals.

Two views for fulfilled tasks:

• Tasks I created and were fulfilled
• Fulfilled Tasks shared with everyone

---

Information Gathered From ECLASS Specification

Actors:

• User
• Server
• Other Users

Actions:

• Define Task
• View Task
• Fulfil Task
  • Fulfil Photo Task
  • Fulfil Audio Task
  • Fulfil Text Task
• Share Task
• Take Photo
• Record Audio (Implied from spec, no formal user story yet)

Use Cases

Use Case 1: Define Task

Basic Flow:

1. User selects option to define a task.
2. System takes user to Task Definition screen.
3. User enters in a description of the task.
4. User enters in the requirement for the task (Photo, Audio or Text)
5. User sets the visibility on the task (Local, Shared)

Notes from Spec:

• Set task to be local (viewable only by creator)

Use Case 2: View Task

Notes from Spec:

• View tasks from other users somehow
• View tasks offline (store tasks in memory)

Use Case 3: Fulfil Task

Includes

• Use Case 5: Take Photo
• Use Case 6: Take Audio

Notes from Spec:

• Take photos and attach multiple photos
• Take a timestamp of the fulfil operation
• Create a report and send back to task creator
• Option to:
  • Store Locally
  • Sent to Central System
  • Sent to Task Creator Only

Use Case 4: Share Task

Notes from Spec:

• Users can share their tasks, allowing all other users to see the task

Use Case 5: Take Photo

Notes from Spec:

• Must be able to take more than 1 photo
• Can retake photos if the photo did not turn out OK
• Photos will be attached to task

Use Case 6: Record Audio

Notes from Spec:

• No user story for this specification yet, however it is written in the problem statement.