Data-driven elicitation of quality requirements in agile companies

Quality Requirements (QRs) are a key artifact to ensure the quality and success of a software system. Despite its importance, QRs have not reached the same degree of attention as its functional counterparts, especially in the context of trending software development methodologies like Agile Software Development (ASD). Moreover, crucial information that can be obtained from data sources of a project under development (e.g. JIRA, github,…) are not fully exploited, or even neglected, in QR elicitation activities. In this work, we present a data-driven approach to semi-automatically generate and document QRs in the context of ASD. We define an architecture focusing on the process and the artefacts involved. We validate and iterate on such architecture by conducting workshops in four companies of different size and profile. Finally, we present the implementation of such architecture, considering the feedback and outcomes of the conducted workshops.Peer ReviewedPostprint (author's final draft

Technical debt and waste in non-functional requirements documentation:an exploratory study

Background: To adequately attend to non-functional requirements (NFRs), they must be documented; otherwise, developers would not know about their existence. However, the documentation of NFRs may be subject to Technical Debt and Waste, as any other software artefact. Aims: The goal is to explore indicators of potential Technical Debt and Waste in NFRs documentation. Method: Based on a subset of data acquired from the most recent NaPiRE (Naming the Pain in Requirements Engineering) survey, we calculate, for a standard set of NFR types, how often respondents state they document a specific type of NFR when they also state that it is important. This allows us to quantify the occurrence of potential Technical Debt and Waste. Results: Based on 398 survey responses, four NFR types (Maintainability, Reliability, Usability, and Performance) are labelled as important but they are not documented by more than 22% of the respondents. We interpret that these NFR types have a higher risk of Technical Debt than other NFR types. Regarding Waste, 15% of the respondents state they document NFRs related to Security and they do not consider it important. Conclusions: There is a clear indication that there is a risk of Technical Debt for a fixed set of NFRs since there is a lack of documentation of important NFRs. The potential risk of incurring Waste is also present but to a lesser extent

Dataset for the systematic mapping study 'Management of quality requirements in agile and rapid software development: A systematic mapping study' https://doi.org/10.1016/j.infsof.2019.106225

The data-set includes list of the primary studies and different classifications and mappings reported in the systematic mapping study, Management of quality requirements in agile and rapid software development: A systematic mapping study. Behutiye, W., Karhapää, P., Lopez, L., Burgués, X., Martínez-Fernández, S., Vollmer, A. M., ... & Oivo, M. (2019). Management of quality requirements in agile and rapid software development: a systematic mapping study. Information and Software Technology. 106225. https://doi.org/10.1016/j.infsof.2019.106225 The dataset includes four excel files that describe the findings and classifications reported in the study as follows. - Primary studies and classification.xlsx Present the list of 156 primary studies and the result of their classification by research method, author affiliation, venue , publication year and contexts -ICB domain classification.xlsx Presents the ICB domain classification of the domains reported in the primary studies - Distribution of quality requirement types.xlsx Presents the result of the distribution of quality requirement types reported in the study - Mapping QR management strategies to challenges.xlsx Presents the mapping of the Quality requirement management strategies to challenges reported in the stud

Toward a better understanding and support of quality requirement documentation in agile software development

Abstract Software applications and services are essential parts of our daily lives. In today’s vibrant and rapidly changing business world, ensuring the quick delivery of quality software is important. Agile software development (ASD) has been widely adopted in the software industry owing to its capabilities for rapidly delivering valuable software. However, the findings from research reveal that ASD faces challenges regarding the documentation and management of quality requirements (QRs). QRs portray how well software performs its functions, and play a crucial role for the success of software. ASD studies reveal that QRs are often neglected, underspecified, not documented, and managed improperly. These often result in increased maintenance costs and system quality degradation. Examining QR documentation is valuable in obtaining a better understanding about the topic. It also helps in building guidelines and models that support QR documentation in ASD, which is a research gap. This dissertation aims to synthesize a better understanding about the documentation of QRs in ASD and to support QR documentation tasks in ASD. In order to achieve this, it first explored the state of the art of the management of QRs in ASD through a systematic mapping study. Then, it examined the state of the QR documentation practices in ASD through two multiple case studies. Next, a design science research methodology was applied to build Agile QR-Doc guidelines. The dissertation complements the literature with empirical knowledge on QR documentation practices, tools and artifacts and related stakeholders involved in QR documentation in ASD. It reveals the significance of documenting QRs, gives insight into aspects practitioners consider important when documenting QRs and a better understanding about factors influencing QR documentation in ASD. It also developed Agile QR-Doc guidelines and a model to support QR documentation in ASD. The guidelines have been validated by practitioners. They identified them as relevant, useful, understandable, and simple enough to use in supporting QR documentation tasks in ASD. The knowledge from the research can help practitioners proactively approach QR documentation tasks in ASD. For researchers, the dissertation offers the synthesis of empirical knowledge on QR documentation in ASD and identifies opportunities for future studies.Tiivistelmä Ohjelmistosovellukset ja -palvelut ovat olennainen osa jokapäiväistä elämäämme. Nykypäivän vilkkaassa ja nopeasti muuttuvassa yritysmaailmassa on olennaista taata laadukkaan ohjelmiston ripeä toimittaminen. Ketterä ohjelmistokehitys (ASD eng. Agile software development) on otettu laajalti käyttöön ohjelmistoteollisuudessa, koska sen ansiosta kyetään toimittamaan arvokkaita ohjelmistoja nopeasti. Tutkimustulokset osoittavat kuitenkin, että laatuvaatimusten (QRs eng. quality requirements) dokumentointi ja hallinta on haasteellista ASD:ssä. Laatuvaatimukset kuvaavat, kuinka hyvin ohjelmisto suorittaa toiminnallisuutensa, ja niillä on ratkaiseva rooli ohjelmiston menestyksen kannalta. Tutkimukset ASD-kontekstissa osoittavat, että laatuvaatimuksia laiminlyödään, niitä ei spesifioida tarpeeksi, niitä ei dokumentoida ja niitä hallinnoidaan väärin. Nämä johtavat usein kohonneisiin ylläpitokustannuksiin ja järjestelmän laadun heikkenemiseen. QR-dokumentoinnin tutkiminen on ensiarvoista aiheen paremman käsityksen kannalta. Sen avulla kyetään kehittämään ohjeita ja malleja tukemaan QR-dokumentointia ASD:ssä, joka on osoitettu tutkimuksessa puutteelliseksi. Väitöskirjan tavoitteena on lisätä ymmärrystä QR-dokumentoinnista ASD:ssä ja tukea sitä ASD:ssä. Tämän saavuttamiseksi väitöskirja tutkii ensin QR-hallintaa ASD:ssä systemaattisen kartoitustutkimuksen kautta. Tämän jälkeen tarkastellaan QR-dokumentoinnin tilaa ohjelmistoteollisuudessa kahden monitapaustutkimuksen avulla. Seuraavaksi kehitetään QR-Doc-ohjeistus laatuvaatimusten dokumentointiin ASD:ssä kehitystutkimusmenetelmää soveltaen. Tämä väitöskirja täydentää QR-dokumentointiin liittyvää tutkimustietoa empiirisellä tiedolla käytänteistä, työkaluista ja artefakteista sekä QR-dokumentointiin liittyvistä sidosryhmistä. Väitöskirja tuo ilmi QR-dokumentoinnin tärkeyden, valaisee ammatinharjoittajien tärkeinä pitämiä näkökulmia QR-dokumentoinnissa sekä auttaa ymmärtämään QR-dokumentointiin vaikuttavia tekijöitä ASD:ssä paremmin. Se esittää myös QR-Doc-ohjeistuksen sekä mallin, joka tukee QR-dokumentointia ASD:ssä. Kehitetty ohjeistus on arvioitu ammatinharjoittajien toimesta. Ohjeistus miellettiin oleelliseksi, hyödylliseksi, ymmärrettäväksi ja riittävän helppokäyttöiseksi, jotta se tukee QR-dokumentointia ASD:ssä. Tutkimuksesta saatu tieto auttaa ammatinharjoittajia lähestymään QR-dokumentointitehtäviä proaktiivisesti. Väitöskirja tarjoaa tutkijoille koottua empiiristä tietoa QR-dokumennista ASD:ssä sekä mahdollisuuksia jatkotutkimukselle

Dataset for the systematic mapping study 'Management of quality requirements in agile and rapid software development: A systematic mapping study' https://doi.org/10.1016/j.infsof.2019.106225

The data-set includes list of the primary studies and different classifications and mappings reported in the systematic mapping study, Management of quality requirements in agile and rapid software development: A systematic mapping study. Behutiye, W., Karhapää, P., Lopez, L., Burgués, X., Martínez-Fernández, S., Vollmer, A. M., ... & Oivo, M. (2019). Management of quality requirements in agile and rapid software development: a systematic mapping study. Information and Software Technology. 106225. https://doi.org/10.1016/j.infsof.2019.106225 The dataset includes four excel files that describe the findings and classifications reported in the study as follows. - Primary studies and classification.xlsx Present the list of 156 primary studies and the result of their classification by research method, author affiliation, venue , publication year and contexts -ICB domain classification.xlsx Presents the ICB domain classification of the domains reported in the primary studies - Distribution of quality requirement types.xlsx Presents the result of the distribution of quality requirement types reported in the study - Mapping QR management strategies to challenges.xlsx Presents the mapping of the Quality requirement management strategies to challenges reported in the stud

Non-functional requirements documentation in agile software development:challenges and solution proposal

Abstract Non-functional requirements (NFRs) are determinant for the success of software projects. However, they are characterized as hard to define, and in agile software development (ASD), are often given less priority and usually not documented. In this paper, we present the findings of the documentation practices and challenges of NFRs in companies utilizing ASD and propose guidelines for enhancing NFRs documentation in ASD. We interviewed practitioners from four companies and identified that epics, features, user stories, acceptance criteria, Definition of Done (DoD), product and sprint backlogs are used for documenting NFRs. Wikis, word documents, mockups and spreadsheets are also used for documenting NFRs. In smaller companies, NFRs are communicated through white board and flip chart discussions and developers’ tacit knowledge is prioritized over documentation. However, loss of traceability of NFRs, the difficulty in comprehending NFRs by new developers joining the team and limitations of documentation practices for NFRs are challenges in ASD. In this regard, we propose guidelines for documenting NFRs in ASD. The proposed guidelines consider the diversity of the NFRs to document and suggest different representation artefacts depending on the NFRs scope and level of detail. The representation artefacts suggested are among those currently used in ASD in order not to introduce new specific ones that might hamper actual adoption by practitioners

Quality requirement documentation guidelines for agile software development

Abstract In agile software development (ASD), where minimal documentation and rapid delivery are the focus, Quality requirements (QRs) are often underspecified and not documented. Guidelines supporting QR documentation task are scarce. The study developed the Agile QR-Doc QR documentation guidelines, which aim to support QR documentation in ASD. We applied a design science research methodology (DSRM) to build the Agile QR-Doc. We used a survey questionnaire and open discussion with ten software practitioners, from two ASD companies to validate the Agile QR-Doc. The practitioners evaluated the guidelines in terms of usefulness, relevance, understandability, and coverage of important aspects for supporting QR documentation and their impact on the agility of the software development process. Agile QR-Doc list 12 recommendations that are grouped into two categories. The first category introduces three recommendations that focus on raising awareness about the significance of QRs, their documentation and related challenges. The second category lists nine recommendations that introduce artifacts, practices and important aspects for documenting QRs. The validation reveals the relevance, understandability and usefulness of the guidelines to support QR documentation in ASD. It also indicates that the guidelines consider important aspects for documenting QRs and that they do not negatively affect the agility of the software development process. Practitioners can utilize the practices, artifacts and knowledge from the guidelines to support QR documentation in ASD. Researchers can benefit from the knowledge on QR documentation in ASD, and application of DSRM in building artifacts

How agile software development practitioners perceive the need for documenting quality requirements:a multiple case study

Abstract Agile software development (ASD) promotes minimal documentation and often prioritizes functional requirements over quality requirements (QRs). This may be beneficial in reducing the time to market of software. When considering QRs in ASD, the minimal documentation practice may be seen as a concern since QRs determine the success of software projects and are as well not easy to specify and document. Nevertheless, what do practitioners think of the necessity of documenting QRs in ASD? How do they perceive factors that may affect documentation of QRs in ASD? We conducted a multiple case study of three cases applying ASD, involving 12 participants. ASD practitioners identify that it is important to document QRs, and perceive that it contributes to ensuring quality, clarifying QRs, and helping in decision making. Time constraint, QR awareness and communication gaps on QRs influence the documentation of QRs in ASD. ASD teams may align their documentation practices to fit the sprint duration. The influence of QR awareness on documentation was dependent on project context and roles. Communication gaps can create confusion on QRs. Missing and outdated QR documentation may result in accruing technical debt, and lack of common understanding on QRs. The study synthesizes empirical evidence on the significance of documenting QRs in ASD and provides an insight into factors affecting documentation of QRs in ASD

Agile quality requirements management best practices portfolio:a situational method engineering approach

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 findings 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 definition of these guidelines and the requirements that will lead us to compile a portfolio 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

Towards optimal quality requirement documentation in agile software development:a multiple case study

Abstract Context: Agile software development (ASD) promotes minimal documentation and often prioritizes functional requirements over quality requirements (QRs). The minimal documentation emphasis may be beneficial in reducing time-to-market for software. However, it can also be a concern, especially with QRs, since they are challenging to specify and document and are crucial for software success. Therefore, understanding how practitioners perceive the importance of QR documentation is valuable because it can provide insight into how they approach this task. It also helps in developing models and guidelines that support the documentation of QRs in ASD, which is a research gap. Objective: We aim to understand practitioners’ perceptions of QR documentation and factors influencing this task to derive a model that supports optimal QR documentation in ASD. Method: We conducted a multiple case study involving 12 participants from three cases that apply ASD. Results: Practitioners identify QR documentation as important and perceive it as contributing to ensuring quality, clarifying QRs, and facilitating decision-making. Time constraints, QR awareness, and communication gaps affect QR documentation. Missing and outdated QR documentation may lead to technical debt and a lack of common understanding regarding QRs. We introduce a model to support optimal QR documentation in ASD by focusing on the factors: time constraints, QR awareness, and communication gaps. The model provides a representation and explanation of the factors affecting QR documentation in ASD and identifies mitigation strategies to overcome issues that may occur due to these factors. Conclusion: The study reveals the importance of documenting QRs in ASD. It introduces a model that is based on empirical knowledge of QR documentation practices in ASD. Both practitioners and researchers can potentially benefit from the model. For instance, practitioners can analyze how time constraints or QR awareness affect documentation, see potential issues that may arise from them, and utilize strategies suggested by the model to address these issues. Researchers can learn about QR documentation in ASD and utilize the model to understand the topic. They can also use the study as a baseline to investigate the topic with other cases