STCI: Oak Ridge October 22 24 2007

Oak Ridge October 22 24 2007

Working meeting

Meeting Outcomes

A list of common and use case-specific requirements, including any requirements that we have missed.
A list of supported environments and platforms. Maybe a list of tool categories we'll support (e.g. debugging, perf tools, etc.)?
A architecture diagram and state diagrams
Software architecture (major components). Maybe even a first cut at control commands?
APIs for the frontend, the plugins and the agents.

09:00 - 09:30: Opening remarks. Agreement on agenda.
09:30 - 12:00: Final go over requirements, use-cases, and data-flows. (This basically assumes we will be done by the end of next week with these - do we need to have a call next week to go over these ?)
12:00 - 13:00: Lunch
13:00 - 18:00: Architecture discussions. This is where we start to map the data flows onto various components.

09:00 - 12:00: Administrative issues: language, components, build system, license, hosting, version control, bug tracker
12:00 - 13:00: Lunch
13:00 - 18:00: Continue architecture discussion

09:00 - 11:00: Discussion of what existing code we may be able to bring to bear to this case (this assumes there are no IP issues with this code). This, most likely, will impact the API's so need to have this discussion first. Also, discuss what platforms are being targeted for phase 1.
11:00 - 14:00: API's (including first cut at header files), probably need to break up into 2-3 working groups to work in parallel on different components.
14:00 - 17:00: Report out on API's (working lunch)
17:00 - 18:00: Wrap up