Behaviour-driven model development and test-driven model review

Behaviour-Driven Model Development and Test-Driven Model Review combines Behaviour-Driven Development concepts, Model-Driven Development and Model-Based Testing to auto-generate code and associated tests.

Method Purpose Short description of the method's purpose and main benefits

Method description A detailed description of the method

Behaviour-Driven Model Development and Test-Driven Model Review combines Behaviour-Driven Development [BHM1] concepts, Model-Driven Development and Model-Based Testing in the following steps:

Define the test interface as methods and signal receptions in UML class diagrams
Express scenarios from the requirements as UML sequence diagrams
Model the required behaviour as UML state machine diagrams
- While doing so, continually run the scenarios from the sequence diagrams against the state machines. The modeler gets feedback which scenarios do not run through yet and where they get stuck.
Validate, that the scenarios work on the finished state machine models
Evaluate coverage of the scenarios on the state machines
Generate a minimal set of tests to complete the coverage
Review the generated tests – they represent all behaviour that might have been unintentionally added while modelling the state machines.
- Go back and change the model and the initial scenarios, if necessary and repeat.
Use the model to generate code
Run the original and the generated scenarios against
- the generated code (to exclude problems introduced by the code generator)
- the target compiled code (to exclude problems introduced by the compiler or the platform)
- the deployed binary in the target environment (to exclude problems introduced by the environment and production periphery)

The approach has been described in more detail in [BHM2], it is similar to Behaviour-Driven Formal Model Development [BHM3].

Method Strengths A listof the strengths of the method

Produces high-quality behaviour models
Enables domain experts to review the model indirectly by reviewing scenarios

Method Limitations The limitations of the method

Only limited tool support available yet

Method References Bibliography references to papers about the method.

[BHM1] Solis and X. Wang, “A study of the characteristics of behaviour-driven development,” in2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications, pp. 383–387.
[BHM2] Schlick R., Krenn W. (2019) Tackling the Challenges of Internet-of-Things-Development using Models. 2ndInternational Workshop on Embedded Software for the Industrial IOT, DATE, Florence, 2019.
[BHM3] Snook C. et al. (2018) Behaviour-Driven Formal Model Development. In: Sun J., Sun M. (eds) Formal Methods and Software Engineering. ICFEM 2018. Lecture Notes in Computer Science, vol 11232. Springer, Cham. https://doi.org/10.1007/978-3-030-02450-5_2

Method Dimensions

Evaluation Environment Type Type of environment where the method is applied. It can be more than one type of environment. (Dimension 1)

Evaluation Type Type of evaluation performed with that method. If a method is hybrid, more than one type can be selected. (Dimension 2)

Type of Component Under Evaluation Type of components that can be evaluated with that method. It can be more than one type. (Dimension 3)

Evaluation Stage The evaluation stage where the method is used. (Dimension 5)

Purpose of the Component Under Evaluation The type of purpose that can be evaluated by a method. It can be more than one type. (Dimension 6)

Type of Requirement Under Evaluation The type of requirements that a method is able to evaluate. It can be more than one type. (Dimension 7)

Evaluation Performance Indicator The type of evaluation criteria or KPI that a method is able to improve. It can be more than one type. (Dimension 8)

Relations

Related Methods A method could be related to other methods.

Tools A method can use zero or more tools.

Part Method A method (when it is a combination: Combination of method artefact that is a specialization of a V&V Method) could be composed of a set of V&V Methods.

Test Case or Verification and Validation activity Test Case or V&V activity performed in a Use Case. We will link to the method to the test cases where the method is used.

Standards A method can be linked with standards.

Context

Workflow

Contents

There are currently no items in this folder.