Scribd
Upload
15 views7 pages

Package Diagram

Uploaded by

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

Package Diagram

Uploaded by

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

Package Diagram

• All the interrelated classes and interfaces of the system


when grouped together form a package.
• To represent all these interrelated classes and interface UML
provides package diagram.
• Package diagram helps in representing the various packages
of a software system and the dependencies between them.
• It also gives a high-level impression of use case and class
diagram.
Package Diagram: purpose
• To provide static models of modules, their parts and their
relationships
• To present the architectural modelling of the system
• To group any UML elements
• To specify the logical distribution of classes
• To emphasize the logical structure of the system
• To offer the logical distribution of classes which is inferred
from the logical architecture of the system
Package Diagram: Uses
• To illustrate the functionality of a software system.
• To illustrate the layered architecture of a software
system.
• The dependencies between these packages can be
adorned with labels / stereotypes to indicate the
communication mechanism between the layers.
Notations

Example
Topic : UML Component Diagram, Deployment Diagram
Guidelines to Draw: Component Diagram
• Based on the analysis of the problem description of the
system, identify the major subsystem.
• Group the individual packages and other logical entities
in the system to provide as separate components.
• Then identify the interfaces needed for components
interaction.
• If needed, identify the subprograms which are part of
each of the components and draw them along with
their associated components.
• Use appropriate notations to draw the complete
component diagram.
Notations
Example

Deployment Diagram
• A deployment diagram shows the physical placement
of components in nodes over a network.
• A deployment diagram can be drawn by identifying
nodes and components.
• A deployment diagram usually describes the
resources required for processing and the installation
of software components in those resources.
Purpose
• It shows the relationship between software and hardware
components in the target system.
• They are useful to show the system design that has subsystem,
concurrent execution, compile time and execution time
invocations, and hardware/software mapping by assigning the
appropriate software components to the hardware devices.
• As they specify the distribution of software components in
various devices and processors in the target environment, it
will be easier for maintenance activities.
• Using this diagram it is easier to identify performance
bottlenecks.

Guidelines to Draw: Deployment Diagram


• Identify the hardware components and processing units in the
target system.
• Analyze the software and find out the subsystem, parallel
execution of modules, server side components, client side
components, business logic components, backend database
servers and software and hardware mapping mechanism to
map the software components to be mapped with appropriate
hardware devices.
• Draw the hardware components and show the software
components inside them and also show the connectivity
between them.
Notations
Example

You might also like