applying the semantic web in your organization...

The Open Source Leaderin Information Collaboration

Applying the Semantic Web in your

Organization Today

zAgile Proprietary and Confidential, Copyright (c) 2008-2009 zAgile Inc.

• The Semantic Web (SW) – Intro and Origins

• Current State of Information on The Web

• Promises and Applications of SW

• Applying SW to The Enterprise

Agenda

• Applying SW to The Enterprise

• zAgile’s Use of SW Technologies

• Demo: zAgile Wikidsmart for Confluence &

JIRA

• Q & A

The State of Information on The Web

The Problems with Information on The Web


Information Challenges in The Enterprise

Business

Manager

Business

Sponsors

Require-Methodology

QA

Sales

Customer

Support

Channels

Call Center

Require-

ments

Strategy

Business

Cases

Focus

Groups

Product

Manager

Spec

Marketing Manager

Lead DeveloperIT Executive

IT

Status Report

Regional Managers

DocumentationCustomer Support

QA

Developer

Enterprise Applications Mimic the Problems

with The Web

• Heterogeneous, Siloed Applications

• Lots of Data but little Semantics

Problem Characteristics

• No Shared Vocabularies

• Lack of Inter-Connectivity of Information

• No Reuse Across Applications & Processes

• …

• From Hypertext to Hyperdata (aka Linked Data)

• Formal, Explicit and Shared Vocabularies for

Representing Information

• Rich Taxonomies for Organizing Knowledge

• Machine Process-able Representation of Information

The Promises of SW

• Machine Process-able Representation of Information

• Infer Facts based upon Existing Assertions

• Reuse Information across Heterogeneous Sources

• …


Linked Data or Hyperdata (Wikidsmart)

Semantic Search (Wikidsmart)

Integrating Information Across Applications

• Well-defined domains

• Large Taxonomies

• Fragmented Information

• Heterogeneous Applications Environments

• Examples:

Applicability of SW – Some Examples

• Examples:

– Libraries

– Medicine / Biology

– Federal government

– Software engineering

– Etc.


A Fragmented Environment…

Issue/Bug Management

(Bugzilla, Jira, etc.)

Wiki (MediaWiki,

Twiki, Confluence, Mindtouch Deki,

etc.)

Version Control(CVS, Subversion,

Perforce, etc.)

Test Cases(HP, IBM,

TestTrack Pro, etc.)

• Project • Project • Component • Test Case• Project

• Component

• Release

• Task/Issues

• Status

• Developer

• Project

• Requirements

• Milestones

• Test Plan

• Process

• Author

• Component

• Version

• Issue/Task

• Developer

• Activity

• Test Case

• Environment

• Pre/Post

Conditions

• Component

• Tester

A Fragmented Environment…



Wiki (MediaWiki,


etc.)


Perforce, etc.)

Test Cases(HP, IBM,


Role

WikiProject Version Control

Issues

Task

Test

Cases

Role

ComponentStatusProcess

A Shared Vocabulary



Wiki (MediaWiki,


etc.)


Perforce, etc.)

Test Cases(HP, IBM,


Capture & Integrate

zAgile

Semantic

Repository

Application

__________

Domain

Capture & Integrate

Bringing It Together -- zAgile’s Wikidsmart for Confluence

Information Collaboration Dashboard

• Open Source semantic infrastructure

and plug-in for Confluence

• Semantic wiki: adds structure,

consistency, easy maintenance,

and cohesion of content

• Smart search: easily find precise

informationinformation

Add Connectors:

• Deep interoperability with other

applications and tools

• Information dashboard: access a

knowledge repository spanning your

tools and applications

JIR

A

Su

bv

ers

ion

Cru

ise

Co

ntr

ol

Test

Ca

se M

gm

t

Sa

lesf

orc

e.c

om

Re

qu

ire

me

nts

Mg

mt

• Problem: distributed teams have different

processes and tools, and nothing is integrated

• Solution: SW is the right vehicle to integrate:

– Teams

Tools and applications

zAgile Addresses Software Engineering First

– Tools and applications

– Processes

– Knowledge

• zAgile’s Software Engineering ontologies are

based upon industry standard metamodel

• Wikidsmart adds structure to the wiki, using

SW technologies

• Simple ALM application built-in to wiki

• Other tools can be “plugged in” while

retaining coherency across the environment

Summary

retaining coherency across the environment

• Cohesion is achieved across the engineering

environment’s teams, tools, processes, and

knowledge


• Test-drive hosted Wikidsmart for Confluence

at www.zagile.com

• Download open source Wikidsmart for your

own projects

• Correspond with zAgile at [email protected],

Suggested Next Steps

• Correspond with zAgile at [email protected],

we can help


Information Integration Across the Enterprise

Project Artifacts

Version Control

Product Artifacts

Project Planner

ForumsDefect

Tracking

Tools

Asset Management

Team Management

Product Management

Auditing & Compliance

Project Management

Quality Management

Dashboard and Applications

Software

Engineering

Teams

ManagersProject

Sponsor

Deliver Unified View

zAgile

Semantic

Repository

Other Applications &

Widgets

Instant Messaging

Build Tools Change Management

Process Management


zAgile’s Wikidsmart -- Architectural View

zAgile XML-RPC Server

(zRPCServ)

Web/Application Container

Jena Framework

zAgile Semantic Acces Layer

(zSlayer)

zAgile

Semantic

Plugin

Web/Application Server

Atlassian Confluence

Reference

zAgile Semantic

Repository

(Metamodels &

Ontologies)

Ontologies &

Metamodels

•Project

•People

•Document

•Organization

•Software

•Methodology

Atlassian Confluence

Repository

Jena Framework - © Copyright 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Hewlett-Packard Development Company, LP

Atlassian Confluence - Copyright © 2009 Atlassian Pty Ltd.

zAgile Semantic Components - Copyright © 2008, 2009 zAgile Inc.

• The Wiki: fantastic for entering and sharing content, but:– No way to ensure consistent data entry

– No way to automate content & link updates

– Hard to find information

– No way to deeply and comprehensively integrate

Sample Problems zAgile Wikidsmart Solves

– No way to deeply and comprehensively integrate information from external systems

– No pre-built “wiki applications” for a given domain problem

• Tools do not talk to each other

• Processes difficult to disseminate or track


applying the semantic web in your organization...

Documents