Checklist: Design Subsystem
This checklist helps make sure that a Design Subsystem decomposition is correct and complete.
Expand All SectionsExpand All Sections    Collapse All SectionsCollapse All Sections
CollapseRelationships  
Related Elements
Back to topBack to top
CollapseMain Description  
 
Back to topBack to top
CollapseCheck Items  
Expand All Check ItemsExpand All Check Items Collapse All Check ItemsCollapse All Check Items
Expand The name of each subsystem is unique and descriptive of the collective responsibilities of the subsystem  
Expand The subsystem description accurately reflects the collective responsibilities of the subsystem  
Expand The subsystem, through its interfaces, presents a single, logically consistent set of services  
Expand The subsystem is the responsibility of a single individual or team  
ExpandThe subsystem realizes at least one interface  
Expand The interfaces realized by the subsystem are clearly identified and the dependencies are correctly documented  
ExpandThe subsystem's dependencies on other model elements is restricted to interfaces and packages to which the subsystem has a compilation dependency  
Expand The information needed to effectively use the subsystem is documented in the subsystem facade  
Expand Other than the interfaces realized by the subsystem, the subsystem's contents are completely encapsulated  
Expand Each operation on an interface realized by the subsystem is utilized in some collaboration  
Expand Each operation on an interface realized by the subsystem is realized by a model element (or a collaboration of model elements) within the subsystem  
ExpandSubsystem partitioning done in a logically consistent way across the entire model  
ExpandThe contents of the subsystem are fully encapsulated behind its interfaces  
Back to topBack to top

©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.