Scribd
Upload
63 views27 pages

Unit 5-Modeling Component Design

This document discusses implementation diagrams in UML, including component diagrams and deployment diagrams. It describes component diagrams as modeling physical components like executables, libraries, and files. Deployment diagrams capture the runtime configuration by showing the topology of processors and devices on which software executes. The document outlines the key elements, relationships, and uses of each diagram type.

Uploaded by

Asif Shaikh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
63 views27 pages

Unit 5-Modeling Component Design

This document discusses implementation diagrams in UML, including component diagrams and deployment diagrams. It describes component diagrams as modeling physical components like executables, libraries, and files. Deployment diagrams capture the runtime configuration by showing the topology of processors and devices on which software executes. The document outlines the key elements, relationships, and uses of each diagram type.

Uploaded by

Asif Shaikh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 27

Unit – 8

Deployment Diagram
Implementation Diagram
 It show the implementation phase of system
development such as the source code structure
and the run time implementation structure
 It is high level diagram also called as physical
diagram
 Two types:-
 Component diagram
 Deployment diagram
Component Diagram
 It model the physical components such as
executables, libraries, tables, files and
documents.
 A Component represents the physical
packaging of logical elements, such as classes,
interfaces, and collaborations.
 Logical modeling help to visualize, specify, and
document the collaborations. Physical modeling
is used to construct the executable system.
Component Diagram
 In the UML, all these physical things are modeled as
components. A component is a physical thing that
conforms to and realizes a set of interfaces, thus
interfaces bridge logical and physical models.
 You also can have file components that represent the
source code files of an application or document files
that represent, for example, the user interface files
such as HTML or JSP files.
 Finally, you can use components to represent even
the database tables of a system as well!
Elements
 Component: The objects interacting with each
other in the system. Depicted by a rectangle
with the name of the object in it, preceded by a
colon and underlined.
Interface
 It is a collection of operations that specify a
service that is provided by or requested from a
class or component.

<<Interface>>
Name

methods
Port
 A Port is a specific window into an encapsulated
component accepting messages to and from the
component conforming to specified interface.
 Ports can support unidirectional communication or
bi-directional communication.
Relationship
 Relation/Association: Similar to the
relation/association used in class diagrams

(dependency) (Realization)
Uses of Component diagram
 Modeling Source Code: In application, we organize the
files into larger groups. Sometimes we update some files or
create new version of file. Component diagrams help to
visualize these source code files and their relationships.
 Modeling Executable releases: Releasing a simple
application is easy but for complex technologies we need
main executable, libraries, stored procedures. Component
diagrams help to visualize, specify, construct and
document the configuration of executable releases,
consisting the deployment components that form each
release and the relationships among those components.
 Modeling physical databases: Mapping a logical
database schema to a relational database is not so simple.
In presence of inheritance decisions should be made
about how to map classes to tables.
 Define a separate table for each class

 Collapse inheritance lattices so that all instances of


any class in a hierarchy have the same state
 Separate parent and child states into different tables
 Modeling adaptable systems: sometimes due to
complex operations the database is separated on
different servers.
Deployment Diagram
 The deployment diagram captures the configuration
of the runtime elements of the application.
 It shows the topology of processors and devices on
which the software executes.
 With UML, we use deployment diagrams to
visualize the static aspect of the physical nodes and
their relationships and to specify their details for
construction.
 It shows allocation of processes to processors in
physical design, thus known as process diagram.
Elements
 Processor:- Hardware capable of executing
programs. It is represented as shaded cube with a
name of the object. It can have list of processes on
it.
Production
Server

 Device:- hardware helping in execution of


applications

Modem
 Connection:- similar to the relation/association
used in class diagrams to define the
interconnection between nodes.

 Deployment diagram addresses the


distribution, delivery, and installation of the
parts that make up the physical system.
Common Uses
 Model Embedded systems:- Embedded
systems involve software that controls devices
such as motors, actuators, and displays and is
controlled by external stimuli (sensor input,
movement, temperature changes). Deployment
diagram can be used to model the devices and
processors that comprise an embedded system.
Thus, we should consider project hardware and
software groups interaction.
 Model Client/Server system:- A client/server
system focus on making clear separation between
the system’s user interface and the system’s
persistent data. We should decide about the
network connectivity of clients to servers and
about the physical distribution of software
components across the nodes.
 Model fully distributed system:- They are
widely distributed encompassing multiple
levels of servers. Nodes can be added or
deleted as per requirement.
Relation between deployment and
component diagram
 The components in a component diagram are
contained in the deployment diagram. Hence,
components provide the application
functionality, and deployment elements
provide the necessary environment for the
components to execute in.
 The basic deployment element is the node. A
node can represent a multitude of components.

You might also like