From: Ernst_Wahl [wahl@aloft.agere.com]
Sent: Friday, February 22, 2002 1:51 PM
Subject: STIL P1450.4 requirements and issues


*. define test/testflow objects and relationships that permit
manipulation as per requirements.

*. some requirements, issues:

    *. interface between testflow and tests should be such that the user
    can define custom tests based on integral STIL types.

    *. flow capable of finite state machine behavior.

    *. allow reuse of a test in various parts of the flow

    *. maintenance conscious language design decisions

    *. passing of prior test results to subsequent test parameters
    and/or tester resource parameters, either directly or as part of a
    mathematical expression.

    *. conditional test/testblock execution, based on, e.g., previous
    test results or test environment like package or wafer.

*. 2 phase development:

    i propose only that we keep this idea in mind when we get bogged
    down on issues that might be separable into phase two.

    1. test specification (go-nogo tests, binary/linear searches,
    conditional flow, soft and hardware binning, etc.), e.g., a
    communication from an IC vendor or consumer to a test house.

    2. test program (datalogging, multi-site, tester-dependent code,
    etc.), e.g., a program that runs on one or more vendor's ATE.