Modeling and Validating Requirements Using Executable Cotnracts and Scenarios

Arnold, Dave; Corriveau, Jean-Pierre; Shi, Wei

doi:10.1109/sera.2010.46

Cited by 10 publications

(17 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…On the other hand, focusing on semi-formal methods through use cases and scenarios as a means to model and test the functional behaviour of a software or a system has been found to have their own challenges like the challenge of generating executable test cases for enhancing efficiency of testing [105]. But exploring semi-formal MBT methods and addressing the challenges within it has been found to generate solutions that are more cost effective and scalable as compared to the formal MBT methods.…”

Section: Comparative Analysis Based On Scientific Literaturementioning

confidence: 99%

See 1 more Smart Citation

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Chunduri

Feldt

Adenmark

2016

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Context. The share and importance of software within automotive vehicles is growing steadily. Most functionalities in modern vehicles, especially safety related functions like advanced emergency braking, are controlled by software. A complex and common phenomenon in today's automotive vehicles is the distribution of such software functions across several Electronic Control Units (ECUs) and consequently across several ECU system software modules. As a result, integration testing of these distributed software functions has been found to be a challenge. The automotive industry neither has infinite resources, nor has the time to carry out exhaustive testing of these functions. On the other hand, the traditional approach of implementing an ad-hoc selection of test scenarios based on the tester's experience, can lead to test gaps and test redundancies. Hence, there is a pressing need within the automotive industry for a feasible and effective verification strategy for testing distributed software functions. Objectives. Firstly, to identify the current approach used to test the distributed automotive embedded software functions in literature and in a case company. Secondly, propose and validate a feasible and effective verification strategy for testing the distributed software functions that would help improve test coverage while reducing test redundancies and test gaps. Methods. To accomplish the objectives, a case study was conducted at Scania CV AB, Södertälje, Sweden. One of the data collection methods was through conducting interviews of different employees involved in the software testing activities. Based on the research objectives, an interview questionnaire with open-ended and close-ended questions has been used. Apart from interviews, data from relevant artifacts in databases and archived documents has been used to achieve data triangulation. Moreover, to further strengthen the validity of the results obtained, adequate literature support has been presented throughout. Towards the end, a verification strategy has been proposed and validated using existing historical data at Scania. Conclusions. The proposed verification strategy to test distributed automotive embedded software functions has given promising results by providing means to identify test gaps and test redundancies. It helps establish an effective and feasible approach to capture function test coverage information that helps enhance the effectiveness of integration testing of the distributed software functions.

show abstract

Section: Comparative Analysis Based On Scientific Literaturementioning

confidence: 99%

“…Arnold et al in [105] explore the concept of modelling requirements using scenarios and contracts for validation of requirements. Here, contracts are preconditions and post conditions to scenarios of the system execution.…”

Section: Summary Of Previous Workmentioning

confidence: 99%

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Chunduri

Feldt

Adenmark

2016

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

show abstract

“…Arnold et al [1,2] developed a framework for the specification and execution of testable requirements models. Whereas the general approach is in parts similar to ours, he does not employ verification methods as we do (by employing a bounded model checker).…”

Section: Other Related Workmentioning

confidence: 99%

“…We mainly have black-box unit testing of functional properties in mind when talking about a test case 2. Inlining is done by software bounded model checking tools automatically as part of the preprocessing of the code.…”

mentioning

confidence: 99%

Bridging the gap between test cases and requirements by abstract testing

Merz

Sinz

Post

et al. 2015

Innovations Syst Softw Eng

View full text Add to dashboard Cite

In this article we propose a technique, called abstract testing, which replaces traditional test cases by abstract test cases. By doing so, fewer test cases are needed, and they are linked more closely to the requirements. Abstract tests can be considered as verification scenarios on the source code level which are derived from the requirements. Checking verification scenarios against the source code is done automatically using a software model checker. We also suggest a migration path from traditional tests to abstract test cases, which provides a smooth transition towards this new technique. Finally, we demonstrate feasibility of abstract testing by a case study from the automotive systems domain.

show abstract

“…( [1], [2]) developed a framework for the specification and execution of testable requirements models. Whereas the general approach is in parts similar to ours, he does not employ verification methods as we do (by employing a bounded model checker).…”

Section: Related Workmentioning

confidence: 99%

Abstract Testing: Connecting Source Code Verification with Requirements

Merz

Sinz

Post

et al. 2010

2010 Seventh International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

Abstract-Traditionally, test cases are used to check whether a system conforms to its requirements. However, to achieve good quality and coverage, large amounts of test cases are needed, and thus huge efforts have to be put into test generation and maintenance. We propose a methodology, called Abstract Testing, in which test cases are replaced by verification scenarios. Such verification scenarios are more abstract than test cases, thus fewer of them are needed and they are easier to create and maintain. Checking verification scenarios against the source code is done automatically using a software model checker. In this paper we describe the general idea of Abstract Testing, and demonstrate its feasibility by a case study from the automotive systems domain.

show abstract

Modeling and Validating Requirements Using Executable Cotnracts and Scenarios

Cited by 10 publications

References 15 publications

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Bridging the gap between test cases and requirements by abstract testing

Abstract Testing: Connecting Source Code Verification with Requirements

Contact Info

Product

Resources

About