Package Diagram

The SysML Package diagram is used to define or view the Packages that provide the fundamental organization of the repository. These can include name-spaces and their sub-Packages and other less formally defined groups of elements. The Packages that appear in diagrams can also be viewed in the Browser window and their hierarchy can be navigated by expanding and collapsing the tree.

The main element that is represented in the Package diagram is the Package itself, with the elements it contains. There are a number of important relationships between Packages, including Dependencies that show that one Package is dependent on one more other Packages. Packages can be organized into a number of different types of hierarchy.

Elements

The main elements that can appear in Package diagrams are:

• Model
• Model Library
• Package
• View
• View Point
• Stakeholder

The main connectors that can appear in Package diagrams are:

• Conform
• Dependency
• Import
• Containment
• Realization
• Refine
• Expose

Tools

A variety of tools can be used with structural modeling and Block Definition diagrams, including:

• Documentation - which allows formal or informal documentation to be generated from the model in a variety of formats
• Traceability - which provides a hierarchical view of an element's relationships to other model elements
• Responsibility Window - which provides a composite view of the important responsibilities of an element, including Constraints, Requirements and Scenarios
• Relationship Matrix - which allows the connections between Packages(or other elements) and other elements such as Requirements and Use Cases to be visualized in a matrix

Usage

The Package diagram can be used to describe the relationship between Packages and the elements that they contain. While structural information is visible in the Browser window there is a range of relationships that can exist between Packages themselves and between Packages and elements, that cannot be visualized in the Browser window. Package diagrams can also be included in documentation and can assist in orientating an audience by giving them an overview of a section of the architecture or design in a similar way to providing a table of contents in a publication.