Difference between revisions of "Planning"

From Federation of Earth Science Information Partners
(spam control)
 
(26 intermediate revisions by 5 users not shown)
Line 1: Line 1:
(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.  [[[User:HowardBurrows|Howard Burrows]] 18:09, 20 January 2006 (EST)]
+
::[[Burrows Exchange Notes 2006-01]]
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 [http://www.cio.gov/archive/bpeaguide.pdf|Practical Guide to FEA] and [http://www.whitehouse.gov/omb/egov/|Whitehouse e-Gov Site]).)
 
----
 
 
 
We will construct the ESIP exchange using the same collection of interrelated "reference models" as the US Government:
 
<br>
 
[[Image:FEA Reference Models.jpg|center|300px|]]
 
<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. 
 
 
 
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:
 
 
# Vision
 
# Requirements
 
# Analysis and Design
 
# Implementation
 
# Deployment
 
<br>
 
==Vision Document==
 
 
 
The full vision document should list:
 
 
 
:Focus: (for us improved quality, use, and appreciation for Earth science)
 
: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 in Federation Mission
 
: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
 

Latest revision as of 18:53, July 10, 2007