Meeting Minutes - CMPUT301F12T06/classproject GitHub Wiki

Meeting Minutes

November 14th, 2012 - Meeting 5 (1PM-2PM)

  • Choose New Use Cases to Implement
  • Updated release planning to add the new use cases
  • Discusses our approach to completing phase 3
  • We have decided that next meeting we will determine our work division

November 7th, 2012 - Meeting 4 (5PM - 7PM)

  • Demoed project to TA
  • Discusses possible improvements and application approach

October 27th, 2012 - Meeting 3 (2PM -3 PM)

  • Decided division of work
  • Discussed android specific implementation details

October 20, 2012 - Meeting 2 (12:30PM - 3:45PM)

  • Went through UI Mockup and Storyboard
  • How to handle data storage
  • MVC of our application
  • Create a UML Class Diagram
  • Went over and organized the priorities of user stories
  • Discussed MVC Model. (Observers are the views, Controllers will be inside of the Views the Task Manager is the Model which will notify the views to update)

October 15, 2012 - Meeting 1

  • How to structure the project. MVC
  • Started development of the requirement specifications
  • A task can be made and it will be automatically uploaded to a central database (there will be no locally stored tasks)
  • How to handle local and centralized data. As a user, I want tasks to be stored so I can view them offline. Tasks should not be able to be created if offline but should be able to view the already stored tasks. (Synchronization every x minutes to detect changes and a button to check).
  • Each user in the server has 2 lists (i.e. Shared tasks fulfilled and user specific fulfilled tasks). When a user shares a task to everyone it will be appended to each users shared list and if they want to post it to the owner then the owner and the person who fulfilled the task will have it appended to their user specific list.
  • List of objects within a task (to check if a task is fulfilled we check whether there is at least 1 object in it); Objects will be called "submissions".
  • Submissions class which contains an Array List of photos, descriptions and audio.
  • Inside the Submissions there is flag that determines its "access"