Subsystem Structuring
- Structuring Criterion: Principles hhigh coupling within a subsystem and low coupling between subsystemsh
- Aggregate/composite object: objects that are part of the same aggregate or composite object should be in the same subsystem
- Geographical locationFIf two objects could potentially be physically separated in different locations, they should be in different subsystems to reduce communication cost
- Clients and servers must be In separate subsystems
- User interface objects are usually clients
- A control objects and all the entity and interface objects it directly controls should all be part of one subsystem