| ... |
... |
@@ -12,9 +12,9 @@ |
| 12 |
12 |
| Business | Non-technical decision makers in the organization developing the software. | |
| 13 |
13 |
| Business Value | The worth of a feature in terms of its benefit to the business. | |
| 14 |
14 |
| Compile Time | The period when the code is compiled. Often used to distinguish from runtime. | |
| 15 |
|
-| Concretion | 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. | |
|
15 |
+| Concretion | The counterpart to 'abstraction'. Concretion is also known as 'implementation'. In OOP, it 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. | |
| 16 |
16 |
| [[Constructor Injection|doc:Software Engineering.Architecture.Dependency Injection.Types of Dependency Injection.WebHome]] | A type of dependency injection in which dependencies are provided to an object through constructor arguments. | |
| 17 |
|
-| 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. | |
|
17 |
+| 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 have a CLI. | |
| 18 |
18 |
| Commitment | Binding promise to complete a specific task within a set period of time. | |
| 19 |
19 |
| 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. | |
| 20 |
20 |
| [[Continuous Integration|doc:Software Engineering.Agile.Extreme Programming.Continuous Integration.WebHome]] (CI) | See link. | |
| ... |
... |
@@ -56,7 +56,7 @@ |
| 56 |
56 |
| Programmer | Someone who writes and tests code. The knowledge level of a beginner. | |
| 57 |
57 |
| Requirement | Statement of what a software must be capable of doing, often outlining features, constraints, and success criteria. | |
| 58 |
58 |
| Resources | Refers to the assets used in the project, including time, money, staff, and effort. | |
| 59 |
|
-| Return of Investment (RoI) | Business value derived from implementing a story, minus the associated effort or cost. | |
|
59 |
+| Return of Investment (RoI) | The ratio of the business value gained from implementing a story to the effort/cost involved. A higher RoI means that something is more worth implementing than something with a low RoI. | |
| 60 |
60 |
| Rollback | The act of returning a system or data to a previous state, often using a snapshot. | |
| 61 |
61 |
| Rotting Code | Code that is increasingly difficult to maintain due to multiple changes that accumulate technical debt by not following best practices. | |
| 62 |
62 |
| Runtime | The period when the code is being executed. Often used to distinguish from compile time. | |
