gbuehler
commented
3 years ago Recent examples: 19159-2 does not format the requirements separately, they are "hidden" inline in the clause text and can be found by searching for "shall"
19119:2016 formats them as in what appears to be a "path-like" string structure... /req/computationalviewpoint/interfaces which i have used before in 19155-2. they are also surrounded by a box.
19107 revision in current development has a numbered structure, with a TOC at the front of the document. however they are formatted as text statements, not "path-like" string structures.
N3936 Recommendations for cultural and linguistic adaptability use a numbered heading type of format, without a box and without the "path-like" structures. some additional information to my earlier examples
it would really be nice if both the requirements format and uml notation text/format could be specified. such as
- a listing of requirements shall exist after the table of contents
- requirements shall be numbered such-and-such a way (19127:2016 uses some strange little symbol i have never seen before in addition to no. and it seemed really redundant).
- requirements shall be formatted such-and-such a way text;bold text; with/without a box, etc, etc
having a "best approved" method for formatting requirements, that is acceptable to both TC211 and OGC (because of common projects) would be very helpful.
Justification: Resolution 596 Template for table of requirements classes and requirements
ISO/TC 211 invites the PMG in cooperation with the project leaders for projects 19136-2, 19150-2, 19103 and 19160-1 to cooperate on drafting a template for requirements classes and requirements in ISO/TC 211 deliverables.
ISO/TC 211 requests that the project leaders report on the progress at the 35th plenary. Proposal: Include specifications for layout conventions for modularization (recommendation 4 in the report on Configuration management and backward compatibility, document N3165). See also PMG report from Jeddah (slides 17-19).