Reviewing Repository - bounswe/2021SpringGroup6 GitHub Wiki

For the first week's assignment, we have taken following actions

Closing unnecessary issues

Reviewing requirements

Added Requirements: 1.1.3.5, 1.2.2.6, 1.2.4.9, 1.3.2.3.2, 2.4
Changed Requirements: 1.1.3.1, 1.5.1.1, 1.5.1.2

Updating communication plan both for general meetings and domain specific meetings

Related Issues:

Introducing our project and repository to newcomers

  • Structure of the repository and Wiki is explained on group meeting.
  • Profile page for the new member is created and added to Wiki home page.

Project Plan

Project plan is updated with new dates. Since the teams are changed, assignees are changed and project is divided into logical parts. New project plan can be found here.

Tasks for Sequence Diagrams

In general, we should add ":" to our class definitions and names may be given but it is optional Below, tasks that need to be done are specified for each sequence diagram.

  • Database access should be added(for both the first and the last one)
  • Filter can be removed, if it is not removed, filter object should be created.
  • Query part should be positioned little bit lower.
  • Status and response message should be returned.
  • Query part should be positioned little bit lower.
  • Status and response message should be returned.
  • Filter should be a class method/static method
  • When filter is created, it should be analyzed that if anything should be returned to the user.
  • Database access should be added(for every step)
  • Dashed lines should be added from class boxes
  • Database access should be added
  • Discussion info object should be created
  • A note regarding an assumption about event is already found should be added under the picture.
  • Dashed lines should be added from class boxes
  • Database access should be added
  • Discussion info object should be created
  • A note regarding an assumption about event is already found should be added under the picture.
  • Dashed lines should be added from class boxes
  • Information from database should be returned with an arrow.
  • Insert arrow should be positioned lower
  • Dashed lines should be added from Event class
  • A note regarding an assumption about event is already found should be added under the picture.
  • Class names should not be underlined.
  • Event information object should be created.
  • The first error message arrow that is going to the user should be positioned lower.
  • "addAnewEventToList" arrow should be positioned lower and it should access to the database.