Difference between revisions of "EarthCube Design Approach"
From Earth Science Information Partners (ESIP)
Wclenhardt (talk | contribs) (Created page with "'''EarthCube Design Approaches''' ''Vision for EarthCube'' :A description of the envisioned scope of EarthCube and how will it transform geosciences research, including the f...") |
Wclenhardt (talk | contribs) |
||
Line 1: | Line 1: | ||
'''EarthCube Design Approaches''' | '''EarthCube Design Approaches''' | ||
− | ''Vision for EarthCube'' | + | [[''Vision for EarthCube'']] |
: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'']] |
: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'']] |
: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'']] |
: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'']] |
: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. |
Revision as of 14:21, October 7, 2011
EarthCube Design Approaches
- 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''
- 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''
- 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.
- 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''
- 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.