| ... |
... |
@@ -1,20 +1,23 @@ |
| 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 |
|
| 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". |
|
13 |
+1. The counterpart of "Concretion". It refers to interfaces and abstract classes that define behavior, namely function signatures, but do not contain information about internal operation. |
|
14 |
+1. A generic, high-level unit. For example, a class contains two functions that contain duplicate code, which should not happen according to the DRY principle. 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 duplicate code was "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)". |
| 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 |
|
-|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 |
+|Assertion|(% style="text-align:justify" %)An assertion function is used in "Test Code". When an unexpected input values are provided, it causes the test containing it to fail. Example call: "assertEquals(expectedResult, actualResult)". |
|
17 |
+|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. |
|
18 |
+|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|((( |
