Cochrane Collaboration Register of Studies Consultation Steve Greenaway & Myles Gorton

Register of Studies Consultation Objectives of the consultation Clarify & prioritise the business & technical requirements for a new Cochrane Register of Studies Database System Produce a Request for Proposal Document Produce a Scoring Guide for responses to the RFP from potential solution providers

Objectives of the consultation

Clarify & prioritise the business & technical requirements for a new Cochrane Register of Studies Database System

Produce a Request for Proposal Document

Produce a Scoring Guide for responses to the RFP from potential solution providers

Register of Studies Consultation Our approach Document review of existing requirements (and RFP) in order to categorise into functional & non-functional Production of the Requirements Catalogue Production of High Level Architecture Diagrams Prioritisation of all requirements via selected interview process using MoSCoW rules Requirements priorities collated & aggregated Here today to present the findings

Our approach

Document review of existing requirements (and RFP) in order to categorise into functional & non-functional

Production of the Requirements Catalogue

Production of High Level Architecture Diagrams

Prioritisation of all requirements via selected interview process using MoSCoW rules

Requirements priorities collated & aggregated

Here today to present the findings

High Level Architecture Diagrams

As-Is High Level Architecture

To-Be High Level Architecture

Conceptual Solution for Register of Studies

Example Technology for Register of Studies

Example Architecture for Register of Studies

Requirements Prioritisation Results

Overall Prioritisation Using the MoSCoW rules Must Have – the requirement is essential for the solution to work Should Have – the requirement is very important for the delivery of an efficient or cost effective solution Could Have – the requirement is a “nice to have” and may enhance the solution, but it is not essential for functionality or efficiency. The requirement could be delivered later as an enhancement of the solution Will Not Have – the requirement is of little or no benefit to the solution

Using the MoSCoW rules

Must Have – the requirement is essential for the solution to work

Should Have – the requirement is very important for the delivery of an efficient or cost effective solution

Could Have – the requirement is a “nice to have” and may enhance the solution, but it is not essential for functionality or efficiency. The requirement could be delivered later as an enhancement of the solution

Will Not Have – the requirement is of little or no benefit to the solution

Web Application & Search Functionality Requirements related to the web application for the Cochrane Register of Studies, its functionality, look and feel, accessibility and search functionality

Requirements related to the web application for the Cochrane Register of Studies, its functionality, look and feel, accessibility and search functionality

Data Migration & Import Validation Requirements related to the importing of data from the Specialised Registers, in particular relating to data migration and data validation processes

Requirements related to the importing of data from the Specialised Registers, in particular relating to data migration and data validation processes

Database Design & Reports Requirements related to the structure of database tables, data types and data entity relationships. Also requirements related to database reporting

Requirements related to the structure of database tables, data types and data entity relationships.

Also requirements related to database reporting

Interfaces & Integration Requirements related to interoperability with existing systems within and external to the Cochrane Collaboration

Requirements related to interoperability with existing systems within and external to the Cochrane Collaboration

Workflow & Process Automation Requirements related to human-to-system workflow and system-to-system process automation. This area is related to interfaces and integration

Requirements related to human-to-system workflow and system-to-system process automation.

This area is related to interfaces and integration

Non-Functional Non-business function requirements such as: Accessibility Availability Scalability Performance Resilience Security

Non-business function requirements such as:

Accessibility

Availability

Scalability

Performance

Resilience

Security

Next Steps

Request for Proposal Finalise Requirements Catalogue and High-Level Architecture diagrams for inclusion as Appendices in Request for Proposal Produce the RFP Produce the Scoring Guide Publish the RFP Obtain responses, score & rank suppliers However…

Finalise Requirements Catalogue and High-Level Architecture diagrams for inclusion as Appendices in Request for Proposal

Produce the RFP

Produce the Scoring Guide

Publish the RFP

Obtain responses, score & rank suppliers

However…

Are There Other Options? Based upon our understanding of the requirements, our findings so far and our experience Many requirements = complex RFP = complex system The solution has the feel of a “Rolls Royce” Would a “Ford” or “Mini” suffice? Is this the best use of the funding available? Back to basics – what is the problem that we are trying to fix?

Based upon our understanding of the requirements, our findings so far and our experience

Many requirements = complex RFP = complex system

The solution has the feel of a “Rolls Royce”

Would a “Ford” or “Mini” suffice?

Is this the best use of the funding available?

Back to basics – what is the problem that we are trying to fix?

What are the problems? Look of the data Data duplication Reference vs. Study based Complete rebuild of CENTRAL with each publication Searching Workflow Benefits of a centralised solution

Look of the data

Data duplication

Reference vs. Study based

Complete rebuild of CENTRAL with each publication

Searching

Workflow

Benefits of a centralised solution

Our Thoughts Cochrane Wiley/Blackwell Users SR’s Hand-search Etc. Register of Studies DB CENTRAL ProCite EndNote Etc. Publication Cochrane Library

Our Thoughts Cochrane Wiley/Blackwell Users SR’s Hand-search Etc. Register of Studies DB CENTRAL ProCite EndNote Etc. Publication Cochrane Library

Our Thoughts Cochrane Wiley/Blackwell Users Register of Studies DB CENTRAL ProCite EndNote Etc. Publication Cochrane Library SR

Our Thoughts Cochrane Wiley/Blackwell Users Register of Studies DB CENTRAL Web Front End Publication Cochrane Library SR COTS Commercial Off The Shelf Package

Any Questions?