Skip to Content

Changes for page Glossary

Last modified by chrisby on 2024/09/19 10:50
From version 11.16
edited by chrisby
on 2023/10/02 22:19
Change comment: There is no comment for this version
To version 11.14
edited by chrisby
on 2023/06/25 14:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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. For example, duplication across multiple functions can be resolved by creating an 'abstraction' - a separate function containing the shared code.
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  |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)'.
... ... @@ -69,6 +69,5 @@
69 69  |Test Code|(% style="text-align:justify" %)Code that tests the functionality of production code. Does not contribute to the operational aspects of an application.
70 70  |Test-Driven Development (TDD)|(% style="text-align:justify" %)A development approach where code is written in small increments, with tests defining functionality written before each coding iteration.
71 71  |Unit|(% style="text-align:justify" %)The smallest testable part of an application. This is often a single class, method or module, but can also be a small cluster of tightly coupled classes or functions that together perform a specific functionality.
72 -|User Story|(% style="text-align:justify" %)Abbreviated description of a feature of a system told from a users perspective. Also see [[this article>>doc:Software Engineering.Agile.Extreme Programming.Planning Game.WebHome]].
73 73  |Virtual Machine (VM)|(% style="text-align:justify" %)A software emulation of a physical computer, able to run its own OS and applications as if it were a separate physical machine.
74 74  |Wiring|(% style="text-align:justify" %)The process conducted by the IoC container to create and inject dependencies, facilitating application startup.