From - Wed Mar 25 13:31:04 1998 Return-Path: Received: from commx ([153.33.32.81]) by mail1.ltx.com (Netscape Messaging Server 3.01) with SMTP id AAA16153; Wed, 4 Mar 1998 14:07:09 -0500 Received: from tessi.com (mailhost.tessi.com) by commx.ltx-tr.com; Wed, 4 Mar 98 10:52:21 PST Received: from mail1.ltx.com (nsmail1.ltx.com) by tessi.com (4.1/SMI-4.1) id AA12060; Wed, 4 Mar 98 11:00:06 PST Received: from ltx.com ([153.33.24.5]) by mail1.ltx.com (Netscape Messaging Server 3.01) with ESMTP id AAA15934; Wed, 4 Mar 1998 14:03:03 -0500 Sender: organ@ltx.com Message-Id: <34FDA52F.2D5B23AE@ltx.com> Date: Wed, 04 Mar 1998 11:02:07 -0800 From: Don Organ Organization: LTX/Trillium X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.5.1 sun4m) Mime-Version: 1.0 To: Francisco Hernandez , Mike Purtell , Tom Munns , Ernie Wahl , James Dexter , Chris Nelson , Tony Taylor , Givargis Danialy , Nathan Biggs , Greg Wilder Cc: stil-a@tessi.com Subject: STIL-A FlowControlTeam Minutes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here's my notes from our 3/4 meeting. Participants: Ernie Wahl Francisco Tony Taylor Mike Purtell Jim Dexter Phil Barch Don Organ Gregg Wilder Agenda: a) agree on agenda b) discuss process (problem statement, scope of work, collect requirements, solicit proposals, evaluate, create spec, evaluate/test/revise, submit to working-group) c) problem statement d) requirements [from Tony's SRS: test sequencing, test flow parameters (options) expression processing as function of flow multi-site status message (to operator) test identification binning test sites (where special processing may be required) flow statitistical reports] e) STIL'izing the enVision syntax f) logistical issues (reflector?, web-site?) g) summarize/wrap-up Process: discussion regarding "test" - didn't really prototype in STIL. Phil: ATE vendors should do some active validation Tony: target Trial-Use standardization Mike: we need to establish the proposal before we can see if ATE vendors will do some validation agreement on trial-use regarding enVision - try to STILize enVision as a way to help gel the problem statements and requirements and solicit other proposal Problem Statement: DVO's: Facilitate EDA vendors generation of ATE programs with minimal manual intervention? Mike's: Flow is the sequencing of activities in a complete test. Ernie: another group is working on TestMethods Phil: let's get back to a strawman Tony: Allow an EDA vendor to generate the TestProgram Flow (as a sequence of tests). Don: Given STIL and the TestMethods and TesterTargetting activities we will facilitate the EDA generation of ATE programs. Ernie: let's avoid EDA - since STIL is a test-interchange format. Requirements test sequencing/flow (multiple threads) - the order of which tests are run sequenceing versus flow: sequencing is single dimensional, not sufficient to define multiple paths depending on device result multiple processing - for mixed signal we may be able to define sequencing in a way that some processors may be able to execute some operations in parallel dataflow versus execution flow? object-oriented test flow parameters (options) tests are the primitives of the flow, and each test has input and output parameters, the flow is responsibile for presentint the parameters to the test and processing the return parameters should return result be a pass/fail? (speed binning might produce a multi-way result, stress testing may produce no result) all tests may be derived from a common base class Next time: common parameters for the flow - Tony will start us off. expression processing as function of flow multi-site status message (to operator) test identification binning test sites (where special processing may be required) flow statitistical reports] Multiple threads easy to maintain -DVO- -- ============================================== Don Organ (408) 383-2518 organ@ltx-tr.com LTX Corp. 3930 N. First St. San Jose, CA 95134 ==============================================