Description
Packages organize model elements into logical groups, providing namespace management and structural organization for complex system models. In SysML v2, packages are fundamental organizational containers that help manage model complexity by grouping related elements together, defining their scope and visibility, and establishing clear boundaries between different aspects of the system model. Packages facilitate modularity and maintainability by allowing engineers to partition large models into manageable sections. They can contain any type of model element including other packages, creating hierarchical structures that reflect the organization of the system or the structure of the engineering team. Packages also support model reuse and configuration management by enabling clear ownership boundaries and version control at the package level. All Davinci projects have two reserved top-level packages:LIBRARY and MODEL. By default LIBRARY is where all included packages from other projects exist. In general model elements will get placed under MODEL and uploaded files default to LIBRARY.
Placing packages under parts or other structural elements can break ownership chains and create ambiguities in the model hierarchy. Packages should typically be organized at the top level or nested within other packages.
Package Access and Sharing
Packages can be configured as eitherprivate or public, controlling whether they can be included in other projects. This feature enables powerful model reuse and collaboration capabilities across your organization.
Private Packages (Default)
By default, all packages are created asprivate, meaning they are only accessible within their source project. Private packages cannot be included in other projects and their contents remain isolated to the project they were created in.
Public Packages
When a package is marked aspublic, it becomes available for inclusion in other Davinci projects. This allows collaborators with access to view and include the package (along with all its owned elements) in their own projects, enabling component and object reuse.
Configuring Package Access
To make a package available for inclusion in other projects:- Open the package in the Properties view
- Locate the
Accessfield next to the Package Name - Change the value from
privatetopublic - Save the changes
public, users with access to your project can include it in their own projects by right-clicking in their Library section and selecting “Include Package”.
When you include a public package from another project, all elements owned by that package are brought into your project’s Library. The included package maintains a link to its source, allowing for updates and version management.
View Types
| View | Description |
|---|---|
| Properties | Edit the object’s properties, attributes, and metadata. |
| Table | Display the object and its children in a tabular format. |
| Tree | View the hierarchical structure of the object. |
| Relationships | Explore the network of connections to other objects. |
| History | Track changes and revisions to the object. |
Properties Fields
Name of the object.
Short name of the object.
Defines whether the package is
private or public.- Private (default): The package is only accessible within its source project and cannot be included in other projects
- Public: The package (and all its owned elements) can be included in other Davinci projects, enabling model reuse and collaboration
public when you want to share component libraries, standards, or templates across multiple projects.Description of the object.
A list of all Relationships this object has with other model objects.Read more about Relationships