Search results

Software developers extensively use stack overflow (SO) for knowledge sharing on software development. Thus, software engineering researchers have started mining the structured/unstructured data present in certain software repositories including the Q&A software developer community SO, with the aim to improve software development. The purpose of this paper is show that how academics/practitioners can get benefit from the valuable user-generated content shared on various online social networks, specifically from Q&A community SO for software development.

A comprehensive literature review was conducted and 166 research papers on SO were categorized about software development from the inception of SO till June 2016.

Most of the studies revolve around a limited number of software development tasks; approximately 70 percent of the papers used millions of posts data, applied basic machine learning methods, and conducted investigations semi-automatically and quantitative studies. Thus, future research should focus on the overcoming existing identified challenges and gaps.

The work on SO is classified into two main categories; “SO design and usage” and “SO content applications.” These categories not only give insights to Q&A forum providers about the shortcomings in design and usage of such forums but also provide ways to overcome them in future. It also enables software developers to exploit such forums for the identified under-utilized tasks of software development.

The study is the first of its kind to explore the work on SO about software development and makes an original contribution by presenting a comprehensive review, design/usage shortcomings of Q&A sites, and future research challenges.

Rather than organize as traditional firms, many of today’s companies organize as platforms that sit at the nexus of multiple exchange and production relationships. This chapter considers a most basic question of organization in platform contexts: the choice of boundaries. Herein, I investigate how classical economic theories of firm boundaries apply to platform-based organization and empirically study how executives made boundary choices in response to changing market and technical challenges in the early mobile computing industry (the predecessor to today’s smartphones). Rather than a strict or unavoidable tradeoff between “openness-versus-control,” most successful platform owners chose their boundaries in a way to simultaneously open-up to outside developers while maintaining coordination across the entire system.

We contend that software developers have an ethical responsibility to strive for reliable software. We base that obligation on long standing engineering traditions that place the public good as a central tenant and on the professional relationship between a software developer and the users of the software developed.

One key to improving team‐based software development is to support the developers’ ability to work together. Sets out one site’s response to this challenge. Developers at this site have a facility, which we will call the “team room”, allowing team members to work together. This is a computer‐supported meeting room that arose from the voluntary, and reflective, efforts of software developers to make it easier for them to work together. The team room’s popularity shows up in its extensive use for meetings and its acceptance as an integral part of software development at this site. When people use the team room, they work on a shared screen, making it easier to work together. Because they can work together, meetings become a time of work, not a pause between work sessions. Explains how these positive work outcomes have had some unexpected effects. For example, developers at this site now rely on room use to help deal with intra‐group conflict, so that the team room has become a buffer to social interaction, serving as a conduit for action.

The purpose of this paper is to identify and quantify the key components of the overall cost of software development when warranty coverage is given by a developer. Also, the authors have studied the impact of imperfect debugging on the optimal release time, warranty policy and development cost which signifies that it is important for the developers to control the parameters that cause a sharp increase in cost.

An optimization problem is formulated to minimize software development cost by considering imperfect fault removal process, faults generation at a constant rate and an environmental factor to differentiate the operational phase from the testing phase. Another optimization problem under perfect debugging conditions, i.e. without error generation is constructed for comparison. These optimization models are solved in MATLAB, and their solutions provide insights to the degree of impact of imperfect debugging on the optimal policies with respect to software release time and warranty time.

A real-life fault data set of Radar System is used to study the impact of various cost factors via sensitivity analysis on release and warranty policy. If firms tend to provide warranty for a longer period of time, then they may have to bear losses due to increased debugging cost with more number of failures occurring during the warrantied time but if the warranty is not provided for sufficient time it may not act as sufficient hedge during field failures.

Every firm is fighting to remain in the competition and expand market share by offering the latest technology-based products, using innovative marketing strategies. Warranty is one such strategic tool to promote the product among masses and develop a sense of quality in the user’s mind. In this paper, the failures encountered during development and after software release are considered to model the failure process.

The paper seeks to test empirically a variety of hypotheses related to human capital and organizational performance within software companies in Egypt.

A valid research instrument was utilized to conduct a survey of 38 software companies who are representative of the 107 members of the Software Industry Chamber of Egypt. A correlation analysis and stepwise regression were conducted to ascertain the validity of the hypotheses.

Statistical support was found for six of the nine hypotheses tested.

One of the limitations of this study is that human capital metrics were based on CEO self‐reported scores. Thus, the ability to generalize is limited to this context.

Of all the human capital metrics collected, the number of superstar developers seems to be the most critical variable in predicting export intensity. Superstar developers are those individuals whose productivity equals four times that of the other developers and twice that of the star developers.

This paper tests empirically the relationship between human capital and organization performance in the Egyptian software industry context and provides support for the recruitment and development of superstar developers.

In response to the increasing number of open‐source software (OSS) project initiatives and the increasing demand of OSS products as alternative solutions by industries, it is important for particular stakeholders such as the project host/supporter project‐leading teams, and prospective customers to determine whether a project initiative is likely to be sustainable and is worth supporting. This paper aims to propose a concept of “health” indicators and an evaluation process that can help to get a status overview of OSS projects in a timely fashion and predict project survivability based on the project data available on web repositories.

For initial empirical evaluation of the concept, the indicators are applied to well‐known web‐based OSS projects (Apache Tomcat and Apache HTTP Server) and the results are compared with challenged projects (Apache Xindice and Apache Slide). The results are discussed with OSS experts to investigate the external validity of the indicators.

From a software project management point of view, a typical web‐based OSS project can be viewed as a web‐engineering process, since most OSS projects exploit the benefits of a web platform and enable the project community to collaborate using web‐based project tools and repositories such as mailing lists, bug trackers, and versioning systems (CVS/SVN) to deliver web systems and applications. These repositories can provide rich collections of process data, and artifacts which can be analyzed to better understand the project status.

The paper provides information of value about open‐source solutions.

The paper has three purposes: the first is to provide a deeper understanding of the ideology and work practices of free and open source software development, the second to characterize the free software movement as a new type of computerization movement and the third to present a conceptual diagram and framework with an analysis showing how the free software computerization movement has evolved into an occupational community.

Qualitative data were collected over a four year period using a virtual ethnography in a study of free and open source software development and, in particular, a study of a free software community, GNUenterprise, located at www.gnuenterprise.org, which has the goal of developing a free enterprise resource planning software system.

It is concluded that the ideology of the free software movement continues to be one of the factors which mobilize people to contribute to free and open source software development. This movement represents a new type of computerization movement which promotes the investment of time in learning a new software development process instead of investment of money in the acquisition and use of new technology.

The research findings are limited by a detailed study of only one free software development project.

This paper is of significance to software developers and managers of firms who wish to incorporate free and open source software into their companies.

This research presents an original conceptual diagram and framework for how computerization movements have emerged into an occupational community.

To better understand the success of an open source software (OSS) project, this study aims to examine the role of social dependency networks (i.e. social and technical dependencies) in online communities.

This study focuses on dependencies using three network metrics – degree centrality, betweenness centrality and closeness centrality – in developer and module networks. A longitudinal analysis from the projects hosted at Sourceforge.net is conducted to examine the effects of social and technical networks on the success of OSS projects. To address our research questions, we have constructed research models to investigate the social network effects in developer networks, the technical network effects in module networks, and the social-technical network effects in both types of networks.

The results reveal nonlinear relationships between degree centrality in both social and technical networks and OSS success, highlighting the importance of a moderate level of degree centrality in team structure and software architecture. Meanwhile, a moderate level of betweenness centrality and a lower level of closeness centrality between developers lead to a higher chance of OSS project success.

This study is the first attempt to consider the network metrics in both module networks of the technical sub-system and developer networks of the social sub-system to better understand their influences on project success.

As the novel coronavirus 2019 (COVID-19) impacts the world, software practitioners are collaboratively working remotely from home. The pandemic has disrupted software practitioners’ productivity forcing changes to agile methodology adopted by software practitioners in software organizations. Therefore, this study aims to provide implication on the issues and recommendations for improving software practitioners’ productivity and also examine the impact of the COVID-19 pandemic on agile software development.

This paper adopts a narrative literature review to provide early assessment based on secondary data from the literature and available document reports from studies published from 2019 to 2022 to explore software practitioners’ productivity and agile software development during the working from home directive amidst the COVID-19 pandemic. A total of 60 sources which met the inclusion criteria were used to provide preliminary evidence grounded on secondary data from the literature. Descriptive analysis was used to provide qualitative findings from the literature.

Findings from this study present the significance of working from home directive on agile software development and software practitioners’ productivity. More importantly, findings from the secondary data shed light on software practitioners’ productivity adopting agile software development amidst the COVID-19 pandemic. Additionally, the findings present virtual collaborative platforms used by software practitioners, technical and social barriers of agile software development during the pandemic and recommendations for remote agile software development.

This study explores the significance of working from home directive on software practitioners’ productivity during COVID-19 pandemic and further investigates how are software practitioners’ productivity adopting agile software development practices amidst the COVID-19 pandemic. Besides, this study discusses the challenges software practitioners currently face and offers some strategies to bridge the gaps in agile software development to help software practitioners, system developers, software managers and software organizations adapt to the changes caused by the pandemic.