We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4
Package and Component Diagram
Purpose of Package Diagrams
Package diagrams are used to structure high level system elements. Packages are used for organizing large system which contains diagrams, documents and other key deliverables. Package Diagram can be used to simplify complex class diagrams, it can group classes into packages. A package is a collection of logically related UML elements. Packages are depicted as file folders and can be used on any of the UML diagrams. Packages appear as rectangles with small tabs at the top. The package name is on the tab or inside the rectangle. The dotted arrows are dependencies. One package depends on another if changes in the other could possibly force changes in the first. Package Diagram Example - Import
<<import>> - one package imports the functionality of other package
Package Diagram Example - Access
<<access>> - one package requires help from functions of other package.
Package Diagram Example - Order Subsystem
Component Diagram: A component diagram is used to break down a large object-oriented system into the smaller components, so as to make them more manageable. It models the physical view of a system such as executables, files, libraries, etc. that resides within the node.
Notation of a Component Diagram
a) A component
b) A node
Why use Component Diagram?
1. It portrays the components of a system at the runtime. 2. It is helpful in testing a system. 3. It envisions the links between several connections.
Example of a Component Diagram
A component diagram for an online shopping system is given below:
The component diagram can be used for the followings:
1. To model the components of the system.
2. To model the schemas of a database. 3. To model the applications of an application. 4. To model the system's source code.