Difference between revisions of "Planning"

From Federation of Earth Science Information Partners
Line 21: Line 21:
::Improved quality, use, and appreciation of Earth science
::Improved quality, use, and appreciation of Earth science
::Specify desired achievement toward each Goal in [[Media:Federation Strategic Plan]].
::Specify desired progress toward each Goal in [[Media:StrategicPlan FINAL.doc|Strategic Plan 2004-2007]].
:Stakeholders (not just users)
:Stakeholders (not just users)
::Primary: Foundation, Federation, Partners
::Primary: Foundation, Federation, Partners

Revision as of 18:31, January 20, 2006

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

FEA Reference Models.jpg
Figure 1. Federal Enterprise Architecture Reference Models

We will construct the ESIP exchange using a collection of interrelated "reference models" as employed by the US Government in the Federal Enterprise Architecture.

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

In addition, we will be performance-driven and will design-to-test (DTT).

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

Vision Document

The full vision document should list:

Improved quality, use, and appreciation of Earth science
Specify desired progress toward each Goal in Strategic Plan 2004-2007.
Stakeholders (not just users)
Primary: Foundation, Federation, Partners
Secondary: Earth scientists, modelers, decision tool providers, decision makers, education
Incremental stages to desired end
esipfed.org, GCMD, ECHO, GOS2, ESG, CLASS, NOMAD...


Functional Requirements
Specify and prioritize elements from the various Federation Documents.
Nonfunctional Requirements
Performance, Security, Hardware
Use Cases
Key scenarios raised to family of similar cases
Each requirement will be defined in terms of a test that would show success

Analysis and Design

This step depends on the evolving requirements and will involve managers and the implementors: Atlantic BT, NGDC, ESRI, etc. Budget contingencies be part of the design documentation.


FEA Implementation Diagram.jpg
Figure 2. Federal Enterprise Architecture Implementation Diagram

This will involve staged implementation according to a sequencing plan recruiting already-existing components. We expect implementation to involve multiple components, each in their own separate implementation state.


Roll out and promotion
All components are currently deployed with a variety of levels of use. Advertising and marketing the integrated ESIP Exchange will take place for targeted communities based on tests at each stage of integration involving sample audiences. We are essentially “Building our ship at sea”.
Impact evaluation
At each stage we will set benchmarks and targets and evaluate performance.
Continual Redesign
As the system evolves we expect both evolutionary and revolutionary changes involving coordination and support from initially independent components. We hope to move from aggregates to become and integrated “system” across components and knowledge environments.