Software Architecture (Fach) / SA01 - Basics (Lektion)
In dieser Lektion befinden sich 7 Karteikarten
Grundlagen von SW Architekturen - nach "Software Architecture in Practice" von Kazman
Diese Lektion wurde von SebP90 erstellt.
- SA Definition & Implications of it SA of a system is the set of structures needed to reason about the system, which compromises software elements, relations among them, and properties of both. Implications: SA is an abstraction Abstraction can be used for taming complexity No internal details of elements A system can have many structures (s. structures) Runtime and Non-runtime elements SA has to be documented Box and Line Drawings are NOT complete architectures (missing behaviour, specificatins and properties of elements & relationships) Good Architecture = Architecture that meets its Quality Attributes and Lifecycle Rqmts.
- Archtitectural pattern Def Description of element and relationship types and a set of constaints of how they are used# Define families of architectures SW elements composed in a way to solve particular problems Types: Module, Component & Connector, Allocatio
- Reference Model Def Divison of functionality into elements and dataflow between them
- Reference Architecture Def A reference model mapped onto software Not necessarily a 1to1 mapping standard tools & templates are used
- Common Component & Connector (C&C) Patterns 1. Shared data pattern 2. Client Server Pattern
- Common allocation patterns 1. Multi-Tier: Distribution and allocation of components of a system in distinct subsets of HW and SW connected by some communicatiom medium 2. Competence Center Pattern: Define a SW systems work structure 2.1 CC Pattern: Allocate to site depending on expertise 2.2 Platform Pattern: One site develops reusable core assets; the other site develops applications using this reusable assets
- Module structure Partition system into implementation units (=modules) are assigned with specific functional responsibility Questions answered: Responsibilites of modules What other elements a module can use Dependencies and relations to óther modules No runtime focus!