Skip to content

Sprint 2 Report

RemiENG edited this page Mar 5, 2019 · 8 revisions

Overview

This report includes the meeting minutes and some key design decisions taken by the team.

Februart 12, 2019

  1. In attendance:

    • Remi Carriere
    • Naxin Fang
    • Boyang Ma
    • Angel Ortiz Regules
    • Marie Vu
  2. Minutes:

    • Identified the problems that need to be fixed from the feedbacks of Sprint 1
    • Create a Milestone called "Sprint 1 improvements"
    • Issues that need to be added:
      • Add Spring Data Source URL in travis.yml
      • Add Top Level Class and corresponding associations
      • Add directionality to task document associations
      • Clean database @after test
      • Use case diagram assign external systems as systems, not roles
  3. Key decisions:

    • Add the Top Level Class before next meeting so we can continue the project
  4. Potential date of next meeting:

    • Tuesday, February 19, 2019
    • Friday, February 22, 2019

Februart 19, 2019

  1. In attendance:

    • Remi Carriere
    • Naxin Fang
    • Boyang Ma
    • Angel Ortiz Regules
    • Marie Vu
  2. Minutes:

    • Talked about the use cases and how to implement the business methods
    • Determined the RESTful service endpoints
    • We need to create DTO classes
    • Do API for service endpoints
  3. Key decisions:

    • Create DTO classes as soon as possible
    • Need to implement the REST controllers before next meeting
    • API for service endpoints needs to be done so that other teams can use them
  4. Potential date of next meeting:

    • Monday, February 25, 2019
    • Tuesday, February 26, 2019

February 26, 2019

  1. In attendance:

    • Remi Carriere
    • Naxin Fang
    • Boyang Ma
    • Angel Ortiz Regules
    • Marie Vu
  2. Minutes:

    • Attended TA hours
    • Need to modify the service class to follow the requirements established by the use-cases.
      • Specifically creating student enrollments now triggers the creation of a number of tasks which are attached to the new enrollment.
    • Need to complete the rest controller
    • Add validation for classes
    • Need more comprehensive testing
    • Finish the CooperatorService class coverage
  3. Key decisions:

    • We have decided to not use DTOs. The explanation can be found in the Design decisions page.
  4. Potential date of next meeting:

    • Friday, March 1st, 2019

February 26, 2019

  1. In attendance:

    • Remi Carriere
    • Naxin Fang
    • Boyang Ma
    • Angel Ortiz Regules
    • Marie Vu
  2. Minutes:

    • Finish integration tests
    • Need to complete the deliverable 2 wiki page
    • Finish mockito tests
    • Need to do integration tests for query services developed by other teams