230 likes | 330 Vues
This project aims to investigate performance improvements in claims processing by developing a prototype using caching, threading, and distributed services. The team, led by Jaden, Bruun, Jason Cavett, Justin Glaser, and Erik Raisanen, works closely with sponsor Eric Stephens and advisor Robert Bubacz to optimize processing time, memory and CPU usage. The iterations involve implementing Java Caching System, EJB Specification v2.1, and distributed services for load balancing and machine assignment. The final results provide recommendations for future enhancements and highlight successful team collaboration.
E N D
Claims Service-Oriented Architecture Performance Prototype Team Hooloovoo
Team Members Jaden Bruun Jason Cavett Justin Glaser Erik Raisanen Sponsor Eric Stephens Advisor Robert Bubacz Team Information
Project Description • Project Background • Claims Processing • Performance vs. Modifiability • New Solution Required • Investigate Performance • Develop Prototype • Investigate Performance Improvements
Process • Baseline Development • Three Iterations • Caching • Threading • Distributed Services
Metrics • Performance • Processing Time • Memory Usage • CPU Usage • Effort • Man Hours • Function Points
Baseline • Processing Claims • Validate the Claim • Retrieve Claim History • Determine Member Eligibility • Provider Validation
Iteration 1: Caching • Java Caching System (JCS) • Aspect-Oriented Programming • Spring Framework • Dynamic vs. Static Caching
Iteration 2: Threading • EJB Specification v2.1 • “The enterprise bean must not attempt to manage threads.” • New Solution • Remove EJBs • Thread per Service
Iteration 3: Distributed Services • Replication of the Baseline • Load Balancing • Assigns Work to Machines
Project Assessment: Problem Areas • Distractions • Poster Presentation • Threading • Specification Restriction • No Mitigation Plan
Project Assessment: Working Well • Solid Team • Sponsor Communication • Bi-Weekly Conference Call • Working Sessions • Dual Core iMac
The Project’s Future • Service Initiative • Implementation of Core Services • Provider and Product in Production • CSOAPP Saves Excellus Time • 6 Months of Work • Value with Use