ESSRT In-Process ReviewSeptember 10, 2012

Agenda

 1. Work Completed Till Date

2. Scope of future activities and deliverables

2

1. Work Completed Till Date

• Subject Accrual Service Specifications Review

• 2TRANSCEND Integration  Analysis, Use Cases and Requirements

• 2TRANSCEND Integration Architecture

• 2TRANSCEND Security Architecture

• 2TRANSCEND Deployment Architecture

• Tolven to THE.Force Change Impact Analysis and updates to all analysis and architecture deliverables

3

1. Work Completed Till Date - contd.

• OSDI Governance Definition – Outline of the effort

• 2TRANSCEND Technical Coordination and Release Management

– Creation and maintenance of Release schedule– Creation and maintenance of Systems environments plan– Facilitate communications between Integration QA and App. QA teams– JIRA Infrastructure Setup– Creation of WBS Technical Tasks in JIRA– Weekly Risk Management activities– Guide development teams– Coordinate environments set up with the systems team– Devise interim delivery strategy for user acceptance testing

4

1. Work Completed Till Date - contd.

2TRANSCEND Analysis

– Analysis of THE.Force – iHub data exchange elements– Logical mapping of iHub data exchange data elements to CDA templates

(and CCD where possible)– CDA samples for the following four iHub data exchange types

• Subject Registration• Consent• Biospecimen• Adverse Event

NCI Enterprise Architecture Repository– Completed detailed assessment of NIH Enterprise Architecture Repository– Completed detailed assessment of the Essential Project (open source

product)– Presented overview, comparative assessment and demo of the two

products to NCI stakeholders– Created a draft implementation approach for the Essential Project

5

2. Scope of future work and activities

Governance Design– Maintain Service Specification Templates, Standards and Processes

Are we still using SAIF for new services?

– Redesign Service Development processes to align with the new Open Source Development approach Redesign Service Specification process based on JCP (Java Community Process) for

JSRs (Java Specification Request)

Enterprise Services Portfolio and Wiki Management– Review new service proposals to make recommendations to NCI management

– Maintain a program wiki space with all related content such as program overview, enterprise service portfolio (Enterprise Service Inventory Blueprint), links to key service artifacts and service implementation status Remove caCIS and other services that did not get implemented

– Publish Governance artifacts on the wiki

5

2. Scope of future work and activities – contd.

Governance Operations– Act as a custodian of NCI’s Enterprise Service Inventory Blueprint and

Roadmap– A comprehensive list of all enterprise services using standard taxonomy,

their definitions, dependencies, major milestones and status – Periodic updates to the roadmap throughout the program lifecycle– Review service scope documents and service specifications to provide

feedback to service development teams– Review Application Architecture documents to provide feedback, with a

focus on assessment regarding alignment with the NES Inventory Blueprint– Act as a custodian of NCI’s Enterprise Architecture Governance framework– Participate in various architecture governance forums such as Enterprise

ARB

Tools– Conduct assessment of open-source Enterprise Architecture Repository

tools, compare with NEAR, make a recommendation and implement the approved repository

6

2. Scope of future work and activities – contd.2TRANSCEND Technical Coordination and Release Management

– Maintenance of the Release schedule– Weekly Risk Management activities– Provide guidance to development teams– Coordinate environments set up with the UCSF team– Coordinate/facilitate resolution of integration testing issues

NCI Enterprise Architecture Repository– Continue to coordinate with NIH– Present NCI’s assessment of the Essential Project to NIH– Implement NCI Enterprise Architecture repository using Essential Project

Transition from caGrid to Interoperability Platform– Analysis of current Grid services – Compilation of current Grid Usage Statistics – Evaluation of Future Grid Technology Standards– Evaluation of Technology Products– Final Migration Approach for current Grid services

8

2. Scope of future work and activities – contd.

9

Dorian Authentication Grid Trust-Master Grid Trust-Slave Grid Grouper CDS Metadata Service GME Service Application Workflow Processor Service Federated Query Processor Index ServiceSecurity Semantics WorkflowApplication Service

/Service GroupsInfrastructure

a. Analysis of current Grid services and dependencies on Grid infrastructure such as Security, Semantics, Workflow and other services

b. Compile current usage statistics by using COTR, Project Manager, Project Sponsor as the first sources of information. Additionally, there will be Grid services developed without NCI funding for which an approach will need to be determined.

c. Research and evaluate future Grid technology standards for Security and Workflow. Use the Grid 2.0 roadmap for the requirements collected during that time period