Enterprise Architecture: Not Just for Enterprise Architects by HC120704001645

VIEWS: 8 PAGES: 26

									Data and Information Architecture:
Not Just for Enterprise Architects!
          Gartner Enterprise Architecture Conference
                13-15 June 2007, Nashville, TN
         Gaylord Opryland Resort & Convention Center
    Brand 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


                                                               1
               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.
                                                         2
                            2. The Evolution of EA
                          in the Federal Government
                                                 Stakeholders
                                                                       Input and Outreach



                                                              Service
                             SOA
Communities of Practice




                                                              Systems


                             (3-5)                              (6)
                                                The “Medici
                                                  Effect”


                             Web                              Shared
                            Services                          Services


                             (1): see slide 2                    (2)

                                                                                    3
                                       Management of Change
    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.

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

                                                              5
               3. Defining EA in the
               Federal Government




Source: FEA Practice Guidance, “Value to the Mission”, December 2006,
                                                                          6
Federal Enterprise Architecture Program, Management Office, OMB, 45 pp.
              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!
                                                                              7
                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.ppt
for complete slides.                                                        8
     (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



                                                              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
                                        VA
    NY
                         ID


                                     MD
                                                              10
     (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
                                     SUPEREGO
    EGO
                         ID


                                 ANALYSIS
                                                              11
     (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
                                      LICENSE
   CARD
                         ID


                                   BADGE
                                                              12
 (3) Service-Oriented Architecture
                                    SOA CoP                    Stakeholders
                                                               Input and Outreach



              People       Goal 1*                     Business     Goal 4


         SOA Tutorials                           SOA CoP Demo Phases 1-4
                                   The “Medici
                                     Effect”


           Information
                                                      Information
           Technology           Goal 3                              Goal 2

SOA Architecture & Infrastructure
                                                 SOA CoP Knowledgebase
                                                                             13
* See next slide for details.
  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.

                                                            14
     (3) Service-Oriented Architecture
  • 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 15
 (3) Service-Oriented Architecture
• 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.

                                                                          16
    (4) Data and Information Architecture
  DRM 1.0                                                       SICoP
                                              All Three




DRM 3.0 unify                                             Ontologies




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
                                                                        17
 (4) Data and Information Architecture
     DRM 2.0 Implementation Metamodel
                                   • 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 Implementation   18
Through Iteration and Testing Report, October 15, 2005.
       (4) Data and Information Architecture

     Tool                          Program                         Purpose
     Web Search                    Federal                         Locate
                                   Sitemaps                        Most searches start
                                   Google: Federal                 with Google, Yahoo,
                                   Sitemaps                        and MSN

     Wikis                         COLAB                           Collaborate
                                   Google: COLAB Wiki              Need to Share*

     Semantic Wikis Knowledgebases Integrate
                                   Google: DRM 3.0 and             Responsibility to
                                   Web 3.0                         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). 19
   (4) Data and Information Architecture
• 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      20
                             (5) Service Systems
           The Challenge: Service Industry Growth


           enable        People         develop           enable       Business        transform


                 Consumer services
                 Non-market services                              Business services




                                       operate &
           design       Products                           create    Information         utilize
                                        maintain


                   Industrial services                           Information services
                                                                                                    21
Source: Dr. Spohrer, Towards a Science of Service Systems, CIOC Best Practices Committee, March 19, 2007.
                        (5) Service Systems
          The Challenge: CIO Council Silos
                                      Stakeholders
                                                                             Input and Outreach



                  People         Goal 1                          Business           Goal 4
                                 (recall slide 14)
       IT Workforce Committee                              Executive Committee
                                        The “Medici
                                          Effect”


               Information
                                                                Information
               Technology          Goal 3                                           Goal 2

Architecture & Infrastructure Committee
                                                        Best Practices Committee
  Source: Pages 21-22, Federal Chief Information Officer Council Strategic Plan: FY 2007-    22
  2009, 28 pp. http://www.cio.gov/documents/CIOCouncilStrategicPlan2007-2009.pdf
               (5) Service Systems




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,
                                                                                23
SICOP Special Conference, February 6, 2007, Mills Davis, Project10X.
  (6) Information Sharing Environment
               Open Community SOA CoP Infrastructure

Name                  Organization          Role
Model-Driven          Modeldriven.org       SOA CoP Demo
Architecture                                Phase 2 and 3
Semantic Wiki         Knoodl.com            Vocabulary
                                            Harmonization &
                                            Data Modeling
GigLite               DoD                   Component
                                            Development &
                                            Testing
Open Source SOA IONA                        SOA CoP Demo 3
Infrastructure
                                                              24
(6) Information Sharing Environment




       Google: SOA CoP Demo 4 and Join Us!
                                             25
                      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.


                                                                          26

								
To top