1 INTEROP WP1: Knowledge Map Michaël Petit (U. of Namur) January 19 th 2004 Updated description of tasks after INTEROP Kickoff Meeting, Bordeaux

2 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 WP1: First Map & recommendations Create DB and Encode RE DB of Research Elements (RE) Define Framework Unifying Framework Draw INTEROP Knowledge Map Diagnose First Map Orientation of research New collaborations M6 M9 D1.1 D1.2 M18 M12 M10 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)

3 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 WP1: Tasks planning M0M6M9M12M18 Task 1: Create DB and Encode Research Elements Task 2: Define first framework Task 3: Draw first INTEROP Knowledge Map Task 4: Refine framework and Update DB Task 5: Diagnose D1.1D1.2

4 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 1: Create DB and Encode Research Elements ( M1-M6) Task 1.1: Choose DB technology (M1-M2) –Database with web user interface? Task 1.2: Define structure of DB contents (M1-M2) –Kind of elements (projects, competencies, publications, …) and relations –Templates for elements (attributes) Task 1.3: Implement and test DB (M3-M5) Task 1.4: Describe and encode elements (M6)

5 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 1.1: Choose DB technology (M1-M2) Alternatives: –Database with web interface (SQL + script, XML files,…) –Template to be filled off-line Text editor (MS Word, Latex, …) XML schema –Both? DB + import of XML documents? –Others? Issues –Start quickly –Development cost –User friendliness –No loss of data –Concurrent access Proposed method –Write a short requirements document –Identify potential technologies –Choose & justify

6 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 1.2: Define structure of DB contents – M1-M2 (1) Kind of elements. E.g.: –Research teams and competencies –Official bodies (standard, industry,…) –Projects –Results: publications, software, … Cross-references. E.g.: –Results of projects –Existing collaborations between teams and/or official bodies Templates for elements (attributes). E.g.: –Projects: start and end date, URL, … –Publications: Authors, publication details, URL,… –…

7 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 1.2: Define structure of DB contents – M1-M2 (2) Define conceptual model –E.g. in UML Class diagram or Entity relationship diagram Issues –Simple to understand and fill

8 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 1.3: Implement and test DB (M3-M5) Transform conceptual model into operational system –Text editor template, XML schema, … ? –DB + web interface ? –Both + import ? Issues –Choice of tools software development (SDE) Template filling (XML Spy, …) –Sufficient server capacity

9 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 1.4: Describe and encode elements (M6) All INTEROP partners Avoid loss of data –Mechanisms for recovery Reuse existing databases? –Cut/paste

10 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 2: Define first framework (M1-M6) Task 2.1: Study existing frameworks (UEML, IDEAS,…) and collect input from partners and other WPs (M1-M3) Task 2.2: Define INTEROP framework, disseminate, get feedback (M4-M5) Task 2.3: Extend DB structure with framework and extend DB user interface to allow classification (M6)

11 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 2.1: example on input: the UEML framework (1) Dimensions –enterprise engineering world components –enterprise life-cycle –genericity –views Genericity Views Life-cycle Requirements Design Implementation Generic Partial Function Particular Information Resource Organization

12 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 2.1: example on input: the UEML framework (2) Enterprise Engineering World Components dimension

13 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 2.1: example on input: the IDEAS framework Classification of Architectures and platforms –Solution Management tools and procedures required to administer an enterprise system (role and policy management, monitoring and simulation) –Workplace Interaction interaction of the human user with the system (input, output, and navigation) –Application Logic functional computation carried out by enterprise system to achieve a business result –Process Logic logical flow in which the functional computation is carried out –Data Logic data required and produced by an enterprise application –Communication capabilities of an enterprise application to be connected with another enterprise application

14 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 2.2: Define first framework (M4-M5) Issues: –Cover EM, ontologies, Arch & platforms –Simple to undertstand and use –Multi-dimensional? –Reaching a consensus? Method: –Define the structure of the framework. E.g.: dimensions and "positions" Subsumption (classification) hierarchies Part-of hierarchies, … –Define contents of the framework (e.g. 3 dimensions and the "positions" on these dimensions) –Define conceptual model and link to research elements model (ERA, UML CD,…)

15 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 2.3: Extend DB structure and interface with framework (M7) Transform conceptual model (framework and links to REs) into operational system –Text editor template, XML schema –DB + web interface –Both + import? Issues –How to build a user interface for a complex classification scheme?

16 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 3: Draw first INTEROP Knowledge Map (M7-M9) Task 3.1: Classify research elements (RE) according to framework and encode classification in DB (M8) Task 3.2: Define and implement queries on RE DB (M7-M8) Task 3.3: Write deliverable D1.1 (use queries and summarise) (M8-M9)

17 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 3.1: Classify RE according to framework (M8) All partners Issues –Reuse of previously encoded data –Motivation of partners

18 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 3.3: Define and implement queries on RE DB (M7-M8) Examples: –Geographical repartition of teams –List and number of projects or teams addressing an area of the framework –List and number of research elements in one area –List and number of teams involved in standardisation bodies –…

19 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 4: Refine framework and Update DB (M9-M12) Task 4.1: Refine framework Task 4.2: Refine DB structure and refine queries Task 4.3: Encode new RE and update existing RE

20 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Task 5: Diagnose (M12-M18) Task 5.1: Analyse INTEROP Map (DB) and elaborate proposals for research reorganisation Task 5.2: Write deliverable D1.2 Task 5.3: Disseminate D1.2

22 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Coordination s –Official WP mailing list –Task force mailing lists? Coordination platform –Temporary solution? Quaterly progress reports –Meetings attended –Work done (by task) with results and man-month –Deviations Meetings Metrics Coordination with other WPs

23 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 WP1: Meetings planning M0: Nov. 03 M6: May 04 M9: Aug. 04 M12: Nov. 04 M18: May 05 Task 1: Create DB and Encode Research Elements Task 2: Define first framework Task 3: Draw first INTEROP Knowledge Map Task 4: Refine framework and Update DB Task 5: Diagnose D1.1 D1.2 Kick-off Coord. M5: April 04 M8: July 04 D1.1 + Task 4 planning Coord. and Final planning M16: March 05 Final activities

24 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 IA1: metrics # research elements in each domain # countries covered by the study # countries where at least one partner exists # answers for each kind of prospecting tools (questionnaires, web…) # research areas where research efforts were identified as uncoordinated, or redundant

25 WP1, INTEROP Kickoff, Bordeaux, 12/1/ 2004 Coordination with other WPs WP2 (platform): –Interop domain ontology –Share the Knowledge Map through the collab. plateform WP3 (mobility): –Provide info for mobility matrix WP4 (method for integration): –Model of AS-IS and TO-BE competences WP7 (generation of Sw from EM): –Relationships btw EM/Onto/A&P vs framework WP8 (ontology based-Integration) –Relationships btw EM/Onto/A&P vs framework –State of the art –Identify new topics WP10 (training) –Glossary –Similarity of KMap and teaching competencies of Universities WP11 (dissemination) –Identify bodies competent in interoperability –Disseminate INTEROP Knowledge Map