Quality of an open source software ecosystem (OSS ecosystem) is key for different ecosystem actors such as contributors or adopters. In fact, the consideration of several quality aspects(e.g., activeness, visibility, interrelatedness, etc.) as a whole may provide a measure of the healthiness of OSS ecosystems. The more health a OSS ecosystem is, the more and better contributors and adopters it will gather. Some research tools have been developed to gather specific quality information from open source community data sources. However, there exist no frameworks available that can be used to evaluate their quality as a whole in order to obtain the health of an OSS ecosystem. To assess the health of these ecosystems, we propose to adopt robust principles and methods from the Service Oriented Computing field.
Autores: Oscar Franco-Bedoya / Marc Oriol / Carlos Müller / Jordi Marco / Pablo Fernández / Manuel Resinas / Xavier Franch / Antonio Ruiz-Cortés /
Palabras Clave:
Autores: Cristina Palomares, Carme Quer, Xavier Franch Revista: Empirical Software Engineering (Springer), in press DOI: http://dx.doi.org/10.1007/s10664-016-9485-x JCR IF 2015: 1.393 (27/106 de la categoría de ingeniería del software)
Autores: Cristina Palomares / Carme Quer / Xavier Franch /
Palabras Clave: exploratory survey - online questionnaire - requirements engineering - software rerquirement patterns
Context: Tertiary studies in software engineering (TS@SE) are widely used to synthesise evidence on a research topic systematically. As part of their protocol, TS@SE define inclusion and exclusion criteria (IC/EC) aimed at selecting those secondary studies (SS) to be included in the analysis. Aims: To provide a state of the art on the definition and application of IC/EC in TS@SE, and from the results of this analysis, we outline an emerging framework, TSICEC, to be used by SE researchers. Method: To provide the state of the art, we conducted a systematic mapping (SM) combining automatic search and snowballing over the body of SE scientific literature, which led to 50 papers after application of our own IC/EC. The extracted data was synthesised using content analysis. The results were used to define a first version of TSICEC. Results: The SM resulted in a coding schema, and a thorough analysis of the selected papers on the basis of this coding. Our TSICEC framework includes guidelines for the definition of IC/EC in TS@SE. Conclusion: This paper is a step forward establishing a foundation for researchers in two ways. As authors, understanding the different possibilities to define IC/EC and apply them to select SS. As readers, having an instrument to understand the methodological rigor upon which TS@SE may claim their findings.
Autores: Dolors Costal / Carles Farré / Xavier Franch / Carme Quer /
Palabras Clave: Inclusion and exclusion criteria - Systematic Mapping Study - Tertiary studies
Context: Modern services and applications need to react to changes in their context (e.g. location, memory consumption, number of users) to improve the user+IBk-s experience. To obtain this context, a monitoring infrastructure with adequate functionality and quality levels is required. But this monitoring infrastructure needs to react to the context as well, raising the need for context-aware monitoring tools. Objective: Provide a generic solution for context-aware monitoringable to effectively react to contextual changes. Method: We have designed CAMA, a service-oriented Context-Aware Monitoring Architecture that can be easily configured, adapted and evolved according to contextual changes. CAMA implements a decoupled architecture and manages a context domain ontology for modelling the inputs, outputs and capabilities of monitoring tools. Results: CAMA has been demonstrated in three real use cases. We have also conducted different evaluations, including an empirical study. The results of the evaluations show that (1) the overhead introduced by the architecture does not degrade the behavior of the system, except in extreme conditions; (2) the use of ontologies is not an impediment for practitioners, even when they have little knowledge about this concept; and (3) the reasoning capabilities of CAMA enable context-aware adaptations. CAMA is a solution useful for both researchers and practitioners. Researchers can use this architecture as a baseline for providing different extensions or implementing new approaches on top of CAMA that require context-aware monitoring. Practitioners may also use CAMA in their projects in order to manage contextual changes in an effective way.
Autores: Oscar Cabrera / Marc Oriol / Xavier Franch / Jordi Marco /
Palabras Clave: Context acquisition - Context life cycle - Context ontology - Context-aware computing - Software adaptation - Software reconfiguration
Autores: Alessia Knauss, Daniela Damian, Xavier Franch, Angela Rook, Hausi A. Müller, Alex Thomo Revista: Informacion & Software Technology 70: 85-99 (2016) DOI: http://dx.doi.org/10.1016/j.infsof.2015.10.001 JCR IF 2015: 1.569 (primer cuartil de la categoría de ingeniería del software) 3 citas (excluyendo self-citations)
Autores: Alessia Knauss / Daniela Damian / Xavier Franch / Angela Rook / Hausi A. Müller / Alex Thomo /
Palabras Clave: Contextual requirements - requirements engineering - Self-adaptive systems
Context. Quality requirements (QRs) describe the desired quality of software, and they play an important role in the success of software projects. In agile software development (ASD), QRs are often ill-defined and not well addressed due to the focus on quickly delivering functionality. Rapid software development (RSD) approaches (e.g., continuous delivery and continuous deployment), which shorten delivery times, are more prone to neglect QRs. Despite the significance of QRs in both ASD and RSD, there is limited synthesized knowledge on their management in those approaches.Objective.This study aims to synthesize state-of-the-art knowledge about QR management in ASD and RSD, focusing on three aspects: bibliometric, strategies, and challenges.Research method.Using a systematic mapping study with a snowballing search strategy, we identified and structured the literature on QR management in ASD and RSD.Results.We found 156 primary studies: 106 are empirical studies, 16 are experience reports, and 34 are theoretical studies. Security and performance were the most commonly reported QR types. We identified various QR management strategies: 74 practices, 43 methods, 13 models, 12 frameworks, 11 advices, 10 tools, and 7 guidelines. Additionally, we identified 18 categories and 4 non-recurring challenges of managing QRs. The limited ability of ASD to handle QRs, time constraints due to short iteration cycles, limitations regarding the testing of QRs and neglect of QRs were the top categories of challenges.Conclusion.Management of QRs is significant in ASD and is becoming important in RSD. This study identified research gaps, such as the need for more tools and guidelines, lightweight QR management strategies that fit short iteration cycles, investigations of the link between QRs challenges and technical debt, and extension of empirical validation of existing strategies to a wider context. It also synthesizes QR management strategies and challenges, which may be useful for practitioners.
Autores: Woubshet Behutiye / Pertti Karhapäa / Lidia Lopez / Xavier Burgués / Silverio Martínez-Fernández / Anna Maria Vollmer / Pilar Rodríguez / Xavier Franch / Markku Oivo /
Palabras Clave: Agile software development - Non-functional requirements - quality requirements - Rapid software development - Systematic literature reviews - Systematic Mapping Study
Requirements elicitation and analysis is a key step in designing and maintaining data warehouses. In order to better support this step, in this paper we (i) propose an extension of the basic goaloriented metamodel in order to include semantic modules, (ii) include a description of each step followed in the process, and (iii) evaluate it by means of an empirical experiment.
Autores: Alejandro Maté / Juan Trujillo / Xavier Franch /
Palabras Clave: Data warehouses - i-star - user requirements
