|
ID
|
1
|
|
Name
|
Installing GODS
|
|
Date Created
|
11/20/03
|
Created By
|
Andi Sutedja
|
|
Date Last Updated
|
10/30/04
|
Last Updated By
|
Kimmy Lin
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Installing GODS to the physician’s Windows machine
|
|
Desired Outcome
|
GODS is installed on the physician’s Windows machine
|
|
User Goals
|
To use GODS to annotate medical images
|
|
Roles
|
Windows User
|
|
Dependencies
|
|
|
Preconditions
|
- Microsoft .NET Framework installed on the user’s Windows machine
- GODS installer file has been downloaded to the Windows machine
|
|
Scenarios
|
The user wants to install GODS on his Windows machine. She
double-clicks on the GODS installer icon and follows the on-screen
instructions to install GODS.
|
|
Postconditions
|
GODS application installed on the user’s Windows machine with
- GODS shortcut icons on the desktop
- GODS folder listed in the program files including
- GODS
- Manual
- GODS website link
- GODS uninstaller
- GODS uninstaller can be invoked through Add/Remove Program
|
|
Business Rules
|
|
|
Requirements
|
|
|
Exception
|
|
|
Implementation Notes
|
GODS Installer should come with a Microsoft .NET Framework installer.
|
|
ID
|
2
|
|
Name
|
Starting GODS
|
|
Date Created
|
10/30/04
|
Created By
|
Kimmy Lin
|
|
Date Last Updated
|
|
Last Updated By
|
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Starting GODS on the physician’s Windows machine
|
|
Desired Outcome
|
Running GODS on the physician’s Windows machine
|
|
User Goals
|
To use GODS to annotate medical images for patient records
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- GODS installed on the physician’s Windows machine
|
|
Scenarios
|
- The physician wants to use GODS to annotate medical images. She
double-clicks on the GODS shortcut icon on the desktop and starts up GODS application.
- The physician wants to use GODS to annotate medical images. She
clicks on "Start" on the desktop, selects "All Programs", clicks on "GODS"
folder and select GODS and starts up GODS application.
|
|
Postconditions
|
GODS started with a connection to the default database. The
first record of the default database is presented.
|
|
Business Rules
|
|
|
Requirements
|
|
|
Exception
|
|
|
Implementation Notes
|
|
|
ID
|
3
|
|
Name
|
Opening a database
|
|
Date Created
|
10/30/04
|
Created By
|
Kimmy Lin
|
|
Date Last Updated
|
|
Last Updated By
|
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Selecting a patient database to work on
|
|
Desired Outcome
|
The desired patient’s record is brought up in GODS
|
|
User Goals
|
To view / annotate the patient’s medical images from a
patient database
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- GODS started
- The patient database exists in the local file system
|
|
Scenarios
|
The physician select "Options" in GODS menu and select menu item "Import
Database". A dialog shows up and the physician select "Browse"
button to choose the MS Access database he wants to work on. She then
fills in the field mappings between the patient database and the fields
presented in GODS.
|
|
Postconditions
|
The first patient record in the database is shown in GODS
|
|
Business Rules
|
|
|
Requirements
|
Modification to the patient’s medical record is not
allowed.
|
|
Exception
|
|
|
Implementation Notes
|
Currently only supports MS Access database.
|
|
ID
|
4
|
|
Name
|
Selecting a record to open from the current database
|
|
Date Created
|
10/24/03
|
Created By
|
Andi Sutedja
|
|
Date Last Updated
|
10/30/04
|
Last Updated By
|
Kimmy Lin
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Selecting a patient to diagnose from the patient database
|
|
Desired Outcome
|
The desired patient’s record is brought up in GODS
|
|
User Goals
|
To view / annotate the patient’s medical image for
diagnostic purpose
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- A patient database is open in GODS
- The desired patient’s record already exists in the patient database
|
|
Scenarios
|
- The physician clicks on the arrow button in "Name" value field.
A drop-down list shows all the patients’ name in the current database.
She then selects the name of the patient she wants to diagnose.
- The physician clicks on the arrow button in "MRN" value field.
A drop-down list shows all the patients’ MRN in the current database.
She then selects the MRN of the patient she wants to diagnose.
|
|
Postconditions
|
The desired patient record is loaded into GODS
|
|
Business Rules
|
|
|
Requirements
|
Modification to the patient’s medical record is not allowed.
|
|
Exception
|
|
|
Implementation Notes
|
|
|
ID
|
5
|
|
Name
|
Creating a mark on the medical image
|
|
Date Created
|
11/04/03
|
Created By
|
Andi Sutedja
|
|
Date Last Updated
|
10/30/04
|
Last Updated By
|
Kimmy Lin
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Dragging a mark from the mark panel and drop it onto the medical image
|
|
Desired Outcome
|
|
|
User Goals
|
To create a mark on the medical image
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- A patient’s record has been loaded into GODS
|
|
Scenarios
|
The physician clicks and holds the mouse on a mark on the mark panel, drags it over
to the desired position on the image and releases the mouse.
|
|
Postconditions
|
- The "Position" field shows the clock position of the mark
relative to the nipple, i.e. 1 o'clock, 11 o'clock, etc, if position applies the particular mark.
- The "Mark Dimension" field shows the default dimension
1 cm x 1 cm if the field applies to the particular mark.
- Description texts for that mark is added to the summary area.
|
|
Business Rules
|
|
|
Requirements
|
|
|
Exception
|
A mark cannot be created outside the valid area of
the medical image for that marks.
|
|
Implementation Notes
|
|
|
ID
|
7
|
|
Name
|
Moving a mark on the medical image
|
|
Date Created
|
10/30/04
|
Created By
|
Kimmy Lin
|
|
Date Last Updated
|
|
Last Updated By
|
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Moving a mark on the medical image
|
|
Desired Outcome
|
|
|
User Goals
|
To adjust the position of a mark on the medical image
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- A patient’s record has been loaded into GODS.
- The mark is present on the medical image.
- The description text for that mark exists in the summary area.
|
|
Scenarios
|
The physician
clicks and holds the mouse on a mark on the medical image, drags it to
the desired position on the image and releases the mouse.
|
|
Postconditions
|
- The mark is in the new position.
- The "Position" field reflects the new clock position of the mark.
- The description text for that mark in the summary area reflects the new clock position of
the mark.
|
|
Business Rules
|
|
|
Requirements
|
|
|
Exception
|
A mark cannot be moved to outside the valid area
of the medical image for that marks.
|
|
Implementation Notes
|
|
|
ID
|
8
|
|
Name
|
Changing the dimension of a mark
|
|
Date Created
|
10/20/03
|
Created By
|
Bipin Vaddi
|
|
Date Last Updated
|
10/30/04
|
Last Updated By
|
Kimmy Lin
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Changing the dimension of a mark on the medical image
|
|
Desired Outcome
|
|
|
User Goals
|
To make the size of a mark accurate
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- A patient’s record has been loaded into GODS.
- The mark is present on the medical image.
- The description text for that mark exists in the summary area.
|
|
Scenarios
|
- The physician selects the mark she wants to resize on
the medical image and edits the "Mark Dimension" field.
- The physician selects the mark she wants to resize on
the medical image, moves the mouse to the edge of the mark when a two-way arrow appears,
clicks on the two-way arrow, drag the arrow until the image size is desirable and releases
the mouse.
|
|
Postconditions
|
- The mark on the medical image reflects the change of dimension.
- The description text for that mark in the summary area
reflects the change of dimension.
|
|
Business Rules
|
|
|
Requirements
|
|
|
Exception
|
|
|
Implementation Notes
|
This use case is only partially implemented in version 1.0.
Functionalities that are not implemented are listed as follows:
- When a mark’s dimension is changed, the mark on the
medical image doesn’t reflect the new size.
- The second scenario.
These functionalities will be implemented in version 1.1
|
|
ID
|
10
|
|
Name
|
Removing a mark from the medical image
|
|
Date Created
|
10/20/03
|
Created By
|
Bipin Vaddi
|
|
Date Last Updated
|
10/30/04
|
Last Updated By
|
Kimmy Lin
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Removing a mark from the medical image
|
|
Desired Outcome
|
|
|
User Goals
|
To remove a mark on the medical image
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- A patient’s record has been loaded into GODS.
- The mark is present on the medical image.
- The description text for that mark exists in the summary area.
|
|
Scenarios
|
- The physician clicks and holds the mouse on a mark
on the medical image, drags it to outside the valid area of the image. A
dialog then shows up to confirm the deletion. She clicks on the
"Yes" or "No" button to confirm or cancel the deletion
respectively.
- The physician selects the mark on the medical image
and hits the "Delete" key on her keyboard. A dialog then shows up to confirm the
deletion. She clicks on the "Yes" or "No" button to
confirm or cancel the deletion respectively.
- The physician selects the mark on the medical image,
right-clicks on the mark and selects delete from the context menu. A dialog then shows
up to confirm the deletion. She clicks on the "Yes" or
"No" button to confirm or cancel the deletion respectively.
|
|
Postconditions
|
- The mark disappears from the medical image.
- The description text for that mark removed from the summary area.
|
|
Business Rules
|
|
|
Requirements
|
|
|
Exception
|
|
|
Implementation Notes
|
This use case is only partially implemented in version 1.0.
Functionalities that are not implemented are listed as follows:
- The second scenario.
- The third scenario.
These functionalities will be implemented in version 1.1
|
|
ID
|
11
|
|
Name
|
Creating an annotation unrelated to a mark
|
|
Date Created
|
10/30/04
|
Created By
|
Kimmy Lin
|
|
Date Last Updated
|
|
Last Updated By
|
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Creating an annotation to the medical image that cannot be visualized by a mark
|
|
Desired Outcome
|
|
|
User Goals
|
To make annotations to the medical image that cannot be
visualized by a mark
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- A patient’s record has been loaded into GODS.
|
|
Scenarios
|
The
physician clicks on the arrow button in the value field of a character. A
drop-down list shows all the possible values of that field. She then
selects the value for that character.
|
|
Postconditions
|
- Description texts for that annotation is added to the summary area.
|
|
Business Rules
|
|
|
Requirements
|
|
|
Exception
|
|
|
Implementation Notes
|
Kimmy Lin
|
|
Date Last Updated
|
|
Last Updated By
|
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Removing an annotation to the medical image that cannot be visualized by a mark |
|
Desired Outcome
|
|
|
User Goals
|
To remove an annotation unrelated to a mark from the
medical image
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- A patient’s record has been loaded into GODS.
- The value field of the character contains a valid
value for that character.
- The description text for that annotation exists in the summary area.
|
|
Scenarios
|
The
physician clicks on the arrow button in the value field of a character. A
drop-down list shows all the possible values of that field. She then
selects the value "none" for that character.
|
|
Postconditions
|
- Description texts for that annotation is removed to the summary area.
|
|
Business Rules
|
|
|
Requirements
|
|
|
Exception
|
|
|
Implementation Notes
|
|
|
ID
|
15
|
|
Name
|
Uninstalling GODS
|
|
Date Created
|
10/30/04
|
Created By
|
Kimmy Lin
|
|
Date Last Updated
|
|
Last Updated By
|
|
|
Priority
|
High
|
|
Version Implemented
|
1.0
|
Version Last Updated
|
|
|
Description
|
Installing GODS to the physician’s Windows machine
|
|
Desired Outcome
|
GODS is installed on the physician’s Windows machine
|
|
User Goals
|
To remove GODS from the Windows machine.
|
|
Roles
|
Physicians
|
|
Dependencies
|
|
|
Preconditions
|
- GODS installed on the physician’s Windows machine.
- GODS is not running.
|
|
Scenarios
|
- The physician clicks on "Start" on the desktop,
selects "All Programs", clicks on "GODS" folder and select "Uninstall GODS"
and uninstall GODS application.
- The physician clicks on "Add/Remove Program" in the "Control Panel"
window, selects GODS from the list and clicks the "Remove" button.
|
|
Postconditions
|
GODS application removed from the physician’s Windows machine with
- GODS shortcut icons removed from the desktop
- GODS folder removed from the program files (except the database)
|
|
Business Rules
|
|
|
Requirements
|
|
|
Exception
|
|
|
Implementation Notes
|
|