Union Hospital Software Upgrade Project

1
Union Hospital Software Upgrade Project

• Team 8

2
Team Members

• Joshua Hertz (PL)
• Programming Group
• Stuart Ford (L)
• Mike Tryczak (L)
• Zach Bertram
• Jeremy Jarvis
• Testing Group
• Ian Price (L)
• Jeff Kelly
• Documentation
• Zach Bertram (L)

PL Project Leader L Group Leader
3
Road Map

• Project Description
• Programming Process
• Solutions Implemented
• Testing Process
• Lessons Learned
• Progress Summary

4
Project Description

• Software used to calculate radiation doses
• Upgrade rendered software unusable
• New scripting language
• Set of 5 macros for Lotus 123
• Required that output not change
• Didnt get very far last quarter

5
Cartoon of the Day
6
Programming Process

• Macro evaluations
• To Do list
• Implementation

7
Problems Found

• Checksum macro fails when run
• Data values not updated when finalized
• Error values produced in ELE marco
• ELE input boxes are misleading
• MU Calc button obscures data
• SmartIcons not clickable after multiple uses

8
Solutions Implemented

• File extensions
• Referencing SmartIcons
• Moved MU Calc button
• Reordered macro execution
• Status of project

9
ELE Macro Interface Upgrade

• The Problem
• GUI was misleading
• Caused users to enter bad information
• Solution
• Redesigned the GUI to make the error less likely
• Drew the users attention to what they were doing

10
ELE Old
11
ELE - New
1
1
2
3
12
Demo

• Mu Calc in action

13
Testing

• Especially important in our project
• Vital that softwares calculations are correct
• Test Plan
• Living document
• Subdivided for better organization
• Testing
• Automated
• By hand
• Verification vs. Validation

14
Test Program

• Document possible testing paths
• Create test script
• Run script on each version of macros
• Compare results

15
Testing Problems

• Cannot test until code is ready
• Modify test plan and test in portions
• Getting automation integrated with Lotus
• Required a lot of effort up front but little
  afterwards
• Tracking and documentation of tests
• Uniform naming and organization scheme

16
Testing Metrics

• 50-70 test cases
• 500 actual tests
• 300 minutes writing and revising test plan
• 500 minutes writing testing utilities
• 400 minutes spent preparing tests and actually
  testing
• 2121 lines of code in script generator and scripts

17
Lessons Learned from Testing

• Automated testing Simplifies Things, but Requires
  Set Up
• Uniform Naming Helps Organization
• Testing Starts well before Development is Done
• Working Once does not Ensure Always Working

18
Quarter Metrics

• 400 Minutes in Meetings
• 3895 Minutes Programming and Research
• Hard to Quantify Lines of Code
• Project is 100 Complete

19
More Lessons Learned

• New People Bring New Ideas
• Everything Takes Longer than You Think
• Deadlines Make People Work
• Simple Things are not Always Obvious
• Reference Material is hard to find for old
  Software.

20
Questions?