| ... |
... |
@@ -7,8 +7,10 @@ |
| 7 |
7 |
|
| 8 |
8 |
|**Term**|(% style="text-align:justify" %)**Explanation** |
| 9 |
9 |
|Abstraction|(% style="text-align:justify" %)((( |
| 10 |
|
-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. |
|
10 |
+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. |
|
11 |
+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". |
| 11 |
11 |
))) |
|
13 |
+|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)". |
| 12 |
12 |
|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. |
| 13 |
13 |
|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. |
| 14 |
14 |
|Concretion|(% style="text-align:justify" %)((( |
