SAS Corporate Compliance – A case study for developing.ppt

Presentation title SAS? Corporate Compliance – A case study for developing reusable  J2EE applications Zhiyong Li Lead Application Architect SAS Pharmaceutical / Corporate Compliance Software Development Agenda Background SAS Drug Development Key Architecture Components Reuse Summary Demo The Sarbanes-Oxley Act of 2002 - What is It? Contains 11 Titles, 66 Sections §404 – Management Assessment of Internal Controls §302 – Corporate Responsibility for Financial Reports §409 – Real-time Issuer Disclosures The Sarbanes-Oxley Act of 2002 - Who is Impacted? All public companies Foreign-based companies / foreign subsidiaries of US companies Chief Executive Officer and Chief Financial Officer Finance, internal audit, audit committee of the Board of Directors, Chief Risk Officer, Chief Audit Officer IT, Sales Marketing, Shipping Receiving… theoretically the entire company SAS? Corporate Compliance Secure, auditable repository, versioning, electronic signatures Highly configurable Assessment-oriented workflow Documentation for control procedure, testing activities, issues, etc. Report for viewing control effectiveness, outstanding issues, etc. J2EE web application with zero footprint client SAS? Drug Development Centralized object repository, versioning and electronic signature Enables compliant environment Data transformation and integration Data exploration Statistical analysis and reporting Study reports and submissions (Very) Thin client SAS Drug Development and SAS Corporate Compliance Key Comparison Similarities Compliant solution Strong audit trail and security functionalities Web-based platform Content Management functionality objects, documents, versioning, electronic signing Differences SAS Drug Development Clinic trial oriented concepts (studies, protocols, submissions) Java Swing applications SAS Corporate Compliance Process oriented workflow for control self assessment Agenda Background SAS Drug Development Key Architecture Components Reuse S