... |
... |
@@ -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) 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. | |
|
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 variable/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. | |
... |
... |
@@ -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.Problems of Waterfall.WebHome]] | See link. | |
|
98 |
+| [[Waterfall|doc:Software Engineering.Agile.Waterfall In Software Development.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. | |