consolidated disease demographics reporting system cmsi 641 fall 2002 craig e. ward harshitha elango

Consolidated Disease Consolidated Disease Demographics Reporting Demographics Reporting

SystemSystemCMSI 641 Fall 2002CMSI 641 Fall 2002

Craig E. WardCraig E. Ward

Harshitha ElangoHarshitha Elango

11/29/0211/29/02 Ward,ElangoWard,Elango 22

AgendaAgenda

Introduction - Introduction - CraigCraig CDDRS Purpose - CDDRS Purpose - CraigCraig High-level Architecture View - High-level Architecture View - HarshithaHarshitha Database Design - Database Design - HarshithaHarshitha Design Architecture View - Design Architecture View - CraigCraig Implementation Patterns - Implementation Patterns - CraigCraig Hardware and Software Selections - Hardware and Software Selections - CraigCraig Verification and Validation Processes - Verification and Validation Processes - HarshithaHarshitha Questions - for Questions - for anyoneanyone


PurposePurpose

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.”


High-level ArchitectureHigh-level Architecture


Database Design Database Design Primary EntitiesPrimary Entities

SubjectSubject DiseaseDisease ReportReport Report SourceReport Source LocationLocation


Database DesignDatabase DesignEntity Relationship DiagramEntity Relationship Diagram


Design Architecture: Use CasesDesign Architecture: Use Cases

Load DataLoad Data Extract DataExtract Data Query DataQuery Data Database AdministrationDatabase Administration Error CorrectionError Correction


Design Architecture: Design Architecture: ComponentsComponents

Input FiltersInput Filters Consolidation EngineConsolidation Engine Query SubsystemQuery Subsystem GUI Front-endGUI Front-end DatabaseDatabase


Components DiagramComponents Diagram


Implementation PatternsImplementation Patterns

Classes identifiedClasses identified Pattern splits functionality into three objectsPattern splits functionality into three objects A Data Access ObjectA Data Access Object

Responsible for accessing the database engineResponsible for accessing the database engine A “Bean” ObjectA “Bean” Object

The “real” entityThe “real” entity A Data Model ObjectA Data Model Object

A read-only copy of an entityA read-only copy of an entity


Implementation Patterns Implementation Patterns DiagramDiagram


Hardware & SoftwareHardware & Software

Commodity Intel hardwareCommodity Intel hardware Red Hat LinuxRed Hat Linux

Unix-class operating systemUnix-class operating system Oracle 9iOracle 9i

High quality SQLHigh quality SQL J2EE Application ServerJ2EE Application Server

JBuilder GUI DevelopmentJBuilder GUI Development HL7-to-XML FilterHL7-to-XML Filter


Verification & ValidationVerification & Validation

Testing MethodologyTesting Methodology Design ReviewsDesign Reviews Requirement TraceabilityRequirement Traceability Test Recording ProceduresTest Recording Procedures


QuestionsQuestions

Can we do this?Can we do this?

consolidated disease demographics reporting system cmsi 641 fall 2002 craig e. ward harshitha elango

Documents