Revisiting Software Engineering in the Social Era

This paper discusses the possible changes that software engineering will have to go through in response to the challenges and issues associated with social media. Indeed, people have never been so connected like nowadays by forming spontaneous relations with others (even strangers) and engaging in ad-hoc interactions. The Web is the backbone of this new social era – an open, global, ubiquitous, and pervasive platform for today\u27s society and world - suggesting that “everything” can socialize or be socialized. This paper also analyzes the evolution of software engineering as a discipline, points out the characteristics of social systems, and finally presents how these characteristics could affect software engineering\u27s models and practices. It is expected that social systems\u27 characteristics will make software engineering evolve one more time to tackle and address the social era\u27s challenges and issues, respectively

Revisiting Software Engineering in the Social Era

This paper discusses the possible changes that software engineering will have to go through in response to the challenges and issues associated with social media. Indeed, people have never been so connected like nowadays by forming spontaneous relations with others (even strangers) and engaging in ad-hoc interactions. The Web is the backbone of this new social era “ an open, global, ubiquitous, and pervasive platform for today\u27s society and world - suggesting that everything can socialize or be socialized. This paper also analyzes the evolution of software engineering as a discipline, points out the characteristics of social systems, and finally presents how these characteristics could affect software engineering\u27s models and practices. It is expected that social systems\u27 characteristics will make software engineering evolve one more time to tackle and address the social era\u27s challenges and issues, respectively

We Don't Need Another Hero? The Impact of "Heroes" on Software Development

A software project has "Hero Developers" when 80% of contributions are delivered by 20% of the developers. Are such heroes a good idea? Are too many heroes bad for software quality? Is it better to have more/less heroes for different kinds of projects? To answer these questions, we studied 661 open source projects from Public open source software (OSS) Github and 171 projects from an Enterprise Github. We find that hero projects are very common. In fact, as projects grow in size, nearly all project become hero projects. These findings motivated us to look more closely at the effects of heroes on software development. Analysis shows that the frequency to close issues and bugs are not significantly affected by the presence of project type (Public or Enterprise). Similarly, the time needed to resolve an issue/bug/enhancement is not affected by heroes or project type. This is a surprising result since, before looking at the data, we expected that increasing heroes on a project will slow down howfast that project reacts to change. However, we do find a statistically significant association between heroes, project types, and enhancement resolution rates. Heroes do not affect enhancement resolution rates in Public projects. However, in Enterprise projects, the more heroes increase the rate at which project complete enhancements. In summary, our empirical results call for a revision of a long-held truism in software engineering. Software heroes are far more common and valuable than suggested by the literature, particularly for medium to large Enterprise developments. Organizations should reflect on better ways to find and retain more of these heroesComment: 8 pages + 1 references, Accepted to International conference on Software Engineering - Software Engineering in Practice, 201

Knowledge society arguments revisited in the semantic technologies era

In the light of high profile governmental and international efforts to realise the knowledge society, I review the arguments made for and against it from a technology standpoint. I focus on advanced knowledge technologies with applications on a large scale and in open- ended environments like the World Wide Web and its ambitious extension, the Semantic Web. I argue for a greater role of social networks in a knowledge society and I explore the recent developments in mechanised trust, knowledge certification, and speculate on their blending with traditional societal institutions. These form the basis of a sketched roadmap for enabling technologies for a knowledge society

Revisiting Sentiment Analysis for Software Engineering in the Era of Large Language Models

Software development is an inherently collaborative process, where various stakeholders frequently express their opinions and emotions across diverse platforms. Recognizing the sentiments conveyed in these interactions is crucial for the effective development and ongoing maintenance of software systems. Over the years, many tools have been proposed to aid in sentiment analysis, but accurately identifying the sentiments expressed in software engineering datasets remains challenging. Although fine-tuned smaller large language models (sLLMs) have shown potential in handling software engineering tasks, they struggle with the shortage of labeled data. With the emergence of bigger large language models (bLLMs), it is pertinent to investigate whether they can handle this challenge in the context of sentiment analysis for software engineering. In this work, we undertake a comprehensive empirical study using five established datasets. We assess the performance of three open-source bLLMs in both zero-shot and few-shot scenarios. Additionally, we compare them with fine-tuned sLLMs. Our experimental findings demonstrate that bLLMs exhibit state-of-the-art performance on datasets marked by limited training data and imbalanced distributions. bLLMs can also achieve excellent performance under a zero-shot setting. However, when ample training data is available or the dataset exhibits a more balanced distribution, fine-tuned sLLMs can still achieve superior results.Comment: Submitted to TOSE

Are Delayed Issues Harder to Resolve? Revisiting Cost-to-Fix of Defects throughout the Lifecycle

Many practitioners and academics believe in a delayed issue effect (DIE); i.e. the longer an issue lingers in the system, the more effort it requires to resolve. This belief is often used to justify major investments in new development processes that promise to retire more issues sooner. This paper tests for the delayed issue effect in 171 software projects conducted around the world in the period from 2006--2014. To the best of our knowledge, this is the largest study yet published on this effect. We found no evidence for the delayed issue effect; i.e. the effort to resolve issues in a later phase was not consistently or substantially greater than when issues were resolved soon after their introduction. This paper documents the above study and explores reasons for this mismatch between this common rule of thumb and empirical data. In summary, DIE is not some constant across all projects. Rather, DIE might be an historical relic that occurs intermittently only in certain kinds of projects. This is a significant result since it predicts that new development processes that promise to faster retire more issues will not have a guaranteed return on investment (depending on the context where applied), and that a long-held truth in software engineering should not be considered a global truism.Comment: 31 pages. Accepted with minor revisions to Journal of Empirical Software Engineering. Keywords: software economics, phase delay, cost to fi

Show me the code: Spatial analysis and open source

This paper considers the intersection of academic spatial analysis with the open source revolution. Its basic premise is that the potential for cross-fertilization between the two is rich, yet some misperceptions about these two communities pose challenges to realizing these opportunities. The paper provides a primer on the open source movement for academicians with an eye towards correcting these misperceptions. It identifies a number of ways in which increased adoption of open source practices in spatial analysis can enhance the development of the next generation of tools and the wider practice of scientific research and education.open source; spatial analysis

The business of invention: considering project management in the arts and industry

Project management has well developed theoretical constructs and is becom- ing increasingly well established in core strategy beyond the industrial and corporate sec- tors from which it first emerged. With a concurrent increase in the significance of innova- tion, project managing for creativity is an area of research and enquiry of considerable sig- nificance. Notionally occupying polar opposite cultural positions in terms of perspectives and processes of creativity, project management in the arts is widely considered to vary significantly from corporate strategy and process. If business were to be more generally characterised by ‘organisation’ and discipline, the arts are more commonly celebrated for disorganisation, indiscipline, and the fundamental challenge to organisation itself. Consid- ering both the confluences and variations between established project management theory in business and practice in the arts, this text introduces theoretical constructs pertaining to creative processes and highlights areas for consideration in the understanding and further development of project management theory

Quarterly Research Output Reports

These reports paper summarize research outputs published in each quarter by academic staff at the University of Lincoln. The lists include substantive research outputs first appearing "in published form" (or equivalent for non-textual outputs) during this period. The lists have been generated automatically from data stored in the Lincoln Repository (http://eprints.lincoln.ac.uk/). Tables summarize the volume of outputs recorded by School

Revisiting Cybersecurity Awareness in the Midst of Disruptions

The awareness of cybersecurity and knowledge about risks from a variety of threats, which present harm or steal private information in internetworking could help in mitigation of vulnerabilities to risks of threats in safeguarding information from malware and bots. Revisiting cybersecurity awareness of every member and evaluation of organization’s posture might help to protect sensitive or private information from a network of computers, working together and forming into botnets. The purpose of the qualitative case study narrative was to explore prospects for integrating cybersecurity education into elementary school children’s curriculum through interviews of elementary schoolteachers, IT experts, and parents to gain feedback about perceptions on cybersecurity knowledge and awareness. The analysis of schools’ organizational security postures related to all levels of education, recommending in raising awareness of the underlying and unprecedented security vulnerabilities. One area of greatest need is in protecting the wellbeing of people in securing private or protected assets and sensitive information, most valuable and vulnerable amid disruption. The possible lack of cybersecurity awareness in online settings could increase an organizational vulnerability to risks of threats and outsider attempts to install malware during a variety of cyber-attacks. Organizations with online ambiguity face a threat from botnets to infect networks. This qualitative exploratory single case-study into perceptions of teachers and leaders, information technology (IT) experts, and parents of elementary school children about cybersecurity awareness level of children in elementary schools helped to reinforce the important role of education in building foundational cyber-safety practices