Analysis and Reporting Toolset (A&RT): Lessons on how to develop a system with an external partner David Smith AstraZeneca.

Slides:



Advertisements
Similar presentations
Implementation of a Validated Statistical Computing Environment Presented by Jeff Schumack, Associate Director – Drug Development Information September.
Advertisements

Calyxinfo Walking through Calyx Info The Organisation.
Upgrading the Oracle Applications: Going Beyond the Technical Upgrade Atlanta OAUG March 19, 1999 Robert Cooney.
Systems Development Environment
CS487 Software Engineering Omar Aldawud
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Information Resources Management January 23, 2001.
System Construction and Implementation Objectives:
Alternate Software Development Methodologies
Chapter 8 Managing IT Project Delivery
Components and Architecture CS 543 – Data Warehousing.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
1 Walk-in slide. 2 How to Manage a System Upgrade The Good, The Bad and The Ugly of Conversions David Cervelli Managing Consultant April 25, 2006.
Ihr Logo Data Explorer - A data profiling tool. Your Logo Agenda  Introduction  Existing System  Limitations of Existing System  Proposed Solution.
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
Contents Integrating clinical trial data Working with CROs
Software Development Stephenson College. Classic Life Cycle.
Antje Rossmanith, Roche 14th German CDISC User Group, 25-Sep-2012
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Confidential - Property of Navitas Accelerate define.xml using defineReady - Saravanan June 17, 2015.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Decision Support System Development By Dr.S.Sridhar,Ph.D., RACI(Paris),RZFM(Germany),RMR(USA),RIEEEProc. web-site :
Metadata driven application for data processing – from local toward global solution Rudi Seljak Statistical Office of the Republic of Slovenia.
The Systems Development Life Cycle
Methodologies. Contents Waterfall Model Evolutionary Models Incremental Development.
Systems Life Cycle A2 Module Heathcote Ch.38.
Systems Analysis and Design in a Changing World, Fourth Edition
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Managing Challenging Projects Presented to the class of: Dr. Jane Mackay M.J. Neely School of Business.
Bina Nusantara 19 C H A P T E R SYSTEM CONSTRUCTION AND IMPLEMENTATION.
Chapter 1: Introduction Omar Meqdadi SE 3860 Lecture 1 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Software Design and Development Development Methodoligies Computing Science.
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
Methodologies/Life Cycle Models
Information Systems Development
Introduction to Systems Analysis and Design
Principles of Information Systems Eighth Edition
Chapter 1 The Systems Development Environment
Methodologies and Algorithms
Software Prototyping.
Leveraging R and Shiny for Point and Click ADaM Analysis
Chapter 1 The Systems Development Environment
CASE Tools and Joint and Rapid Application Development
Chapter 1 The Systems Development Environment
Systems Analysis and Design
Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Chapter 1 The Systems Development Environment
Information Systems Development
Advantages OF BDD Testing
MBI 630: Systems Analysis and Design
Using the Checklist for SDMX Data Providers
Tomaž Špeh, Rudi Seljak Statistical Office of the Republic of Slovenia
Gathering Systems Requirements
Systems Construction and Implementation
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
System Construction and Implementation
Systems Construction and Implementation
The Waterfall Model Also known as: classic life cycle, the waterfall model, the linear model Rarely projects are sequential (allows iteration indirectly)
Gathering Systems Requirements
Information Systems Development (ISD) Systems Development Life Cycle
Chapter 1 The Systems Development Environment
SDLC (Software Development Life Cycle)
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Analysis and Reporting Toolset (A&RT): Lessons on how to develop a system with an external partner David Smith AstraZeneca

Content Introduction Project Initiation Software development methodology Planning: Getting it right Collaboration: The importance of experts Sizing the application Implementation Lessons

Introduction For some years following Astra and Zeneca’s merger clinical statistics and programming groups operated in a diverse way The A&RT project was setup to develop a standard analysis and reporting environment based on a set of integrated applications

Project Initiation A complete User Requirement Specification (URS) was developed by the business A basic technical architecture was specified as part of the URS. This defined the requirements for Powerful UNIX Platform User interface Data input, processing, reporting and publishing functionality

A&RT Technical Solution CTP - UNIX Transfer System In-house Solution Web Application In-house Macros RDB SDTM Creation of reporting datasets Output Tool Creation of tables and listings SAS- Publish Provision of OODS Publishing Submission In-house Solution Study setup Vendor Solution Word XML GUI Randomisation Raw Clinical Data

Project Initiation Functional business user requirements were also defined Development, validation and production environments Database folder structures for raw, SDTM and reporting databases (RDB) Folder structure for SAS programs and outputs Folder structure for publishing statistical tables and figures

Data flow through technical components… A&RT Common Technical Platform: SAS v9.1 GEL Draft Document templates: CTD, CSR SAS Raw Datasets from Data Capture After data base lock Randomisation Data from GRand interface Dev RDBVal RDBProd RDB SAS Raw Datasets from Data Capture Early data SAS Macros/code to convert to SDTM format SDTM datasets SAS Macros/code to create RDB, including derived variables Validated SAS Code to create RDB Validated SAS code to create SDTM Sample randomisation file Common Web Interface & Metadata Repository Development EnvironmentValidation Env SAS-Publishing System (GEL) interface Production Env Output Tools (SAS Macros) Validated Output Tools A&R Data in Tables & Listings of CSR/CTD Raw data store

Project Team Organisation A joint business and IS and business team was formed with a project leader from each function. Controlled by a IS / business steering group Leading a technical delivery team The formation of a Business Design sub team was a crucial part of the project Provided the IS team with business application development expertise A separate implementation and change management team was formed To manage drug project migration and process change

Steering Committee Implementation Change Management Technical Delivery Team VP, IS Business Project Leader Business Training Lead IS Quality Management Framework Leader Business Implementation Leader IS Project Architecture Lead Business Design Leader IS Project Analyst IS Project Leader CTP Delivery Leader Implementation Leader UK S S US A&RT Project Governance Structure January 2006 Sponsor VP, Global Medical Sciences VP, Clinical Information Science LEAD IS Service Delivery Framework Implementation Leader IS Partner Delivery Leader

A&RT Business Design Organisation Business Design Leadership Team Output Tools Common Technical Platform UNIX / SAS Metadata and Mapping SDTM / RDB Tools ART / GEL GUI Team Leader Interfaces / PDF

Software Development Methodology AstraZeneca IS followed a development methodology commonly known as the ‘waterfall’ method. Also known as the Classic Life Cycle Model (or) Linear Sequential Model An alien methodology to the business application development programmers More familiar with a flexible iterative prototyping methodology The business experts had to define precise and detailed functional requirements before any code was developed Formal sign-off required between each development step

Waterfall Software Development Method

Planning: Getting it right Reality was not as easy as the waterfall theory suggested Thorough business analysis is required if the product design is to be sufficiently complete Missing detail at this design stage can have serious consequences later on The project team significantly underestimated the time required to develop the detailed design Despite a significant effort in time and manpower we still had to perform many iterations of the design specification after formal sign-off

Planning: Getting it right When we did receive our first test versions of the system significant problems arose hardware infrastructure was not ready to run the applications built by the development partner GUI screen and database functions did not work when loaded into the AstraZeneca environment The partner delivered GUI and Oracle database that controlled the functionality of the system it did not work along side the AZ SAS servers The development partner had followed our design specification but AZ had not considered how this might be misinterpreted given the complex nature of clinical data

Collaboration: The importance of experts Mistakes in design and planning had to be corrected fast A rapid iterative development process was initiated A close team of business and development partner experts was formed Business process experts SAS application experts A shared development environment was created Domain knowledge of the partner was significantly improved This expert to expert collaboration continued through development, testing and implementation

Sizing the Application The first release of A&RT appeared to function well until the user base started to expand Issues were soon detected that had gone unnoticed during the formal system and user acceptance testing What works for 5 studies and 10 users did not work for 100 studies and 200 users In the haste to deliver, adequate performance testing had not been performed we realised too late how critical formal load testing was to the final success of the tool

Implementation – Success? A&RT was delivered into full production use in 2009 Functionally the system did what is was designed to do so this part was a success Still an ongoing challenge to fully deliver the system performance users expect. This is the subject of ongoing system enhancements based on load testing performed late in the project.

Lessons (1) Before embarking on a complex system build consider the possibility that a vendor ‘off the shelf’ supplied solution might be more cost effective Compare expenses that include all in-house resource use over an extended time Resist the desire by IS to follow a waterfall approach Business experts must be part of a prototype review team Follow the agile software development methodology based on iterative and incremental development Business and IS development experts must work together as a team

Lessons (2) IS developers must have access to experts e.g. SAS application experts, Oracle experts and system performance experts. Plan for a number of prototype iterations to be performed Recognise resource will be required for an extended period Project planners necessarily have an eye on budgets and timelines but recognise that more time may be needed in reality to ensure robust testing. Include non-functional requirements describing expected user and data load on the system along with the expected performance Always include load testing

Questions