Skip to Content

Changes for page Glossary

Last modified by chrisby on 2024/09/19 10:50
From version 12.7
edited by chrisby
on 2023/10/13 10:27
Change comment: There is no comment for this version
To version 12.8
edited by chrisby
on 2023/10/13 10:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -38,6 +38,12 @@
38 38  )))
39 39  |[[Field Injection>>doc:Software Engineering.Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)A type of dependency injection where a dependency is injected directly into an object's field via reflection, bypassing encapsulation.
40 40  |Graphical User Interface (GUI)|(% style="text-align:justify" %)A user interface that allows users to interact with the system through graphical elements like icons, buttons, windows, and menus.
41 +|Isolation/Isolated|(% style="text-align:justify" %)(((
42 +The opposite of integration. Isolation is the separation of a unit or component from the rest of the system in order to test, develop or understand it independently and ensure that it works correctly without external interference. For example, in unit testing, a single unit is usually tested independently of other units and is isolated from them.
43 +)))
44 +|Integration/Integrated|(% style="text-align:justify" %)(((
45 +The opposite of isolation. Integration is the process of combining different software units or components to work together as a single, cohesive system.  For example, component testing is more integrated than unit testing because it involves multiple units working together. Integration testing tests the interaction between two components.
46 +)))
41 41  |[[Inversion of Control>>doc:Software Engineering.Architecture.Dependency Injection.Dependency Injection Explained.WebHome]] (IoC)|(% style="text-align:justify" %)A design principle that encourages the delegation of application unit wiring to a computer algorithm that facilitates [[dependency injection>>doc:Software Engineering.Architecture.Dependency Injection.WebHome]], rather than the developer implementing this logic manually.
42 42  |Module|(% style="text-align:justify" %)A distinct part of a software that encapsulates specific implementation details, such as functions, data structures, classes, interfaces, or even other modules. It exposes a concise API designed to perform specific tasks. These modules are typically crafted for reusability and improved code organization, thereby promoting a modular design.
43 43  |Logic|(% style="text-align:justify" %)Code with non-trivial complexity. For instance, getters and setters have trivial complexity and are usually not considered 'logic'.