JDI open source supplement

From IGSTK

Contents 1 Purpose 2 Outline 2.1 Abstract 2.2 Introduction 2.3 System Architecture 2.4 Software process 2.5 Building IGSTK user community 3 Paper write up schedule 4 Comments 5 Paper Draft

Purpose

The purpose of the paper is to give an overview of the IGSTK toolkit. The paper presents IGSTK system architecture, software process used in the project, and procedures that are being followed to build a user community.

Outline

Abstract

Introduction

1. General background
   1. Image guided surgery systems
   2. Open source software for medical imaging and bio-informatics
2. IGSTK
   1. Project history: collaborators, funding source
   2. Project Objectives

System Architecture

1. Overview of a component-based framework
2. Short descriptions of each components

Software process

1. IGSTK best practices
2. Test driven development
   1. Dashboard
   2. Bug Tracking
   3. Code Coverage
   4. Dynamic Testing

Building IGSTK user community

1. Expanding user base
   1. Maintaining users and developers mailing list
   2. Organizing hands-on workshops and demonstrations
   3. Providing example applications
2. Collaborations with research institutions
3. Preventing intellectual property burdens
4. Publications: papers and books

Paper write up schedule

1) Paper outline discussion: April 26
2) First draft : May 6
3) Collect feedback on first draft: May 13
4) Second draft  : May 20
5) Final feedback : May 24
6) Paper submission : May 30

Comments

Kevin Gary

• Architecture should include SM and Events with a focus on safety. My guess is you planned on working that in but thought I'd mention it.
• I have heard us say "test-driven development" within the IGSTK team before, but I have to question this. I t doesn't seem to me that we really do TDD, which is the practice of writing a failing test first, then writing a little code to make it pass, then writing a little more test code, writing a little more app code to make it work, etc. I readily agree that unit tests play a major role in IGSTK, but I don't think TDD as it is understood in the community is really followed.
• You say Dynamic Testing in 4.b.iv where I think you mean Dynamic Analysis.
• Section 5 is a great idea, it is not discussed enough in the literature. One concept that is sometimes discussed is how the social organization of the team maps onto design and code acceptance decisions - things like who decides who gets to check what in to CVS?

Paper Draft

Media:IGSTK_JDI_06-01-2007.doc

Media:IGSTK-JDI-Submission-06072007.doc