National Cancer Institute   U.S. National Institutes of Health www.cancer.gov
caBIG® Knowledge Center: A part of the Enterprise Support Network

CCTS Architecture Governance Plan

From CTMS_WIKI

Jump to: navigation, search

Contents

Introduction

Background

The caBIG Clinical Trials Suite (CCTS) is an enterprise clinical trials system being designed primarily for use in trial sites. The suite is comprised of a collection of interoperable modules covering a broad range of key areas in cancer clinical trials management. These include patient registration via C3PR, patient scheduling via PSC, adverse events reporting via caAERS, lab analysis via LabViewer, and clinical data management via C3D. Integration between these applications is centered around five key scenarios: Study Creation, Register Subject, Load Labs in CDMS, Lab-driven AE Creation, and AE-Triggered Schedule Change. The implementation is based upon the caGrid infrastructure with caXchange as the Enterprise Service Bus for reliable message routing and GAARDS providing robust security.

Scope

This document describes the general approach to governance of the CCTS architecture.

This document is a work in progress used strictly for planning for the CCTS 2.0 release. Up until that release, it could be altered in any way.

Related Documentation

End User Technical CCTS Architecture Guide
Analysis Planning

Governance Approach

Governance of applications and architecture in the caBIG CTMS domain is handled by the CTMS Composite Architect Team (CAT). This team represents an implementation of RM-ODP, with members from the five viewpoints:

  • Enterprise
  • Information
  • Computational
  • Engineering
  • Technology

Proposals to changes in architecture must be presented to, reviewed by, and approved by the CAT. As of now, there is no formal process for bringing items to the CAT for review. However, for CCTS, we will be taking the following approach

  1. Determine which parts of the architecture need to be changed to meet new requirements (Project Manager, Architects)
  2. Define new architectural changes through formal documentation (Architects)
  3. Present architectural changes to the CCTS technical team for review (Architects, Technical Team)
  4. Modify the architectural changes per CCTS technical team feedback if needed (Architects)
  5. Present the architectural changes to the CAT for approval (Architects)
  6. Modify the architectural changed per CAT feedback if needed (Architects)
  7. Implement architectural changes (Project Manager, Technical Team)

Resources

Team Member Role
Patrick McConnell
  • CCTS Architect
  • CAT Engineering Viewpoint
Kalpesh Patel
  • CCTS Architect
  • CAT Computational Viewpoint
Edmond Mulaire CCTS Project Manager
KC Projects