Skip to content

Meeting Minutes

Jump to bottom
Zheng Yu Cui edited this page Oct 24, 2019 · 21 revisions

Meeting 1: Tues, Sept 24 Minutes

Goals of this meeting:

  • Figure requirements (by considering viewpoint: student)
  • Separate tasks

Issues to add:

  • Requirements, Actors and Use cases
  • Domain model
  • Database design
  • Test cases for persistence layer

Requirements (not formal):

  1. Student must be able to log in.
  2. Student must be able to search by course number.
  3. Student must be able to choose different tutor.
    • Student must be able to check the tutor’s reviews.
  4. Student must be able to read reviews left for them.
  5. Student must be able to book a session with a tutor or group session.
    • Student cannot book for a timeslot for a tutor if they are already booked.
  6. System shall be able to notify the tutor for a tutoring request and give them an option to accept or decline.
  7. Student must be able to cancel their booking
  8. Student must be able to view their previous, current, and pending bookings.
  9. Student must be able to anonymously leave reviews for tutors.
  10. System must randomly assign a room to an individual tutoring session.
  11. Student must be able to view the full fee of the session prior to it
  12. System shall notify the manager in case of group session requests
  13. Student must be able to see which group sessions are available.
  14. Student must be able to email the company to request them to add a course.
  15. System shall be available on multiple platforms. (????)

Task separation:

  • Paul: Database
  • Zheng: Database
  • Erdong: Domain Model
  • Talha: Testing of persistence
  • Mustafain: Testing of persistence

Todo:

  • Vote for the top 5 most important requirements
  • Add formal requirements into the issues
  • Distribute Requirements among ourselves

Meeting 2: Fri, Oct 6 Minutes

Goals of this meeting:

  • Discuss domain model
  • Discuss Use Case diagram

Outcomes:

We discussed the domain model diagram that Erdong came up with. We discussed whether the Student and Tutor classes should both be associated with a Review class(e.g TutorReview for Tutor and StudentReview for Student). It was decided that we don't need separate review classes for both, and that a single Review class associated with the User class would suffice.

TODOs before next meeting:

  • Start working on use case diagrams individually
  • Finalize domain model and figure out code generation using UML Lab (Erdong)
  • Start with database design (Paul and Zheng)
  • Start designing test suite for Persistence Layer(Mustafain and Talha)

Meeting 3: Wed, Oct 9 Minutes

Goals of this meeting:

  • Finalize Domain Model
  • Detailed specification for the Use Case

Outcomes:

  • We finalized the domain model after discussing some last changes to it
  • We added a generalization for the room and tutor availability classes. We also added a separate University class that has an aggregation relationship with the Course class
  • We decided what the detailed specification should include.
  • Successfully deployed the Spring Boot backend and Heroku app.

TODOs:

  • Generate code from UML lab
  • Start Persistence layer design and Testing
  • Figure out issue with TravisCI

Meeting 4: Wed, Oct 23 Minutes

Goals of this meeting:

  • Determine what needs to be done for Deliverable 2
  • Discuss current issues with Deliverable 1

Outcomes:

  • Removal of Tutoring System class
  • Removal of schoolName attribute of Student
  • Distribution of tasks

TODOs:

  • Fix JUnit testing for Deliverable 1
  • Fix the 404 error for the RESTful services
  • Add issues to GitHub
Clone this wiki locally