1 data and information architecture: not just for enterprise architects! gartner enterprise...

1

Data and Information Architecture: Not Just for Enterprise Architects!

Gartner Enterprise Architecture Conference13-15 June 2007, Nashville, TN

Gaylord Opryland Resort & Convention CenterBrand L. Niemann, Senior Enterprise Architect, U.S. EPA,

and Co-Chair, CIO Council's Semantic Interoperability Community of Practice (SICoP) and SOA CoP

June 14, 2007

2

1. Introduction

• In my 25+ year government career I have been asked by senior government leadership to:– (1) Chair the CIO Council’s Web Services Working

Group.– (2) Served on the Solution Architects Working Group

and the Data Reference Model (DRM) 1.0 Team.– (3) Co-Chair the CIO Council’s Semantic

Interoperability Community of Practice (SICoP).– (4) Lead the DRM 2.0 Implementation Through

Testing and Iteration Team.– (5) Co-Chair the SOA CoP.– (6) Serve as the Secretariat of the CIO Council’s Best

Practices Committee.

3

2. 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

(1): see slide 2 (2)

(3-5) (6)

4

Getting The “Medici Effect”

• “The Medicis were a banking family in Florence who funded creators from a wide range of disciplines. Thanks to this family and a few others like it, sculptors, scientists, poets, philosophers, financiers, painters, and architects converged on the city of Florence. There they found each other, learned from one another, and broke down barriers and cultures. Together they forged a new world based on new ideas – what became known as the Renaissance.”– Frans Johansson, The Medici Effect, Harvard

Business School Press, 2006, pages 2-3.

5

Getting The “Medici Effect”

• The Medici Effect:– “When you step into an intersection of fields,

disciplines, or cultures, you can combine existing concepts into a large number of extraordinary ideas.”

– “We have met teams and individuals who have searched for, and found, intersections between disciplines, cultures, concepts, and domains. Once there, they have the opportunity to innovate as never before, creating the Medici Effect.”

• Frans Johansson, The Medici Effect, Harvard Business School Press, 2006, page 186.

6

3. 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.

7

3. Defining EA in the Federal Government

• Make the relationships between:– 1. Enterprise Architecture

• A management practice for transitioning from the current state to the desired future state.

– 2. Segment Architecture, and• Detailed results-oriented architecture (baseline and target) and

transition strategy for common, shared, or enterprise services.– 3. Solution Architecture

• An architecture for an individual IT system that is part of a segment.

• real using SOA in white papers, workshops/conferences, and pilots:– See Collaborative Expedition Workshop #57, Tuesday, January

23, 2007 at NSF , Opening Up Networked Improvement Activities Around Service Oriented Architecture in 2007.

– 3rd SOA for E-Government Conference, May 1-2, 2007.– Note: I ended up back where I began with Solution Architecture!

8

4. Six Critical Areas

• (1) Enterprise Architecture (previous)

• (2) Semantic Interoperability

• (3) Service-Oriented Architecture

• (4) Data and Information Architecture

• (5) Service Systems, and an

• (6) Information Sharing Environment

See http://colab.cim3.net/file/work/SICoP/2007-06-14/SICoPGartner06142007.pptfor complete slides.

http://colab.cim3.net/file/work/SICoP/2007-06-14/SICoPGartner06142007.ppt

9

(2) 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

10




ID

VANY

MD

11




ID

SUPEREGO

EGO

ANALYSIS

12




ID

LICENSE

CARD

BADGE

13

(3) Service-Oriented Architecture

People Business

InformationTechnology

Information

SOA Architecture & InfrastructureSOA CoP Knowledgebase

SOA CoP Demo Phases 1-4SOA Tutorials

Goal 1*

Goal 2Goal 3

Goal 4



* See next slide for details.

SOA CoP

14

Federal Chief Information Officer Council Strategic Plan (FY 2007-2009) Goals

• Goal 1. A cadre of highly capable IT professionals with the mission critical competencies needed to meet agency goals.

• Goal 2. Information securely, rapidly, and reliably delivered to our stakeholders.

• Goal 3. Interoperable IT solutions, identified and used efficiently and effectively across the Federal Government.

• Goal 4. An integrated, accessible Federal infrastructure enabling interoperability across Federal, state, tribal, and local governments, as well as partners in the commercial and academic sectors.

15


• Improve Data Quality with Semantic SOA:– Data Modeling and OWL: Two Ways to

Structure Data, David Hay, Essential Strategies, Inc.:

• Objectives of a Data Model:– Capture the semantics of an organization.– Communicate these to the business without requiring

technical skills.– Provide an architecture to use as the basis for database

design and system design.» Now: Provides the basis for designing Service

Oriented Architectures.

http://www.semantic-conference.com/2007/sessions/m5.html http://www.semantic-conference.com/2007/handouts/2-UpBW/Hay_David_2_2UpBW.pdf

http://www.semantic-conference.com/2007/sessions/m5.html

16


• Improve Data Quality with Semantic SOA:– Data Modeling and OWL: Two Ways to Structure

Data, David Hay, Essential Strategies, Inc. (continued):

• Synopsis:– Both data modeling and ontology languages represent the

structure of business data (ontologies).– Data modeling represent data being collected, and filters

according to the rules.– Ontology languages represent data being used, with ability to

have computer make inferences.

• Comment from Lucian Russell (SICoP White Paper 3):– So ontology can improve data quality in legacy systems! David

Hay agreed.

17

(4) 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

18


• Definitions:– Metamodel: Precise

definitions of constructs and rules needed for abstraction, generalization, and semantic models.

– Model: Relationships between the data and its metadata - W3C.

– Metadata: Data about the data for: Discovery, Integration, and Execution.

– Data: Structured e.g. Table, Semi-Structured e.g. Email, and Unstructured e.g. Paragraph.

Source: Professor Andreas Tolk, 2005, and DRM 2.0 ImplementationThrough Iteration and Testing Report, October 15, 2005.

DRM 2.0 Implementation Metamodel

19


Tool Program Purpose

Web Search Federal SitemapsGoogle: Federal Sitemaps

LocateMost searches start with Google, Yahoo, and MSN

Wikis COLABGoogle: COLAB Wiki

CollaborateNeed to Share*

Semantic Wikis KnowledgebasesGoogle: DRM 3.0 and Web 3.0

IntegrateResponsibility to Provide*

* Mike McConnell, Director of National Intelligence: Move the intelligence community beyond the "need to share" philosophy toward a "responsibility to provide" model (March 6, 2007).

20


• SICoP and SOA CoP Special Recognitions:– Outstanding Contributions to the SICoP Special

Conference 2, April 25th (recall slide 12); and– Best Presentation at the 3rd SOA for E-Government

Conference, May 1-2nd:• “Semantic Technology is the first fundamental change in

Information Management since the RDBMS was developed in the early 1980’s”:

– Michael Lang, Revelytix, Co-Founder and Director, and Co-Chair, SICoP Vocabulary Management WG. Enterprise Data Modeling / SOA in a Semantic Wiki Knoodl.com.

– Demonstration at the June 18-19, 2007, W3C Workshop on eGovernment and the Web, National Academy of Sciences.

http://colab.cim3.net/file/work/SOACoP/2007_05_0102/MLang05022007.ppt

http://colab.cim3.net/file/work/SOACoP/2007_05_0102/MLang05022007.ppt

21

The Challenge: Service Industry Growth

People Business

Products Information

enable develop enable transform

designoperate &maintain

create utilize

Industrial services Information services

Business servicesConsumer services

Non-market services

Source: Dr. Spohrer, Towards a Science of Service Systems, CIOC Best Practices Committee, March 19, 2007.

(5) Service Systems

22

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(recall slide 14)

Goal 2Goal 3

Goal 4

(5) Service Systems



http://www.cio.gov/documents/CIOCouncilStrategicPlan2007-2009.pdf

23

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.

(5) Service Systems

24

(6) Information Sharing Environment

Name Organization RoleModel-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

Open Community SOA CoP Infrastructure

25

(6) Information Sharing Environment

Google: SOA CoP Demo 4 and Join Us!

26

5. Synopsis

• Enterprise Architecture now is really about getting to a common language (Semantic Interoperability) about SOA (Service-Oriented Architecture).

• SOA itself is evolving to deal with the semantics of Data and Information Architecture across the distributed enterprise.

• Service Systems are about people working with their information using information technology for a business purpose in an Information Sharing Environment.

• An Information Sharing Environment produces service innovation (the Medici Effect).– So this is not for just Enterprise Architects, but about involving

everybody! Recall slides 3, 13, and 22.