Bab 12 deployment diagram 2010
-
Upload
asuransipaninlife -
Category
Education
-
view
2.247 -
download
5
Transcript of Bab 12 deployment diagram 2010
BAB XIIBAB XIIDeployment DiagramDeployment Diagram
Deployment/physical diagram menggambarkan detail bagaimana komponendi-deploy dalam infrastruktur sistem, dimanakomponen akan terletak (pada mesin, server atau piranti keras apa), bagaimana kemampuanjaringan pada lokasi tersebut, spesifikasi server, dan hal-hal lain yang bersifat fisikal.Sebuah node adalah server, workstation ataupiranti keras lain yang digunakan untuk men-deploy komponen dalam lingkungansebenarnya.
-- BersifatBersifat statisstatis
-- MemperlihatkanMemperlihatkan konfigurasikonfigurasi saatsaat aplikasiaplikasidijalankandijalankan ((saatsaat runtime).runtime).
-- MemuatMemuat node node besertabeserta komponenkomponen--komponenkomponen yang yang adaada didalamnyadidalamnya
-- BerhubunganBerhubungan dengandengan diagram diagram komponenkomponendimanadimana deployment diagram deployment diagram memuatmemuat satusatuatauatau lebihlebih komponenkomponen--komponenkomponen
UML Deployment Diagrams
• Models the run-time architecture (topology) of:
• Processors• Devices• Software components
• Is ultimately traceable to initial requirements
Topologynode
Softwarecomponent
Classes, objects,Collab., etc.
Use-caserequirement
UML Deployment Diagrams
• When you model the static deployment view of a system, you'll typically use deployment diagrams in one of three ways.
– To model embedded systems– To model client/server systems– To model fully distributed systems
Modeling an Embedded System
• An embedded system is a software-intensive collection of hardware that interfaces with the physical world.
• Embedded systems involve software that controls devices such as motors, actuators, and displays and that, in turn, is controlled by external stimuli such as sensor input, movement, and temperature changes.
• You can use deployment diagrams to model the devices and processors that comprise an embedded system.
Modeling an Embedded System
• To model an embedded system– Identify the devices and nodes that are unique to
your system– Provide visual cues, especially for unusual devices,
by using the UML's extensibility mechanisms to define system-specific stereotypes with appropriate icons
– Model the relationships among these processors and devices in a deployment diagram.
Modeling an Embedded System
Modeling a Client/Server System
• A client/server system is a common architecture focused on making a clear separation of concerns between the system's user interface (which lives on the client) and the system's persistent data (which lives on the server).
Modeling a Client/Server System
• To model a client/server system,– Identify the nodes that represent your
system's client and server processors– Highlight those devices that are germane to
the behavior of your system– Provide visual cues for these processors and
devices via stereotyping.– Model the topology of these nodes in a
deployment diagram
Modeling a Client/Server System
Modeling a Fully Distributed System
• To model a fully distributed system– Identify the system's devices and processors as
for simpler client/server systems– Pay close attention to logical groupings of
nodes, which you can specify by using packages
– Model these devices and processors using deployment diagrams
Modeling a Fully Distributed System
Stereotype Examples in Deployment Diagrams
<<printer>>HP LaserJet 5MP
<<router>>Cisco X2000
<<carController>>SAAB 9-5Navigator
Communication Associations in Deployment Diagrams
NEC PowerMatei-Select VL4PC:ClientA
Dell Dimension2350 PC:ClientB
Silicon GraphicsO2:Server
VAX:DB Server*
*
*
*
* *
<<TCP/IP>>
<<TCP/IP>>
<<DecNet>>
Component Support in UML Deployment Diagrams
NEC Server
UNIX Transactionserver sub-system
<<supports>>
Deployment Diagrams in the form of Class Diagrams
Deployment Diagram Example
The deployment diagram below shows that the users access the Reporting Tool by using a browser running on their local machine and connecting via HTTP over their company's intranet to the Reporting Tool. This tool physically runs on the Application Server named w3reporting.myco.com. The diagram shows the Reporting Tool component drawn inside of IBM WebSphere, which in turn is drawn inside of the node w3.reporting.myco.com. The Reporting Tool connects to its reporting database using the Java language to IBM DB2's JDBC interface, which then communicates to the actual DB2 database running on the server named db1.myco.com using native DB2 communication. In addition to talking to the reporting database, the Report Tool component communicates via SOAP over HTTPS to the Billboard Service.
UML Deployment Diagram Example• The three-dimensional boxes represent nodes, either software or hardware. Physical nodes
should be labeled with the stereotype device, to indicate that it is a physical device such as a computer or switch.
• Connections between nodes are represented with simple lines, and are assigned stereotypes such as RMI and message bus to indicate the type of connection.
Concise UML 2 Deployment Diagram
• A better example is shown in the figure below. Software elements are now simply listed by their physical filenames, information that developers are very likely to be interested in, and thus a more compact diagram is possible. A drum is used as a visual stereotype for the University DBdatabase, making it easier to distinguish on the diagram. Another difference is that the concise version shows less details, not as many tagged values are shown as this information can be
captured in either supporting documentation, configuration files, or source code.
Network Diagrams• Network diagrams are often drawn using software-based
drawing tools (figure below was drawn using Microsoft Visio)
Diagram Deployment
Deployment Diagram
• Shows the configuration of run-time processing nodes and the components that live on them
Course CourseOffering
Student Professor
Course.dllCourse People.dll
User
Register.exeBilling.exeBilling
Diagrams in UML – Component Diagram
shows the organizations and dependencies among a set ofcomponents (mostly <<uses>>).
In UML 1.1, a component represented implementation items, such as files and executables;…In UML 2.0, a component is a replaceable/reusable, architecture/design-time construct w. interfaces
Student Professor
Registrar Webserver Course Oracle Server
Library Server
Dorm PC
Main Building Solaris
Diagrams in UML – Deployment Diagram
• shows the configuration of run-time processing elements and the software processes living on them.
• visualizes the distribution of components across the enterprise.
Register.exe
People.dll Billing.exe
CourseCourse Offering
People DatabaseStudentProfessor
wireless
RMI, sockets TCP/IP
Copyright © 1997 by Rational Software Corporation
Deployment Diagram
Registration Database
Library
Dorm
Main Building