User Tools
bok:eng:mbse:sysml:adapting-sysml
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
bok:eng:mbse:sysml:adapting-sysml [2020/10/03 02:50] anwlur [Process] |
bok:eng:mbse:sysml:adapting-sysml [2020/11/19 13:17] (current) anwlur [Process] added information on model libraries |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| ===== Methodology ===== | ===== Methodology ===== | ||
| - | ==== Process ==== | + | ==== Process - Profiles ==== |
| + | An established process((C.Paredis and T. Johnson, "Using OMG's SysML to support simulation" Proceeding of the 2008 Winter Simulation Conference (2008))) to create profiles is laid out below: | ||
| - Create a metal-model for the specific domain that is being integrated. This could be done with the use of an [[bok:eng:mbse:ontology|ontology]]. | - Create a metal-model for the specific domain that is being integrated. This could be done with the use of an [[bok:eng:mbse:ontology|ontology]]. | ||
| - Create a SysML profile that will map the meta model to SysML stereotypes | - Create a SysML profile that will map the meta model to SysML stereotypes | ||
| - Create a transformation map between the meta model and SysML profile's entities | - Create a transformation map between the meta model and SysML profile's entities | ||
| - For each transformation include the corresponding API call to the domain specific tool | - For each transformation include the corresponding API call to the domain specific tool | ||
| + | |||
| + | For an examination of applying SysML to other languages such as Modelica see [[bok:eng:mbse:sysml:integrate-sysml-other-languages|Integrating SysML with other languages]]. | ||
| If language modeler wants to make the use of a particular profile mandatory then the relationship between the model and the profile shall be **required**. | If language modeler wants to make the use of a particular profile mandatory then the relationship between the model and the profile shall be **required**. | ||
| + | ==== Process - Model Library ==== | ||
| + | |||
| + | Model Libraries are useful if the modeler wants to takes parts 'off-the-shelf' rather than re-create them. Should only be used for parts that will be re-used. | ||
| + | |||
| + | To merge a maintained XMI file (e.g. a standard item type model library) do the following: | ||
| + | - Select the package that you want the model library to be a child of (e.g. if intended model hierarchy is 'Overview/Standard Item Type', and your XMI package top directly is 'Standard Item Type' then select 'Overview' package in your target model | ||
| + | - Publish -> Model Exchange -> Import XMI -> Import Package from XML... | ||
| + | - Select your source XMI -> Import | ||
| ===== Parts ===== | ===== Parts ===== | ||
bok/eng/mbse/sysml/adapting-sysml.1601693448.txt.gz ยท Last modified: 2020/10/03 02:50 by anwlur
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
