Tool Mentor: Structuring the Implementation Model Using Rational Rose
var backPath = './../../../';
var imgPath = './../../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_gpYSoAILEdq-_NKqZM1EhA", "_qS-iwAIOEdqTna4sZVFRow", "{06FB737B-5D74-4C3B-98F4-36153CFB2E34}", "{AE16EC14-5366-4CFD-A207-14F352D1B3E3}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_U5tiUAISEdqTna4sZVFRow", "{06FB737B-5D74-4C3B-98F4-36153CFB2E34}", "{AE16EC14-5366-4CFD-A207-14F352D1B3E3}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_AUv4MAIMEdq-_NKqZM1EhA", "_5ZuQsAIUEdqEutyfYo0quQ", "{06FB737B-5D74-4C3B-98F4-36153CFB2E34}", "{AE16EC14-5366-4CFD-A207-14F352D1B3E3}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_jD8dUAIbEdqEutyfYo0quQ", "_F1OgYAIbEdqEutyfYo0quQ", "{06FB737B-5D74-4C3B-98F4-36153CFB2E34}", "{AE16EC14-5366-4CFD-A207-14F352D1B3E3}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
Tool Mentor: Structuring the Implementation Model Using Rational Rose
This tool mentor describes how to create and structure the model elements, that represent the implementation model of a system, using Rational Rose.
Tool: Rational Rose
Relationships
Related Elements
Structure the Implementation Model
Main Description
Overview
Component diagrams provide a physical view of the current model. A component diagram shows the organizations and
dependencies among implementation elements, including source code files, binary code files, and executable files,
modeled as components.
For more
information about Component Diagrams, see the Component Diagrams (Overview) topic in the Rational Rose online help.
The following is a summary of the steps you perform to structure the implementation model:
Create a component diagram in the Component View
Create a subsystem structure that mirrors the Design Model structure
1. Create a component diagram in the Component View
In this step, you should:
Rename the Main component diagram using a more descriptive title.
Create additional component diagrams.
2. Create a subsystem structure that mirrors the Design Model structure
Subsystems are modeled as packages. In this step you:
Create a package structure in your Component View that mirrors the package structure you created for your
design model in the Logical View.
Create the actual components and assign their stereotypes and Language.
Assign classes (or interfaces) to components.
Optionally create a component from an existing software module.
You can drag executable programs (.exe), ActiveX (.ocx), Data Link Libraries (.dll), and Type Libraries (.tlb) from a
source such as Explorer and drop them in a component package (either in the browser or a diagram). You should limit the
elements you include to those that are external to your model or elements that are used by the modeled system only.
These elements are not intended to be reverse engineered into the model since they rarely contain the complete source
code. They are only necessary when building your system.
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
contentPage.onload();
Wyszukiwarka
Podobne podstrony:
structure implementation model9D33ADsetting up impl model with ucm?DD9D5Astructure implementation model?E0DEF9model structure guidelines for rational xde?veloperm2FD64Acontrol structures continueRzutparteru Model (1)model ekonometryczny zatrudnienie (13 stron),Modelowanie i symulacja systemów, Model dynamicznyJęazykoznawsto ogólne model sens tekstfunction xml parse into structson rise?v model 3 PL poziomodroga Model (4)2008 marzec OKE Poznań model odp prwięcej podobnych podstron