There are multiple ways to organize your model into Packages. The S. Friedenthal in the "Practical Guide to SysML" recommends organizing your model structure in the following ways:
By system hierarchy (e.g., system level, subsystem level, component level).
By process life cycle where each model subpackage represents a stage in the process (e.g., requirements analysis, system design).
By teams that are working on the model (e.g., Requirements Team, Integrated Product Team (IPT) 1, 2).
By the type of model elements contained in it (e.g., requirements, behavior, structure).
By model elements that are likely to change together.
By model elements organized to support reuse (e.g., model libraries).
By other logical or cohesive groupings of model elements based on defined model-partitioning criteria.
A combination of the preceding.
The Package structure of MagicGrid project.
Automated Package Structure Creation in MagicGrid Projects
The package structure is automatically created upon the creation of the MagicGrid project. However, you can also create package structures for any additional components or subsystems within the solution domain of your model. You can do that by using predefined package structure configurations. To learn more, see the Automated Package Structure Creation page.
To create a predefined package structure in a MagicGrid project
- Right-click a block you want to create a package structure for, and in its shortcut menu, select Tools > Create Package Structure. The Select Package Structure dialog opens.
In the dialog, select the class you require:
To create a package structure for a component, select PackagesForComponent class.
To create a package structure for a subsystem, select PackagesForSubsystem class.
- Click OK.
A package structure is created for the selected element.