Skip to Content

Changes for page Glossary

Last modified by chrisby on 2024/09/19 10:50
From version 5.2
edited by chrisby
on 2023/02/04 21:32
Change comment: There is no comment for this version
To version 4.1
edited by chrisby
on 2022/12/31 18:07
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,10 @@
1 1  (% class="box infomessage" %)
2 2  (((
3 3  (% style="text-align: justify;" %)
4 -The explanations given here do not claim to be complete. They merely serve as a brief description to give an idea of the respective term. For more detailed information, the Internet should be consulted. Note that some of these technical terms are fuzzy, overlap with other terms, or have different meanings depending on the context or the people using them. This Glossary is an attempt to structure these terms in a concise manner. Be open to variations as you talk and work with other developers.
4 +The explanations given here do not claim to be complete. They merely serve as a brief description to give an idea of the respective term. For more detailed information, the Internet should be consulted.
5 +
6 +(% style="text-align: justify;" %)
7 +Note that some of these technical terms are fuzzy, overlap with other terms, or have different meanings depending on the context or the people using them. This Glossary is an attempt to structure these terms in a concise manner. Be open to variations as you talk and work with other developers.
5 5  )))
6 6  
7 7  
... ... @@ -14,7 +14,7 @@
14 14  |Aware/Unaware|(% style="text-align:justify" %)The class A contains a source code reference of the class B and therefore is aware of the class B. If you were to read only the source code of class A, you would know that there must be a class B. If there was no such reference, class A would be unaware of class B.
15 15  |Best Practices|(% style="text-align:justify" %)Generally accepted guidelines aimed at increasing your programming productivity. If you take them seriously, you will save yourself a lot of pain.
16 16  |Concretion|(% style="text-align:justify" %)(((
17 -It is the counterpart of "abstraction" and is sometimes called "implementation". In OOP it refers to classes that implement methods of interfaces or abstract classes. A concretion defines the internal workings of these abstract functions by providing the "concrete" code.
20 +It is the counterpart of "abstraction" and is sometimes called "implementation". It refers to classes that implement interfaces or inherit from abstract classes. It defines the internal workings of the functions it must provide by containing the "concrete" code.
18 18  )))
19 19  |[[Constructor Injection>>doc:Software Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)Dependency Injection performed by passing a dependency to an instance via constructor argument.
20 20  |Component|(((
... ... @@ -24,7 +24,7 @@
24 24  |Data Structure|(% style="text-align:justify" %)A very simple type of class that contains only data and no logic. For example, a class that has only public fields but no methods. Another form is a class with private fields and simple corresponding getters and setters.
25 25  |Dependency|(% style="text-align:justify" %)In the context of classes, a dependency is a field that must be initialized with an instance of another class in order for an object of that class to function properly. Often, the initialization is realized via Dependency Injection.
26 26  |Dependency Cycle|(% style="text-align:justify" %)For example, an instance of one class requires an instance of another class to be constructed, and vice versa. So both classes need the other dependency to construct an instance. Therefore, it is impossible to construct either instance at all. Always make sure that the dependency graph looks like a directed acyclic graph.
27 -|[[Dependency Injection>>doc:Software Architecture.Dependency Injection.WebHome]] (DI)|(% style="text-align:justify" %)An object is injected with the dependencies it needs instead of constructing them itself.
30 +|[[Dependency Injection>>doc:Software Engineering.Dependency Injection.WebHome]] (DI)|(% style="text-align:justify" %)An object is injected with the dependencies it needs instead of constructing them itself.
28 28  |Dirty|(((
29 29  (% style="text-align: justify;" %)
30 30  ~1. Messy, unreadable, or poorly designed code is referred to as "dirty code". Often associated with code written "quick-and-dirty" due to time pressure.