<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hello Frank,<div class=""><br class=""></div><div class=""> I have a use case where the numbers will exceed 10 .</div><div class=""><br class=""></div><div class="">It's not for numbered requirements but numbered test-files.</div><div class="">These result from different scenarios generated by our SPIN models, as part of the qualification activity.</div><div class=""><br class=""></div><div class="">The files are generated (and numbered) automatically, so the constraints are somewhat different.</div><div class=""><br class=""></div><div class="">For the Events Manager, for example, I'd expect the final number of generated test source files to exceed 10.</div><div class="">It is unlikely that we would reach 100, though.</div><div class=""><br class=""></div><div class="">Regards, Andrew</div><div><br class=""><blockquote type="cite" class=""><div class="">On 11 Dec 2020, at 15:16, Frank Kühndel <<a href="mailto:frank.kuehndel@embedded-brains.de" class="">frank.kuehndel@embedded-brains.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello Joel,<br class=""><br class="">On 12/11/20 3:49 PM, Joel Sherrill wrote:<br class=""><blockquote type="cite" class=""><br class=""><br class="">On Fri, Dec 11, 2020, 8:41 AM Frank Kuehndel<br class=""><<a href="mailto:frank.kuehndel@embedded-brains.de" class="">frank.kuehndel@embedded-brains.de</a><br class=""><<a href="mailto:frank.kuehndel@embedded-brains.de" class="">mailto:frank.kuehndel@embedded-brains.de</a>>> wrote:<br class=""><br class=""> From: Frank Kühndel <<a href="mailto:frank.kuehndel@embedded-brains.de" class="">frank.kuehndel@embedded-brains.de</a><br class=""> <<a href="mailto:frank.kuehndel@embedded-brains.de" class="">mailto:frank.kuehndel@embedded-brains.de</a>>><br class=""><br class=""> ---<br class=""> eng/req/req-for-req.rst | 21 +++++++++++++++++++++<br class=""> 1 file changed, 21 insertions(+)<br class=""><br class=""> diff --git a/eng/req/req-for-req.rst b/eng/req/req-for-req.rst<br class=""> index 9225e95..dcc4c11 100644<br class=""> --- a/eng/req/req-for-req.rst<br class=""> +++ b/eng/req/req-for-req.rst<br class=""> @@ -308,6 +308,27 @@ spec:/classic/task/create-err-invname<br class=""><br class=""> ...<br class=""><br class=""> +If requirements or the YAML files which contain them are to be<br class=""> numbered,<br class=""> +the numbering shall start with 0. For example:<br class=""><br class=""> +<br class=""> +.. code-block:: none<br class=""> +<br class=""> + weak-alias-0.yml<br class=""> + weak-alias-1.yml<br class=""> +<br class=""> +Smaller numbers shall be prefixed with 0 to the same count of digits<br class=""> +as the largest number. For example:<br class=""><br class=""><br class="">When one goes from 99 to 100 requirements and didn't anticipate having<br class="">that many, does this mean all the files will have to be renamed?<br class=""></blockquote><br class="">I can change the text to what Gedare Bloom suggested: "If we know the<br class="">max count (N) ahead of time, ..."<br class=""><br class="">Just from my experience with the requirements for the basedefs, when I<br class="">create the requirements for an operation, I know the number I end up<br class="">with before checking them in. The issue we discuss would only cause<br class="">trouble if later more requirements for the same operation must be added.<br class="">This is not totally unlikely but it means that one actually has 9 and<br class="">then need a 10th one.<br class=""><br class=""><blockquote type="cite" class=""><br class="">Should we start with a minimum of three or four digits? What would drive<br class="">the number of requirements in a set? How large of a functional area will<br class="">a single numbered set contain?<br class=""><br class="">I'm just wondering if it is simpler to just have 001 as a minimum.<br class=""></blockquote><br class="">I think that 99 requirements for a single operation are really out of<br class="">scope. That will hopefully never ever happen. Even 9 is already a lot.<br class="">Also it is rather advisable to adapt the names of the requirements to<br class="">indicate the purpose. The numbering is more for the case that there are<br class="">two or more requirements on the same topic (like on handling the same<br class="">bad input argument).<br class=""><br class=""> my-function-0<br class=""> my-function-1<br class=""> my-function-global-side-effect<br class=""> my-function-bad-argument-x-error-handling<br class=""> my-function-bad-argument-y-error-handling<br class=""> my-function-called-in-wrong-state<br class=""><br class="">My opinion is that defining whether we start counting with 0 or with 1<br class="">makes sense. Everything else seems to me a bit like solving theoretical<br class="">problems.<br class=""><br class=""><blockquote type="cite" class=""><br class=""> +<br class=""> +.. code-block:: none<br class=""> +<br class=""> + alias-00.yml<br class=""> + alias-01.yml<br class=""> + alias-02.yml<br class=""> + ...<br class=""> + alias-09.yml<br class=""> + alias-10.yml<br class=""> + alias-11.yml<br class=""> +<br class=""> Conflict Free Requirements<br class=""> --------------------------<br class=""><br class=""> -- <br class=""> 2.26.2<br class=""><br class=""> _______________________________________________<br class=""> devel mailing list<br class=""> <a href="mailto:devel@rtems.org" class="">devel@rtems.org</a> <<a href="mailto:devel@rtems.org" class="">mailto:devel@rtems.org</a>><br class=""> <a href="http://lists.rtems.org/mailman/listinfo/devel" class="">http://lists.rtems.org/mailman/listinfo/devel</a><br class=""> <<a href="http://lists.rtems.org/mailman/listinfo/devel" class="">http://lists.rtems.org/mailman/listinfo/devel</a>><br class=""><br class=""></blockquote><br class="">Greetings<br class="">Frank<br class="">_______________________________________________<br class="">devel mailing list<br class=""><a href="mailto:devel@rtems.org" class="">devel@rtems.org</a><br class="">http://lists.rtems.org/mailman/listinfo/devel</div></div></blockquote></div><br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">--------------------------------------------------------------------<br class="">Andrew Butterfield Tel: +353-1-896-2517 Fax: +353-1-677-2204<br class="">Lero@TCD, Head of Software Foundations & Verification Research Group<br class="">School of Computer Science and Statistics,<br class="">Room G.39, O'Reilly Institute, Trinity College, University of Dublin<br class=""> <a href="http://www.scss.tcd.ie/Andrew.Butterfield/" class="">http://www.scss.tcd.ie/Andrew.Butterfield/</a><br class="">--------------------------------------------------------------------</div>
</div>
<br class=""></body></html>