OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tag message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Thread: TA Modeling -- (formerly: RE: [tag] Test Assertion Model suggestion, 'Take Four')


Stephen:

General comment:

That structure below seems more appropriate for the markup phase.
I find it rather scary/daunting in a general guideline doc, or too
detailed... 

Primary concern for me: a guideline doc that people feel they can use
after just one reading, and can apply easily to their own specification.
I'd reserve the details for those willing to go to the next step - a
formal processable representation (not everyone !)

Cheers,
Jacques

-----Original Message-----
From: stephen.green@systml.co.uk [mailto:stephen.green@systml.co.uk] 
Sent: Monday, September 24, 2007 2:12 PM
To: tag@lists.oasis-open.org
Subject: [tag] Test Assertion Model suggestion, 'Take Four'

Proposed:

1..n   Test Assertions Guideline
-1..1   Identifier: <ID>
-1..1   Version: <ID>
-0..1   Previous Version: <Link>
-1..1   Description: <Text>
-1..1   Date: <Date>
<more here - authors, etc?>
-0..n   Specification
--0..1   Specification Cross Reference: <Link>
--0..1   Specification Description: <Text>
-0..n   Specification Module
--0..1   Specification Module Cross Reference: <Link>
--0..1   Specification Module Description: <Text>
-0..n   Specification Variation (Profile, etc)
--0..1   Specification Variation Cross Reference: <Link>
--0..1   Specification Variation Description: <Text>
-0..n   Test Assertion Guideline Variation
--0..1   Test Assertion Guideline Variation Cross Reference: <Link>
--0..1   Test Assertion Guideline Variation Description: <Text>
-0..n   Comment: <Text>
-0..n   Pre-requisite
--0..1   Pre-requisite Cross Reference: <Link>
--0..1   Pre-requisite Description: <Text>
-0..n   Test Assertion
--1..1   Test Assertion ID: <ID>
--0..n   Specification requirement
---0..1   Specification requirement Cross Reference: <Link>
---0..1   Specification requirement quote: <Text>
--0..?   Item under test: <Text>
--0..1   Assertion Description: <Text>
--0..n   Normative Comment: <Text>
--0..1   Test Assertion Pass Criteria: <Text>
--0..n   Test
---0..1   Test ID: <ID>
---0..n   Pre-condition
----0..1   Pre-condition Description: <Text>
----0..1   Pre-condition Cross Reference: <Link>
---0..n   Test Trigger
----0..1   Test Trigger Description: <Text>
----0..1   Test Trigger Cross Reference: <Link>
---1..n   Test Effect
----0..1   Test Effect Description: <Text>
----0..1   Test Effect Cross Reference: <Link>

Proposed amendments made:
added: head identifier and description
added: specification/variability references, etc (modules, profiles,
etc)
added: links to another set of test assertions which are varied in this
one
added: pre-requisites
removed: post-conditions

--
Stephen Green

Partner
SystML, http://www.systml.co.uk
Tel: +44 (0) 117 9541606

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








[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]