User Tools

Site Tools


mbse:modelmgt:notations

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
mbse:modelmgt:notations [2015/10/31 23:44]
lvanzandt
mbse:modelmgt:notations [2015/11/01 10:28] (current)
sfriedenthal
Line 12: Line 12:
  
 For a sound argument on the value of the Decision Viewpoints backed by good case study empiricism, see the seminal 2011 paper [[http://​www.cs.rug.nl/​paris/​papers/​JSS11c.pdf|here]] For a sound argument on the value of the Decision Viewpoints backed by good case study empiricism, see the seminal 2011 paper [[http://​www.cs.rug.nl/​paris/​papers/​JSS11c.pdf|here]]
 +
 +Refer to {{mbse:​observations_on_proposed_decision_framework_for _sysML_v2 _requirements-friedenthal-2015-10-31.pdf|Friedenthal observations}} ​
  
 === [NOTATION-SYSML-PROV-101] === === [NOTATION-SYSML-PROV-101] ===
Line 21: Line 23:
  
 For an argument proposing automatic collection of PAV attributes, see [[http://​edas.info/​p19129#​S1569520677|VanZandt2015]] For an argument proposing automatic collection of PAV attributes, see [[http://​edas.info/​p19129#​S1569520677|VanZandt2015]]
 +=== [NOTATION-SYSML-TEMP-101] ===
 +(TEMP == Temporality)
 +
 +Members of the Model Lifecycle Management Activity Team suggest that the OMG SysML Specification team consider the inclusion of the concepts of bounded temporality--or what innovative PLM vendors call "​effectivity"​ into the elements of SysML'​s structural, behavioral, and relational elements. All concepts (here, both abstract and reified) except for axiomatic Truths exhibit temporality. That is, their spatial extent, their behavior, or their relationships hold for particular durations in Time. However, current modeling notations and practices assume that every structural, behavioral, or relational claim either always does not exist or always does exist. The inability to explicitly represent temporality or effectivity in model elements leads architects and systems engineers into awkward complexity as they attempt to communicate that particular claims within their models hold for one context yet don't, may not, or may be qualitatively different in other contexts.
mbse/modelmgt/notations.1446349482.txt.gz ยท Last modified: 2015/10/31 23:44 by lvanzandt