scholarly journals How systematic reviews cover practitioners' issues: A study on Stack Exchange communities

2019 ◽  
Author(s):  
Bruno Cartaxo ◽  
Gustavo Pinto ◽  
Fernando Kamei ◽  
Danilo Monteiro ◽  
Fabio Queda ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Systematic Reviews ◽  
Engineering Practice ◽  
Evidence Based ◽  
Research To Practice ◽  
High Quality ◽  
Good Opportunity ◽  
Agile Software ◽  
Tertiary Study

Context: One of the goals of Evidence-Based Software Engineering is to leverage evidence from research to practice. However, some studies suggest this goal has not being fully accomplished. Objective: This paper proposes a strategy to assess how systematic reviews cover practitioners' issues in software engineering. Method: We selected 24 systematic reviews identified by a comprehensive tertiary study. Using search strings of the selected systematic reviews, we queried most relevant practitioners' issues on five active Stack Exchange communities, a professional and high-quality Question & Answer platform. After examining more than 1,800 issues, we investigated how findings of the selected systematic reviews could help to solve (i.e. cover) practitioners' issues. Results: After excluding false positives and duplicates, a total of 424 issues were considered related to the selected systematic reviews. This number corresponds to 1.75% of the 26,687 most relevant issues on the five Stack Exchange communities. Among these 424 issues, systematic reviews can successfully cover 14.1% (60) of them. Based on a qualitative analysis, we identified 45 recurrent issues spread in many software engineering areas. The most demanded topic is related to agile software development, with 15 recurrent issues identified and 127 practitioners' issues as a whole. Conclusions: An overall coverage rate of 14.1% reveals a good opportunity for conducting systematic reviews in software engineering to fill the gap of not covered issues. We also observed practitioners explicitly demanding for scientific empirical evidence, rich in context and oriented to specific target audiences. Finally, we also provided guidelines for researchers who want to conduct systematic reviews more connected with software engineering practice.

scholarly journals How systematic reviews cover practitioners' issues: A study on Stack Exchange communities

2019 ◽  
Author(s):  
Bruno Cartaxo ◽  
Gustavo Pinto ◽  
Fernando Kamei ◽  
Danilo Monteiro ◽  
Fabio Queda ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Systematic Reviews ◽  
Engineering Practice ◽  
Evidence Based ◽  
Research To Practice ◽  
High Quality ◽  
Good Opportunity ◽  
Agile Software ◽  
Tertiary Study

Context: One of the goals of Evidence-Based Software Engineering is to leverage evidence from research to practice. However, some studies suggest this goal has not being fully accomplished. Objective: This paper proposes a strategy to assess how systematic reviews cover practitioners' issues in software engineering. Method: We selected 24 systematic reviews identified by a comprehensive tertiary study. Using search strings of the selected systematic reviews, we queried most relevant practitioners' issues on five active Stack Exchange communities, a professional and high-quality Question & Answer platform. After examining more than 1,800 issues, we investigated how findings of the selected systematic reviews could help to solve (i.e. cover) practitioners' issues. Results: After excluding false positives and duplicates, a total of 424 issues were considered related to the selected systematic reviews. This number corresponds to 1.75% of the 26,687 most relevant issues on the five Stack Exchange communities. Among these 424 issues, systematic reviews can successfully cover 14.1% (60) of them. Based on a qualitative analysis, we identified 45 recurrent issues spread in many software engineering areas. The most demanded topic is related to agile software development, with 15 recurrent issues identified and 127 practitioners' issues as a whole. Conclusions: An overall coverage rate of 14.1% reveals a good opportunity for conducting systematic reviews in software engineering to fill the gap of not covered issues. We also observed practitioners explicitly demanding for scientific empirical evidence, rich in context and oriented to specific target audiences. Finally, we also provided guidelines for researchers who want to conduct systematic reviews more connected with software engineering practice.

An Analysis of Process Characteristics for Developing Scientific Software

2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

Agile Software

2014 ◽  
pp. 96-116
Author(s):  
Zaidoun Alzoabi
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Changing Environment ◽  
Agile Methodology ◽  
Agile Software

The term Agile Method of software development was coined in the 2001.This approach is characterized with creativity, flexibility, adaptability, responsiveness, and human-centricity. Researchers have suggested that the complex, uncertain, and ever-changing environment is pushing developers to adopt agile methods rather than traditional software development. Agile methodologist claim that their Agile methods is the answer for the software engineering chaotic situation, in which projects are exceeding their time and budget limits, requirements are not fulfilled, and consequently ending up with unsatisfied customers. In this chapter we will explain agile methodology, its general characteristics, and quick description of the famous agile methods known in the industry and research.

Using Wiki for Managing Knowledge in Agile Software Development

2016 ◽  
pp. 397-423
Author(s):  
Pankaj Kamthan
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Agile Software Development ◽  
Software System ◽  
Web Environment ◽  
The Past ◽  
Agile Methodologies ◽  
The Social ◽  
Industrial Software ◽  
Agile Software

The movement towards agility is one of the most significant changes in industrial software engineering over the past decade. In the practice of agile methodologies, there are different types of knowledge that is created, communicated, and consumed. For the benefit of the stakeholders involved, there is a pressing need to manage this knowledge, both during development and beyond deployment of a software system. This chapter proposes a framework comprising related conceptual models as means for understanding the use of Wiki for managing knowledge in agile software development. In doing so, Wiki is considered beyond that of a technology or a tool, as a facilitator of knowledge, and placed in a larger context of the Social Web environment. For the sake of practicality, a number of illustrative examples are given, and implications of deploying a Wiki are highlighted.

Systematic literature reviews in agile software development: A tertiary study

2017 ◽  
Vol 85 ◽  
pp. 60-70 ◽  
Author(s):  
Rashina Hoda ◽  
Norsaremah Salleh ◽  
John Grundy ◽  
Hui Mien Tee
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Literature Reviews ◽  
Agile Software ◽  
Tertiary Study

Agile Software

2012 ◽  
pp. 14-34 ◽  
Author(s):  
Zaidoun Alzoabi
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Changing Environment ◽  
Agile Methodology ◽  
Agile Software

The term Agile Method of software development was coined in the 2001.This approach is characterized with creativity, flexibility, adaptability, responsiveness, and human-centricity. Researchers have suggested that the complex, uncertain, and ever-changing environment is pushing developers to adopt agile methods rather than traditional software development. Agile methodologist claim that their Agile methods is the answer for the software engineering chaotic situation, in which projects are exceeding their time and budget limits, requirements are not fulfilled, and consequently ending up with unsatisfied customers. In this chapter we will explain agile methodology, its general characteristics, and quick description of the famous agile methods known in the industry and research.

Teaching Agile Software Development Quality Assurance

2009 ◽  
pp. 2700-2713
Author(s):  
Orit Hazzan ◽  
Yael Dubinsky
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Specific Teaching ◽  
Quality Issues ◽  
Agile Software ◽  
Software Development Environments ◽  
The Way

This chapter presents a teaching framework for agile quality—that is, the way quality issues are perceived in agile software development environments. The teaching framework consists of nine principles, the actual implementation of which is varied and should be adjusted for different specific teaching environments. This chapter outlines the principles and addresses their contribution to learners’ understanding of agile quality. In addition, we highlight some of the differences between agile software development and plan-driven software development in general, and with respect to software quality in particular. This chapter provides a framework to be used by software engineering instructors who wish to base students learning on students’ experiences of the different aspects involved in software development environments.

Wiki for Agility

2017 ◽  
pp. 896-916
Author(s):  
Pankaj Kamthan
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Conceptual Model ◽  
Agile Software Development ◽  
Social Aspects ◽  
Social Web ◽  
Agile Methodologies ◽  
The Social ◽  
Industrial Software ◽  
Agile Software

The movement towards agility is one of the most significant human-centered and socially oriented changes in industrial software engineering. In the practice of agile methodologies, there are different types of content (data, information, or knowledge) that are created, communicated, and consumed. It is imperative for an organization to manage such content, both during development and beyond deployment. This chapter proposes a conceptual model for understanding and exploring the use of Wiki as a vehicle for managing content in agile software development. In doing so, the parity between agile software development and Wiki is shown, human and social aspects of each are emphasized, the Social Web-Context of Wiki is demonstrated, illustrative examples are given, and the implications of committing to a Wiki are considered.

Sign in / Sign up

Export Citation Format

Share Document