Changes for page Glossary

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -5,17 +5,9 @@
5	5
6	6
7	7	|**Term**|**Explanation**
8		-|Aware/Unaware|(((
9		-Aware:
10		-
11		-* Class A contains a source code reference of class B and is therefore aware of class B. If you only read the source code of class A, you would know that there has to be a class B.
12		-
13		-Unaware:
14		-
15		-* Class C does not contain a source code reference of class D and is therefore unaware of class D. If you only read the source code of class C, you wouldn't know about the existence of class D.
16		-)))
	8	+|Aware/Unaware|The class A contains a source code reference of the class B and therefore is aware of the class B. If you were to read only the source code of class A, you would know that there must be a class B. If there was no such reference, class A would be unaware of class B.
17	17	|Best Practices|Generally accepted guidelines aimed at increasing your programming productivity. If you take them seriously, you will save yourself a lot of pain.
18		-|[[Constructor Injection>>path:/bin/view/Software%20Engineering/Dependency%20Injection/Types%20of%20Dependency%20Injections%20Compared/]]|Dependency Injection performed by passing a dependency to an instance via constructor argument.
	10	+|[[Constructor Injection>>doc:Software Engineering.Dependency Injection.Types of Dependency Injection.WebHome]]|Dependency Injection performed by passing a dependency to an instance via constructor argument.
19	19	|Component|(((
20	20	1. In Spring, it is a general term for a bean that no other Spring Bean Annotation matches.
21	21	1. In software architecture, it is a module that can be executed independently. It is often compiled and/or compressed into an executable binary such as a .jar or .exe file.
...	...	@@ -23,7 +23,7 @@
23	23	|Data Structure|A very simple type of class that contains only data and no logic. For example, a class that has only public fields but no methods.
24	24	|Dependency|In the context of classes, a dependency is a field that must be initialized in order for an object of that class to function properly. Normally an object is inject via Dependency Injection.
25	25	|Dependency Cycle|For example, class A depends on class B and class B depends on class A. If both objects need the other dependency to construct instances, dependency injection is impossible. Dependency cycles should be avoided. Instead, the dependency graph should look like a directed acyclic graph.
26		-|[[Dependency Injection>>path:/bin/view/Software%20Engineering/Dependency%20Injection/Separation%20of%20Implementation%20and%20Build%20logic/]] (DI)|An object is injected with the dependencies it needs instead of constructing them itself.
	18	+|[[Dependency Injection>>doc:Software Engineering.Dependency Injection.WebHome]] (DI)|An object is injected with the dependencies it needs instead of constructing them itself.
27	27	|Dirty|(((
28	28	~1. Messy, unreadable, or poorly designed code is referred to as "dirty code". Often associated with code written "quick-and-dirty" due to time pressure.
29	29
...	...	@@ -40,8 +40,8 @@
40	40
41	41	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.
42	42	)))
43		-|[[Field Injection>>path:/bin/view/Software%20Engineering/Dependency%20Injection/Types%20of%20Dependency%20Injections%20Compared/]]|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.
44		-|[[Inversion of Control (IoC)>>path:/bin/view/Software%20Engineering/Dependency%20Injection/Separation%20of%20Implementation%20and%20Build%20logic/]]|Transfers the responsibility of defining the logic and order of Dependency Injections from the developer to computer.
	35	+|[[Field Injection>>doc:Software Engineering.Dependency Injection.Types of Dependency Injection.WebHome]]|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.
	36	+|[[Inversion of Control>>doc:Software Engineering.Dependency Injection.Dependency Injection Explained.WebHome]] (IoC)|Transfers the responsibility of defining the logic and order of Dependency Injections from the developer to computer.
45	45	|JavaBean|(((
46	46	A design convention for data structures. Usually it means a class which has:
47	47
...	...	@@ -65,7 +65,7 @@
65	65	* 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.
66	66	)))
67	67	|Separation of Concerns|A principle that says that programs should be modular, with each module taking care of a different aspect of the program. Such modules provide higher level functions that take care of the aspect hidden in the background. For example,
68		-|[[Setter Injection>>path:/bin/view/Software%20Engineering/Dependency%20Injection/Types%20of%20Dependency%20Injections%20Compared/]]|Dependency Injection performed by passing a dependency to an instance via setter method argument.
	60	+|[[Setter Injection>>doc:Software Engineering.Dependency Injection.Types of Dependency Injection.WebHome]]|Dependency Injection performed by passing a dependency to an instance via setter method argument.
69	69	|Spring Bean|(((
70	70	A term used in Spring IoC 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.
71	71