Continuous Software Engineering Practices in {AI/ML} Development Past the Narrow Lens of {MLOps}: {A}doption Challenges

This book provides essential insights on the adoption of modern software engineering practices at large companies producing software-intensive systems, where hundreds or even thousands of engineers collaborate to deliver on new systems and new versions of already deployed ones. It is based on the findings collected and lessons learned at the Software Center (SC), a unique collaboration between research and industry, with Chalmers University of Technology, Gothenburg University and Malm University as academic partners and Ericsson, AB Volvo, Volvo Car Corporation, Saab Electronic Defense Systems, Grundfos, Axis Communications, Jeppesen (Boeing) and Sony Mobile as industrial partners. The 17 chapters present the Stairway to Heaven model, which represents the typical evolution path companies move through as they develop and mature their software engineering capabilities. The chaptersdescribe theoretical frameworks, conceptual models and, most importantly, the industrial experiences gained by the partner companies in applying novel software engineering techniques. The books structure consists of six parts. Part I describes the model in detail and presents an overview of lessons learned in the collaboration between industry and academia. Part II deals with the first step of the Stairway to Heaven, in which R&D adopts agile work practices. Part III of the book combines the next two phases, i.e., continuous integration (CI) and continuous delivery (CD), as they are closely intertwined. Part IV is concerned with the highest level, referred to as R&D as an innovation system, while Part V addresses a topic that is separate from the Stairway to Heaven and yet critically important in large organizations: organizational performance metrics that capture data, and visualizations of the status of software assets, defects and teams. Lastly, Part VI presents the perspectives of two of the SC partner companies. The book is intended for practitioners and professionals in the software-intensive systems industry, providing concrete models, frameworks and case studies that show the specific challenges that the partner companies encountered, their approaches to overcoming them, and the results. Researchers will gain valuable insights on the problems faced by large software companies, and on how to effectively tackle them in the context of successful cooperation projects.

Context: In the last years, the Grey Literature (GL) had a notable increase in interest in diverse areas of knowledge. In Software Engineering (SE), with the advance of social media, the SE practitioners are heavy consumers of GL, opposite to traditional research papers, such as the Systematic Literature Review (SLR). Problem: Despite the increase of numbers of SLRs, some researchers claim the lack of connection to the practice of SE, due to the lack of evidence derived from SE practitioners. Goal: Introduce methods and techniques to support a Grey Literature Review (GLR) in SE, aiming to approximate the literature review to the practice of SE. Method: First, we will investigate how secondary studies use GL; Second, we will employ a survey with researchers of SLRs and SE practitioners; Third, we will analyze the use of GL according to the context; Fourth, we will review the GL source in SE; Finally, we will propose a guideline to help SE researchers and practitioners to conduct the GLR. Preliminary findings: We have initiated the tertiary study conducting the manual (4,875 studies) and automatic (6,279 studies) searches. We eliminated those that were not an article, and also those were not written in English, remaining 8,019 potential studies. Currently, we are applying the inclusion and exclusion criteria.

The economy of Bangladesh largely depends on agriculture. Agroforestry is one of the modern agricultural practices which ensure maximum utilization of resources and offer sustainable environmental and economic development. The present study was carried out to find out farmers’ perceptions and problems towards the adoption of agroforestry practices in the coastal area of Bangladesh. In total, 400 farmers were selected from five upazila of the Noakhali district following a proportionate random sampling technique. Face-to-face interviews, case studies, and focus group discussions (FGD) were used to obtain the data. Statics such as range, mean, standard deviation, Chi-square, and correlation analysis were applied. Most of the respondents were middle-aged (45%) with a low literacy rate and large family size (55%). The majority of them (50%) had small-sized land, and they had limited access to agricultural training. A greater part of the respondents (61%) had a very low level of knowledge of agroforestry practice. Silvopasture and homestead agroforestry system was practiced by most of the farmers (77%) without proper concept. Only 11% of the respondents know and practice multistrata agroforestry, which is one of the best agroforestry practice. The perception of the respondents towards the adoption of agroforestry was found low in most of the cases. They expressed a low level of acuity towards agroforestry, and they were not so interested towards the adoption of these practices. “Agroforestry adoption may be hampered by a lack of institutions and policies to support it” and “Lack of knowledge and awareness on agroforestry practice” was identified most significant problems with a chi-square value of 41.6 and 39.2 at 5% level of significance. Respondents’ knowledge of agroforestry, exposure to training, and farm size were positively and significantly correlated with their adoption of the practice (r = 0.437∗∗, 0.572∗∗, and 0.64∗∗, respectively). Demonstrations, awareness campaigns, financial incentives, and collaborations between government organizations and NGOs may increase the adoption of agroforestry practices in the coastal region of Bangladesh.

Trends that have contributed to the globalisation of the software engineering industry include virtual collaborative teams, off-shore outsourcing, and international migration of IT professionals. These three trends and the international spread of software engineering standards and methodologies are explored with specific examples from the Australian software engineering industry. Results from a Europe/Australia study about adoption of software best practice conducted in 16 countries are then summarised and analysed using Hofstede's cultural dimensions. The discussion considers the efficacy of the concept 'national culture' in light of the analysis and concludes that software engineering researchers need to reconsider the concept and measurement of national culture. Implications of the globalisation of software engineering standards and methodologies on various stakeholders are discussed.

necessity of formal methods education has developed from its increasing assimilation into systems development within industry. Organizations responsible for a wide range of applications have found it necessary to find an improved means of intellectual control over their complex system development and that formal methods can meet this need. To this end, the International Survey of Industrial Applications of Formal Methods concluded and recommended: The current educational base in the US is weak in teaching formal methods in the context of software engineering . . . There is a clear need for improved integration of formal methods techniques with other software engineering practices[2]There exists a number of articles in the current literature expressing the belief that the current educational program offered for a computer science degree does not stress the fundamental mathematical and engineering principles that should form the basis of software engineering[3,4,5,6]. theory learned in mathematics and science classes is applied in other engineering classes, but unfortunately has not been applied in software engineering. inability to apply logic in practical circumstances prevents the student from doing the systematic analysis necessary to solve practical problems.For these reasons, it is desirable to include the definition and application of a formal method into the undergraduate curriculum with the goal of increasing the complex problem solving skills of the software engineer. Formal analysis should be introduced early into the undergraduate curriculum to ensure substantial learning, use, and training in formal methods application.

Software engineers have to cope with uncertainties and changing requirements. Agile methods provide flexibility towards changes and the emergence of continuous delivery has made regular feedback loops possible. The abilities to maintain high code quality through reviews, to regularly release software, and to collect and prioritize user feedback, are necessary for continuous software engineering (CSE). However, there exists no software process metamodel that handles the continuous character of software engineering. In this paper, we describe an empirical process metamodel for continuous software engineering called CSEPM, which treats development activities as parallel running workflows and allows tailoring and customization. CSEPM includes static aspects that describe the relations between specific CSE concepts including reviews, releases, and feedback. It also describes the dynamic aspect of CSE, how development workflows are activated through change events. We show how CSEPM allows to instantiate linear, iterative, agile and continuous process models and how it enables tailoring and customization.

Clean room software engineering is a formal software development method that can strictly engineer software development and eliminate defects before they can cause serious harm. The clean room software engineering model has its own advantages and disadvantages in use. To use it in traditional software engineering, it is necessary to clarify the relationship between it and traditional software engineering methods and practices. Based on the technology and principles of the clean room software process, this paper gets the advantages and disadvantages of the clean room. Corresponding the traditional method-based software process to the key technology of the clean room, making the traditional management-based software engineering method and the tailored clean room compatible, and the software engineering practice of the clean room software process is compared with the traditional software engineering practice. To discuss the clean room and traditional software engineering, in order to expand the use of clean room methods, improve the clean room software process, and improve the quality of software.

The chapter provides possible directions for the wider application of the systems approach to information systems development. Potential improvement of software development practices is linked by some leading experts to the application of more systemic ideas. However, the current state of the practice in software engineering and information systems development shows the urgent need for improvement through greater application of systems thinking.

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.

This paper presents a graduate curriculum for software engineering education, as proposed by the Air Force Institute of Technology (AFIT). In order to define such a curriculum, it is first necessary to define what is meant by the term “software engineer,” and what capabilities are expected in a graduate of such a program. The process of “software engineering” is examined in the context of requirements for software system development and management within the Air Force. These requirements help define the fundamental concepts and techniques, as well as the support tools, which must be integrated into an effective curriculum for software engineering. The program presented incorporates both the theory and practice of software engineering. The proposed curriculum for a Master of Science degree with a major in software engineering is based on AFIT’s experience with software engineering education and its ongoing contact with many Air Force agencies involved in software development. Many of AFIT’s student thesis efforts have involved large-scale software developments which often extend from student to student over several years. This paper presents this program, along with supporting discussion of program objectives and course content.

The Software Engineering Institute (SEI) is a federally funded research and development center situated as a college‐level unit at Carnegie Mellon University with facilities in Pittsburgh, PA and Arlington, VA. The SEI was created in 1984 by the U.S. Department of Defense to mature and transition new technology to industry so that the government could acquire software‐intensive systems from a broader, more capable contractor base. The SEI works to transform software engineering from an ad‐hoc, labor‐intensive activity to a managed, technology‐supported engineering discipline. The SEI's objectives are to accelerate the introduction and widespread use of high‐payoff software engineering practices and technology by identifying, evaluating, and maturing promising or underused technology and practices; maintain a long‐term competency in software engineering and technology transition; enable government and industry organizations to make measured improvements in their software engineering practices by working with them directly; and foster the adoption and sustained use of standards of excellence for software engineering practice. The institute explores promising solutions to potentially significant problems, selects the best candidate solutions, and works on them to determine their value. In some cases, the SEI works to overcome the limitations that prevent a solution from being of general use in the software community. Finally, the SEI moves mature solutions of proven value into widespread use; examples include the Capability Maturity Model® for Software (SW‐CMM®), and a model curriculum for a master's degree program in software engineering that has been adopted by universties across the country. SEI activities are grouped into two principal areas: software engineering management practices and software engineering technical practices.

Software engineering and programming are integral components of the modern technology landscape, underpinning the development of software applications and systems that power our digital world. This research paper delves into the core concepts and practices of software engineering, emphasizing the importance of structured development methodologies, design principles, and quality assurance. It also explores the role of programming in software creation, shedding light on various programming paradigms and the significance of coding standards.

In teaching software engineering, it is a major challenge to integrate applied methodology and theory into the practice of software development. Today teaching a course in software engineering involves a theoretical approach with white board and doing a project at the end of the course. Teaching Software engineering as a course involves many disciplines and requires delivering lectures accompanied by lecture demos and hands on lab sessions to accompany individual constituent topics or areas that form the bricks and mortar of this course. Only when the bricks and mortar of software engineering have delivered a solid foundation, is it then the software engineering as a course will be delivered in a true and meaningful sense. This paper presents a method to teach Software Engineering using the applied approach that the author designed and successfully used.

A review of the qualitative research methods discussed in papers that study software engineering teams showed most of those papers did not follow a systematic process during the qualitative analysis. This finding is concerning as this deficiency in research analysis procedure may reduce the validity and/or completeness of the qualitative results. Such a lack of rigor may be a result of qualitative research not being as firmly established in software engineering as quantitative research methodologies. In engineering research, quantitative methods are typically more prevalent and qualitative analysis is part of a mixed-method analysis process. However, when researching teams, where human activity is abundant, qualitative analysis may need to take precedence. In this paper, we focus on the qualitative analysis method called content analysis with the goal of presenting a rigorous process for content analysis in the context of software engineering. We then present and demonstrate the use of that content analysis process for software engineering researchers using two examples. An analysis of 215 articles that were a result of a mapping study on software engineering team research is presented. Those papers were analyzed to determine which utilized a qualitative data analysis method in their research in addition to the rigor and type of qualitative analysis performed. We ultimately included 23 papers in this study. We present a mapping study and a content analysis process that include a straightforward way to select, code, and present data in both inductive and deductive studies. We demonstrated the process using the keywords from the papers included in this study as well as on a second data set that utilized responses from structured interview transcripts from practicing software engineers. The first dataset also resulted in a taxonomy to categorize software engineering team research. We presented and demonstrated a content analysis process in terms of software engineering in order to improve future qualitative software engineering research that would benefit from systematic content analysis.

Repository-based development of software systems has gained more attention recently by addressing new challenges such as security and dependability. However, there are still gaps in existing modeling languages and/or formalisms dedicated to define model repositories and the way how to reuse them in the automation of software development. Thus, there is a strong requirement for defining a model repository description language not only as a modeling approach, but also as a suitable instrument to support system and software engineers in the activity of search and retrieval of appropriate models beyond keyword-based search. Moreover, modeling approaches allow using tools for the specification and the exploitation of the designed artifacts e.g. analysis and evaluation. The goal of this paper is to advance the state of the art in model repository description for software and systems engineering. In particular, we have designed a flexible and extensible modeling language, by means of an OMG style metamodel, to specify model repositories for modeling artifacts, and we have defined an operational architecture for development tools. In particular, we show the feasibility of our own approach by reporting some preliminary prototype providing a model-based repository of security and dependability S&D pattern models.