| ... |
... |
@@ -26,7 +26,7 @@ |
| 26 |
26 |
| Entity | 1) In the OOP context, this means that two separately constructed objects of the same type, even with identical field values, are still distinct entities. 2) In software architecture, refers to classes representing application data models and core business logic. A banking application might have entity classes like Account, Order, Customer, or Employee with methods like `myCustomer.executeOrder(someOrder)`. | |
| 27 |
27 |
| Estimates | Intelligent guesses about the resources needed to complete a task. No binding promises as opposed to commitments. | |
| 28 |
28 |
| [[Field Injection|doc:Software Engineering.Architecture.Dependency Injection.Types of Dependency Injection.WebHome]] | A type of dependency injection where a dependency is injected directly into an object's field via reflection, bypassing encapsulation. | |
| 29 |
|
-| Functionality / Feature | An operation that a system can perform from the user's point of view. For example, the "login" functionality/feature on a website. | |
|
29 |
+| Functionality | An operation that a system can perform from the user's point of view. For example, the "login" functionality on a website. | |
| 30 |
30 |
| Graphical User Interface (GUI) | A user interface that allows users to interact with the system through graphical elements like icons, buttons, windows, and menus. | |
| 31 |
31 |
| Isolation/Isolated | The opposite of integration. Isolation is the separation of a unit or component from the rest of the system in order to test, develop or understand it independently and ensure that it works correctly without external interference. For example, in unit testing, a single unit is usually tested independently of other units and is isolated from them. | |
| 32 |
32 |
| [[Iteration|doc:Software Engineering.Agile.Extreme Programming.Planning Game.WebHome]] | See link. | |
| ... |
... |
@@ -54,7 +54,6 @@ |
| 54 |
54 |
| Snapshot | A saved state of a system or data at a specific point in time. Can be used for rollbacks. | |
| 55 |
55 |
| Software Engineer | Technical expert with in-depth knowledge in many areas, including high-level topics such as software architecture and system design. | |
| 56 |
56 |
| 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. | |
| 57 |
|
-| [[Story/User Story|doc:Software Engineering.Agile.Extreme Programming.Planning Game.WebHome]] | See link. | |
| 58 |
58 |
| System | Entirety of software components designed to work together effectively in a production environment. | |
| 59 |
59 |
| Test Code | Code that tests the functionality of production code. Does not contribute to the operational aspects of an application. | |
| 60 |
60 |
| 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. | |
| ... |
... |
@@ -61,5 +61,4 @@ |
| 61 |
61 |
| Test Suite | The sum of all the test code used to check that a system meets its requirements. | |
| 62 |
62 |
| Unit | The smallest testable part of an application. This is often a single class, method or module, but can also be a small cluster of tightly coupled classes or functions that together perform a specific functionality. | |
| 63 |
63 |
| 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. | |
| 64 |
|
-| [[Waterfall|doc:Software Engineering.Agile.Problems of Waterfall.WebHome]] | See link. | |
| 65 |
65 |
| Wiring | The process conducted by the IoC container to create and inject dependencies, facilitating application startup. | |
