Towards Scenario-Based Testing of UML Diagrams

Brosch, Petra; Egly, Uwe; Gabmeyer, Sebastian; Kappel, Gerti; Seidl, Martina; Tompits, Hans; Widl, Magdalena; Wimmer, Manuel

doi:10.1007/978-3-642-30473-6_12

Cited by 16 publications

(14 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The first family on a subset of the SMTP protocol is based on the state machines presented in Section 2. The second family models the behavior of a coffee machine and its users similar to the example presented in [8]. Finally, in the third family we model the behavior of the famous dining philosophers problem, inspired by the running example of [25].…”

Section: Discussionmentioning

confidence: 99%

“…In [8], we proposed to use model checking to validate the merged version of an evolving sequence diagram. No support for the merging process itself is provided.…”

Section: Related Workmentioning

confidence: 99%

“…The formalization of the communication between state machines is not relevant for this paper and is therefore omitted. It can be found in [8].…”

Section: Definition 1 (State Machine)mentioning

confidence: 99%

See 2 more Smart Citations

Guided Merging of Sequence Diagrams

Widl

Biere

Brosch

et al. 2013

Software Language Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. The employment of optimistic model versioning systems allows multiple developers of a team to work independently on their local copies of a software model. The merging process towards one consolidated version obviously turns out to be challenging when performed without any tool support. Recently, several sophisticated approaches for model merging have been presented. However, even for multi-view modeling languages like UML, which distribute the information on the system under development over different diagrams, diagrams of different views are merged independently of each other. Hence, inconsistencies between different views are likely to be introduced into the merged model. We suggest to solve this problem by exploiting information stored in one view as constraint for the computation of a consolidated version of another view. More specifically, we demonstrate how state machines can guide the integration of parallel changes performed on a sequence diagram. We give a concise formal description of this problem and suggest a translation to propositional logic.

show abstract

Section: Discussionmentioning

confidence: 99%

“…In [8], we proposed to use model checking to validate the merged version of an evolving sequence diagram. No support for the merging process itself is provided.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Guided Merging of Sequence Diagrams

Widl

Biere

Brosch

et al. 2013

Software Language Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…Similarly, Bouabana-Tebibel et al [22] translate UML activity diagrams to Object Petri Nets [92] and analyze the Petri Nets using a model checker to allow the designer to verify properties such as: deadlock-free (there are no UML states that prevent any activity to be invoked eventually), livelock-free (there are no loops of activities on the diagram) and quasi-liveness (guarantees that each UML activity can be invoked eventually). Furthermore, Brosch et al [26] translate UML statechart diagrams and sequence diagrams to PROMELA [84] to allow the designer to automatically verify the consistency between both diagrams.…”

Section: Verification Of Uml Modelsmentioning

confidence: 99%

Lightweight and static verification of UML executable models

Planas

Cabot

Gómez

2016

Computer Languages, Systems & Structures

View full text Add to dashboard Cite

A la meva família, per acompanyar-me en aquest camí.A dissertation presented by Elena Planas Hortal in partial fulfillment of the requirements for the degree of Doctor per la Universitat Politècnica de Catalunya Barcelona, February 10, 2013 Agraïments Doing a PhD thesis is a lonely task that cannot be carried out alone. AnonymAquesta tesiés el resultat d'uns quants anys de feina, durant els quals he rebut el suport, tan professional com personal, de moltes persones. Aquests agraïments són per tots vosaltres.En primer lloc, vull donar les gràcies als meus directors de tesi, al Dr. Jordi Cabot i a la Dra. Cristina Gómez, per donar-me l'oportunitat de treballar i aprendre al seu costat. Al Jordi, moltes gràcies per aportar una visió clara i resolutiva dels problemes, pels seus consells precisos que sempre m'han resultat moltútils i per la seva disponibilitat des de qualsevol lloc del món. A la Cristina, moltes gràcies pel seu rigor científic i grau d'exigència, i també per la seva proximitat, dedicació i interès constant. A tots dos, moltes gràcies per la vostra orientació i suport que m'han permès arribar fins aquí.Moltíssimes gràcies a totes les persones que han col.laborat directament amb el desenvolupament d'aquesta tesi. Un agraïment molt especial al David Sánchez, per haver-me ajudat amb la implementació de la tesi, però sobretot pel seu entusiasme en tot moment. També a l'Esther Guerra i al Juan de Lara, per permetre'm ampliar la visió del meu propi treball aplicant-lo a d'altres camps.També vull donar les gràcies als examinadors d'aquesta tesi: el Dr. Antoni Olivé i a la Dra. Ruth Raventós, de la Universitat Politècnica de Catalunya (UPC), al Dr. Robert Clarisó, de la Universitat Oberta de Catalunya (UOC), al Dr. Vicente Pelechano, de la Universitat Politècnica de València (UPV) i al Dr. Manuel Wimmer, de la Vienna University of Technology (TUWien) per acceptar formar part del tribunal. També, als revisors externs que van llegir una versió prèvia d'aquesta tesi i em van fer arribar els seus suggeriments per millorar-la.A tots els meus companys del Grup de Modelització Conceptual (GMC): Gràcies pels vostres comentaris i consells al llarg del desenvolupament d'aquesta tesi. Un agraïment especial a l'Antonio Villegas i al David Aguilera, per proporcionar-me la plantilla d'aquesta tesi i resoldre els meus dubtes de L A T E X amb una rapidesa increïble.A tots els companys i amics dels estudis d'Informàtica, Multimèdia i Telecomunicació de la UOC. Al Josep Prieto, per donar-me totes les facilitats per poder acabar aquesta tesi. Al Santi Caballé i a l'Elena Rodríguez, per haver-se fet càrrec de les meves assignatures mentre jo he estat redactant aquest document. Als meus companys de despatx, el David Bañeres i el Jordi Conesa, pels moments compartits al llarg de tots aquests anys. A l'Àgata Lapedriza, l'Àngels Rius, i tants d'altres, per formar part del meu dia dia.A very special acknowledgment (in english) to all my dutch collegues from the Software Engineering and Technology group (SET) at the Eindhoven Unive...

show abstract

“…To ensure such high quality models, the predominantly code-centric testing strategies must be complemented with approaches for testing at the model-level. Such model-level tests help detect errors at an early development stage (see, e.g., [3], [4]). …”

Section: Introductionmentioning

confidence: 99%

Comparing Three Notations for Defining Scenario-Based Model Tests: A Controlled Experiment

Hoisl

Sobernig

Strembeck

2014

2014 9th International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

Abstract-Scenarios are an established means to specify requirements for software systems. Scenario-based tests allow for validating software models against such requirements. In this paper, we consider three alternative notations to define such scenario tests on structural models: a semi-structured natural-language notation, a diagrammatic notation, and a fully-structured textual notation. In particular, we performed a study to understand how these three notations compare to each other with respect to accuracy and effort of comprehending scenario-test definitions, as well as with respect to the detection of errors in the models under test. 20 software professionals (software engineers, testers, researchers) participated in a controlled experiment based on six different comprehension and maintenance tasks. For each of these tasks, questions on a scenario-test definition and on a model under test had to be answered. In an ex-post questionnaire, the participants rated each notation on a number of dimensions (e.g., practicality or scalability). Our results show that the choice of a specific scenario-test notation can affect the productivity (in terms of correctness and time-effort) when testing software models for requirements conformance. In particular, the participants of our study spent comparatively less time and completed the tasks more accurately when using the natural-language notation compared to the other two notations. Moreover, the participants of our study explicitly expressed their preference for the natural-language notation.

show abstract

Towards Scenario-Based Testing of UML Diagrams

Cited by 16 publications

References 6 publications

Guided Merging of Sequence Diagrams

Guided Merging of Sequence Diagrams

Lightweight and static verification of UML executable models

Comparing Three Notations for Defining Scenario-Based Model Tests: A Controlled Experiment

Contact Info

Product

Resources

About