IGSTK Weekly T-con
December 16, 2004
2pm EST

Agenda
------
1. Review and Acceptance of the minutes from Dec. 9 (attached below, All)
2. Iteration 1 wrap-up (All)
   - See some ideas for review activities below
   - Expect LOE for review to be low given the time and the amount
     of code - who can sign up for what next week?
   - Expectations for transitioning to Iteration 2.
3. IGSTK textbook update (KC)
4. Update on any other outstanding Action Items (All)
5. Summary of Action Items and Schedule next meeting (Sohan, KG)

Review Activities for 12/20-12/22:
----------------------------------
1. Test build process of demo application and core packages
   - Should be done by non-developer members of the team:
     KG, KC, BB, Stephen (?)
2. Verify functionality of the demo application
   - Verify it functionally works and provides "interesting"
     functionality
3. Validation of the demo application
   - Does this demo application fulfill our requirements and
     expectations?
4. Verification and Validation of the core packages
   - Tracker, Viewer, State Machine, etc.
   - Are we good on the dashboard?
5. Code reviews
   - Are we doing these?
   - What code needs to be reviewed now before we get further?

Dates:
------
End of first iteration: Dec. 16. (today! whoop whoop)
Code freeze: Dec. 17.
Review: Dec. 20 - 22. 
Wrap-up first iteration: Dec. 23. 
Next meeting: TBD

Minutes (Thanks again Sohan!)
-----------------------------
IGstk Weekly Meeting, Dec. 09, 2004

Participants:
Kevin Cleary 
Kevin Gary 
Brian Blake
Stephen Aylward
Julien Jomier
Sohan Ranjan 

1. A module named "Sandbox" has been created for collaborative development.
   This module has a sub-dectory for "Examples" which contains the demo 
   application, which is under development. 

2. Demo Application

   The description, user story and requirements is on the IGstk Wiki for review.

   Stephen said that this application would provide a platform for future
   application developments based on IGstk.

3. Requirements
   KGary and Brian has a discussion on requirements. KGary may visit DC in
   January to clean up and finalize the functional requirements.

4. Workflows
   Brian has put the workflows on Wiki for review.
   UNC Radiologists didn't show up on Tuesday to review the workflows.
   KCleary has given a copy to Dr. Levy for review. Feedback awaited.
 
5. Viewer Requirements
   Luis and Julien have put viewer requirements on the Wiki. 
   KCleary said that the requirements are at a very high level. KGary said that
   we need to define functionality apart from putting specifications.
   Stephen added that people are going in different directions with 
   workflows and requirements. We may stick to requirements from a
   radiologists viewpoint, and let software follow.

6. Scope of development
   The scope of development can not be expanded in a nebulous way. It was decided 
   that we would stick to the deliverables put in the IGstk Phase-II proposal. 

7. Next t-con meeting on THURSDAY DECEMBER 16 at 2 PM EST.