1 / 4

Package Diagrams

Learn how to create a package diagram in UML to organize and depict requirements, architecture, and designs effectively. Follow guidelines on naming, cohesion, architectural layers, and more.

fchapple
Download Presentation

Package Diagrams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Package Diagrams • A package diagram is a UML diagram composed only of packages and the dependencies between them. A package is a UML construct that enables you to organize model elements, such as use cases or classes, into groups. Packages are depicted as file folders and can be applied on any UML diagram. Create a package diagram to: • Depict a high-level overview of your requirements (overviewing a collection of UML Use Case diagrams) • Depict a high-level overview of your architecture/design (overviewing a collection of UML Class diagrams). • To logically modularize a complex diagram.

  2. General Guidelines • Give Packages Simple, Descriptive Names •  Apply Packages to Simplify Diagrams • Packages Should be Cohesive • Indicate Architectural Layers With Stereotypes on Packages • Avoid Cyclic Dependencies Between Packages • Package Dependencies Should Reflect Internal Relationships

  3. Class Package Example

  4. Use Case Package Example

More Related