Methodology

1. caBIG® Clinical Information Suite QA Process & Tooling – Ensuring Quality in an Agile Delivery Project Jeff Pierce, Jim Jones, Kevin Gann, AmrutRao, Aviva Mordetsky, PradeepDharmavarapu, Brian Bell, Daniel Lunski, Aaron Evans Ekagra • Overview • The National Cancer Institute’s (NCI) caBIG Clinical Information Suite project is providing a comprehensive suite of software specifications and open-source software modules that together make up an oncology-extended Electronic Health Record capability. • The project utilizes a hybrid methodology comprised of the best practices from both the Rational Unified Process and Agile methodologies. • Quality Assurance’s role in the fast-paced, iterative and incremental project is to assure the completeness and correctness of the three key sets of deliverables: • Software specifications • Reference caBIG Clinical Information Suite Application Implementation • Web Service(s) Reference Implementations • Quality Assurance has developed a strategy that incorporates inspection, functional testing and extensive test automation. • All specifications are inspected for completeness and correctness • A comprehensive set of functional test cases is defined • JUnit-based test framework is used for automated regression testing Iterative & Incremental (6) Release Cycle based project management approach October 2011 Traditional Unified Process Approach Business capabilities will move through this life cycle and progress through the various release cycles • Process • Analysis Team’s defines use cases in Enterprise Architect and Requirements in JAMA Contour. • EA and JAMA are integrated to support Requirements traceability • Test cases are defined in Quality Center and linked to Requirements in Contour • Contour and Quality Center are integrated to support requirements traceability • Test cases are executed manually and by the automated test framework • Quality Center supports traceability of test cases to requirements and defects • Defect reporting • JIRA and Quality Center are integrated to provide defect visibility to Development Methodology Agile-Based Methodology – We’ve adopted an aggressive Agile-based methodology, with two week sprints, parallel work streams, and iterative releases of compact groupings of deliverables, enabling rapid execution and delivery of requirements, specifications, and software implementations of modularized business capabilities. Integrated Toolset – Quality Assurance is connected to all aspects of the system delivery lifecycle via a completely integrated set of tools. Test Management – HP Quality Center is used for test case management, requirement traceability and quality metrics reporting. Use Cases Requirements Test Execution Enterprise Architect JAMA Contour HP Quality Center Test Automation (Junit Framework, SOAP UI Pro) Tests BRIDGE BRIDGE Test Results nment Requirements Requirements Deployed QA Environment Deployed QA Environment Load Tests Tests JIRA Studio Defects BRIDGE Continuous Delivery Environment Defects Defects and Tasks • Automation • Automated Test Framework – QA has developed a JUnit/Java-based framework for testing the reference implementations of the web services. • Using Apache CXF to generate web service client • Custom builder objects which construct payloads using ISO 21090 datatypes. • JUnit framework provides assertion framework, reporting, and ANT build script execution • Java allows customization and flexibility for test care parameterization • JUnit is tightly integrated into Eclipse IDE • Continuous Delivery Environment– The project uses virtual hardware provided by Amazon EC2 for QA test environments. Builds are promoted from the Hudson Continuous Integration Server. • Execution and results reporting of automated test framework is provided via Hudson server • Quickly create deployed instances of the developed services • Allows QA to rapidly recreate test environments for different deployment scenarios Programmatic Test Data Generation HP QC Data Files (XLS, CSV, etc.) Service Under Test Network JAVA Testing Framework Other Test Generation Methods (MBT, etc.) Reports Continuous Delivery Environment Java Classes ANT or IDE Execution Web Service Client