Page 1© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Draft Interoperability Proposal Terry Davies SRNWP Meeting October 8-11, 2007.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

By: MSMZ. Objective After completing this chapter, you will be able to: Explain 2 contract review stage List the objective of each stage of the contract.
System Development Life Cycle (SDLC)
© Crown copyright Met Office SRNWP Interoperability Workshop, ECMWF January 2008 SRNWP Interoperability Alan Dickinson Met Office.
CSC271 Database Systems Lecture # 18. Summary: Previous Lecture  Transactions  Authorization  Authorization identifier, ownership, privileges  GRANT/REVOKE.
Oct-2012 – Aug-2014 Budget Status (*) Tempus IDEA– 3’rd Year Budget Planning Travel cost Mobility WP4 is still an on going activity Next mobility program.
1 Software Design Introduction  The chapter will address the following questions:  How do you factor a program into manageable program modules that can.
System Analysis (Part 1)
What is Software Design?  Introduction  Software design consists of two components, modular design and packaging.  Modular design is the decomposition.
Copyright Irwin/McGraw-Hill Software Design Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
(Project) SIGN OFF PROCESS June 21, 2010
System Design and Analysis
Project Workshops Assessment. 2 Deadlines and Deliverables No later than 16:00 on Tuesday, Week 21 in the Easter Term (second Tuesday) This is a hard.
Unit Five – Transforming Organizations
© Crown copyright Met Office SRNWP Interoperability Workshop, ECMWF, January 2008 SRNWP Interoperability Terry Davies Met Office.
Systems Development Life Cycle
Business Consulting Services Agenda Discussion: Management Reports Discussion: Project Reports Discussion: Engagement Proposal Upcoming Events Review Project.
Acquiring Information Systems and Applications
SYSTEM ANALYSIS AND DESIGN
Introduction to Systems Analysis and Design Trisha Cummings.
Expert Team on System Aspects and Interoperability Programme Glenn Greed, UKMO, Project Manager Interoperability Ulrich Schättler, DWD, Chairman of the.
Typical Software Documents with an emphasis on writing proposals.
Innovative Schools toolkit STRATEGIC WORKSHOP 5 Project implementation, tracking and management.
Interoperability between the European NWP modelling systems Ulrich Schättler, François Bouttier, Xiaohua Yang, Radmila Brozkova, Alan Radford A Report.
1 IT Project – Project Lifecycle, methodologies, tools, resources and other issues.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Software Engineering Management Lecture 1 The Software Process.
“Initiate the reorganisation and strengthening of the SRNWP Programme” EMN/C27/Doc12 C27 took place the 4-6 April 2006 in Toulouse 13th SRNWP Meeting 12th.
Page 1© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik SRNWP – Revised Verification Proposal Clive Wilson Presented by Terry Davies at SRNWP Meeting.
Page 1© Crown copyright 2005 SRNWP – Revised Verification Proposal Clive Wilson, COSMO Annual Meeting September 18-21, 2007.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
SRNWP meeting, Dubrovnik OMSZ PROPOSAL October, OMSZ proposal for becoming responsible member of the C-SRNWP programme ANDRÁS HORÁNYI
I Power Higher Computing Software Development The Software Development Process.
Computers Are Your Future Tenth Edition Chapter 13: Systems Analysis & Design Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall1.
IT 21103/ System Analysis & Design. Chapter 02 Project Initiation.
9th COSMO General Meeting September 2007 Athens (Greece) Programme Short-Range NWP Report of the Programme Manager.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Innovative Schools toolkit Strategic Workshop 5 Project implementation, tracking and management.
Business Consulting Services Engagement Proposal & Letter of Agreement Project Management Timelines/GANNT Chart.
Systems Development Life Cycle
COSMO – 09/2007 STC Report and Presentation by Cosmo Partners DWD, MCH, USAM / ARPA SIM, HNMS, IMGW, NMA, HMC.
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
Project roles and responsibilities
Project 1 (CGNB 413) Briefing
Sprint Plans and Burndown Charts David Millard | davidmillard.org.
DEVELOPMENT OF A WHITE PAPER ON CORRECTIONAL SERVICES Ministry of Correctional Services.
Doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide Common Editorial Comment Resolution Process Date: Authors:
Introduction to System Analysis and Design MADE BY: SIR NASEEM AHMED KHAN DOW VOCATIONAL & TECHNICAL TRAINING CENTRE.
C-SRNWP (SHORT RANGE NUMERICAL WEATHER PREDICTION NETWORK) AND THE FORECASTING CAPABILITY AREA OF EUMETNET Responsible member: Hungarian Meteorological.
GEO Implementation Mechanisms Giovanni Rum, GEO Secretariat GEO Work Programme Symposium Geneva, 2-4 May 2016.
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Capacity Building in: GEO Strategic Plan 2016 – 2025 and Work Programme 2016 Andiswa Mlisa GEO Secretariat Workshop on Capacity Building and Developing.
Systems Development Life Cycle
Methodologies and Algorithms
Software Engineering Management
An example of how to develop a dynamic business model
Introduction to System Analysis and Design
Systems Analysis and Design
CLINICAL INFORMATION SYSTEM
Introduction to Systems Analysis and Design
Chapter 13: Systems Analysis and Design
Systems Analysis and Design
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Towards WISE as a distributed system
Systems Development Life Cycle
UOE timeliness standards
UNIT No- III- Leverging Information System ( Investing strategy )
(Project) SIGN OFF PROCESS MONTH DAY, YEAR
What is a System? A system is a collection of interrelated components that work together to perform a specific task.
Presentation transcript:

Page 1© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Draft Interoperability Proposal Terry Davies SRNWP Meeting October 8-11, 2007

Page 2© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Flow chart

Page 3© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Interoperability deliverables D1-D3 D1: A report documenting the standard output format and including a list of parameters for which the standard output format is applied. D2: A report documenting the standard observational data format. D3: Requirements Specification for the adaptor software: This document includes the identification of the methods that can be used for implementing the adaptors, and for maintenance of the software in connection with the consortia. It must be agreed by all groups involved.

Page 4© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Interoperability deliverables D4-D6 D4: Four adaptors that transform the output from every LAM to the standard output format. This includes the software as well as the documentation D5: Enhancements to existing software tools that enable all LAMs to process data from the four available GMs. This includes the software as well as the documentation. D6: Enhancements to existing software tools that enable all LAMs to process data from the other LAMs. This includes the software as well as the documentation.

Page 5© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Not submitted because: D1, D2 and D3 require consultation between the consortia to reach agreement on formats and specifications. D4, D5 and D6 are best carried out by each of the consortia working to the agreed specifications. In this case there is a better chance of achieving success if the consortia work together through the WG and for each consortium to find its own staff resources to do the actual work.

Page 6© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Draft proposal for UK as RM  Aim to deliver D1 to D4 within 2 years of commencement.  As RM the UK will provide a Programme Manager at between 0.25 and 0,5 of a FTE – figure to be confirmed once further work has been completed into scope.  The PM will coordinate and manage the technical work and produce reports required by Council.  Each NWP consortium will carry out its own work for D4 under the coordination of the PM. (options for funding are given later).

Page 7© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Draft proposal for UK as RM Deliverables D5 and D6 would effectively allow any NWP model to use any other to provide lateral boundary conditions. The UK has some doubts over the desirability and achievability of these deliverables in a relatively short time scale. They are not as straightforward as D4 and it is felt that more work needs to be done to resolve the scope of the work. In particular, C-SRNWP members can provide valuable input into considering how sophisticated such a system need be. For instance, would a simple reversal of the systems to convert model output to a standard format suffice? There is also a question over the responsibility for maintenance of conversion systems as models change. And should the owners of global modelling systems be responsible for maintaining those models in a way that allows users of their lateral boundary conditions to carry on unaffected by change?

Page 8© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Draft proposal for UK as RM  Many of these issues will require work to be done at individual nation level, not just by consortia.  The UK feels that firm proposals for this developments required to deliver D5 and D6 should be deferred until there has been further examination of the size and complexity of the task.

Page 9© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Funding options  Option 1 To provide the same level of funding as previously envisaged (€100K per annum). €30K to go to RM (€20K for 0.25 FTE plus €10K for travelling expenses) and the rest to be shared equally between NWP consortia (Unified Model, Hirlam, COSMO, Aladdin and ECMWF).  Option 2 To reduce funding to €30K for the RM and ask the consortia to fund the technical work themselves.

Page 10© Crown copyright 2007SRNWP 8-11 October 2007, Dubrovnik Questions