This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
mbse:sysml_stk_iw2011 [2011/01/26 18:51] bjorncole |
mbse:sysml_stk_iw2011 [2011/01/29 13:13] bjorncole |
||
---|---|---|---|
Line 2: | Line 2: | ||
//<This agenda is in draft form>// | //<This agenda is in draft form>// | ||
+ | |||
+ | Morining Session: "Model Scaling Issues" | ||
We would like to winnow down the potential topics for further action by the Challenge Team that have arisen through recent experiences in both the Space Systems and Telescope Challenge Teams as their models become larger and more mature. The common thread is that of handling scale. | We would like to winnow down the potential topics for further action by the Challenge Team that have arisen through recent experiences in both the Space Systems and Telescope Challenge Teams as their models become larger and more mature. The common thread is that of handling scale. | ||
Line 8: | Line 10: | ||
* Finding common issues to develop standard approaches for (e.g. moving between multiple local reference frames) | * Finding common issues to develop standard approaches for (e.g. moving between multiple local reference frames) | ||
- | * Matching SysML profiles to Ontologies | ||
- | * Coordinating system model and domain analysis via Ontology | ||
* Issues of evolution: merging, branching, configuration control, etc. | * Issues of evolution: merging, branching, configuration control, etc. | ||
* Variant modeling | * Variant modeling | ||
Line 16: | Line 16: | ||
* Zooming between levels of detail | * Zooming between levels of detail | ||
* Defining a navigation scheme for large models | * Defining a navigation scheme for large models | ||
+ | |||
+ | The afternoon session aims to focus on specific STK / SysML integration issues. For example: | ||
+ | |||
+ | * **A truly standard way to define a reference frame within SysML** | ||
+ | * Any markup on typical models that is missing that appears to be required to populate STK | ||
+ | * **What about time? Do we need it to truly interface Scenarios to STK? What might we need?** | ||
+ | * **Advertising STK's analysis service to SysML with available handles to connect with** | ||
+ | * Importing STK Scenarios and trajectories into the SysML model | ||
+ | |||
+ | We may knock down one, maybe two of the above STK / SysML issues in the hour, so we will have to choose. | ||
Discussion minutes: | Discussion minutes: |