MagicDraw UML and SysML Plugin eSchool
Motto: "Learn good ways to work with MagicDraw UML and its SysML Plugin !"
About the eSchool
UML2 in MagicDraw
MagicDraw UML tips
MagicDraw SysML Plugin
MagicDraw for Java
MagicDraw for XML
Advanced UML and SysML Training
  • MagicDraw UML, SysML, DoDaf, etc., training courses by No Magic. Please click here
Home » OMG SysML issues » 08 Blocks » OMG SysML RTF: proposal by No Magic for unified "value slice" system for initialisation, configuration, and animation » Alternative value context metamodels and considerations on sharing of values » ALTERNATIVE: Slot-based: root "instance values tree" at the «ValueSlice» and map to all parts within value context » Analysis of an attempt to share a Slot-based "instance values trees/branch" between higher value contexts

TypeE: also resuses TypeC and instance values from a <<ValueSlice>> for TypeC

Wed, 04/23/2008 - 19:42 — author

For completeness. Changes to the instance values carried by the branch within usages of C in - say - and IBD for <<ValueSlice>> SliceD - would express themselves here. Sharing values comes at a price.

Image: 
‹ TypeD: reuses assembly TypeC and instance values from a <<ValueSlice>> for TypeCup[Suggest show both part-specific values & static values "showing through" to part within a value context with static indicator] ›
Search
The MagicDraw SysML Plugin Tutorial Overview