sysml-roadmap:property_modeling_core_team
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
sysml-roadmap:property_modeling_core_team [2016-12-25 11:42] sfriedenthal [Driving Requirements] |
sysml-roadmap:property_modeling_core_team [2017-04-26 17:42] (current) hpdekoning [Driving Requirements] |
||
|---|---|---|---|
| Line 30: | 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 80: | Line 80: | ||
| - | ===== Presentations ===== | + | |
| ===== Driving Requirements ===== | ===== Driving Requirements ===== | ||
| - | The initial requirements specification is maintained in the MS Word file below. The 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}} | ||
sysml-roadmap/property_modeling_core_team.1482684174.txt.gz · Last modified: 2016-12-25 11:42 by sfriedenthal
Page Tools
