A Model-Based Design Tool of Automotive Software Architecture

Author(s):  
Jeong-Si Kim ◽  
Chaedeok Lim ◽  
Tae-Man Han
Author(s):  
Tibor Farkas

Premium quality and innovation are the cornerstones of the leading positions of car manufacturers and suppliers in the world market. The permanently increasing complexity of in-car electronics and the rapidly growing amount of automotive software running on embedded electronic control units, places higher demands on quality assurance for the future. Quality cannot be implemented into software on embedded control units after their development. Methods for defects detection have to be constituted to automatically stop development to fix a problem before the defect continues downstream. In addition preventive actions have to be taken in respect of front-loading quality and reliability. An automatic and tool independent check of custom development rules, quality standards and enterprise wide guidelines can support the quality assurance process in the development of automotive control software. In the domain of automotive software engineering there is a lack of automated checking for standard conformance. Especially, a formal and tool independent notation of rules to follow is missing. In this chapter, the model-based design of automotive vehicle functions is taken as an example to show how textual rules describing development standards to be met can be transformed into a formal notation using the open standards Meta Object Facility and Object Constraint Language. Thereafter these rules can be checked automatically. The feasibility of this approach is shown by a software demonstrator.


2010 ◽  
Vol 44 (6) ◽  
pp. 507-518 ◽  
Author(s):  
Arnab Ray ◽  
Raoul Jetley ◽  
Paul L. Jones ◽  
Yi Zhang

Abstract This paper demonstrates the benefits of adopting model-based design techniques for engineering medical device software. By using a patient-controlled analgesic (PCA) infusion pump as a candidate medical device, the authors show how using models to capture design information allows for i) fast and efficient construction of executable device prototypes ii) creation of a standard, reusable baseline software architecture for a particular device family, iii) formal verification of the design against safety requirements, and iv) creation of a safety framework that reduces verification costs for future versions of the device software.1


2009 ◽  
pp. 135-146 ◽  
Author(s):  
Michael Geisinger ◽  
Simon Barner ◽  
Martin Wojtczyk ◽  
Alois Knoll

2006 ◽  
Author(s):  
Christian Wewetzer ◽  
Klaus Lamberg ◽  
Rainer Otterbach

Sign in / Sign up

Export Citation Format

Share Document