Information—Integration—Intelligence Solutions Semantic Web for Enterprise Architecture with...

Information—Integration—Intelligence Solutions

Semantic Web for Enterprise Architecture

with TopBraid Suite™

Supporting the Complete Semantic Application Lifecycle

© Copyright 2007-2008 TopQuadrant Inc. Slide 2

Formed in 2001 First Semantic Web Consulting

Firm in U.S.

Products & Services TopBraid Suite – a solution

platform for: Data Integration Rapid Application development

TopBraid Composer – a premier ontology development tool

Focused solutions for select areas (including EA)

Professional Services, Training and Consulting

Company Overview

Offices:

Mountain View, CA

Alexandria, VA

Co-founder/CTO Prior to TQ: Founder member of IBM’s Object

Technology Practice, IBM’s Java and Emerging Technology Practice and IBM’s Portal Practice, founder and Managing Director of IDE, Object Technologist since 1982Ralph Hodgson

Executive Management Team

Co-founder/CEO Prior to TQ: Principal at IBM Global Services,

IT Manager and Senior Developer at a number of Financial Services Companies including Transamerica and Citigroup.Irene Polikoff

Co-founder/COO Prior to TQ: CTO at a software start up providing

web platform for the insurance industry, Senior Consultant at IBM’s Object Technology Practice, Research Faculty and CS Lecturer at Carnegie-Mellon UniversityRobert Coyne, PhD

Product and Technology Executive TeamChief Scientist Joined in 2002 Prior to TQ: Co-founder and VP of Customer

Applications, Synquiry Technologies, a semantic technology startup, Researcher at Swiss Telecom

Author: Semantic Web for the Working Ontologist (2008)Dean Allemang, PhD

Holger Knublauch, PhD

VP of Product Development Joined in 2005 Prior to TQ: Researcher at Stanford

University where he created the leading open source ontology development tool – Protégé OWL

Jeremy Carroll, PhD

Chief Product Architect Joined in 2008 Prior to TQ: Lead Architect of HP’s

Jena Platform Team


TQ team has authored 4 books covering Semantic Technology

TQ team has authored 4 books covering Semantic Technology

Thought Leadership

TopBraid SuiteSupporting the Complete Semantic Application Lifecycle

Application Deployment Platform

Collaborative Information Management


(Ontology Modeling Tool

Customer Story: General Services Administration (GSA)

As part of the e-Gov initiative, the US government has made a commitment to a Federal Enterprise Architecture

Components include the Federal Enterprise Architecture Reference Model (FEARM), a controlled vocabulary for business, technology services and performance measures of enterprise systems

The Federal Transition Framework provides a single information source for all aspects of cross-agency initiatives in the US government



All aspects of the Federal Enterprise Architecture must interoperate . . .

. . . But they are managed by different agencies and information councils!



Specific GSA Use Case – Bricks Management

GSA Tactical Direction (Next 2 Years)

GSA Strategic Dir. (2 to 5 yrs)

Retired (Product / Date)

GSA Approved Standard (Current)

GSA Approved Waivers and Additional Supporting Information

In Containment (Product / Date /Projected Retirement)

A “Brick” is a technology policy roadmap for the next five years.

e.g.,

•“What web browser is approved today?”

•“What desktop operating system do we plan to use next year?”

•“What network OS has been retired?”



GSA Bricks – basic use cases

•Allow small group of users to maintain Bricks

•Allow many users (architects, project managers, developers) to view/review Bricks

•Cross-reference Bricks by POC, responsible party, author

•Cross-reference technology by vendor, Brick



Challenges for Bricks Management

Challenge “As-is” Solution “To-be” solution

Distributed authorship

Master PowerPoint file, centrally managed, changes are merged

Data-backed web pages

Rich cross-referenced data

Search the PowerPoint for text, use manually built cross-reference index

Semantic Web linked data

Reference to external sources (FEA)

Names of FEA entities pasted into PowerPoint, often with errors

Semantic links to URIs for FEA entities

Input to the EA committee from the broader IT community

Verbal and unsystematic as part of meetings

Linked information about standards, vendors, systems and their use of technologies is available for analysis and decisions



Extended Bricks-based Use Cases

•Policy Consistency checking•Same technology Is both “approved” and “retired” •Retirement date of current technology leaves gap before new technology is ready

•Retirement date after published life span of technology•Lifecycle Management

•Re-assign Bricks to a new Responsible Party (e.g., when current one leaves)

•Analyze the impact of changing the policy•System Compliance testing

• Is a complex system (with many technologies) in compliance with policies?

•Procurement Support•Support construction of RFPs•Leverage knowledge of what systems/organizations are using each product for license negotiations



Extended US-Govt General Use Cases

•Support Cross-Agency Initiatives• Inform policy decisions in participating agencies• Increase speed of adoption•Locate synergistic programs across agencies

•“Line of sight” project management•Evaluate single system in terms of technology, business and service aspects

•Redundancy and gap analysis at multiple levels

•Evaluate compliance of fielded systems•Example: Public Health Information Network (PHIN) model evaluates readiness of emergency response systems



DEMO – Bricks Management with TopBraid Live™

•Show sample brick from PPT (next slide). •Open Bricks management app. Search for Web Browser in the general search; note command completion.

•Examine the brick, and compare to the PPT slide.

GSA

.

15

Web Browser

GSA Approved Waivers and Additional Supporting Information

GSA Tactical Direction (Next 2 Years) GSA Strategic Direction (2 to 5 Years)

Retired (Product / Date)

GSA Approved Standard (Current)

Responsible Group: Desktop SubcommitteeCIO POC: G. Thomas

Author: K. Rice 202 501 0496

In Containment (Product / Date /Projected Retirement)

MS Internet Explorer 6.0MS Internet Explorer 7.X MS Internet Explorer X.X

All versions of Netscape (effective Nov 2000).

All versions of IE before 5.0 (effective 15 Jun 2002)

MS IE 5.x (April 12, 2007).

•Currently, the web browser is heavily dependant on the OS in which it operates. Currently IE does the best job with the standard GSA OS and is widely accepted in the www environment. Netscape or Firefox (Mozilla derivatives) can only be used with an approved waiver from the Desktop Standards Subcommittee.

•An approved exception is for developers to use other browsers to support external clients.

ITAPC Approved: April 2007

MS IE 6.0 (4/12/07/1/1/08)




•Open Bricks management app. Search for Web Browser in the general search; note command completion.

•Examine the brick, and compare to the PPT slide.




•Cross-reference by any entity on the screen, e.g.,•Click on G. Thomas at the bottom of the Web Browser brick, and see all bricks for which he is the POC

•Click on Desktop Operating System, and see all of its policies.

•Click on a policy (say, Windows XP2), and see its profile

•Click on a Vendor (e.g., Microsoft) and see all its products.




•Value of Semantic Web Linked Data so far:•Every entity is ‘first class’ – all information about it can be displayed

•Information is linked in a uniform way – Person, Vendor, Product, etc., everything is a linked entity

•Question: How do we specify/control what is displayed about a particular type of entity?




•Return to the Web browser brick (search again, or go through G. Thomas). It includes a list of all relevant products. Products are shown with their Vendors. What if I want to customize this display?




•Return to TobBraid Composer™. Select TechnologyProduct from the Classes pane. The Instance pane shows all known instances, and information about them.

•Customize this display, to add another property, “brandName”.

•Reload the Bricks application, and navigate again to Web browser. The new information appears on the grid.


•Display now shows Brand Name for all products.




•Value of Semantic Web Linked Data so far:•“Model driven interface” – specification of the user interface is manage just like any other data.

•Non-programmers can customize interfaces

•Interface customization can refer to schema information as well.




•Multiple views on information. In this view, we can make spot-edits to information (e.g., add “Navigator” as the brand name for Netscape’s browser). In another view, information is display-only.

•Linked information can use existing information to prompt answers (e.g., add new POC – list of Persons appears)




•Viewing modes include widgets like calendars or graphs as relevant.

•Select “Desktop Operating Systems”

•Policy decisions include dates of retirement, in containment, etc.

•Select “Calendar” and select all properties. Scroll back to May, 2008 or March, 2008 to see calendar view of information.




•Graph view can make certain relationships visually apparent – For instance, the multiple relationships between the Web browser brick and IE 6.0 is apparent in this diagram:




•Value of Semantic Web Linked Data so far:•Same information can be viewed in different ways

•Same information can be acted on in different ways

•Supports different user communities, e.g., Bricks maintainers vs. Bricks users




•Many of these advantages could be managed by a carefully designed relational model. One strength of Semantic Web Linked Data is the ability to refer to external information (the “Web” part of “Semantic Web”)

•Federal Enterprise Architecture (FEA) is a vocabulary of Service Components, Business Areas, Technologies and Performance Measures for the federal government.




•View the FEA fragment relevant to Bricks (technology areas)

•Find a brick called Electronic Messaging

•There is an FEA category called Electronic messaging – that brick belongs here

•Update the FEA correlation of the Brick to match the FEA category. See the update immediately.




•Offline analytics using SPARLQMotion. Open DemoScripts.n3 in the browser. Edit script Conflicts

•The script finds technologies that are both approved and retired, and shows them in a tab delimited file

•ConflictsXML formats them in a table

•Run both scripts




•Replace one POC with another – view the script called ListPOC

•It uses POCs.jsp

•It calls another script, ChangePOC

•Change C. McFerren’s assignment to G. Thomas

•Reload BricksData to see the changes



Benefits of using Semantic Web for Enterprise Architecutre

•Every entity is ‘first class’ – no re-engineering data to promote entities as req’ts change

•Flexible schemas – add new kinds of data (metadata) as systems change

•Link external information – refer to reference models, standards, any external information as a ‘web’ connection (URI)



Benefits of using TopBraid Suite™ for Enterprise Architecture

•Standards-based – based natively on RDF, RDFS and OWL

•Integrated development/deployment environment. What you see in Composer is what you get in Live

•Integrated Forms and Grid editors – end users can customize displays using Composer editors

•Multiple import modes – information from other EA systems, spreadsheets, databases, etc.



Benefits of using TopBraid Suite™ for Enterprise Architecture (cont.)

•Multiple display widgets – forms, grids, calendar, map, graph, etc.

•Model-driven interface – user interface is specified just like any other data.

•SPARQLMotion™ - graphic dataflow language for specifying complex information filters and transformations

•Integration with JSP and other means for generating web interactions

Information—Integration—Intelligence Solutions Semantic Web for Enterprise Architecture with...

Documents

Transcript of Information—Integration—Intelligence Solutions Semantic Web for Enterprise Architecture with...