Changes for page Glossary

Summary

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

Details

Page properties

Content

...	...	@@ -36,11 +36,12 @@
36	36	(% style="text-align: justify;" %)
37	37	2. In software architecture, refers to classes representing application data models. A banking application might have entity classes like Account, Order, Customer, or Employee.
38	38	)))
	39	+|Environment|(% style="text-align:justify" %)Refers to the specific sets of infrastructure on which software applications run, intended for different purposes. For example, a production environment typically runs on secure, off-site servers, is accessible to end users, stores customer data, and so on. In contrast, a development environment is typically localized to a developer's PC, has software development tools installed, and lacks some of the production environment features.
39	39	|[[Field 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 injected directly into an object's field via reflection, bypassing encapsulation.
40	40	|Graphical User Interface (GUI)|(% style="text-align:justify" %)A user interface that allows users to interact with the system through graphical elements like icons, buttons, windows, and menus.
41	41	|In-Memory|(% style="text-align:justify" %)In-memory refers to storing and processing data directly in a computer's random access memory (RAM) and is faster than traditional disk storage. However, it lacks data persistence. Examples include in-memory databases or the Linux temporary file system (tmpfs), which are often used in development environments where there is no need to store critical data.
42	42	|[[Inversion of Control>>doc:Software Engineering.Architecture.Dependency Injection.Dependency Injection Explained.WebHome]] (IoC)|(% style="text-align:justify" %)A design principle that delegates a program's control flow to a separate container or framework that "wires" application components together, facilitating [[dependency injection>>doc:Software Engineering.Architecture.Dependency Injection.WebHome]]. An IoC container, as found in the Spring Framework, is a common tool for implementing this principle.
43		-|JavaBean|A design convention for data structures. Typically, a class with a public no-argument constructor, private fields, and getter/setter methods for each field. Often followed by DTOs and entities.
	44	+|JavaBean|(% style="text-align:justify" %)A design convention for data structures. Typically, a class with a public no-argument constructor, private fields, and getter/setter methods for each field. Often followed by DTOs and entities.
44	44	|Module|(% style="text-align:justify" %)A distinct part of a software that encapsulates specific implementation details, such as functions, data structures, classes, interfaces, or even other modules. It exposes a concise API designed to perform specific tasks. These modules are typically crafted for reusability and improved code organization, thereby promoting a modular design.
45	45	|Logic|(% style="text-align:justify" %)Code with non-trivial complexity. For instance, getters and setters have trivial complexity and are usually not considered 'logic'.
46	46	|Magic|(% style="text-align:justify" %)Code that performs complex tasks while abstracting away the complexity, presenting a simple interface to the user.
...	...	@@ -47,7 +47,7 @@
47	47	|Operating System (OS)|(% style="text-align:justify" %)The foundational system software that manages and coordinates all computer resources. Examples include Windows, MacOS, and Linux.
48	48	|Pain|(% style="text-align:justify" %)An unpleasant experience caused by unnecessary efforts that could be mitigated with better code design.
49	49	|Production Code|(% style="text-align:justify" %)Production code forms the software that meets the requirements of the project. It is the code that is deployed in a production environment and used by end users.
50		-|Representation|Refers to a specific implementation of an abstract data type or an object. It's the actual, concrete realization of an abstract concept or structure.
	51	+|Representation|(% style="text-align:justify" %)Refers to a specific implementation of an abstract data type or an object. It's the actual, concrete realization of an abstract concept or structure. Can be used interchangeably with the term 'concretion' in this sense.
51	51	|Rollback|The act of returning a system or data to a previous state, often using a snapshot.
52	52	|Runtime|The period when the code is being executed.
53	53	|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.
...	...	@@ -55,6 +55,7 @@
55	55	|[[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.
56	56	|Snapshot|A saved state of a system or data at a specific point in time. Can be used for rollbacks.
57	57	|Spring Bean|(((
	59	+(% style="text-align: justify;" %)
58	58	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.
59	59	)))
60	60	|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.