Project Report (Sprint 2)

Effort Table

Team Member	Roles / Tasks	Time Spent (Hours)
Annabelle Dion	RESTful service class, UnitTesting, Q&A Report	13
Sia Ham	RESTful API, Documentation, Unit Testing, QA Plan, Bug fixing	17
Thomas Jarvis	RESTful service class, UnitTesting, IntegrationTesting, API	18
Norman Kong	RESTful Service Class, Unit Testing, Integration Testing, Bug fixing	15
Catherine Van Gheluwe	API, UnitTesting, Debugging	17

Documentation

• RESTful Service Endpoints
• Software Quality Assurance Plan and Report

Meeting Minutes

Meeting 1 : Thursday, February 25th 5:15 PM

• Agenda

  • Sprint Planning (schedule next meeting)
  • Task Division

• Attendance

  • Everyone was present

• Decisions Made

  1. Sprint Planning

     • Meeting 2: Thursday, March 4th @7:00PM
     • Divide the team into a group of 3 & a group of 2. Each team will work on the RESTful service class and RESTful API for dev2-section 1: "Backend Implementation and Evolution of Persistence Layer".
     • Finish Restful services by Thursday, March 4th, and start unit testing and integration testing (<= to be discussed in the next meeting)
     • Update welcome page, README files

  2. Task Division

     • Documentation will be a rotational task. One person will be assigned documentation on top of their coding task for each sprint.

note that these tasks are not set in stone

Team Member	Roles / Tasks
Annabelle Dion	RESTful service class
Sia Ham	RESTful API
Thomas Jarvis	RESTful service class
Norman Kong	RESTful service class
Catherine Van Gheluwe	RESTful API

Meeting 2 : Thursday, March 4th @7:30PM

• Agenda

  • Sprint Planning & Tasks Updates
  • Sprint 1 feedback

• Attendance

  • Everyone was present

• Decisions Made

  1. Sprint Planning & Tasks Update
     • Meeting 3: Saturday, March 6th @7:30PM
     • Finish RESTFul Service by Saturday, March 6th so that API can be done as soon as possible
     • Once RESTFul is done, start working on unit testing
  2. Sprint 1 feedback
     • Fix model
     • Remove unused import statements
     • Add comments, Javadocs

Meeting 4 : Monday, March 15th @8:30PM

• Agenda

  • Update team on work done and where we are at.
  • Plan next steps to finish Deliverable 2.

• Attendance

  • Everyone was present

• Decisions Made

  1. Tasks Update
     • Norman and Thomas worked on Controller code, basically finished.
  2. Task division *

Team Member	Roles / Tasks
Annabelle Dion	Unit/Integration Testing + Q&A Report
Sia Ham	Unit/Integration Testing + Q&A Report
Thomas Jarvis	Dto + Business Methods
Norman Kong	Dto + Business Methods
Catherine Van Gheluwe	Unit/Integration Testing + Q&A Report

Meeting 4 : Sunday, March 15th @8:30PM

• Agenda

  • Update team on work done so far.
  • Plan next steps to finish deliverable 2.

• Attendance

  • Everyone was present

• Decisions Made

  1. Tasks Update
     • Norman and Thomas basically finished the Controller code (to be finished shortly after the meeting, then pushed).
  2. Task division
     • Cath and Sia will work on Unit testing.
     • Annabelle will work on QA Report.
     • Thomas and Norman will work on debugging.
     • Next meeting: Thursday, March 18th, 7:30 pm.

Team Member	Roles / Tasks
Annabelle Dion	Q&A Report
Sia Ham	Unit/Integration Testing
Thomas Jarvis	General Debugging, documentation
Norman Kong	General Debugging, documentation
Catherine Van Gheluwe	Unit/Integration Testing

Meeting 5 : Thursday, March 18th @8:10PM

• Agenda

  • Assess what work is left to do and divide tasks to finish for the deadline (midnight).

• Attendance

  • Everyone was present

• Notes

  1. Customer unit tests still have to be written.
  2. A few minor fixes are needed to satisfy "implement all use cases as business methods and make them available as RESTful services using Java Spring technology."
     • The code inside the methods editAppointment, editMechanic, editTimeSlot must be moved to the Service.
  3. QA Software Report is almost done.
  4. Integration testing to be done.

Team Member	Roles / Tasks
Annabelle Dion	Q&A Report
Sia Ham	Fixing service method - use case requirement
Thomas Jarvis	Integration Testing
Norman Kong	Integration testing
Catherine Van Gheluwe	Unit tests for Customer