Domain Modeling Crash Course

Поделиться
HTML-код
  • Опубликовано: 7 ноя 2024

Комментарии • 10

  • @latedeveloper7836
    @latedeveloper7836 3 года назад +8

    0:30 Visualise a domain model with a class diagram from UML
    0:45 Here: classes, customer, order and item descriptions, some important attributes (name, address), relationships (associations between classes)
    3:40 Useless model example - doesn't really go beyond requirements
    4:15 Domain module should show info to fulfill requirements

  • @morgadoapi4431
    @morgadoapi4431 2 года назад +8

    Thanks for the video Tobias Olsson. May your Viking forefathers give you the energy to continue bringing out good videos!

  • @h0bb3
    @h0bb3  Год назад +2

    Please like and subscribe! Thinking about doing more vids like this!

  • @lisasalxa5795
    @lisasalxa5795 2 года назад +8

    what actually the difference between uml class diagram and uml domain class diagram

    • @h0bb3
      @h0bb3  Год назад +8

      The major difference is that the domain model is modeling the reality (as in the requirments) it is therefore less detailed than a design diagram as this often contains much more details and also specific software classes needed to build the software per se.
      As the domain model is used for analysis it does not require a detailed UML notations. For example associations are bi-directional and we use a name, compared to design where we use the roles (direction/navigability, name, and multiplicity)
      domain model -> used to understand the requirements better
      design model -> used to understand how we can build a software system

  • @jasur.tech101
    @jasur.tech101 2 года назад +1

    What is updated domain model?

  • @Brett5ive
    @Brett5ive Год назад +1

    Thanks!

  • @ricardoyalico3513
    @ricardoyalico3513 3 года назад +2

    Good video ty

  • @patrikvajgel240
    @patrikvajgel240 Месяц назад

    poggies