Cochrane Collaboration - Register of Studies Consultation

893 views

Published on

UK Contributors Meeting, Edinburgh - March 2009

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
893
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Cochrane Collaboration - Register of Studies Consultation

  1. 1. Cochrane Collaboration Register of Studies Consultation Steve Greenaway & Myles Gorton
  2. 2. Register of Studies Consultation <ul><li>Objectives of the consultation </li></ul><ul><ul><li>Clarify & prioritise the business & technical requirements for a new Cochrane Register of Studies Database System </li></ul></ul><ul><ul><li>Produce a Request for Proposal Document </li></ul></ul><ul><ul><li>Produce a Scoring Guide for responses to the RFP from potential solution providers </li></ul></ul>
  3. 3. Register of Studies Consultation <ul><li>Our approach </li></ul><ul><ul><li>Document review of existing requirements (and RFP) in order to categorise into functional & non-functional </li></ul></ul><ul><ul><li>Production of the Requirements Catalogue </li></ul></ul><ul><ul><li>Production of High Level Architecture Diagrams </li></ul></ul><ul><ul><li>Prioritisation of all requirements via selected interview process using MoSCoW rules </li></ul></ul><ul><ul><li>Requirements priorities collated & aggregated </li></ul></ul><ul><li>Here today to present the findings </li></ul>
  4. 4. High Level Architecture Diagrams
  5. 5. As-Is High Level Architecture
  6. 6. To-Be High Level Architecture
  7. 7. Conceptual Solution for Register of Studies
  8. 8. Example Technology for Register of Studies
  9. 9. Example Architecture for Register of Studies
  10. 10. Requirements Prioritisation Results
  11. 11. Overall Prioritisation <ul><li>Using the MoSCoW rules </li></ul><ul><ul><li>Must Have – the requirement is essential for the solution to work </li></ul></ul><ul><ul><li>Should Have – the requirement is very important for the delivery of an efficient or cost effective solution </li></ul></ul><ul><ul><li>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 </li></ul></ul><ul><ul><li>Will Not Have – the requirement is of little or no benefit to the solution </li></ul></ul>
  12. 12. Web Application & Search Functionality <ul><li>Requirements related to the web application for the Cochrane Register of Studies, its functionality, look and feel, accessibility and search functionality </li></ul>
  13. 13. Data Migration & Import Validation <ul><li>Requirements related to the importing of data from the Specialised Registers, in particular relating to data migration and data validation processes </li></ul>
  14. 14. Database Design & Reports <ul><li>Requirements related to the structure of database tables, data types and data entity relationships. </li></ul><ul><li>Also requirements related to database reporting </li></ul>
  15. 15. Interfaces & Integration <ul><li>Requirements related to interoperability with existing systems within and external to the Cochrane Collaboration </li></ul>
  16. 16. Workflow & Process Automation <ul><li>Requirements related to human-to-system workflow and system-to-system process automation. </li></ul><ul><li>This area is related to interfaces and integration </li></ul>
  17. 17. Non-Functional <ul><li>Non-business function requirements such as: </li></ul><ul><ul><li>Accessibility </li></ul></ul><ul><ul><li>Availability </li></ul></ul><ul><ul><li>Scalability </li></ul></ul><ul><ul><li>Performance </li></ul></ul><ul><ul><li>Resilience </li></ul></ul><ul><ul><li>Security </li></ul></ul>
  18. 18. Next Steps
  19. 19. Request for Proposal <ul><li>Finalise Requirements Catalogue and High-Level Architecture diagrams for inclusion as Appendices in Request for Proposal </li></ul><ul><ul><li>Produce the RFP </li></ul></ul><ul><ul><li>Produce the Scoring Guide </li></ul></ul><ul><ul><li>Publish the RFP </li></ul></ul><ul><li>Obtain responses, score & rank suppliers </li></ul><ul><li>However… </li></ul>
  20. 20. Are There Other Options? <ul><li>Based upon our understanding of the requirements, our findings so far and our experience </li></ul><ul><ul><li>Many requirements = complex RFP = complex system </li></ul></ul><ul><ul><li>The solution has the feel of a “Rolls Royce” </li></ul></ul><ul><ul><li>Would a “Ford” or “Mini” suffice? </li></ul></ul><ul><ul><li>Is this the best use of the funding available? </li></ul></ul><ul><li>Back to basics – what is the problem that we are trying to fix? </li></ul>
  21. 21. What are the problems? <ul><li>Look of the data </li></ul><ul><li>Data duplication </li></ul><ul><li>Reference vs. Study based </li></ul><ul><li>Complete rebuild of CENTRAL with each publication </li></ul><ul><li>Searching </li></ul><ul><li>Workflow </li></ul><ul><li>Benefits of a centralised solution </li></ul>
  22. 22. Our Thoughts Cochrane Wiley/Blackwell Users SR’s Hand-search Etc. Register of Studies DB CENTRAL ProCite EndNote Etc. Publication Cochrane Library
  23. 23. Our Thoughts Cochrane Wiley/Blackwell Users SR’s Hand-search Etc. Register of Studies DB CENTRAL ProCite EndNote Etc. Publication Cochrane Library
  24. 24. Our Thoughts Cochrane Wiley/Blackwell Users Register of Studies DB CENTRAL ProCite EndNote Etc. Publication Cochrane Library SR
  25. 25. Our Thoughts Cochrane Wiley/Blackwell Users Register of Studies DB CENTRAL Web Front End Publication Cochrane Library SR COTS Commercial Off The Shelf Package
  26. 26. Any Questions?

×