TA Meeting #1

Meeting Details

Revising our class diagram briefly with our TA and getting feedback.
Planning our sequence diagrams.
Discussing other elements of the course such as attending weekly TA meetings, presenting personal work and taking notes of meetings.

We explained our class diagram to our TA. He gave us some general feedback.
TA told us that a separate class for sport fields is not needed. Therefore, we will not include it.
We will need a field for user class that stores a list of hidden(private) attributes. We should not handle such hidden attributes in get/set methods as they are general methods that will be used by the user itself as well.
We discussed how many sequence diagrams are needed in general and listed some of the core scenarios.

We will need to update our requirements and possibly mockups regularly since we will weekly get feedbacks.
We should attend weekly TA meetings as we will present our personal work in the meetings, which will be used in the grading process.

We should adjust our class diagram to make fields/methods as private as possible.
We should add a field to the user class that lists the private information.
We forgot to ask how we should handle guest users in the class diagram. We should ask this in the Tuesday's PS.