Changes for page Glossary

Summary

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

Details

Page properties

Content

...	...	@@ -10,9 +10,11 @@
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	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	+|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.
13	13	|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)'.
14	14	|Awareness|(% style="text-align:justify" %)A class A is aware of class B if it contains a reference to class B in its source code. If no such reference exists, class A is unaware of class B.
15	15	|Best Practices|(% style="text-align:justify" %)Widely accepted guidelines designed to enhance programming productivity and code quality. Adherence can prevent many potential issues.
	17	+|Business Logic|(% style="text-align:justify" %)Represents the core computations, data processing, and rules that form the backbone of a software application. It's independent of details such as data presentation, storage mechanisms, networking, third-party library and operating system interactions.
16	16	|Concretion|(% style="text-align:justify" %)The counterpart to 'abstraction', also known as 'implementation'. In OOP, refers to non-abstract classes that implement the methods of interfaces or abstract classes. A concretion provides the 'concrete' code defining the workings of these abstract functions.
17	17	|[[Constructor Injection>>doc:Software Engineering.Architecture.Dependency Injection.Types of Dependency Injection.WebHome]]|(% style="text-align:justify" %)A type of dependency injection in which dependencies are provided to an object through constructor arguments.
18	18	|Component|(((
...	...	@@ -36,7 +36,7 @@
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 set 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 etc. In contrast, a development environment is usually localized to a developer's PC, have software development tools installed, and does not the include some features of the production environment just mentioned.
	41	+|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.
40	40	|[[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.
41	41	|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.
42	42	|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.
...	...	@@ -48,7 +48,10 @@
48	48	|Operating System (OS)|(% style="text-align:justify" %)The foundational system software that manages and coordinates all computer resources. Examples include Windows, MacOS, and Linux.
49	49	|Pain|(% style="text-align:justify" %)An unpleasant experience caused by unnecessary efforts that could be mitigated with better code design.
50	50	|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.
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.
	53	+|Representation|(% style="text-align:justify" %)(((
	54	+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.
	55	+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.
	56	+)))
52	52	|Rollback|The act of returning a system or data to a previous state, often using a snapshot.
53	53	|Runtime|The period when the code is being executed.
54	54	|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.