| ... |
... |
@@ -13,7 +13,6 @@ |
| 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. |
| 15 |
15 |
|Best Practices|(% style="text-align:justify" %)Widely accepted guidelines designed to enhance programming productivity and code quality. Adherence can prevent many potential issues. |
| 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. |
| 17 |
17 |
|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. |
| 18 |
18 |
|[[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. |
| 19 |
19 |
|Component|((( |
| ... |
... |
@@ -49,10 +49,7 @@ |
| 49 |
49 |
|Operating System (OS)|(% style="text-align:justify" %)The foundational system software that manages and coordinates all computer resources. Examples include Windows, MacOS, and Linux. |
| 50 |
50 |
|Pain|(% style="text-align:justify" %)An unpleasant experience caused by unnecessary efforts that could be mitigated with better code design. |
| 51 |
51 |
|Production Code|(% style="text-align:justify" %)Production code forms the software that meets the requirements of the project. It is the code that is deployed in a production environment and used by end users. |
| 52 |
|
-|Representation|(% style="text-align:justify" %)((( |
| 53 |
|
-1. Often used when discussing the specific ways in which data or objects are implemented or modeled within a program or displayed in a GUI. |
| 54 |
|
-1. Less commonly, it refers to a specific implementation of an abstract data type or object. It's the actual, concrete realization of an abstract concept or structure. Can be used interchangeably with the term 'concretion' in this sense. |
| 55 |
|
-))) |
|
51 |
+|Representation|(% style="text-align:justify" %)Refers to a specific implementation of an abstract data type or an object. It's the actual, concrete realization of an abstract concept or structure. |
| 56 |
56 |
|Rollback|The act of returning a system or data to a previous state, often using a snapshot. |
| 57 |
57 |
|Runtime|The period when the code is being executed. |
| 58 |
58 |
|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. |
