Enterprise Architecture Working
Group Session: Suggestions
Senior Enterprise Architect
EPA Enterprise Architecture Team
April 10, 2008
• Slide 9: Solution Technology Requirements
Indicators Crosswalk Template Snapshot:
– Land Quality Management Segment has captured the
information flow and interface profile table. Each
solution architect could use the information flow in the
table to create this diagram as a supporting artifact.
• My Comment: Even better, the interface could
be to an executable application that linked
information architecture to data architecture
according to Slide 14 (see next slide).
• Slide 14: Business Transformation
– Expected Impacts on Technology are (1) Data
Optimization, (2) Data Management &
Communications, and (3) Metadata
Management and External Access and Data
My Comment: This again could be realized in a
real application that provides actual “line of
sight” and Emergency Management data and
information (see next slides for pilot example).
Data Architecture Pilot
• Enterprise (subject matter expertise and peer
review): EPA Report on the Environment
• Segment (topics and subtropics): Five
Categories and 89 Indicators.
• Solutions (data tables and metadata):
Standardized and DRM 2.0 Compliant.
My Comment: What we have already done is now
called a Web 2.0/3.0 Enterprise Mashup.
Web 2.0/3.0 Enterprise Mashups
• Enterprise Mashups are application hybrids combining
content and functions from more than one existing
source to create powerful Web applications, integrated
Web experiences and expanded customer value
networks. Mashups are the fastest growing enterprise
ecosystem on the Web by far. Mashups are social, role-
based, network-centric, complex, distributed and
essential to all knowledge-based networks, models and
businesses. Source: Open Enterprise 2.0 Mashup
Summit - Expanding Customer Value Networks
My Comment: So we would like all the Segment
Architectures to be “Solutioned” (implemented) in such a
way that EPA and its stakeholders can mash them up at
will to solve needs that we haven’t yet thought existed.
• See EPA Data Architecture Pilot:
– Enterprise Data Architecture and Implementation:
Federated, Faceted, Semantic Search of Both EPA
Metadata and Data with Governance, March 26,
2008, Updated April 4, 2008.
• See Best Practices:
– Enterprise Mashup: A Practical Guide to Federal
Service Oriented Architecture.
• Collaborate to Pilot This for Emergency
Management (with Joan Karrie) for the next EA
Working Group Session.