Sprint 1 Report

Overview

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

In attendance:
- Remi Carriere
- Naxin Fang
- Boyang Ma
- Angel Ortiz Regules
- Marie Vu
Minutes:
- Identified the functional and non-functional requirements of the student viewpoint
- Determined potential use cases for the student viewpoint
- Created a list of problems about the project that needed to be solved
Problems needed to be solved:
- How to address the problematic student properly
- what extra features should we put in the use case diagram
- Should we separate the use case diagram into different categories
Tasks needed to be completed before next meeting:
- Finalize the function and non-function requirements
- Make the first draft of the use case diagram(s)
- Start looking into how to use UML Lab to create the class diagram and generate the code
- Start looking into the general structure of the persistence layer
Potential date of next meeting:
- Tuesday, January 29, 2019
- Wednesday, January 30, 2019

In attendance:
- Remi Carriere
- Naxin Fang
- Boyang Ma
- Angel Ortiz Regules
- Marie Vu
Minutes:
- Modified the functional and non-functional requirements
- Edit the Use case diagram
- Made the first draft of the domain model
Problems needed to be solved:
- How should we address the use case that we need from an external system in the use case diagram
- What is the most effective way to separate the use case diagram
- what is the proper way to construct the relationship between student and course offering
Tasks needed to be completed before next meeting:
- Finalize domain model
- Complete the main and alternative flows for the five most important use cases
- Complete UML class diagram and generate the code
- Complete Persistence layer
- Start building test unit
- Create sprint 1 report wiki page
Potential date of next meeting:
- Wednesday, February 06, 2019
- Thursday, February 07, 2019

In attendance:
- Remi Carriere
- Naxin Fang
- Boyang Ma
- Angel Ortiz Regules
- Marie Vu
Minutes:
- Finalized use case diagram
- Continued to work on the test unit
Problems needed to be solved:
- What is the most effect way to create tests for objects that have composition relationships
- The integration on Travis CI is still failing
Tasks needed to be completed before next meeting:
- Complete unit test suite
- Continuous integration
- Complete deliverable 1 documentation wiki page
- Complete sprint 1 report wiki page
- Update README
- Convert persistence layer to CRUD repositories for each class
- Create tests to persist objects with null attributes
Potential date of next meeting:
- Friday, February 08, 2019

In attendance:
- Remi Carriere
- Naxin Fang
- Boyang Ma
- Angel Ortiz Regules
- Marie Vu
Minutes:
- Finalized CRUD repositories
- All read/write tests complete
- Travis CI integration fully functional
- Travis CI automatically deploys to Heroku
Problems needed to be solved:
- Test references between objects
Tasks needed to be completed:
- Final Edits for test suite
- Final edits for all project documentation
Potential date of next meeting:
- Tuesday, February 12, 2019
- Wednesday, February 13, 2019