Karteikarten
System design
Karten in diesem Stapel (7)
- 18 System design issues1. Identify design goals (non-functional)
2. Subsystem decomposition (functional)
3. Identify concurrency (dynamic)
4. Hardware/software mapping (object)
5. Persistent data management (object)
6. Global resource handling (dynamic)
7. Software control (dynamic)
8. Boundary conditions (functional) - 2Coupling and cohesionCohesion: dependencies among classes
Coupling: dependencies between subsystems
Low Coupling & High Cohesion - 3Architectural style vs. architecture (Subsystem decomposition)Subsystem decomposition: Identification, relationship to each other
Architectural style: Pattern for subsystem decomposition
Software architecture: Instance of an architectural style - 4Layered architectural style Layer:subsystem that provides service to another subsystem with restrictions
- Layer no knowledge of higher layer
- Layer only depends on service from lower layer - 5Client server achitectural styleOne or more servers provide services to instances of subsystem
Server does not know interface of server
Client knows interface of server
Response in general immediate - 6Design goals of Client-server srchitecture-Portability
-Location Transparency
-High Performance
-Scalability
-Flexibility
-Reliability - 7Model view controller (MVC) architectural styleModel (subsystem) -> updates View
responsible for application domain
View (subsystem) -> updates Model
displays information to user
Controller (subsystem) -> sends updates to Controller sub.
responsible for interacting with user & notifying views of changes in model
Informationen
- Beschreibung
- Der Nutzer hat seine Fachbereichs-Information gelöscht. Karteikarten am System design, erstellt von Gelöschter Nutzer am 15/09/2019.
- Erstellt von
- Gelöschter Nutzer · Sep 2019
- Aktualisiert
- 15 Sep 2019
- Aufrufe
- 25
- Verlauf
-
- Erstellt von Mikael Caselitz · 3 Sep 2019
- Kopiert von Mikael Caselitz · 15 Sep 2019
- Bewertung