Specification of Timed EFSM Fault Models in SDL

Batth, S.S.; Vieira, E.R.; Cavalli, Ana; Uyar, M. Ümit

doi:10.1007/978-3-540-73196-2_4

Cited by 18 publications

(13 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Approaches described in [11][12][13]17] present mutation operators targeting formal abstract models, independently from specific programming languages. In [11], the great variety of operators used to introduce mutation in graph-based models is gathered into two basic operations (i.e., insertion and omission) and their combinations.…”

Section: Introductionmentioning

confidence: 99%

A mutation model for the SystemC TLM 2.0 communication interfaces

Bombieri

Fummi

Pravadelli

2008

Proceedings of the Conference on Design, Automation and Test in Europe

View full text Add to dashboard Cite

Mutation analysis is a widely-adopted strategy in software testing with two main purposes: measuring the quality of test suites, and identifying redundant code in programs. Similar approaches are applied in hardware verification and testing too, especially at RTL or gate level, where mutants are generally referred as faults, and mutation analysis is performed by means of fault modeling and fault simulation. However, in modern embedded systems there is a close integration between HW and SW parts, and verification strategies should be applied early in the design flow. This requires the definition of new mutation analysis-based strategies that work at system level, where HW and SW functionalities are not partitioned yet. In this context, the paper proposes a mutation model for perturbing transaction level modeling (TLM) SystemC descriptions. In particular, the main constructs provided by the SystemC TLM 2.0 library have been analyzed, and a set of mutants is proposed to perturb the primitives related to the TLM communication interfaces.

show abstract

Section: Introductionmentioning

confidence: 99%

A mutation model for the SystemC TLM 2.0 communication interfaces

Bombieri

Fummi

Pravadelli

2008

Proceedings of the Conference on Design, Automation and Test in Europe

View full text Add to dashboard Cite

show abstract

“…Mutation operators have also been defined for modeling languages such as finite state machines [8,18,26], state charts [32,52], Petri nets [17], and timed automata [44]. Mutation operators for models focus on the modeling elements and can do things like remove an element or change the target node for an edge.…”

Section: Mutation-based Testingmentioning

confidence: 99%

Using mutation to design tests for aspect-oriented models

Lindström

Offutt

Sundmark

et al. 2017

Information and Software Technology

View full text Add to dashboard Cite

Using mutation to design tests for aspect-oriented models. Technology, http://dx.doi.org/10. 1016/j.infsof.2016.04.007 Access to the published version may require subscription. N.B. When citing this work, cite the original published paper. Information and Software AbstractContext: Testing for properties such as robustness or security is complicated because their concerns are often repeated in many locations and muddled with the normal code. Such "cross-cutting concerns" include things like interrupt events, exception handling, and security protocols. Aspect-oriented (AO) modeling allows developers to model the cross-cutting behavior independently of the normal behavior, thus supporting model-based testing of cross-cutting concerns. However, mutation operators defined for AO programs (source code) are usually not applicable to AO models (AOMs) and operators defined for models do not target the AO features.Objective: We present a method to design abstract tests at the aspect-oriented model level. We define mutation operators for aspect-oriented models and evaluate the generated mutants for an example system. Method: AOMs are mutated with novel operators that specifically target the AO modeling features. Test traces killing these mutant models are then generated. The generated and selected traces are abstract tests that can be transformed to concrete black-box tests and run on the implementation level, to evaluate the behavior of the woven cross-cutting concerns (combined aspect and base models). Results: This paper is a significant extension of our paper at Mutation 2015. We present a complete fault model, additional mutation operators, and a thorough analysis of the mutants generated for an example system. Conclusions: The analysis shows that some mutants are stillborn (syntactically illegal) but none is equivalent (exhibiting the same behavior as the original model). Additionally, our AOM-specific mutation operators can be combined with pre-existing operators to mutate code or models without any overlap.

show abstract

“…The more classical proposals are usually based on timed automata, although recent proposals tend to consider other formalisms such as temporal extensions of labeled transition systems and of finite state machines (e.g. [4,34,35,44,48]). Due to the intrinsical difficulty behind testing timed systems, different approaches to the problem have been exercised, falling into one or more of the following categories.…”

Section: Related Workmentioning

confidence: 99%

Testing timed systems modeled by Stream X-machines

2009

View full text Add to dashboard Cite

Stream X-machines have been used to specify real systems requiring to represent complex data structures. They are a kind of extended finite state machine using a shared memory to specify communications between the components of systems. In this paper we introduce an extension of the Stream X-machines formalism in order to specify systems that present temporal requirements. On the one hand, we consider that (output) actions take time to be performed. On the other hand, our formalism allows to specify timeouts. Timeouts represent the time a system can wait for the environment to react. Since timeous affect the set of available actions of the system, a relation focusing on the functional behavior of systems, that is, the actions that they can perform, must explicitly take into account the possible timeouts. We also propose a formal testing methodology allowing to systematically test a system with respect to a specification. Finally, we introduce a test derivation algorithm. Given a specification, the derived test suite is sound and complete, that is, a system under test successfully passes the test suite if and only if this system conforms to the specification.

show abstract

Specification of Timed EFSM Fault Models in SDL

Cited by 18 publications

References 14 publications

A mutation model for the SystemC TLM 2.0 communication interfaces

A mutation model for the SystemC TLM 2.0 communication interfaces

Using mutation to design tests for aspect-oriented models

Testing timed systems modeled by Stream X-machines

Contact Info

Product

Resources

About