Design Goals & System Decomposition

More documents

Recommendations

Info

Why is Design so Difficult? • Analysis: Focuses on the application domain • Design: Focuses on the solution domain • The solution domain is changing very rapidly • Halftime knowledge in software engineering: About 3-5 years • Cost of hardware rapidly sinking �Design knowledge is a moving target • Design window: Time in which design decisions have to be made. © 2006 Bernd Bruegge Software Engineering WS 2006/2007 4
The Scope of System Design • Bridge the gap • between a problem and an existing system in a manageable way • How? • Use Divide & Conquer: 1) Identify design goals 2) Model the new system design as a set of subsystems 3-8) Address the major design goals. © 2006 Bernd Bruegge Software Engineering WS 2006/2007 Problem System Design Existing System 5
Page 1 and 2: Design Goals & System Decomposition
Page 3: Design is Difficult • There are t
Page 7 and 8: Overview System Design I (This Lect
Page 9 and 10: From Analysis to 1. Design Goals De
Page 11 and 12: Stakeholders have different Design
Page 13 and 14: Subsystem Decomposition • Subsyst
Page 15 and 16: Subsystem Interfaces vs API • Sub
Page 17: Subsystem Interface Object • Good
Page 20 and 21: Example of a Subsystem Decompositio
Page 22 and 23: Example of a Bad Subsystem Decompos
Page 24 and 25: Virtual Machine • The terms layer
Page 26 and 27: Building Systems as a Set of Virtua
Page 28 and 29: Opaque Layering in ARENA Interface
Page 30 and 31: Properties of Layered Systems • L
Page 32 and 33: Coupling and Coherence of Subsystem
Page 34 and 35: How to achieve high Coherence • H
Page 36 and 37: Additional Readings • E.W. Dijkst

Design Goals & System Decomposition

Create successful ePaper yourself

Delete template?

Save as template?