Scribd
Upload
6 views14 pages

Component Diagram

The document provides an overview of component diagrams in UML, highlighting their role in modeling the physical implementation of software and its high-level components. It explains the characteristics of components, such as modularity and encapsulation, and details the various elements involved, including component stereotypes, interfaces, and dependencies. The conclusion emphasizes the importance of components as physical, replaceable parts of a system that adhere to defined interfaces.

Uploaded by

saurabhkumar7155294
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views14 pages

Component Diagram

The document provides an overview of component diagrams in UML, highlighting their role in modeling the physical implementation of software and its high-level components. It explains the characteristics of components, such as modularity and encapsulation, and details the various elements involved, including component stereotypes, interfaces, and dependencies. The conclusion emphasizes the importance of components as physical, replaceable parts of a system that adhere to defined interfaces.

Uploaded by

saurabhkumar7155294
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

COMPONENT

DIAGRAM
INTRODUCTION
• UML diagram classification:
• Static
• Use case diagram, Classdiagram
• Dynamic
• State diagram, Activity diagram, Sequence diagram, Collaboration
diagram
• Implementation
• Component diagram, Deployment diagram

• Implementation diagrams describe the different elements


required for implementing a system
COMPONENT DIAGRAM
• Models the physical implementation of the software (file
resources)

• Models the high-level software components, and their interfaces

• Dependencies are designed such that they can be treated as


independently as possible

• Components to use with Component Diagram are:


• Components required to run the system(library file, etc.)

• Source code file, and data file

• Executable file (.exe)


COMPONENT DIAGRAM
(contd…)
• Component is an Autonomous unit
• Modular

• Encapsulated

• Hidden internals and inaccessible

• One or moreinterfaces

• Well defined interface lets to access the component’s


operations

• Component and subsystems can be flexibly reused and


replaced
Elements of Component
Diagram

• Component Stereotype
• <<executable>>: executable file (.exe)
• <<library>>: references resources (.dll)
• <<file>>:text file, source code file, etc.
• <<table>>: database file, table file,etc.
• <<document>>: document file, web page file, etc.
Elements of Component

Component Interface

Component dependencies
Elements(contd…)
• Interface may also be shown
using a rectangle symbol with a
keyword <<interface>>
preceding the name

• Services that the component


expects from its environment is
modeled using a socket

• multiple components that


require or provide a particular
interface
Interface
An interface (small circle or semi-circle on a stick) describes a
group of operations used (required) or created (provided) by
components. A full circle represents an interface created or
provided by the component. A semi-circle represents a required
interface, like a person's input.
Dependencies
Draw dependencies among components using dashed arrows.
Port
Ports are represented using a square along the edge of the system
or a component. A port is often used to help expose required and
provided interfaces of a component.
CONCLUSION
• Components
• Physical and replaceable part of the system that
conforms to and provides the realization of a set of
interfaces
g. .:
• COM+ components, Java Beans, …
• source code files
• Documents
• Nodes
• Describes the physical resources and the components it
hold

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy