Planning

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

(I am using this page to begin a discussion that I hope will become the development plan (and budget) for the ESIP Exchange. As of now, these are the comments of one person. HowardBurrows 18:09, 20 January 2006 (EST) The plan is based on a book by Jim Conallen entitled "Building Web Applications with UML Second Edition". The plan adopts elements of the Federal Enterprise Architecture (see Guide to FEA and e-Gov Site).)

We will construct the ESIP exchange using the same collection of interrelated "reference models" as the US Government:

The most important aspects of our development strategy are shown on the left and right of the diagram. Construction will be driven by the "business" of the Federation as described in our Federation Documents. The result will follow a component-based architecture.

Developing the ESIP Exchange will involve a number of interations through the following five steps:

Vision
Requirements
Analysis and Design
Implementation
Deployment

Vision Document

The full vision document should list:

   Focus: (for us improved Earth science quality, use, and appreciation)
   Stakeholders (not just users)
   Scope
   Components