19164492
Descripción
Fichas por Mikael Caselitz, actualizado hace más de 1 año
|
Creado por Mikael Caselitz
hace alrededor de 5 años
|
|
| Pregunta | Respuesta |
| 8 System design issues | 1. 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) |
| Coupling and cohesion | Cohesion: dependencies among classes Coupling: dependencies between subsystems Low Coupling & High Cohesion |
| Architectural 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 |
| Layered 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 |
| Client server achitectural style | One 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 |
| Design goals of Client-server srchitecture | -Portability -Location Transparency -High Performance -Scalability -Flexibility -Reliability |
| Model view controller (MVC) architectural style | Model (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 |
¿Quieres crear tus propias Fichas gratiscon GoConqr? Más información.