2. Are we agreed on
supporting hierarchy? (SubFlows)
Yes. Ernie prefers to call them TestFlows. Jose - is
the nesting limited? No - but from a partical point, implementations may have
limits. Jim - subflows can be used for grouping, and also for parallel flows at
the same level in the hierarchy. Jose/Jim/Ernie - subflows could be used for
different cores.
3. 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)?
FlowNode=Vertex (in
graph theory). Also, consider adding a non-branch action (such as closing the
relay on a loadboard). We had some discussion as to what this point means (is
the FlowNode a test? or a pointer to a test? we tried to defer this issue).
Ernie thinks the binning might be an attribute of a test (or of a flow) - would
like to ensure that removing a test that is associated with a bin to also remove
that bin. Ernie thinks of the test and the test method as one thing (with
pre-action, body, and post-action) - so he sees binning as an exit action.
Ernie's emphasis is to encourage a maintainable program
structure.
We didn't close on this issue. We seem to have good
agreement on all aspects other than the binning, and we might be close on
the binning as well. We'll pick up here next
time.