Managing SemanticModels for representingIntangible EnterpriseAssets: The ARISTOTELEProject SoftwareArchitecturePierluigi R...
 Overview of the ARISTOTELE project The ARISTOTELE Approach ARISTOTELE Models ARISTOTELE tools ARISTOTELE Architectur...
Problems to Overcome Conflicting goals Separation and missing interconnection between enterprise learning pathwaysand re...
ARISTOTELE Approach: overview1. To merge strategicorganisational objectives andworker preferences and needsto create perso...
 The top level is the starting point: inputs (organizational objectives and workerneeds, preferences, …) “influencing” th...
The general Idea6
 Knowledge Model (KM) provides constructs for the representation ofenterprise knowledge entities, enterprisedomain vocab...
 The models have been defined following four maindirections: the analysis of organizational practices of the pilots, the...
Role of the Models: Integrated Schemas9
 Reference Ontologies: used to represent andstructure enterprise’s resources (e.g., worker profile,competences, project a...
The Knowledge Model: reference Ontology11SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
The Knowledge Model: Organisation Ontologyand IWT Learning Domain Model12SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
Competence Model13
Worker Model14
Learning Experience Generation Model15
A Knowledge model instance example16
Training Domain Instance17SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
 Knowledge Management (KM) Tool, exploiting methodologiesand techniques supporting organizational knowledge building andm...
How Fit Everithing Together19
 Several Challenges Complexity of the systems Enterprise architecture Enterprise Application Integration and Semantic ...
 Provides a methodological and technological framework describingprinciples and guidelines underlying the whole ARISTOTEL...
Definition of the High Level ArchitectureDocumentation (1/2) Produce the documentation that communicates thearchitectural...
 More in detail, the process followed the steps Identify the stakeholders and their needs (Designer, Developer, Integrat...
ArchitectureDesignMIKE 2.0SemanticEnterpriseEnterprise 2.0High LevelArchitectureSoftwareArchitectureDocumentationViews & B...
 Input User Requirements Business Process Patterns: to describe how ARISTOTELE supports themembers of the organization...
ARISTOTELE Architecture Logical viewDataDataTools PWLE LEG HRM CN KMServicesCore ServicesOrchestration ServicesBase Servic...
Semantic Layer high level architecure27SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
Enterprise Liked Data Layer2828SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
Available tools29
Available tools30
 Web site: http://www-aristotele-eu.org Follow us on twitter: (@Aristotele_ip) URL:http://twitter.com/#!/Aristotele_ip ...
Upcoming SlideShare
Loading in …5
×

Managing Semantic Models for representing Intangible Enterprise Assets: The ARISTOTELE Project Software Architecture

829 views

Published on

Managing Semantic Models for representing Intangible Enterprise Assets: The ARISTOTELE Project Software Architecture. Learn more on http://www.aristotele-ip.eu/

Published in: Technology, Education, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
829
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Managing Semantic Models for representing Intangible Enterprise Assets: The ARISTOTELE Project Software Architecture

  1. 1. Managing SemanticModels for representingIntangible EnterpriseAssets: The ARISTOTELEProject SoftwareArchitecturePierluigi RitrovatoDep. Of Electronic Engineeringand Computer Engineering,University of SalernoMOMA S.p.A
  2. 2.  Overview of the ARISTOTELE project The ARISTOTELE Approach ARISTOTELE Models ARISTOTELE tools ARISTOTELE Architecture The approach The logical view Other Available results The Architecture Already Developed toolsOutlines2
  3. 3. Problems to Overcome Conflicting goals Separation and missing interconnection between enterprise learning pathwaysand real contingent workers’ needs. Lack of integration Missing links between learning strategies oriented to different working andorganisational contexts. Difficulty to capture and reuse formal and informal knowledge for organisationallearning. Once the needed knowledge is acquired, all information on how thisknowledge was built disappears Lack of any form of Collective Intelligence Heterogeneity High-level fragmentation of data, information, tools and environment used byworkers to operate in their working life (studying, carrying out process activities,discussing, collaborating, etc.). Difficulty to assess, exploit, share and reuse learning experiences in terms ofapproach, contents and knowledge both at personal and enterprise level.SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 20123
  4. 4. ARISTOTELE Approach: overview1. To merge strategicorganisational objectives andworker preferences and needsto create personalised andadaptive learning experience;2. To support organisationalprocesses: optimising humanresource allocation; supportingdaily work through PersonalWorking Learning Environment;individual performanceassessment;3. To support innovationmanagement and buildingthrough Innovation FactorySOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 20124
  5. 5.  The top level is the starting point: inputs (organizational objectives and workerneeds, preferences, …) “influencing” the key ARISTOTELE processes The middle level embraces the key ARISTOTELE processes centred oncollaboration: Building of personalized learning experiences Creation of Innovation Factory for collaborative innovation boosting Management and sharing of personal knowledge to be “reused” in different domains and tasks The bottom level includes features supporting update and reuse of organizationalknowledgeARISTOTELE enabling building blocksand research areas5SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  6. 6. The general Idea6
  7. 7.  Knowledge Model (KM) provides constructs for the representation ofenterprise knowledge entities, enterprisedomain vocabulary, educational vocabulary Competence Model (CM) provides constructs for the representation ofcompetences and their relations to otherconcepts such as context, activities, andobjectives Worker Model (WM) provides constructs for the representation ofworker including social, learning, workingand personal goals Learning Experience Model (LEM) provides constructs for the learningexperience needed to achieve a newcompetence or fill a competence gap.ARISTOTELE Models7SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  8. 8.  The models have been defined following four maindirections: the analysis of organizational practices of the pilots, theproject’s scenarios and requirements, and the methodologiesneeds to derive the main concepts and relationships of the fourmodels; the definition of few and clear principles to follow during themodeling activities; the selection of a set of specifications, standards and availablemodels from the the State-of-the-Art and Intelligent WebTeacher (IWT) platform that represent the building blocks of thefour models; the analysis of actual experiences from communities of practiceModels Definition8SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  9. 9. Role of the Models: Integrated Schemas9
  10. 10.  Reference Ontologies: used to represent andstructure enterprise’s resources (e.g., worker profile,competences, project and activities, etc.) FOAF, DOAP, SKOS, SIOC, etc. Organisation Ontologies: exploited to provide ashared classification of the resources available in theKnowledge base. to classify knowledge resources according to the context of theenterprise and to provide a common access layer toheterogeneous resources daily produced by the workers (e.g.,document, wiki, blog, etc.).Characteristics of the ARISTOTELEModels10SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  11. 11. The Knowledge Model: reference Ontology11SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  12. 12. The Knowledge Model: Organisation Ontologyand IWT Learning Domain Model12SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  13. 13. Competence Model13
  14. 14. Worker Model14
  15. 15. Learning Experience Generation Model15
  16. 16. A Knowledge model instance example16
  17. 17. Training Domain Instance17SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  18. 18.  Knowledge Management (KM) Tool, exploiting methodologiesand techniques supporting organizational knowledge building andmaintenance (merging, matching, versioning) in a semi-automaticway using knowledge extraction techniques as well. Human Resource Management (HRM) Tool, exploitingmethodologies and techniques supporting competence gapanalysis, team and group formation, internal resourcescompetence development, and recruitment. Social Collaboration and Networking (CN) Tool, aiming atsupporting the innovation process within the organization. . Learning Experience Generation (LEG) Tool, exploitingmethodologies and techniques to recommend suitable contentsand didactic approaches to the workers, to generate, adapt andmanage personalized learning experiences tailored to theorganizational objectives. Personal and reliable Working and Learning Environment(PWLE) tool, acting as a methodological and technologicalintegrator for all the other tools.The Tools18SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  19. 19. How Fit Everithing Together19
  20. 20.  Several Challenges Complexity of the systems Enterprise architecture Enterprise Application Integration and Semantic technologies Integration of Several Technologies several form of deployment (SaaS, IaaS, distributed, centralised) Facilitate Adoption, Acceptance and Assimilation Provide the right information to the involved stakeholders(distributed teams) Respecting the time constrains Key decisions Incremental approach (2 steps) first High Level Architecture (guidelines, approach description anddocumentation) – exploited for tools design Architecture Design leveraging on existing frameworksDesign the ARISTOTELE Architecture20SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  21. 21.  Provides a methodological and technological framework describingprinciples and guidelines underlying the whole ARISTOTELEPlatform Provides specification of the logical description of the architecture Provide an understanding of what kind of building block we rely on and How they contribute to the achievement of the whole system Provides guidelines for architects and developers team in chargeof the design and development of the different ARISTOTELEmodules Provides information about decomposition of the platform Identification of the main building blocks Identification of their responsibilities Provides information about ARISTOTELE enabling technologiesfeaturesDefinition of the High Level ArchitectureWhat it is: Sketch the whole system21SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  22. 22. Definition of the High Level ArchitectureDocumentation (1/2) Produce the documentation that communicates thearchitectural decisions Inspired to the Views and Beyond (V&B) approachproposed by the Software Engineering Institute Motivation – An architecture document is useful only if itcommunicates effectively the architectural decisions Fundamental unit of documentation – Views, each representinga "part of the whole" system structures Fundamental principle – Documenting an architecture is amatter of documenting the relevant views, and then addingdocumentation that applies to more than one view The concept of View allows simplify the communication byfocusing only on some aspects at a time22SOA-KME Workshop at CISIS 2012Palermo 4th-6th, 2012
  23. 23.  More in detail, the process followed the steps Identify the stakeholders and their needs (Designer, Developer, Integrator,Administrator) Identify the useful views Establish the information sources Gather information Create the documentation package Review Views Logical - Defines the typology of building blocks and how they are related Decomposition - Defines the required building blocks for each logical layer Implementation – Provides guidelines for the most significant implementationissues Technological – Clarify the role of the technological baseline (IWT andSharePoint) with respect to the overall architecture Integration - Defines interaction and communication patterns amongARISTOTELE components, SharePoint components, IWT components andlegacy applications Deployment – Provides guidance for the platform deploymentDefinition of the High Level ArchitectureDocumentation (2/2)23SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  24. 24. ArchitectureDesignMIKE 2.0SemanticEnterpriseEnterprise 2.0High LevelArchitectureSoftwareArchitectureDocumentationViews & BeyondHigh levelsystem overviewUserRequirementsBusinessProcessPatternsArchitecturaldriversARISTOTELE Architecture designSAFEArchitecture
  25. 25.  Input User Requirements Business Process Patterns: to describe how ARISTOTELE supports themembers of the organization From High Level Architecture: Architectural drivers Views&Beyond approach for the documentation of the architecture A first high level system overview From MIKE 2.0: SAFE Architecture: An architecture for the Federated Enterprise (Methodologyfor the definition of the architecture, SOA pattern adoption) Semantic Enterprise: provides a layer for the enterprise to establish coherence,consistency, and interoperability across its information assets Enterprise 2.0: brings the collaborative and social computing conceptsassociated with Web 2.0 into the Enterprise Output: Software Architecture DocumentationARISTOTELE Architecture design
  26. 26. ARISTOTELE Architecture Logical viewDataDataTools PWLE LEG HRM CN KMServicesCore ServicesOrchestration ServicesBase ServicesContent Data Semantic DataService BrokerRecommenderSystemEnterprise LinkedData LayerKnowledgeManagementLink DiscoverySharePoint IWTExternal orLegacy Triple StoreSharePointServicesIWTServicesCompetenceGapTag SuggestionExpert FindingWorkerCompetenceUpdateRelevanceCalculationTeam BuildingLearningExperience
  27. 27. Semantic Layer high level architecure27SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  28. 28. Enterprise Liked Data Layer2828SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012
  29. 29. Available tools29
  30. 30. Available tools30
  31. 31.  Web site: http://www-aristotele-eu.org Follow us on twitter: (@Aristotele_ip) URL:http://twitter.com/#!/Aristotele_ip LinkedIn: ID Group - ARISTOTELE Facebook: ARISTOTELE ProjectARISTOTELE references31Thank you very muchfor your attention andstay tuned!SOA-KME Workshop @ CISIS 2012Palermo 4th-6th, 2012

×