Checklist: Design Model








var backPath = './../../../';
var imgPath = './../../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_QV4x0AISEdqTna4sZVFRow", "_kjFBYN7HEdm8G6yT7-Wdqw", "{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}", "1.4639852935143625E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_kjFBYN7HEdm8G6yT7-Wdqw", "{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}", "1.4639852935143625E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_mTMIkN7REdmjRZts2c4ZjQ", "{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}", "1.4639852935143625E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_jD8dUAIbEdqEutyfYo0quQ", "_wl69ADIdEdqDs_9ORT1Rig", "1.4639852935143625E-305"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', true, false, false);

//override the subsection text
contentPage.subSection.expandAllText = 'Expand All Check Items';
contentPage.subSection.collapseAllText = 'Collapse All Check Items';










Checklist: Design Model















This checklist helps make sure that a the Design Model is specified correctly.






Relationships



Related Elements


Design Model






Main Description







Check Items




General



The objectives of the model are clearly stated and visible. The model is at an appropriate level of detail given the model objectives. The model's use of modeling constructs is appropriate to the problem at hand. The model is as simple as possible while still achieving the goals of the model. The model appears to be able to accommodate reasonably expected future changes. The design is appropriate to the task at hand (neither too complex nor too advanced). The design appears to be understandable and maintainable. The design appears to be implementable.



Layers



There are no more than seven (plus or minus two) layers. The rationale for layer definition is clearly presented and consistently applied. Layer boundaries are respected within the design. Layers are used to encapsulate conceptual boundaries between different kinds of services and provide useful abstractions which makes the design easier to understand.









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







contentPage.onload();