1. Consolidated Disease Demographics Reporting System CMSI 641 Fall 2002 Craig E. Ward Harshitha Elango

2. 11/29/02Ward,Elango2 Agenda Introduction - Craig Introduction - Craig CDDRS Purpose - Craig CDDRS Purpose - Craig High-level Architecture View - Harshitha High-level Architecture View - Harshitha Database Design - Harshitha Database Design - Harshitha Design Architecture View - Craig Design Architecture View - Craig Implementation Patterns - Craig Implementation Patterns - Craig Hardware and Software Selections - Craig Hardware and Software Selections - Craig Verification and Validation Processes - Harshitha Verification and Validation Processes - Harshitha Questions - for anyone Questions - for anyone

3. 11/29/02Ward,Elango3 Purpose Trends of diseases over time Trends of disease progression over geographic areas Development of new occurrences of disease outbreaks Combinations of the above “The Consolidated Disease Demographics Report System (CDDRS) is a data warehouse of the demographics related to diseases.”

4. 11/29/02Ward,Elango4 High-level Architecture

5. 11/29/02Ward,Elango5 Database Design Primary Entities Subject Subject Disease Disease Report Report Report Source Report Source Location Location

6. 11/29/02Ward,Elango6 Database Design Entity Relationship Diagram

7. 11/29/02Ward,Elango7 Database Design: Attributes

8. 11/29/02Ward,Elango8 Design Architecture: Use Cases Load Data Load Data Extract Data Extract Data Query Data Query Data Database Administration Database Administration Error Correction Error Correction

9. 11/29/02Ward,Elango9 Design Architecture: Components Input Filters Input Filters Consolidation Engine Consolidation Engine Query Subsystem Query Subsystem GUI Front-end GUI Front-end Database Database

10. 11/29/02Ward,Elango10 Components Diagram

11. 11/29/02Ward,Elango11 Implementation Patterns Classes identified Classes identified Pattern splits functionality into three objects Pattern splits functionality into three objects A Data Access Object A Data Access Object Responsible for accessing the database engine Responsible for accessing the database engine A “Bean” Object A “Bean” Object The “real” entity The “real” entity A Data Model Object A Data Model Object A read-only copy of an entity A read-only copy of an entity

12. 11/29/02Ward,Elango12 Implementation Patterns Diagram

13. 11/29/02Ward,Elango13 Hardware & Software Commodity Intel hardware Commodity Intel hardware Red Hat Linux Red Hat Linux Unix-class operating system Unix-class operating system Oracle 9i Oracle 9i High quality SQL High quality SQL J2EE Application Server J2EE Application Server JBuilder GUI Development JBuilder GUI Development HL7-to-XML Filter HL7-to-XML Filter

14. 11/29/02Ward,Elango14 Verification & Validation Testing Methodology Testing Methodology Design Reviews Design Reviews Requirement Traceability Requirement Traceability Test Recording Procedures Test Recording Procedures

15. 11/29/02Ward,Elango15 Questions Can we do this?