The package diagram shows the organization and dependencies between packages that make up a model. It displays packages and their elements, and relationships between packages such as dependencies, imports, and merges. Packages provide namespaces and can contain other packages, elements, and define relationships to other packages.

1. Package Diagram
GROUP MEMBRS:
WASI ALI 14005065029
M. YASEEN 14005065046
SYED BILAL 14005065008

2. PACKAGE DIAGRAM
• The PACKAGE DIAGRAM in the UML (unified Modeling Language)
shows the dependencies between the packages that make up a
model.
• Package Diagram show the arrangement and organization of model
elements.
• It can also show structure and dependencies between sub-system or
modules.

3. UML PACKAGE SYMBOLS

4. UML PACKAGE SYMBOLS
• ACCESS: It is defined as directed relationship between an importing
namespace and a package able element.
• DEPENDENCY: Dependency relationship signifies that a single or set of
model elements requires other model elements for implementation.
• IMPORT; It is defined as a directed relationship that identifies a package
whose members are to be imported by a namespace.
• MERGE; It indicates that the contents of two packages are to be combined.

5. PACKAGE
• Package is used to group elements and provides a namespace for the
grouped elements. A package is a namespace for its members and may
contain other packages.
• Package can also merge with other package, thus provide the hierarchical
organization of the package.
• Different types of elements are allow to have the same name.
• Members of the package may be shown within the boundaries of the
package.

6. MEMBERS OF PACKAGE
• Member of the package not shown inside the package.
• Member of the package shown inside the package.
• Member of the package may e shown outside of the
package by branching lines.

7. RELATIONSHIPS
• There are three types of relationship in Package diagram.
• DEPENDENCY:
• GENERALIZATION:
• REFINEMENT:

8. DEPENDENCY
• One package depend on other package.
• Fish depend on water.

9. GENERALIZATIONS
• Generalization show the main branch and its kinds.

10. REFINEMENT
• Refinement show different kind of relationship between packages.
• One package refines another package, if it contain same elements but
offers more details about those elements.

11. PACKAGE IMPORT
• The keyword <<import>> is a indicated relationship between an
importing namespace and imported package.
• The keyword <<access>> is shown to indicate private visibility.
• The visibility of a package import could be either public or private.

12. PACKAGE IMPORT
• Private import of Presentation package and public import of Domain
package.

13. PACKAGE MERGE
• Package Merge indicates that content of one package is extended by
the content of another package.
• Package merge used when elements defined in different packages
have the same name and are intended to represent the same
concept.
• Package merge is shown using a dashed line with an open arrowhead
pointing from the receiving package to the merged package.

14. PACKAGE MERGE
• UML packages constructs and primitive types are merged by UML
Kernel package.

15. PACKAGE RELATIONSHIP
• A relationship between two packages is called a package dependency.
• The dependency relationship between packages is consistent with the
associative relationship between classes.
• EX: If changing the content of a package P2, affects the content of
another package P1, We can say that P1 has a Package Dependency
on P2.

16. PACKAGE RELATIONSHIP
• There are two types of Relationship:
• Unidirectional relationship.
• Bidirectional relationship.

17. PACKAGE RELATIONSHIP
• Unidirectional Relationship: one package have only one direction in
the diagram.

18. PACKAGE RELATIONSHIP
• Bidirectional Relationship: one package have two
direction and one package directed by two packages.

19. Class package diagram

20. THANK
YOU