Thursday, March 28, 2013

Meeting 3/28/13

Status Report for Week #4-2

03/28/13

Tasks accomplished

  1. Finished the Cognitive Walk through activity in class as a team.
  2. Created a context diagram and a class diagram for the model portion of the design.

Tasks In Progress

  1. Continuing to work on the design document.
    1. Planned out the class relationships for the view/controllers.
    2. Split up responsibility for initial creation of each view for the prototype due with the design document.

Tasks Planned For Next Week

  1. Finalize the Design Document and prototype.
    1. Emma is doing the view/controllers diagram
    2. Each team member has 1 to 3 screens to have complete before Monday's meeting
    3. Monday's meeting we will wire up the views to work for the prototype and take screenshots to put into the document.

Issues

  1. None.

Metrics

(Times below are since the last update unless otherwise noted.)
  1. Effort expended on project for each person and the total for the team for that week and a running total.
  2. Christoffer Rosen: 1.5 Hours in team meeting
  3. Emma Nelson: 1.5 Hours in team meeting, 1 hour playing with SenchaTouch
  4. Sam Lucidi: 1.5 Hours in team meeting
  5. Mustafa All-Sahihi: 1.5 Hours in team meeting
  6. Ben Hare: 1.5 Hours in team meeting
  7. Total: 64 Hours spent in total by all team members

Tuesday, March 26, 2013

Meeting 3/26/13

Status Report for Week 4-1

03/26/13

Tasks accomplished

  1. Complete the physical design for the in-class activity that is due for Thursday's class as a team in the meeting.

Tasks In Progress

  1. The Design document is in progress. We've established some basic information about the technologies we are going to use and how they will interact.
  2. Chris has been playing with SenchaTouch and has developed a log-in screen for us to use as a part of the prototype and the final product.

Tasks Planned For Next Week

  1. Finish the design document and the prototype before the deadline.

Issues

  1. None

Metrics

(Times below are since the last update unless otherwise noted.)
  1. Effort expended on project for each person and the total for the team for that week and a running total.
  2. Christoffer Rosen: 1.5 Hours in the meeting, 1.5 Hours working with SenchaTouch
  3. Emma Nelson: 1.5 Hours in the meeting
  4. Sam Lucidi: 1.5 Hours in the meeting
  5. Mustafa All-Sahihi: 1.5 Hours in the meeting
  6. Ben Hare: 1.5 Hours in the meeting
  7. Total: 55.5 Hours total by all team members.

Friday, March 22, 2013

Meeting 3/21/13

Status Report for Week 3-2

03/21/13

Tasks accomplished

  1. Identified nouns and discussed how the object model will look for the system.
All team members participated in both tasks. Everything was done during the team meeting.

Tasks In Progress

  1. Started work on the Design Document.
    • We want to complete the design in the next week. This will give us about a week to pull together a prototype before the due date of April 3.
All team members participated in both tasks. Everything was done during the team meeting.

Tasks Planned For Next Week

  1. Continue hammering out the design details during the meetings.
  2. Divide up the work for diagramming all our design decisions to be put into the document.
  3. Have at least a working rough draft by Thursday, March 28 so all it needs is some polish before turning it in (e.g. formatting, proofing, etc).

Issues

  1. We need to figure out an easy way to conference call Sam into our meetings. Every time we fight with the camera and speaker and Google+ for about 30 minutes before he can connect and we can start our meeting for real.

Metrics

(Times below are since the last update unless otherwise noted.)
  1. Effort expended on project for each person and the total for the team for that week and a running total.
  2. Christoffer Rosen: 1 Hour 30 Minutes in team meeting
  3. Emma Nelson: 1 Hour 30 Minutes in team meeting
  4. Sam Lucidi: 1 Hour 30 Minutes in team meeting
  5. Mustafa All-Sahihi: 1 Hour 30 Minutes in team meeting
  6. Ben Hare: 1 Hour 30 Minutes in team meeting
  7. Total: 42 Hours for all team members combined

Meeting 3/19/13

Status Report for Week #3-1

03/19/13

Tasks accomplished

  1. Finished SRS in the meeting as a team. Sam did the mock-ups which we then worked together to revise.
  2. In-Class activity for 3-1 was completed by Sam, Chris, and Ben before the meeting.

Tasks In Progress

  1. None

Tasks Planned For Next Meeting

  1. Start on the Design Document.

Issues

  1. None

Metrics

(Times below are since the last update unless otherwise noted.)
  1. Effort expended on project for each person and the total for the team for that week and a running total.
  2. Christoffer Rosen: 1 Hour 30 Minutes in meeting
  3. Emma Nelson: 1 Hour 30 Minutes in meeting, 15 minutes writing blog posts
  4. Sam Lucidi: 1 Hour 30 Minutes in meeting
  5. Mustafa All-Sahihi: 1 Hour 30 Minutes in meeting
  6. Ben Hare: 1 Hour 30 Minutes in meeting
  7. Total: 34.5 Hours by all team members combined

Thursday, March 14, 2013

Meeting 3/14/13

Status Report for Week #2-2

03/14/13

Tasks accomplished

  1. Completed the in-class activity from Wednesday's class. Emma did the first two sections before the meeting on Wednesday. Sam finished the Use Case diagram during the meeting with input from all team members.
  2. Completed the User Profiles and System Features sections of the SRS. All team members contributed during the meeting.

Tasks In Progress

  1. Started on the task analysis section of the SRS. Each member is responsible for completing one HTA. Should take about 30 minutes to complete the verbal section needed for the SRS at most.

Tasks Planned For Next Week

  1. Finish SRS Document before deadline of March 20th. All team members are responsible and we should finish during our next meeting.
  2. HTA Assignments (to be used in the task analysis section of the SRS). Each member is responsible for completing their own individual assignment. Four of the five will be chosen to be a Feature listed in the task analysis.

Issues

  1. None thus far.

Metrics

(Times below are since the last update unless otherwise noted.)
  1. Effort expended on project for each person and the total for the team for that week and a running total.
  2. Christoffer Rosen: 1 Hour, 30 Minutes in meeting. 15 Minutes on the context diagram for the class activity (part 1).
  3. Emma Nelson: 1 Hour, 30 Minutes in meeting. 15 Minutes working on the class activity before the meeting. 45 Minutes working on blog - writing posts, fixing format, and editing the template.
  4. Sam Lucidi: 1 Hour, 30 Minutes in meeting.
  5. Mustafa All-Sahihi: 1 Hour, 30 Minutes in meeting.
  6. Ben Hare: 1 Hour, 30 Minutes in meeting.
  7. Total: 26.75 Hours by all team members combined.

Tuesday, March 12, 2013

Meeting 3/12/13

Status Report for Week #2-1

3/12/13

Tasks accomplished

  1. Finished the first in-class activity and submitted the document. 
  2. Continued working on the SRS document and finished 1 of the user profiles.
     The whole team worked together in a team room, aside from Sam who teleconferenced in from home for an hour and a half.

Tasks In Progress

  1. The SRS Document - Everyone is responsible for its completion by the deadline (3/20)
    • User Profiles Section

Tasks Planned For Next Meeting

  1. Finish any outstanding class activity work - all are responsible, roughly 1 hour (if needed)
  2. Continue working on the SRS - Everyone is responsible for its completion by the deadline (3/20)
    • Feature Set
    • Non-functional Requirements
    • Prototype

Issues 

  1. Outstanding issues:
    1. Technology stack research and decision 
  2. No resolved issues

Metrics

(Times below are for time spent since last update unless otherwise noted.)
  1. Christoffer Rosen: 1 Hour, 30 Minutes
  2. Emma Nelson: 1 Hour, 30 Minutes
  3. Sam Lucidi: 1 Hour, 30 Minutes
  4. Mustafa All-Salihi: 1 Hour, 30 Minutes
  5. Ben Hare: 1 Hour, 30 Minutes
  6. Total: 18 Hours spent total by all team members. We spent 1 Hour and 30 minutes in a team meeting finishing the in-class activity from Monday and working on the SRS. This comes to 4.5 hours per member.

Sunday, March 10, 2013

Meeting 3/7/2013

Status Report for Week #1

3/7/2013

Tasks accomplished

  1. Project has been selected and approved by professor.

Tasks In Progress

  1. Started on SRS document and on hammering out the details of our project.
  2. The whole team is responsible for finishing the SRS before it is due during week 3.

Tasks Planned For Next Week

  1. Continue to work on the SRS and discuss specific technologies/libraries to be used in implementation.
  2. The whole team is responsible for finishing the SRS before it is due during week 3. We are also each responsible for looking into the suggested options (particularly if we were the one to propose it).

Issues 

  1. No outstanding issues.
  2. No prior issues that needed resolving.

Metrics

(Times below are for time spent since last update unless otherwise noted.)
  1. Christoffer Rosen: 1 Hour, 30 Minutes
  2. Emma Nelson: 1 Hour, 30 Minutes
  3. Sam Lucidi: 1 Hour, 30 Minutes
  4. Mustafa All-Salihi: 1 Hour, 30 Minutes
  5. Ben Hare: 1 Hour, 30 Minutes
  6. Total: 15 Hours spent total by all team members. We spent 1 Hour and 30 minutes in a team meeting starting on the SRS and talking through the details of program flow and what technologies we want to build the project on.

Tuesday, March 5, 2013

Team Planning Meeting

Status Report for Week #1

3/5/2013

Tasks accomplished

  1. Came up with project proposals.
  2. Ranked all project proposals and submitted our top three.

Tasks In Progress

  1. None at the moment

Tasks Planned For Next Week

  1. Start on Project Deliverables

Issues

  1. None

Metrics

  1. Christoffer Rosen: 1 Hour, 30 Minutes
  2. Emma Nelson: 1 Hour, 30 Minutes
  3. Sam Lucidi: 1 Hour, 30 Minutes
  4. Mustafa All-Salihi: 1 Hour, 30 minutes
  5. Ben Hare: 1 Hour, 30 minutes
  6. Total: 7.5 Hours spent by all team members. Each member spent 15 minutes individually thinking of project proposals and we spent 1 Hour and 15 minutes in a team meeting going through the ideas and deciding the top three proposals.