Model-Based Testing for Systems of Systems
For Model-Based testing to be successful, it is necessary to model the system to be tested with an executable model-the most common ones are decision tables, finite state machines, statecharts, and some extension of classical Petri nets. Since these executable models are frequently paired with engines that allow a user to “execute” the model, this serves as an elegant form of rapid prototyping. Further, interesting scenarios can be easily captured and almost automatically expressed as system level test cases.
After a brief discussion that eliminates three of the executable models, this chapter presents Event-Driven Petri Nets and blends them with the Swim Lane pattern of UML, resulting in a model ideally suited for the communication interactions that are the essence of Systems of Systems testing. The material is taken almost exclusively from chapter 17 of Software Testing-A Craftsman’s Approach, fourth edition.
This eBook identifies a set of communication primitives that are necessary to express the communication among constituents in a system of systems. Each primitive is expressed as a traditional Petri net. The chapter concludes with a small, event driven system of systems modelled in Swim Lane Event-Driven Petri Nets.
1. Characteristics of Systems of Systems that require a new executable model.
2. A set of communication primitives designed for the needs of constituent systems.