1 / 16

Process Modeling Tool (PMT) Very Short Overview

Validas AG offers innovative solutions for tool qualification and process modeling in software engineering, supporting compliance with safety standards. The Process Modeling Tool formalizes and improves processes, ensuring safety and documenting compliance with standards. It generates reports, plans, and validation actions, making safety easier and safer. The tool has been used to certify Validas qualification processes and will soon be open source.

robertswilliams
Download Presentation

Process Modeling Tool (PMT) Very Short Overview

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. Oscar Slotosch, Validas AG Process Modeling Tool (PMT)Very Short Overview

  2. Validas AG About Us • We are a technology consultancy for quality assurance of embedded systems • Our core competences are model- based development, model-based testing, test automation, tool qualification • We develop innovative software engineering methods, implement them in form of tools and processes and we support our customers in their application.

  3. Portfolio and History Tool qualificationsince2006 Model-based Test since2001 Tool testsince2007 Qualification Kits fortools/librariessince2012/15 Tool Chain Analysis since2010 Validas AG

  4. Validas Topics Neuronal Nets

  5. Qualification Kit Qualification Processes Tool 5 • Standards (ISO 26262, IEC 61508, DO 178, EN 50128) require a safe usage of all SW development tools & libraries • Tool classification • Critical tools: Qualification • Safe Usage • We consider the following processes • Tool Chain Analysis • Qualification Kit Creation • Tool Qualification Tool Chain Analysis Tool 5 Application Developer with TCA Application Developer with QST ToolSafetyManual Library 1 Library 2 Library 2 Library 4 Library 5 Library 5 Library 5 Tool/ LibraryQualification Report Tool Qualification Templates Pot. Errors Tests Guidelines Tool / LibraryProvider with TCA Model Manual Qualification Kit

  6. Motivation: (QKit-)Compliances • Function-Specifications • Potential Errors • Known Bugs • Code-Coverage (ALL ASIL) • Architecture • Programming Guidelines • Tool Qualification Reports • Many Tests / TAU • … SWC Qualification Kit:(6-SEOOC Compliant) • Function-Specifications • Potential Errors • Known Bugs • Code-Coverage (ASIL D) • negative Tests / TAU • … SWC Qualification Kit:(8-12 Compliant) • Feature-Specifications • Potential Errors • Known Bugs • Mitigations • Requirements Tests / TAU • … Tool Qualification Kit:(8-11 Compliant) similar structures: development processes

  7. Goals of Process Modeling Tool Goals: Making Safety Easier & Safer • Formalize & improve processes • Show compliance with safety standards (Safety Plan) • Support achieving compliance (Safety Case) • Document processes Features: • Model processes (with BPMB like visualization) • Validate processes (syntactically) for consistency and completeness • Generate process & compliance reports • Generate Verification & Validation Plans (for separate VVT) • Can be used for modelling of model-based processes • Has been used to certify Validas qualification processes • Will be open source soon

  8. Process Modeling Tool PMT Model-Based Process Link Requirementsto Processes and Verification Actions Formalize Tailor Parameters QKit PMT ISO 26262, IEC 61508, .. Formalize ParameterValues Generate Generate Generate VVT ProcessDescription VerificationValidationPlan VerificationValidationReport Project: V&V Compliance Report Safety Case Safety Plan

  9. Graphical Notation Elements • Process Module: blue, rounded box: • Verification Module: green, rounded box: • Hierarchical Process Module: blue folders: • Hierarchical Verification Module: green folders: • Artifact: Grey box with note: • Model: Orange box with note: • StakeHolder: transparent box: • Conditions: yellow routes: Relations • Before After: solid arrow: • Read/Write: dashed arrow: • Artifact Containment: dotted arrow: Default • Start & End

  10. Process Example

  11. Example Compliane Argumentation • We use Test Generators that have to generate complete test case • We check this during V&V

  12. Verification and Validation Model • V&V Model documents Verification and Validation (for all instances of the parameters) • V&V Model is basis for Verification and Validation Tool (VVT) • VVT Model is generated from PMT (based on Process and Planning parameters) • Meta Model of VVT:

  13. Example: Corresponding Checklist

  14. Summary • Model-based process makes safety more safe • Safety plans & safety cases • PMT Prototype • Model processes with Parameters for Variants • Compliance Document Generators • VVT Prototype • Verification and Validation / check list generation is key for compliance • V&V report generation • Approach has been applied to certify Validas tool qualification process • Meta-Process can for semantic check of processes • Approach is currently used for all Validas qualification processes • QKits for tools • Classification & qualification of tool chains • QKits for libraries • QKits for software

  15. Model for Parameterized and Compliant Model-Based Processes Process Requirement References Claimes Compliance StakeHolder Artifact Input ProcessModule Output Parameter References Instances Before / After References Binding Model MetaModel Mandatory Mandatory Optional Includes VerifcationModule Optional MetaModelAtribute Optional MetaModelElement Mandatory MetaModelAssociation

  16. Future? PMT = Project Management Tool • Process Modules & Artifacts have the following project states: • DEFINED: Initial State • READY: Inputs are available (and pre-ceeding tasks are done) • IN_PROGRESS: work started • DONE: work finished • Workflow: • DEFINED (initial) • READY (automatically determined by PMT) • DONE (set from user)

More Related