Présentation Interop GdR - lsis.orgE9sentation%20Interop... · • Approche technologique,...

123 Novembre 2007 InterOP – GdR MACS – Aix en Provence

INTEROPINTEROPInteroperability Research for

Networked Enterprise Applications and Software

Network of Excellence

- n° 508011 -

B. Vallespir


HistoriqueHistorique

Budget d’implantation

Integration40%

Imp. Services

20%

Software10%

Hardware10%

Misc.20%

L’interopérabilité, clé d’amélioration de la compétitivitédes entreprises


HistoriqueHistorique

• 2000 : Création par la Commission Européenne d’un groupe de travail sur le thème : Interoperability for Enterprise Applications

• 2002 (1er juin 2002 – 30 juin 2003) : Création d’un réseau thématique sous le 5ème PCRD : IDEAS « Interoperability Development for Enterprise Applications and Software –Roadmaps » (Leader : Université Bordeaux 1)


HistoriqueHistoriqueVolonté de l’UE de créer un Espace Européen de Recherche (EER) à travers le 6ème PCRD, enmettant en place de nouveaux instruments : les Réseaux d’Excellence (NoE) et les Projets Intégrés (IP).

Projet Intégré ATHENA (Advanced Technology for interoperability of Heterogeneous Enterprise Networks and their Applications, N°507849)

Réseau d’Excellence INTEROP (InteroperabilityResearch for NetworkedEnterprises Applications andSoftware, N°508011)

Deuxprojets


DDééfinition de lfinition de l’’InteropInteropéérabilitrabilitéé

Capacité d’un système ou d’un produit à travailler avec d’autres systèmes ou produits sans effort spécifique de

la part de l’utilisateur

Capacité d’un système ou d’un produit à travailler avec d’autres systèmes ou produits sans effort spécifique de

la part de l’utilisateur

Capacité d’un logiciel ou d’une application d’entreprise à

interagir avec d’autres

Capacité d’un logiciel ou d’une application d’entreprise à

interagir avec d’autres


ATHENA en ATHENA en brefbref

• Un des plus grands programmes de recherches IT financés par la commission européenne (15 M€, coût : 30M€)

• Objectif stratégique 2.3.1.9 : Networked Businesses andGovernments

• Objectif principal d’ATHENA : avoir un impact industriel

• Approche technologique, globale, guidée par les besoins utilisateurs

• Complétée par des activités de transfert économique et de construction d’une communauté


CR FIAT (IT)

EADS (FR)

INTRACOM (GR)

AIDIMA (ES)FHG/IPK (DE)

DFKI (DE)

SINTEF (NO)

ESI (ES)

LEKS/IASI-CNR (IT)

UNIV. BORDEAUX 1 (FR)

UNINOVA (PT)

IC FOCUS (UK)

SAP (DE)

IBM (UK)

SIEMENS (DE)

TXT (IT)

Gruppo FORMULA (IT)

GRAISOFT/ADELIOR (FR)

COMPUTAS (NO)

Fournisseurs

Recherche

Industrie

ATHENA ATHENA en en brefbref

Partenaires


Le projet INTEROPLe projet INTEROP

• Partenariat : • 47 institutions• 204 chercheurs permanents, 140 doctorants• 13 états-membres UE + Norvège et Confédération

Helvétique• Coordination : Université Bordeaux 1• Date de lancement : 1er novembre 2003• Durée : 36 (42) mois• Budget total : 12 M€• Contribution européenne : 6,5 M€


Le projet INTEROPLe projet INTEROP

INTEROP est le seul Réseau d’Excellence dans le domaine des technologies de l’information et de la communication pour les réseaux d’entreprises (ICT for Networked Enterprise)


eBusinesseBusiness dans le 6dans le 6èèmeme PCRDPCRDIN

TER

OP

VE-FORUM

ATHENA Mytreasury

SATINE

DBE Spider-win V-CES

ECOLEAD Crosswork CodesNet

Trustcom NoRest XBRL

Net

wor

k of

Exc

elle

nce

Integrated projects

Specific support action

STREP Coordination actions


Objectif dObjectif d’’INTEROPINTEROP

Créer un réseau européen de recherche dans le domaine de l’interopérabilité d’entreprise par l’intégration de trois domaines de recherche :

• Architectures et plateformes• Modélisation d’entreprise• Ontologie

Architectureset plateformes

Modélisation d’entreprise Ontologie

INTEROP


Objectif dObjectif d’’INTEROPINTEROP

• Architectures et technologies informatiques,définition des moyens informatiques et de communication pour l’interopérabilité (web services…),

• Modélisation d’entreprise, modélisation des organisations en réseaux afin d’établir les besoins et exigences en matière d’interopérabilité,

• Ontologie, définition de la sémantique nécessaire àassurer l’interopérabilité.


ActivitActivitéés et rs et réésultats attendussultats attendus

Création d’un laboratoire virtuel de recherche sur l’interopérabilité desapplications d’entreprises

Outils decollaboration

Activités derecherche Mobilité

Dissémination Mastereuropéen E-learning


M36Période 1 Période 2 Période 3

M24 M42

30/04/0701/11/03

2ème programme de travail


M0 M12

M171er programme de travail

R2R1Reviews R3 R4

LuxembourgPalma Berlin ValenceWS GenèveBologne

GA1GA GA3Bergen

GA4Nancy

R5 FinalR6remote

Bordeaux

GA2

Advisory AC1 AC2 AC3 AC4 AC5

PhasagePhasage


M36Période 1 Période 2 Période 3

M24 M42

M17


M0 M12

1er programme de travail

PhasagePhasage

• Intégration du réseau• Mobilité des chercheurs• Dissémination• Conférence ESA’05

• Laboratoire virtuel• Master européen• Conférence I-ESA• Coopération avec la Chine



WorkpackagesWorkpackages du 1du 1erer programmeprogramme

4 WPs 2 WPs

5 WPs 3 WPs

IntégrationManagement

Recherche Diffusion del’excellence


WorkpackagesWorkpackages

WP1 : Cartographie descompétences dans le réseauINTEROP

WP2 : Méthodes de travailet plate-forme pour lacollaboration et la dissémination

WP3 : Mobilité des chercheurs

WP4 : Méthodes d’intégration scientifique et évaluation

Intégration



WP5 : Structure unifiée de modélisation d’entreprise

WP6 : Principes de conception et de réalisation de l’Interopérabilité

WP7 : Génération de logicield’entreprise personnalisé

WP8 : Méthodologie pour l’intégrationdes composantes thématiques

WP9 : Nouvelles architectures etplates-formes pour l’interopérabilité

Recherche



WP10 : Formation à distance et diplômes européens

WP11 : Dissémination et communication

WP12 : Transfert de recherche vers les PME

Diffusion del’excellence



WP13 : ManagementStratégique

WP14 : ManagementOpérationnel

Management


WG: Laboratoire virtuel, modèle d’intégration et indicateurs de performance

Activités d’intégration

WP

1 : C

arte

de

com

péte

nces

WP

2 : P

late

form

eW

P3

: Mob

ilité

WP

G :

Glo

ssai

re

Diffusion de l’excellence

WP

10 :

Edu

catio

n

WP

11 :

Dis

sém

inat

ion/

Sta

ndar

disa

tion

Structure du 2Structure du 2èèmeme programmeprogramme

ME(DEM)

AP(DAP)

DomainesON (DO)

Dom

aine

inte

rope

rabi

lité

(DI)

Synchronisation de modèles

Morphismes des modèles

Alignement de BP, ME et IT

Interopérabilité dirigée par les modèles

Méthodes d’ingénierie et Besoins Utilisateurs

Enrichissement sémantique de la ME et A&P

Activités jointes de recherche

Confiance, sécurité et politiques

WP12 : Problem driven basis - SMEs/Industry


WG: Laboratoire virtuel, modèle d’intégration et indicateurs de performance

Activités d’intégration

WP

1 : C

arte

de

com

péte

nces

WP

2 : P

late

form

eW

P3

: Mob

ilité

WP

G :

Glo

ssai

re

Diffusion de l’excellence

WP

10 :

Edu

catio

n

WP

11 :

Dis

sém

inat

ion/

Sta

ndar

disa

tion

Structure du 3Structure du 3èèmeme programmeprogramme

ME(DEM)

AP(DAP)

DomainesON (DO)

Dom

aine

inte

rope

rabi

lité

(DI)

Synchronisation de modèles

Morphismes des modèles

Alignement de BP, ME et IT

Interopérabilité dirigée par les modèles

Méthodes d’ingénierie et Besoins Utilisateurs

Enrichissement sémantique de la ME et A&P

Activités jointes de recherche

Confiance, sécurité et politiques

WP12 : Problem driven basis - SMEs/Industry

TF Knowledge Integration

TF Vlab

TF Education & training


Carte de compCarte de compéétencestencesPT1

PT2

PT3

WP1 Knowledge map for Enterprise Modelling, Ontology, Architecture and Platform for interoperability researches inside INTEROP

Obj

ectif

s Etablir une carte de la recherche sur l’interopérabilité réalisée dans le NoE et donner des recommandations pour la restructuration de cette recherche

Tâch

es

1 : First state of the art of research on Interoperability in INTEROP2 : Elaboration of a Knowledge Map of researches in the NoE3 : Relationships, diagnostic and recommendations for NoE researches in the area of interoperability

Dél

ivra

bles D1.1 Knowledge map of research in interoperability in the INTEROP NoE (first version)

D1.2 Diagnostic of research inside INTEROP NoE and Recommendations to strengthen research efforts in interoperability (including updated framework, state of the art and knowledge map)

M9

M18

WP1 INTEROP knowledge map


Carte de compCarte de compéétencestencesObjectifs détaillés

To establish a first map of the research on interoperability performed by the NoE partners and to pose a first diagnostic in order to provide recommendations in order to do an initial restructuring of research activities in the NoE. Implied sub-objectives are:• To elaborate a state of the art on the current status and structure of research among the NoEpartners in fields needed for ensuring enterprise interoperability. In particular, the NoE partners will communicate the advancement of their work in the domains of Enterprise Modelling, Ontology, Architecture and Platform for interoperability concern. This will be done by listing related research elements (competences, research teams, projects and results).• To define a first unifying framework to be used to position these research elements in order to provide a map of the research in interoperability (in the NoE). • To elaborate a first Knowledge map which will allow to show :

- the complementarities of researches inside the NoE- the gaps among the partners.- the research domains to strengthen- the recommendations to give to the various partners


Plateforme collaborativePlateforme collaborativePT1

PT2

PT3

WP2 INTEROP method of work and Platform enabling collaboration, knowledge sharing and dissemination

Obj

ectif

s Analyser les méthodes de collaborations pour finir à Interop une approche commune et une plateforme pour le travail d’une équipe virtuelle

Tâch

es

1 : Collaboration methods of work and dissemination methods analysis2 : Platform architecture3 : Platform roll-out4 : Knowledge maintenance methods and domain ontology5 : Platform maintenance & improvements

Dél

ivra

bles D2.1 Collaboration methods of work and dissemination methods

D2.2 Knowledge maintenance methods and domain ontology

M6

M18

WP2 Platform management


Plateforme collaborativePlateforme collaborativeObjectifs détaillés

The objective of this work package is to analyse collaboration methods in order to provide INTEROP partners with a common approach and platform to virtual team working and communities of practice. Three main methods will be analysed: synchronous collaboration methods to allow topics discussion among geographically distributed researches; knowledge management approach and methods to allow semantic indexing, semantic search and knowledge navigation; long-distance training to allow knowledge dissemination. In order to have a comprehensive and standard knowledge maintenance approach, knowledge maintenance method will be devised; the knowledge map will be provide by the domain ontology defined at this stage.The results of this work package is to establish, customise (if needed), roll-out and maintain a platform based on a common repository which integrates a set of tools to enable real-time collaborative sessions (CSCW), to share knowledge (KM), and to provide training (e-Learning) for the entire duration of the network. Three key technologies will be merged to provide a seamlessly integrated environment that will support INTEROP partners during their activities and the dissemination of INTEROP results.


GlossaireGlossairePT1

PT2

PT3

WP10 Training activities by e-learning (for researchers and key staff)

Obj

ectif

s Développer un glossaire sur l’ensembles des thèmes d’Interop

Tâch

es

PT1. 1 : Preparation and dissemination of a Glossary on EM, Architecture & Platform and Ontologies

PT21 : Automatic Extraction of “Level-3” terms2 : Manual Selection of Level-1 and Level-2 terms3 : Validation of the “flat” list of Level 1-2-3 terms

Dél

ivra

bles D10.1 Interoperability GlossaryM12

WPG Glossary

4 : Automatic Extraction of definitions5 : Validation of definitions6 : Building and validating Structured Glossary (Taxonomy)7 : Build a Glossary Extraction Web Service

DG1 Interoperability Glossary Acquisition Procedure M21

DG2 Interoperability TaxonomyM24DG3 Glossary Acquisition Web Service ModuleM36


GlossaireGlossaireObjectifs détaillés (PT2)The main objective of WPG is to provide a structured interoperability glossary (a thesaurus) along with the tools and methods to use this glossary within the scope of several WPs and Task Groups. The glossary concepts will be used as metadata for information/data exchange, classification, and indexing. The WP will provide to the NoE partners with a shared description of the relevant interoperability concepts, and a set of glossary services, accessible trough the INTEROP collaborative platform.During the first year of the INTEROP project several Work-Packages ascertained the need of identifying a glossary of interoperability terms for a variety of tasks, e.g: • Building a knowledge map and classifying interoperability knowledge domains (WP1)• Classifying partner’s competences for the INTEROP mobility matrix (WP 3)• Providing a list of relevant domain topics and concepts for educational objectives (WP 10)More in general, indexing with a set of common meta-data the various deliverables, state of art, scientific papers and databases that are progressively made available on the INTEROP collaborative platform (WP2, WP4, WP7, WP8, WP9, WP11 and again WP10)In the INTEROP first year project plan only WP.10 included a sub-task explicitly concerned with the creation of a glossary of interoperability terms (WP 10.1).This task was conducted primarily by one partner, who made available a set of automatic procedures to extract an initial glossary from relevant interoperability documents and generic glossaries available through the Internet. A team of 6 INTEROP partners then revised and extended this initial glossary, leading to a final set of 378 interoperability terms and definitions.This glossary is indeed a good starting point, but further developments are needed, especially since the initial glossary was extracted having in mind the specific objectives of WP 10. Furthermore, tools and methods are needed to make accessible and to exploit the information available in the glossary, also in view of improving the document management capabilities of the INTEROP collaborative platform.Accordingly, it seems reasonable to foresee a specific work-package acting as a “glossary service” for all the WPs that need to use and exploit an interoperability glossary. Eventually, the glossary may evolve in an Interoperability Ontology, through an integrated effort with WP 8. In fact, building a glossary is a commonly adopted initial step in ontology building, along with the design of a formal model and a core set of general concepts and relations (Core Ontology).There are several benefits in creating a durable glossary-ontology activity:• Semantic unification: the glossary represents an informal, but shared view of relevant interoperability concepts. This activity will let interoperability semantics emerge naturally from applications and collaborative work.• Classification/ retrieval of INTEROP documents: glossary terms may be used as meta-data for indexing INTEROP documents and databases, to help manual and automatic retrieval and classification. • Integration of competences from Enterprise Modelling, Ontology and Platform & Architectures, since both the creation and use of a commonly agreed set of “basic”meanings will facilitate the identification of common competences.In addition to these “general” benefits, the creation of a common interoperability glossary will impact also on specific work-packages, as previously stated, however, specific timing constraints must be considered, since many WPs already started their activity. These timing constraints will be handled in two ways:The first is creating a “task force” to speed up at least the initial phases of the glossary acquisition procedure. The task force will include task-group leaders and selected partners from the involved WPs;The second is to include the results made available by the partners in the various WPs, chiefly in WP1 and WP 10, among the sources used to select the glossary term list. As already detailed in D.10, the glossary acquisition procedure is heavily based on the reuse of existing knowledge sources, therefore we will include all available partner’s results among such sources.


IntIntéégration de connaissancegration de connaissancePT1

PT2

PT3

Obj

ectif

s Gérer l’ensemble des supports à la gestion des connaissances

Tâch

es

1 : Coordination2 : Development and Implementation3 : Kmap Requirements,Data Collection and Diagnosis4 : Glossary, Taxonomy, Ontology5 : Management of Platform Evolution

Dél

ivra

bles DTFKI5.1 Knowledge maintenance methods and domain ontology

DTFKI5.2 Description on the final structure of the platform and the Knowledge maintenance method

M36

M42

TFKI Knowledge Integration


IntIntéégration de connaissancegration de connaissanceObjectifs détaillés

- To enhance the integration actions between the knowledge Map, Glossary, ontologies onto the platform.- To implement the first version of the KMap in three steps, including the establishment of a benchmark for platform performance, in time for the next review.- To form an implementation team, involving the suppliers of the KMap Software, where problems can reach timely resolution.- In parallel to continue the KMap data collection activity and to further enhance the completeness and quality of the KMap data and impact of the glossary work giving improved enquiry capability.- To discuss and define a future architecture of the INTEROP platform with a strategy for inclusion of heterogeneous software tools via an interoperable user interface. To realise a first implementation of this architecture by integrating the e-learning application developed with Moodleinto the INTEROP platform


MobilitMobilitééPT1

PT2

PT3

WP3 Roadmap for Researcher Mobility

Obj

ectif

s Mettre en œuvre un programme de séjours scientifiques

Tâch

es

1 : Identify scientific issues and partners for mobility2 : Create the conditions of mobility

Dél

ivra

bles D3.1 INTEROP mobility matrix

D3.2 Financial, administrative and social arrangementsM6

M18

WP3 Researcher Mobility

WP3 Researcher Mobility

D3.3 Mobility criteria and procedure version 3M24D3.4 Mobility programme resultsM30D3.5 Mobility programme resultsM42


MobilitMobilitééObjectifs détaillés

To set up a programme for scientific stays and create the conditions for researcher and doctoral students mobility within the INTEROP area. The roadmap obtained at the end of WP4 will then guide the systematic deployment of mobility from Month 18 to the end of the project and beyond.


IntIntéégration scientifiquegration scientifiquePT1

PT2

PT3

WP4 Method for Scientific Integration and Assessment

Obj

ectif

s Fournir une définition (modèle conceptuel) de l’intégration scientifique couvrant la circulation des idées, la diffusion des documents scientifiques et de la connaissance, etc

Tâch

es

1 : Defining Scientific Integration and validation of the definition2 : Making the (further) INTEROP NoE Workplans Model Enabled

Dél

ivra

bles D4.1 Scientific Integration Conceptual model and its application in INTEROP

D4.2 INTEROP NoE 2nd Workplan

M6

M11

WP4 Project modelling – Creation of Virtual Lab

TFVlab Task Force Virtual Lab creation and implementation


IntIntéégration scientifiquegration scientifiqueObjectifs détaillés

• To achieve a definition (conceptual model) of scientific integration (SI) (DSI), covering such topics as circulation of ideas, the diffusion of technical and scientific documents and knowledge, researchers mobility, knowledge deployment, and means through which researchers meet and exchange ideas ( workshops, tutorials, schools, seminars, conferences, and scientific exchanges and visits).• To validate the DSI in reference to:

- the pre-network and current operations regarding scientific integration (SI 0-measure/ SI AS-IS)- the INTEROP NOE workprogramme (= pre-method NOE “Life Cycle Objective” or SI TO-BE)- SI gap identification- To specify (“formalize”) SI gaps and assist the INTEROP NOE in positioning its various performance criteria w.r.t. to those gaps; in evaluating and fine-tuning, or revising, the performance criteria to better target SI gaps; in identifying integration gaps; and in prioritizing the network actions regarding the SI gaps.


EE--learninglearning et programme de formationet programme de formationPT1

PT2

PT3

WP10 Training activities by e-learning (for researchers and key staff)

Obj

ectif

s Développer des moyens de formation sur l’interopérabilité : master, tutorials, e-learning, bibliothèque virtuelle, etc.

Tâch

es

1 : Preparation and dissemination of a Glossary on EM, Architecture & Platform and Ontologies2 : To create a virtual Library (Interoperability Explicit Knowledge Repository-IEKR)3 : Creation of Tutorials (interactive courses on CDROM) on Interoperability4 : Creation of web courses about interoperability5 : Coordination of the creation of a European Master on Interoperability6 : Coordination of the creation of a European PhD Program on Interoperability

Dél

ivra

bles D10.1 Interoperability Glossary

D10.2 Interoperability Explicit Knowledge Repository-IEKR

M12

M18

WP10 Training activities by e-learning and education program on interoperability

TFET TaskForce Education and Training


EE--learninglearning et programme de formationet programme de formationObjectifs détaillés

• To spread the results of the network between its members (internal) and outside the network (external).• To develop training activities for internal and external researchers, PhD students and enterprises.• To coordinate the creation of a specialized Master on Enterprise Modelling, Architecture & Platform and Ontologies supported by e-learning methodologies. • To coordinate the creation of a graduate curriculum: a European PhD Program on Interoperability based on exchange of teachers between European Universities and e-learning methodologies.• To create a virtual Library of papers about interoperability (Interoperability Explicit Knowledge Repository-IEKR)• To build tutorials (interactive courses on CDROM) and courses on the web about interoperability.• To collect best practices applying interoperability.• To define glossaries on interoperability matters in order to unify semantics.

During the development of this WP many universities and research centres will put their research on interoperability in common, with the purpose of creating a European Educational Program on this matter. The virtual teaching should be supplemented with presence teaching to obtain the maximum benefits of the development of these actions. The distribution of the teaching among present and virtual will depend on the readiness of university professors' mobility.


DissDissééminationminationPT1

PT2

PT3

WP11 Dissemination and communication

Obj

ectif

s Structuration du réseau en terme de communication et définition d’une stratégie de dissémination

Tâch

es

1 : Set up, animate and govern the External Network2 : Prepare and hold 3 Workshops and a Conference3 : Co-operate with scientific organisations4 : Co-operate with standardisation bodies and industry standardisation initiatives

Dél

ivra

bles D11.1 Final plan for using and disseminating knowledge

D11.2 External Network Achievement, workshops and one International Conference Report, Scientific Collaboration and Standardisation Report

M9

M18

WP11 Dissemination, communication & standardisation


DissDissééminationminationObjectifs détaillés

- Structure the networked laboratory in term of communication and dissemination of results to an External Network in the European research community. This must lead in a first time in the elaboration of a plan for using and disseminating knowledge.- Increase awareness on technology for organisational interoperability with emphasis on Enterprise Modelling (EM), Architectures and Platforms (A&P) and Ontologies.- Define a common consortium strategy for the dissemination and evaluation of the results of the joint research - Identify and evaluate interoperability requirements of software applications with users and standardization bodies


Actions envers les Actions envers les PMEsPMEsPT1

PT2

PT3

WP12 Methodology to implement services and to develop take-up actions towards SMEs

Obj

ectif

s Développer une méthodologie pour implanter des services dans les PMEs

Tâch

es

1 : To develop the methodology by using experience of NoE members (AIDIMA, CIMMEDIA)2 : To determine the type of applications and to select four pilot test cases.3 : To perform the implementation in the four selected pilot cases and to produce four reports analysing the conditions of implementation4 : To compare and evaluate the results of the implementation and to present the results

Dél

ivra

bles D12.1 The methodology to implement services and to develop take up actions towards

SME’s

D12.2 Reports on the four implementations and on the possibility to generalise the methodology to develop take-up actions towards SME’s

M6

M18

WP12 Services/take-up towards SMEs


Actions envers les Actions envers les PMEsPMEsObjectifs détaillés

- To develop a methodology in order to implement services and to develop take up actions towards SME’s- To test the methodology in several test cases- To evaluate the results of the implementation


ModModéélisation dlisation d’’entreprise et UEMLentreprise et UEMLPT1

PT2

PT3

WP5 Common Enterprise Modelling Framework (CEMF)

Obj

ectif

s Développer UEML 2.0 et évaluer comment UEML 2.0 peut permettre la synchronisation de modèles d’entreprise distribués et hétérogènes

Tâch

es

1 : Definition of partners and harmonization points 2 : Selection of a set of languages to be integrated into UEML 1.x 3 : State of the art on languages4 : Analysis of integration of UEML 2.0 with Architectural & Ontological approaches & solutions5 : Analysis and structuring of approaches and use cases

Dél

ivra

bles

D5.1 UEML 2.0: the strategy, the meta-model, mappings, the positioning report and the requirement analysis report

M9

DEM Domain enterprise modelling and UEML: unifying for interoperability and integration

DEM1 M24 UEML 2.1DEM2 M36 Roadmap for UEMLDEM3 M36 Research direction in enterprise modelling for interoperability and integration


ModModéélisation dlisation d’’entreprise et UEMLentreprise et UEMLObjectifs détaillés

According to the first two main axis mentioned in JR1, the effort will be devoted on one hand to pursue the analysis of the modelling needs and to deliver the new UEML 2.0, a more complete UEML language and, on the other hand to evaluate how the UEML 2.0 can be used to support synchronisation of different distributed enterprise models. Specific short-term objectives are:1. to provide the UEML 2.0 based on (i) a requirement analysis (requirements issued from the UEML Project) following a refined requirement analysis method (first version issued from the UEML Project), and (ii) a selection of languages for enterprise modelling; 2. to report the state of the art in languages for representing (semantic) mappings between models;3. to propose a first positioning report for integrating the UEML 2.0 with Architectural and Ontological approaches and solutions;4. to analyse and to define objectives and requirements for synchronisation and interoperability of different distributed enterprise models.The objectives 1 to 3 will be pursued by two main teams TeamReq and TeamUEML working respectively on requirements and on the rest. This is important to guarantee some disjointedness between the two orthogonal points of view of who provides the needs and wishes, and who provides the solutions. The objective 4 will be pursued by another experienced team SynchTeam.


Synchronisation de modSynchronisation de modèèleslesPT1

PT2

PT3

WP5 Common Enterprise Modelling Framework (CEMF)

Obj

ectif

s Développer une approche pour permettre la synchronisation de modèles d’entreprise distribués

Tâch

es

1 : Definition of partners and harmonization points 2 : Selection of a set of languages to be integrated into UEML 1.x 3 : State of the art on languages4 : Analysis of integration of UEML 2.0 with Architectural & Ontological approaches & solutions5 : Analysis and structuring of approaches and use cases

Dél

ivra

bles D5.2 Description of objectives, requirements and scenarios for synchronisation of

different distributed enterprise models including benefits and gabsM18

TG1 SDDEM - Synchronization of models for Interoperability

DTG1.1 Report on Generic Approaches and SDDEM Life Cycle ModelM24DTG1.2 Report on Model based analysis across enterprisesM36


Synchronisation de modSynchronisation de modèèleslesObjectifs détaillés

According to the first two main axis mentioned in JR1, the effort will be devoted on one hand to pursue the analysis of the modelling needs and to deliver the new UEML 2.0, a more complete UEML language and, on the other hand to evaluate how the UEML 2.0 can be used to support synchronisation of different distributed enterprise models. Specific short-term objectives are:1. to provide the UEML 2.0 based on (i) a requirement analysis (requirements issued from the UEML Project) following a refined requirement analysis method (first version issued from the UEML Project), and (ii) a selection of languages for enterprise modelling; 2. to report the state of the art in languages for representing (semantic) mappings between models;3. to propose a first positioning report for integrating the UEML 2.0 with Architectural and Ontological approaches and solutions;4. to analyse and to define objectives and requirements for synchronisation and interoperability of different distributed enterprise models.The objectives 1 to 3 will be pursued by two main teams TeamReq and TeamUEML working respectively on requirements and on the rest. This is important to guarantee some disjointedness between the two orthogonal points of view of who provides the needs and wishes, and who provides the solutions. The objective 4 will be pursued by another experienced team SynchTeam.


Transformation de modTransformation de modèèlesles

PT2

PT3

Obj

ectif

s Présenter les méthodes et outils relatifs aux relations existant entre deux ou plusieurs spécifications de modèles éventuellement représentés par des langages différents.

Tâch

es

1 : Analyse the existing SoAs2 : Roadmap3 : MoMo project forum4 : MoMo Toolbox5 : Dissemination

Dél

ivra

bles DTG3.1 Problem Analysis and Roadmap

DTG3.2 Research Roadmap on Model Morphism in the context of application interoperability

M24

M36

TG3 MOMO – Models Morphisms


Transformation de modTransformation de modèèleslesObjectifs détaillés

With the term Model Morphisms we intend to indicate the methods and tools that address the relationships existing (but, generally, implicit) between two or more model specifications, which are possibly represented in distinct languages as well. Such relationships are indicated by different terms, such as mapping, merging, integration, transformation, fusion, composition and also abstraction and refinement. But these terms all have in common the idea that the objects to be taken into consideration are models and some relation(s) among them. Models are also of different nature, representing different aspects of the reality, and are formulated by using different model constructs, at a different degree of formalism.

These preliminary considerations already show the complexity of the matter. For this reason, TG3 has an ambitious objective to pursue, and the activities cannot be simply associated to a set of specific deliverables, they require the definition of a roadmap. Along this roadmap, we place a few short term objectives that are reasonably achievable in the remaining time of INTEROP. But we are aware of the complexity and significance of the whole area, and therefore we have the further objective, a sort of meta-objective, that is the heritage we intend to provide for the researchers that, after the ending of INTEROP will continue their activities in this field.

Specifically, the objective of this task group is to acquire a better understanding of TG3 in the perspective of interoperability by:• Producing a State-of-the-Art report (SoA) by performing an analysis of material already produced in other WPs of INTEROP in order to get a sound understanding of the challenge to design a roadmap on TG3 for the European Research Area and within INTEROP• Identifying further developments in the area of TG3• Testing and comparing technologies and development of a framework for TG3.• Dissemination through exchanges with other experts across WPs , TGs as well as external expertsThe work in this task group addresses basic topics which will support the work in other WP or TG due to the fact that model morphism is an often occurring pattern in interoperability problems. The work will be accompanied / concluded by at least one Workshop.


Architecture et plateformesArchitecture et plateformesPT1

PT2

PT3

Obj

ectif

s Coordonner les recherches et maintenir un état de l’art sur le domaine des architectures et plateformes informatiques

Tâch

es

1 : SoA2 : Contacts and relationships with other TGs3 : Knowledge base maintainance4 : Provision of tutorials and learning material5 : Support to the WP Glossary

Dél

ivra

bles

DAP1 Revised SOA reports and research coordination M1M24

DAP Architecture & platforms

6 : Coordination of research strategiesfor Interoperability architecture approaches

7 : Identification of future research challengesand opportunities

DAP2 Revised SOA reports and research coordination M2M36


Architecture et plateformesArchitecture et plateformesObjectifs détaillés (PT2)

The goal of this domain group is to focus on research coordination in the area of Architecture&Platforms and to continuously update the state of the art, but not to perform any research activities directly. Few research activities will be performed in the Domain activity. Any Architecture&Platform related research are being allocated to appropriate task groups. It is planned with one special A&P workshop/meeting in the next period, in addition to meetings during each of the jointly arranged INTEROP workshops and meetings.


GGéénnéération dration d’’applications personnalisapplications personnalisééesesPT1

PT2

PT3

WP7 Method and specification to generate customised Enterprise Software – first version

Obj

ectif

s Définir une méthode de spécification d’applications d’entreprise personnalisées sur la base d’approches existantes telle que MDA

Tâch

es

1 : State of the art of methods to derive IT specifications from models and of methods to develop IT specific components based on IT modelling2 : Definition of a systematic method to derive IT specifications from Enterprise or process models

Dél

ivra

bles D7.1 State of the art of methods to derive IT specifications from models and of methods

to develop IT specific components based on IT modelling

D7.2 Requirements and systematic method to derive IT specifications from enterprise models

M12

M18


GGéénnéération dration d’’applications personnalisapplications personnalisééesesObjectifs détaillés

- to establish an exhaustive state of the art of the empiric methods and techniques to derive IT specifications from Business Process models and from Enterprise models,- to establish a state of the art of existing methods and techniques to develop complete software tools and software modules based on IT modelling,- to contribute to the definition of a systematic method to derive IT specifications from enterprise and business process models.

This mapping from enterprise to system models, including use of ontologies will allow:- to understand how best utilise the various enterprise modelling research approaches for flexible mapping to system solutions and adaptative architectures,- to understand how to utilise the offerings from ontology research field for the architectural support of semantic interoperability,- to harmonise use of metamodelling, modelling and transformation tools,- to analyse common experiences with metamodelling and transformation techniques, such as the OMG Meta Object Facility and the XMI representation or similar, to try to harmonise and integrate the various tool offerings, and open source solutions of the partners,- to seek synergy with the various OMG MDA tools, of partners and open source, and their mappings and transformations from CIM (Computational Independent (Business) Models) to PIM (Platform Independent (System) Models) and to PSM (Platfom Specific (System) Models).


OntologiesOntologiesPT1

PT2

PT3

Obj

ectif

s Explorer les potentialités des techniques basées sur les ontologies pour traiter les problèmes d’interopérabilité

Tâch

es

a : Ontology languages and reasoning for interoperabilityb : Ontology management for interoperable systemsc : Ontology-based Search and Discovery of digital resourcesd : Practical impact of ontologies on ESA interoperability

Dél

ivra

bles

D8.2 Architecture alternatives and ontology based solutions aimed at supporting enterprise

M18

DO Domain Ontologies for Interoperability

DO1 M24 Basic Ontological solutions for InteroperabilityDO2 M36 Ontology-based methods for Interoperability

1 : Basic Ontological solutions for Interoperability2 : Ontology-based methods for interoperability3 : Dissemination

WP8 Ontology-based integration of Enterprise Modelling and Architecture & Platforms


OntologiesOntologiesObjectifs détaillés (PT2)

Ontologies represent a new technology with the purpose to improve electronic information organization, management, and understanding. An ontology is a conceptual information model that describes “the things that exist” in a domain (hence the name): concepts, properties, facts, rules and relationships. An ontology acts as a standardized reference model to support information integration and knowledge sharing. Hence, the role of ontologies is twofold: - they support human understanding and communication,- they, in machine-processable form, facilitate content-based access, communication and integration across different information systems. These roles are both achieved by explicating and formalizing the meaning, or semantics, of organization and enterprise application information resources. The aim of this WP is to explore the potentialities of Ontology-based techniques to tackle the problem of interoperability investigating the way such techniques can be joined together with the other two fundamental perspectives that constitute the claim of INTEROP (namely Enterprise Modeling and Architectures and Platforms).

Concretely in this new phase of the work we want to investigate:• the possibilities offered by ontologies to model dynamic, behavioral and service oriented aspects and related reasoning tasks and implementations• the issues emerging when dealing with a multiple ontology scenario from a theoretical and architectural point of view and the problem of ontology “evolution”• the techniques and tools for semantic query processing• the practical impact of the above point in supporting ESA interoperability


IntIntéégrationgrationPT1

PT2

PT3

WP8 Ontology-based integration of Enterprise Modelling and Architecture & Platforms

Obj

ectif

s Traiter l’interopérabilité suivant les points de vue ontologie, modélisation d’entreprise et architecture et plateformes

Tâch

es

1 : State of the art and state of the practice2 : Relationships between enterprise modelling, ontology management and supporting architectures

Dél

ivra

bles D8.1 State of the art and state of the practice including initial possible research

orientationsM12


IntIntéégrationgrationObjectifs détaillés

The aim of this work package is to tackle interoperability (i.e. connectivity and cooperation) jointly from the three perspectives that constitute the claim of the Interop NoE (namely, enterprise modelling, structured knowledge (or ontology), architecture and enabling technology) in order to:• Identify the mutual contributions and the expected benefits from joining the perspectives,• Quickly reach a common understanding, within the NoE, of the potential contributions of every perspective to the NoE objectives, and by the way speed up the integration within the NoE,• Identify to-day’s deficiencies and obstacles from and to the three perspectives.• Contribute to the lifting of the identified obstacles.

The expected results of this Work Package are mainly:• Enabling cross-fertilization of the three perspectives,• Exhibiting new fundamental research topics to be carried out in every perspective and in the joined perspectives with regard to the scientific objectives of the NoE,• Feeding the partners with research orientations within the integrated activities and the joint programme activities,• Elaborating a methodological framework for the integration of solutions coming from the three contributive perspectives to achieve effective and customizable interoperability.


Enrichissement sEnrichissement séémantiquemantiquePT1

PT2

PT3

Obj

ectif

s Améliorer l’interopérabilité grâce aux ontologies

Tâch

es

1 : Experimentation framework and case studies2 : Ontology for the case studies and the experimentation3 : Enterprise modeling and semantic enrichment

Dél

ivra

bles DTG4.1 A practical experiment on semantic enrichment in an homogeneous environment

DTG4.2 An experiment and an evaluation of semantic enrichment in heterogeneous environments

M24

M36

TG4 Semantic Enrichment of Enterprise Modeling, Architectures and Platforms


Enrichissement sEnrichissement séémantiquemantiqueObjectifs détaillés

This task group focuses on one of the claim of the INTEROP NoE: improve interoperability solutions and practices by “summing up”concepts and techniques coming from three domains (Enterprise Modelling, Ontology, Architecture and Platforms). Indeed, a large variety of concepts, techniques and tools are available to-day to build and manage ontologies (see, for instance those techniques, services and tools mentioned in the INTEROP deliverable D8.1) . This task group focuses on the use and the evaluation of the adequacy of these concepts, techniques, services and tools in the frame of a model-based approach of enterprise systems.

The aim of this activity is to:• Situate the needed types of ontology and the related services in the model-based view of enterprise systems (e.g. Ontology-guided modeling, Ontology and EM analysis for completeness and correctness, ontology for common interpretation of heterogeneous EM).• Evaluate the appropriateness (and the possible incompleteness) of these services from the EM level to the ICT level: do the existing services cover the needs? Are there any gaps and where are they situated?

A longer term objective is to contribute to the assessment of “to what extent ontologies and related services will improve the interoperability solutions and the processes to implement these solutions?”

Some questions that will drive the activity of this task group are:• What kind of ontologies can be defined and are suited for covering the whole spectrum of interoperability as addressed by INTEROP (i.e. from the business level to the ICT level)?• What kinds of semantic/ontology-based techniques and services can be developed or used to go through that spectrum (i) downward (i.e. from a model to its implementation) as well as (ii) upward (i.e. from existing systems to a model, especially to take into account legacies)?• How the availability of such ontologies and their related services can impact

- Enterprise modeling techniques and their supporting tools?- Enterprise models exchange, sharing and re-use (for instance, what is the role and the benefits of semantic annotation in these situations)?- The choice, the implementation and the re-use of interoperability solutions?


InteropInteropéérabilitrabilitééPT1

PT2

PT3

Obj

ectif

s Définir les concepts et principes génériques pour concevoir des solutions interopérables et rassembler les connaissances scientifiques sur l’interopérabilité issues des autres WP.

Tâch

es

1 : Conceptual approaches for interoperability2 : Enabling technologies for interoperability3 : Applicative approaches for interoperability

Dél

ivra

bles

DI1 Interoperability domain – Interoperability knowledge corpus – Progress reportM24

DI Domain interoperability

DI2 Interoperability domain – Interoperability knowledge corpus – Final reportM36

WP6 Design Principles for interoperability – Good practices and solutions

1 : Initial information exchange anddefinition of the method of work2 : Collection of existing good practicesand solutions relevant to interoperability3 : State of the art on existing knowntheories & paradigms

PT1 PT2

D6.1 Collection of existing good practices and solutions for interoperabilityD6.2 State of the art on relevant theories and paradigms for interoperability

M18

M18


InteropInteropéérabilitrabilitééObjectifs détaillés

PT1The problem statement is that existing software and applications were not designed to interoperate. However, we formulate the hypothesis that the interoperability of enterprise applications and software can be designed-in. Consequently, the objective of this research is to identify generic features, define generic principles and patterns to design interoperable solutions. These design principles and patterns are independent of technologies and methodologies, and apply across industry sectors.

PT2This workpackage aims at capturing scientific interoperability knowledge developed by other Joint Research WPs/TGs. The objective is to construct a basic knowledge corpus to establish the interoperability domain as a scientific discipline.Note that this workpackage is a domain WP and does not deal with specific interoperability problem solving. It aims at interacting with R&D task groups and workpackages; on the one hand to provide generic interoperability understanding to TGs/WPs, and on the other hand to capture generic interoperability solution components from TGs/WPs.


MDIMDIPT1

PT2

PT3

Obj

ectif

s Analyser et proposer des solutions pour une approche de l’interopérabilité dirigée par les modèles

Tâch

es

1 : Model establishment and system configuration2 : Model Driven Interoperability

Dél

ivra

bles DTG2.1 Report on Model establishment and system configuration

DTG2.2 Report on Model Driven Interoperability

M24

M36

TG2 MDI - Model Driven Interoperability


MDIMDIObjectifs détaillés

The aim of this Task Group is to analyse and propose solutions for MDI, Model Driven Interoperability. This focus idea came out of the initial work in WP7 – motivated by using the MDA/MDD approach to achieve interoperability. We have now coined the term MDI – Model Driven Interoperability – to emphasise on this, and the task group will focus on the necessary analysis and design to be able to realise this in practice. The task group will contribute to a method (principle and structure) to enable Interoperable Enterprise Software Applications (ESA) starting from the level of the Enterprise Model and using a model driven approach, combined with use of ontologies and semantic annotations. The work will incrementally analyse the 2 parts of MDI – Models, Interoperability and how to drive the Interoperability in 2 different tasks.

This approach will combine the most recent research results in the three domains: Enterprise Modelling, Ontology and Architecture & Platform – together with the domain of ESA (Enterprise Software Applications).

The need for Interoperability between Enterprise Software Applications appears in various situations:• introduction of a new type of ESA in the enterprise and connection with the existing one,• connection of ESA between several enterprises, • mergers of enterprises and integration of legacy software, and similar situations.

We recall that this topic was identified in the IDEAS Roadmap with a high priority.The task group will strongly focus on Integration Activities for the domains of Enterprise Modelling, Ontology and Architecture&Platforms – related to support the focus domain of Enterprise Software Applications;


AlignementAlignementPT1

PT2

PT3

Obj

ectif

s Proposer des outils pour analyser l’adéquation entre les aspects stratégiques et les infrastructures

Tâch

es

1 : Business model ontology2 : Mapping between business model, enterprise model, and application & platform (IS) model3 : Evolution of business models4 : Coordination of dissemination events5 : Coordination and project management

Dél

ivra

bles DTG5.1 Progress report on the comparison/mapping/evolution between business models

DTG5.2 Report on the proposed workshop and PhD course

M24

M35

TG5 Alignment of BP/EM and IT

DTG5.3 Final report on the comparison, mapping and evolution between modelsM36


AlignementAlignementObjectifs détaillés

The business/IT alignment aspects of interoperability problems are the focus of this new task group and its cluster of Interop partners.In line with the pioneering work of Henderson and Venkatraman, (1993), this project should address the « strategic fit » between the strategic or business aspects and the infrastructure components, in a business/IT alignment framework , using an “Ontology-based approach”. This research is based on the assumption that an explicit business model should help to align the business strategy, the “Enterprise Modelling” world (Organization infrastructure), and the “Architecture and Platform” world (IS infrastructure).

The link with the business view (called the economic model in some existing Interop documents) has been mentioned in some work packages of the previous plan but barely addressed until now. This task will focus of this issue, which is clearly at the intersection of “Enterprise Modelling”, “Architecture and Platform”, and “Ontology”. The integration with other work packages and other new task groups is evident.

This cluster emphasizes the business/IT alignment and IS integration dimensions, barely addressed but important in an interoperability context.


MMééthodesthodesPT1

PT2

PT3

Obj

ectif

s Fournir un ensemble de connaissances sur les services interopérables d’ingénierie des méthodes (method engineering)

Tâch

es

1 : Exploration of methods and method engineering approaches2 : Development of the INTEROP method repository3 : Feeding and using of the INTEROP method repository

Dél

ivra

bles DTG6.1 Exploration of Methods and Method Engineering Approaches

DTG6.2 INTEROP Method Repository

M24

M36

TG6 Methods, Requirements and Method Engineering for Interoperability


MMééthodesthodesObjectifs détaillés

The main objective of this task group is to develop and validate two alternative ways of providing a knowledge repository of interoperable Method Engineering services. The first alternative is best described as a systematic assembly-based method engineering approach for constructing methods supporting different interoperability issues. It requires systems engineering effort to integrate the methods as application system services. The second alternative uses the Model-configured, User-composed Services Platform (MUSP) approach as developed in the Athena A1 project. It requires the use of the MDCE platform, as developed and delivered from the Athena project, but will allow users to model-configure and compose their own method services without any systems engineering involvement.The project will combine many layers of knowledge, specifically: (1) Method Knowledge Level called Methods / Method Chunks for Interoperability and (2) Method Engineering Knowledge Level called Assembly-based Method Engineering Approach for Interoperability.

(1) Methods / Method Chunks for InteroperabilityThe main tangible result is a repository of method chunks or user-configured and user-composed aggregated methods (INTEROP method repository) supporting different interoperability issues in the domains of Enterprise Modelling (EM), Ontology (ONT) and Architecture & Platforms (A&P). The definition of these method chunks will be based on the work already realised by different WPs and in the Athena project. The following objectives will be pursued:• To analyse the use of methods in organisations and discover representative situation dealing with interoperability problems; • To make an inventory of methods proposed by the INTEROP community;• To define method chunks based on the methods proposed by industrial and public communities and to put them in the INTEROP method repository;• To identify cases /scenarios in order to illustrate situation assessment for different method chunks selection and assembly.

(2) Assembly-based Method Engineering Approach for InteroperabilityThe core aim of this theme is to provide a method engineering approach allowing the construction of situation-specific methods in the interoperability context by reusing method chunks from the INTEROP method repository. The objectives to achieve are the following:• To provide guidelines for method chunks definition; • To propose the architecture for the INTEROP method repository; • To elicit requirements for methods supporting interoperability issues and to identify the gap in relation to already existing methods.


Aspects non fonctionnelsAspects non fonctionnelsPT1

PT2

PT3

WP9 Model driven and dynamic, federated enterprise interoperability architectures and interoperability for non-functional aspects

Obj

ectif

s Prise en compte des aspects non fonctionnels de l’interopérabilité tels que sécurité, qualité de services, etc.

Tâch

esD

éliv

rabl

es D9.1 State-of-the art/research for Interoperability architecture approaches

D9.2 Coordinated research strategies for Interoperability architecture approaches, including collection of user-cases, requirements and experiences for interoperable systems

M9

M18


Aspects non fonctionnelsAspects non fonctionnelsObjectifs détaillés

• Investigate and understand the advantages and disadvantages of the various interoperability architectural approaches – to identify synergy and best of practice results• Coordinate the ongoing research for new adaptive and evolution-supporting architectures• Exchange user-cases, requirements and pilot/demonstrator experiences

- Interoperability for non-functional aspects of Interoperability architectures- Harmonise and integrate the partners results around interoperability for non-functional aspects and qualities such as:- Safety and Trust, Security, Quality of Service, …

Understand and evaluate the various architectural approaches that the partners are working on, in particular including the model-driven architecture approach, service-oriented approaches, peer-2-peer architectures, grid architectures and experiences from earlier component-based and message-oriented architectures. Identify advantages and disadvantages, and coordinate future research based on this. Harmonise and coordinate the partners ongoing and planned work on non-functional aspects of Interoperable systems. The initial focus is based on the partners existing work related to security, safety, trust, dependability and quality of service. As the partner’s research evolves, it is assumed that also other areas will be introduced.


Confiance / sConfiance / séécuritcuritééPT1

PT2

PT3

Obj

ectif

s Combler le manque de connaissance concernant les points stratégiques relatifs à la confiance et la sécurité des échanges

Tâch

es

1 : Roadmap2 : Topical tasks

Dél

ivra

bles DTG7.1 Roadmap report

DTG7.2 Report on the horizontal issues and Task Group final report including subtask research results following the five task group topics

M24

M36

TG7 Interoperability Challenges of Trust, Confidence/Security and Policies


Confiance / sConfiance / séécuritcuritééObjectifs détaillésSeveral key issues related to Interoperability stem from non-functional aspects. They are traditionally introduced for separation of concerns between the main behaviour of an enterprise (functionality) and the supporting technologies and issues causing alternation of the functional behaviour. Common examples of non-functional aspects include quality of service and security, business value, etc. These need to be carefully addressed from a business and strategic standpoint. They have a significant impact on corporate governance and compliance, and are, as a result, of strategic nature within the corporate environment. However, this impact requires us to take a step back and consider their functional implications, in particular considering Enterprise Modelling, Ontologies and Architectures & Platforms. This proposal aims to put right the lack of knowledge about how these strategic issues affect interoperability, and to create approaches and methodologies for their formalization, design, evolution and execution. This becomes all the more significant now that the general scenario of interoperation (e.g., agile, networked enterprises) spans many administrative and legal domains, involving collaborations which are often established in short lived, ad hoc, ways, within loosely coupled environments. Interoperability in this context needs to be studied and factored into designs from the beginning rather than “hard wired” through integration “patches”. In this context, the current proposal addresses a truly challenging interoperability issue.The Task Group proposes a two-phased approach. The first phase will be based on the work on non-functional aspects done in WP9, combined with the expertise of the project partners and their respective involvements in other relevant projects and research activities; it will define an initial framework. This will then be used in the second phase of the project to guide the creation of a new understanding of the identified topics.The project will forge links with other relevant projects such as the 6FP TRUSTCOM project. Project partners have already established links with the eContent programme INDICARE project (INformed DIalogue about Consumer Acceptability of DRM Solutions in Europe), which has expressed great interest in the INTEROP NoE and in interoperability issues. Where appropriate, existing links with key industry actors (Microsoft, InterTrust, ContentGuard, RightsCom,etc.) and standards organizations (ISO) will be used.The task group will address those issue of business and strategic interoperability knowledge and challenges identified by the task group members when considering the broader work on non-functional aspects. These issues cover an initial set of five main topics: (i) Trust and Trust Models, Reputation, Privacy; (ii) eContracting, contract knowledge management, business commitment monitoring and fulfilment, and the ontologies of contracts; (iii) Non-Functional Aspects, including generic supporting mechanisms, relating to Security (data/ontology, privacy in data mining, authentication, integrity, confidentiality, non-repudiation, etc.), Information Security, Quality of Service (QoS), Quality Attributes, Performance, Reliability and Availability; (iv) Digital Rights and Policy Management, Policy Frameworks, Compliance, regulatory environments and corporate governance; (v) Business Value, Alignment, Business processes, Risk Management and Asset Management.


16Bui

ldin

g E

urop

e

Présentation Interop GdR - lsis.orgE9sentation%20Interop... · • Approche technologique,...

Documents

Transcript of Présentation Interop GdR - lsis.orgE9sentation%20Interop... · • Approche technologique,...