A Systematic Literature Review on Implementing Non-functional Requirements in Agile Software Development: Issues and Facilitating Practices

Jarzębowicz, Aleksander; Weichbroth, Paweł

doi:10.1007/978-3-030-67084-9_6

Cited by 22 publications

(20 citation statements)

References 73 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…QRs have great importance in determining the success of software projects [2]. However, in ASD, they are often neglected, under-specified and not documented resulting in poor quality software and increased maintenance costs [5], [14].…”

Section: Methodsmentioning

confidence: 99%

See 1 more Smart Citation

Quality Requirement Documentation Guidelines for Agile Software Development

2022

View full text Add to dashboard Cite

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.INDEX TERMS Agile software development, design science, documentation, quality requirement.

show abstract

Section: Methodsmentioning

confidence: 99%

“…In ASD, there are limitations regarding the documentation of QRs [10]- [14]. For instance, informal QR documentation practices, such as relying on tacit knowledge, the infrastructure, other teams and organization for documentation of QRs, and under-specification of QRs, are problematic [2], [15].…”

Section: At Times Practitioners Depend On Tacit Knowledge and Domentioning

confidence: 99%

Quality Requirement Documentation Guidelines for Agile Software Development

2022

View full text Add to dashboard Cite

show abstract

“…Second, while most aspects of a system (including non-functional requirements) can be continuously monitored by automated means (e.g., server up-time, connection status, etc.) [14], non-functional requirement testing cannot be easily automated [113],…”

Section: Motivationmentioning

confidence: 99%

Investigating the Interplay between Developers and Automation

Elazhary

2021

2021 IEEE/ACM 43rd International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)

View full text Add to dashboard Cite

Continuous software engineering is a rapidly growing discipline in software engineering. Among its many reported benets is increased development velocity, faster feedback for developers, and better software quality. It also comes with its own share of challenges, most of which are centered on making automated builds more ecient or detecting problems with build conguration. However, the majority of literature in this area does not take into account software developers, which are arguably the cornerstone of software development.Software development is still a human-driven endeavour. It is a developer who writes the code, tests it, makes the nal decision while factoring in the build results, and so on. Furthermore, software development does not happen in a vacuum. Development takes place within the context of practices dictating how it should be done, and perceived benets that drive practice adoption and implementation. Software development, and by extension continuous software development, is a socio-technical endeavour that features interactions between human aspects (developers, testers, etc.), technical aspects (automation), and environmental aspects (process, projectspecic characteristics, infrastructure, etc.). While the software engineering eld has its share of theories, frameworks, and models, or borrows them from other elds, we still do not have a human-centric framework for software engineering that takes into account other socio-technical aspects (technical and environmental).My dissertation addresses this need for a socio-technical framework by illustrating a series of studies that ultimately resulted in the creation of a socio-technical theory of continuous software engineering that focuses on phenomena involving both humans and automation. In particular, I focus on the role of continuous software engineering tools (automation) in the software development process and how they displace existing tools, disrupt existing workows, and feature in software developer decision making. This theory will enable further research in this area as well as allow researchers to make more grounded recommendations for industrial applications.

show abstract

“…We decided to use Scopus as the library lists various publishers (such as SpringerLink, ACM, or Wiley). Besides, other authors have used Scopus for conducting systematic literature reviews and systematic mapping studies (e.g., [23,48]).…”

Section: Search Strategymentioning

confidence: 99%

“…The search results showed high redundancies. Furthermore, several studies has proven the opportunity to work with Scopus as a single database for secondary studies (e.g., [23,5,48]). However, there is a possibility that we did not find all relevant studies due to the search being carried out in one database.…”

Section: Limitationsmentioning

confidence: 99%

The Integrated List of Agile Practices -- A Tertiary Study

Neumann¹

2021

Preprint

View full text Add to dashboard Cite

Context: Companies adapt agile methods, practices or artifacts for their use in practice since more than two decades. This adaptions result in a wide variety of described agile practices. For instance, the Agile Alliance lists 75 different practices in its Agile Glossary. This situation may lead to misunderstandings, as agile practices with similar names can be interpreted and used differently. Objective: This paper synthesize an integrated list of agile practices, both from primary and secondary sources. Method: We performed a tertiary study to identify existing overviews and lists of agile practices in the literature. We identified 876 studies, of which 37 were included. Results: The results of our paper show that certain agile practices are listed and used more often in existing studies. Our integrated list of agile practices comprises 38 entries structured in five categories. Contribution: The high number of agile practices and thus, the wide variety increased steadily over the past decades due to the adaption of agile methods. Based on our findings, we present a comprehensive overview of agile practices. The research community benefits from our integrated list of agile practices as a potential basis for future research. Also, practitioners benefit from our findings, as the structured overview of agile practices provides the opportunity to select or adapt practices for their specific needs.

show abstract

A Systematic Literature Review on Implementing Non-functional Requirements in Agile Software Development: Issues and Facilitating Practices

Cited by 22 publications

References 73 publications

Quality Requirement Documentation Guidelines for Agile Software Development

Quality Requirement Documentation Guidelines for Agile Software Development

Investigating the Interplay between Developers and Automation

The Integrated List of Agile Practices -- A Tertiary Study

Contact Info

Product

Resources

About