Changes for page Glossary

Summary

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

Details

Page properties

Content

...	...	@@ -27,9 +27,10 @@
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		-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.
	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.
31	31	)))
32		-|Distribution|A version of an OS packaged with specific software and configurations for particular use cases. Examples are Ubuntu, Fedora and Arch Linux, which are based on Linux.
33	33	|Dynamic|(((
34	34	(% style="text-align: justify;" %)
35	35	Often refers to processes that appear at run time when the code has already been executed and is "running". Examples:
...	...	@@ -42,9 +42,9 @@
42	42	~1. In an object context, this means that two objects of the same type that contain exactly the same values in their fields can be considered equivalent, but are still two separate entities.
43	43
44	44	(% style="text-align: justify;" %)
45		-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//.
	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.
46	46	)))
47		-|[[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.
	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.
48	48	|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.
49	49	|[[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.
50	50	|JavaBean|(((
...	...	@@ -59,14 +59,17 @@
59	59	Often DTOs and entities follow this convention.
60	60	)))
61	61	|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.
62		-|Magic|(% style="text-align:justify" %)'Code that handles complex tasks while hiding that complexity to present a simple interface.'^^[[~[source~]>>url:https://en.wikipedia.org/wiki/Magic_(programming)]]^^
63		-|Operating System (OS)|(% style="text-align:justify" %)(((
64		-It is the core system software that controls and coordinates all of the computer's resources. Examples are Windows, Mac OS and Linux.
65		-)))
	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.
66	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	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	|Rollback|The process of reverting a system or data to a previous snapshot.
69		-|Runtime|'At runtime' means the period of time during which the code is executed.
	67	+|Runtime|(((
	68	+(% style="text-align: justify;" %)
	69	+The period of time during which the code is executed. For example:
	70	+
	71	+* An exception is thrown by the compiler that finds invalid syntax in the source code. This is called a compile-time exception.
	72	+* 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.
	73	+)))
70	70	|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.
71	71	|[[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.
72	72	|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.
...	...	@@ -86,5 +86,4 @@
86	86	)))
87	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.
88	88	|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.
89		-|Virtual Machine (VM)|(% style="text-align:justify" %)A software emulation of a physical computer that can run its own OS and applications as if it were a separate physical machine.
90	90	|Wiring|(% style="text-align:justify" %)The process of generating and injecting dependencies to start an application, performed by the IoC container.