| ... |
... |
@@ -76,7 +76,7 @@ |
| 76 |
76 |
| Snapshot | A saved state of a system or data at a specific point in time. Can be used for rollbacks. | |
| 77 |
77 |
| Software Engineer | Technical expert with in-depth knowledge in many areas, including high-level topics such as software architecture and system design. | |
| 78 |
78 |
| Solution Domain | The language/terminology used by technical experts to describe the technical solutions to the software requirements defined by the problem domain. | |
| 79 |
|
-| Specification | A detailed technical description of the requirements under which a user story is considered complete. Much more detailed than the original user story. | |
|
79 |
+| Specification | A detailed description of the requirements under which a user story is considered complete. Much more detailed than the original user story. | |
| 80 |
80 |
| Stakeholders | Individuals with an interest in the success of a software project, which may include customers, developers, investors, externals and others who are affected by the projects outcome. | |
| 81 |
81 |
| 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. | |
| 82 |
82 |
| [[Story / User Story|doc:Software Engineering.Agile.Extreme Programming.Planning Game.WebHome]] | See link. | |
