AHM 2014: Conceptual Design, Developing a Data-Oriented Human-Centric Enterprise Architecture for EarthCube
1. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
CD: Developing a Data-Oriented Human-
Centric Enterprise Architecture for EarthCube
Yunfeng Jiang, Zhenlong Li, Kai Liu, Han Qin, George Taylor, Jizhe Xia,
Min Sun, Chen Xu, Chaowei Yang, Manzhu Yu
NSF Spatiotemporal Innovation Center
George Mason University
Carol Meyer and Erin Robinson,
Federation of Earth Science Information Partners
Sponsored by NSF EarthCube Program (ICER-1343759)
2. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
EarthCube Overview
Geoscience future focus (GEO 2009): Fostering a sustainable future
through a better understanding of our complex and changing planet.
CIF21 (2012): providing a comprehensive, integrated, sustainable,
and secure cyberinfrastructure (CI) to accelerate research and
education and new functional capabilities in computational and
data-intensive science and engineering, thereby transforming our
ability to effectively address and solve the many complex problems
facing science and society.
EarthCube Vision (Governance 2014): “… enable transformative
geoscience by fostering a community committed to providing
unprecedented discovery, access, and analysis of geoscience data…”
3. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
Project Objective
Our Conceptual Design project is to design an
EarthCube Enterprise Architecture (EA) to support
EarthCube for facilitating data communication and
human collaboration in pursuit of collaborative
geosciences.
The designed EA is to assist EarthCube (2012) as:
A geoscience research engine
A geoscience resource management platform
A geoscience computing service provider
A geoscience education platform
5. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
Progress so far
Extract EC user requirements
related to data, information
and computing resources
Summarize the extracted
requirements
Determine the capabilities (the
based layer in the framework)
of EearthCube EA
Determine the operational
activities for implementing the
capabilities
Draft the Volume I and the CV
and OV in Volume II
Workshops report
and Roadmaps
User requirement
matrix
Architectural
requirements
Capabilities
Operational
activities
Study EA design cases and
determine EarthCube EA
framework
Previous EA
design
EarthCube EA
framework
Sep 2013 Mar 2014Spiral 1 Analyzing user requirements SSpiral 2 Draft
7. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
EarthCubeEnterpriseArchitectureOverview
Overarchingaspectsofarchitecturethatrelateto
EarthCubeEnterpriseArchitecture
EarthCubeArchitectureDictionary
Articulatethedatarelationshipsandalignment
structuresintheEarthCubeArchitectureContent
TechnicalStandards
ArticulateapplicableOperationalandTechnical
standardsandguidance EarthCube Operational
Articulate EarthCube operational
scenarios, processes, activities and
requirements
EarthCube Services
Articulate the performers, activities,
services, and their exchanges providing for,
or supporting EarthCube functions
EarthCube Systems
Articulate the legacy systems or
independent systems, their composition,
interconnectivity, and context providing for
or supporting EarthCube functions
EarthCubeProject
ExemplifyhowtousetheEarthCubeEA
toGuideProjectDesign
Volume I Volume III Volume II Volume IV
EarthCube Capability
Articulate the capability requirement,
delivery timing, and deployed capability
EarthCube Enterprise Architeture
8. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
Design Report Structure
Define the Services Implementing EarthCube Capabilities
SvcV-1
Services Context
Description
SvcV-2
Services Resource Flow
Description
SvcV-4
Services Functionality
Description
SvcV-8
Services Evolution
Description
Assemble EarthCube Systems
SV-1
Systems Interface
Description
SV-2
Systems Resource Flow
Description
SV-4
Systems Functionality
Description
SV-8
Systems Evolution
Description
Define EarthCube End User Operations
OV-1
High-level Operational
Concept Graphic
OV-2
Operational Resource
Flow
OV-4
Organizational
Relationships Chart
Define EarthCube Capabilities
CV-1
Vision
CV-4
Capability Dependencies
CV-3
Capability Phasing
Define EarthCube Project
PV-1
Project Portfolio
Relationships
PV-2
Project Timelines
PV-3
Project to Capability
Mapping
StandardizeEarthCube
StdV-1
StandardsProfile
Introduce EarthCube Enterprise Architecture
AV-1
Overview and Summary
Information
AV-2
Integrated Dictionary
CV-6 Capability to
Operational Activities
Mapping
OV-5b
Operational activity
model
9. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
Capabilities (CV-1)
Education
Data
collection
Modeling
Provernance
Resource discovery,
access, analysis
Interoperability
Scientific
Workflow
Layer-based
architecture
Web service
Semantics &
Ontologies
Brokering
Computing
EC end users
Researchers
Educators
Students
Decision makers
Governance
Enabling Capabilities
End-user Capabilities
Enable
Feedback
Communication
Publishing
Resource Capabilities
Data/
Publications/
Information
Knowledge
Geoscience
facilities
IT resources
EC technology
provider
Computer experts
CI experts
CI developers
EC resource
providers
Data providers
IT infrastructure
providers
Geoscience
communities
Industry
Support
Feedback
Design/Develop
Use
Provide
Quality Control/Reliability
Access Control/Security
The capabilities of EarthCube
are derived by analyzing user
requirements.
10. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
End User Operations (OV-5b)
Determine
goals
Determine
search
strategy
End users
Present
discovery
options
Format query
and retrieve
results
Present results
and
assessment
informaiton
Assess result
items and
provide
suggestion
Evaluate
results
Results Ok?
Resource
provider
Perform query
and return
results
Create query
no yes
Ci
Tool providerSupporting roles
Search engine
Search portal
Distributed
resources
Tools/
Apps
Services
Data
Access
resource
Analyze
data
Example 1: resource discovery activity
CI
11. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
End User Operations (OV-5b)
Example 2: model development activity
12. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
End User Operations (OV-5b)
Example 3: governance activity
End users
RCN
Mediator
CI
Support use (by CI
components)
Use
Audit usage
Evaluate current
performance
Communicate
(workshops, etc.)
Scientific governance
Technical governance
Translate
requirments
Resource providers Communicate with
mediator, end users
and RCN
Decide shortfalls
Report shortfalls
Response with
implementable directives,
and allocate grant
Develop and provide
recourse based on
directives
Building blocks
NSF program manager
Operational manager
Chief ArchitectSecurity manager
Outreach manager Financial manager
Summarize resource
shortfalls (user
requirement)
Supporting roles
feedback
feedback
13. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
EarthCube EA Workshop at ESIP
Summer Meeting
• Date: July 7, 2014
• Location: Copper Mountain, Colorado
• Content: Domain experts to review and
comment on the design
– Review EA volumes developed
– Discuss EA in general for EarthCube
– Comment and advice on improving the design
• 10 experts will lead the discussion
• Other 10-20 experts will help review and comment
14. 7/25/2014 EarthCube All-Hands, June 24-26, 2014, Washington D.C.
Reference
– NSF 2011. Earth Cube Guidance for the Community
– EarthCube Brochure 2012. What is EarthCube?
– EarthCube Flyer 2013
– EarthCube Enterprise Governance Draft Charter 2014
– Zachman Framework
– Gartner Enterprise Architecture
– TOGAF Enterprise Architecture
– Federal Enterprise Architecture Framework
– DoD Architecture Framework (DoDAF)
– EarthCube End-User Workshops: Executive Summaries
2013
– EarthCube Working Group Roadmaps
Hinweis der Redaktion
These are summarized from volume 1, especially the section 1
EarthCube EA design principles:
Interoperability
Data-driven
Integrating existing resources rather than developing new ones
Community-based, i.e. human-centric
Must utilize standards and cutting-edge technologies, such as catalog services, ontology and cloud computing.
This should be overall structure of the design report
This page is sort of repeating the content in page 8, I just put it here for now.