Unified Modeling Language, UML, and OMG SysML are trademarks of the Object Management Group. All other product and service names mentioned are the trademarks of their respective companies.
Back to Top
A: Model Management is an umbrella term that refers to the use of Packages and related constructs to manage the complexity of large, complex Models that represent large, complex Systems. Model Management is important to a modeler because if she cannot manage the complexity of a large, complex model, there is no reason to expect she will be able to manage the complexity of a large, complex system.
Model Management uses Packages as a generic grouping construct, as well as the following stereotypes (customizations) of Package:
The notations for Package and its common stereotypes are shown in the figure below.
Q: What is Model Management and why is it important?
A: Model Management is an umbrella term that refers to the use of Packages and related constructs to manage the complexity of large, complex Models that represent large, complex Systems. Model Management is important to a modeler because if she cannot manage the complexity of a large, complex model, there is no reason to expect she will be able to manage the complexity of a large, complex system.
Model Management uses Packages as a generic grouping construct, as well as the following stereotypes (customizations) of Package:
- Package: Basic grouping construct for organizing model elements and diagrams that defines unique namespace semantics, as well as Import and Contains relationships. Packages can nested and stereotyped (i.e., customized) to further organize their contents.
- Model («model»): The (system) Model stereotype organizes all model elements that describe the architecture of the system of interest, including all of its Views and Subystems.
- View («view»)/Viewpoint («viewpoint»): The View stereotype organizes a projection (cf. set theory projection) on a Model from the perspective (Viewpoint) of a set of stakeholders (e.g., Customer, Systems Engineer, System Analyst, System Designer, Software Engineer, Test Engineer). A Model View conforms to the perspective of its Viewpoint. In SysML both View and Viewpoint are first class elements than can be precisely defined.
- Subsystem («subsystem): The Subsystem stereotype decomposes a Model or its Views to reflect the logical or physical structure of the system of interest. Subsystems may be logical or physical abstractions, and if both types are present they should be distinguished by using stereotype keywords or some other distinctive notation. SysML and UML predefine the «subsystem» stereotype; users may define the «system» stereotype to complement the «subsystem» stereotype if the latter is not already predefined.
- Model Library «modelLibrary»: The Model Library stereotype organizes model elements intended for reuse in a Model.
- Framework «framework»: The Framework stereotype groups model elements that are intended to organize other models into Views, Subsystems, etc. Frameworks can conform to industry standards (DoDAF/MODAF, UPDM, TOGAF), corporate standards, or can be specified ad hoc.
- Profile «profile»: The Profile stereotype organizes model elements used to customize domains, platforms, and processes. These model elements include Stereotypes, Tagged Values, and Constraints.
The notations for Package and its common stereotypes are shown in the figure below.
Package Constructs
Reproduced by Permission © 2003-2012 PivotPoint Technology Corp.
Reproduced by Permission © 2003-2012 PivotPoint Technology Corp.
Keep in mind that you can request additional questions to be answered in the SysML FAQ by sending email to FAQ@SysMLforum.com.
Back to Top
Back to Top