Using Model-Based Design in conformance with safety standards

Transcription

1 Using Model-Based Design in conformance with safety standards MATLAB EXPO 2014 Kristian Lindqvist Senior Engineer 2014 The MathWorks, Inc. 1

2 High-Integrity Applications Software-based systems that are designed and maintained such that they have a high probability of carrying out their intended function 2

3 Why are we here? I want to show: How can MathWorks tools help develop high-integrity systems? What are the standard requirements for using the tools? How can MathWorks simplify meeting standards? 3

4 How can MathWorks tools help develop high-integrity systems? 4

5 Reference Workflow Model-Based Design for High-Integrity Software Exemplary verification and validation process for safety-related software created using Model-Based Design 5

6 Reference Workflow Model-Based Design for High-Integrity Software Model Verification Detect design errors at design time 6

7 Verification by simulation Simulation / model testing (Simulink) Model coverage (Simulink V&V) Req. Mgmt. Int. (Simulink V&V) 7

8 Test Coverage Analysis for Models Simulation / model testing (Simulink) Model coverage (Simulink V&V) Req. Mgmt. Int. (Simulink V&V) Coverage from first simulation Coverage from second simulation Total coverage Decision coverage Condition coverage MC/DC Lookup table coverage Signal range coverage 8

9 Tracing Requirements Model Creating links between textual documents and model objects Simulation / model testing (Simulink) Model coverage (Simulink V&V) Req. Mgmt. Int. (Simulink V&V) 9

10 Model Static Review and Analysis High-Integrity Modeling Guidelines Checks Model standards checking (Simulink V&V) 10

11 High-Integrity Modeling Guidelines Checks Model Advisor checks to facilitate standard objectives at the model level 11

12 Reference Workflow Model-Based Design for High-Integrity Software Code Verification Gain confidence in the generated code 12

13 Code Verification in the context of ISO Processor In-the-Loop PIL test (Embedded Coder) 13

14 Code Verification in the context of ISO Prevention of unintended functionality Traceability matrix analysis (IEC Certification Kit) or Model vs. code coverage (third-party tool) 14

15 Traceability Matrix Generation Generate traceability information covering requirements, model elements, and generated code Req #1 Req #2 Req #3 Use Microsoft Excel to track, and annotate generated traceabilty matrices for your project Fulfill requirements to document traceability information and to demonstrate absence of unintended functionality >> iec.exporttracereport('model_name') 15

16 Example: Door Locking System Small realistic example System model Modular development Automation Artifacts creation 16

17 Reference Workflow Model-Based Design for High-Integrity Software Model standards checking (Simulink V&V) PIL test (Embedded Coder) Simulation / model testing (Simulink) Model coverage (Simulink V&V) Req. Mgmt. Int. (Simulink V&V) Traceability matrix analysis (IEC Certification Kit) or model vs. code coverage (third-party tool) Simulink/Stateflow Embedded Coder Third-party tool 17

18 Advanced Reference Workflow Additional Best Practices Model standards checking (Simulink V&V) Property Proving (Simulink Design Verifier) Simulation / model testing (Simulink) Model coverage (Simulink V&V) Req. Mgmt. Int. (Simulink V&V) PIL test (Embedded Coder) Test generation (Simulink Design Verifier) Run-time error detection (Polyspace products) Traceability matrix analysis (IEC Certification Kit) or model vs. code coverage (third-party tool) MISRA-C checking (Polyspace products) Simulink/Stateflow Embedded Coder Third-party tool 18

19 What are the standard requirement for using the tools? 19

20 Tool Inventory and Classification Inventory of all the tools involved Document use cases of the tools Classify the tools for their use cases Generally, most tools will not have to be qualified 20

21 Tool Classification and Qualification (ISO 26262) I. Tool Classification II. Tool Qualification Tool use cases Tool impact Tool error detection Tool confidence level ASIL UC 1..n TI 2 TD 3 TD 2 TD 1 Medium High TCL 3 TCL 2 Qualification methods for TCL3 Qualification methods for TCL2 Increasing qualification requirements TI 1 TCL 1 Qualification not required 21

22 Reference Workflow Model-Based Design for High-Integrity Software Model standards checking (Simulink V&V) PIL test (Embedded Coder) Simulation / model testing (Simulink) Model coverage (Simulink V&V) Req. Mgmt. Int. (Simulink V&V) Traceability matrix analysis (IEC Certification Kit) or model vs. code coverage (third-party tool) Simulink/Stateflow Embedded Coder Third-party tool 22

23 How can MathWorks simplify meeting the standard? 23

24 MathWorks Certification Kits IEC ISO EN IEC Certification Kit DO-178C DO-278A DO-330 DO-254 DO Qualification Kit 24

25 MathWorks Certification Kits Supports tool qualification Streamlines standard compliant development of embedded systems

26 Independent Assessment by TÜV SÜD Example Certificate Assessment Report 26

27 Qualification of Model-Based Design Tools Embedded Coder, Simulink Design Verifier, Simulink Verification and Validation, and Polyspace are pre-qualified for all ASILs according to ISO Simulink Verification and Validation Simulink Design Verifier PolySpace Client/Server for C/C++ Embedded Coder Note: Embedded Coder, Simulink Design Verifier, Simulink Verification and Validation, and Polyspace products were not developed using certified processes. 27

28 Process Compliance Demonstration Annotated method tables with suggestions on how to use Model-Based Design processes and tools to apply the methods listed in the standard 28

29 Reference Workflow - Compliance Demonstration Templates 29

30 Test Cases for Tool Qualification/Validation Test automation provided to validate tools within the project 30

31 Process Deployment Advisory Service MathWorks Consulting services to quickly adopt Model-Based Design for standards Objectives Identify gaps in current processes Provide a roadmap to an optimized standard compliant process Assist with deployment of that roadmap Educate on the standard Help with software tool qualification 31

32 Summary How can MathWorks tools help develop high-integrity systems? Model-Based Design offers many Verification and Validation methods Tool automation help meet the process documentation requirements What are the standard requirements for using the tools? The Reference Workflow is guiding through the development process How can MathWorks simplify meeting the standard? Certification/Qualification Kits and Consulting expertise eases the Tool Qualification process 32