User Tools

Site Tools


sysml-roadmap:property_modeling_core_team

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
sysml-roadmap:property_modeling_core_team [2016-11-01 08:13]
hpdekoning [UML Object-Oriented Data Model]
sysml-roadmap:property_modeling_core_team [2017-04-26 17:42]
hpdekoning Added requirements specification in Excel format 2017-40-26
Line 10: Line 10:
 Roger Burkhart, Harald Eisenmann, Manas Bajaj, Ilya Tolchinsky, Nerijus Jankevicius,​ Hans Peter de Koning Roger Burkhart, Harald Eisenmann, Manas Bajaj, Ilya Tolchinsky, Nerijus Jankevicius,​ Hans Peter de Koning
  
-Status: ​Very much a work in progress ...+Status: ​Draft concepts and requirements available for review
  
  
Line 21: Line 21:
 see http://​sebokwiki.org/​wiki/​System_Property_%28glossary%29 . see http://​sebokwiki.org/​wiki/​System_Property_%28glossary%29 .
  
-This activity is a precursor to developing the full set of concept model requirements. The concept of **system property** is tackled first, as it is a central concept in any system model. +This activity is a precursor to developing the full set of concept model requirements. The concept of **system property** is tackled first, as it is a central concept in any system model. ​In SysML v1.4, these concepts are modeled as: 
- +    * **ValueType** and **ValueProperty** 
- +    * Annex E.5, Model Library for Quantities, Units, Dimensions, and Values (QUDV)
- +
- +
- +
  
 ===== Limitations of SysML v1 ===== ===== Limitations of SysML v1 =====
Line 34: Line 30:
   * No support for value property collections:​ a variable-length list (or sequence), set, bag, ordered set of a particular value type   * No support for value property collections:​ a variable-length list (or sequence), set, bag, ordered set of a particular value type
   * Too simplistic support for measurement scales other than ratio scale (in QUDV)   * Too simplistic support for measurement scales other than ratio scale (in QUDV)
-  * No standard feature ​to constrain the range of a numerical ​value type+  * The inability ​to easily restrict a valid range of values for a value property. One can do this with constraints,​ but it should be very simple to do. For example, one may wish to restrict the valid range of values for water temperature to 0 – 100 degrees Celsius or 32 – 212 degrees Fahrenheit. ​
   * Complex meta-model (including QUDV) leads to implementation inefficiencies for tool vendors and usability issues for end-users   * Complex meta-model (including QUDV) leads to implementation inefficiencies for tool vendors and usability issues for end-users
   * A (numerical) value type defines (and fixes) a selected measurement unit, but the actual measure scale in use (rather than unit) for a value property of a given value type should be selectable from a set of permissible measurement scales   * A (numerical) value type defines (and fixes) a selected measurement unit, but the actual measure scale in use (rather than unit) for a value property of a given value type should be selectable from a set of permissible measurement scales
Line 42: Line 38:
  
  
- +===== SE Needs for Properties & Expressions ​===== 
- +  * {{sysml-roadmap:​secm_-_property_thoughts_r5.docx|Property Thoughts R5}} 
- +  * {{sysml-roadmap:​sysml_v2_rfp_properties_comments_b4_20151207.xlsx|Property Comment Spreadsheet}}
-===== Starting Point ===== +
- +
-  * SysML v1.4, in particular:​ +
-    * Concepts **ValueType** and **ValueProperty** +
-    * Annex E.5, Model Library for Quantities, Units, Dimensions, and Values (QUDV) +
- +
-  * List of initial thoughts: ​{{sysml-roadmap:​secm_-_property_thoughts_r5.docx|Property Thoughts R5}}. +
   * Draft high level class diagram:\\ {{sysml-roadmap:​properties_diagram_v4.jpg}}   * Draft high level class diagram:\\ {{sysml-roadmap:​properties_diagram_v4.jpg}}
  
Line 89: Line 77:
   * **value**: particular magnitude or designation for a given observable characteristic \\ Examples: (1) the value //1540.5// expressed in //​kilogram//​ for the "​mass"​ property of "my car", (2) the value //red// for the "​color"​ variable, (3) the default value //true// for the "​isEncrypted"​ boolean formal parameter of operation "​sendData",​ (4) the value //​299792458//​ expressed in //m/s// for the "speed of light in vacuum"​ physical constant.   * **value**: particular magnitude or designation for a given observable characteristic \\ Examples: (1) the value //1540.5// expressed in //​kilogram//​ for the "​mass"​ property of "my car", (2) the value //red// for the "​color"​ variable, (3) the default value //true// for the "​isEncrypted"​ boolean formal parameter of operation "​sendData",​ (4) the value //​299792458//​ expressed in //m/s// for the "speed of light in vacuum"​ physical constant.
   * **value type**: named definition of the essential semantics and structure of the set of possible values of an observable characteristic,​ without the **value** itself   * **value type**: named definition of the essential semantics and structure of the set of possible values of an observable characteristic,​ without the **value** itself
 +
 +
  
  
Line 94: Line 84:
 ===== Driving Requirements ===== ===== Driving Requirements =====
  
-The initial ​requirements ​specification is maintained ​in the MS Word file belowThe template used is compatible with future inclusion into the SysML v2 RFP document.+The requirements ​for Properties, Values Expressions (status 26 April 2017) are provided hereafter ​in an Excel file. Currently ​the requirements are transferred to the SECM Team Cloud Server model  
 + 
 +{{ :​sysml-roadmap:​requirements_on_properties_values_and_expressions-2017-04-26.xlsx |}} 
 + 
 +Older versions of the requirements specification are kept below:
  
-{{ :​sysml-roadmap:​sysml-v2-rfp-reqs-values-and-expressions-draft5.docx |}}+  *{{ :​sysml-roadmap:​sysml-v2-rfp-reqs-values-and-expressions-draft5.docx |}} 
 +  *{{ :​sysml-roadmap:​secm-properties-and-expressions-draft_requirements-2016-12-08.pdf |SECM-Properties & Expressions-Draft Requirements Presentation at Coronado Meeting-2016-12-08}}
  
  
Line 112: Line 107:
 {{ :​sysml-roadmap:​secm-valuetype-overview.png |Figure 1 - ValueType Overview}} {{ :​sysml-roadmap:​secm-valuetype-overview.png |Figure 1 - ValueType Overview}}
  
-{{ :​sysml-roadmap:​secm-valuetype-other-uses-than-property.png?200 |Figure 2 - Other ValueTypes than Property}}+{{ :​sysml-roadmap:​secm-valuetype-other-uses-than-property.png |Figure 2 - Other ValueTypes than Property}}
  
-{{ :​sysml-roadmap:​secm-collectionvaluetype.png?200 |Figure 3 - Collection ValueTypes}}+{{ :​sysml-roadmap:​secm-collectionvaluetype.png |Figure 3 - Collection ValueTypes}}
  
-{{ :​sysml-roadmap:​secm-sampledfunctionvaluetype.png?200 |Figure 4 - Discretely Sampled Function ValueType}}+{{ :​sysml-roadmap:​secm-sampledfunctionvaluetype.png |Figure 4 - Discretely Sampled Function ValueType}}
  
-{{ :​sysml-roadmap:​secm-core-concepts-system-element-with-properties.png?200 |Figure 5 - Integration of Property with Core System Elements}}+{{ :​sysml-roadmap:​secm-core-concepts-system-element-with-properties.png |Figure 5 - Integration of Property with Core System Elements}}
  
  
sysml-roadmap/property_modeling_core_team.txt · Last modified: 2017-04-26 17:42 by hpdekoning