Ontology And Taxonomy Modeling Quick Guide


Published on

Approach to information using ontology / taxonomy layer. Experiences on data model design work.

Published in: Education, Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Brain will not get bigger – amount of information will
  • The data integration. It is where we spend most of our time,
  • Development of Ontology driven system is like any other dev, except perhaps one thing: focus is on subject centric computing. = system development with sem tech approach
  • Top down – bottom up
  • Biz case requires a large understanding or business needs, application landscape, integration challenges, data sources and interfaces Lack of risk taking in times when you should innovate and generate new type of business?
  • Ontology And Taxonomy Modeling Quick Guide

    1. 1. Ontology modeling quick guide Experiences on Taxonomy and Ontology development work heimo hanninen Tieto, [email_address]
    2. 2. Why do we need better concepts for organizing information? 2011-02-09 [email_address]
    3. 3. Information is Constantly in Motion – - a need for better management 30% of people’s time is spent searching for relevant information Only one-third of CFOs believe that the information is easy to use, tailored, cost-effective or integrated 17% of IT budgets for storage hardware and storage management software and people More than 60% of CEOs believe their business needs to access and understand information faster to make swift decisions 30–50% of design time is copy management 85% of information is unstructured 37% growth of disk storage in 2005 40% of IT budgets may be spent on integration Source: IBM [email_address] Documents Transactions Customers Partners Employees Organizations Financials Products E-mails Databases Media Web content Reports
    4. 4. Corporate information in silos – a need for connecting layer 2011-05-11 [email_address] Partners R&D Production ICT Sales & Marketing HR
    5. 5. What is ontology in IT system scope? Enterprise Architect Dmitry Bogachev – Topic Maps 2007 -metadata
    6. 6. IM Layers (a’la Heimo) 2011-05-03 project technology service staff solution customer Business Ontology/Domain model : -Business entities -With associations and -Properties -Across domains Taxonomy : -Categorize -Hierarchical -Domain specific Information : -with metadata -identified -content and data Direct link Indirect link Value chain : -Processes document
    7. 7. Phased modelling work 2011-06-17 Preparation [email_address] iterative iterative
    8. 8. Recursive ontology development [email_address] 2011-02-09 Visualize Formalize Populate Analyze & Refine <ul><li>Biz reqs </li></ul><ul><li>Value chain </li></ul><ul><li>User study </li></ul><ul><li>Conceptual model </li></ul><ul><li> Cmap </li></ul><ul><li>Logical model </li></ul><ul><li> UML class diagram </li></ul><ul><li>Implementation model </li></ul><ul><li> RDF(S), OWL, Topic Maps, XML schema </li></ul>test Use case Prototype Pilot Use case Process walk
    9. 9. About the design work <ul><li>A kind of data modeling and knowledge engineering </li></ul><ul><ul><li>80% of communication, 20% of design </li></ul></ul><ul><li>Top down: business needs the information </li></ul><ul><li>Bottom up: inventorying where to get the data </li></ul><ul><li>Middle out: start with a motivated gang, a small system </li></ul><ul><li>Skills required: </li></ul><ul><ul><li>SMEs, often a guy who has been around long enough (find them) </li></ul></ul><ul><ul><li>Communication and facilitation skills </li></ul></ul><ul><ul><li>Data modeling (visualization) skills </li></ul></ul><ul><li>Team work: to create understanding on situation and common goal </li></ul><ul><li>Deliver something tangible to review (PoC approach) </li></ul><ul><li>Focus on the business not on the technology </li></ul><ul><li>“ Keep stakeholders close and enemies closer” </li></ul>2011-02-09 [email_address]
    10. 10. System development with semantic technology approach <ul><li>Understanding semantics of biz entities and taking good care of managing identities of entities and information related. </li></ul><ul><li>Understand business (value proposition & process) </li></ul><ul><li>Extract info objects needed in process: </li></ul><ul><ul><li>Entities, </li></ul></ul><ul><ul><li>their relationship, </li></ul></ul><ul><ul><li>properties and </li></ul></ul><ul><ul><li>info resources (links to docs) </li></ul></ul><ul><li>Model the formal ontology in W3C: RDF/OWL or ISO: Topic Maps </li></ul><ul><li>Analyze and build adapters to sources (mapping) </li></ul><ul><li>Analyze biz app interface and provide methods and </li></ul><ul><li>Create ontology queries and package results for methods </li></ul>2011-03-04 [email_address]
    11. 11. Finding critical information assets and mapping them to business objects 1. Biz Process Walk through 2. Describe biz entities, properties and relations in common biz language 3. Identify sources. Understand local glossaries 4. Create mapping from local to global glossary Business ontology Heimo Hänninen [email_address] R&D Logistics Manufac- turing Marketing Sales Distri- bution Customer Support Product Design PDM, ERP CMS BI Sales & Marketing Partner’s data CRM
    12. 12. Faced problems in the real world <ul><li>Poor data quality in source systems </li></ul><ul><ul><li>missing metadata, no identifiers, ad hoc field naming etc. </li></ul></ul><ul><li>Security mgt. </li></ul><ul><ul><li>do you have to copy ACL or request it while user runs a query? </li></ul></ul><ul><li>Performance </li></ul><ul><ul><li>if running complex queries </li></ul></ul><ul><li>Governance </li></ul><ul><ul><li>difficult to define, who owns centralized knowledge service (it's not CMS, nor DW, nor CRM, nor PDM but can benefit from those all). </li></ul></ul><ul><ul><li>Usage: everyone want to ride on a bus but nobody wants to run the bus company. </li></ul></ul><ul><li>Ontology is redundant metadata about data in other systems. </li></ul><ul><ul><li>Not good for real time critical systems. Virtual ontology engine  which reads data directly from source is not here yet. </li></ul></ul><ul><li>Difficult to calculate the business case. </li></ul><ul><li>Not in ICT main stream. </li></ul><ul><ul><li>Educate and lobby managers, train developers to use sem tech </li></ul></ul>[email_address] 2011-03-04