Skip to Content

Changes for page Glossary

Last modified by chrisby on 2024/09/19 10:50
From version 5.4
edited by chrisby
on 2023/02/04 21:53
Change comment: There is no comment for this version
To version 5.5
edited by chrisby
on 2023/02/08 20:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -48,7 +48,7 @@
48 48  (% style="text-align: justify;" %)
49 49  2. In the context of software architecture, the term refers to classes that represent the model of the application and often represent things from the real world. 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 150 because that is a logical constraint on people's ages, even though the integer data range is technically much larger.
50 50  )))
51 -|[[Field Injection>>doc:Software Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)Dependency Injection is performed by forcibly injecting a dependency into an instance through the use of reflections that break even the encapsulation measures. This type of Dependency Injection is to be avoided.
51 +|[[Field Injection>>doc:Software Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)A type of dependency Injection is performed by forcibly injecting a dependency into an instance through the use of reflections that break even the encapsulation measures. This type of Dependency Injection is to be avoided.
52 52  |[[Inversion of Control>>doc:Software Architecture.Dependency Injection.Dependency Injection Explained.WebHome]] (IoC)|(% style="text-align:justify" %)Transfers the responsibility of defining the logic and order of Dependency Injections from the developer to computer.
53 53  |JavaBean|(((
54 54  (% style="text-align: justify;" %)
... ... @@ -61,31 +61,29 @@
61 61  (% style="text-align: justify;" %)
62 62  Often, DTO's and entities follow this convention.
63 63  )))
64 -|Logic|(% style="text-align:justify" %)Any code with non-trivial complexity can be referred to as "logic". In contrast, for example, getters and setters have trivial complexity.
65 -|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 the Spring IoC container is quite simple, but the logic and wiring that goes on in the background is complex.
66 -|Pain|(% style="text-align:justify" %)Something causes pain when somebody spend unnecessary and great effort on a task that often could have been prevented by better code design.
67 -|Production Code|(% style="text-align:justify" %)The counterpart of the Test Code. It contains all the code required to run the application.
64 +|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.
65 +|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.
66 +|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.
67 +|Production Code|(% style="text-align:justify" %)The counterpart to the Test Code. It contains all the code needed to run the application.
68 68  |Runtime|(((
69 -(% style="text-align: justify;" %)
70 -The time period in which the code is executed. For example:
69 +The period of time during which the code is executed. For example:
71 71  
72 -* An exception is thrown by the compiler that finds an invalid syntax in the source code. This is called a compile-time exception.
71 +* An exception is thrown by the compiler that finds invalid syntax in the source code. This is called a compile-time exception.
73 73  * Suppose that after a successful compilation, an executable file was created, started, and an exception was thrown shortly thereafter. Since this happened at runtime, it is a runtime exception.
74 74  )))
75 -|Separation of Concerns|(% style="text-align:justify" %)A principle that says that programs should be modular, with each module dealing with a different aspect of the program. This is intended to give the software a clear, understandable structure.
76 -|[[Setter Injection>>doc:Software Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)Dependency Injection performed by passing a dependency to an instance via setter method argument.
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 +|[[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.
77 77  |Spring Bean|(((
78 78  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.
79 79  
80 -It is not to be confused with JavaBeans.
79 +It should not be confused with JavaBeans.
81 81  )))
82 82  |Static|(((
83 -(% style="text-align: justify;" %)
84 -Often refers to processes that depend non-running code. Examples:
82 +Often refers to processes that depend on non-running code. Examples:
85 85  
86 -* Static Code Analysis Tools can examine source code files for possible improvements.
84 +* Static code analysis tools can examine source code files for possible improvements.
87 87  * Statically typed languages determine the type of an object at compile time.
88 88  )))
89 -|Test Code|(% style="text-align:justify" %)The counterpart of the Production Code. It is code that checks whether the production code works as expected. Test Code plays no role in the operation of an application.
87 +|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.
90 90  |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.
91 -|Wiring|(% style="text-align:justify" %)The process of generating and injecting dependencies to set up an application performed by the IoC container.
89 +|Wiring|(% style="text-align:justify" %)The process of generating and injecting dependencies to start an application, performed by the IoC container.