| ... |
... |
@@ -7,18 +7,18 @@ |
| 7 |
7 |
|
| 8 |
8 |
|**Term**|(% style="text-align:justify" %)**Explanation** |
| 9 |
9 |
|Abstraction|(% style="text-align:justify" %)((( |
| 10 |
|
-1. The opposite of "Concretion". It refers to interfaces and abstract classes that define behavior, namely function signatures, but contain no information about the internal operation of the functions. |
| 11 |
|
-1. A generic, high-level unit. For example, a class may have two functions that contain duplicate code, which the DRY principle says should not happen. The duplication can be resolved by moving the duplicate code to a common function (the "abstraction" of that code) and calling the function where the code was previously located. The duplicated code has been "abstracted". |
|
10 |
+1. The opposite of 'Concretion'. It refers to interfaces and abstract classes that define behavior, namely function signatures, but contain no information about the internal operation of the functions. |
|
11 |
+1. A generic, high-level unit. For example, a class may have two functions that contain duplicate code, which the DRY principle says should not happen. The duplication can be resolved by moving the duplicate code to a common function (the 'abstraction' of that code) and calling the function where the code was previously located. The duplicated code has been 'abstracted'. |
| 12 |
12 |
))) |
| 13 |
|
-|Assertion|(% style="text-align:justify" %)Refers to an assertion function which is an essential part of test code. If the input values do not satisfy a particular condition, the test containing the assertion will fail. Example call: "assertEquals(expectedResult, actualResult)". |
|
13 |
+|Assertion|(% style="text-align:justify" %)Refers to an assertion function which is an essential part of test code. If the input values do not satisfy a particular condition, the test containing the assertion will fail. Example call: 'assertEquals(expectedResult, actualResult)'. |
| 14 |
14 |
|Aware/Unaware|(% style="text-align:justify" %)Class A contains a source code reference to class B and is therefore aware of class B. If you only read 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 for increasing your programming productivity. Taking them seriously will save you a lot of pain. |
| 16 |
16 |
|Concretion|(% style="text-align:justify" %)((( |
| 17 |
|
-It is the counterpart to "abstraction" and is sometimes called "implementation". In OOP it refers to non-abstract classes that could implement methods of interfaces or abstract classes. A concretion defines the internal workings of these abstract functions by providing the "concrete" code. |
|
17 |
+It is the counterpart to 'abstraction' and is sometimes called 'implementation'. In OOP it refers to non-abstract classes that implement methods of interfaces or abstract classes. A concretion defines the internal workings of these abstract functions by providing 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, which is performed by passing a dependency to an instance via a constructor argument. |
| 20 |
20 |
|Component|((( |
| 21 |
|
-1. In Spring, this is a generic annotation for a bean that does not match any other Spring bean annotation: "@Component". |
|
21 |
+1. In Spring, this is a generic annotation for a bean that does not match any other Spring bean annotation: '@Component'. |
| 22 |
22 |
1. In software architecture, it is a module that can be executed independently. It is often compiled and/or compressed into an executable such as a .jar or .exe file. |
| 23 |
23 |
))) |
| 24 |
24 |
|Daemon|(% style="text-align:justify" %)A program that runs in the background of a computer system, i.e. without a GUI. |
| ... |
... |
@@ -27,12 +27,12 @@ |
| 27 |
27 |
|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. |
| 28 |
28 |
|[[Dependency Injection>>doc:Software Architecture.Dependency Injection.WebHome]] (DI)|(% style="text-align:justify" %)A technique in which the dependencies an object needs are injected from the outside, rather than constructed within the class. |
| 29 |
29 |
|Dirty|((( |
| 30 |
|
-Messy, unreadable, or poorly designed code is referred to as "dirty code". Often associated with code written "quick-and-dirty" due to the time constraints of a software project. |
|
30 |
+Messy, unreadable, or poorly designed code is referred to as 'dirty code'. Often associated with code written 'quick-and-dirty' due to the time constraints of a software project. |
| 31 |
31 |
))) |
| 32 |
32 |
|Distribution|A version of an OS packaged with specific software and configurations for particular use cases. Examples are Ubuntu, Fedora and Arch Linux, which are based on Linux. |
| 33 |
33 |
|Dynamic|((( |
| 34 |
34 |
(% style="text-align: justify;" %) |
| 35 |
|
-Often refers to processes that appear at run time when the code has already been executed and is "running". Examples: |
|
35 |
+Often refers to processes that appear at run time when the code has already been executed and is 'running'. Examples: |
| 36 |
36 |
|
| 37 |
37 |
* Dynamic dependencies are dependencies that can be replaced at runtime. |
| 38 |
38 |
* Dynamically typed languages determine the type of an object at runtime. |
