From: Don Organ
Sent: Tuesday, February 11, 2003 10:31
AM
To: STIL. 4 (E-mail)
Subject: stds-1450.4: Teleconference
Minutes 2/11/2003
Teleconference
minutes Feb 11, 2003
Dave
Dowding
Jim
O'Reilly
Don
Organ
Ernie
Wahl
Tom
Micek
Jim
Mosley
---------------------------------------------
Agenda
-
Tony Taylor's feedback (via Dave)
-
STIL.4 reflector issue (bouncing email)
-
Ernie's attachments - from his email this morning
-
Jim Mosley's email
Tony Taylor's
feedback (via Dave)
Tony is glad to
see the use-case, and is encouraging his to have a tutorial/example section in
the specification. Dave doesn't feel the first use-cases would be the right
use-case, but likes/supports the idea. Another question from Tony is whether
we would have a graphical representation of the flow. Dave supports this as
well, but feels we should not be proposing any graphical
standard.
Jim O'Reilly -
would like to include an example (as in the 1999 spec) and then dissect
it.
STIL.4
reflector
henrnburg@att.net (I might not have
it spelled correctly here) - this email is bouncing from the
reflector.
Conference call
note:
Starting in March,
the conference call meeting id will be: 14504
Ernie's 2/11/2003
email and attachments
Ernie started
writing code for Dave's UseCase. Some things (such as binning) haven't yet
been addressed, other aspects of the specification are not fully consistent.
His files:
ExampleCode.asc -
an example application
Syntax.asc - this
is Ernie's ideas regarding the syntax - expected to be roughly consistent with
the proposal
Defaults.asc -
shows how defaults can be used
Keywords.asc -
just a list of keywords
Walk through Syntax.asc: PassBinMap|FailBinMap -
separate binmaps to facilitate targetting to some existing test systems. The
Axis - generally a single Axis for failures, but may have multiples for
passing (speed, power supply, cached/cacheless). For each element in this
N-dimensional array, you must have a hard bin (can be the same at different
elements).
FlowNode -
somewhat different from what is in the document. The execute portion is the
same. However, could pass in a speed bin as an argument - and call the same
test object over and over for different speed bins. The method_id allows
direct instantiation of a TestMethod. Ports - trying to match up to Don's
"horizontal slice". The Method Test - various types of Methods (including
Test, Group and Flow). Has In, InOut and Out parameters. Modifier mutable
(means non-constant). Ports - limited to Pass/Fail (unlike the FlowNode).
User-defined Method (externally defined) may have inheritance. At the bottom
is the test method instantiation.
Next time, let's
continue with the defaults.
-DVO-
---------------------------------------------------------------------------------
Don
Organ
Inovys Corporation
---------------------------------------------------------------------------------