DOCSLIB.ORG

Model-Based Testing of Automotive Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Model-Based Testing of Automotive Systems 2008 International Conference on Software Testing, Verification, and Validation Model-based Testing of Automotive Systems Eckard Bringmann, Andreas Krämer PikeTec GmbH, Germany [email protected], [email protected] Abstract systems within the next decade. Consequently the impact of software on the customer and hence on In recent years the development of automotive market shares and competition will be enormous. This embedded devices has changed from an electrical and establishes software as a key technology in the mechanical engineering discipline to a combination of automotive domain. software and electrical/mechanical engineering. The During recent years the growth of software in the effects of this change on development processes, automotive industry led to a development process methods, and tools as well as on required engineering founded on model based technologies which have skills were very significant and are still ongoing today. many advantages for automotive developments. Firstly At present there is a new trend in the automotive model-based technologies such as MATLAB/Simulink, industry towards model-based development. Software Statemate, MatrixX, or LabView are domain specific components are no longer handwritten in C or and support powerful mechanisms for handling and Assembler code but modeled with processing continuous signals and events which are the MATLAB/Simulink™, Statemate, or similar tools. most important data types in the automotive domain. However, quality assurance of model-based These model-based technologies allow the developments, especially testing, is still poorly development of high-level models that can be used for supported. Many development projects require simulation in very early stages of the development creation of expensive proprietary testing solutions. process. This in turn is important since automotive In this paper we discuss the characteristics of development is an interdisciplinary business with automotive model-based development processes, the software, electrical, and mechanical engineering consequences for test development and the need to aspects inextricably entwined. Graphical models and reconsider testing procedures in practice. simulation of such models allows engineers to find a Furthermore, we introduce the test tool “TPT” which common functional understanding early in the design masters the complexity of model-based testing in the phase. So, model-based development improves automotive domain. To illustrate this statement we communication within development teams, with present a small automotive case study. customers, or between car manufacturers and suppliers. TPT is based on graphical test models that are not It reduces time to market through component re-use only easy to understand but also powerful enough to and reduces costs by validating systems and software express very complex, fully automated closed loop tests designs up front prior to implementation. Consequently in real-time. TPT has been initially developed by models are often treated as part of the requirements Daimler Software Technology Research. It is already specification, since the models illustrate the required in use in many production-vehicle development functionality in an executable manner. Model-based projects at car manufacturers and suppliers. development provides a development process from requirements to code, ensuring that the implemented 1. Motivation systems are complete and behave as expected. Model- based development allows segregation of concerns; Within only a few years the share of software technical aspects such as fixed-point scaling (i.e. the controlled innovations in the automotive industry has transformation of floating-point algorithms to fixed- increased from 20 percent to 80 percent, and is still point computations), calibration data management, and growing. Forecasts claim that software will determine the representation of signals in memory are separated more than 90% of the functionality of automotive from the core algorithms thereby keeping the models as lean as possible. 0-7695-3127-X/08978-0-7695-3127-4/08 $25.00 $25.00 © 2008 © 2008 IEEE IEEE 483485 DOI 10.1109/ICST.2008.45 2. Model-based testing in practice only a piece of software, but a complex construction that consists of software, hardware, electrical, Along with the growing functionality and the mechanical, and/or hydraulic parts. The development introduction of model-based development processes, of such a system requires the co-design of software and the demands on quality assurance have also increased. hardware components. Consequently an iterative In terms of testing, model-based development enables process is needed with a considerable number of system engineers to test the system in a virtual interim releases of the integrated system. Thoroughly environment when they are inexpensive to fix, i.e. testing these interim releases is crucial to ensure that before the code is actually implemented or integrated requirements inconsistencies and design or on the final hardware (which is called ECU or implementation faults can be uncovered as early as electronic control unit). However, in practice there are possible. This means that the same tests have to be just a few testing procedures that address the repeated again and again over the development cycle. automotive domain-specific requirements of model- Test automation is therefore essential as the manual test based testing sufficiently. The applied test methods and workload over many iterations would be at best tools are often proprietary, ineffective and require expensive and likely not practical, leading to less than significant effort and money. About 15 years ago thorough quality assurance standards. testing embedded devices comprised primarily of four Test automation also simplifies the coordination well-understood areas: (1) electromagnetic between car manufacturers and suppliers during compatibility (EMC tests), (2) electrical tests (e.g. development. Every ECU sample delivered by the short-circuit, creeping current, stress peaks), (3) supplier during development must fulfill at least a environmental tests (i.e. testing under extreme climate predefined acceptance test before being integrated in a conditions), and (4) field tests (on proving ground or new car setup. Finally, testing automotive systems the road). There was no need for dedicated functional often requires test scenarios with a very precise testing methods because the functional complexity was sequence of time-sensitive actions, especially for comparatively low. With the increasing popularity of power-train and chassis systems (in the range of µ-sec). model-based development the engineering discipline of The only way to execute such scenarios is automation. automotive model-based testing has been neglected for a long time. With the promise of model-based 3.2 Portability between integration levels development to prove concepts at early development stages by means of executable models it was assumed One major benefit of model-based development is that testing those models and the derived code is less the possibility to “do things as early as possible”. In important and therefore would not require new terms of testing this means to test the functionality in techniques. the model before the software is implemented and integrated into the final ECU. Between the initial modeling and the integration into the ECU there are 3. Requirements for automotive MBT intermediate integration levels described below. Since the functionality of the system should remain constant The term ‘model-based testing’ is widely used today and independent of the integration level, relevant test with slightly different meanings. In the automotive cases should also be constant throughout the industry it is normally used to describe all testing integration and implementation. activities in the context of model-based development In order to maximize reuse, a test procedure for projects. model-based developments should support the Automotive model-based development has specific portability or reuse of test cases between the various characteristics that require the use of dedicated model- platforms. On the one hand this reduces the effort of based testing approaches. The characteristics of, and test case design tremendously and, on the other hand, the resulting requirements for model-based testing are allows for easy comparison of test results between the discussed below. different integration levels which may be tested on different systems. In addition sharing test cases 3.1 Test automation between different levels also means that test cases can be expressed in a common notation. Test cases can be corrected or extended in a central test model without Automotive systems usually interact with a real- the need to adjust a lot of different test world environment which is under continual control of implementations for the different integration levels. the embedded system. Thus the whole system is not 484486 Although this requirement sounds trivial from a in a cheap and manageable way. Therefore the effort theoretical point of view it is a weak point in today’s spent by PiL testing is worthwhile in almost all cases. testing practice for model-based development because Hardware-in-the-Loop (HiL): When testing the test procedures and test languages are usually embedded system on HiL level the software runs on the specialized for one particular test platform and are very final ECU. However the environment around the ECU
Load more

Recommended publications
  • PCLTA-21 PCI Network Adapter Models 74501, 74502, 74503, and 74504
    PCLTA-21 PCI Network Adapter Models 74501, 74502, 74503, and 74504 ▼ Universal 32-bit PCI adapter card for LONWORKS® networks for PCs with 3.3V or 5V PCI ▼ Plug-and-play network driver compatible with MicrosoftWindows® 98/2000 and Windows XP ▼ Downloadable firmware allows updates without accessing or changing hardware ▼ Integral FT 3150® Free Topology Smart Transceiver, RS-485, TPT/XF-78, or TPT/XF-1250 transceiver ▼ LNS® Network Services Interface (NSI) supports LNS applications ▼ Layer 5 MIP for use with OpenLDV™ driver Description ▼ CE Mark, U.L. Listed, cU.L. Listed The PCLTA-21 Network Adapter is a high-perform- ance LONWORKS interface for personal computers equipped with a 3.3V or 5V 32-bit Peripheral The NSI mode of the PCLTA-21 adapter is used Component Interconnect (PCI) interface and a compati- with applications based on the LNS network operating system such as the LonMaker Tool, or the LNS DDE ble operating system. Designed for use in LONWORKS control networks that require a PC for monitoring, Server. managing, or diagnosing the network, the PCLTA-21 The MIP mode of the PCLTA-21 adapter is used with adapter is ideal for industrial control, building automa- applications based on OpenLDV. tion, and process control applications. The PCLTA-21 In both NSI and MIP modes, the adapter permits the adapter features an integral twisted pair transceiver, host PC to act as a LONWORKS application device, such downloadable memory, a network management inter- that the PC is running application-specific programs face, and plug-and-play capability with Microsoft while the adapter handles lower layer functions such as Windows 98/2000 and Windows XP.
    [Show full text]
  • Automated Annotation of Simulink Generated C Code Based on the Simulink Model
    DEGREE PROJECT IN COMPUTER SCIENCE AND ENGINEERING, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2020 Automated Annotation of Simulink Generated C Code Based on the Simulink Model SREEYA BASU ROY KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE Automated Annotation of Simulink Generated C Code Based on the Simulink Model SREEYA BASU ROY Master in Embedded Systems Date: September 25, 2020 Supervisor: Predrag Filipovikj Examiner: Matthias Becker School of Electrical Engineering and Computer Science Host company: Scania CV AB Swedish title: Automatisk Kommentar av Simulink Genererad C kod Baserad på Simulink Modellen iii Abstract There has been a wave of transformation in the automotive industry in recent years, with most vehicular functions being controlled electron- ically instead of mechanically. This has led to an exponential increase in the complexity of software functions in vehicles, making it essential for manufactures to guarantee their correctness. Traditional software testing is reaching its limits, consequently pushing the automotive in- dustry to explore other forms of quality assurance. One such technique that has been gaining momentum over the years is a set of verification techniques based on mathematical logic called formal verification tech- niques. Although formal techniques have not yet been adopted on a large scale, these methods offer systematic and possibly more exhaus- tive verification of the software under test, since their fundamentals are based on the principles of mathematics. In order to be able to apply formal verification, the system under test must be transformed into a formal model, and a set of proper- ties over such models, which can then be verified using some of the well-established formal verification techniques, such as model check- ing or deductive verification.
    [Show full text]
  • Systematic Testing of the Continuous Behavior of Automotive Systems
    Systematic Testing of the Continuous Behavior of Automotive Systems Eckard Bringmann Andreas Krämer DaimlerChrysler DaimlerChrysler Alt-Moabit 96a Alt-Moabit 96a 10559 Berlin, Germany 10559 Berlin, Germany +49 30 39982 242 +49 30 39982 336 [email protected] [email protected] ABSTRACT gap, the testing of automotive systems in practice focuses on In this paper, we introduce a new test method that enables the simple data tables to describe input signals or on script languages, systematic definition of executable test cases for testing the such as Visual Basic, Python or Perl, to automate tests. continuous behavior of automotive embedded systems. This Nevertheless, signals are still very difficult to handle in these method is based on a graphical notation for test cases that is not languages. Even worse, there is no systematic procedure to help only easy to understand but also powerful enough to express very testers reveal redundancies and missing, test relevant, aspects complex, fully automated tests as well as reactive tests. This new within their test cases. In other words, the selection of test data approach is already in use in several production-vehicle occurs ad hoc and is based on some use cases and typical extreme development projects at DaimlerChrysler and at some suppliers. scenarios but often does not cover all functional requirements of the system under test (SUT). Categories and Subject Descriptors Our new approach – which is called Time Partition Testing D2.5 [Software Engineering]: Testing
    [Show full text]
  • Lecture #4: Simulation of Hybrid Systems
    Embedded Control Systems Lecture 4 – Spring 2018 Knut Åkesson Modelling of Physcial Systems Model knowledge is stored in books and human minds which computers cannot access “The change of motion is proportional to the motive force impressed “ – Newton Newtons second law of motion: F=m*a Slide from: Open Source Modelica Consortium, Copyright © Equation Based Modelling • Equations were used in the third millennium B.C. • Equality sign was introduced by Robert Recorde in 1557 Newton still wrote text (Principia, vol. 1, 1686) “The change of motion is proportional to the motive force impressed ” Programming languages usually do not allow equations! Slide from: Open Source Modelica Consortium, Copyright © Languages for Equation-based Modelling of Physcial Systems Two widely used tools/languages based on the same ideas Modelica + Open standard + Supported by many different vendors, including open source implementations + Many existing libraries + A plant model in Modelica can be imported into Simulink - Matlab is often used for the control design History: The Modelica design effort was initiated in September 1996 by Hilding Elmqvist from Lund, Sweden. Simscape + Easy integration in the Mathworks tool chain (Simulink/Stateflow/Simscape) - Closed implementation What is Modelica A language for modeling of complex cyber-physical systems • Robotics • Automotive • Aircrafts • Satellites • Power plants • Systems biology Slide from: Open Source Modelica Consortium, Copyright © What is Modelica A language for modeling of complex cyber-physical systems
    [Show full text]
  • Introduction to Simulink
    Introduction to Simulink Mariusz Janiak p. 331 C-3, 71 320 26 44 c 2015 Mariusz Janiak All Rights Reserved Contents 1 Introduction 2 Essentials 3 Continuous systems 4 Hardware-in-the-Loop (HIL) Simulation Introduction Simulink is a block diagram environment for multidomain simulation and Model-Based Design. It supports simulation, automatic code generation, and continuous test and verification of embedded systems.1 Graphical editor Customizable block libraries Solvers for modeling and simulating dynamic systems Integrated with Matlab Web page www.mathworks.com 1 The MathWorks, Inc. Introduction Simulink capabilities Building the model (hierarchical subsystems) Simulating the model Analyzing simulation results Managing projects Connecting to hardware Introduction Alternatives to Simulink Xcos (www.scilab.org/en/scilab/features/xcos) OpenModelica (www.openmodelica.org) MapleSim (www.maplesoft.com/products/maplesim) Wolfram SystemModeler (www.wolfram.com/system-modeler) Introduction Model based design with Simulink Modeling and simulation Multidomain dynamic systems Nonlinear systems Continuous-, Discrete-time, Multi-rate systems Plant and controller design Rapidly model what-if scenarios Communicate design ideas Select/Optimize control architecture and parameters Implementation Automatic code generation Rapid prototyping for HIL, SIL Verification and validation Essentials Working with Simulink Launching Simulink Library Browser Finding Blocks Getting Help Context sensitive help Simulink documentation Demo Working with a simple model Changing
    [Show full text]
  • Automated Unit Testing in Model-Based Embedded Software Development
    Automated Unit Testing in Model-based Embedded Software Development Christoph Luckeneder1, Hermann Kaindl1 and Martin Korinek2 1Institute of Computer Technology, TU Wien, Vienna, Austria 2Robert Bosch AG, Gollnergasse¨ 15-17, Vienna, Austria Keywords: Automated Testing, Unit Tests, Model-based Development, Embedded Software, Safety-critical Systems, Automotive. Abstract: Automating software tests is generally desirable, and especially for the software of safety-critical real-time systems such as automotive control systems. For such systems, also conforming with the ISO 26262 standard for functional safety of road vehicles is absolutely necessary. These are embedded systems, however, which pose additional challenges with regard to test automation. In particular, the questions arise on which hardware platform the tests should be performed and by use of which workflow and tools. This is especially relevant in terms of cost, while still ensuring conformance with ISO 26262. In this paper, we present a practical approach for automated unit testing in model-based embedded software development for a safety-critical automotive application. Our approach includes both a workflow and sup- porting tools for performing automated unit tests. In particular, we analyze an as-is workflow and propose changes to the workflow for reducing costs and time needed for performing such tests. In addition, we present an improved tool chain for supporting the test workflow. In effect, without manually implementing each test case twice unit tests can be performed both in a simulation environment and on an open-loop test environment including the embedded platform target hardware. 1 INTRODUCTION The following support through a tool chain was planned: modeling and simulation of the resulting Automotive systems have more and more become software models, as well as model-based test automa- software-intensive systems, which include large-scale tion.
    [Show full text]
  • FMI Target for Simulink Coder, It Is Now Possible to Export Models from Simulink to Any Platform That Supports Fmus for Co-Simulation
    Supporting your vision Cross-Platform Modeling with FMI Target for Simulink® Coder™ Open technology standards for an integrated product lifecycle Engine Transmission Thermal EV/HV Chassis Compo- Models Models Systems Models nents Models Functional Mock-Up Interface The challenge for manufacturers of complex machinery that heavily rely on components from suppliers is the seamless exchange of data and specifications during the development. The same holds true for large corporates with multiple R&D departments at various locations using several development tools due to different objectives. Those challenges include different programming languages from the various tools, the lack of standardized model interfaces and the concerns for the protection of intellectual property. The development of the Functional Mock-up Interface (FMI) has enabled software-, model- and hardware-in-the-loop simulations with dynamic system models from different software environments. With the FMI Target for Simulink Coder, it is now possible to export models from Simulink to any platform that supports FMUs for Co-Simulation. FMI for Co-Simulation The goal is to couple two or more models with solvers in a co-simulation environment. The data exchange between subsystems is restricted to discrete communication points. The subsystems are processed independently from each other by their individual solvers during the time interval between two communication points. Master algorithms control the synchronization of all slave simulation solvers and the data exchange between the subsystems. The interface allows for both standard and advanced master algorithms, such as variable communication step sizes, signal extrapolation of higher order and error checking. FMI Target for Simulink® Coder™ FMI for Co-Simulation For the exchange of models across different platforms, the FMI Target for Simulink Coder enables the export of models from Simulink as FMUs for Co-Simulation.
    [Show full text]
  • Making Simulink Models Robust with Respect to Change Making Simulink Models Robust with Respect to Change
    Making Simulink Models Robust with Respect to Change Making Simulink Models Robust with Respect to Change By Monika Jaskolka, B.Co.Sc., M.A.Sc. a thesis submitted to the Department of Computing and Software and the School of Graduate Studies of McMaster University in partial fulfillment of the requirements for the degree of Doctor of Philosophy Doctor of Philosophy (December 2020) McMaster University (Software Engineering) Hamilton, ON, Canada Title: Making Simulink Models Robust with Respect to Change Author: Monika Jaskolka B.Co.Sc. (Laurentian University) M.A.Sc. (McMaster University) Supervisors: Dr. Mark Lawford, Dr. Alan Wassyng Number of Pages: xi, 206 ii For my husband, Jason iii Abstract Model-Based Development (MBD) is an approach that uses software models to describe the behaviour of embedded software and cyber-physical systems. MBD has become an increasingly prevalent paradigm, with Simulink by MathWorks being the most widely used MBD platform for control software. Unlike textual programming languages, visual languages for MBD such as Simulink use block diagrams as their syntax. Thus, some software engineering principles created for textual languages are not easily adapted to this graphical notation or have not yet been supported. A software engineering principle that is not readily supported in Simulink is the modularization of systems using information hiding. As with all software artifacts, Simulink models must be constantly maintained and are subject to evolution over their lifetime. This principle hides likely changes, thus enabling the design to be robust with respect to future changes. In this thesis, we perform repository mining on an industry change management system of Simulink models to understand how they are likely to change.
    [Show full text]
  • Modeling and Simulation in Scilab/Scicos Mathematics Subject Classification (2000): 01-01, 04-01, 11 Axx, 26-01
    Stephen L. Campbell, Jean-Philippe Chancelier and Ramine Nikoukhah Modeling and Simulation in Scilab/Scicos Mathematics Subject Classification (2000): 01-01, 04-01, 11 Axx, 26-01 Library of Congress Control Number: 2005930797 ISBN-10: 0-387-27802-8 ISBN-13: 978-0387278025 Printed on acid-free paper. © 2006 Springer Science + Business Media, Inc. All rights reserved. This work may not be translated or copied in whole or in part without the written permission of the publisher (Springer Science+Business Media, Inc., 233 Spring Street, New York, NY 10013, USA), except for brief excerpts in connection with reviews or scholarly analysis. Use in connection with any form of information storage and retrieval, electronic adaption, computer software, or by similar or dissimilar methodology now known or hereafter developed is forbidden. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. Printed in the United States of America. (BPR/HAM) 9 8 7 6 5 4 3 2 1 springeronline.com Preface Scilab (http://www.scilab.org) is a free open-source software package for scientific com- putation. It includes hundreds of general purpose and specialized functions for numerical computation, organized in libraries called toolboxes that cover such areas as simulation, optimization, systems and control, and signal processing. These functions reduce consid- erably the burden of programming for scientific applications. One important Scilab toolbox is Scicos. Scicos (http://www.scicos.org) provides a block-diagram graphical editor for the construction and simulation of dynamical sys- tems.
    [Show full text]
  • A Modelica Power System Library for Phasor Time-Domain Simulation
    2013 4th IEEE PES Innovative Smart Grid Technologies Europe (ISGT Europe), October 6-9, Copenhagen 1 A Modelica Power System Library for Phasor Time-Domain Simulation T. Bogodorova, Student Member, IEEE, M. Sabate, G. Leon,´ L. Vanfretti, Member, IEEE, M. Halat, J. B. Heyberger, and P. Panciatici, Member, IEEE Abstract— Power system phasor time-domain simulation is the FMI Toolbox; while for Mathematica, SystemModeler often carried out through domain specific tools such as Eurostag, links Modelica models directly with the computation kernel. PSS/E, and others. While these tools are efficient, their individual The aims of this article is to demonstrate the value of sub-component models and solvers cannot be accessed by the users for modification. One of the main goals of the FP7 iTesla Modelica as a convenient language for modeling of complex project [1] is to perform model validation, for which, a modelling physical systems containing electric power subcomponents, and simulation environment that provides model transparency to show results of software-to-software validations in order and extensibility is necessary. 1 To this end, a power system to demonstrate the capability of Modelica for supporting library has been built using the Modelica language. This article phasor time-domain power system models, and to illustrate describes the Power Systems library, and the software-to-software validation carried out for the implemented component as well as how power system Modelica models can be shared across the validation of small-scale power system models constructed different simulation platforms. In addition, several aspects of using different library components. Simulations from the Mo- using Modelica for simulation of complex power systems are delica models are compared with their Eurostag equivalents.
    [Show full text]
  • OMG Sysphs: Integrating Sysml, Simulink, Modelica And
    OMG SysPhs: Integrating SysML, Simulink, Modelica and FMI | ref.: 3DS_Document_2015 | ref.: 2/13/20 | Confidential Information | Information | Confidential Nerijus Jankevicius Systèmes CATIA | No Magic Dassault © INCOSE IW, Torrance, Jan 27, 2020 3DS.COM System Model as an Integration Framework © 2012-2014 by Sanford Friedenthal SysML as co-simulation environment 35 Reduce and standardize mappings 4 Unified Physics Domain Flowing Substance Flow rate Potential to flow Electrical Charge Current Voltage Hydraulic Volume Volumetric flow rate Pressure Rotational Angular momentum Torque Angular velocity Translational Linear momentum Force Velocity Thermal Entropy Entropy flow Temperature flow rate = amount of substance/time flow rate * potential = energy / time = power The Standard : SysPhs •SysPhS - https://www.omg.org/spec/SysPhS/1.0 • SysML Mapping to SiMulink and Modelica • SysPhS profile • SysPhS library Simulation profile Modelica vs Simulink • Modelica • SiMulink • Language is better suited for physical • Language is well-suited for control modeling (plant) algorithMs • Object oriented approach for • TransforMational seMantics of signals modeling physical and signal processing coMponents (Mechanical, electrical, etc.) • Causal seMantics (inputs -> outputs) • Causal and A-Causal seMantics • Well integrated into the “MATLAB (equations) universe” • Open standard (of the textual • Widely used in industry (standard de- language) facto) • Multi tool support (although DyMola • Many existing tool integrations is doMinant) • Code generation to
    [Show full text]
  • TPT Tutorial
    Time Partition Testing Systematic automated testing of embedded systems PikeTec GmbH, http://www.piketec.com There are only a few tools for testing embedded systems in the automotive domain. Their function usually lies in the test-management or automation of tests by means of test scripts. Time Partition Testing (TPT) noticeably exceeds this. It combines a systematic and very graphic modelling technique for test cases with a fully automatic test execution in different environments and automatic test evaluation in a unique way. In doing so, TPT even supports testing of control systems. Time Partition Testing (TPT) was developed to graphically and compactly model tests of embedded systems – especially those with continuous behaviour –, to automate those tests and to offer a systematic that supports the tester in selecting an ideal amount of test cases. The intuitive graphic modelling technique for test cases, the mechanisms for the structuring of complex test problems, the simple integration in any test- bench and a number of additional interesting features makes TPT a unique test solution. All this has contributed to TPT becoming the central testing tool in a large number of development projects at car manufacturers and suppliers and has become an integral part of the process chain. Embedded systems TPT is specialized on testing embedded systems whose inputs and outputs can be represented as signals. Most control systems belong to this system class. The implementation language of the embedded system (e.g. ‘C’ code, C++, MATLAB/Simulink/Stateflow, Statemate or a combination of multiple languages) is irrelevant for TPT. TPT does not require a particular implementation language.
    [Show full text]