| ... |
... |
@@ -64,7 +64,7 @@ |
| 64 |
64 |
| Requirement | Statement of what a software must be capable of doing, often outlining features, constraints, and success criteria. | |
| 65 |
65 |
| Resources | Refers to the assets used in the project, including time, money, staff, and effort. | |
| 66 |
66 |
| Restructuring | Modifying code to change its functionality, or to improve its quality ('refactoring') or performance ('performance optimization'). | |
| 67 |
|
-| 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. | |
|
67 |
+| 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. | |
| 68 |
68 |
| Rollback | The act of returning a system or data to a previous state, often using a snapshot. | |
| 69 |
69 |
| Rotting Code | Code that is increasingly difficult to maintain due to multiple changes that accumulate technical debt by not following best practices. | |
| 70 |
70 |
| Runtime | The period when the code is being executed. Often used to distinguish from compile time. | |
