| ... |
... |
@@ -10,11 +10,10 @@ |
| 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 |
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 |
|
-|Architecture|(% style="text-align:justify" %)Refers to the overall structure of a software system. It defines the components of the system, their interactions, and the design rules that govern them. Its purpose is to ensure that the system meets its requirements while promoting maintainability, scalability, and minimizing the cost of development and evolution over time. |
| 14 |
14 |
|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)'. |
| 15 |
15 |
|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. |
| 16 |
16 |
|Best Practices|(% style="text-align:justify" %)Widely accepted guidelines designed to enhance programming productivity and code quality. Adherence can prevent many potential issues. |
| 17 |
|
-|Business Logic|(% style="text-align:justify" %)Represents the core computations, data processing, and rules that form the backbone of a software application. It's independent of details such as data presentation, storage mechanisms, networking, third-party library and operating system interactions. |
|
16 |
+|Business Logic|(% style="text-align:justify" %)Represents the core computations, data processing, and rules that form the backbone of a software application. It's independent of low-level details such as data presentation, storage mechanisms, networking, third-party library and operating system interactions. |
| 18 |
18 |
|Concretion|(% style="text-align:justify" %)The counterpart to 'abstraction', also known as 'implementation'. In OOP, refers to non-abstract classes that implement the methods of interfaces or abstract classes. A concretion provides the 'concrete' code defining the workings of these abstract functions. |
| 19 |
19 |
|[[Constructor Injection>>doc:Software Engineering.Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)A type of dependency injection in which dependencies are provided to an object through constructor arguments. |
| 20 |
20 |
|Component|((( |
