From IGSTK

Contents 1 Iteration Requirements 1.1 To Do: move remaining requirements from Iteration 6 to Iteration 7 1.2 General Requirements 1.2.1 Callibration Components 1.2.2 Tracker Components 1.2.3 Landmark Registration Component 1.2.4 Spatial Object Components 1.2.5 Image I/O 1.2.6 View Components 1.2.7 State Machine

Iteration Requirements

To Do: move remaining requirements from Iteration 6 to Iteration 7

Note: Add a note to each requirement indicating whether it is "new" or "approved".

General Requirements

Callibration Components

1. [JZ 11/28/05] The calibration components will provide the functions to calculate the transform from the pointer focus position to the tracker position (igstkPivotCalibration), and the transform from freehand ultrasound image plane to the tracker position (igstkUltrasoundCalibration).
2. [JZ 11/28/05] The igstkPivotCalibration class will be added in the Iteration 7 and igstkUltrasoundCalibration will be added before Itertation 8 is released for ultrasound application.
3. [JZ 11/28/05] The igstkPivotCalibration class will get the input samples (rotation and translation) from the pivoting trackers, and return the calibration transform.
4. [JZ 11/28/05] The calibration RMS will be calculated to evaluate whether a feasible calibration transform is computed.
5. [JZ 11/29/05] The pivot position will be calculated.
6. [JZ 11/29/05] The igstkPivotCalibration will provide the function to retrieve the input sample used to calculate the calibration transform.
7. [JZ 11/29/05] The igstkPivtoCalibration will provide the function to simulate the pivot position for any input rotation and translation from the calculated calibration transform.

Tracker Components

1. [DG 11/23/05] The tracker will provide support for tool buttons and foot pedals, so that these can be used to drive actions in the application.
2. [DG 11/23/05] The tracker will inform the application of which tools are available via events which carry information that allows the application to identify the tool and tool type.
3. [DG 11/23/05] The tracker will inform the application via an event when a tool goes offline due to the tool becoming unplugged or malfunctioning.

Landmark Registration Component

1. [AE 11/23/05] A robust algorithm will be implemented to verify the registration

Spatial Object Components

1. [PC 11/23/05] Add Mesh Spatial Object for representing tumors
2. [PC 11/23/05] Add group spatial objects to model different tracking tools, such as NeedleSpatialObject
3. [PC 12/08/05] All transforms sent to the spatial object should be private

Image I/O

1. [AE 12/13/2005] Taking screenshots and saving them as image file

View Components

1. [PC 11/23/05] Add 2D annotations to the Views
2. [PC 11/23/05] Add oblique view plane support in View2D

State Machine

1. [LI 12/14/05] The transition table of the State Machine must be fully populated. The method SetReadyToRun() will verify the completness of the transition table.
2. [LI 12/14/05] When SM actions may result in failure or success, the method that triggers the action must be called "AttemtTo...", and it should move the SM into a state labeled "AttemtingTo...". In this state the SM will have an observer connected to the class that will report the success or failure of the operation. That class will report this information in the form of an Event. The event will be translated into a SM input and will take the SM out of the "AttemptingTo..." state.