Skip to Content

Changes for page Glossary

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

Summary

Details

Page properties
Content
... ... @@ -17,8 +17,7 @@
17 17  |[[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.
18 18  |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.
19 19  |Component|(((
20 -1. In Spring, a generic annotation for a bean that doesn't fit other specific Spring bean annotations: '@Component'.
21 -1. In software architecture, a module capable of independent operation, often compiled or packaged into an executable such as a .jar or .exe file.
20 +In software architecture, a module capable of independent operation, often compiled or packaged into an executable such as a .jar or .exe file.
22 22  )))
23 23  |Daemon|(% style="text-align:justify" %)A program running in the background of a system, typically without a GUI.
24 24  |Data Structure|(% style="text-align:justify" %)A class primarily meant to hold data and provide basic operations to access and manipulate that data. May contain only public fields, or private fields with associated getter and setter methods.
... ... @@ -39,8 +39,7 @@
39 39  )))
40 40  |[[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.
41 41  |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.
42 -|[[Inversion of Control>>doc:Software Engineering.Architecture.Dependency Injection.Dependency Injection Explained.WebHome]] (IoC)|(% style="text-align:justify" %)A design principle that delegates a program's control flow to a separate container or framework that "wires" application components together, facilitating [[dependency injection>>doc:Software Engineering.Architecture.Dependency Injection.WebHome]]. An IoC container, as found in the Spring Framework, is a common tool for implementing this principle.
43 -|JavaBean|A design convention for data structures. Typically, a class with a public no-argument constructor, private fields, and getter/setter methods for each field. Often followed by DTOs and entities.
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.
44 44  |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.
45 45  |Logic|(% style="text-align:justify" %)Code with non-trivial complexity. For instance, getters and setters have trivial complexity and are usually not considered 'logic'.
46 46  |Magic|(% style="text-align:justify" %)Code that performs complex tasks while abstracting away the complexity, presenting a simple interface to the user.
... ... @@ -53,9 +53,6 @@
53 53  |Separation of Concerns|(% style="text-align:justify" %)A design principle suggesting that each module or component should have a single responsibility or concern, enhancing clarity and maintainability.
54 54  |[[Setter 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 provided to an object through a setter method.
55 55  |Snapshot|A saved state of a system or data at a specific point in time. Can be used for rollbacks.
56 -|Spring Bean|(((
57 -An object managed within the Spring Framework's IoC container, which can be injected into other beans or receive injections itself. It contributes to the application's functionality upon startup and should not be confused with JavaBeans.
58 -)))
59 59  |Static|Pertains to behaviors or properties determined at compile time. Examples: static code analysis tools inspect source code; statically-typed languages determine an object's type at compile time.
60 60  |System|Entirety of software components designed to work together effectively in a production environment.
61 61  |Test Code|(% style="text-align:justify" %)Code that tests the functionality of production code. Does not contribute to the operational aspects of an application.