Team 1 Health Insurance Management System (HIMS)

Team Members Allen Tucker Ashley Plier Tara Chengalvala Ibrahim Elsaeed Venkat Reddy Jakka Sundeep Yama

Agenda Project Description Project Assessment Development Process Scheduling Team Organization Structure

Agenda (cont.) Project Resources Test Strategy Example Tests Project Summary Lessons Learned

Project Description Manage the human resources of a Health Care Maintainers Organization (HMO) Web based access to health insurance database (emphasis on claims data) Targeted Actors  Members – Individual who has a plan in the system  Employers – Employment source of members  Providers – Doctors, physician, etc.  Operator – Maintenance and management of the system

Project Assessment The good…  Use cases  UML Models  Design Rational (e.g. why certain aspects un-modeled) The bad…  Requirements management Well written, but poorly enumerated The ugly…  Traceability – almost none present

Development Process Begin post Inception phase Borrow from Agile  Test early, test often  Continually integrate Collaborative Behaviors  User Account Management  Health Account Management

Scheduling Three week long iterations with use cases being divided up into behaviors.

Scheduling (cont.) Each week in an iteration focuses on a different use case.

Organizational Structure Validation Team Integration Team Component Team Code Defects Binaries C(x) C(y) Stubs Exe. Drivers C(s) Ver. 0.01

Organizational Structure Validation Team Integration Team Component Team Code Defects Binaries C(x) C(y) Stubs Exe. Drivers C(s) Ver Unit and Component (package) level development Stubs “White Box” Testing

Organizational Structure Validation Team Integration Team Component Team Code Defects Binaries C(x) C(y) Stubs Exe. Drivers C(s) Ver Integrating components for collaborative behaviors Drivers “White Box” Testing

Organizational Structure Validation Team Integration Team Component Team Code Defects Binaries C(x) C(y) Stubs Exe. Drivers C(s) Ver Functional Testing Project Documentation “Black Box” Testing

Organizational Structure Validation Team Integration Team Component Team Code Defects Binaries C(x) C(y) Stubs Exe. Drivers C(s) Ver. 0.01

Project Resources  Development Environment: Netbeans 6.5  Implementation Language: Java  Apache ANT  EMMA  JUNIT  Version Control:  Defect Tracker:  Documentation:

Test Strategy  Use Case Driven Approach (Functional) Dependent on Traceability Data  Design models only  75% statement code coverage

Example Tests  Design Model Inspection  Functional Test Case (System Level Test)  Integration Test Case  Unit Test Case

Design Model Inspection

Functional Test Case

Integration/Unit Test Organization HIMS

Integration/Unit Test Organization HIMS Package structure delivered in design

Integration/Unit Test Organization HIMS Contains integration level code (and gui)

Integration/Unit Test Case

Baseline testing within tester class’s constructor

Integration/Unit Test Case Error Guessing Technique Expected vs. Actual Comparisons

Project Summary  Natural grouping of features mandated schedule adjustments…(birds of a feather)

Project Summary (cont.)  Design Model Results GUI Design Work

Project Summary (cont.)  Statement coverage inadequate  Moved to boundaries and error predictive methods

Project Summary (cont.)  Defects exists within the system.

Project Summary (cont.)  Insufficient amount of functional regression testing for certain features.

Project Summary (cont.)  Personnel shifts due to deliverable deadlines  Outstanding Work Items Functionality (use cases not implemented) Defects

Lessons Learned  Guided inspection of models decrease wasted coding effort  White box statement coverage insufficient Adopt new strategy given chance to do complete rework of project (e.g. boundaries, error guessing)  Flexible Team