Release Planning - CMPUT301F12T01/classproject GitHub Wiki

Release Plan

By October 22, 2012, we will turn all the User Stories into Use Cases.

By November 5, 2012, we will implement the following User Stories: 1, 3, 4, 7, 8, 10, 15. We will also have completed/revised the Use Cases for the remaining User Stories: 2, 5, 6, 9, 11, 12, 13, 14. We would like to focus on creating and fulfilling Tasks locally first before we work with the server. In terms of completing a Task, we will focus on simpler Tasks, such as requiring text, before working on Tasks that require photos and/or audio.

By December 3, 2012, we will implement the remaining User Stories: 2, 5, 6, 9, 11, 12, 13, 14. These contain requirements such as sharing Tasks with other Users as well as being able to fulfill Tasks through photos (and maybe audio).

In addition, we will create Use Cases for the User Stories 16, 18, 19, 21, 22. and implement 2-3 of them. In particular, we plan to implement the User Stories that involve obtaining a User's reports on their device (phone) and being able to publish the reports of a task to the server for everyone to see. (17, 20)

We would also hope to squeeze in the ability to edit your own task.

For Future Releases:

We would like to have the option to allow a user who is fulfilling a task to have the report go just back to the original creator of the task, rather than having the report being sent to the server for all users to see.

In addition, we would like to be giving the user the option to attach multiple photos when fulfilling a task. We would aim to expand the types of media users can request such as audio and video clips. In addition, we would add the ability to tag a task such that when users can like or favourite a task we can suggest tasks that are relevant so the User can find similar tasks.

User Story Numbering

Note that some of the User Stories have been combined into similar Use Cases, which can be viewed here.

1. As a user, I want to define tasks.
2. As a user, I want to share tasks.
3. As a user, I want to fulfill tasks.
4. As a user, I want some tasks to requires photos.
5. As a user fulfilling a task I want to take photos and attach the photos to the task.
6. As a user who defines a task I want to receive the results of users fulfilling a task.
7. As a user I want to be able to fulfill my own tasks.
8. As a user fulfilling a task I want my actions time stamped.
9. As a user, I want tasks to be stored so I can view them offline.
10. As a user, I want to fulfill tasks that require text by entering text.
11. As a user fulfilling a task, I want to be able to attach multiple photos.
12. As a user, I should be able to retake photos I am taking, if I fail to take the photo I want to correct, so that I don't have erroneous photos.
13. As a user I should be able to get tasks from other users somehow.
14. As a user fulfilling a task I should be able to send the fulfilled report back to the task writing user somehow.
15. As a user creating a task I want some tasks to be local only to myself.
16. As a user I want to ensure that others cannot modify my tasks. Only I should be able to modify them (security/authentication).
17. As a user I want to specify different repositories where I can get tasks from.
18. As a user I want to get my task responses on my phone but not in my email. (One could use the webservice, or a seperate response webservice).
19. As a user I want to specify tasks that include audio or video components.
20. As a user browsing tasks, I want to manage my favorites.
21. As a user I want to see random tasks.
22. As a user I want to publish the results of a task somehow.
23. As a user I want to email tasks to other users and import tasks emailed to me.
24. As a user, I want to optionally get tasks that are from my particular interest only (containing tags or keywords)
25. As a user, I want to vote (like) for tasks that I consider particularly relevant.
26. As a user I want to see the popularity of a task (votes/likes).