Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% class="box infomessage" %) | ||
| 2 | ((( | ||
| 3 | (% style="text-align: justify;" %) | ||
| 4 | The explanations given here do not claim to be complete. They merely serve as a brief description to give an idea of the respective term. For more detailed information, the Internet should be consulted. Note that some of these technical terms are fuzzy, overlap with other terms, or have different meanings depending on the context or the people using them. This Glossary is an attempt to structure these terms in a concise manner. Be open to variations as you talk and work with other developers. | ||
| 5 | ))) | ||
| 6 | |||
| 7 | |||
| 8 | |**Term**|(% style="text-align:justify" %)**Explanation** | ||
| 9 | |Abstraction|(% style="text-align:justify" %)((( | ||
| 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. 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 | ))) | ||
| 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 | |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 | |Best Practices|(% style="text-align:justify" %)Widely accepted guidelines designed to enhance programming productivity and code quality. Adherence can prevent many potential issues. | ||
| 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 | |[[Constructor Injection>>doc:Software Engineering.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 | |Component|((( | ||
| 19 | 1. In Spring, a generic annotation for a bean that doesn't fit other specific Spring bean annotations: '@Component'. | ||
| 20 | 1. In software architecture, a module capable of independent operation, often compiled or packaged into an executable such as a .jar or .exe file. | ||
| 21 | ))) | ||
| 22 | |Daemon|(% style="text-align:justify" %)A program running in the background of a system, typically without a GUI. | ||
| 23 | |Data Structure|(% style="text-align:justify" %)A class primarily meant to hold data and provide basic operations to access and manipulate that data. May contain only public fields, or private fields with associated getter and setter methods. | ||
| 24 | |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.Dependency Injection.WebHome]]. | ||
| 25 | |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. | ||
| 26 | |[[Dependency Injection>>doc:Software Engineering.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. | ||
| 27 | |Dirty|Code that is messy, unreadable, or poorly designed. Often refers to 'quick-and-dirty' code written under time pressure. | ||
| 28 | |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. | ||
| 29 | |Dynamic|((( | ||
| 30 | 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. | ||
| 31 | ))) | ||
| 32 | |Entity|((( | ||
| 33 | (% style="text-align: justify;" %) | ||
| 34 | ~1. In object context, this signifies that two objects of the same type, even with identical field values, are still distinct entities. | ||
| 35 | |||
| 36 | (% style="text-align: justify;" %) | ||
| 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 | ))) | ||
| 39 | |[[Field Injection>>doc:Software Engineering.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 | |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 | |[[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.Dependency Injection.WebHome]]. An IoC container, as found in the Spring Framework, is a common tool for implementing this principle. | ||
| 42 | |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. | ||
| 43 | |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. | ||
| 44 | |Logic|(% style="text-align:justify" %)Code with non-trivial complexity. For instance, getters and setters have trivial complexity and are usually not considered 'logic'. | ||
| 45 | |Magic|(% style="text-align:justify" %)Code that performs complex tasks while abstracting away the complexity, presenting a simple interface to the user. | ||
| 46 | |Operating System (OS)|(% style="text-align:justify" %)The foundational system software that manages and coordinates all computer resources. Examples include Windows, MacOS, and Linux. | ||
| 47 | |Pain|(% style="text-align:justify" %)An unpleasant experience caused by unnecessary efforts that could be mitigated with better code design. | ||
| 48 | |Production Code|(% style="text-align:justify" %)Code that comprises the functioning part of an application, as opposed to test code. | ||
| 49 | |Rollback|The act of returning a system or data to a previous state, often using a snapshot. | ||
| 50 | |Runtime|The period when the code is being executed. | ||
| 51 | |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. | ||
| 52 | |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. | ||
| 53 | |[[Setter Injection>>doc:Software Engineering.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. | ||
| 54 | |Snapshot|A saved state of a system or data at a specific point in time. Can be used for rollbacks. | ||
| 55 | |Spring Bean|((( | ||
| 56 | 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. | ||
| 57 | ))) | ||
| 58 | |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. | ||
| 59 | |Test Code|(% style="text-align:justify" %)Code that tests the functionality of production code. Does not contribute to the operational aspects of an application. | ||
| 60 | |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. | ||
| 61 | |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. | ||
| 62 | |Virtual Machine (VM)|(% style="text-align:justify" %)A software emulation of a physical computer, able to run its own OS and applications as if it were a separate physical machine. | ||
| 63 | |Wiring|(% style="text-align:justify" %)The process conducted by the IoC container to create and inject dependencies, facilitating application startup. |