An automated Model-based Testing Approach in Software Product Lines Using a Variability Language.

This paper presents the application of an automated testing approach for Software Product Lines (SPL) driven by its state-machine and variability models. Context: Model-based testing provides a technique for automatic generation of test cases using models. Introduction of a variability model in this technique can achieve testing automation in SPL. Method: We use UML and CVL (Common Variability Language) models as input, and JUnit test cases are derived from these models. This approach has been implemented using the UML2 Eclipse Modeling platform and the CVL-Tool. Validation: A model checking tool prototype has been developed and a case study has been performed. Conclusions: Preliminary experiments have proved that our approach can find structural errors in the SPL under test. In our future work we will introduce Object Constraint Language (OCL) constraints attached to the input UML mode

Formalizing relations between use cases in the unified modeling language

The Unified Modeling Language (UML) is a semi-formal graphical language that has been accepted as standard to model object-oriented software systems. This language defines various kinds of diagrams that are used to describe different aspects or views of a system. In particular, Use Cases diagrams are used to capture the requirements of the systems and to guide their development process. The different Use Cases defined throughout a development process are not independent but it is possible to set relations between them. The main relations considered by UML are the following: Generalization, Include and Extend. These relations as well as the remaining UML constructs are semi-formally defined, giving place to ambiguous interpretations and inconsistencies.\nThis paper presents a formalization that gives precision to the definition of the main relations between Use Cases. This formalization will allow us to check consistency when incrementing the Use Cases model during the software development process and when relating Use Cases model with others modelsÁrea: Informática Teórica - Inteligencia Artificial - Lenguajes - Compiladore

Formalizing relations between use cases in the unified modeling language

The Unified Modeling Language (UML) is a semi-formal graphical language that has been accepted as standard to model object-oriented software systems. This language defines various kinds of diagrams that are used to describe different aspects or views of a system. In particular, Use Cases diagrams are used to capture the requirements of the systems and to guide their development process. The different Use Cases defined throughout a development process are not independent but it is possible to set relations between them. The main relations considered by UML are the following: Generalization, Include and Extend. These relations as well as the remaining UML constructs are semi-formally defined, giving place to ambiguous interpretations and inconsistencies. This paper presents a formalization that gives precision to the definition of the main relations between Use Cases. This formalization will allow us to check consistency when incrementing the Use Cases model during the software development process and when relating Use Cases model with others modelsÁrea: Informática Teórica - Inteligencia Artificial - Lenguajes - CompiladoresRed de Universidades con Carreras en Informática (RedUNCI

The Modelling Journey

These were slides developed as part of our work with the JISC Community Engagement Team and CETIS to introduce people to different forms of system modelling, including scenarios and personas, soft systems methods, UML (Use cases, activity diagrams and sequence diagrams), BMPN and EA modelling with Archimate

The Role of ¨Roles¨ in Use Case Diagrams

Use cases are the modeling technique of UML for formalizing the functional requirements placed on systems. This technique has limitations in modeling the context of a system, in relating systems involved in a same business process, in reusing use cases, and in specifying various constraints such as execution constraints between use case occurrences. These limitations can be overcome to some extent by the realization of multiple diagrams of various types, but with unclear relationships between them. Thus, the specification activity becomes complex and error prone. In this paper, we show how to overcome the limitations of use cases by making the roles of actors explicit. Interestingly, our contributions not only make UML a more expressive specification language, they also make it simpler to use and more consistent

Practical Application Of Uml Activity Diagrams For The Generation Of Test Cases

Software testing and debugging represents around one third of total effort in development projects. Different factors which have influence on poor practices of testing have been identified through specific surveys. Amongst several, one of the most important is the lack of efficient methods to exploit development models for generating test cases. This paper presents a new method for automatically generating a complete set of functional test cases from UML activity diagrams complementing specification of use cases. Test cases are prioritized according to software risk information. Results from experiences with more than 70 software professionals/experts validate benefits of the method. Participants also confirm its interest and effectiveness for testing needs of industry

Designing tool support for translating use cases and UML 2.0 Sequence Diagrams into a Coloured Petri Net

Using a case study on the specification of an elevator controller, this paper presents an approach that can translate given UML descriptions into a Coloured Petri Net (CPN) model. The UML descriptions must be specified in the form of Use Cases and UML 2.0 Sequence Diagrams. The CPN model constitutes one single, coherent and executable representation of all possible behaviours that are specified by the given UML artefacts. CPNs consitute a formal modelling language that enables construction and analysis of scalable, executable models of behaviour. A combined use of UML and CPN can be useful in several projects. CPN is well supported by CPN Tools and the work we present here is aimed at building a CPN Tools front-end engine that implements the proposed translation.Fundação para a Ciência e a Tecnologia (FCT) - SFRH/BSAB/607/200

Use cases in software development: an investigation in its roles and values

This research work identifies the roles and values of USE CASES in software development, and analysed the concept of USE CASES critically in other to ascertain their usefulness in achieving a user’s requirement when applied to a system development methodology. We examined the major considerations for deploying advanced UML modelling by considering the best approach for a programmer to get to the source code by putting the right aspect of the UML to work at the right stage of a system life cycle in an object (OO) oriented analysis and design practice. research has found out that to achieve a successful object oriented programming design and implementation, an analyst should strive to drive an OO software design from USE CASE

On Use Cases and Their Relationships in the Unified Modelling Language

. In the Unified Modelling Language, use cases are provided as a way of summarising the requirements on a system. They are defined informally as specifications of sets of sequences of actions, and several relationships between use cases are informally defined. Dependable, tool-supported software development necessitates precise definitions of all these concepts but the topic has so far received little attention in the literature, beyond what is present in Catalysis. This paper explores how these notions can be formalised whilst staying as close as possible to the UML standard, makes some suggestions and raises further questions. 1 Introduction The Unified Modelling Language has been widely adopted as a standard language for modelling the design of (software) systems. Nevertheless, certain aspects of UML are not yet defined precisely. This paper is concerned with one such aspect: use cases and their relationships. The relationship between a use case and its constituent actions, and es..