Domain Modelling

Question 1

What is Domain Modelling?

Answer 1

A structural visual representation of interconnected concepts or real world objects that incorporates vocabulary, key concepts, behaviors and relationships of all its entities.

Question 2

What’s the purpose of Domain Modelling?

Answer 2

To allow for a better understanding of real-world problems and their relationships regardless of technical/business competencies

Question 3

What are some common challenges with domain diagrams?

Answer 3

• Relationships may not be clearly defined
• Requires strong expertise i
• Requires regular communication between domain experts and develo pers

Question 4

Explain the difference between domain an design modelling.

Answer 4

domain modeling is more concerned about real-world relationships while design model is more concerned with representing software objects and their relationships and how they will establish the requirements of the system.

Question 5

Explain methods or activities that you would use to identify classes and relationships
that need to be in your domain model.

Answer 5

Using noun identification (misunderstanding requirements)
Analysing the important entities of a system (entities may exist that are not important to the system.
conceptual class category list
relationships can be identified actions carried out by entities

Question 6

What is the representational gap between the domain model and the design model
and how do we keep it low?

Answer 6

The representational gap is the difference between the class model representation of the domain and of the design of the software itself.