From IGSTK

I have started an outline for the paper. The outline is a pretty full dump of what IGSTK is about, so in the end I suspect some aspects will bubble to the surface as the key points. The outline has three themes for emphasis:

1. Architecture: Component-based, SM-grounded in safety-critical domain 2. Process: Applying Agile methods in safety-critical application domains 3. Open Source: Can open source be used in safety-critical domains? Yes!

I think with our existing material I can put together something fairly rapidly. However, I would appreciate input in all areas, particularly in describing the applications and on the third theme above on open source. I defer to Luis/David on state machines if either prefers, or can draft it myself. Same for requirements and Brian Blake. Let me know.

Working References

Here is a working list of papers to reference:

• Agile process and Mission Critical Development
  • Gawlas, Julius. Mission-Critical Development WIth XP and Agile Processes. Dr. Dobbs, January 2004
  • Bowers, J., May, J., Melander, E., Baarman, M., and Ayoob, A. Tailoring XP for Large System Mission Critical Software Development. In XP/Agile Universe 2002, D. Wells and L. Williams (eds.). LCNS, Springer-Verlag 2002.
• State Machine Architecture
• Domain-relevant references
  • We should reference MITK from Ivo Wolf as it also uses State Machines albeit in a different way
  • Kohn, L.T., Corrigan, J.M., Donaldson M.S., “To Err is Human: Building a Safer Health System�?, National Academy Press, Washington D.C., 2000. From the MICCAI paper.