MILESTONE H: Design Policy for Interoperability and Agreed-Upon Community Delivery
- A High-Performance Software Framework and Interoperable Applications for the Rapid Advancement of Earth System Science. Part I: Core Earth System Modeling Framework Development (Cooperative Agreement NCC5-623, hereafter referred to as Part I )
- A High-Performance Software Framework and Interoperable Applications for the Rapid Advancement of Earth System Science. Part II: Modeling Applications for the Earth System Modeling Framework (Cooperative Agreement NCC5-625, hereafter referred to as Part II )
- A High-Performance Software Framework and Interoperable Applications for the Rapid Advancement of Earth System Science. Part III: Data Assimilation Applications for the Earth System Modeling Framework (GSFC Task Agreement GSFC-CT-3, hereafter referred to as Part III)
- V. Balaji (NOAA/GFDL) vb@gfdl.gov
- Cecelia DeLuca (NSF/NCAR) cdeluca@ucar.edu
- Chris Hill (MIT) cnh@plume.mit.edu
| EARTH SYSTEM MODELING FRAMEWORK
/ CAN 00-OES-01
Contents
H1. Deliver ESMF Architecture
Document, Implementation Report including prototype code, and draft Build
Plan via the Web. The ESMF Architecture Document will include a definition
of compliance and a listing and description of object classes and functionality
classes. Decide on implementation language(s) and language interoperability
strategy based on findings in the Implementation Report.
H2. Select Advisory Board and external customers. The ESMF Advisory Board is listed under the Contacts link on the navigation bar of the ESMF website. A list of external customers is available here. H3. External peer review of Architecture Document. Updated General Requirements Document. The Architecture Document has being circulated to the ESMF Peer Review Board and the comments received have been incorporated into the document. An updated General Requirements Document is available via the Development link on the ESMF website navigation bar.
Titles of the agreements and agreement numbers. Design, implementation, and
community delivery policies agreed upon.
Contact information for the lead software engineer and team members. This information is covered in Section 2.1, "Communication", of the Draft Developers Guide submitted for milestone A. The full project (Part I, Part II and Part III) has appointed a technical lead team that oversees all three parts. The team has three members A written description of the application being developed. Section 5, "Scope", of the ESMF Requirements document submitted as part of the fulfillment of joint milestone A describes the scope of the entire project, Parts I, II and III. It provides a written description of the software being developed under the project and of the pre-existing applications that are being deployed as part of the project. The deployment work that will be carried out under Parts II and III constitutes facets of the "suite of applications demonstrating how the ESMF software is used in practice" that is described in the ESMF Requirements document Section 5. Software development effort associated with the "interface specification for coupling components" and the "reference implementation" is also described in the ESMF Requirements document Section 5. The implementation work for these latter two items pertains primarily to the Part I proposal, but the design and detailed architecture component of the development cuts across all three parts of the project (Part I, Part II and Part III). Section 5 also outlines a range of demonstration experiments that will be deployed under the Part II and III agreements. The publicly available Part I, Part II and Part III milestone table document accessible via the "Milestones and Archives" link on the ESMF website navigation bar shows the final set of milestones in joint form. It lists the exact application configurations that will be deployed on the framework, under Part II and Part III, known as the Part II and III JMC codes. As indicated in Section 5 these applications are pre-existing and are being "deployed" on the framework, as opposed to being developed. The milestone agreements should in no way be construed to imply that these pre-existing applications are being developed as part of the agreements. The development activity being carried out under Part I, Part II and Part III is limited to design, implementation and validation of the ESMF framework and ancillary development required to support deployment. The text of the joint milestone document shows the exact configurations (of the pre-existing applications) that will be used to demonstrate deployment (see the table of JMC codes and the milestone I and J items) and interoperability. More detailed descriptions of each of the pre-existing JMC applications is publicly available at the "Applications" link on the side bar of the ESMF project web site. Identification of the Software Engineering Plan under which this work is taking place. A software engineering plan including an ESMF Developer's Guide was provided in Milestone A. Documentation as identified in the appropriate milestone. Build documentation for the code that accompanies the Implementation Report is forthcoming.
|
