Meeting #5, 2021 03 16

Zoom meeting 2021-03-16 12:00-14:00 CET

Attendees:
Knut Jetlund, Norway
Reese Plews, Japan
Heidi Vanparys, Denmark
Clemens Portele, Germany
Tatjana Kutzner, Technical University of Munich
Peter Parslow, Ordnance Survey, UK, TC211 PMG
Chuck Heazel, NGA, USA
Ronald Tse, CalConnect / ISOGR RA
Mats Åhlin ISO/TC 211

Conceptual model of normative statements

ref https://github.com/orgs/ISO-TC211/teams/adhoc-automated-documentation/discussions/11

What kind of formalization should this model have?

Several solutions are possible.

• No standardization, only an internal document

• Addendum to ISO 19105

• Individual TS/TR/IS

• Arguments for some kind of standardization: The model may very well be used by other communities as well, not only internally in ISO/TC 211. For example, national specifications. This model will be very useful as input for ISO SMART — there is going to be a new ISO SMART Steering Group at the ISO Council.

• Conclusion: No clear conclusion was reached. A most likely approach would be to suggest a NWIP for a TR/TS. But we will wait and gain some experiences with the model first.

The draft conceptual model - changes discussed and agreed on:

• Add association from AbstractTestSuite to RequirementsSuite (ref https://github.com/orgs/ISO-TC211/teams/adhoc-automated-documentation/discussions/11/comments/7)
• Set multiplicity from ModularSpecification to AbstractTestSuite = 1 (ref https://github.com/orgs/ISO-TC211/teams/adhoc-automated-documentation/discussions/11/comments/7)
• Add verbs as association names (ref https://github.com/orgs/ISO-TC211/teams/adhoc-automated-documentation/discussions/11/comments/6)
• Use nouns as role names (ref https://github.com/orgs/ISO-TC211/teams/adhoc-automated-documentation/discussions/11/comments/6)
• Remove the name attribute - URI and localId is enough
• Rename description to text
• Remove the attribute executableExpression(ref https://github.com/orgs/ISO-TC211/teams/adhoc-automated-documentation/discussions/11/comments/7)
• Change the role name subExpression to subStatement (ref https://github.com/orgs/ISO-TC211/teams/adhoc-automated-documentation/discussions/11/comments/7)
• Definitions for NormativeStatement and subclasses must refer to https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor026

How to use the model in practice - requirements instances in standards?

• UML Profile according to the conceptual model - Example. Other implementations possible.
• Some questions raised whether UML is fit for writing requirements.
• Arguments for requirements in UML: Model documentation with requirements. Structure. Relation to classes.

Next steps

One meeting per month up to the next ISO/TC 211 plenary: April, May.

• Meeting #6 April 23rd, 13-15 CET
• Doodle for meeting #7 (May): https://doodle.com/poll/6exik9gavqc8xmcd?utm_source=poll&utm_medium=link

Results & recommendations to the plenary:

• Update the existing documentation (https://github.com/ISO-TC211/UML-Best-Practices/wiki/DocumentationOfUmlModels) & https://github.com/ISO-TC211/UML-Best-Practices/blob/master/DocumentationOfUMLModels/Automatic%20generation%20of%20documentation%20from%20UML%20models.docx based on findings from this group. Github only, not Word document.
• Recommend the use of MDD for ISO/TC 211 standards
• Present a conceptual model for normative statements as an extension of ISO 19105
• Future NWIP for the conceptual model for normative statements