1 / 9

Dynamic Requirements Definition System Interoperability Issues Mapping Nicolas Figay, EADS

ATHENA M30 Intermediate Audit 4.-5. October 2006 Brussels, Belgium. Dynamic Requirements Definition System Interoperability Issues Mapping Nicolas Figay, EADS. Presentation Outline. DRDS Objective DRDS functionalities DRDS Achievements Objective of the Mapping Approach

karsen
Download Presentation

Dynamic Requirements Definition System Interoperability Issues Mapping Nicolas Figay, EADS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ATHENA M30 Intermediate Audit 4.-5. October 2006 Brussels, Belgium Dynamic Requirements Definition System Interoperability Issues Mapping Nicolas Figay, EADS

  2. Presentation Outline • DRDS Objective • DRDS functionalities • DRDS Achievements • Objective of the Mapping Approach • Mapping Approach Overview • Mapping Approach Implementation • Relation between DRDS & Mapping Approach

  3. DRDS Objectives • According to D.B4.4

  4. DRDS Functionalities • Refer to the functionalities of DRDS that support the objectives

  5. DRDS Achievements • State major achievements • E.g Number of requirements • Lessons learned

  6. Mapping Approach Objectives Mapping approach was developed in order to: • Track the specific solutions that are used to solve specific needs and requirements defined in the Business Scenarios • To filter this correspondence through a level of abstraction (generic needs/issues against generic solution) in order to: • allow factorization of common needs coming from different sectors (Aerospace, Telecom, Furniture, Automotive…) or family of application (SCM, e-Procurement, PLM, Portfolio Management…) • apply gain know-how during ATHENA through the AIF (generic solutions and needs are structured by the AIF) • Obtain a knowledge base that will allow to continuously improve efficiency of AIF and associated methodology through analysis

  7. Mapping Approach Overview Specific Requirements B4 Specific Solutions Ax Projects Generalisation Generalisation Interoperability Issues B4 A4 Contextualized Issues and Solutions ATHENA Generic Solution A4B5 Contextualisation Contextualisation Context Elements (from A4) Mapped issues and solutions are those belonging to the same contexts or set of contexts. Several analysis viewpoints may exist, related to set of context.

  8. Mapping Approach Realisation • A knowledge model was created in OWL, using the Protégé editor: • Federation of heterogeneous information coming from ATHENA • No development • Commercial or proprietary tools independent • Potential usage of advanced querying or reasoning on the WEB • Contextualisation • Identification of context elements coming from the different projects (e.g. phases of Interoperability project methodology from A4) • Creation of “contextualised_element” class allowing to associate any contextualised element to the context by means of properties • Contextualisation of solutions and issues by dynamic typing of individuals • Elaboration of set of queries (in SPARQL) to analyse: • Quality of contextualisation • Accuracy of context elements usage to improve interoperability and speed up collaboration through successive analysis campaign

  9. DRDS & Mapping Approach • DRDS application • operational tool allowing to enter, classify and manage the requirements • on the WEB, for numerous users (robust, scalable) • Mapping approach • Establishment of relationships with information that are not within the DRDS , through context elements that are under continuous development and evaluation within ATHENA • It was not appropriate to extend the DRDS • A utility will be used in order to export the content of the DRDS as RDF-XML file that will be integrated in the knowledge base • Knowledge based was designed in order to allow such an approach

More Related