component & deployment diagram © copyright 2001 snu oopsla lab

Component & Deployment Diagram

© copyright 2001 SNU OOPSLA Lab.

Contents Implementation Diagrams Component Diagram Deployment Diagram Implementation Modeling

Show aspects of model implementation, including source code structure and run-time implementation structure

Kinds component diagram deployment diagram

Implementation Diagrams

Shows the organizations and dependencies among software components

Components include source code components binary code components executable components

Component Diagram

Components

DictionarySpell-check

Synonyms

mymailer: Mailer

+Mailbox+RoutingList

-MailQueue

Planner

Scheduler

GUI

Reservations

Update

Component Diagram

Shows the configuration of run-time processing elements and the software components, processes and objects that live on them

Deployment diagrams may be used to show which components may run on which nodes

Deployment Diagram

AdminServer:HostMachine

Joe’sMachine:PC

:Scheduler reservations

:Planner

«database»meetingsDB

Deployment Diagram

Node1

Node2

«cluster»

x y

«cluster»

x y

«become»

«database»

w z

Deployment Diagram (cont’d)

When to model structure

Adopt an opportunistic top-down+bottom-up approach to modeling structure

Specify the top-level structure using “architecturally significant” classifiers and model management constructs (packages, models, subsystems; see Tutorial 3)

Specify lower-level structure as you discover detail re classifiers and relationships

If you understand your domain well you can frequently start with structural modeling; otherwise

If you start with use case modeling (as with a use-case driven method) make sure that your structural model is consistent with your use cases

If you start with role modeling (as with a collaboration-driven method) make sure that your structural model is consistent with your collaborations

Define a “skeleton” (or “backbone”) that can be extended and refined as you learn more about your domain.

Focus on using basic constructs well; add advanced constructs and/or notation only as required.

Defer implementation concerns until late in the modeling process.

Structural diagrams should emphasize a particular aspect of the structural model contain classifiers at the same level of abstraction

Large numbers of classifiers should be organized into packages

Structural Modeling Tips

Example : Package Diagram of Business Model

In transaction

Example : Deployment Diagram

Example : Rational Rose Component Diagram

Example : Rational Rose Component Tool

Example : Rational Rose Deployment Diagram

Example : Rational Rose Deployment Tool