Changes for page Glossary

Summary

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

Details

Page properties

Content

...	...	@@ -8,7 +8,7 @@
8	8	|**Term**|(% style="text-align:justify" %)**Explanation**
9	9	|Abstraction|(% style="text-align:justify" %)(((
10	10	1. The counterpart to 'Concretion', refers to interfaces and abstract classes that define behavior (function signatures) but leave the internal operation of these functions undefined.
11		-1. A higher-level, generalized unit of code. For example, duplication across multiple functions can be resolved by creating an 'abstraction' - a separate function containing the shared code.
	11	+1. A higher-level, generalized unit of code. Duplication across multiple functions can be resolved by creating an 'abstraction' - a separate function containing the shared code. This adheres to the DRY principle.
12	12	)))
13	13	|Architecture|(% style="text-align:justify" %)Refers to the overall structure of a software system. It defines the components of the system, their interactions, and the design rules that govern them. Its purpose is to ensure that the system meets its requirements while promoting maintainability, scalability, and minimizing the cost of development and evolution over time.
14	14	|Assertion|(% style="text-align:justify" %)Pertains to an assertion function, a crucial part of testing. If the input values don't satisfy a certain condition, the test containing the assertion fails. Example: 'assertEquals(expectedResult, actualResult)'.
...	...	@@ -26,10 +26,9 @@
26	26	|Dependency|(% style="text-align:justify" %)In context of classes, a dependency is an object required by another object to perform its functions. Often, dependencies are provided via [[dependency injection>>doc:Software Engineering.Architecture.Dependency Injection.WebHome]].
27	27	|Dependency Cycle|(% style="text-align:justify" %)A situation where two or more classes depend on each other to be instantiated. This situation creates a circular dependency that makes object creation impossible. The dependency graph should be a directed acyclic graph rather than a cycle.
28	28	|[[Dependency Injection>>doc:Software Engineering.Architecture.Dependency Injection.WebHome]] (DI)|(% style="text-align:justify" %)A technique where an object's dependencies are provided from outside, rather than being created within the object itself.
29		-|Dirty|(% style="text-align:justify" %)Code that is messy, unreadable, or poorly designed. Often refers to 'quick-and-dirty' code written under time pressure.
30		-|Distribution|(% style="text-align:justify" %)A version of an OS packaged with specific software and configurations, designed for specific use cases. Examples: Ubuntu, Fedora, and Arch Linux, all based on Linux.
	29	+|Dirty|Code that is messy, unreadable, or poorly designed. Often refers to 'quick-and-dirty' code written under time pressure.
	30	+|Distribution|A version of an OS packaged with specific software and configurations, designed for specific use cases. Examples: Ubuntu, Fedora, and Arch Linux, all based on Linux.
31	31	|Dynamic|(((
32		-(% style="text-align: justify;" %)
33	33	Pertains to behaviors or properties determined at runtime. Examples: dynamic dependencies can be replaced at runtime; dynamically-typed languages determine an object's type at runtime.
34	34	)))
35	35	|Entity|(((
...	...	@@ -55,17 +55,17 @@
55	55	1. Often used when discussing the specific ways in which data or objects are implemented or modeled within a program or displayed in a GUI.
56	56	1. Less commonly, it refers to a specific implementation of an abstract data type or object. It's the actual, concrete realization of an abstract concept or structure. Can be used interchangeably with the term 'concretion' in this sense.
57	57	)))
58		-|Rollback|(% style="text-align:justify" %)The act of returning a system or data to a previous state, often using a snapshot.
59		-|Runtime|(% style="text-align:justify" %)The period when the code is being executed.
	57	+|Rollback|The act of returning a system or data to a previous state, often using a snapshot.
	58	+|Runtime|The period when the code is being executed.
60	60	|Self-Containment|(% style="text-align:justify" %)The ability of software to operate independently, without dependence on external services or factors. This characteristic ensures that its results are determined solely by its source code, which promotes stability and consistency.
61	61	|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.
62	62	|[[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.
63		-|Snapshot|(% style="text-align:justify" %)A saved state of a system or data at a specific point in time. Can be used for rollbacks.
	62	+|Snapshot|A saved state of a system or data at a specific point in time. Can be used for rollbacks.
64	64	|Spring Bean|(((
65	65	(% style="text-align: justify;" %)
66	66	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.
67	67	)))
68		-|Static|(% style="text-align:justify" %)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.
	67	+|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.
69	69	|Test Code|(% style="text-align:justify" %)Code that tests the functionality of production code. Does not contribute to the operational aspects of an application.
70	70	|Test-Driven Development (TDD)|(% style="text-align:justify" %)A development approach where code is written in small increments, with tests defining functionality written before each coding iteration.
71	71	|Unit|(% style="text-align:justify" %)The smallest testable part of an application. This is often a single class, method or module, but can also be a small cluster of tightly coupled classes or functions that together perform a specific functionality.