Difference between revisions of "Planning"

From Federation of Earth Science Information Partners
Line 3: Line 3:
 
----
 
----
  
We will construct the ESIP exchange using a collection of interrelated "reference models" as employed by the US Government in the Federal Enterprise Architecture:
+
[[Image:FEA Reference Models.jpg|center|]]
 +
<center>Figure 1. Federal Enterprise Architecture Reference Models</center>
 
<br>
 
<br>
[[Image:FEA Reference Models.jpg|center|300px|]]
+
We will construct the ESIP exchange using a collection of interrelated "reference models" as employed by the US Government in the Federal Enterprise Architecture.
<br>
+
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.   
+
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).
 
In addition, we will be performance-driven and will design-to-test (DTT).
 
----
 
----
 
----
 
----
Developing the ESIP Exchange will involve a number of interations through the following five steps:
+
Developing the ESIP Exchange will involve a number of iterations through the following five steps:
 
   
 
   
 
==Vision Document==
 
==Vision Document==
Line 18: Line 19:
 
The full vision document should list:
 
The full vision document should list:
  
:Focus: (for us improved quality, use, and appreciation for Earth science)
+
:Purpose
 +
::Improved quality, use, and appreciation of Earth science
 +
::Specify desired achievement toward each Goal in [[Media:Federation Strategic Plan]].
 
:Stakeholders (not just users)
 
:Stakeholders (not just users)
::*Primary*: Foundation, Federation, Partners
+
::Primary: Foundation, Federation, Partners
::*Secondary*: Earth scientists, modelers, decision tool providers, decision makers, education
+
::Secondary: Earth scientists, modelers, decision tool providers, decision makers, education
 
:Scope
 
:Scope
 
::Incremental stages to desired end
 
::Incremental stages to desired end
Line 31: Line 34:
 
:Glossary
 
:Glossary
 
:Functional Requirements
 
:Functional Requirements
::Specify and prioritize elements in Federation Mission
+
::Specify and prioritize elements from the various [[Federation Documents]]. 
 
:Nonfunctional Requirements
 
:Nonfunctional Requirements
 
::Performance, Security, Hardware
 
::Performance, Security, Hardware
Line 45: Line 48:
 
==Implementation==
 
==Implementation==
  
This will involve staged implementation conducted by recruiting already_existing components:
+
[[Image:FEA_Implementation_Diagram.jpg|center|]]
 +
<center>Figure 2. Federal Enterprise Architecture Implementation Diagram</center>
 +
<br>
 +
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.
  
[[Image:FEA_Implementation_Diagram.jpg|center|]]
 
  
 
==Deployment==
 
==Deployment==
  
All components are already deployed with varying 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.
+
;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.

Revision as of 18:28, 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:

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

Requirements

Glossary
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
Tests
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.

Implementation

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.


Deployment

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.