| ... |
... |
@@ -14,7 +14,6 @@ |
| 14 |
14 |
| Command-Line Interface (CLI) | "[...] a means of interacting with a computer program by inputting lines of text [...]".^[[src](https://en.wikipedia.org/wiki/Command-line_interface)]^ For example, tools/commands used when working with a (Linux) terminal. | |
| 15 |
15 |
| Commitment | Binding promise to complete a specific task within a set period of time. | |
| 16 |
16 |
| Component | Often used to refer to a set of units, modules, or "architectural" components without a clearer specification. In software architecture, it refers to a module capable of independent operation, often compiled or packaged into an executable such as a `.jar` or `.exe` file. | |
| 17 |
|
-| [[Continuous Integration|doc:Software Engineering.Agile.Extreme Programming.Continuous Integration.WebHome]] (CI) | See link. | |
| 18 |
18 |
| Daemon | A program running in the background of a system, often without a GUI. | |
| 19 |
19 |
| Data Structure | 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. | |
| 20 |
20 |
| Dependency | In context of classes, a dependency is an object required by another object to perform its functions. Often, dependencies are provided via dependency injection. | |
| ... |
... |
@@ -47,7 +47,6 @@ |
| 47 |
47 |
| Resources | Refers to the assets used in the project, including time, money, staff, and effort. | |
| 48 |
48 |
| Return of Investment (RoI) | Business value derived from implementing a story, minus the associated effort or cost. | |
| 49 |
49 |
| Rollback | The act of returning a system or data to a previous state, often using a snapshot. | |
| 50 |
|
-| Rotting Code | Code that is increasingly difficult to maintain due to multiple changes that accumulate technical debt by not following best practices. | |
| 51 |
51 |
| Runtime | The period when the code is being executed. Often used to distinguish from compile time. | |
| 52 |
52 |
| Security | Measures implemented to protect systems from threats, unauthorized access, and vulnerabilities. This includes, but is not limited to, authentication, authorization, and encryption. | |
| 53 |
53 |
| Self-Containment | 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. | |
| ... |
... |
@@ -58,7 +58,6 @@ |
| 58 |
58 |
| Static | Behaviors/properties determined before or at compile time. Examples: static code analysis tools inspect source code; statically-typed languages determine an object's type at compile time. | |
| 59 |
59 |
| [[Story/User Story|doc:Software Engineering.Agile.Extreme Programming.Planning Game.WebHome]] | See link. | |
| 60 |
60 |
| System | Entirety of software components designed to work together effectively in a production environment. | |
| 61 |
|
-| Technical Debt | The implicit cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer. Often the result of poor design, testing, and refactoring. | |
| 62 |
62 |
| Test Code | Code that tests the functionality of production code. Does not contribute to the operational aspects of an application. | |
| 63 |
63 |
| 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. | |
| 64 |
64 |
| Test Suite | The sum of all the test code used to check that a system meets its requirements. | |
