What's New Features Tutorials Support Pricing Try Now Request Demo

What/
HOME isSUPPORT
Package/ Diagram?
WHAT IS PACKAGE DIAGRAM?

Purpose of Package Diagrams

Package Diagram at a Glance

What is Package Diagram?

Basic Concepts of Package

Diagram

Dependency Notation

Import

Access

Modeling Complex Grouping

Example: Layering Structure

Example: Order System

Example: Order Processing

System Package diagram, a kind of structural diagram, shows the arrangement and organization of model elements in
middle to large scale project. Package diagram can show both structure and dependencies between sub-
systems or modules, showing di!erent views of a system, for example, as multi-layered (aka multi-tiered)
Related Links application - multi-layered application model.

Learn UML Faster, Better and Easier

Are you looking for a Free UML tool for learning UML faster, easier and quicker?
Visual Paradigm Community Edition is a UML software that supports all UML diagram
types. It is an international award-winning UML modeler, and yet it is easy-to-use,
intuitive & completely free.

Free Download

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 "le folders and can be used on any of the UML diagrams.

Package Diagram at a Glance

Package diagram is used to simplify complex class diagrams, you can group classes into packages. A package is
a collection of logically related UML elements.

The diagram below is a business model in which the classes are grouped into packages:

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 "rst.

Basic Concepts of Package Diagram

Package diagram follows hierarchal structure of nested packages. Atomic module for nested package are
usually class diagrams. There are few constraints while using package diagrams, they are as follows.

Package name should not be the same for a system, however classes inside di!erent packages could have
the same name.

Packages can include whole diagrams, name of components alone or no components at all.

Fully quali"ed name of a package has the following syntax.

Packages can be represented by the notations with some examples shown below:

Package Diagram - Dependency Notation

There are two sub-types involved in dependency. They are <<import>> & <<access>>. Though there are two
stereotypes users can use their own stereotype to represent the type of dependency between two packages.

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.

Modeling Complex Grouping

A package diagram is often used to describe the hierarchical relationships (groupings) between packages and
other packages or objects. A package represents a namespace.

Package Diagram Example - Layering Structure

Package Diagram Example - Order Subsystem

Package Diagram Example - Order Processing System

Package Diagram Example - Order Processing System

Order Processing System - The Problem Description

We are going to design package diagram for "Track Order" scenario for an online shopping store. Track
Order module is responsible for providing tracking information for the products ordered by customers.
Customer types in the tracking serial number, Track Order modules refers the system and updates the
current shipping status to the customer.

Based on the project Description we should "rst identify the packages in the system and then related them
together according to the relationship:

Identify the packages of the system

There is a track order module, it has to talk with other module to know about the order details, let us call it
"Order Details".

Next after fetching Order Details it has to know about shipping details, let us call that as "Shipping".

Identify the dependencies in the System

Track order should get order details from "Order Details" and "Order Details" has to know the tracking info
given by the customer. Two modules are accessing each other which su#ces <<access>> dual dependency

To know shipping information, "Shipping" can import "Track Order" to make the navigation easier.

Finally, Track Order dependency to UI Framework is also mapped which completes our Package Diagram for
Order Processing subsystem.

Try to Draw UML Package Diagram Now

You've learned what a Object Diagram is and how to draw a Object
Diagram. It's time to draw a Object Diagram of your own. Get Visual
Paradigm Community Edition, a free UML software, and create your own
Object Diagram with the free Object Diagram tool. It's easy-to-use and
intuitive.

Free Download

Related Links

1. What is Uni!ed Modeling Language?

2. Professional UML diagram tool

Turn every software project into a successful one.

Try Visual Paradigm Free

Product Support Learn About Us

Features Forums Community Circle Visual Paradigm

Editions Request Help Know-how Newsroom

Try Now Customer Service Demo Videos YouTube Channel

Pricing Tutorials Academic Partnership

Visual Paradigm Online Documents

@2020 by Visual Paradigm. All rights reserved. Legal Privacy statement

      