User Tools

Site Tools


mbse:sysml_stk_iw2011

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
mbse:sysml_stk_iw2011 [2011/01/26 19:00]
bjorncole
mbse:sysml_stk_iw2011 [2011/01/29 13:13]
bjorncole
Line 3: Line 3:
 //<This agenda is in draft form>// //<This agenda is in draft form>//
  
-There are two alternative proposals for the agenda:+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 10: 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 19: Line 17:
   * Defining a navigation scheme for large models   * Defining a navigation scheme for large models
  
-An alternative is to focus on specific STK / SysML integration issues. ​ For example:+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+  ​* **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   * Any markup on typical models that is missing that appears to be required to populate STK
-  * Advertising STK's analysis service to SysML with available handles to connect with +  ​* **What about time?  Do we need it to truly interface Scenarios to STK?  What might we need?** 
-  * Importing STK Scenarios and trajectories into the SysML model+  * **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. We may knock down one, maybe two of the above STK / SysML issues in the hour, so we will have to choose.
mbse/sysml_stk_iw2011.txt · Last modified: 2011/01/31 14:26 by bjorncole