@inproceedings{, author = {Nicolas, Carlos-Fernando and Eizaguirre, Fernando and Ortube, Asier Larrucea and Barner, Simon and Chauvel, Franck and Sagardui, Goiuria and P{\'{e}}rez, Jon}, title = {GSN Support of Mixed-Criticality Systems Certification}, booktitle = {Proceedings of the SAFECOMP 2017 Workshops ASSURE, DECSoS, SASSUR, TELERISE, and TIPS}, publisher = {Springer}, series = {LNCS}, number = {10489}, pages = {157--172}, year = {2017}, month = sep, timestamp = 2017.09.12, abstract = {Safety-critical applications could benefit from the standardisation, cost reduction and cross-domain suitability of current heterogeneous computing platforms. They are of particular interest for Mixed-Criticality Product Lines (MCPL) where safety- and non-safety functions can be deployed on a single embedded device using suitable isolation artefacts and development processes. The development of MCPLs can be facilitated by providing a reference architecture, a model-based design, analysis tools and Modular Safety Cases (MSC) to support the safety claims. In this paper, we present a method based on the MSCs to ease the certification of MCPLs. This approach consists of a semi-automated composition of layered argument fragments that trace the safety requirements argumentation to the supporting evidences. The core of the method presented in this paper is an argument database that is represented using the Goal Structuring Notation language (GSN). The defined method enables the concurrent generation of the arguments and the compilation of evidences, as well as the automated composition of safety cases for the variants of products. In addition, this paper exposes an industrial-grade case study consisting of a safety wind turbine system where the presented methodology is exemplified.}, isbn = {978-3-319-66284-8}, doi = {10.1007/978-3-319-66284-8_14}, keywords = {Goal Structuring Notation (GSN), Model-Based Development, Safety-critical Systems, Product Lines, Variability}, } @incollection{, author = {Aravantinos, Vincent and Voss, Sebastian and Teufl, Sabine and H{\"{o}}lzl, Florian and Sch{\"{a}}tz, Bernhard}, title = {AutoFOCUS 3: Tooling Concepts for Seamless, Model-based Development of Embedded Systems}, booktitle = {ACES-MB&WUCOR@MoDELS 2015}, publisher = {CEUR-WS.org}, series = {CEUR Workshop Proceedings}, pages = {19-26}, year = {2015}, abstract = {This paper presents tooling concepts in AutoFOCUS 3 supporting the development of software-intensive embedded system design. AutoFOCUS 3 is a highly integrated model-based tool covering the complete development process from requirements elicitation, deployment, the modelling of the hardware platform to code generation. This is achieved thanks to precise static and dynamic semantics based on the FOCUS theory. Models are used for requirements, for the software architecture (SA), for the hardware platform and for relations between those different viewpoints: traces from requirements to the SA, refinements between SAs, and deployments of the SA to the platform. This holistic usage of models allows the provision of a wide range of analysis and synthesis techniques such as testing, model checking and deployment and scheduling generation. In this paper, we demonstrate how tooling concepts on different steps in the development process look like, based on these integrated models and implemented in AutoFOCUS 3.}, keywords = {AutoFOCUS3, Seamless MBD, Model-Based Development, Embedded Systems, Tooling Concept, Tooling, model-based systems engineering, MbSE}, url = {http://ceur-ws.org/Vol-1508/paper4.pdf}, } @inproceedings{, author = {Voss, Sebastian and Sch{\"{a}}tz, Bernhard and Khalil, Maged and C{\^{a}}rlan, Carmen}, title = {Towards Modular Certification using Integrated Model-Based Safety Cases}, booktitle = {Proceedings of the International Workshop on Verification and Assurance ({VeriSure} 2013) (co-located with {CAV})}, publisher = {Springer}, year = {2013}, abstract = {Software-intensive systems are characterized by an increasing number of features implementing complex functionalities. In many domains, these new functionalities perform more and more safety-critical tasks. To argue about the safety of such systems, Safety Cases are a proven technique that allows a systematic argumentation. Safety Cases may contain complex arguments that can be decomposed corresponding to modular system artifacts. This paper illustrates how a model-based system design can be tightly integrated with safety case arguments, to demonstrate both how safety cases link safety-specific analysis techniques like FMEA or FTA to architectural elements to provide evidence for safety argumentation, as well as how safety cases can be directly applied to efficiently guide the construction of the system architecture w.r.t. the claims given in the safety case. We demonstrate how existing information about the system and tool assisted techniques (e.g. formal verification, statistical testing) can be integrated into a safety case for a convincing argument in a seamless model-based development environment.}, keywords = {Modular Certification, Safety Cases, Model-based Development, AutoFOCUS3, model-based safety cases, ExplicitCase, model-based systems engineering, MbSE}, url = {http://fm.csl.sri.com/VeriSure2013/}, } @inproceedings{, author = {Campetelli, Alarico and H{\"{o}}lzl, Florian and Neubeck, Florian}, title = {User-friendly Model Checking Integration in Model-based Development}, booktitle = {Proceedings of the 24th International Conference on Computer Applications in Industry and Engineering}, year = {2011}, abstract = {We present our approach to a user-friendly model checking integration in model-based development. The used modeling tool is AutoFocus 3, developed at our research group and specialized for reactive and embedded systems. For this integration, we approach usability at four points: tight coupling of verification properties with model elements, different specification languages for the formulation of properties, visualization of counterexamples as well as evaluation of different model checkers for adequate performance. Dealing with these issues leads to one of the first model-based development environments incorporating property specification, model checking and debugging.}, keywords = {verification, model checking, model-based development, tool support, embedded systems, AutoFOCUS3, formal verification, model-based systems engineering, MbSE}, } @inproceedings{Buckl2010c, author = {Buckl, Christian and Gaponova, Irina and Geisinger, Michael and Knoll, Alois and Lee, Edward A.}, title = {Model-Based Specification of Timing Requirements}, booktitle = {Proceedings of the 10th ACM International Conference on Embedded Software (EMSOFT 2010)}, publisher = {Association for Computer Machinery}, pages = {239--248}, year = {2010}, month = oct, institution = {Technische Universit{\"{a}}t M{\"{u}}nchen}, address = {Scottsdale, Arizona, USA}, abstract = {In the past, model-based development focused mainly on functional and structural aspects of thesystem to be developed. Recently, several approaches to include timing aspects have been suggested.However, these approaches focus predominantly on later development phases. Models specifyingthe requirements with respect to timing without focusing on a specific solution are missing.For example, few models allow the specification of the allowed jitter of a system.In this paper, we identify requirements that are necessary to express the desired timingbehavior of hard and soft real-time systems by analyzing different application domains.Based on these results, we evaluate existing approaches with respect to their suitabilityto model timing requirements and present an suitable approach. Finally, this paper describesthe application of the suggested approach in the context of an example from the automation domain.}, doi = {10.1145/1879021.1879053}, keywords = {Automation, embedded, Model-based Development, multifunk, Real-Time Systems, Requirements Analysis, Survey, time, Timing Requirements}, url = {Buckl2010c.pdf}, } @inproceedings{, author = {Geisinger, Michael and Barner, Simon and Wojtczyk, Martin and Knoll, Alois}, title = {A Software Architecture for Model-Based Programming of Robot Systems}, booktitle = {Advances in Robotics Research -- Theory, Implementation, Application}, publisher = {Springer}, pages = {135--146}, year = {2009}, month = jun, abstract = {While robot systems become more and more elaborate, the need to simplify programming them grows as well. Regarding the high degree of internal heterogeneity in the sense that different micro-controller platforms,protocols and performance layers are used in a single robot application, it is no longer feasible to have specialists dedicated to each individual task. This motivates the need for tool support that allows an abstract view not only on a robot's sensors and actuators, but also on the interconnection between the different components.In this work, we present how the model-based development and code generation tool EasyLab can be extended to support programming of all parts of a robot, including the main controller as well as peripheral devices like smart sensors. We show three typical use cases in the context of mobile platforms and also give an outlook on upcoming features such as distributed modeling and support for multi-core architectures.}, isbn = {978-3-642-01212-9}, doi = {10.1007/978-3-642-01213-6_13}, keywords = {embedded, easykit, EasyLab, Model-based Development, Code Generation, Interpretation, Zero Code Development, Smart Sensors, Smart Actuators, Communication}, } @inproceedings{Barner2008a, author = {Barner, Simon and Geisinger, Michael and Buckl, Christian and Knoll, Alois}, title = {{EasyLab}: Model-Based Development of Software for Mechatronic Systems}, booktitle = {IEEE/ASME International Conference on Mechatronic and Embedded Systems and Applications}, pages = {540--545}, year = {2008}, institution = {Technische Universit{\"{a}}t M{\"{u}}nchen}, address = {Beijing, China}, abstract = {Model-based development tools are one possible solution to handle the increasing complexity of mechatronic systems. While traditional approaches often separate design of hardware and software, especially in mechatronic systems hardware/software interaction is the most critical component. Hence, both aspects must be considered in this context. The goal is a model-based development tool for software/hardware co-design including the generation of efficient code for the respective target platforms. EasyLab is a modular and easily expandable development tool especially suitable for such applications. Its objectives are to facilitate reusability and to accelerate the development process. It raises the level of abstraction and thus simplifies the development of mechatronic systems even for unexperienced users. A graphical user interface provides various modeling languages that are easy to use. By employing platform optimized generation of the code, efficiency of the resulting programs can be guaranteed, which we demonstrate on a set of experimental mechatronic systems.}, doi = {10.1109/mesa.2008.4735652}, keywords = {easykit, EasyLab, embedded, Hardware-Software Codesign, Model-based Development, Rapid Hardware Prototyping, Zero Code Development}, }