Changes for page Glossary

Last modified by chrisby on 2024/09/19 10:50

From version 2.7
edited by chrisby
on 2022/12/29 20:35
Change comment: There is no comment for this version
To version 2.9
edited by chrisby
on 2022/12/29 21:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,13 +2,18 @@
2 2  (((
3 3  (% style="text-align: justify;" %)
4 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 -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.
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".
11 11  )))
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)".
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" %)(((