© copyright 2011 Semantic Insights™. Automated Traceability of Key Success Factors through Lifecycle Documents Chuck Rehberg, Chief Scientist Semantic.

Slides:



Advertisements
Similar presentations
1 Information Enterprise Architecture v September Walt Okon Senior Architect Engineer Senior Architect Engineer for Information Sharing Enterprise.
Advertisements

Chapter 7 System Models.
Taxonomy & Ontology Impact on Search Infrastructure John R. McGrath Sr. Director, Fast Search & Transfer.
IR Confidential & Proprietary Do Not Distribute Our Proposed IT Strategy (2006 – 2011) Developing Optimal IT Strategy Through Business Context, Applications,
Strategies to Improve Business and Technical Writing Francine Mahak, PhD Utah Government Auditors Association June 5, 2013.
Data Architecture at CIA Dave Roberts Chief Technical Officer Application Services, CIO CIA
Presented to: By: Date: Federal Aviation Administration Registry/Repository in a SOA Environment SOA Brown Bag #5 SWIM Team March 9, 2011.
Cyber Defence Data Exchange and Collaboration Infrastructure (CDXI)
|epcc| NeSC Workshop Open Issues in Grid Scheduling Ali Anjomshoaa EPCC, University of Edinburgh Tuesday, 21 October 2003 Overview of a Grid Scheduling.
SICoP 2011: Transforming Government through Innovation with Semantic Technologies Brand L. Niemann Director and Senior Data Scientist, Semantic Community.
© 2009 IBM Corporation iEA16 Defining and Aligning Requirements using System Architect and DOORs Paul W. Johnson CEO / President Pragmatica Innovations.
Chapter 5 – Enterprise Analysis
Policy based Cloud Services on a VCL platform Karuna P Joshi, Yelena Yesha, Tim Finin, Anupam Joshi University of Maryland, Baltimore County.
Reference Architecture for IT Optimization
The 20th International Conference on Software Engineering and Knowledge Engineering (SEKE2008) Department of Electrical and Computer Engineering
Copyright 2001 Advanced Strategies, Inc. 1 Data Bridging An Overview Prepared for DIGIT By Advanced Strategies, Inc.
Scope of TOGAF ADM The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the.
DoDAF V2.0 Community Update Overview
DoD Information Enterprise Architecture v2.0
The Engine Driving Business Management in Project Centric Environments MAGSOFT INTERNATIONAL LLC.
Overview of OASIS SOA Reference Architecture Foundation (SOA-RAF)
Establishing a service oriented composite applications development process for supporting work- based learning and competency progression management Hilary.
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
Unified Logs and Reporting for Hybrid Centralized Management
Semantic Web and Web Mining: Networking with Industry and Academia İsmail Hakkı Toroslu IST EVENT 2006.
Requirements Specification
MS DB Proposal Scott Canaan B. Thomas Golisano College of Computing & Information Sciences.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
LandWarNet 2020 and Beyond Enterprise Architecture
Click to add text © 2010 IBM Corporation OpenPages Solution Overview Mark Dinning Principal Solutions Consultant.
Getting Smarter with Information An Information Agenda Approach
The Engine Driving Purchasing Management in Complex Environments MAGSOFT INTERNATIONAL LLC.
Presentation Outline (hidden slide) Technical Level: 100 Intended Audience: TDMs, ITPros, ITDMs, BI specialists Objectives (what do you want the audience.
Knowledge Management in a fast changing world Kate Elphick
MPEG-21 : Overview MUMT 611 Doug Van Nort. Introduction Rather than audiovisual content, purpose is set of standards to deliver multimedia in secure environment.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
Agent Model for Interaction with Semantic Web Services Ivo Mihailovic.
Army Net-Centric Data Strategy Center Of Excellence (ANCDS) Army Data Harmonization and Integration Working Group (ADHIWG) Sever Ciorlian ANCDS Team Lead.
© copyright 2011 Semantic Insights™ Semantic Search/Research using PriArt: A DoD IG Example Chuck Rehberg CTO/Chief Scientist Trigent Software/Semantic.
Ontology for Federation and Integration of Systems Cross-track A2 Summary Anatoly Levenchuk & Cory Casanave Co-chairs 1 Ontology Summit 2012
Delivering business value through Context Driven Content Management Karsten Fogh Ho-Lanng, CTO.
Illustrations and Answers for TDT4252 exam, June
BAA - Big Mechanism using SIRA Technology Chuck Rehberg CTO at Trigent Software and Chief Scientist at Semantic Insights™
© copyright 2014 Semantic Insights™ “A New Natural Language Understanding Technology for Research of Large Information Corpora." By Chuck Rehberg, CTO.
1 ECCF Training 2.0 Implemental Perspective (IP) ECCF Training Working Group January 2011.
Personalized Interaction With Semantic Information Portals Eric Schwarzkopf DFKI
Service Service metadata what Service is who responsible for service constraints service creation service maintenance service deployment rules rules processing.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
The DoD Information Enterprise Strategic Plan and Roadmap (SP&R)
1 ECCF Training Computationally Independent Model (CIM) ECCF Training Working Group January 2011.
Selected Semantic Web UMBC CoBrA – Context Broker Architecture  Using OWL to define ontologies for context modeling and reasoning  Taking.
Semantic Wiki: Automating the Read, Write, and Reporting functions Chuck Rehberg, Semantic Insights.
Applying ontology and linguistics to automate reading, writing, and reporting of knowledge and information in a semantic wiki Chuck Rehberg Semantic Insights.
Built on the Powerful Microsoft Azure Platform, Forensic Advantage Helps Public Safety and National Security Agencies Collect, Analyze, Report, and Distribute.
Microsoft Azure and ServiceNow: Extending IT Best Practices to the Microsoft Cloud to Give Enterprises Total Control of Their Infrastructure MICROSOFT.
IQ Server Product Overview June The problem we solve in a customer’s words… “We have almost 400 applications and they are all intertwined and very.
Architecture Ecosystem SIG March 2010 Update Jacksonville FL.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
1© Copyright 2012 EMC Corporation. All rights reserved. Turning Big Data into Competitive Advantage “Big data will represent a hugely disruptive force.
AuraPortal Cloud Helps Empower Organizations to Organize and Control Their Business Processes via Applications on the Microsoft Azure Cloud Platform MICROSOFT.
Jens Ziegler, Markus Graube, Johannes Pfeffer, Leon Urbas
EI Architecture Overview/Current Assessment/Technical Architecture
CIM Modeling for E&U - (Short Version)
IC Conceptual Data Model (CDM)
Deployment Planning Services
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Single Point of Entry (SPOE)
Oscar AP by Massive Analytic: A Precognitive Analytics Platform for Effortless Data-Driven Decisions. Now Available in Azure Marketplace MICROSOFT AZURE.
11/17/2018 9:32 PM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN.
Presentation transcript:

© copyright 2011 Semantic Insights™

Automated Traceability of Key Success Factors through Lifecycle Documents Chuck Rehberg, Chief Scientist Semantic Insights™ (A division of Trigent Software, Inc.) 20-Nov-2011

Executive Summary Problem Addressed –The need to verify high-level requirements are transformed and reflected through all levels of project documents. Solution Proposed - A system that: –Given a list of Key Success Factors and a potentially large set of documents –Generates a “Traceability Report” mapping each Key Success Factor to Specific Statements in Specific Sections in Specific Documents Solution Requirements –Domain-specific Semantic Data (Dictionary, Ontology, Experiences, Language) –List of Key Success factors stated in natural language –Set of documents New Technologies Employed (recently patented or patent pending) –Natural Language Processing (non-statistical dictionary-driven, with WSD) –Meaning maps (multiple ways of saying the same thing) –Generation of focused high-speed rules-based document “readers” –Natural language report generation

Functional Overview

The basic process Identify Key Success Factors –Key Success Factors include natural language statements of Mission, Goals and other Requirements, often taken directly from the initial program documents. Provide Domain-specific Semantic data –This includes: Dictionary, Ontology, Experience and Language Provide access to the document corpus to be automatically read and analyzed Generate the desired report

Sample “Key Success Factors” 1.Function as one unified DoD Enterprise, creating an information advantage for our people and mission partners. 2.Provide a rich information sharing environment in which data and services are visible, accessible, understandable, and trusted across the enterprise. 3.Provide an available and protected network infrastructure (the GIG) that enables responsive information-centric operations using dynamic and interoperable communications and computing capabilities. 4.Drive the fundamental concepts of net-centricity across all mission of the Department of Defense to ensure that all applicable DoD programs, regardless of Component or portfolio, comply with the DoD net-centric vision and enable agile, collaborative net-centric information sharing.

Unpacking the Semantics of “Key Success Factors” (KSF) Each KSF statement embodies a number of semantically distinct assertions. For example from the preceding list: –“Provide a rich information sharing environment in which data and services are visible, accessible, understandable, and trusted across the enterprise.” The System unpacks this KSF statement into these basic requirements: –Environment provides information. –Information is shared. –Services are understandable across the enterprise. –Services are accessible across the enterprise. –Services are visible across the enterprise. –Services are trusted across the enterprise. –Data are understandable across the enterprise. –Data are accessible across the enterprise. –Data are visible across the enterprise. –Data are trusted across the enterprise.

Providing Domain-specific Semantic data (continuing the previous example) Beyond the normal everyday meanings, you may need to specify domain-specific semantics for these terms: –Environment –Information –“share” as in “to share information” –Services –Enterprise –understandable –accessible –visible –Data Such semantic information includes: –Linguistic metadata such as “part of speech” and usage –An Ontology specifying relevant generalizations, specializations, composition, and relationships to other concepts. Note: The following basic demo uses only the predefined English dictionary and grows the initial Ontology dynamically

High-speed machine reading Readers –The system generates special purpose high-speed readers capable of quickly “reading” a large set of documents. –The goal of the reader is to identify statements which semantically overlap each of your Key Success Factors. –Domain-specific semantic information will be used to increase the accuracy of the results of the high-speed reader. Implications and Inferences –The system further uses domain-specific knowledge to find statements that imply support for your Key Success Factors.

Introducing PriArt

Enter Key Success Factor Statement

“Unpacked” KSF Form (demo purposes)

Select Architecture Documents to Read Architecture/ Appendix B_Draft OV-5a_IEA xxxxxxxxxxxx.doc Appendix F_Draft GIG 2.0 Alignment with DoD IEA xxxxxxxxxx.doc AV-1_Initial Draft DoD IEA xxxxxxxxxxxxx.doc CV-1 (rev1)_Initial Draft DoD IEA xxxxxxxxxxxxx.doc CV-2_Initial Draft DoD IEA xxxxxxxxxxxx.doc DoD EIEA AV-1_Vxxxxxxxxxxxx.doc Draft Activity Decomposition Overview (OV-5a)_IEA xxxxxxxxxx.pptx Draft Document Framework Description_IEA xxxxxxxxxxxxx.doc Draft IE Capabilities Taxonomy (CV-2)_IEA xxxxxxxxxxxxxxxxx.doc Draft IE Capability Vision (CV-1)_IEA xxxxxxxxxxxxxxxxx.doc Draft IE Operational Concept (OV-1)_IEA xxxxxxxxxxxxxxxxx.doc Draft Integrated Dictionary (AV-2)_IEA xxxxxxxxxxx.xlsx Draft Integrated Document_IEA xxxxxxxxxxxxxxxxxxxxxxx.doc Draft Operational Viewpoint_IEA xxxxxxxxxxxxxxxxxxxx.doc Draft Overview and Summary (AV-1)_IEA xxxxxxxxxxxxxxxxxxx.doc Draft Updated EA Compliance Req_IEA xxxxxxxxxxxxxxxxxxx.doc Operational Context Initial Draft DoD IEA xxxxxxxxxxxxxxx.doc OV-1_Initial Draft DoD IEA xxxxxxxxxxxxxxx.doc OV-5a_Initial Draft DoD IEA xxxxxxxxxxxxxxx.doc OV-6a_Initial Draft DoD IEA xxxxxxxxxxxxxxx.doc Revised EA Compliance Initial Draft DoD IEA xxxxxxxxxxxxxxx.doc

Report on a set of Architecture Documents showing mapping within one document. (Draft Integrated Document_IEA v2_Sep Deliverable_ doc)

Report on a set of Architecture Documents showing all references to a selected KSF.

PDF Report follows same format as on-line report

Generated Bibliography Bibliography [ 1 ] doc. Retrieved on 11/20/ :58:38, from IE Operational Concept (OV- 1)_IEA xxxxxxxxxxxxx.doc [ 2 ] doc. Retrieved on 11/20/ :59:15, from Integrated Document_IEA xxxxxxxxxxxxxxxx.doc [ 3 ] doc. Retrieved on 11/20/ :18:59, from Operational Viewpoint_IEA xxxxxxxxxxxxxxxx.doc [ 4 ] doc. Retrieved on 11/20/ :20:46, from 6a_Initial Draft DoD IEA xxxxxxxxxxxxxxx.doc [...]

However, the information source may refer to new terms and new concepts SIRA combines both advanced linguistics and semantics to discover and learn newly encountered items Example: using linguistic placeholders like “the unknown thing” (#?#) This Investigation: Environment provides information. Services are understandable across the enterprise. Services are accessible across the enterprise. Services are visible across the enterprise. Services are trusted across the enterprise. Data are understandable across the enterprise. Data are accessible across the enterprise. Data are visible across the enterprise. Data are trusted across the enterprise. Becomes: #?# are accessible across the #?#. #?# are trusted across the #?#. #?# are understandable across the #?#. #?# are visible across the #?#. #?# provides information. The investigation now includes anything that asserts these relationships

Applied to a Portfolio of existing Systems Portfolio/ 03a_CDD for GFM DI Incr xxxxxxxxxxxxxxxxxx.pdf xxxxxxxxx CDD.doc a4542xx.pdf a5265xx.pdf Army DIMHRS CDD xxxxxxxx.pdf DAI CDD Appendices approved xxxxxxxxxxx.pdf Document-NECC CDD xxxxxxxxxxxxx.doc DRAFT NCES CDD xxxxxxxxxx.doc Final CDD draft xxxxxxxxx.doc GCSS-A_MS B_CDD_xxxxxxxxx.doc GCSS_FoS_MA_ICD_xxxxxxxxxx.pdf GIGMAICX.pdf Joint_JET-_NN_CDD_Appendix_xxxxxxxxxxxxxxxxxxx.doc Lightweight FSP CDD xxxxxxxxxxx.doc NSWCDD-MP-xxxxxxxxxxx.pdf Unmanned Systems ICD Draft xxxxxxx.doc

Over 2000 pages of source documents become 30 pages of points relevant to the investigation with bibliography and hyperlinks

The need for more accuracy By using “the unknown thing” (#?#) you can identify items which represent the specific kinds of items desired. For example (samples from previous report): –Environment Cloud Computing SOA –Information Survival Information potential or impending attack based on intelligence law enforcement and open source information Information on security relevant events –Services NECS Services –Enterprise The GI Analytical Environment GCSS-Army –Data User Profile However #?# can also identify items which may be outside our interest. Perhaps this is not relevant: –“Program-specific assessments from this literature will provide tailored information. [4]”

Enhance the Ontology to increase accuracy SIRA naturally uses your investigation and information sources to automatically extend the current Ontology However, many relationships such as generalization, specialization, instantiation, and composition are often not explicitly stated in the text. These may be required to identify relevant information. By adding semantic information to the Ontology, the system automatically extends the subsequent semantic research to include these concepts/terms (and their synonyms) where appropriate. In short, you can introduce a concept and corresponding terms, define the relevant semantic relationships and linguistic metadata, and begin using the term in your investigation right away.

Reporting and Queries As a result of machine reading, the information source documents are semantically index relative to the investigation. The system supports interactive queries of this semantic index. Report templates and content can be dynamically defined to render the results the query results. All semantic information can be exported “Key Success Factors” are just one example of an investigation. There is no restriction on the nature and content of an investigation.

24 Who we are: –Semantic Insights is the R&D division of Trigent Software, Inc. –We focus on developing semantics-based information products that produce high-value results serving the needs of general users requiring little or no training. –Visit us at Who we are

25 Chuck Rehberg As CTO at Trigent Software and Chief Scientist at Semantic Insights, Chuck Rehberg has developed patented high performance rules engine technology and advanced natural language processing technologies that empower a new generation of semantic research solutions. Chuck has more than twenty five years in the high-tech industry, developing leading-edge solutions in the areas of Artificial Intelligence, Semantic Technologies, analysis and large –scale configuration software.

© copyright 2011 Semantic Insights™