Navegación

Búsqueda

Búsqueda avanzada

Resultados de búsqueda para experiment

Evaluating TESTAR’s effectiveness through code coverage

Testing is of paramount importance in assuring the quality of software products. Nevertheless, it is not easy to judge which techniques or tools are the most effective. A commonly used surrogate metric to evaluate the effectiveness of testing tools is code coverage, which has been widely used for unit and integration testing. However, for GUI testing approaches, this metric has not been sufficiently investigated. To fill this gap, we run experiments with the TESTAR tool, a scriptless testing tool that automatically generates test cases at the GraphicalUser Interface (GUI) level. In the experiment, we analyze and compare the obtained code coverage when using four different action selection mechanisms (ASMs) in TESTAR that are used to test three SUTs.

Autores: Aaron van der Brugge / Fernando Pastor Ricos / Pekka Aho / Beatriz Marín / Tanja E.J. Vos / 
Palabras Clave: Code Coverage - Effectiveness - experiment - GUI testing

Empirical software product line engineering: A systematic literature review. An IST journal publication

The adoption of Software Product Line Engineering (SPLE) is usually only based on its theoretical benefits instead of empirical evidences. In fact, there is no work that synthesizes the empirical studies on SPLE. This makes it difficult for researchers to base their contributions on previous works validated with an empirical strategy. The objective of this work is to discover and summarize the studies that have used empirical evidences in SPLE limited to those ones with the intervention of humans. This will allow evaluating the quality and to know the scope of these studies over time. Doing so, research opportunities can arise. A systematic literature review was conducted. The scope of the work focuses on those studies in which there is human intervention and were published between 2000 and 2018. We considered peer-reviewed papers from journals and top software engineering conferences. Out of a total of 1880 studies in the initial set, a total of 62 primary studies were selected after applying a series of inclusion and exclusion criteria. We found that, approximately 56+AFwAJQ of the studies used the empirical case study strategy while the rest used experimental strategies. Around 86+AFwAJQ of the case studies were performed in an industrial environment showing the penetration of SPLE in industry. The interest of empirical studies has been growing since 2008. Around 95.16+AFwAJQ of the studies address aspects related to domain engineering while application engineering received less attention. Most of the experiments and case study evaluated showed an acceptable level of quality. The first study found dates from 2005 and since then, the interest in the empirical SPLE has increased.

Autores: Ana E. Chacón-Luna / Antonio Manuel Gutiérrez / José A. Galindo / David Benavides / 
Palabras Clave: Case Study - Empirical strategies - experiment - software product lines - Systematic literature review

MDD vs. traditional software development: A practitioner’s subjective perspective

Today practitioners have a myriad of methods from which to choose for the development of software applications. However they lack empirical data that characterize these methods in terms of usefulness, ease of use or compatibility, all of them relevant variables to assess the developer’s intention to use them. In this context, we propose to compare three methods, each following a different paradigm (Model-Driven, Model-Based and the traditional, code-centric, respectively) with respect to its intention to use by junior software developers while developing the business layer of a Web 2.0 application. To do that, we have conducted an experiment with graduate students of the University of Alicante. The application developed was a Social Network, which was organized in three different modules. Subjects were asked to use a different method for each one of the three modules, and then answer a questionnaire that gathered their perceptions during its use. The results show that the method that followed the Model-Driven development paradigm is regarded as the most useful, although it is also regarded as the more difficult to use. They also show that junior software developers feel comfortable with the use of models, and are likely to use them if accompanied by a model-driven development environment.

Autores: Yulkeidi Martínez / Cristina Cachero / Santiago Meliá / 
Palabras Clave: code-centric development - compatibility - ease of use - experiment - intention to use - MBD - MDD - usefulness

No encuentra los resultados que busca? Prueba nuestra Búsqueda avanzada