... |
... |
@@ -59,7 +59,6 @@ |
59 |
59 |
| Problem Domain | The language/terminology used to describe the software requirements ("the problems") from the perspective of non-technical stakeholders. | |
60 |
60 |
| Production Code | Code that comprises the functioning part of an application, as opposed to test code. | |
61 |
61 |
| Programmer | Someone who writes and tests code. The knowledge level of a beginner. | |
62 |
|
-| Refactoring | Modifying code to improve its quality without changing its functionality. | |
63 |
63 |
| Requirement | Statement of what a software must be capable of doing, often outlining features, constraints, and success criteria. | |
64 |
64 |
| Resources | Refers to the assets used in the project, including time, money, staff, and effort. | |
65 |
65 |
| 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. | |
... |
... |
@@ -91,5 +91,4 @@ |
91 |
91 |
| [[Velocity|doc:Software Engineering.Agile.Extreme Programming.Planning Game.Agile and Data.WebHome]] | See link. | |
92 |
92 |
| 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. | |
93 |
93 |
| [[Waterfall|doc:Software Engineering.Agile.Problems of Waterfall.WebHome]] | See link. | |
94 |
|
-| Whispers | Vague comments in the source code that imply code problems without clearly explaining or addressing them. | |
95 |
95 |
| Wiring | The process conducted by the IoC container to create and inject dependencies, facilitating application startup. | |