Mod 5

Unit_V
Component
• A component is a physical and replaceable part of a system that
conforms to and provides the realization of a set of interfaces.
Graphically, a component is rendered as a rectangle with tabs.
• Names
• • A component name must be unique within its enclosing package
Components and Classes
• There are some significant differences between components and
classes.
• Classes represent logical abstractions;
• components represent physical things that live in the world of bits.
• In short, components may live on nodes, classes may not.
• Components represent the physical packaging of otherwise logical
components and are at a different level of abstraction.
• Classes may have attributes and operations directly.
• components only have operations that are reachable only through
their interfaces.
•
Components and Classes
Components and Interfaces
• An interface is a collection of operations that are used to specify a service
of a class or a component.
• The relationship between component and interface is important.
• All the most common component-based operating system facilities (such as
COM+, CORBA, and Enterprise Java Beans) use interfaces as the glue that
binds components together.
• An interface that a component realizes is called an export interface,
meaning an interface that the component provides as a service to other
components.
• A component may provide many export interfaces.
• The interface that a component uses is called an import interface, meaning
an interface that the component conforms to and so builds on.
• A component may conform to many import interfaces.
• A component may both import and export interfaces.
Kinds of Components
• Three kinds of components:
• • Deployment components.
• • Product components.
• • Execution components.
•
• Organizing Components:
• • You can organize components by grouping them in packages in the same
manner in which you organize classes.
• • The UML defines five standard stereotypes that apply to components
• 1. executable 2. library 3. table 4. file 5. document

Deployment diagram
• The deployment diagram visualizes the physical hardware on which
the software will be deployed.
• It portrays the static deployment view of a system. It involves the

nodes and their relationships.
• It ascertains how software is deployed on the hardware.
• It maps the software architecture created in design to the physical

system architecture, where the software will be executed as a node.
• Since it involves many nodes, the relationship is shown by utilizing

communication paths.
Purpose of Deployment Diagram
• The main purpose of the deployment diagram is to represent how

software is installed on the hardware component.
• It depicts in what manner a software interacts with hardware to

perform its execution.
• Both the deployment diagram and the component diagram are
closely interrelated to each other as they focus on software and
hardware components.
• The component diagram represents the components of a system,

whereas the deployment diagram describes how they are actually
deployed on the hardware.
• How to draw a Deployment Diagram?
• The deployment diagram portrays the deployment view of the
system.
• It helps in visualizing the topological view of a system.
• It incorporates nodes, which are physical hardware.
• The nodes are used to execute the artifacts. The instances of artifacts
can be deployed on the instances of nodes
CASE
STUDIES
This is an example of UML deployment diagram which
shows manifestation of components by artifacts and internal structure of artifacts. I would call this
kind of deployment diagrams manifestation diagrams or implementation diagrams as they actually
do not show any deployments.
• The iTunes setup can be downloaded from the iTunes website, and
also it can be installed on the home computer.
• Once the installation and the registration are done, iTunes application
can easily interconnect with the Apple iTunes store.
• Users can purchase and download music, video, TV serials, etc. and
cache it in the media library.
• The deployment diagram is mostly employed by network engineers,
system administrators, etc. with the purpose of representing the
deployment of software on the hardware system.
• It envisions the interaction of the software with the hardware to
accomplish the execution.
• The selected hardware must be of good quality so that the software
can work more efficiently at a faster rate by producing accurate
results in no time
• Android is a software stack for mobile devices that includes an
operating system, middleware and key applications.
• Android relies on Linux OS for core system services such as security,
memory management, process management, network stack, and
driver model.
• The Linux kernel also acts as an abstraction layer between the
hardware and the rest of the software stack.
• Android applications are written in Java.
• Android SDK tools compile and package the code along with any
required data and resource files into Android application archive
file having .apk suffix.
• The .apk file represents one Android application to be deployed to
the Android-enabled mobile devices.
• Android applications are composed of one or more
application components (activities, services, content providers, and
broadcast receivers). Each component performs a different role in the
overall application behavior, and each one can be activated
individually (even by other applications).
• The manifest (deployment specification) file AndroidManifest.xml
describes application requirements, such as the minimum version of
Android required and any supported hardware configurations, and it
also declares all components in the application.
• With Android API Level 8 or later, application could be installed on
the external storage (for example, on the SD card).
• This is an optional feature that could be requested for the specific
application using a manifest attribute.
• By default, application is installed on the internal storage of the
mobile device and cannot be moved to the external storage.
• Deployment Diagram for Credit Card Processing System
This is a UML representation of how a credit card is deployed. It starts

with the user entering his credit card into the machine.
• The client PC is dependent on the user since the information varies
for each user. Different connections exist between the different
nodes of the system, i.e.: TCP/IP, RMI, JDBC.
• The entire information is processed to the database server where the
credit card database is located.
• Class Diagram.
• State Machine Diagram
• Sequence Diagram
• Component Diagram.
• Deployment Diagram.
• Use Case Diagram
• Communication Diagram
• Behavioural Diagram,
• Object Diagram.
• Package Diagram.
• Interaction Overview Diagram
• Timing Diagram
• Profile Diagram.
• Activity Diagram
• Composite Structure Diagram.

Mod 5

Uploaded by

Copyright:

Available Formats

Mod 5

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mod 5

Uploaded by

Copyright:

Available Formats

Unit_V

• 1. executable 2. library 3. table 4. file 5. document

• It portrays the static deployment view of a system. It involves the

• It maps the software architecture created in design to the physical

• Since it involves many nodes, the relationship is shown by utilizing

• The main purpose of the deployment diagram is to represent how

• It depicts in what manner a software interacts with hardware to

• The component diagram represents the components of a system,

• It incorporates nodes, which are physical hardware.

This is a UML representation of how a credit card is deployed. It starts

You might also like