| ... |
... |
@@ -48,7 +48,6 @@ |
| 48 |
48 |
| Separation of Concerns | A design principle suggesting that each module or component should have a single responsibility or concern, enhancing clarity and maintainability. | |
| 49 |
49 |
| [[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. | |
| 50 |
50 |
| Snapshot | A saved state of a system or data at a specific point in time. Can be used for rollbacks. | |
| 51 |
|
-| Software Engineer | Technical expert with in-depth knowledge in many areas, including high-level topics such as software architecture and system design. | |
| 52 |
52 |
| 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. | |
| 53 |
53 |
| System | Entirety of software components designed to work together effectively in a production environment. | |
| 54 |
54 |
| Test Code | Code that tests the functionality of production code. Does not contribute to the operational aspects of an application. | |
