Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Science Modernisation Strategy v1 0

1.627 visualizaciones

Publicado el

Modernisation Strategy for Science at RBG Kew. The presentation is part of a "toolkit" delivered to help Kew to rationalise, consolidate and integrate disparate & legacy Science Applications and Data.

Publicado en: Tecnología
  • There are over 16,000 woodworking plans that comes with step-by-step instructions and detailed photos, Click here to take a look ▲▲▲ http://t.cn/A6hKwqcb
       Responder 
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí
  • Want to preview some of our plans? You can get 50 Woodworking Plans and a 440-Page "The Art of Woodworking" Book... Absolutely FREE ■■■ http://tinyurl.com/y3hc8gpw
       Responder 
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí
  • Want to preview some of our plans? You can get 50 Woodworking Plans and a 440-Page "The Art of Woodworking" Book... Absolutely FREE ◆◆◆ http://ishbv.com/tedsplans/pdf
       Responder 
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí
  • The #1 Woodworking Resource With Over 16,000 Plans, Download 50 FREE Plans... ●●● http://tinyurl.com/yy9yh8fu
       Responder 
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí
  • Sé el primero en recomendar esto

Science Modernisation Strategy v1 0

  1. 1. Science Modernisation High-Level Strategy Salim Sheikh Version 1.0 30th March 2010
  2. 2. What is a Blueprint? The objective of the Blueprint is to: • implement strategic business drivers (from IT & DM strategy) • define core business processes and information requirements. • specify standard systems including data, applications and platforms. The products that form the Blueprint include: • Business (Process) Architecture • Information Architecture • Application Architecture Enterprise Architecture Layers • Technical Architecture
  3. 3. SHS High Level Approach Select Science Apps to Blueprint PROJECT STAGES Discovery Phase 1 Phase 2 “AS IS” Blueprint “TO BE” Blueprint Analysis Analysis Prioritised Prioritisation Technology Review Prioritisation Cost Options Workstream Completed & Planning Business Case Roadmap Workstream Project Plans Incremental delivery Governance Solution Architecture Implementation (per workstream) of “TO BE” blueprint Controls (per workstream) Maintain Blueprint & Implement Roadmap
  4. 4. Discovery Stage Details End-to-End Steps Discovery Phase 1 Review User Workshops Consolidate Outputs Analysis Science Applications Consolidate Consolidate Consolidate EA “AS IS” Blueprint Logical Architecture Logical Data Model Use Cases Recommendations Phase 2 Business Process Group Workshops Consolidate Outputs Analysis Modelling Finalise Logical Finalise Conceptual EA “TO BE” Blueprint Architecture Data Model Recommendations
  5. 5. Discovery Stage Details Phase 1 Analysis Phase 1 Phase 2 Discovery “AS IS” Blueprint “TO BE” Blueprint Analysis Analysis Review User Workshops Consolidate Outputs Science Applications
  6. 6. New Product Phase 1 Analysis Original Product Activities, Steps & Products ACTIVITIES STEPS PRODUCTS User Survey Results Review Business Requirements Validate Use User Workshops Drivers (from IT & Capture (incl. Cases & Use Cases DM strategy) Use Cases) Requirements (per application) Requirements Matrix Application Audit 1-2-1 Interviews Complete EA reviews (per application) Science review (EA + Science App & Data completed and Validation Apps Team) Audit templates templates Logical Architecture (per application) Review Science Applications Data Audit Reverse- Install & Configure EA reviews & (per application) engineer Science review Data Analysis consolidates Science App and Validation Tools outputs Conceptual Data Model Databases (covers all applications) Review Establish key Functional, Non- EA reviews & Business requirements Science review Consolidate Outputs Application functional consolidates (per application) and Validation Use Cases requirements outputs (per application)
  7. 7. Discovery Stage Details “AS IS” Blueprint Phase 1 Phase 2 Discovery “AS IS” Blueprint “TO BE” Blueprint Analysis Analysis Consolidate Consolidate Consolidate EA Logical Architecture Logical Data Model Use Cases Recommendations
  8. 8. New Product “AS IS” Blueprint Original Product Activities, Steps & Products ACTIVITIES STEPS PRODUCTS Review Create “AS IS” Logical Create Architecture Logical Science Logical Update Consolidate logical (covers all applications) Architectures Review & Architecture Reqm’ts Logical Architecture application from previous Validation (enterprise- Matrix groupings activities wide) Requirements Matrix “AS IS” Conceptual Review Data Model Logical Data Create Science Create Update Consolidate Models from logical data Review & Conceptual Reqm’ts (covers all applications) Logical Data Model previous groupings Validation Data Model Matrix activities Requirements Matrix Consolidate Requirements Matrix Consolidate Update business Group “AS IS” Requirements Use Cases requirements (per Use Cases Matrix application) Grouped “AS IS” Use Cases EA Science Review Logical Groupings System Scores System Scores Recommendations and Validation
  9. 9. Discovery Stage Details Phase 2 Analysis Phase 1 Phase 2 Discovery “AS IS” Blueprint “TO BE” Blueprint Analysis Analysis Business Process Group Workshops Consolidate Outputs Modelling
  10. 10. New Product Phase 2 Analysis Original Product Activities, Steps & Products ACTIVITIES STEPS • validate group use cases PRODUCTS • establish business processes • validate reqm’ts Grouped “TO BE” Use Cases Review Grouped Validate & Update Conduct Group Requirements Matrix Group Workshops “AS IS” Prioritise Use Requirements Workshops Use Cases Cases Matrix Business Processes (per grouping) Update Business Review Business Processes Map Business EA reviews & Update Business Process Processes (from Processes to consolidates Requirements Modelling Group Data Models outputs Matrix Workshops) Business Architecture
  11. 11. Discovery Stage Details “TO BE” Blueprint Phase 1 Phase 2 Discovery “AS IS” Blueprint “TO BE” Blueprint Analysis Analysis Finalise Logical Finalise Conceptual EA Architecture Data Model Recommendations
  12. 12. New Product “TO BE” Blueprint Original Product Activities, Steps & Products ACTIVITIES STEPS PRODUCTS Create “TO BE” “TO BE” Logical Review “AS IS” Logical Update Architecture Finalise Logical Architecture Requirements (covers all applications) Logical Architecture Architecture (enterprise- Matrix wide) Requirements Matrix “TO BE” Conceptual Data Model Finalise Review “AS IS” Create “TO BE” Update Conceptual Data Conceptual Requirements (covers all applications) Conceptual Data Model Model Data Model Matrix Requirements Matrix Conceptual Design EA Create Conceptual Create Logical Science Review Recommendations Design Design and Validation Logical Design
  13. 13. Prioritisation & Planning Technology Review Prioritised Prioritisation Technology Review Prioritisation Cost Options Workstream Completed & Planning Business Case Roadmap Analyse External Analyse Internal EA Tools Tools Recommendations
  14. 14. New Product Technology Review Original Product Activities, Steps & Products ACTIVITIES STEPS PRODUCTS Review External Business Analyse External Applications (e.g. Benefits Options Appraisal Tools TROPICOS) Realisation Review Internal & Business Analyse Internal Procured ORACLE Tools Review Benefits Tools Applications (e.g. Realisation ORACLE) EA Produce Procurement & Technology Technology Science Review Recommendations Sign-Off Recommendations Recommendations
  15. 15. Prioritisation & Planning Prioritisation Prioritised Prioritisation Technology Review Prioritisation Cost Options Workstream Completed & Planning Business Case Roadmap Programme Prioritisation Dependency Review Roadmap
  16. 16. New Product Prioritisation Original Product Activities, Steps & Products ACTIVITIES STEPS PRODUCTS Review Review Programme Programme Programme Business Dependency Review Dependencies Priorities Dependencies Report Review outputs Produce Prioritised Workstream Prioritisation from Programme Review System Review Logical Prioritisation Roadmap Roadmap Dependency Scores Groups Roadmap Review
  17. 17. Prioritisation & Planning Cost Options Prioritised Prioritisation Technology Review Prioritisation Cost Options Workstream Completed & Planning Business Case Roadmap Present Options Business Benefits Sign-Off Appraisal Realisation
  18. 18. New Product Cost Options Original Product Activities, Steps & Products ACTIVITIES STEPS PRODUCTS Review Review Present Options Review Options Prioritised Programme Appraisal Appraisal Workstream Cost Options Dependencies Roadmap Business Benefits Review Benefits Review Benefits Benefits Realisation Realisation for Science for Programme Report Review & Approval Sign-Off Workstream Implementation
  19. 19. Worked Examples BREAK OUT WALK THROUGH WORKED EXAMPLES
  20. 20. Creating Logical Groupings (App & Data Audit Product) Business H B R usiness Functions functions derived from use cases E-Clearance, HSPD -12, and EODS Recruitment One Stop E-Training E-Payroll EHRI Existing Business functions are logically grouped. This Science is how Science systems will be consolidated to Systems form e.g. Collection Systems
  21. 21. System Scoring An in-depth system scoring will be performed across multiple domains: strategic, business, data, technology, and security alignment. The template, scoring criteria, and scoring justifications are provided in a separate spreadsheet. Summary of Systems Scoring 5.0 Consolidate / Retire Target Technology Fit 2.5 Consolidate / Retire Re-engineer 0.0 0.0 2.5 5.0 Business Fit
  22. 22. Cost Options • A Prioritised Workstream Roadmap will help direct all cost option discussions/considerations • Options will be based on the following criteria: • System scoring (incl. COTS integration and bespoke development) • Estimated total cost to migrate, consolidate, retire, and finally decommission a system. • Cost required to do data migration (to Oracle DB) • In addition, Programme dependencies will also need to be considered
  23. 23. Questions Dr Salim Sheikh Enterprise Architect Email: salims@acm.org

×