From: owner-stds-1450-4@majordomo.ieee.org on behalf of Don Organ
[don.organ@inovys.com] Sent: Tuesday, May 14, 2002 10:03
AM To: STIL. 4 Subject: stds-1450.4: STIL.4 flow control
issues
At our previous
conference call, we said our agenda for this week's call would be "Flow Control
Object Model".
Here's some
questions I think we might want to address:
Are we agreed on
the general concept of a FSM/FlowChart/declarative approach?
Are we agreed on
supporting hierarchy? (SubFlows)
What are the basic
boxes in the Flow? Something for a TestMethod call, the SubFlow, some
decision/branch/loop point, a bin. Are these extensible (such as to
include the Plot in the 3/8/99 document)?
What are the return types
from a Test Method (pass/fail, or pass/fail/error, or
user-defined)?
In whatever box the
TestMethod is called from, is it possible to call more than one
TestMethod?
Is there a
restriction on the number of output arcs from a FlowNode?
How do Ernie's
concepts of pre-action and post-action and arbiter fit in?
What are the
highest level entry points into the flow? (Load, StartOfTest,
Unload)
Assuming SubFlows,
how many input ports are allowed? How are the return ports
specified?
Where is the
Pattern Exec called from? (Calling it from low in the hierarchy - such as from
within a TestMethod, allows more control and flexibility. However, calling it
from high in the hierarchy would allow an entire sub-flow be grouped under a
single Pattern Exec - which could be desireable when creating speed-binning
flow - where 2 subflows differ only in the Category/Selector. Or do we
consider breaking it apart?)
-DVO-
----------------------------------------------------------------- Don
Organ
Inovys Corporation (925) 924-9110
x122 -----------------------------------------------------------------