RE: [tag] My AI - comments on splitting/repositioning of 'Prerequisites' content

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Stephen:

I didn't mean to make this ID scheme a general "best practice" rule...
But only for our own examples, for the reader to relate more easily Tas
and requirements, for convenience.

I thought we could have an editorial note like this:

"In order for the reader to easily relate the examples of test
assertions presented in the guideline, to the normative statements that
they address, this guideline uses the following conventions:
Whenever a test assertion is addressing a requirement of ID "xyz" in the
"widget" specification, a TA addressing this requirement will have an ID
of the form: widget-TAxyz-abc, where "abc" is an optional
sub-identifier, e.g. in case several TAs address the same requirement."

I think this can help in our guideline, as we jump back and forth to
requirements in previous sections, showing TA variants, etc.

I'll leave it to users to decide their own scheme... Maybe we could warn
them to be aware that the relationship between requirements and Tas can
be many-to-many.

Jacques





-----Original Message-----
From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On
Behalf Of Stephen Green
Sent: Sunday, September 14, 2008 11:00 PM
To: TAG TC
Subject: Re: [tag] My AI - comments on splitting/repositioning of
'Prerequisites' content

> Shouldn't we try to have TA Ids more intuitively related to the 
> Requirement IDs they address?

Jacques,

I remember we originally had it down to write a short paragraph about
using a scheme for making IDs. We dropped it because nobody could
provide a clear enough reason to use a scheme. Maybe you have now
provided something - that some might choose to use ID schemes to ensure
both TA IDs and Normative Source IDs have a clear relationship because
this helps in grouping for conformance clauses and the like.

Steve

>
> For instance, if we have Requirement 101 (with part (a) and part (b)),

> then we could decide that all Tas that address 101 should have an ID 
> of the form:
> widget-TA101-xyz
> Where we use xyz to distinguish which part of 101 is addressed, and 
> possibly different variants of the TA.
>
> Cheers,
> Jacques
>
>
>
>
> -----Original Message-----
> From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On 
> Behalf Of Stephen Green
> Sent: Sunday, September 14, 2008 1:51 PM
> To: TAG TC
> Subject: [tag] My AI - comments on splitting/repositioning of 
> 'Prerequisites' content
>
> I've added my comments on splitting/repositioning of 'Prerequisites'
> content:
>
> http://wiki.oasis-open.org/tag/TestAssertionGuidelines?action=diff&rev
> 2=
> 212&rev1=211
>
> I'm happy with the split and position of the content. I have 
> reservations about combining TA examples for spec req 100 example as 
> it goes against our illustration of granularity.
> If this is the only way to keep the text clear though I'd accept it, 
> provided we make a comment to explain this (such as 'for clarity and 
> simplicity we will revert to handling the example specification 
> requirement 100 with a single test assertion example ...').
>
> --
> Stephen D. Green
>
> Partner
> SystML, http://www.systml.co.uk
> Tel: +44 (0) 117 9541606
> Associate Director
> Document Engineering Services
> http://www.documentengineeringservices.com
>
> http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>



--
Stephen D. Green

Partner
SystML, http://www.systml.co.uk
Tel: +44 (0) 117 9541606
Associate Director
Document Engineering Services
http://www.documentengineeringservices.com

http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php