Artifact: Design Package
var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_qwxC8N7YEdmjRZts2c4ZjQ", "{DB21F5EF-810B-4994-B120-79FA8774FA9D}", "{80CC5437-F481-487B-A69B-957D9D236D8D}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_QV4x0AISEdqTna4sZVFRow", "_kjFBYN7HEdm8G6yT7-Wdqw", "{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}", "{80CC5437-F481-487B-A69B-957D9D236D8D}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_qwxC8N7YEdmjRZts2c4ZjQ", "{DB21F5EF-810B-4994-B120-79FA8774FA9D}", "{80CC5437-F481-487B-A69B-957D9D236D8D}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_kjFBYN7HEdm8G6yT7-Wdqw", "{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}", "{80CC5437-F481-487B-A69B-957D9D236D8D}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_mTMIkN7REdmjRZts2c4ZjQ", "{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}", "{80CC5437-F481-487B-A69B-957D9D236D8D}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_n7ZcgN7REdmjRZts2c4ZjQ", "{80CC5437-F481-487B-A69B-957D9D236D8D}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
Artifact: Design Package
This work product is a collection of classes, relationships, design use-case realizations, diagrams, and other packages. It is used to structure the design model by dividing it into smaller parts.
Work Product Kinds: Model Element
Purpose
Design packages are used to group related Design Model elements together for organizational purposes, and often for
configuration management. Unlike the Artifact: Design Subsystem, a design package does not offer a formal
interface, though it may expose some of its contents (marked as 'public') which offer behavior. Design packages should
be used primarily as a model organizational tool, to group related things together; if behavioral semantics are needed,
use Design Subsystems.
A design package and its contents are the responsibility of a single Role: Designer.
Elements within the package may be dependent on the elements contained by other packages; this gives rise to
dependencies between packages. Package dependencies can be used as a tool to analyze the resiliency of the design
model: a model with cross-dependent packages is less resilient to change.
Relationships
Container Artifact
Design Model
RolesResponsible:
Designer
Modified By:
Software Architect
TasksInput To:
Output From:
Identify Design Elements
Identify Design Mechanisms
Incorporate Existing Design Elements
Process Usage
Analysis & Design
>
Refine the Architecture
>
Design Package
Analysis & Design
>
Refine the Architecture
>
Design Package
Analysis & Design
>
Analyze Behavior
>
Design Package
Analysis & Design
>
Analyze Behavior
>
Design Package
Analysis & Design
>
Design Components
>
Design Package
Tailoring
Representation OptionsUML Representation: Package in the design model.
Packages are used in the models to group similar model elements, improving the organization of the model and making it
easier to understand. Packaging in large models is essential. Even in smaller models, appropriate packaging can
dramatically improve the comprehensibility of the model. Some packaging is almost always useful. For more information,
see Guideline: Design Package.
More Information
Checklists
Design Package
Guidelines
Design Package
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
contentPage.onload();
Wyszukiwarka
Podobne podstrony:
package treepackage summarypackage summarypackagepackage summarypackage usepackage summarypackage treepackage summarypackage usepackage summarypackage treepackage framepackage summarypackage treePackageElementwięcej podobnych podstron