Class Diagram Review 1 - bounswe/bounswe2019group9 GitHub Wiki

Review 1 by Halit

These are the list of things I believe we should talk over to improve the Class Diagram Draft. These questions/suggestions are not final, and will most possibly be proceeded by more reviews.

General Structure

  1. Why are unidirectional associations used in almost everywhere instead of bidirectional ones.

  2. Why are most classes separated into a normal version and a controller version.

    2.1. How about merging Review and ReviewController? 2.2. How about merging WritingExercise and WritingExerciseController? 2.3. How about breaking up LearningMaterialController and merging its parts with LearningMaterial, Tag and other classes.

Numbers

  1. Why are some numbers missing about associations?

    1.1. LanguageController one to many Language

Diagram / Shapes

  1. Why is it that two different ways to represent an arrow head is used? (-> and -▶) According to the resources I've checked, they mean the same thing, unidirectional association. If the composition interaction was meant, it should be shown as -♦ not as -▶

Typos ?

  1. RegiteredUserController => RegisteredUserController