1998 Paradyn Week Agenda

1) Process Issues

    A. Is there sufficient interest for the results of this standards effort?
       Or should Maryland, Wisconsin, and IBM proceed as we have?
    B. Who are the participants (active and observing)?
       Do other vendors wish to participate?
       Do other research projects wish to participate?
       What is the level of commitment of resources?
    C. How are decisions made?

2) Scope

    A. What are we trying to standardize?
       A multi-layered model, with well-defined interfaces at the
       dyninst and DAIS levels:

       Areas of functionality:
        * Platform independent process instrumentation on a single node.
        * Platform independent process control functions on a single node.
        * Platform independent extracting data from processes.
        * Multi-node, multi-tool support/RPC architecture.
    B. Who are the target users?
    C. What is the final product?
        * Standard specification document?
        * Reference implementation?
        * Test suite?

3) Time Table

    A. What do we want to have done and when?

4) Technical Discussion of dyninstAPI

    A. Status of current design
    B. Status of initial implementation
    C. Vision for the future

5) Technical Discussion of DAIS

    A. Status of current design
    B. Status of initial implementation
    C. Vision for the future

6) Logistics of current dyninstAPI implementation

    A. Process to incorporate changes from partners?
    B. Who will implement new features as interface evolves?
    C. How to minimize rapid changes in the code base
    D. Testing: who and how?
    E. Legal: ownership and rights to code.

7) Where do we go from here?

    A. Time/place for the next meeting?
    B. Tasks to be done by the next meeting