1 / 8

WP4 Instantiation WP4 Status 25 September, 2013

WP4 Instantiation WP4 Status 25 September, 2013. WP 4 Objectives. Generic Models Processes Tools. Define a domain-independent procedure for instantiation Take the generic results from WP2 and WP3 Translate them to the industrial domains Enhance with domain-specific extensions

tanek
Download Presentation

WP4 Instantiation WP4 Status 25 September, 2013

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. WP4 Instantiation WP4 Status 25 September, 2013

  2. WP 4 Objectives Generic Models Processes Tools • Define a domain-independent procedure for instantiation • Take the generic results from WP2 and WP3 • Translate them to the industrial domains • Enhance with domain-specific extensions • Prepare guidelines for instantiation to ”other new domains” WP 2WP 3 Domain-specific Models Processes Tools WP4 Company-specific Models Processes Tools Implementation and use WP5

  3. Background of WP 4 Domain-specific Instantiation automotive aerospace railway cross-and-other ARP 4754 DO 178B/C DO 254 ISO 26262 EN 50 126 EN 50 128 EN 50 129 IEC 61508 … Generic results Generic Process Model Component Model, Contracts, V&V CAR CTF & Tools

  4. Guidelines and Process Model • Analyse steps taken in the instantiation process for automotive, aerospace and railway • Particular focus on cross-domain instantiation • Cross-domain defines commonalities and differences between standards as a reference to the „Generic“ part of the GPM • Define commonalities and differences in the domain-specific instantiation • Prepare guidelines for instantiation to new domains • E.g. robotics, industrial automation, healthcare

  5. Instantiation Component Model • Component-based approach • Generic component model comes from WP2.2 • Mapping of properties / attributes / contracts to relevant frameworks in the individual domains • Automotive: EAST-ADL, AUTOSAR , ... • Concepts available cover explicit safety properties, e.g. safety case, safety requirement, safety constraint, error model and hazard. • Aerospace: AADL, lwCCM, ... • Concepts such as performance, schedulability, and reliability can be modeled in thread components. • Application components have properties that specify timing requirements, further constraints can be modeled as component properties • Railway and Cross-Domain: CHESS / VERDE, CESAR, UML/MARTE

  6. Preparation of Instantiation CTF & CAR (for railway) • Tool Framework and artefact repository (M24) • Instantiation of WP3 CTF, CAR and Tools on the basis of the generic process model and/or component model • Utilization of instantiatied process model as a driver for the CTF (pSC: railway only) • Configuration of the tool framework with regards to the instantiation process model • Selection of railway-relevant tools • Demonstrator-specific toolset (e.g. coverage verification?) • Configuration and adaptation of this toolset

  7. Overview of current planning situation: Deliverables • D4.1.1 Review of specific safety requirements and software development practice for the automotive, construction equipment, avionics and railway domains finished M12 • D4.1.2 Modeling and methodology for reusing software in automotive, construction equipment, avionics and railway domains finished M21 • D4.1.3 Methodology integration for reusability of component in the automotive, construction equipment, avionics and railway domains, finished M27 • D4.3.1 Enhancements of the pSafeCer Tools Platform for the railway domain, finished M28 • D4.4.1 Review of specific safety requirements and software development practice and resulting guidelines for tools and methodology integration for reusability of component in other (and new) domainsfinished M25

  8. Partners involved

More Related