| ... |
... |
@@ -60,10 +60,10 @@ |
| 60 |
60 |
| Problem Domain | The language/terminology used to describe the software requirements ("the problems") from the perspective of non-technical stakeholders. | |
| 61 |
61 |
| Production Code | Code that comprises the functioning part of an application, as opposed to test code. | |
| 62 |
62 |
| Programmer | Someone who writes and tests code. The knowledge level of a beginner. | |
| 63 |
|
-| Refactoring | Modifying code to improve its quality without changing its functionality. It is a subtype of 'Restructuring'. | |
|
63 |
+| Refactoring | Modifying code to improve its quality without changing its functionality. It is a subtype of 'Restructuring'. Often used as: 'to refactor code'. | |
| 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 |
|
-| Restructuring | Modifying code to change its functionality, or to improve its quality or performance. | |
|
66 |
+| Restructuring | Modifying code to improve some aspect of it, such as its quality or performance. | |
| 67 |
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. | |
