“…This calls for including non-functional characteristics as part of the component interface specifications, which is best achieved by using multiple viewpoints [40,46,42]. Contract-based design supports multiple viewpoints by giving a mathematically precise answer to what it means to fuse them.…”
Section: Positive Impact Of Contract-based Designmentioning
confidence: 99%
“…Chapter 5 deals with Assume/Guarantee contracts [40,46]. This framework is the most straightforward instance of the meta-theory.…”
“…This calls for including non-functional characteristics as part of the component interface specifications, which is best achieved by using multiple viewpoints [40,46,42]. Contract-based design supports multiple viewpoints by giving a mathematically precise answer to what it means to fuse them.…”
Section: Positive Impact Of Contract-based Designmentioning
confidence: 99%
“…Chapter 5 deals with Assume/Guarantee contracts [40,46]. This framework is the most straightforward instance of the meta-theory.…”
“…This support is provided by applying the work in [6,68,73,75,76] that present a formal and general contracts [53] theory for modeling and specifying systems.…”
Section: Introductionmentioning
confidence: 99%
“…These tasks (I)-(IV) are also described in FuSa standards; however, the fact is that in contracts theory [6,68,73,75,76], these tasks are given formal semantics, i.e., interpretations in formal (mathematical) conditions. The present paper capitalizes on this fact by considering the support that can be provided for tasks (I)-(IV) by having a tool that evaluates these formal contract conditions.…”
Section: Introductionmentioning
confidence: 99%
“…Despite the fact that formal representations have several advantages over non-formal ones, formal languages are difficult to use by non-experts [23] and in industrial practice, 'overcoming the burden of formalization is a major challenge' [10]. Therefore, instead of focusing on enforcing all of the contract conditions in [6,68,73,75,76], the present paper instead identifies necessary conditions of the formal interpretations of tasks (I)-(IV) where these conditions can be evaluated even when requirements and architectures are not represented formally; in the following, such necessary conditions will be called syntactic contract conditions.…”
Functional safety standards such as IEC 61508 and ISO 26262 advocate a particularly stringent requirements engineering where safety requirements must be structured in a hierarchical manner and specified in accordance with the system architecture. In contrast to the stringent requirements engineering in functional safety standards, according to previous studies, requirements engineering in industry is in general of poor quality. Contracts theory has been previously shown to be suitable for supporting such a stringent requirements engineering effort; this support has also been implemented in tools. However, to use these contract-based tools, requirements must be formalized, which is a major challenge in industry. Therefore, to support current industrial requirements engineering practice and the stringent requirements engineering in functional safety standards, it is shown how tool support can be provided even when requirements, and also architectures, are not formalized. This is achieved by enforcing syntactic, yet formal, conditions in contracts theory. Despite the need for further validation, initial findings in an industrial case study indicate high potential in realizing the proposed support in an industrial setting.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.