<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Dec 11, 2020 at 9:12 AM Frank Kühndel <<a href="mailto:frank.kuehndel@embedded-brains.de">frank.kuehndel@embedded-brains.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Gedare,<br>
<br>
On 12/11/20 4:41 PM, Gedare Bloom wrote:<br>
> <br>
> <br>
> On Fri, Dec 11, 2020 at 8:16 AM Frank Kühndel<br>
> <<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a><br>
> <mailto:<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a>>> wrote:<br>
> <br>
> Hello Joel,<br>
> <br>
> On 12/11/20 3:49 PM, Joel Sherrill wrote:<br>
> ><br>
> ><br>
> > On Fri, Dec 11, 2020, 8:41 AM Frank Kuehndel<br>
> > <<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a><br>
> <mailto:<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a><br>
> <mailto:<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a>>>> wrote:<br>
> ><br>
> > From: Frank Kühndel <<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a><br>
> <mailto:<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a><br>
> <mailto:<a href="mailto:frank.kuehndel@embedded-brains.de" target="_blank">frank.kuehndel@embedded-brains.de</a>>>><br>
> ><br>
> > ---<br>
> > eng/req/req-for-req.rst | 21 +++++++++++++++++++++<br>
> > 1 file changed, 21 insertions(+)<br>
> ><br>
> > diff --git a/eng/req/req-for-req.rst b/eng/req/req-for-req.rst<br>
> > index 9225e95..dcc4c11 100644<br>
> > --- a/eng/req/req-for-req.rst<br>
> > +++ b/eng/req/req-for-req.rst<br>
> > @@ -308,6 +308,27 @@ spec:/classic/task/create-err-invname<br>
> ><br>
> > ...<br>
> ><br>
> > +If requirements or the YAML files which contain them are to be<br>
> > numbered,<br>
> > +the numbering shall start with 0. For example:<br>
> ><br>
> > +<br>
> > +.. code-block:: none<br>
> > +<br>
> > + weak-alias-0.yml<br>
> > + weak-alias-1.yml<br>
> > +<br>
> > +Smaller numbers shall be prefixed with 0 to the same count of<br>
> digits<br>
> > +as the largest number. For example:<br>
> ><br>
> ><br>
> > When one goes from 99 to 100 requirements and didn't anticipate having<br>
> > that many, does this mean all the files will have to be renamed?<br>
> <br>
> I can change the text to what Gedare Bloom suggested: "If we know the<br>
> max count (N) ahead of time, ..."<br>
> <br>
> Just from my experience with the requirements for the basedefs, when I<br>
> create the requirements for an operation, I know the number I end up<br>
> with before checking them in. The issue we discuss would only cause<br>
> trouble if later more requirements for the same operation must be added.<br>
> This is not totally unlikely but it means that one actually has 9 and<br>
> then need a 10th one.<br>
> <br>
> ><br>
> > Should we start with a minimum of three or four digits? What would<br>
> drive<br>
> > the number of requirements in a set? How large of a functional<br>
> area will<br>
> > a single numbered set contain?<br>
> ><br>
> > I'm just wondering if it is simpler to just have 001 as a minimum.<br>
> <br>
> I think that 99 requirements for a single operation are really out of<br>
> scope. That will hopefully never ever happen. Even 9 is already a lot.<br>
> Also it is rather advisable to adapt the names of the requirements to<br>
> indicate the purpose. The numbering is more for the case that there are<br>
> two or more requirements on the same topic (like on handling the same<br>
> bad input argument).<br>
> <br>
> my-function-0<br>
> my-function-1<br>
> my-function-global-side-effect<br>
> my-function-bad-argument-x-error-handling<br>
> my-function-bad-argument-y-error-handling<br>
> my-function-called-in-wrong-state<br>
> <br>
> <br>
> This actually means there is a requirement for unnumbered names as well.<br>
> <br>
> Would it be better to explicitly define all requirements numbered and<br>
> use -0, in case they should be extended later, or perhaps to start<br>
> numbering without a number as 0 "implied" and numbers begin with 1?<br>
> <br>
<br>
If there is a -1 then I personally prefer that there should be a -0. For<br>
the basedefs, I ended all requirements with -0 even if there was no -1.<br>
Yet, whether this is the most wisest thing to do, I cannot say. I would<br>
leave it to the author.<br>
<br>
These numbers are mainly for requirements which need to be split:<br>
<br>
my-function.yml<br>
"The function shall return 7 and set global variable X to 5".<br>
<br>
If later someone needs to split this, would renaming it be so much trouble?<br>
<br></blockquote><div>I don't know if renaming them would be a problem or not. Need an expert to weigh in on that.</div><div><br></div><div>If renaming them introduces challenges, then we should explicitly use -0 for the first requirement always, and not allow unnumbered ones to exist.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
my-function-0.yml<br>
"The function shall return 7".<br>
<br>
my-function-1.yml<br>
"The function shall set global variable X to 5".<br>
<br>
Could be as well:<br>
<br>
my-function-result.yml<br>
"The function shall return 7".<br>
<br>
my-function-side-effect.yml<br>
"The function shall set global variable X to 5".<br>
<br>
Greetings<br>
Frank<br>
<br>
> <br>
> My opinion is that defining whether we start counting with 0 or with 1<br>
> makes sense. Everything else seems to me a bit like solving theoretical<br>
> problems.<br>
> <br>
> ><br>
> > +<br>
> > +.. code-block:: none<br>
> > +<br>
> > + alias-00.yml<br>
> > + alias-01.yml<br>
> > + alias-02.yml<br>
> > + ...<br>
> > + alias-09.yml<br>
> > + alias-10.yml<br>
> > + alias-11.yml<br>
> > +<br>
> > Conflict Free Requirements<br>
> > --------------------------<br>
> ><br>
> > --<br>
> > 2.26.2<br>
> ><br>
> > _______________________________________________<br>
> > devel mailing list<br>
> > <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>>><br>
> > <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>><br>
> > <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>>><br>
> ><br>
> <br>
> Greetings<br>
> Frank<br>
> _______________________________________________<br>
> devel mailing list<br>
> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>><br>
> <br>
</blockquote></div></div>