Non-Knowledge as a New Lens on Software Engineering

Empirical studies play an important role in the evolution of the software engineering discipline. They allow us to build a body of knowledge in software engineering that has been supported by observation and empirical evidence. These studies allow us to test out theories, identify important variables and to build models that can be supported by empirical evidence.

Theory-oriented software engineering

CONTEXT. In software engineering (SE), aligning research and practice has long been challenging. GOAL. To assist researchers in extracting practical issues from the practical knowledge repositories of SE and making scientific information about SE accessible to practitioners. METHOD. We conducted several empirical studies to determine the causes of the disconnect between research and practice, which makes it challenging for practitioners to seek out and apply scientific knowledge. RESULTS. We obtained data on practitioners' difficulties with finding, comprehending, and evaluating SE scientific knowledge that supported us in creating a set of eight heuristics for conducting practical research in SE.

In recent years, the use and investigations about Grey Literature (GL) increased, in particular, in Software Engineering (SE) research. However, its understanding is still scarce and sometimes controversial, such as interpreting GL types and assessing their credibility. This study aimed to understand the credibility aspects that SE researchers consider in assessing GL and its types. To achieve this goal, we surveyed 53 SE researchers (who answered that they have used GL in our previous investigation), receiving a total of 34 valid responses. Our main findings show that: 1) GL source produced or cited by a renowned source is the main credibility criteria used to assess GL, 2) most of the GL types tend to have a Low to Moderate level of Control and Expertise, 3) there is a positive statistical correlation between the level of Control and Expertise for most GL types, and 4) the different respondent profiles shared similar opinions about the credibility criteria. Our investigation contributes to helping future SE researchers that intend to use GL with more credibility. Additionally, shows the need for future studies to better understand the GL types in SE research.

Empirical research is playing a significant role in software engineering (SE), and it has been applied to evaluate software artifacts and technologies. There have been a great number of empirical research articles published recently. There is also a large research community in empirical software engineering (ESE). In this paper, we identify both the overall landscape and detailed implementations of ESE, and investigate frequently applied empirical methods, targeted research purposes, used data sources, and applied data processing approaches and tools in ESE. The aim is to identify new trends and obtain interesting observations of empirical software engineering across different sub-fields of software engineering. We conduct a mapping study on 538 selected articles from January 2013 to November 2017, with four research questions. We observe that the trend of applying empirical methods in software engineering is continuously increasing and the most commonly applied methods are experiment, case study and survey. Moreover, open source projects are the most frequently used data sources. We also observe that most of researchers have paid attention to the validity and the possibility to replicate their studies. These observations are carefully analyzed and presented as carefully designed diagrams. We also reveal shortcomings and demanded knowledge/strategies in ESE and propose recommendations for researchers.

Background: The use of Grey Literature (GL) has been investigated in diverse research areas. In Software Engineering (SE), this topic has an increasing interest over the last years. Problem: Even with the increase of GL published in diverse sources, the understanding of their use on the SE research community is still controversial. Objective: To understand how Brazilian SE researchers use GL, we aimed to become aware of the criteria to assess the credibility of their use, as well as the benefits and challenges. Method: We surveyed 76 active SE researchers participants of a flagship SE conference in Brazil, using a questionnaire with 11 questions to share their views on the use of GL in the context of SE research. We followed a qualitative approach to analyze open questions. Results: We found that most surveyed researchers use GL mainly to understand new topics. Our work identified new findings, including: 1) GL sources used by SE researchers (e.g., blogs, community website); 2) motivations to use (e.g., to understand problems and to complement research findings) or reasons to avoid GL (e.g., lack of reliability, lack of scientific value); 3) the benefit that is easy to access and read GL and the challenge of GL to have its scientific value recognized; and 4) criteria to assess GL credibility, showing the importance of the content owner to be renowned (e.g., renowned author and institutions). Conclusions: Our findings contribute to form a body of knowledge on the use of GL by SE researchers, by discussing novel (some contradictory) results and providing a set of lessons learned to both SE researchers and practitioners.

In this chapter, the authors review the landscape of research methodologies and paradigms available for Information Technology (IT) and Software Engineering (SwE). The aims of the chapter are two-fold: (i) create awareness in current research communities in IT and SwE on the variety of research paradigms and methodologies, and (ii) provide an useful map for guiding new researchers on the selection of an IT or SwE research paradigm and methodology. To achieve this, the chapter reviews the core IT and SwE research methodological literature, and based on the findings, the authors illustrate an updated IT and SwE research framework that comprehensively integrates findings and best practices and provides a coherent systemic (holistic) view of this research landscape.

Artificial intelligence and recent advances in deep learning architectures, including transformer networks and large language models, change the way people think and act to solve problems. Software engineering, as an increasingly complex process to design, develop, test, deploy, and maintain large-scale software systems for solving real-world challenges, is profoundly affected by many revolutionary artificial intelligence tools in general and machine learning in particular. In this roadmap for artificial intelligence in software engineering, we highlight the recent deep impact of artificial intelligence on software engineering by discussing successful stories of applications of artificial intelligence to classic and new software development challenges. We identify the new challenges that the software engineering community has to address in the coming years to successfully apply artificial intelligence in software engineering, and we share our research roadmap toward the effective use of artificial intelligence in the software engineering profession, while still protecting fundamental human values. We spotlight three main areas that challenge the research in software engineering: the use of generative artificial intelligence and large language models for engineering large software systems, the need of large and unbiased datasets and benchmarks for training and evaluating deep learning and large language models for software engineering, and the need of a new code of digital ethics to apply artificial intelligence in software engineering.

Welcome to ICSE 2002, the Twenty-Fourth International Conference on Software Engineering!This year, besides the 3 keynotes, 48 papers, 3 panels, 9 industry papers, 2 invited industry presentations, 2 state-of-the-art talks, 3 impact talks, 8 posters, and 3 informal demonstrations in the main ICSE conference, we have 16 tutorials, 14 workshops, 2 symposia and 1 co-located event. These proceedings represent a snapshot in history on the state of the art and state of the practice of software engineering.While the road to ICSE was complicated by events taking place around the world, the unfortunate need to relocate does not detract from the outstanding opportunity we all have to share ideas and experiences and to foster new relationships with members of our profession.It Takes 2 to TangoWhile all software engineers may be accused of dancing to the beat of different drummers, one could speculate which dance partner they might want to select: • industrial applied software engineers and academic researchers in software engineering? • software engineers and systems engineers? • software engineers and information technologists? • software engineers and computer scientists?The point I am trying to make is that this year's ICSE brings together all of the above combinations and facilitates a synergistic environment for all attendees.Research is a community endeavor. ICSE is the premier generalist conference in software engineering research, encompassing all major subfields of software engineering. It plays a vital role in maintaining and developing the research community through exchange of ideas, development of a research agenda and setting standards for quality research.303 full research papers were submitted to ICSE 2002, of which 45 (less than 15reviewing and selectivity make publication in ICSE an honor for authors of selected papers, and ensures attendees and readers a selection of the best current research in software engineering.A program committee of experts drawn from around the world and across the spectrum of software engineering research were responsible for selecting a program of high quality technical papers and providing constructive criticism to authors of all submissions, whether selected or not. ICSE program committee members commit to a very heavy load of reviewing, made heavier this year by a review period that was shortened when we postponed the paper submission deadline by a week due to the tragic events of September 11. Each submitted paper was reviewed by three or more members of the program committee. The final selection was made in a lively two day, face-to-face meeting of the full committee. We are grateful to the ICSE 2002 program committee for magnificent work under difficult conditions, and we are proud of the result they have achieved.

We welcome you to the Twenty-Eighth International Conference on Software Engineering and Shanghai, China. This is the first instance of the ICSE conference series to be held in China, and it is an exciting time and place for ICSE 2006. The conference brings researchers, educators, practitioners and students together to present, exchange ideas and engage in discussions about the recent and exciting innovations and research in software engineering. Exciting sessions on practical experience, educational issues, and doctoral and new faculty symposia have been organized. The conference also includes a wide variety of tutorial, workshops and demonstration offerings. Finally, since research and markets in our host country China are continuously growing, ICSE includes a separate Far East Track for discussions on the contributions and challenges of our Chinese colleagues. We trust that this mix will provide interesting and stimulating offerings to all members of our growing community. The technical program committee is pleased to present this conference proceeding that contains the research papers of the technical program for ICSE 2006. The technical program for this conference focuses on new and innovative software engineering contributions in theory, formal methods, system building and empirical studies. The papers represent an alluring array of topics, including software design, architecture, reuse, testing, analysis, processes and formal methods. Because of the growing number of paper submission and the resulting large program committees in the past, we instituted a new two-phase reviewing process this year. Our program committee had 36 members. In the first phase, each submitted paper was reviewed by 3 reviewers: 2 from the program committee and an external reviewer from the software engineering community. We had 265 external reviewers who contributed 370 reviews for this phase. Those papers receiving the best reviews were considered in the second phase. A total of 99 papers entered the second phase. Each of these papers was reviewed by another program committee member. Thus, each accepted paper had a total of 4 reviews (3 reviews from pc members and 1 review from an external reviewer). Each rejected paper had at least 3 reviews. The pc members reviewed 24-25 papers in the two phases, a reasonable number. We feel that this system worked very well. The program committee met for two days in December, 2005 in Frankfurt, Germany. By the end of the meeting, a consensus emerged for the 36 papers in this proceedings (9% of the total submissions). There were many high quality submissions that could not be accommodated in the program; hopefully a revised version will be published elsewhere. In addition to the papers, we organized four invited sessions. One invited session focuses on empirical studies, an increasingly important component of software engineering research and practice. We also have an invited panel that addresses the value and practice of formal methods. Since software engineering techniques are growing in importance in challenging safety critical domains, we included two invited sessions: one on software engineering for automotive engineering and the other on software engineering for assisted living. We are very pleased that a notably diverse and outstanding group of three leaders of the software engineering community have agreed to present keynote speeches. The opening day keynote will be presented by Prof. Yang Fuqing, from Peking University, a woman who has been at the very forefront of the software engineering communities of research and practice in China for decades. Her perspectives on the past and future of software engineering in China will be complemented by a keynote on similar themes presented on the second day. This second keynote will be delivered by Prof. Barry Boehm, from the University of Southern California, USA. His talk will review the history of software engineering research and practice in the West over the past decades, and project it forward into the 21st century. Finally, the keynote speaker on the third day, Mr. Reinhold Achatz, from Siemens Corp., will present a complementary view of software engineering research and practice, as viewed from the perspective of one of the great multinational corporations, based in Europe. We are truly excited at the prospect that these three keynotes will provide a searching multidimensional view of our community at this time of historic convergence of communities. The continued success and high quality of the ICSE conference series would not be possible without the help and support of the software engineering community. First, we would like to gratefully acknowledge and thank all of the authors who submitted papers. We especially thank the program committee members for their efforts and commitments in reviewing the papers and securing reviews from external reviewers. They put in an extraordinary amount of their time to provide thoughtful and knowledgeable reviews. The exceptionally strong technical program represented by the papers in this proceeding could not be possible without their efforts.

CERSE - Catalog for empirical research in software engineering: A Systematic mapping study

Abstract. The rapid advancement of Artificial Intelligence (AI) has significantly influenced various industries, including software engineering. This paper explores the integration of AI into software engineering, focusing on its applications across different stages of the software development life cycle, including design, development, testing, project management, and maintenance. AI's ability to automate tasks, enhance efficiency, and improve code quality is revolutionizing how software is built and maintained. The paper also addresses the challenges and risks associated with AI-driven software engineering, such as dependency on AI tools, ethical concerns, and security vulnerabilities. Finally, the paper highlights future trends in AI-powered software engineering, including adaptive and self-healing systems, AI-enhanced collaboration, and full software automation. The role of AI in shaping the future of software engineering is both profound and transformative, making it a critical area of study.

Most graduates of baccalaureate computing programs (at least in the United States) take jobs in the computing profession immediately upon graduation. These jobs generally involve software development or maintenance activities, and therefore demand certain software engineering skills and knowledge.It appears, however, that typical undergraduate computing programs are at present inadequately preparing their students in the area of software engineering. This was in evidence at the 1991 International Conference on Software Engineering, in comments made at plenary sessions and in a special workshop on directions in software engineering education. It is also evidenced by recent attempts to encourage development of software engineering programs at the undergraduate level, separate from those in computer science or computer engineering.The purpose of this panel is to explore the following question: “What software engineering knowledge and skills should be required in a typical baccalaureate computing program, assuming the program is preparing its graduates for immediate entry into the computing profession?” In addressing this question, the panel will consider the recent report of the ACM/IEEE-CS Joint Curriculum Task Force, proposed software engineering curricula for undergraduates, and accreditation criteria.

Software engineers have always been experimenting with various models in an endeavor to improve upon software processes. Recently, a new area of software process improvement through experience management has got attention of the software engineering community. Software developers are experimenting with experience management to improve software process. This chapter explores the role of experience management in mitigating the effects of software crisis and investigates the current state of EM in Indian software engineering environment. The chapter discusses the need and integration of knowledge and experience management practices in software engineering environments. The chapter begins with the discussion of the ills of software engineering, classically referred to as “software crisis,” like late delivery of the systems, ill-functionality, and cost overruns, and justifies how managing the knowledge and experience of software engineers and practitioners can ward off these evils. The chapter then discusses the models and methodologies for knowledge and experience management in software engineering. Finally, the chapter sheds light on the major works carried out in this area and suggests possible future research avenues in this domain.

Discussions of software engineering education tend to focus on the needs of industry and the preparation of graduates for professional careers. This is understandable, and may even be appropriate, but what about those who hope to go on to do research in software engineering - how well are we catering for them?