My first SMS in the IST (IF 2018: 2.921 - Q1 in SE)

A bunch of letters and numbers only understandable for some of us :D

For the researchers conducting Systematic Mapping Studies (SMS) and Systematic Literature Reviews (SLR), they understand the work behind an SMS or SLR publication. Nine researchers from three institutions working during almost three years conducting the study and preparing the paper. After all this time, our paper is already in press (since November 12th) in the Information and Software Technology journal (IF 2018: 2.921).

Management of quality requirements in agile and rapid software development: A systematic mapping study

Woubshet Behutiye, Pertti Karhapää, Lidia López, Xavier Burgués, Silverio Martínez-Fernández, Anna MariaVollmer, Pilar Rodríguez, Xavier Franch, and Markku Oivo

Abstract. 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.

Paper accepted at the CAiSE Forum 2018

Q-Rapids Tool Prototype: Supporting Decision-Makers in Managing Quality in Rapid Software Development

Lidia López, Silverio Martínez-Fernández, Cristina Gómez, Michał Choraś, Rafał Kozik, Liliana Guzmán, Anna Maria Vollmer, Xavier Franch, Andreas Jedlitschka

Abstract. Software quality is an essential competitive factor for the success of software companies today. Increasing the software quality levels of software products and services requires an adequate integration of quality requirements (QRs) in the software life-cycle, which is still scarcely supported in current rapid software development (RSD) approaches. One of the goals of the Q-Rapids (Quality-aware Rapid Software Development) method is providing tool support to decision-makers for QR management in RSD. The Q-Rapids method is based on gathering data from several and heterogeneous sources, to be aggregated into quality-related strategic indicators (e.g., customer satisfaction, product quality) and presented to decision-makers using a highly informative dashboard. The current release of Q-Rapids Tool provides four sets of functionality: (1) data gathering from source tools (e.g. GitLab, Jira, SonarQube, and Jenkins), (2) aggregation of data into three levels of abstraction (metrics, product/process factors, and strategic indicators), (3) visualization of the aggregated data, and (4) navigation through the aggregated data. The tool  has been evaluated by four European companies that follow RSD processes.

Paper accepted at 30th International Conference on Advance Information Systems Engineering (CAiSE 2018)

Data-Driven Elicitation, Assessment and Documentation of Quality Requirements in Agile Software Development

Xavier Franch, Cristina Gómez, Andreas Jedlitschka, Lidia López, Silverio Martínez-Fernández, Marc Oriol, Jari Partanen

Abstract. Quality Requirements (QRs) are difficult to deal with in agile software development. Given the pressure to deploy fast, quality concerns are often sacrificed for the sake of richer functionality. In addition, artefacts like user stories are not particularly well-suited for representing QRs. In this exploratory paper, we envisage a data-driven method, called Q-Rapids, to QR elicitation, assessment and documentation in agile software development. Q-Rapids proposes: 1) The collection and analysis of design and runtime data in order to raise quality alerts; 2) The suggestion of candidate QRs to address these alerts; 3) A strategic analysis of the impact of such requirements by visualizing their effect on a set of indicators rendered in a dashboard; 4) The documentation of the requirements (if finally accepted) in the backlog. The approach is illustrated with three scenarios evaluated through a questionnaire by experts from a telecom company.

Paper accepted at the 1st International Workshop on Managing Quality in Agile and Rapid Software Development Processes

Agile Quality Requirements Management Best Practices Portfolio: A Situational Method Engineering Approach 

Lidia López, Woubshet Behutiye, Pertti Karhapää, Jolita Ralyté, Xavier Franch and Markku Oivo

Abstract.  Management of Quality Requirements (QRs) is determinant for the success of software projects. However, this management is currently under-considered in software projects and in particular, in agile methods. Although agile processes are focused on the functional aspects of the software, some agile practices can be beneficial for the management of QRs. For example, the collaboration and interaction of people can help in the QR elicitation by reducing vagueness of requirements through communication. In this paper, we present the initial find-ings of our research investigating what industrial practices, from the agile methods, can be used for better management of QRs in agile software development. We use Situational Method Engineering to identify, complement and classify a portfolio of best practices for QR management in agile environments. In this regard, we present the methodological approach that we are applying for the defini-tion of these guidelines and the requirements that will lead us to compile a portfo-lio of agile QR management best practices. The proposed requirements correspond to the whole software life cycle starting in the elicitation and finalizing in the deployment phases.

Co-located to the 18th International Conference on Product-Focused Software Process Improvement (PROFES 2017).