1 / 20

MOGENTES 3 rd and Final Review Reporting Period January 2010 – March 2011 Cologne, 26 May 2011

MOGENTES 3 rd and Final Review Reporting Period January 2010 – March 2011 Cologne, 26 May 2011. WP8 – Dissemination and Exploitation Erwin Schoitsch, AIT. T 8.1 Dissemination - Objectives. to provide widespread access to the ideas and basic results of the MOGENTES project,

edward
Download Presentation

MOGENTES 3 rd and Final Review Reporting Period January 2010 – March 2011 Cologne, 26 May 2011

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. MOGENTES 3rd and Final ReviewReporting Period January 2010 – March 2011 Cologne, 26 May 2011 WP8 – Dissemination and Exploitation Erwin Schoitsch, AIT

  2. T 8.1 Dissemination - Objectives • to provide widespread access to the ideas and basic results of the MOGENTES project, • to promote usage of formal methods and model-based approaches in validation of dependable embedded systems, to create awareness and facilitate exploitation, • to disseminate knowledge to technical/scientific audience and – as appropriate – to the general press and public, • to keep close contacts and maintain mutual co-operation with the European Technology Platforms EPoSS and Artemis with respect to technology aspects. • Links to related WG (ERCIM, EWICS, national computer associations, …) and conference organizations (SAFECOMP, Formal Methods such as FMCO)

  3. T 8.2 Exploitation - Objectives • to aid the early creation and adoption of products or industrial applications based on the project’s results, • Industrial partners: to implement the experiences and results of the project within their processes for development and V&V • Tool developers: Extension of their portfolio (e.g. extend and qualify iLock tool suite (PROV)), strategies for tool qualification (D 8.5) • Research centers: technology transfer, consultancy • Universities: to integrate results in research work, lectures, lab exercises and diploma/PhD thesis

  4. T 8.3 Standardization - Objectives • to foster consideration of project results in related standardisation activities (influence standardization, esp. functional safety and communications (ISOBus)) • to take care of fitting project results into the frame work of functional safety standards conformance, • to keep close contacts and maintain mutual co-operation with the European Technology Platforms EPoSS and Artemis wrt. to standardization. • Co-operation with (pre-)standardization groups (EWICS TC7), and with standards bodies like CEN, ETSI, ISO, IEC, AUTOSAR consortium (e.g. conformance testing of middleware)

  5. Progress – Deliverables and Milestones Deliverables 3rd Year + extension: T 8.1 Dissemination: • D 8.3c Dissemination report (M39) T 8.2 Exploitation: • D 8.4e: Bi-annual Exploitation Plan (evolving document) M30 • D 8.4f: Final Exploitation Report (M39) T 8.3 Standardization: included in Exploitation Reports, co-operation with FP7 Support Action ProSE; IEC 61508, ISO 26262; ETSI MTS/MBT contacts; MBT/TCG rated high in ProSE experts survey!! T 8.4 IP Management: see Final Reports, no specific measures required Milestones: • M30 External presentation (at Month 30): • – MOGENTES hasbeencommunicatedtothegeneralpublic (press release) • – MOGENTES hasbeenpresentedatat least 2 industrialfairsorconferences(overfulfilled: CPS week, ICT 2010, SAFECOMP 2010, etc., see D 8.3c, done)      

  6. Progress – Updated Dissemination Material • MOGENTES Flyer (fact sheet), updated • Final Press release • MOGENTES Poster updated (DATE 2010, CPS week 2010, ICT 2010, ME10, ...) • Web site: Maintenance continued • (publications, public deliverables)

  7. MOGENTES Workshop at SAFECOMP 2010, Vienna (Sept. 2010) ERCIM/DECOS/MOGENTES - Dependable Embedded Systems: Model-based Design and Validation (Automated Test Case Generation) • Morning Session: • 11:45 – 12:15 Exploitation of Embedded Systems Research Results via Standardization– a path towards business (Erwin Schoitsch, AIT, Austria) • Afternoon Session: 14:00 – 17:30 • The afternoon session is dedicated to papers on “Validation and Verification”, presenting the results of the European FP7 project MOGENTES (Model Based Generation of Efficient Tests for Dependable Systems, contract no. 216679), planned presentations are: • 14:00 – 14:30 MOGENTES Overview (W. Herzner, AIT) • 14:30 - 15:00 Modelling and Mutation Testing (UML) (R. Schlick, AIT) • 15:00 – 15:30 Automated Test Case Generation (Harald Brandl, TU Graz) • 15:30 – 16:00 Tool Integration and (Balázs Polgár, András Pataricza, Imre Kocsis, Budapest University of Technology and Economics) • 16:00 – 16:30 Coffee Break • 16:30 – 16:30 Model based Fault Injection Tool (MIFI, MODIFI) (SP Research Institute of Sweden) • 16:30 – 17:00 Qualitative Fault Modelling (András Kövi, Budapest University of Technology and Economics) • 17:00 – 17:30 Plenary discussion, concluding remarks

  8. ICT 2010, MOGENTES Demonstrator (Re:Lab, AIT)

  9. Progress – Conferences, Workshops, Papers(2010, 2011) • 35 papers in Journals or Proceedings • ~ 25 presentations or talks on MOGENTES or including MOGENTES as example (e.g. Open ProSE Workshop, Safecomp Workshop, SMT workshops) • 4 Workshops (co-) organized including MOGENTES topics and presentations, FMCO Graz 2010 • ~ 25 events distribution of flyers or info (e.g. IDIMT, DATE 2010, Artemis and EPoSS events) (6 exhibitions) • Lectures and courses: ETH (at Oxford Univ.), BME, TU Graz, AIT (FH Joanneum, TTZ) • 10 PhD or Master Theses on related subjects: BME, ETH, TUG • 5 Bachelor Theses (BME)

  10. Exploitation - structure of document Concept of evolving report: missing input to complete, plans will become more concrete and detailed each time!! (tables, chapters) – template includes already all chapters/subchapters for expected input of final report! 2MOGENTES: Industrial Expectations, Economic and Strategic Impact 2.1Reinforcing Competitiveness 2.2Impact on Major Industrial Domains 2.2.1Automotive Sector 2.2.2Railway Sector 2.2.3Off-highway Vehicles Sector (Farm and Construction) 2.2.4Tool Sector 2.2.5Research and University Sector 3 Exploitation of Results by Partners 3.1Industrial Exploitation Plans … subchapter for each partner … 3.2Research and Academic Exploitation Plans … subchapter for each partner … 4 Standardization: Plans and Activities

  11. Exploitation – structure of document 5Exploitable Results 5.1General Aspects of Exploitation of MOGENTES Results 5.1.1 Template for Overall Expected Benefits 5.2First (Preliminary) Assessment of Exploitable Knowledge and Results: 5.2.1 Collective List of Exploitable Results (Items, Tools, Methods, … ) 5.2.2 Overview table on Exploitable Knowledge 5.2.3 Exploitation of Knowledge (Intangible Assets): 5.3Results to be collected from Partners (for Evaluation and Creation of Overall Exploitation Matrix) (detailed 2nd Assessment) 5.3.1 Template for Analysis of Exploitable MOGENTES Parts 6 Academic Exploitation: Education, Training, Diss. 6.1Overview over Dissemination, Education and Training Goals and Activities 6.2Lectures and Courses, Lab Exercises and Students Exchange 6.2.1 Lectures and Courses 6.2.2 Students’ Exchange, Lab Exercises (“Practica”) 6.3List of Bachelor, Master and PhD Theses

  12. Exploitation by partners – example chapter 3 3.2.3 ETH/Oxford exploitation of MOGENTES developments • A core-component of the MOGENTES test-vector generator is used in a research project funded by Toyota (software for cars). Toyota funds an extension to fit their needs (patent for these extensions is about to be filed). • Intel Research Haifa is using the symbolic execution engine that was improved and enhanced in MOGENTES to validate power requirements of the interplay of Intel CPUs and an Intel chipset (Intel funds ETH/Oxford for this work). • ARTEMIS CESAR project (largest ARTEMIS project, ARTEMIS Reference Technology Platform): the MOGENTES test-vector generator for Simulink is used (will be evaluated by the industrial partners (Airbus and others)). • Jasper Design Automation has licensed the symbolic execution engine from ETH for generating test-vectors from SystemC models. • IBM UK is evaluating a test-vector generator version for concurrent code. • TATA: test vector generation tool based on MOGENTES marketed (users e.g. Hyundai). • GM: uses internally the test vector generation tool based on MOGENTES.

  13. Collective List of Exploitable Results/Knowledge Table 5-1 "List of exploitable MOGENTES items" – current status: • 12 tools, e,g. • Argus/Ulysses: TCG from action systems (AS) • COVER: TCG from Simulink models using CBMC • MODIFI: model-implemented fault injection • Prover iLock: TCG based on minimal cut sets • Several model transformation tools • Mutation-generation of UML models, fault-based TCG from UML models • 5 methodologies, e.g. • Action Systems as intermediate models for test case generation, • Model transformation • Model-based integration of tools • 10 application / domain specific results • Application of exploitable items in railway and automotive domain, e.g.in compliance with functional safety requirements (i.e. ISO 26262) or reusing UML profile for railway signalling , test case interpreter, formal model of ELEKTRA Table 5-2 Overview of “Exploitable results” (clustered groups of exploitable knowledge) - knowledge behind results (base for IP) • 12 entries, e.g. • Formal requirements specification using UML/OCL, ontology based verification of UML models • Qualitative Action Systems • Model-implemented fault injection • Mutation generation of UML models

  14. Analysis of Exploitable MOGENTES Parts: Table 5.3 • Template given in table 5.3 • Name of item • Responsible partner • Short description (5-10 lines) • Other involved partners • Market opportunities • Product maturity • Status of plans for sustainable customization/maintenance/further development • Final status of entries: • UML/(oo)AS-based TCG (TUG, AIT) • UML Rail Signalling model (AIT, TRSS) • Model based integration of tools (BME) • Ontology based verification of UML models (BME) • UML + UPPAAL based test case generation (BME) • IOCO checker for Action Systems (TUG) • MODIFI (SP) • Modelling UML/statechart/OCL/AGSL to TCG (PROL) • Model-based development and verification (QA plan) (PROL) • Prover iLock-related new components developed within MOGENTES (PROV)

  15. Example (1)

  16. Example (2)

  17. T 8.3 Standardization – Results and Contributions • IEC 61508 (AIT, SP) Int. Standard since April 2010 • inclusion of MBT (Model-based Testing) – see examples from last review!! • ISO 11783 (ISOBUS) (Re:Lab)ISO 25119 (Safety-related parts of control systems for agriculture and forestry machinery) • active in standardisation work: RELAB • ISO 26262 • active in standardisation work: AIT, FFA, SP • EN50126, 128, 129 railway functional safety standards • active in maintenance process: TRSS • using: PROLAN, Prover (ProveriLock Tool qualification) • AUTOSAR • active member: FFA • SMT-Lib (formal methods standard) • ETH submitted proposal for theory for sets, lists and maps, and • Floating Point Arithmetic • Further standardisation activities (AIT): • IEC 61511 (currently active), IEC 61131, IEC 62443, IEC 61784-4, IEC 62061 (SP) • ProSE, EWICS TC7, CEN • ETSI contacts: TC MTS/MBT (Methods for Test Specification), ETSI Testing Group

  18. Functional Safety Std. ISO/DIS 26262, Part 6(Product Development, Software level) Proposal AT (under review): Table 13 – Methods for deriving test cases for software unit testing Table 16 - Methods for deriving test cases for software integration testing: Current methods: ASIL A B C D 1a Analysis of requirements ++ ++ ++ ++ 1b Generation and anlysis of equivalence classes + ++ ++ ++ 1c Analysis of boundary values + ++ ++ ++ 1d Error Guessing + + + + 1e Model based testing d + ++ ++ ++ d Model based testing is the automatic generation of efficient test procedures/vectors using models of system requirements and specified functionality (SoftwareTech July 2009, Vol. 12, No. 2. http://wwww.goldpractices.com/practices/mbt/ ) Secretariat observation (review): Open: Too detailed a method? See US-59

  19. Functional Safety Std. ISO/DIS 26262, Part 6(Product Development, Software level) Secretariat observation (review): Open: Too detailed a method? See US-59 – therefore unfortunately rejected. (although “error guessing” is still in this list....  ) Finally, in ISO 26262-6, Annex B on model-based development, model-based testing and test case generation is mentioned as: Model based development: • “Verification activities can also be treated differently since models can be used as a useful source of information for the testing process (e.g. model-based testing), or can serve as the object to be verified. The seamless utilization of models facilitates highly consistent and efficient development.” Current Status: Part 1-9 FDIS voting (27.6.2011), Part 10.2 commenting phase finished (AT input repeated).

  20. Thank you for your kind attention

More Related