| ... |
... |
@@ -8,7 +8,7 @@ |
| 8 |
8 |
|**Term**|(% style="text-align:justify" %)**Explanation** |
| 9 |
9 |
|Abstraction|(% style="text-align:justify" %)((( |
| 10 |
10 |
1. The counterpart to 'Concretion', refers to interfaces and abstract classes that define behavior (function signatures) but leave the internal operation of these functions undefined. |
| 11 |
|
-1. A higher-level, generalized unit of code. Duplication across multiple functions can be resolved by creating an 'abstraction' - a separate function containing the shared code. This adheres to the DRY principle. |
|
11 |
+1. A higher-level, generalized unit of code. Duplication across multiple functions can be resolved by creating an 'abstraction'—a separate function containing the shared code. This adheres to the DRY principle. |
| 12 |
12 |
))) |
| 13 |
13 |
|Assertion|(% style="text-align:justify" %)Pertains to an assertion function, a crucial part of testing. If the input values don't satisfy a certain condition, the test containing the assertion fails. Example: 'assertEquals(expectedResult, actualResult)'. |
| 14 |
14 |
|Awareness|(% style="text-align:justify" %)A class A is aware of class B if it contains a reference to class B in its source code. If no such reference exists, class A is unaware of class B. |
| ... |
... |
@@ -47,7 +47,6 @@ |
| 47 |
47 |
|Production Code|(% style="text-align:justify" %)Code that comprises the functioning part of an application, as opposed to test code. |
| 48 |
48 |
|Rollback|The act of returning a system or data to a previous state, often using a snapshot. |
| 49 |
49 |
|Runtime|The period when the code is being executed. |
| 50 |
|
-|Self-Containment|(% style="text-align:justify" %)The ability of software to operate independently, without dependence on external services or factors. This characteristic ensures that its results are determined solely by its source code, which promotes stability and consistency. |
| 51 |
51 |
|Separation of Concerns|(% style="text-align:justify" %)A design principle suggesting that each module or component should have a single responsibility or concern, enhancing clarity and maintainability. |
| 52 |
52 |
|[[Setter Injection>>doc:Software Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)A type of dependency injection where a dependency is provided to an object through a setter method. |
| 53 |
53 |
|Snapshot|A saved state of a system or data at a specific point in time. Can be used for rollbacks. |
