Integrating Pattern-Based Formal Requirements Specification in an Industrial Tool-Chain

Filipovikj, Predrag; Jagerfield, Trevor; Nyberg, Mattias; Rodríguez-Navas, Guillermo; Seceleanu, Cristina

doi:10.1109/compsac.2016.140

Cited by 16 publications

(6 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several tools are available for pattern-based specifications. The PSPWizard [17] and the SESAMM Specifier [8] provide for a given pattern library export functionalities to a formal logic or to a textual representation. The SESAMM specifier has been integrated into an industrial toolchain in the automotive domain.…”

Section: Related Workmentioning

confidence: 99%

“…Bosch company investigated the suitability of the pattern catalog from [14] for 289 informal behavioral requirements from their automotive projects. A report on the integration of a pattern-based specification tool in an industrial (automotive) tool chain is given in [8,9]. A restricted set of patterns was used for the formal specifications within the PICASSOS project [5].…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Multiple Analyses, Requirements Once: simplifying testing & verification in automotive model-based development

Berger¹,

Nellen²,

Katoen³

et al. 2019

Preprint

View full text Add to dashboard Cite

In industrial model-based development (MBD) frameworks, requirements are typically specified informally using textual descriptions. To enable the application of formal methods, these specifications need to be formalized in the input languages of all formal tools that should be applied to analyse the models at different development levels. In this paper we propose a unified approach for the computer-assisted formal specification of requirements and their fully automated translation into the specification languages of different verification tools. We consider a two-stage MBD scenario where first Simulink models are developed from which executable code is generated automatically. We (i) propose a specification language and a prototypical tool for the formal but still textual specification of requirements, (ii) show how these requirements can be translated automatically into the input languages of Simulink Design Verifier for verification of Simulink models and BTC EmbeddedValidator for source code verification, and (iii) show how our unified framework enables besides automated formal verification also the automated generation of test cases.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Multiple Analyses, Requirements Once: simplifying testing & verification in automotive model-based development

Berger¹,

Nellen²,

Katoen³

et al. 2019

Preprint

View full text Add to dashboard Cite

show abstract

“…Many studies have proposed their own solutions to address this issue. Predrag Filipovikj et al [ 4 ] proposed a pattern-based approach to formally describe security requirements, seeking successful industrial applications of security requirements engineering. The EAST-ADL (i.e., Electronics Architecture and Software Technology—Architecture Description Language) framework language was proposed in [ 5 ] to describe the automotive domain in accordance with the ISO 26262 standard.…”

Section: Introductionmentioning

confidence: 99%

A Framework for Cybersecurity Requirements Management in the Automotive Domain

Luo

Jiang

Wang

et al. 2023

Sensors

View full text Add to dashboard Cite

The rapid development of intelligent connected vehicles has increased the attack surface of vehicles and made the complexity of vehicle systems unprecedented. Original equipment manufacturers (OEMs) need to accurately represent and identify threats and match corresponding security requirements. Meanwhile, the fast iteration cycle of modern vehicles requires development engineers to quickly obtain cybersecurity requirements for new features in their developed systems in order to develop system code that meets cybersecurity requirements. However, existing threat identification and cybersecurity requirement methods in the automotive domain cannot accurately describe and identify threats for a new feature while also quickly matching appropriate cybersecurity requirements. This article proposes a cybersecurity requirements management system (CRMS) framework to assist OEM security experts in conducting comprehensive automated threat analysis and risk assessment and to help development engineers identify security requirements prior to software development. The proposed CRMS framework enables development engineers to quickly model their systems using the UML-based (i.e., capable of describing systems using UML) Eclipse Modeling Framework and security experts to integrate their security experience into a threat library and security requirement library expressed in Alloy formal language. In order to ensure accurate matching between the two, a middleware communication framework called the component channel messaging and interface (CCMI) framework, specifically designed for the automotive domain, is proposed. The CCMI communication framework enables the fast model of development engineers to match with the formal model of security experts for threat and security requirement matching, achieving accurate and automated threat and risk identification and security requirement matching. To validate our work, we conducted experiments on the proposed framework and compared the results with the HEAVENS approach. The results showed that the proposed framework is superior in terms of threat detection rates and coverage rates of security requirements. Moreover, it also saves analysis time for large and complex systems, and the cost-saving effect becomes more pronounced with increasing system complexity.

show abstract

“…Transforming natural language requirements into formal representations has shown to be an effective way of verifying that the requirements are met, but so far it has been too difficult for the general tester and the requirements engineer to express requirements or test cases in a formal way [7], [8], [9].…”

Section: Introductionmentioning

confidence: 99%

“…In the aforementioned work, the authors propose 17 patterns that support the translation from structured English language into formal specifications. However, using these patterns typically requires tool support to be practically useful [9], [13]. Another approach is to start from the point of the domain knowledge of the tester, trying to simplify the specification language itself so it can be used by the average tester.…”

Section: Introductionmentioning

confidence: 99%

From Natural Language Requirements to Passive Test Cases Using Guarded Assertions

Flemström¹,

Eduard²,

Wasif³

et al. 2018

2018 IEEE International Conference on Software Quality, Reliability and Security (QRS)

View full text Add to dashboard Cite

In large-scale embedded system development, requirements are often expressed in natural language. Translating these requirements to executable test cases, while keeping the test cases and requirements aligned, is a challenging task. While such a transformation typically requires extensive domain knowledge, we show that a systematic process in combination with passive testing would facilitate the translation as well as linking the requirements to tests. Passive testing approaches observe the behavior of the system and test their correctness without interfering with the normal behavior. We use a specific approach to passive testing: guarded assertions (G/A). This paper presents a method for transforming system requirements expressed in natural language into G/As. We further present a proof of concept evaluation, performed at Bombardier Transportation Sweden AB, in which we show how the process would be used, together with practical advice of the reasoning behind the translation steps.

show abstract

Integrating Pattern-Based Formal Requirements Specification in an Industrial Tool-Chain

Cited by 16 publications

References 21 publications

Multiple Analyses, Requirements Once: simplifying testing & verification in automotive model-based development

Multiple Analyses, Requirements Once: simplifying testing & verification in automotive model-based development

A Framework for Cybersecurity Requirements Management in the Automotive Domain

From Natural Language Requirements to Passive Test Cases Using Guarded Assertions

Contact Info

Product

Resources

About