Summary of new Guideline structure

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

Here is a quick summary of the accepted updates to the Guideline structure, focusing here on sections #2 and #3:

(the updated /new content of several sub-sections is subject to Action items that are reminded inline, and will be reminded in a separate email)

Let me know if I missed anything.

 

Jacques

 

---------------------------------------------------------------------------------------------------------------------------------

2. Designing a Simple Test Assertion

 

2.1 The Core Structure of a T.A.

(notes:

- includes first example widget-TA100.

- Also will include another Essential TA Element: "prescription Level" or similar name. Action Item: Paul R.

This one reflects the mandatory / preferred / permitted aspect of the normative statement addressed by the TA. , not exclusive of other values.

- also But does NOT include anymore bullet (b) moved in Advanced features.

- also, what used to be called "Reference [to specification] is for now renamed more generally "Normative Source".

- also, will include a quick forward reference to other "optional TA parts": Action Item: Paul R.)

 

2.2. Best Practices

2.2.1- Granularity of  TA (includes former 2.2 early examples widget-TA1 and widget-TA2, along with observation #2)

2.2.2- Implicit TA parts (includes the discussion on implicit/explicit TA parts , bullet (a) in former 2.1.)

2.2.3- Optional statements

(includes former 2.4, focusing on the TA Predicate. Must now also set the "Prescription Level" element.

Action Item: Youngkon Lee will attempt to reformulate his "regulation" refinement for the Optional statement pattern that combines both optionality and mandatory subset of alternatives)

2.2.4- Negative TA cases? (Action Item: Stephen G. to investigate - when predicate true means spec violation)

 

 

3. Advanced Features

 

3.1 Complex Predicates

(incluides former observations #3 and #4, with related example.

Reference: see the Unisoft TA variants: bold assertion / cause-effect behavior / conditional assertion)

 

3.2 TA Prerequisites

(formerly 2.3. Action Item: Stephen G.)

 

3.3 Various Normative Sources

(This is describing more completely the options of what used to be "Reference" TA Part. Cover 3 types of data that could be combined: (1) references to normative statements, (2) copy of normative statements, (3) Interpretation of normative sources in case these are complex, multiple or non-textual)

(contains part of former 3.1)

 

3.4 The Case of Multiple Specifications

(contains part of former 3.1)

3.4.1- Addressing normative statements from different specifications

3.4.2- Specifications depending on each other

(here, Action Item: J.D. for the option of handling this with pre-requisites)

 

3.5 Classification

(Action Item: J.D. E.g. look at the Voting Standard classification)

3.5.1- Classes of TA Target (cover relationships between classes, inheritance, composition. Consequence for TA scope.)

3.5.2- TA grouping and tagging

 

Still TBD: 

 (following subsections could be smaller parts of a catch-all subsection called "Other Best Practices" if not important enough for a full subsection)

 

3.6 Specification Versions (Action Item: Paul)

 

3.7 Variables and Target Properties  (Action Item: D.M.)