Evaluating a formal scenario-based method for the requirements analysis in automotive software engineering

Automotive software systems often consist of multiple reactive components that must satisfy complex and safety-critical requirements. In automotive projects, the requirements are usually documented informally and are reviewed manually; this regularly causes inconsistencies to remain hidden until the integration phase, where their repair requires costly iterations. We therefore seek methods for the early automated requirement analysis and evaluated the scenario-based specification approach based on LSCs/MSDs; it promises to support an incremental and precise specification of requirements, and offers automated analysis through scenario execution and formal realizability checking. In a case study, we used ScenarioTools to model and analyze the requirements of a software to control a high-voltage coupling for electric vehicles. Our example contained 36 requirements and assumptions that we could successfully formalize, and we could successfully find specification defects by automated realizability checking. In this paper, we report on lessons learned, tool and method extensions we have introduced, and open challenges.

[1]  David Harel,et al.  LSCs: Breathing Life into Message Sequence Charts , 1999, Formal Methods Syst. Des..

[2]  Jochen Hoenicke,et al.  rt-Inconsistency: A New Property for Real-Time Requirements , 2011, FASE.

[3]  David Harel,et al.  Come, let's play - scenario-based programming using LSCs and the play-engine , 2003 .

[4]  Jörg Holtmann,et al.  ScenarioTools Real-Time Play-Out for Test Sequence Validation in an Automotive Case Study , 2014, Electron. Commun. Eur. Assoc. Softw. Sci. Technol..

[5]  B.H.C. Cheng,et al.  Real-time specification patterns , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[6]  Manfred Broy,et al.  Model-Based Engineering of Embedded Systems: The SPES 2020 Methodology , 2012 .

[7]  Jochen Hoenicke,et al.  Automotive behavioral requirements expressed in a specification pattern system: a case study at BOSCH , 2011, Requirements Engineering.

[8]  David Harel,et al.  Assert and negate revisited: Modal semantics for UML sequence diagrams , 2008, SCESM '06.

[9]  Kim G. Larsen,et al.  Formal Analysis and Testing of Real-Time Automotive Systems Using UPPAAL Tools , 2015, FMICS.

[10]  Manfred Broy,et al.  Model-Based Engineering of Embedded Systems , 2012, Springer Berlin Heidelberg.

[11]  Maxime Cordy,et al.  Incrementally synthesizing controllers from scenario-based product line specifications , 2013, ESEC/FSE 2013.

[12]  Chenxi Zhang,et al.  Use of formal method in construting safey-critical automotive software component , 2014, 2014 IEEE 5th International Conference on Software Engineering and Service Science.

[13]  David Harel,et al.  Come, Let’s Play , 2003, Springer Berlin Heidelberg.

[14]  Joel Greenyer,et al.  The ScenarioTools Play-Out of Modal Sequence Diagram Specifications with Environment Assumptions , 2013, Electron. Commun. Eur. Assoc. Softw. Sci. Technol..

[15]  Matthias Meyer,et al.  Formal scenario-based requirements specification and test case generation in healthcare applications , 2010, SEHC '10.