Software Architecture (Fach) / Patterns & Tactics (Lektion)
In dieser Lektion befinden sich 4 Karteikarten
Description of Patterns (for example Layer Pattern) and Tactics in Software Architecture
Diese Lektion wurde von SebP90 erstellt.
- Tactics Def "Tactics are design decisions that influence the control of a QA response" Events -> "Tactics to control performance" -> Response generated within time constraint Examples for Performance tactics: Introduce concurreny Prioritize events Limit event response
- Availability Tactics Availability tactics enable a system to endure faults so that services remain compliant with their specifications. Goal:Detect, Recover and Prevent Faults Event -> Control Av. Tactics-> Fault Masked or Repair Made Examples: Ping/Echo Redundancy Exception Handling
- Modifiability Tactics Goal: controlling the complexity, time and cost of making changes Events -> Tactics to control Modif. -> Changes Made, Tested and Deployed within TIme and Budget Examples: Increase Semantic Coherence Reduce Coupling -> Encapsulation Split Modules
- Performance Tactics Goal: response to an event arriving at the system within some time-based constraint. Examples Limit event response Introduce concurrency Priorization of events