From: dave_dowding@agilent.com Sent: Monday, March 24, 2003 10:20 PM To: stds-1450-4@majordomo.ieee.org Subject: stds-1450.4: Use Case #4 pdf Attached Greetings, Use Case #4, including section 9.0 Flow Diagram is attached. It provides a simple two test Flow. The first flow node performs a basic function (wiggle) test at nominal levels and timing. The second performs simple input leakage. The intent of of this use case is to provide a vehicle to establish specific FlowNode entities and assumptions. It should also help determine the interaction mechanisms Flow entities need to work with TestMethods. Since TestMethods are undefined at this time, this use case assumes a simple notion of parameter passing to a function (the TestMethod) with a simple return value from the TestMethod that expresses a test "Pass" or "Fail" result. We should be able to exercise our existing Flow syntax and underlying assumptions with this basic use case set, without getting stuck on corner case situations. We can then move to more complex/capable flow situations found in testing today. Regarding our meeting agenda items for tomorrow's conference call: 1. Finish discussions on Jim O'Reilly's Use Case #2 program flow data. 2. Review the attached Use Case #4. a. Determine if this use case is ready to complete section 8.0 Syntax Example. b. Discuss use case flow diagram norms (i.e. what level of detail is required.) 3. Determine the status of other use case syntax examples. Progress/time frame priority. Any other items of business required can be added to this proposed agenda during our conference call. Dave Dowding <>