2015
DOI: 10.7250/csimq.2015-4.05
|View full text |Cite
|
Sign up to set email alerts
|

Contract-Based Design of Embedded Systems Integrating Nominal Behavior and Safety

Abstract: Abstract. The distributed design process for safety-critical embedded systems has become an increasingly difficult challenge: Electronic Control Units (ECUs) in vehicles, for instance, participate in many vehicle functions, while each vehicle function, in turn, is spread across several ECUs. Many suppliers participate in systems design and many partial functions are reused from past projects, not always knowing the assumptions at the time of their development. In particular, efficient allocation of safety mech… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 15 publications
(4 citation statements)
references
References 17 publications
0
4
0
Order By: Relevance
“…In contrast to the bottom up approach of combining component contracts into a composed contract, a top down approach is also possible and sometimes desired. Decomposing a set of requirements into individual component contracts has been studied in [14].…”
Section: Component Substitution and Diagnosismentioning
confidence: 99%
“…In contrast to the bottom up approach of combining component contracts into a composed contract, a top down approach is also possible and sometimes desired. Decomposing a set of requirements into individual component contracts has been studied in [14].…”
Section: Component Substitution and Diagnosismentioning
confidence: 99%
“…The behavior of a system, e.g., a platoon, in various degraded operational modes can be captured by a set of Assumption/Guarantee contracts [8]. A contract C =< A, G > can be defined as a pair of properties in which A represents the Assumptions on the system environment and G represents the Guarantee that the system promises, given that the assumptions are fulfilled [55]. Sljivo et al distinguish between strong contract C and weak contract C weak =< B, H >, where B and H are weak Assumption and weak Guarantee, respectively [56].…”
Section: ) Degradation Cascade Employing Contractsmentioning
confidence: 99%
“…Based on the counterexample, a user can manually localize the fault in K that causes the violation of φ. Contract-based design (CBD) (Cimatti and Tonetta 2012;Kaiser et al 2015) supports the automated verification of refinement consistency and correctness. In CBD, model checking is used to identify whether the top-level requirements of a system are consistently refined along the refinement of the system to components.…”
Section: Model Checkingmentioning
confidence: 99%