Changes for page Glossary

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

From version 22.1
edited by chrisby
on 2024/05/05 09:13
Change comment: Renamed back-links.
To version 18.59
edited by chrisby
on 2024/01/21 11:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
2 2  
3 3  | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
4 4  | **Term** | **Explanation** |
5 -| Abstraction | 1) The counterpart of 'concreteness', it refers to interfaces and abstract classes that define behavior (function signatures) but leave the internal implementation of those functions undefined. 2) Duplicated logic can often be merged by creating an 'abstraction' - an additional function containing the duplicated code. |
5 +| Abstraction | 1) The counterpart of 'concreteness', it refers to interfaces and abstract classes that define behavior (function signatures) but leave the internal implementation of those functions undefined. 2) A higher-level, generalized unit of shared code. Duplication across multiple functions can often be resolved by creating an 'abstraction' - an additional function containing the duplicated code. |
6 6  | Abstraction Level | For example, with functions, the level of abstraction refers to how general or specific the function is, with higher levels of abstraction representing broader, more general functionality and lower levels of abstraction representing more detailed, specific operations. |
7 7  | [[Acceptance Test|doc:Software Engineering.Agile.Extreme Programming.Acceptance Tests.WebHome]] | See link. |
8 8  | [[Agile|doc:Software Engineering.Agile.WebHome]] | See link. |
... ... @@ -17,7 +17,7 @@
17 17  | Concretion | The counterpart to 'abstraction'. Concretion is also known as 'implementation'. In OOP, it 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]] | A type of dependency injection in which dependencies are provided to an object through constructor arguments. |
19 19  | Command-Line Interface (CLI) | "[...] a means of interacting with a computer program by inputting lines of text [...]".^[[src](https://en.wikipedia.org/wiki/Command-line_interface)]^ For example, tools/commands used when working with a (Linux) terminal have a CLI. |
20 -| Commitment | A binding promise from one person to another to complete a specific task within a specified period of time. |
20 +| Commitment | Binding promise to complete a specific task within a set period of time. |
21 21  | Component | Often used to refer to a set of units, modules, or "architectural" components without a clearer specification. In software architecture, it refers to a module capable of independent operation, often compiled or packaged into an executable such as a `.jar` or `.exe` file. |
22 22  | [[Continuous Integration|doc:Software Engineering.Agile.Extreme Programming.Continuous Integration.WebHome]] (CI) | See link. |
23 23  | Customers | Individuals who use the software product, focusing on the value it provides to meet their needs. |
... ... @@ -95,6 +95,6 @@
95 95  | Unit | The smallest testable part of an application. This is often a single class, but can also be a single function, or a small cluster of tightly coupled classes or functions that together perform a specific task. |
96 96  | [[Velocity|doc:Software Engineering.Agile.Extreme Programming.Planning Game.Agile and Data.WebHome]] | See link. |
97 97  | Virtual Machine (VM) | A software emulation of a physical computer, able to run its own OS and applications as if it were a separate physical machine. |
98 -| [[Waterfall|doc:Software Engineering.Agile.Waterfall In Software Development2.WebHome]] | See link. |
98 +| [[Waterfall|doc:Software Engineering.Agile.Problems of Waterfall.WebHome]] | See link. |
99 99  | Whispers | Vague comments in the source code that imply code problems without clearly explaining or addressing them. |
100 100  | Wiring | The process conducted by the IoC container to create and inject dependencies, facilitating application startup. |