1 / 34

JUDICIAL IMPLEMENTATION OF GJXDM

JUDICIAL IMPLEMENTATION OF GJXDM. PAT BROOKS LARRY BRENDEL JIM BOESCHEN RICHARD TEWS. Agenda. JUDICIAL IMPLEMENTATION OF GJXDM GJXDM Users Conference September 2006. Project Background Agile – an Application Development approach Technologies Utilized Providers perspective

phelan-mcmillan
Télécharger la présentation

JUDICIAL IMPLEMENTATION OF GJXDM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JUDICIAL IMPLEMENTATION OF GJXDM • PAT BROOKS • LARRY BRENDEL • JIM BOESCHEN • RICHARD TEWS

  2. Agenda JUDICIAL IMPLEMENTATION OF GJXDMGJXDM Users Conference September 2006 • Project Background • Agile – an Application Development approach • Technologies Utilized • Providers perspective • Lessons learned • GJXDM Projects

  3. SAVED TIME – SAVED MONEY Saved Development Time Reduced By 50-75%

  4. COURT AUTOMATION VISIONService & Justice Access 1994 49 49 • Reduced costs to the litigant and taxpayer • Greater efficiency • Wider access and enhanced accountability • Timeliness in processing of cases without sacrificing the quality of justice • Utilizing similar facilities statewide based on standards for hardware, software and common data definitions • The ability to interface electronically with other state and local systems and networks

  5. STANDARDIZE JIS DECISION • DECIDED TO STANDARDIZE JIS SYSTEMS • CHOSE ORACLE-BASED SOLUTION • BEGAN CONVERSIONS • 18-24 MONTHS CONVERSION TIME PER COURT

  6. BACKGROUND INFORMATION Custom conversion programming was required for each legacy system: • Limited code reuse • 18-24 months development time • Serial development activity • Limited documentation on a targeted platform

  7. BUSINESS CHALLENGES • Faster conversion of legacy case information • Case filing interfaces for adult and juvenile case types • Prepare for national data exchanges

  8. APPROACH TO BUSINESS CHALLENGES • Conducted research on GJXDM projects • Sought out experts • Developed a Request for Proposal • Established the development team (Internal/External Resources) • Established proof of concept project • Developed a project release plan with prioritized functionality • Iterative release of application • Maintain application

  9. GET A CONSULTANT WITH EXPERIENCE YOU CAN TRUST When building relationships with vendors…. Partner with consultants you can trust.

  10. SOFTWARE PROJECTSVENTURE INTOUNCHARTED TERRITORY

  11. SOFTWARE ENGINEERING • Iterations • Stories • Stand up meetings • Refactoring • Unit testing

  12. EARLY LESSONS • STORY COMPLETION SHOULD BE WITHIN AN ITERATION • REFACTOR EARLY TO AVOID LONG-TERM CONSEQUENCES

  13. ANT CVS WinCVS/Tortise Cruise Control Eclipse Digestor J-unit Hibernate/iBatis Maven MiddleGen TECHNOLOGIES USED • MQSeries • Oracle PL/SQL • WebSphere Application Server • WebSphere Developer Suite • XML Beans • XML Spy • XML Buddy • JAVA • Lotus Notes • Microsoft Excel • Axis

  14. DEVELOPMENT TASKS • Construct Prototype • Data Analysis • Define data analysis team (involve right people at the right time) • Collected/define data elements • Establish information exchange point (JIS Knowledge Database) • Create the object model • Map to the GJXDM • Create Extensions • Create Subset • Create Constraints

  15. DEVELOPMENT TASKS • Create Java data objects to map data • Construct Java model (Eclipse) • Create Database to Java data object mapping (Hibernate/iBatis) • Create XML to Java mapping (Digester) • Create rules (Java code) • Create constraints • Developed Unit test (Cruise Control) • Developed Stress test (Cruise Control) • Create sample XML data • Published the IEPD (Information Exchange Package Document)

  16. A DATA EXCHANGE BUILT WITH XML AND WEB SERVICES DELIVERY - INTEGRITY - SECURITY

  17. LESSONS LEARNED ABOUT DATA EXCHANGES • Development of first secure Web service • (2 programmers, 3 months) • Second service • (1 programmer, 1 week) • Published information or samples of a secure Web service is not readily-available

  18. DATA SHARING IS POSSIBLE WITHIN AND BETWEEN ORGANIZATIONSDEVELOP INFORMATION EXCHANGE POINTSSPRINGBOARD FOR FUTURE DEVELOPMENT EFFORTS

  19. LEGACY SYSTEM CONVERSION • MAP DATA FROM LEGACY SYSTEM TO NEW SYSTEM (KNOWLEDGE DATABASE) • EXTRACT DATA FROM LEGACY SYSTEM • LOAD DATA INTO ORACLE DATABASE • CREATE DATABASE OBJECTS • TUNE FOR OPTIMAL PERFORMANCE IN CREATING XML DOCUMENTS • CONSOLIDATE DEMOGRAPHIC INFORMATION FOR PEOPLE IN LEGACY SYSTEM • BUILD XML DOCUMENTS FOR CASES • LOAD XML DOCUMENTS INTO DATABASE • CORRECT CASES WHERE VALID XML DOCUMENT COULD NOT BE BUILT • CORRECT CASES WHERE ERROR OCCURRED WHEN LOADING CASE INTO THE DATABASE

  20. EARLY LESSONS FROM A PROVIDER PERSPECTIVE • BUILD ITERATIVELY – • SMALL PIECES END-TO-END • REFACTOR DOCUMENTATION AND CODE • COLLABORATE • MAPPING BUSINESS MODEL TO GJXDM EXCHANGE TRANSLATION • VALIDATE XML AGAINST SCHEMA BEFORE SUBMITTING

  21. INTERESTING PROJECT STATS • Modeled 647 data elements from GJXDM • Developed 3,400 separate Java programs • Stored data in 51 different tables • Converted over 3,000,000 cases • Converted and consolidated over 3,000,000 party records • Project began in April 2005 • Roughly 72 million records converted as of June 2006

  22. LESSONS LEARNED – OUR VIEW OF THE PATH TO SUCCESS • FIND EXECUTIVE SPONSORSHIP • ESTABLISH GOVERNANCE STRATEGY • CONDUCT RESEARCH • EDUCATE YOUR TEAM • PARTNER WITH EXPERTS • ESTABLISH AN APPROPRIATE BUDGET • ESTABLISH PROJECT TIMELINES • PRIORITIZE • DO A PILOT / PROOF OF CONCEPT • INCREMENTS AND ITERATIONS • HAVE A CLEARLY DEFINED PROJECT SCOPE • UNIT TESTS SHOULD TEST REAL BUSINESS PROCESSES

  23. …LEAD, FOLLOW, OR GET OUT OF THE WAY Meeting The Target Date Meeting The Target Date • Implementation date set prior to project initiation • Avoid “Analysis Paralysis” • Pick a path, decision making is essential • Be “Agile” • Rigidly reassess decisions • Implementation date set prior to project initiation • Avoid “Analysis Paralysis” • Pick a path, decision making is essential • Be “Agile” • Rigidly reassess decisions

  24. REALIZE THE VISION • Improve data accuracy • Decrease administrative costs • Enabling parallel development • Streamline processes • Developed automated processes • Reduce case filing time • Improves professionalism • Increased Reusability • Eliminate Redundancy • Broadened Technical Skills

  25. GJXDM PROJECTS • Criminal Initial Filing • Transfer of criminal information from the local prosecutors to the court • E-Warrants • Transmission of warrant information to state and local law enforcement • Civil Initial Filing • Transmission of civil case information from attorneys to the court • CaseNet Web Service • Extension of current award winning public solution • E-Filing • Electronic submission of case information from litigants to the court

  26. DISCUSSION Q & A

  27. CONTACTS Larry Brendel Programmer/Analyst Supervisor Information Technology Office of State Courts Administrator 573.526.8312 larry.brendel@courts.mo.gov Patrick Brooks Manager, Applications Development and Administration Information Technology Office of State Courts Administrator 573.526.8885 pat.brooks@courts.mo.gov Jim Boeschen Programmer/Analyst Supervisor Information Technology Office of State Courts Administrator 573.526.8830 jim.boeschen@courts.mo.gov Richard Tews Asynchrony Solutions Director Technology Services 314.678.2264 314.757.7690 mobile rich.tews@asolutions.com

More Related