1 / 11

D1.2-Input / Tool Integr., Requ.Tracking

D1.2-Input / Tool Integr., Requ.Tracking. WP1-4 Interaction Meeting, Bor å s, June 2-3, 2008 ARC / BME. DECOS Test Bench (Requirements Tracking). Objectives Guides designers through the verification and validation (V&V) process

annick
Download Presentation

D1.2-Input / Tool Integr., Requ.Tracking

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. D1.2-Input / Tool Integr., Requ.Tracking WP1-4 Interaction Meeting, Borås, June 2-3, 2008 ARC / BME

  2. DECOS Test Bench (Requirements Tracking) Objectives • Guides designers through the verification and validation (V&V) process • Follows functional safety standards(like IEC 61508 and related sectoral standards, e.g. EN 50129, ISO WD 26262) • Defines a requirements driven workflow for generation of modular (component-based) safety cases • Helps in identifying and carrying out V&V activities • Provides validation plans (v-plans) to control the V&V process (traceability, completeness) for the various DECOS artefacts (architecture model, core/high level services, hardware, tools, applications) • Provides interfaces to external V&V capabilities (V&V methods, tools) • Collects the results of the V&V activities (evidence) for establishing safety cases and for reuse

  3. Test BenchManagement Data &DocumentsRepository Control Info(workflow,V&V tool spec.etc.) AUT (Artefact Under Test) V&V-Tools V&V-Tool Generic Test Bench – Ingredients On-line User Guidance Implemented in DOORS™ e.g. • ITEM (Hazard and Risk Analysis) • RACER (Formal Verification) • SCADE MTC (Simulation) • LDRA (Testing) • PROPANE (Fault Injection) • EMI Test Bench • Tools • Middleware • Hardware • Models • Applications

  4. V-Plan example

  5. Evidence Positive Results Conceptual Framework DECOS - Test Bench Framework Certification arguments Safety Case Validation Plan (V-Plan) DECOS artefact V&V Activities Requirements Standards Other sources(e.g. domain) Inconclusi-ve Results V&VMethods V&V Tools Negative Results Feedback to developer AUT incarnation External tools

  6. Safety Case Reporter • Inserting "Warrants" between requirements and selected tools (V&V activities)

  7. Safety Case Reporter – Listings (shortened)

  8. Tool Integration – MOGENTES objectives • Integration of new: • Modeling tools (e.g. fault models) • Test case generation tools • Test analysis tools • with (mostly existing): • Development process/tools • Modeling tools (e.g. Simulink) • Test environment • Test analysis tools

  9. R.C. tool 1 R.C. tool k . . . Requ.s Capture Requ.s Spec.(s) . . . Models (sys. faults, …) TCG tool 1 TCG tool m . . . TCG . . . Test cases Tool Integration Dimensions • "Black box" vs. "white box" • Black box: • no change to the tools • file exchange (+ workflow) • White box: • "bottom up" • tools are (at least partially) modified for directl interaction • Horizontal vs. vertical

  10. Tool integration aspects (1) • Artefact exchange (data interfaces for inputs and results) • Standards • Glue • Model transformations • Transport coupled with control • Control (invocation) • System calls • Remote procedure calls (COM, CORBA, SOAP) • Frameworks (ECLIPSE) • Extension mechanisms (API, script lang., plug-in)

  11. Tool integration aspects (2) • Workflow (process) • ad hoc • implicit • explicit • tools: • MQ series workflow,.. • User interaction (user interfaces) • creation/manipulation, configuration, result inspection • consistent look and feel/usage concepts • replace input/configuration with other tools output • (Back) Traceability • search corresponding elements • line number, model element, etc.

More Related