data and information architecture: not just for enterprise architects! brand l. niemann, senior...
TRANSCRIPT
Data and Information Architecture: Not Just for Enterprise Architects!
Brand L. Niemann, Senior Enterprise Architect, U.S. EPA, and Co-Chair, CIO Council's Semantic Interoperability Community of Practice (SICoP) and SOA CoPJune 14, 2007
The Evolution of EA in the Federal Government
SOAService
Systems
Web Services
Shared Services
The “MediciEffect”
StakeholdersInput and Outreach
Co
mm
un
itie
s o
f P
ract
ice
Management of Change
Defining EA in the Federal Government
Source: FEA Practice Guidance, “Value to the Mission”, December 2006, Federal Enterprise Architecture Program, Management Office, OMB, 45 pp.
Communities of Practice
Enterprise Architecture
Semantic Interoperability
Service-Oriented Architecture
Data and Information Architecture
Service Systems, and an
Information Sharing Environment
Semantic Interoperability
Semantics = Meaning = Relationships- Humans (and therefore our machines) only ever understand
anything in so far as it is related to other things
ID
Semantic Interoperability
Semantics = Meaning = Relationships- Humans (and therefore our machines) only ever understand
anything in so far as it is related to other things
ID
VANY
MD
Semantic Interoperability
Semantics = Meaning = Relationships- Humans (and therefore our machines) only ever understand
anything in so far as it is related to other things
ID
SUPEREGO
EGO
ANALYSIS
Semantic Interoperability
Semantics = Meaning = Relationships- Humans (and therefore our machines) only ever understand
anything in so far as it is related to other things
ID
LICENSE
CARD
BADGE
Service-Oriented Architecture SOA CoP
People Business
InformationTechnology
Information
SOA Architecture & Infrastructure SOA CoP Knowledgebase
SOA CoP Demo Phases 1-4SOA Tutorials
Goal 1*
Goal 2Goal 3
Goal 4
The “MediciEffect”
StakeholdersInput and Outreach
* CIO Council Strategic Plan Goals – see slide 12.
Data and Information Architecture
Source: Expanding E-Government, Improved Service Delivery for the American People Using Information Technology, December 2005, pp. 2-3.http://www.whitehouse.gov/omb/budintegration/expanding_egov_2005.pdf
DRM 1.0 SICoP
Ontologies
All Three
DRM 3.0 unify
Semantic Wikis: The Role of Techno-Social Collaboration in Building DRM 3.0 and Web 3.0 for Managing Context Across Multiple Documents and Organizations, SICOP Special Conference, February 6, 2007, Mills Davis, Project10X.
Service Systems
Service Systems The Challenge: CIO Council Silos
People Business
InformationTechnology
Information
Architecture & Infrastructure CommitteeBest Practices Committee
Executive CommitteeIT Workforce Committee
Source: Pages 21-22, Federal Chief Information Officer Council Strategic Plan: FY 2007-2009, 28 pp. http://www.cio.gov/documents/CIOCouncilStrategicPlan2007-2009.pdf
Goal 1(see Source)
Goal 2Goal 3
Goal 4
The “MediciEffect”
StakeholdersInput and Outreach
Information Sharing Environment Open Community SOA CoP Infrastructure
Name Organization Role
Model-Driven Architecture
Modeldriven.org SOA CoP Demo Phase 2 and 3
Semantic Wiki Knoodl.com Vocabulary Harmonization & Data Modeling
GigLite DoD Component Development & Testing
Open Source SOA Infrastructure
IONA SOA CoP Demo 3
Google: SOA CoP Demo 4 and Join Us!
Lessons Learned
Drive toward a common language (semantic interoperability) in your SOA.
Leverage SOA to deal with the semantics of Data and Information Architecture across the distributed enterprise.
Focus on information sharing with service systems. Create an Information Sharing Environment to generate
service innovation (the Medici Effect).
Notes on Conference Presentations
Keynote Session – Richard Buchanan, What Does the Future Hold?
Keynote Session – Anne Lapkin, The Architect’s New Imperative: Integration EA, BPM, and Service Management
Track Sessions – Brian Burke, The Role of EA in Shaping BPM and SOA
Keynote Session – Chris Anderson, The Long Tail and the Economics of Abundance
Track Session – David Norton, Closing the Gap Between EA and Model-Driven Development
Track Session – Anne Lapkin, Bringing Technology Trends to the Board Room
Keynote Session – Richard Buchanan, What Does the Future Hold?
His Views My Views
Human System Service System
Rules in Software Rules in Data
Architect the Lines, Not the Boxes
Architect the Lines of Business with Vendors as the Boxes
Game / Outcomes Results (working SOA demo)
Admit Weakness Yes, and work at the COO level
Keynote Session – Anne Lapkin, The Architect’s New Imperative: Integration EA, BPM, and Service Management
Recent Gartner Analysts’ Retreat to get a taxonomy. In my experience you really need an ontology by asking everyone
the following:- What is your concept of say “enterprise architecture”?
- How would you define it?
- Please provide a specific example of how your definition explains the concept.
We have done the Federal Enterprise Architecture Reference Model Ontology to provide:- A common language and relationships between concepts.
- A line-of-sight between goals and outcomes.
- An executable artifact for ontology-driven applications. Applying Integration EA, BPM, and Service Management to slide 12 – see
next slide.
Applying Integration EA, BPM, and Service Management to the CIO Council
People Business
InformationTechnology
Information
Architecture & Infrastructure CommitteeBest Practices Committee
Executive CommitteeIT Workforce Committee
Goal 1
Goal 2Goal 3
Goal 4
The “MediciEffect”
StakeholdersInput and Outreach
Service Management Integration EABPM
Track Sessions – Brian Burke, The Role of EA in Shaping BPM and SOA
His Concepts Semantic Web Concepts
Generic IF&Ps are the key to loosening the coupling
Universal Resource Identifiers in RDF and OWL
Making the implicit explicit “A little semantics goes a long way” (Jim Hendler)
Don’t code the rules – put them in the data/metadata
RDF and OWL are the data and the metadata!
Manage change for agility Database and XML Schemas are brittle – use RDF Schema
Keynote Session – Chris Anderson, The Long Tail and the Economics of Abundance
“The smartest guys don’t work for you” (Scott McNealy) and the most interesting ideas come from unexpected places:- In a community of practice, the smartest guys can all
work together and you never know where the greatest contribution will come from next.
Make essential things free, open, and everywhere and decentralize what you can and only centralize what you must:- IONA Open Source SOA Infrastructure and Federal
SOA Jump Start Kit for the SOA CoP!
Track Session – David Norton, Closing the Gap Between EA and Model-Driven Development
His Views My Views
Close the gap between them MDA is executable EA (see SOA CoP Demo Phases 1-2)
OMG is different from the Microsoft ontology DSL’s
OMG now has the Ontology Definition Metamodel (ODM)
Value in modeling EA? Federal Enterprise Architecture Reference Model Ontologies
EA and software development are separate activities
EA, Segment Architecture, and Solutions Architecture should be integrated (slide 3)
Track Session – Anne Lapkin, Bringing Technology Trends to the Board Room
I agree with her conclusions and recommendations!
Prepare a business plan and “investor - elevator pitch” on how to get from the current state to the future state of increased agility and competitiveness in sensible increments.
This requires courage, persistence, and being proactive and reminds me of:- ‘Stop drawing architecture diagrams and talking to only
other EA’s and get out of your offices and start talking to lots of people inside and outside your organization to find out what their IT needs are and how you can help them.’ (OMB Chief Architect, Dick Burke)