2010 Design, Automation &Amp; Test in Europe Conference &Amp; Exhibition (DATE 2010) 2010
DOI: 10.1109/date.2010.5457125
|View full text |Cite
|
Sign up to set email alerts
|

Timing modeling and analysis for AUTOSAR-based software development - a case study

Abstract: Safety-critical automotive systems must ful ll hard real-time constraints for reliability and safety. This paper presents a case study for the application of an AUTOSARbased language for timing modeling and analysis. We present and apply the Timing Augmented Description Language (TADL) and demonstrate a methodology for the development of a speedadaptive steer-by-wire system. We examine the impact of TADL and the methodology on the development process and the suitability and interoperability of the applied tool… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
12
0

Year Published

2012
2012
2020
2020

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 27 publications
(12 citation statements)
references
References 4 publications
0
12
0
Order By: Relevance
“…For example, let us To form this trade-off, the CPU utilization test is applied, meaning that the algorithm merges multiple tasks into one task whenever the CPU utilization after merging gets lower. 2 The utilization of the task containing τ i and τ j , denoted by u τ i j is computed by Eq. 15.…”
Section: Methods 2: the Feedback-based Refinement Approach (Smsafr)mentioning
confidence: 99%
See 2 more Smart Citations
“…For example, let us To form this trade-off, the CPU utilization test is applied, meaning that the algorithm merges multiple tasks into one task whenever the CPU utilization after merging gets lower. 2 The utilization of the task containing τ i and τ j , denoted by u τ i j is computed by Eq. 15.…”
Section: Methods 2: the Feedback-based Refinement Approach (Smsafr)mentioning
confidence: 99%
“…Let us presume that in average a shared runnable belongs to 3 transactions. There are 60 transactions in the benchmark where the number of runnables per transaction (excluding dummy transactions), according to the benchmark, is in the range of [2,10] with an average of 5. Therefore, in average 30% of the runnables belong to at least one transaction…”
Section: Application and Hardware Specificationsmentioning
confidence: 99%
See 1 more Smart Citation
“…AU-TOSAR serves as a specification for different layers (i.e., application software, runtime environment and basic software) of a system constituted by hierarchical components. AUTOSAR itself does not provide any means to perform timing analysis and for that reason it has been enriched by the TIMing MOdel (TIMMO) [17], which builds on the Timing Augmented Description Language (TADL).…”
Section: Related Workmentioning
confidence: 99%
“…In [16], the authors explore timing analysis with an AUTO-SAR-based [3] modeling language. The commercial SymTA/S [44] analysis tool is used for schedulability analysis.…”
Section: Related Workmentioning
confidence: 99%