Supporting System Level Design of Distributed Real Time Systems for Automotive Applications

Müller-Glaser, Klaus D.; Reichmann, Clemens; Kuehl, Markus

doi:10.1007/978-3-540-77419-8_2

Cited by 2 publications

(2 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…At present, Rhapsody and Simulink complement each other well and allow bi-directional integration in the following manner [13]:…”

Section: Model Transformationmentioning

confidence: 99%

“…The main limitation remains the capability to transform a Rhapsody model seamlessly to a Simulink model [5,11,13]. This 'model transformation' task was identified as major part of the project work; because a transformation tool did not exist, which was crucial for further exploitation of the collective advantages of the Rhapsody / Simulink combination.…”

Section: Model Transformationmentioning

confidence: 99%

See 1 more Smart Citation

Model Driven System Engineering for vehicle system utilizing Model Driven Architecture approach and hardware-in-the-loop simulation

Chong

Wong

Jia

et al. 2011

2011 IEEE International Conference on Mechatronics and Automation

View full text Add to dashboard Cite

In this paper, we show how Model Driven System Engineering (MDSE) can be applied in the development of a vehicle system. The drivers for the research have been to increase efficiency, flexibility and reconfigurability of UK vehicle system engineering, for enhanced competitiveness and innovation in face of increasing global competitions. Key contributions of the research include (i) establishment of baseline Model Driven Architecture (MDA) approach at the platform independent level; ( ii) identification of suitable methodology and toolset (based on Rhapsody / Simulink combination) to permit MDA system designs and hardware-in-the loop (HIL) simulation (based on xPC Target by Mathworks) for system verification; (iii) design and development of a model transformer for seamless transformation of the Rhapsody model to a Simulink model. The end outcome is a streamlined, integrated development platform to facilitate integration of various subsystems and verification ofoverall system performance to meet the desired system requirements. A case study based on a vehicle system (in this case a train system) had been implemented to verify the effectiveness and capability of the development platform by designing and developing an engine controller and an ABS controller for the train system. The research outcomes shown promising results, which are anticipated to benefit the wider transport sectors, as well as other sectors such as manufacturing and automation.Index Terms -Model driven system engineering (MDSE), Model driven architecture (MDA), hardware in the loop (HIL) simulation, and model based design.

show abstract

“…At present, Rhapsody and Simulink complement each other well and allow bi-directional integration in the following manner [13]:…”

Section: Model Transformationmentioning

confidence: 99%

Section: Model Transformationmentioning

confidence: 99%

Model Driven System Engineering for vehicle system utilizing Model Driven Architecture approach and hardware-in-the-loop simulation

Chong

Wong

Jia

et al. 2011

2011 IEEE International Conference on Mechatronics and Automation

View full text Add to dashboard Cite

show abstract

Software paradigms, assessment types and non-functional requirements in model-based integration testing

Häser

Felderer

Breu

2014

Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering

View full text Add to dashboard Cite

Context:In modern systems, like cyber-physical systems, where software and physical services are interacting, safety, security or performance play an important role. In order to guarantee the correct interoperability of such systems, with respect to functional and non-functional requirements, integration testing is an effective measure to achieve this. Model-based testing moreover not only enables early definition and validation, but also test automation. This makes it a good choice to overcome urgent challenges of integration testing. Objective: Many publications on model-based integration testing (MBIT) approaches can be found. Nevertheless, a study giving a systematic overview on the underlying software paradigms, measures for guiding the integration testing process as well as non-functional requirements they are suitable for, is missing. The aim of this paper is to find and synthesize the relevant primary studies to gain a comprehensive understanding of the current state of model-based integration testing. Method: For synthesizing the relevant studies, we conducted a systematic literature review (SLR) according to the guidelines of Kitchenham. Results: The systematic search and selection retrieved 83 relevant studies from which data has been extracted. Our review identified three assessment criteria for guiding the testing process, namely static metrics, dynamic metrics and stochastic &random. In addition it shows that just a small fraction considers non-functional requirements. Most approaches are for component-oriented systems. Conclusion: Results from the SLR show that there are two major research gaps. First, there is an accumulated need for approaches in the MBIT field that support non-functional requirements, as they are gaining importance. Second, means for steering the integration testing process, especially together with automation, need to evolve.

show abstract

Supporting System Level Design of Distributed Real Time Systems for Automotive Applications

Cited by 2 publications

References 1 publication

Model Driven System Engineering for vehicle system utilizing Model Driven Architecture approach and hardware-in-the-loop simulation

Model Driven System Engineering for vehicle system utilizing Model Driven Architecture approach and hardware-in-the-loop simulation

Software paradigms, assessment types and non-functional requirements in model-based integration testing

Contact Info

Product

Resources

About