A Single Requirement Modeling with Graphical Language for Embedded System

Abstract

In order to do requirement-based testing of embedded system, we must have correct requirement specifications. But, natural language requirements of a client have ambiguity, inaccuracy, and inconsistency. To solve these problems, natural language requirements are modeled with modeling language such as UML and Simulink. During a modeling phase, the requirements are rearranged and retranslated in use-case. These activities are disadvantages of modeling. In this paper, we propose the technique, which is how to model a embedded system requirement into a model without rearranging and retranslating. This technique 1) represent a embedded system requirement with graphical language, and 2) model a requirement into a model. Because this technique only describes "what-to-do" of the requirement, this technique is useful to not only the low-level requirements but also the high-level requirements. We show some example systems modeled by REED, which has adopted this technique.

Requirement-based testing of an automotive ECU considering the behavior of the vehicle

“…The requirements are the relations between the input and output conditions of the SUT. In this paper, the RBT method uses R-bench (Oh et al, 2008) as the embedded software automation test tool.…”

“…Although HILS can evaluate the control algorithm in the ECU and predict the behavior of the vehicle, it is limited in its ability to evaluate the reliability of the ECU requirements. Requirement Based Testing (RBT) is a method used to verify the quality of an embedded system, such as an electronic control unit, which is adopted in vehicles (Wagner, 1994;Jung et al, 2008;Oh et al, 2008). RBT tests whether the embedded system satisfies pre-defined requirements.…”

“…The same inputs are provided to both the ECU and the test oracle. The quality of the embedded system can be verified by comparing the outputs of the ECU with those of the test oracle (Oh et al, 2008). Model Based Testing (MBT) is another method used to verify the quality of the embedded software of ECUs (Lamberg and Beine, 2004;Chen and Jones, 2007).…”

An overview on test generation from functional requirements

“…Mogyorodi (2001Mogyorodi ( , 2002Mogyorodi ( , 2003Mogyorodi ( ) 2003 Statistical Usage Testing Based on UML Huebner et al (2003), Riebisch et al (2002Riebisch et al ( ) 2003 Traceability from Use Cases to Test Cases Zielczynski (2006) Nebut and Fleurey (2003), Nebut et al (2006Nebut et al ( ) 2007 An Automatic Tool for Generating Test Cases from the System's Requirements Ibrahim et al (2007), Ismail et al (2007Ismail et al ( ) 2008 REED. Requirement Editor Oh et al (2008Oh et al ( ) 2007 Test Cases Generation from Use Cases Gutiérrez et al (2008aGutiérrez et al ( ,b) 2009 Software Product Line Testing Pérez et al (2009Pérez et al ( ) 2009 Bridging Test and Model-driven Approaches in Web Engineering Robles et al (2009) presents an overview to quantify the degree of maturity, systematization and automation of the existing works about the generation of functional test cases from functional requirements described in natural languages or, at least, in an informal language. In the literature, there are several approaches like (Liu and Yuting, 2008;Stocks and Carrington, 1996) or (TerMaat, 2001) that offer suitable results in the systematic generation of test cases.…”

“…• Another relevant approach within this group is REED (Oh et al, 2008) which generates test cases from a single requirement. Nevertheless, it is not included on the paper because, in fact, it is not an approach, but a tool to represent requirements in a specific notation and generate test case.…”