Rivalry2

HTML Diff

0 added 0 removed

Original 2026-01-01

Modified 2026-02-21

1 Programmers always write software for a specific field. For example, accounting software relies on accounting rules, and a website for watching TV shows relies on TV industry concepts such as seasons or episodes. The same goes for other fields: booking flights and hotels, finding tours, buying and selling cars.

2 Understanding the domain for which you're writing a program is just as important as being able to program. Fields can be complex, like accounting or engineering manufacturing. You do not need to know it thoroughly, but a general understanding is still required.

3 Let's look at Hexlet since you know its key concepts - courses, lessons, professions, tests, code reviews, quizzes, course participants, and projects. There are two hundredentities- concepts in the code on Hexlet.

4 Entities are often in relationships with one another:

5 <ul><li>Professions consist of courses</li>

6 <li>Courses consist of lessons</li>

7 <li>Lessons consist of theory blocks, quizzes, and exercises</li>

8 <li>Quizzes aggregate questions</li>

9 <li>Questions obtain answers</li>

10 </ul>These connections have specific names:

11 <ul><li>One-to-manyoro2m- one lesson can have one course, but one course contains many lessons</li>

12 <li>Many-to-manyorm2m- many users can take one course, and one user can take many courses</li>

13 <li>One-to-oneoro2o- it is how users and experts connect on Hexlet</li>

14 </ul>In reality, everything is still a little more complicated because the same entity may look completely different from the point of view of various systems. The users are two separate things from the point of view of accountants and mentors.

15 The descriptions of the objects belonging to the domain under consideration and their connections aredomain ontology.

16 The ontology is well-known by experts in the relevant field - for example, accountants, professors, and lawyers. They often present it intuitively and informally, so we can communicate with them to build a formal ontology.

17 This process occurs throughout the development of the project and beyond separate stages. In creating the ontology, we identify specific terms and agree:

18 <ul><li>What they mean</li>

19 <li>How they are related</li>

20 </ul>We can form the data model using the ER model in high-level conceptual database design. The architecture for future applications starts to appear at this stage.

21 It is not always possible to unambiguously say what connection exists between two entities. We can think ahead and immediately create more complex cases - for example, m2m rather than o2m, which affects the complexity of the code.

22 More complex connectivity means more code lines and higher development and maintenance costs. The complexity of the connections can be described as follows, in order of complexity: o2o, o2m, m2m. Someone can make mistakes when choosing a connector, which indicates a lack of understanding of the topic.

23 Let us give you an example. Suppose we implement a user and a foreign passport association in the system:

24 <ul><li>Intuitively, these concepts have a one-to-one relationship: a user can have a foreign passport</li>

25 <li>But you can change the passport if it gets lost or expires</li>

26 <li>In addition, some countries allow you to have more than one foreign passport</li>

27 </ul>On the other hand, the real world is always more complex and more complete than any model. Programmers create a universal and comprehensive model of a particular domain and try to understand the needs of a business, identify only significant parts of the field under consideration, and transfer them to the code.

28 How entities appear in code varies between languages:

29 <ul><li>Some define types using abstract data types, interfaces, or classes</li>

30 <li>Others define structures</li>

31 <li>Others don't provide options except for dictionaries and associative arrays</li>

32 </ul>From the next lesson, we'll start studying various subject areas and build suitable data models:

33 The most significant topic will emerge when we begin to study OOP and ORM. You can have a general idea of subject areas, entities, and relationships. Remember to read the information in the links provided - the more questions you have at this stage, the better.