4 - Architecture Flashcards
KISS
avoid distributed responsibilities + small teams + think in interfaces
System Integration
requires modularity principles (interaction relation/interfaces/behavior)
Specialist Perspective
illustrates concepts of application domain + shows relation between subsystems/interfaces/behaviour + described by CRC-Cards or UML/SysML
Encapsultion
Specifying behavior which is visible from environment
Role Dependent Views
Developer View (development and integration) + Test View (design/development of test env) + Implementation View (executables/hardware cmoponents)
Deployment Perspective
illustrates deployment of components on HW at runtime + shows component mapping + described by UML deployment diagram
Composition
Synthesis of subsystem
Architecture Description serves as …
communication platform + design/implementation plan + basis for project planning
Architecture
fundamental organization of a system & interface for future extensions & ensures desired requirements
Stakeholders
User (functionality) + Management (effectivity) + Developer (implementation) + Marketing (performance) + Organization + …
Role of Architecture within System Life-Cycle
Organization (Division of labor) + Development Process (Structure/Integration) + Operational (Deployment/Monitoring) + Maintenance (Impact Analysis)
Technical Perspective
illustrates technical solution for the system including its realization + shows technical system/interfaces/relation + described by SysML IBD or source code
Architectural Goals
describe states as abstract as possible (information hiding) + model only methods that are relevant for interaction + low coupling
Distributed Systems
parallel composition of subsystems (parallel vs. interleaved execution)
