| ... |
... |
@@ -46,12 +46,10 @@ |
| 46 |
46 |
| Magic | Code that performs complex tasks while abstracting away the complexity, presenting a simple interface to the user. | |
| 47 |
47 |
| Manager | Individuals responsible for planning, organizing, leading, and controlling a software project's resources, schedule, and deliverables to meet stakeholder expectations. | |
| 48 |
48 |
| Operating System (OS) | The foundational system software that manages and coordinates all computer resources. Examples are Windows, MacOS and Linux. | |
| 49 |
|
-| Overloaded | Some programming languages offer the feature of overloading, which means that two operators with the same name can be distinguished if they have different signatures. For example, these two functions are overloaded: `tripleNumber(n: float)` and `tripleNumber(n: int)`. | |
| 50 |
50 |
| Pain | An unpleasant experience caused by unnecessary efforts that could have been mitigated with better design of the original code. | |
| 51 |
51 |
| [[Pair Programming|doc:Software Engineering.Agile.Extreme Programming.Pair Programming.WebHome]] / Pairing (up) | See link. | |
| 52 |
52 |
| Physical | Counterpart to logical. Refers to hardware. For example, physically deleting a file means removing it from the disk. | |
| 53 |
53 |
| Points / Story Points | A unit of measure used to estimate the effort required to complete a user story. See also [[here|doc:Software Engineering.Agile.Extreme Programming.Planning Game.Effort Estimation.WebHome]]. | |
| 54 |
|
-| Problem Domain | The language/terminology used to describe the software requirements ("the problems") from the perspective of non-technical stakeholders. | |
| 55 |
55 |
| Production Code | Code that comprises the functioning part of an application, as opposed to test code. | |
| 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. | |
| ... |
... |
@@ -67,7 +67,6 @@ |
| 67 |
67 |
| [[Setter Injection|doc:Software Engineering.Architecture.Dependency Injection.Types of Dependency Injection.WebHome]] | A type of dependency injection where a dependency is provided to an object through a setter method. | |
| 68 |
68 |
| Snapshot | A saved state of a system or data at a specific point in time. Can be used for rollbacks. | |
| 69 |
69 |
| Software Engineer | Technical expert with in-depth knowledge in many areas, including high-level topics such as software architecture and system design. | |
| 70 |
|
-| Solution Domain | The language/terminology used by technical experts to describe the technical solutions to the software requirements described by the problem domain. | |
| 71 |
71 |
| Specification | A detailed description of the requirements under which a user story is considered complete. Much more detailed than the original user story. | |
| 72 |
72 |
| 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. | |
| 73 |
73 |
| 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. | |
| ... |
... |
@@ -79,8 +79,7 @@ |
| 79 |
79 |
| Test Code | Code that tests the functionality of production code. Does not contribute to the operational aspects of an application. | |
| 80 |
80 |
| Test-Driven Development (TDD) | A development approach where code is written in small increments, with tests defining functionality written at the beginning of each coding iteration. | |
| 81 |
81 |
| Test Suite | The sum of all the test code used to check that a system meets its requirements. | |
| 82 |
|
-| Testability | Code is testable, or has good testability, if it is easy to write tests for. | |
| 83 |
|
-| Unit | The smallest testable part of an application. This is often a single class, but can also be a single function, or a small cluster of tightly coupled classes or functions that together perform a specific task. | |
|
79 |
+| Unit | The smallest testable part of an application. This is often a single class, but can also be a single method, or a small cluster of tightly coupled classes or functions that together perform a specific task. | |
| 84 |
84 |
| [[Velocity|doc:Software Engineering.Agile.Extreme Programming.Planning Game.Agile and Data.WebHome]] | See link. | |
| 85 |
85 |
| 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. | |
| 86 |
86 |
| [[Waterfall|doc:Software Engineering.Agile.Problems of Waterfall.WebHome]] | See link. | |
