3 September 2003

URL for Docs:
  http://65.119.15.228/stil.4
Docs referenced:
  Aug26,2003 Phase1/Phase2 document

Attendees:	D2
		Jose Santiago
		Ernie Wahl
		Jim Mosely
		Don Organ

Topic for today: Flow Control

Definition of Flow Control:
- EW: Associate Finite State Machine: where nodes connected by arrows that 
  represent a change of state. In simplest sense, the node is a test. (Node 
  point to a test to make reusable) 
- JM: Sequencing of tests in a test program flow. Dependency flow of tests prior,
  sequence followed through flow determine binning. Also, higher method of 
  organizing groups of tests.
- JS: Connectivity of test, data access, ability to control and define binning, 
  handling results data (datalogging). Pre/Post conditions... 

Side discussion on Phase One and Two:
Phase One = represent the design info (timing/levels/vectors... but not 
necessarily the sequencing of tests at a virtual or tester independent data. 
Phase Two = such as exception handling... ATE specifics... different ways  
the tester can handle.

Side discussion on who and how Test Flow extension constructs are used:
1. Porting design data into company/process standard Test Flows 
   (predefined test methodology, such as subflows, binning, test sequence, 
    DC tests, etc.)
2. EDA and in-house ATPGs generating complete "test sets" for entities devices 
   using technology such as found in P1450.6 Core Test.
3. "Tester loadable" test program files conversion back to STIL. (debug session saves)
4. EDA-to-ATE conversion tools for generating test programs.