2011 Design, Automation &Amp; Test in Europe 2011
DOI: 10.1109/date.2011.5763167
|View full text |Cite
|
Sign up to set email alerts
|

Using contract-based component specifications for virtual integration testing and architecture design

Abstract: We elaborate on the theoretical foundation and practical application of the contract-based specification method originally developed in the Integrated Project SPEEDS [11], [9] for two key use cases in embedded systems design. We demonstrate how formal contract-based component specifications for functional, safety, and real-time aspects of components can be expressed using the pattern-based requirement specification language RSL developed in the Artemis Project CESAR, and develop a formal approach for virtual i… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
47
0

Year Published

2013
2013
2021
2021

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 83 publications
(48 citation statements)
references
References 8 publications
1
47
0
Order By: Relevance
“…An in-depth discussion about virtual integration can be found in [8]. In [8] contracts were extended by so called weak assumptions.…”
Section: Formal Underpinning and Validation Of Contractsmentioning
confidence: 99%
See 2 more Smart Citations
“…An in-depth discussion about virtual integration can be found in [8]. In [8] contracts were extended by so called weak assumptions.…”
Section: Formal Underpinning and Validation Of Contractsmentioning
confidence: 99%
“…In [8] contracts were extended by so called weak assumptions. Weak assumptions are used to describe a set of possible environments in which the component guarantees different behaviors.…”
Section: Formal Underpinning and Validation Of Contractsmentioning
confidence: 99%
See 1 more Smart Citation
“…e.g., [3][4][5]15,17,18,22,29]), is an emerging paradigm for correct-by-construction systems which structures components properties into contracts. A contract specifies the properties assumed to be satisfied by the component environment (assumptions), and the properties guaranteed by the component in response (guarantees).…”
Section: Introductionmentioning
confidence: 99%
“…It comprises different level of granularity. In case of a component-based design [5] the unit-tests have to validate that each individual component fulfills its requirements. The integrationtests deal with the problems that arise through the combination of multiple components and have to ensure their correct interaction.…”
Section: Introductionmentioning
confidence: 99%