Difference between revisions of "EarthCube Design Approach"

From Federation of Earth Science Information Partners
 
Line 1: Line 1:
 
'''EarthCube Design Approaches'''
 
'''EarthCube Design Approaches'''
 
 
''[[Vision for EarthCube]]''  
+
''[[Vision for EarthCube]] (ESIP Leadership)''  
  
 
:A description of the envisioned scope of EarthCube and how will it transform geosciences research, including the functionality EarthCube can provide to the whole Geosciences community.
 
:A description of the envisioned scope of EarthCube and how will it transform geosciences research, including the functionality EarthCube can provide to the whole Geosciences community.
  
''[[Community-Based Governance model]]''
+
''[[Community-Based Governance model]] (ESIP Leadership)''
 
:The community structures necessary to acquire current and future user input/requirements, to respond to changing data and science needs, to adapt and adopt new technologies, to coordinate components and facilities, to foster partnerships and community participation.
 
:The community structures necessary to acquire current and future user input/requirements, to respond to changing data and science needs, to adapt and adopt new technologies, to coordinate components and facilities, to foster partnerships and community participation.
  
''[[Conceptual CI Architecture]]''  
+
''[[Conceptual CI Architecture]] (Rahul, Sara, Chris Lynnes??)''  
 
:The architecture necessary to provide the services of EarthCube, to integrate advanced information technologies that facilitate access to distributed resources such as computational tools and services, instruments, data, and people.
 
:The architecture necessary to provide the services of EarthCube, to integrate advanced information technologies that facilitate access to distributed resources such as computational tools and services, instruments, data, and people.
  
''[[Design Process]]''
+
''[[Design Process]] (Bruce, ??)''
 
:User requirement-driven design methodology, identification of design team members, qualifications of development team, time-line for design demonstration and scale-up, design tools and practices that create robust, sustainable, well-documented and open source infrastructure
 
:User requirement-driven design methodology, identification of design team members, qualifications of development team, time-line for design demonstration and scale-up, design tools and practices that create robust, sustainable, well-documented and open source infrastructure
  
''[[Operations and Sustainability Model]]''
+
''[[Operations and Sustainability Model]] (ESIP professional staff)''
 
:Operational aspects of a community-wide enterprise that address such activities as centralized functions, coordination of services, user services, including training, and identification of what it will take to sustain a viable infrastructure over a long periods of time and who will carry out these functions.
 
:Operational aspects of a community-wide enterprise that address such activities as centralized functions, coordination of services, user services, including training, and identification of what it will take to sustain a viable infrastructure over a long periods of time and who will carry out these functions.

Latest revision as of 09:37, October 10, 2011

EarthCube Design Approaches

Vision for EarthCube (ESIP Leadership)

A description of the envisioned scope of EarthCube and how will it transform geosciences research, including the functionality EarthCube can provide to the whole Geosciences community.

Community-Based Governance model (ESIP Leadership)

The community structures necessary to acquire current and future user input/requirements, to respond to changing data and science needs, to adapt and adopt new technologies, to coordinate components and facilities, to foster partnerships and community participation.

Conceptual CI Architecture (Rahul, Sara, Chris Lynnes??)

The architecture necessary to provide the services of EarthCube, to integrate advanced information technologies that facilitate access to distributed resources such as computational tools and services, instruments, data, and people.

Design Process (Bruce, ??)

User requirement-driven design methodology, identification of design team members, qualifications of development team, time-line for design demonstration and scale-up, design tools and practices that create robust, sustainable, well-documented and open source infrastructure

Operations and Sustainability Model (ESIP professional staff)

Operational aspects of a community-wide enterprise that address such activities as centralized functions, coordination of services, user services, including training, and identification of what it will take to sustain a viable infrastructure over a long periods of time and who will carry out these functions.