RESOURCEOME – CREATE, ORGANISE AND APPLY YOUR KNOWLEDGE<br />Alessandro Bettacchi, Simon Brander, Nicola Paoletti<br />1/2...
Resourceome in a few words  <br />1/20/2010<br />2<br />Resourceome - Complex System Design - AY 2009/2010<br />
Resourceome in a few words <br />1/20/2010<br />3<br />Resourceome - Complex System Design - AY 2009/2010<br />Resourceome...
 A semantic-driven and agent-oriented workflow management system.</li></li></ul><li>BACKGROUND AND CONCEPTS<br />1/20/2010...
Background and concepts<br />WHAT IS KNOWLEDGE?<br />Knowledge is the collection of the informations needed by a human bei...
Background and concepts<br />TWO TYPES OF KNOWLEDGE<br />1/20/2010<br />6<br />Resourceome - Complex System Design - AY 20...
Background and concepts<br />ONTOLOGIES IN INFORMATION SCIENCE<br />1/20/2010<br />7<br />Resourceome - Complex System Des...
Background and concepts<br />WHAT IS WORKFLOW?<br />A workflow is the partial or total automation of a business process. I...
Background and concepts<br />WORKFLOW MANAGEMENT SYSTEMS<br />1/20/2010<br />9<br />Resourceome - Complex System Design - ...
Engine: provides the run time execution environment for a workflow istance
 Administration and Monitoring: provides user management and process control functions.
Client Application: is the software system responsible for the interaction between the end user and the WMS
 Invoked Applications: consist of external software components invoked to perform tasks that are not part of the WMS logic...
RESOURCEOME WORKFLOW management system<br />1/20/2010<br />11<br />Resourceome - Complex System Design - AY 2009/2010<br />
Resourceome Workflow Management System<br />THE WORKFLOW MODEL<br />1/20/2010<br />12<br />Resourceome - Complex System De...
Control Flow Patterns</li></ul>THE WORKFLOW MODEL - ACTIVITY<br /><ul><li>Activies are the computational blocks of a workf...
For each activity, a set of input/output parameters are defined. A parameter has its own datatype, supporting primitive ty...
If: conditional routing. The choice of the activity to execute is case-driven
Iterator: cyclic execution of a subflow until its condition is true
Concurrence: enables parallel execution
Default Exception: determines the routing according to previous exceptions or errors
Terminate: forces the termination of the workflow</li></li></ul><li>Resourceome Workflow Management System<br />RESOURCEOM...
Resourceome Workflow Management System<br />1/20/2010<br />15<br />Resourceome - Complex System Design - AY 2009/2010<br /...
FEATURES:
 Advanced manipulation of activity parameters
 Graphical Editor for If and Iterator conditions
 Ontology-driven process definition
 Workflow loading/saving</li></ul>WORKFLOW ENGINE<br /><ul><li> HERMES: an agent-based middleware able to execute a workfl...
 Execution Hystory
Upcoming SlideShare
Loading in …5
×

Resourceome presentation

608 views

Published on

Resourceome: a semantic knowledge management system based on multilevel ontology model, supporting both procedural and declarative knowledge.
http://resourceome.cs.unicam.it/

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
608
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Resourceome presentation

  1. 1. RESOURCEOME – CREATE, ORGANISE AND APPLY YOUR KNOWLEDGE<br />Alessandro Bettacchi, Simon Brander, Nicola Paoletti<br />1/20/2010<br />1<br />Resourceome - Complex System Design - AY 2009/2010<br />
  2. 2. Resourceome in a few words <br />1/20/2010<br />2<br />Resourceome - Complex System Design - AY 2009/2010<br />
  3. 3. Resourceome in a few words <br />1/20/2010<br />3<br />Resourceome - Complex System Design - AY 2009/2010<br />Resourceome is a Web-based framework consisting of:<br /><ul><li> A semantic knowledge management system based on a multilevel ontology model and supporting both procedural and declarative knowledge.
  4. 4. A semantic-driven and agent-oriented workflow management system.</li></li></ul><li>BACKGROUND AND CONCEPTS<br />1/20/2010<br />4<br />Resourceome - Complex System Design - AY 2009/2010<br />
  5. 5. Background and concepts<br />WHAT IS KNOWLEDGE?<br />Knowledge is the collection of the informations needed by a human being or a machine to carry out a task.<br />1/20/2010<br />5<br />Resourceome - Complex System Design - AY 2009/2010<br />KNOWLEDGE MANAGEMENT SYSTEMS<br />A Knowledge Management System (KMS) is a complex system providing a continous flow of knowledge to the right people at the right time within the organization in order to maximize the return on intellectual assets and information sources.<br />
  6. 6. Background and concepts<br />TWO TYPES OF KNOWLEDGE<br />1/20/2010<br />6<br />Resourceome - Complex System Design - AY 2009/2010<br />Declarative knowledge refers to our memory for concepts, facts, or episodes.<br />Procedural knowledge refers to the ability to perform various tasks.<br />
  7. 7. Background and concepts<br />ONTOLOGIES IN INFORMATION SCIENCE<br />1/20/2010<br />7<br />Resourceome - Complex System Design - AY 2009/2010<br />“An ontology is a formal, explicit specification of a shared conceptualization for a domain of interest.”<br />R. Gruber <br />In Information Science, ontologies are models representing an explicit knowledge and are specified through a formal language.<br />
  8. 8. Background and concepts<br />WHAT IS WORKFLOW?<br />A workflow is the partial or total automation of a business process. It is based on a model involving activities and control patterns which determine the execution flow.<br />1/20/2010<br />8<br />Resourceome - Complex System Design - AY 2009/2010<br />WORKFLOW MANAGEMENT SYSTEMS (WMS)<br />“A system that completely defines, manages and executes workflows through the execution of software.”<br />Workflow Management Coalition - WfMC<br />
  9. 9. Background and concepts<br />WORKFLOW MANAGEMENT SYSTEMS<br />1/20/2010<br />9<br />Resourceome - Complex System Design - AY 2009/2010<br /><ul><li>Process Definition: enables the modelling and the design of a workflow
  10. 10. Engine: provides the run time execution environment for a workflow istance
  11. 11. Administration and Monitoring: provides user management and process control functions.
  12. 12. Client Application: is the software system responsible for the interaction between the end user and the WMS
  13. 13. Invoked Applications: consist of external software components invoked to perform tasks that are not part of the WMS logic</li></li></ul><li>RESOURCEOME KNOWLEDGE ManaGement system<br />1/20/2010<br />10<br />Resourceome - Complex System Design - AY 2009/2010<br />
  14. 14. RESOURCEOME WORKFLOW management system<br />1/20/2010<br />11<br />Resourceome - Complex System Design - AY 2009/2010<br />
  15. 15. Resourceome Workflow Management System<br />THE WORKFLOW MODEL<br />1/20/2010<br />12<br />Resourceome - Complex System Design - AY 2009/2010<br />The main actors in the Resourceome workflow model are:<br /><ul><li>Activities
  16. 16. Control Flow Patterns</li></ul>THE WORKFLOW MODEL - ACTIVITY<br /><ul><li>Activies are the computational blocks of a workflow. A single activity may perform a simple and atomic operation (web service invoking, data conversion, ...) as well as a complex operation (subflow).
  17. 17. For each activity, a set of input/output parameters are defined. A parameter has its own datatype, supporting primitive types (STRING, INT, BOOLEAN,...), complex types (HashMap, Iterator, Set, ...) and arrays. </li></li></ul><li>Resourceome Workflow Management System<br />THE WORKFLOW MODEL – CONTROL FLOW PATTERNS<br />1/20/2010<br />13<br />Resourceome - Complex System Design - AY 2009/2010<br />Control flow patterns determine the order in which activities are executed.<br />Resourceome supports the following patterns:<br /><ul><li>Sequence: executes an activity after another
  18. 18. If: conditional routing. The choice of the activity to execute is case-driven
  19. 19. Iterator: cyclic execution of a subflow until its condition is true
  20. 20. Concurrence: enables parallel execution
  21. 21. Default Exception: determines the routing according to previous exceptions or errors
  22. 22. Terminate: forces the termination of the workflow</li></li></ul><li>Resourceome Workflow Management System<br />RESOURCEOME WMS ARCHITECTURE<br />1/20/2010<br />14<br />Resourceome - Complex System Design - AY 2009/2010<br />
  23. 23. Resourceome Workflow Management System<br />1/20/2010<br />15<br />Resourceome - Complex System Design - AY 2009/2010<br />PROCESS DEFINITION Tools<br /><ul><li> WORKFLOW EDITOR: a graphical tool for the design of complex workflows of activities.
  24. 24. FEATURES:
  25. 25. Advanced manipulation of activity parameters
  26. 26. Graphical Editor for If and Iterator conditions
  27. 27. Ontology-driven process definition
  28. 28. Workflow loading/saving</li></ul>WORKFLOW ENGINE<br /><ul><li> HERMES: an agent-based middleware able to execute a workflow definition as mobile and distributed code.</li></li></ul><li>Resourceome Workflow Management System<br />INVOKED APPLICATIONS<br />1/20/2010<br />16<br />Resourceome - Complex System Design - AY 2009/2010<br />Administration and Monitoring Tools<br /><ul><li>Monitoring Tools: interfacing with Hermes engine, collect informations on running workflows together with their status, and besides, provide:
  29. 29. Execution Hystory
  30. 30. Results visualization with several plugins
  31. 31. Publishing Tools: make available a workflow to the end user through a simplified GUI; in this way, published workflows can be accessed and executed without knowing their implementation.
  32. 32. Web Services: invoked at run time by the execution engine, assure a wide interoperability.
  33. 33. Visualization Plugins: are called when rendering a workflow result and provide specific views according to the result data type.</li></li></ul><li>CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />17<br />Resourceome - Complex System Design - AY 2009/2010<br />
  34. 34. CaseStudy: Industry, Business, and Finance<br />Knowledge<br /><ul><li>Companies
  35. 35. General information aboutcompanies
  36. 36. Country-specific business entitytypes
  37. 37. Industry ClassificationBenchmark (ICB)
  38. 38. Stock Markets
  39. 39. Markets
  40. 40. TickerSymbols</li></ul>1/20/2010<br />18<br />Resourceome - Complex System Design - AY 2009/2010<br />CaseStudy: Ontology<br />Makethisknowledgeusable in ResourceomeWorkflows<br />
  41. 41. CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />19<br />Resourceome - Complex System Design - AY 2009/2010<br />Case Study: OntologyDevelopmentProcess<br />1. Determine Scope<br /><ul><li>Covered domain?
  42. 42. Useofontology?
  43. 43. CompetencyQuestions?</li></li></ul><li>CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />20<br />Resourceome - Complex System Design - AY 2009/2010<br />Case Study: OntologyDevelopmentProcess<br />2. ConsiderReuse<br /><ul><li>Existingknowledge?</li></li></ul><li>CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />21<br />Resourceome - Complex System Design - AY 2009/2010<br />Case Study: OntologyDevelopmentProcess<br />3. Enumerate Terms<br /><ul><li>Whatimportantterms?</li></li></ul><li>CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />22<br />Resourceome - Complex System Design - AY 2009/2010<br />Case Study: OntologyDevelopmentProcess<br />4. DefineClasses<br /><ul><li>Whatclassesfromterms?
  44. 44. Classhierarchy?</li></li></ul><li>CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />23<br />Resourceome - Complex System Design - AY 2009/2010<br />Case Study: OntologyDevelopmentProcess<br />5. DefineProperties<br /><ul><li>Objectproperties?
  45. 45. Data properties?</li></li></ul><li>CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />24<br />Resourceome - Complex System Design - AY 2009/2010<br />Case Study: OntologyDevelopmentProcess<br />6. DefineConstraints<br /><ul><li>Whatkindofpropertyconstraints?</li></li></ul><li>CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />25<br />Resourceome - Complex System Design - AY 2009/2010<br />Case Study: OntologyDevelopmentProcess<br />7. Create Instances<br /><ul><li>Whatinstancesshouldexist?</li></li></ul><li>CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />26<br />Resourceome - Complex System Design - AY 2009/2010<br />Case Study: Ontology<br />
  46. 46. CaseStudy: Industry, Business, and Finance<br />1/20/2010<br />27<br />Resourceome - Complex System Design - AY 2009/2010<br />Case Study: Ontology (XML Code)<br />
  47. 47. CaseStudy: Industry, Business, and Finance<br />ProvidedValue<br /><ul><li>Comparetheperformance of companies
  48. 48. Conductwholisticcompanyassessment
  49. 49. Findpossibleinvestmentalternatives
  50. 50. Overview the important information in oneplace
  51. 51. etc…</li></ul>1/20/2010<br />28<br />Resourceome - Complex System Design - AY 2009/2010<br />CaseStudy: Scenarios<br />
  52. 52. SEE IT IN ACTION…<br />1/20/2010<br />29<br />Resourceome - Complex System Design - AY 2009/2010<br />

×