0% found this document useful (0 votes)
177 views4 pages

SDA LAB Package Diagram

A package diagram shows the organization and relationships between model elements such as classes, diagrams, and packages. Packages are used to group related elements and are depicted as file folders. Package diagrams illustrate the layered architecture of a system and provide benefits like clarifying complex structures and large projects. The basic components are packages to group elements, dependencies to show relationships between elements, and imports/merges to share elements between packages.
Copyright
© © All Rights Reserved
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
0% found this document useful (0 votes)
177 views4 pages

SDA LAB Package Diagram

A package diagram shows the organization and relationships between model elements such as classes, diagrams, and packages. Packages are used to group related elements and are depicted as file folders. Package diagrams illustrate the layered architecture of a system and provide benefits like clarifying complex structures and large projects. The basic components are packages to group elements, dependencies to show relationships between elements, and imports/merges to share elements between packages.
Copyright
© © All Rights Reserved
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

[SDA LAB]

[Package Diagram]

SYED HAMZA IBRAR GILLANI


ROLL NO: FA-2019-BSSE-060
SECTION: B

Submitted to: Mrs. Sadia Zafar

Dated: 31-May-2021
What is a package diagram?
Package diagrams are structural diagrams used to show the organization and
arrangement of various model elements in the form of packages. A package is a
grouping of related UML elements, such as diagrams, documents, classes, or even
other packages. Each element is nested within the package, which is depicted as a
file folder within the diagram, then arranged hierarchically within the diagram.
Package diagrams are most commonly used to provide a visual organization of the
layered architecture within any UML classifier, such as a software system.

Benefits of a package diagram


A well-designed package diagram provides numerous benefits to those looking to
create a visualization of their UML system or project.
 They provide a clear view of the hierarchical structure of the various UML
elements within a given system. 
 These diagrams can simplify complex class diagrams into well-ordered
visuals.
 They offer valuable high-level visibility into large-scale projects and
systems.
 Package diagrams can be used to visually clarify a wide variety of projects
and systems.
 These visuals can be easily updated as systems and projects evolve.

Basic components of a package diagram


The makeup of a package diagram is relatively simple. Each diagram includes only
two symbols:

Symbol Symbol
Description
Image Name
Groups common elements based on data, behavior, or
Package
user interaction

Depicts the relationship between one element


Dependency
(package, named element, etc. ) and another

These symbols can be used in a variety of ways to represent different iterations of


packages, dependencies, and other elements within a system. Here are the basic
components you’ll find within a package diagram:

 Package: A namespace used to group together logically related elements


within a system. Each element contained within the package should be a package
able element and have a unique name.

 Package able element: A named element, possibly owned directly by a


package. These can include events, components, use cases, and packages
themselves. Package able elements can also be rendered as a rectangle within a
package, labeled with the appropriate name.

 Dependencies: A visual representation of how one element (or set of


elements) depends on or influences another. Dependencies are divided into two
groups: access and import dependencies.

 Element import: A directed relationship between an importing namespace


and an imported package able element. This is used to import select individual
elements without resorting to a package import and without making it public
within the namespace. 

 Package import: A directed relationship between and importing namespace


and an imported package. This type of directed relationship adds the names of
the members of the imported package to its own namespace

 Package merge: A directed relationship in which the contents of one


package are extended by the contents of another. Essentially, the content of two
packages are combined to produce a new package.
Example: Online shopping system

You might also like