| ... |
... |
@@ -28,7 +28,6 @@ |
| 28 |
28 |
| Functionality | An operation that a system can perform from the user's point of view. For example, the "login" functionality on a website. | |
| 29 |
29 |
| Graphical User Interface (GUI) | A user interface that allows users to interact with the system through graphical elements like icons, buttons, windows, and menus. | |
| 30 |
30 |
| 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. | |
| 31 |
|
-| [[Iteration|doc:Software Engineering.Agile.Extreme Programming.Planning Game.WebHome]] | A short development cycle, often 2 weeks, that starts with planning, continues with implementing stories and ends a new product release and with feedback. | |
| 32 |
32 |
| Implementation | The counterpart to behavior. It refers to the internal code that achieves a desired behavior of a component. For example, a sorting function might be implemented with a QuickSort algorithm. | |
| 33 |
33 |
| Integration/Integrated | The opposite of isolation. Integration is the process of combining different software units or components to work together as a single, cohesive system. For example, component testing is more integrated than unit testing because it involves multiple units working together. Integration testing tests the interaction between two components. | |
| 34 |
34 |
| [[Inversion of Control|doc:Software Engineering.Architecture.Dependency Injection.Dependency Injection Explained.WebHome]] (IoC) | A design principle that encourages the delegation of application unit wiring to a computer algorithm that facilitates dependency injection, rather than the developer implementing this logic manually. | |
