May 2011 Milestone Materials Atmosphere-ocean design document Updated target interoperability table Adoption status table NUOPC Layer software prototype.

Slides:



Advertisements
Similar presentations
Prescriptive Process models
Advertisements

Presentation by Prabhjot Singh
ECMDA workshop Thales ATM experience in using MDE ECMDA Workshop From code centric to model centric software engineering Bilbao 11 July 2006.
CS487 Software Engineering Omar Aldawud
Software Process Model
MapleLeaf, LLC SDLC Methodology. MapleLeaf, LLC, has established standard phases and processes in regards to project management methodologies for planning.
Chapter 4 Quality Assurance in Context
Software Process Models
Component Patterns – Architecture and Applications with EJB copyright © 2001, MATHEMA AG Component Patterns Architecture and Applications with EJB JavaForum.
Design Creative Process of transferring the problem into a solution
Rational Unified Process Workflows. The Rational Unified Process.
1 SOFTWARE LIFE-CYCLES Beyond the Waterfall. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
CMU’s TTO3 Tasks Analyze annotation manuals and annotated samples from all TTO3 teams –Status: Formal UML models have been constructed and merged together.
Object-Oriented Analysis and Design
Reuse Activities Selecting Design Patterns and Components
Implementation of Project Governance at the Center Level
Information Technology Division Executive Office for Administration and Finance Shared Application Infrastructure (SAI) Program Overview.
Session 3: NUOPC Interoperability Layer Instructors: Rocky Dunlap and Fei Liu NOAA Cooperative Institute for Research in Environmental Sciences University.
Update on INSPIRE: INSPIRE maintenance and implementation and INSPIRE related EEA activities on biodiversity CDDA/European protected areas technical meeting.
Chapter 6 Software Implementation Process Group
Testing. Definition From the dictionary- the means by which the presence, quality, or genuineness of anything is determined; a means of trial. For software.
THE ROLE OF PROCESS IN SOFTWARE QUALITY By K.KARTHIKEYAN.
RUP Fundamentals - Instructor Notes
Chapter 2 The process Process, Methods, and Tools
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Integrating Security Design Into The Software Development Process For E-Commerce Systems By: M.T. Chan, L.F. Kwok (City University of Hong Kong)
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 07. Review Architectural Representation – Using UML – Using ADL.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Software Testing. What is Testing? The process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation.
1 NUOPC National Unified Operational Prediction Capability 1 Review Committee for Operational Processing Centers National Unified Operational Prediction.
February 2012 Milestone Materials Implicit coupling design document NUOPC Layer software prototype bundled with ESMF Updated NUOPC Layer reference manual.
CESM/ESMF Progress Report Mariana Vertenstein NCAR Earth System Laboratory CESM Software Engineering Group (CSEG) NCAR is sponsored by the National Science.
Design Patterns CSCI 5801: Software Engineering. Design Patterns.
SE-02 COMPONENTS – WHY? Object-oriented source-level re-use of code requires same source code language. Object-oriented source-level re-use may require.
1/23 Prescriptive Process Models. 2/23 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive.
Architectural Patterns Support Lecture. Software Architecture l Architecture is OVERLOADED System architecture Application architecture l Architecture.
Earth System Modeling Framework Status Cecelia DeLuca NOAA Cooperative Institute for Research in Environmental Sciences University of Colorado, Boulder.
Chapter 7 Interactive Design and Prototyping Human Performance Engineering Robert W. Bailey, Ph.D. Third Edition.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Prototyping By: Michael McBee & Shere Stewart. Prototyping What is Prototyping? It is an iterative process involving analysts and users where a model.
JRA Execution Plan 13 January JRA1 Execution Plan Frédéric Hemmer EGEE Middleware Manager EGEE is proposed as a project funded by the European.
Project Management Culture: Implementing Change Martyn Upton, Project Office.
Developed by Reneta Barneva, SUNY Fredonia The Process.
The principles of an object oriented software development process Week 04 1.
Software Model Process
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
ASUG SAP Adoption Influence Council The focus is on how to increase awareness, adoption and implementation of SAP enhancements that are delivered as part.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
State of ESMF: The NUOPC Layer Gerhard Theurich NRL/SAIC ESMF Executive Board / Interagency Working Group Meeting June 12, 2014.
Enterprise Architecture Reference Framework Generalities
Nesting Milestone Materials Nesting design document Updated NUOPC Layer software prototype bundled with ESMF Updated NUOPC Layer reference manual Nesting.
The NOAA Environmental Modeling System at NCEP Mark Iredell and the NEMS group NOAA/NWS/NCEP Environmental Modeling Center June 12, 2014.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
IPDA Architecture Project International Planetary Data Alliance IPDA Architecture Project Report.
#atpconf What’s in Your Program Toolbox?. #atpconf Presenters ■ Jessi Mielke  Certification Program Manager  Esri ■ Lisa O’Leary, Ph.D.  Senior Psychometrician.
National Aeronautics and Space Administration 1 CCSDS Information Architecture Working Group Daniel J. Crichton NASA/JPL 24 March 2005.
POOL Based CMS Framework Bill Tanenbaum US-CMS/Fermilab 04/June/2003.
Software Verification and Validation
Building a Distributed Earth System Model Community
V-Shaped SDLC Model Lecture-6.
System Requirements BTS530.
INFS 6225 – Object-Oriented Systems Analysis & Design
Software Engineering Lecture 18.
Software Development Process
Software Engineering Lecture #45
Software Processes Process should be
Software Engineering Lecture 17.
A brief introduction to NEMS
Presentation transcript:

May 2011 Milestone Materials Atmosphere-ocean design document Updated target interoperability table Adoption status table NUOPC Layer software prototype and reference manual Prototype atmosphere-ocean coupled applications:  NOGAPS-HYCOM – functional prototype  COAMPS(-NCOM) – in progress  NEMS-GFS – in progress

Functions of prototype Establish an architecture in which major components are siblings. The initial design supports explicit coupling and concurrent or sequential execution of components. Allow inheritance from generic component templates. Couple components with pre-fabricated connectors. Standardize the number and function of phases of initialize, creating a standard setup pattern. Constrain the data that may be sent between components with standardized field data structures and a field dictionary. Implement a compliance checker to provide feedback during component development. Use compatibility checking to determine if required import fields for a component were supplied. Other run-time reporting alerts users to any issues with compliance.

Interoperability impact Component templates and generic connectors make it easier for modelers to create compliant systems since they can reuse existing code and patterns Constraining and clearly defining initialize phases ensures that components fit into standard drivers. Constraining Field data structures and metadata ensures that the data communicated between components is understood The ESMF layer ensures that components plug together into an executable application. The NUOPC layer reports when the components don't play together during execution. Detailed reporting provides the model developer with the insight necessary to debug and rectify code quickly.

More information See: For additional information on this milestone, including links to NUOPC Layer code, documentation, and supporting design documents.