Skip to Content

Changes for page Glossary

Last modified by chrisby on 2024/09/19 10:50
From version 5.10
edited by chrisby
on 2023/05/07 11:26
Change comment: There is no comment for this version
To version 5.7
edited by chrisby
on 2023/03/07 22:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -21,15 +21,12 @@
21 21  1. In Spring, this is a generic annotation for a bean that does not match any other Spring bean annotation: "@Component".
22 22  1. In software architecture, it is a module that can be executed independently. It is often compiled and/or compressed into an executable such as a .jar or .exe file.
23 23  )))
24 -|Daemon|(% style="text-align:justify" %)A program that runs in the background of a computer system, i.e. without a GUI.
25 25  |Data Structure|(% style="text-align:justify" %)A very simple type of class that contains only data and no logic. For example, a class that has only public fields and no methods. Another form is a class with private fields and simple corresponding getters and setters.
26 26  |Dependency|(% style="text-align:justify" %)In the context of classes, a dependency is a member field of one class that must be initialized with an instance of another class in order for an instance of the first class to function properly. This initialization is often done by dependency injection.
27 27  |Dependency Cycle|(% style="text-align:justify" %)For example, an instance of one class requires an instance of another class to be constructed, and vice versa. So both classes need the other dependency to construct an instance. Therefore, it is impossible to construct either instance at all. Always make sure that the dependency graph looks like a directed acyclic graph.
28 28  |[[Dependency Injection>>doc:Software Architecture.Dependency Injection.WebHome]] (DI)|(% style="text-align:justify" %)A technique in which the dependencies an object needs are injected from the outside, rather than constructed within the class.
29 29  |Dirty|(((
30 -~1. Messy, unreadable, or poorly designed code is referred to as "dirty code". Often associated with code written "quick-and-dirty" due to the time constraints of a software project.
31 -
32 -2. The term comes from the phrase "getting one's hands dirty" and refers to coding work that is considered monotonous, detailed, low-level, or undemanding, but necessary. The term is often used in the context of I/O operations. For example, creating a database transaction, is often done in a similar way and is not considered fun by experienced programmers who have done it many times. High-level design is more exciting because it requires more creativity from the developer and is more intellectually stimulating.
29 +~1. Messy, unreadable, or poorly designed code is referred to as "dirty code". Often associated with code written "quick-and-dirty" due to the time constraints of a software project.2. The term comes from the phrase "getting one's hands dirty" and refers to coding work that is considered monotonous, detailed, low-level, or undemanding, but necessary. The term is often used in the context of I/O operations. For example, creating a database transaction, is often done in a similar way and is not considered fun by experienced programmers who have done it many times. High-level design is more exciting because it requires more creativity from the developer and is more intellectually stimulating.
33 33  )))
34 34  |Dynamic|(((
35 35  (% style="text-align: justify;" %)
... ... @@ -46,7 +46,6 @@
46 46  2. In the context of software architecture, the term refers to classes that represent the data model of the application. For example, a banking application may have entity classes such as //account//, //order//, //customer//, or //employee//. They are often built like simple data structures, but may contain additional validation logic to impose logical constraints on their fields. For example, the integer field //customer.age// must always be between 0 and 120 because this is a logical constraint on the age of people, even though the integer data range is technically much larger.
47 47  )))
48 48  |[[Field Injection>>doc:Software Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)A type of dependency injection that is performed by forcibly injecting a dependency into an instance through the use of reflections that break even the encapsulation of private fields. This type of dependency injection should be avoided.
49 -|Graphical User Interface (GUI)|(% style="text-align:justify" %)A type of user interface that allows the user to interact with the computer by means of graphical elements such as icons, buttons, windows and menus.
50 50  |[[Inversion of Control>>doc:Software Architecture.Dependency Injection.Dependency Injection Explained.WebHome]] (IoC)|(% style="text-align:justify" %)Shifts the responsibility for defining the logic and order of dependency injections from the developer to the computer.
51 51  |JavaBean|(((
52 52  (% style="text-align: justify;" %)
... ... @@ -60,10 +60,9 @@
60 60  Often DTOs and entities follow this convention.
61 61  )))
62 62  |Logic|(% style="text-align:justify" %)Any code with non-trivial complexity can be called "logic". In contrast, for example, getters and setters have trivial complexity.
63 -|Magic|(% style="text-align:justify" %)"Code that handles complex tasks while hiding that complexity to present a simple interface."^^[[~[sources~]>>url:https://en.wikipedia.org/wiki/Magic_(programming)]]^^ For example, the introduction of an IoC container is often quite simple, but the logic and wiring that goes on in the background is complex.
59 +|Magic|(% style="text-align:justify" %)"Code that handles complex tasks while hiding that complexity to present a simple interface."^^[[[sources]>>url:https://en.wikipedia.org/wiki/Magic_(programming)]]^^ For example, the introduction of an IoC container is often quite simple, but the logic and wiring that goes on in the background is complex.
64 64  |Pain|(% style="text-align:justify" %)Something causes pain when someone spends unnecessary effort on a task that could often have been avoided by better code design.
65 65  |Production Code|(% style="text-align:justify" %)The counterpart to the Test Code. It contains all the code needed to run the application.
66 -|Rollback|The process of reverting a system or data to a previous snapshot.
67 67  |Runtime|(((
68 68  (% style="text-align: justify;" %)
69 69  The period of time during which the code is executed. For example:
... ... @@ -73,7 +73,6 @@
73 73  )))
74 74  |Separation of Concerns|(% style="text-align:justify" %)A principle that says that software should be structured modular, with each module dealing with a different aspect of the program. This is intended to give the software a clear, understandable architecture.
75 75  |[[Setter Injection>>doc:Software Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)A type of dependency injection, which is performed by passing a dependency to an instance via a setter method argument.
76 -|Snapshot|A snapshot is a copy of a system or data at a specific point in time. It enables 'rollbacks' that can be used to revert to that state in the future if needed.
77 77  |Spring Bean|(((
78 78  (% style="text-align: justify;" %)
79 79  A term used in the Spring Framework for an object that is contained in the IoC container to be injected into other beans and/or to receive dependency injections. It is one of many components/beans that are wired together via IoC to form the application when it is started.
... ... @@ -89,5 +89,5 @@
89 89  * Statically typed languages determine the type of an object at compile time.
90 90  )))
91 91  |Test Code|(% style="text-align:justify" %)The counterpart to the Production Code. It is code that checks that the production code works as expected. Test code has no role in the operation of an application.
92 -|Test-Driven Development (TDD)|(% style="text-align:justify" %)A workflow in which the developer implements code in small steps, incrementally and iteratively, defining tests at each iteration.
86 +|Test-Driven Development|(% style="text-align:justify" %)A workflow in which the developer implements code in small steps, incrementally and iteratively, defining tests at each iteration.
93 93  |Wiring|(% style="text-align:justify" %)The process of generating and injecting dependencies to start an application, performed by the IoC container.