| ... |
... |
@@ -28,12 +28,10 @@ |
| 28 |
28 |
| Developer | Skilled programmer with advanced technical knowledge in areas such as software design, coding best practices, technical concepts, etc. | |
| 29 |
29 |
| Dirty (Code) | Code that is messy, unreadable, or poorly designed. | |
| 30 |
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 |
|
-| Dyad | A function with two arguments. | |
| 32 |
32 |
| Dynamic | Behaviors/properties determined at runtime. Examples: dynamic dependencies can be replaced at runtime; dynamically-typed languages determine an object's type at runtime. | |
| 33 |
33 |
| Entity | 1) In the OOP context, this means that two separately constructed objects of the same type, even with identical field values, are still distinct entities. 2) In software architecture, refers to classes representing application data models and core business logic. A banking application might have entity classes like Account, Order, Customer, or Employee with methods like `myCustomer.executeOrder(someOrder)`. | |
| 34 |
34 |
| Estimates | Intelligent guesses about the resources needed to complete a user story. It is not a binding promise as opposed to a commitment. | |
| 35 |
35 |
| [[Field Injection|doc:Software Engineering.Architecture.Dependency Injection.Types of Dependency Injection.WebHome]] | A type of dependency injection where a dependency is injected directly into an object's field via reflection, bypassing encapsulation. | |
| 36 |
|
-| Flag Argument | A flag argument is a boolean parameter passed to a function, signaling it to perform a specific operation or change its behavior based on the flag's true or false value. | |
| 37 |
37 |
| Functionality / Feature | An operation that a system can perform from the user's point of view. For example, the "login" functionality/feature on a website. | |
| 38 |
38 |
| Graphical User Interface (GUI) | A user interface that allows users to interact with the system through graphical elements like icons, buttons, windows, and menus. | |
| 39 |
39 |
| Isolation/Isolated | The opposite of integration. Isolation is the separation of a unit or component from the rest of the system in order to test, develop or understand it independently and ensure that it works correctly without external interference. For example, in unit testing, a single unit is usually tested independently of other units and is isolated from them. | |
| ... |
... |
@@ -42,7 +42,6 @@ |
| 42 |
42 |
| Integration/Integrated | 1) The opposite of isolation. Integration is the process of combining different software units or components to work together as a single, cohesive system. For example, component testing is more integrated than unit testing because it involves multiple units working together. Integration testing tests the interaction between two components. 2) (Code) Integration, another term for merging code, usually into the main branch. See also 'Continuous Integration'. | |
| 43 |
43 |
| [[Inversion of Control|doc:Software Engineering.Architecture.Dependency Injection.Dependency Injection Explained.WebHome]] (IoC) | A design principle that encourages the delegation of application unit wiring to a computer algorithm that facilitates dependency injection, rather than the developer implementing this logic manually. | |
| 44 |
44 |
| Module | 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. Many languages provide modularization features such as [Go modules](https://go.dev/blog/using-go-modules) or [Java modules](https://www.oracle.com/corporate/features/understanding-java-9-modules.html). | |
| 45 |
|
-| Monad | A function with one argument. | |
| 46 |
46 |
| Layer | Level of abstraction in a system where related functionality is grouped together. For example, in a horizontally layered architecture, there is a controller layer consisting of controllers that are technically similar because they translate HTTP requests into data structures and vice versa. | |
| 47 |
47 |
| Logic | A set of instructions that determines how a program operates based on given inputs or conditions. Thus, basically any source code can be considered logic. | |
| 48 |
48 |
| Logical | The counterpart to physical. The abstract representation of something in software. For example, deleting a file from the desktop only logically deletes it, but actually moves it to the Recycle Bin, while the file physically remains on disk until the Recycle Bin is emptied. | |
| ... |
... |
@@ -83,7 +83,6 @@ |
| 83 |
83 |
| Test-Driven Development (TDD) | A development approach where code is written in small increments, with tests defining functionality written at the beginning of each coding iteration. | |
| 84 |
84 |
| Test Suite | The sum of all the test code used to check that a system meets its requirements. | |
| 85 |
85 |
| Testability | Code is testable, or has good testability, if it is easy to write tests for. | |
| 86 |
|
-| Triad | A function with three arguments. | |
| 87 |
87 |
| Unit | The smallest testable part of an application. This is often a single class, but can also be a single function, or a small cluster of tightly coupled classes or functions that together perform a specific task. | |
| 88 |
88 |
| [[Velocity|doc:Software Engineering.Agile.Extreme Programming.Planning Game.Agile and Data.WebHome]] | See link. | |
| 89 |
89 |
| Virtual Machine (VM) | A software emulation of a physical computer, able to run its own OS and applications as if it were a separate physical machine. | |
