Software-intensive systems are ubiquitous in the industrialized world. The reliability of software has implications for how we understand scientific knowledge produced using software-intensive systems and for our understanding of the ethical and political status of technology. The reliability of a software system is largely determined by the distribution of errors and by the consequences of those errors in the usage of that system. We select a taxonomy of software error types from the literature on empirically (...) observed software errors and compare that taxonomy to Giuseppe Primiero’s Minds and Machines 24: 249–273, (2014) taxonomy of error in information systems. Because Primiero’s taxonomy is articulated in terms of a coherent, explicit model of computation and is more fine-grained than the empirical taxonomy we select, we might expect Primiero’s taxonomy to provide insights into how to reduce the frequency of software error better than the empirical taxonomy. Whether using one software error taxonomy can help to reduce the frequency of software errors better than another taxonomy is ultimately an empirical question. (shrink)

The popularity of empirical methods in software engineering research is on the rise. Surveys, experiments, metrics, case studies, and field studies are examples of empirical methods used to investigate both software engineering processes and products. The increased application of empirical methods has also brought about an increase in discussions about adapting these methods to the peculiarities of software engineering. In contrast, the ethical issues raised by empirical methods have received little, (...) if any, attention in the software engineering literature. This article is intended to introduce the ethical issues raised by empirical research to the software engineering research community, and to stimulate discussion of how best to deal with these ethical issues. Through a review of the ethical codes of several fields that commonly employ humans and artifacts as research subjects, we have identified major ethical issues relevant to empirical studies of software engineering. These issues are illustrated with real empirical studies of software engineering. (shrink)

This paper asserts that the software engineering (SE) research literature describes open source software development (OSSD) as a homogenous phenomenon. Through a discourse analysis of the SE research literature on OSSD, it is argued that the view of OSSD as a homogenous phenomenon is not grounded in empirical evidence. Rather, it emerges from key assumptions held within the SE research discipline about its identity and how to do SE research. As such, it is argued that the (...) view of OSSD as a homogenous phenomenon may constitute a systematic bias in the SE research literature. Implications of this are. (shrink)

Experiments in computing share many characteristics with the traditional experimental method, but also present significant differences from a practical perspective, due to their aim at producing software artifacts and the central role played by human actors and organizations involved in the software development process. By analyzing some of the most significant experiments in the subfield of software engineering, we aim at showing how the conceptual framework that supports experimental methodology in this context needs an extension in (...) a socio-technical perspective. (shrink)

It has been argued that the Internet and social media increase the number of available viewpoints, perspectives, ideas and opinions available, leading to a very diverse pool of information. However, critics have argued that algorithms used by search engines, social networking platforms and other large online intermediaries actually decrease information diversity by forming so-called “filter bubbles”. This may form a serious threat to our democracies. In response to this threat others have developed algorithms and digital tools to combat filter bubbles. (...) This paper first provides examples of different software designs that try to break filter bubbles. Secondly, we show how norms required by two democracy models dominate the tools that are developed to fight the filter bubbles, while norms of other models are completely missing in the tools. The paper in conclusion argues that democracy itself is a contested concept and points to a variety of norms. Designers of diversity enhancing tools must thus be exposed to diverse conceptions of democracy. (shrink)

This paper takes part in the methodological debate concerning the nature and the justification of hypotheses about computational systems in software engineering by providing an epistemological analysis of Software Testing, the practice of observing the programs’ executions to examine whether they fulfil software requirements. Property specifications articulating such requirements are shown to involve falsifiable hypotheses about software systems that are evaluated by means of tests which are likely to falsify those hypotheses. Software Reliability metrics, (...) used to measure the growth of probability that given failures will occur at specified times as new executions are observed, is shown to involve a Bayesian confirmation of falsifiable hypotheses on programs. Coverage criteria, used to select those input values with which the system under test is to be launched, are understood as theory-laden principles guiding software tests, here compared to scientific experiments. Redundant computations, fault seeding models and formal methods used in software engineering to evaluate test results are taken to be instantiations of some epistemological strategies used in scientific experiments to distinguish between valid and non-valid experimental outcomes. The final part of the paper explores the problem, advanced in the context of the philosophy of technology, of defining the epistemological status of software engineering by conceiving it as a scientifically attested technology. (shrink)

This institutional self-study investigated the use of text-matching software to prevent plagiarism by students in a Canadian university that did not have an institutional license for TMS at the time of the study. Assignments from a graduate-level engineering course were analyzed using iThenticate®. During the initial phase of the study, similarity scores from the first student assignments were collected to determine a baseline level of textual similarity. Students were then offered an educational intervention workshop on academic integrity. Another (...) set of similarity scores from consenting participants’ second assignments were then collected, and a statistically significant assignment effect was found between the similarity scores of the two assignments. The results of this study indicate that TMS, when used in conjunction with educational interventions about academic integrity, can be useful to students and educators to prevent and identify academic misconduct. This study adds to the growing body of empirical research about academic integrity in Canadian higher education and, in particular, in engineering fields. (shrink)

Software quality is one of the important elements of project management. Software review is one of the most cost effective techniques for detect and remove defects for improving software quality during software development life cycle. Literature suggests that experience and training have positive effect on software review performance. However, there is no empirical study conducted to analysis the important relationships between, experience, training and performance. A laboratory study was conducted with 192 volunteer university students (...) to examining the above relationships in a software review task. The results suggests that (1) there is positive relationships between role experience and performance, (2) training has no impact on performance, (3) working experience has an positive effect on performance (4) working experience has an impact and (5) role experience has no impact on performance. (shrink)

Organizations may need to attract occupational groups they did not recruit so far to implement strategic changes. Against the backdrop of this practical problem, this study introduces and explores an occupation-based measure of person-organization fit: occupational fit. I investigate its relationship with employer attractiveness based on human capital theory and explore the role of employer image as a moderator in this relationship. I surveyed 153 software engineers and mechanical engineers to analyze whether their occupational fit with software (...) class='Hi'>engineering and mechanical engineering firms is related to employer attractiveness. I find that occupational fit is only related to a firm’s employer attractiveness among software engineers. Employer image does not moderate this relationship. A qualitative follow-up study proposes first explanations for the unexpected differences between the two occupations by indicating that occupations may differ in the logic they apply to determine fit and their degree of professionalization. The study contributes to research by highlighting the neglected role of occupation in recruitment research and exploring potential boundary conditions of recruitment for fit. Implications for future research and practice are discussed. (shrink)

The Software Engineering Code of Ethics and Professional Practice, intended as a standard for teaching and practicing software engineering, documents the ethical and professional obligations of software engineers. The code should instruct practitioners about the standards society expects them to meet, about what their peers strive for, and about what to expect of one another. In addition, the code should also inform the public about the responsibilities that are important to the profession. Adopted in 2000 (...) by the IEEE Computer Society and the ACM--two leading international computing societies--the code of ethics is intended as a guide for members of the evolving software engineering profession. The code was developed by a multinational task force with additional input from other professionals from industry, government posts, military installations, and educational professions. (shrink)

There are many tangled normative and technical questions involved in evaluating the quality of software used in epidemiological simulations. In this paper we answer some of these questions and offer practical guidance to practitioners, funders, scientific journals, and consumers of epidemiological research. The heart of our paper is a case study of the Imperial College London covid-19 simulator, set in the context of recent work in epistemology of simulation and philosophy of epidemiology.

Unlike in most professions, a license is not required to work as a software engineer. This essay argues software engineers, because they now render an essential service to society, should be licensed in a process that resembles licensing for doctors, lawyers and teachers.

Over the past 30 years, computer engineering has developed a lot. Currently, computer and software applications have a central role in business, medicine, security, communications, industry, education, and everyday life. Software developers, peoples who manage computer networks, data security analysts can do well, but they also have the potential to cause suffering and harm to the clients or ordinary peoples, willingly or not. For this reason, IT activities must be regulated by specific laws. From the beginning, we (...) argue that the law is not the same thing as ethics, even if both promote the good. Certain ethical principles can be strengthened by law. In the field of computer science and technology, can exists theft, privacy violations, violence and harassment. To combat and punish such actions and behaviors, law is needed. But is software engineering a profession? If so, are there codes of professional ethics whereby specialists in the field can regulate their professional activity, as is the case, for example, in areas such as justice or medicine? In relation with that, Gibbs and Ford have identified 8 components of a professional infrastructure. Some of that is: initial vocational training, professional accreditation, licensing, continuous vocational training, the existence of code of ethics.. With the fact that software engineering is a profession, in this article we present the main principles of behavior. The principles are not legally binding. This are grouped by interest categories depending on who or what is involved in the interaction with software engineering. (shrink)

The purpose of this article is to propose an ethical framework for software engineers that connects software developers’ ethical responsibilities directly to their professional standards. The implementation of such an ethical framework can overcome the traditional dichotomy between professional skills and ethical skills, which plagues the engineering professions, by proposing an approach to the fundamental tasks of the practitioner, i.e., software development, in which the professional standards are intrinsically connected to the ethical responsibilities. In so doing, (...) the ethical framework improves the practitioner’s professionalism and ethics. We call this approach Ethical-Driven Software Development, as an approach to software development. EDSD manifests the advantages of an ethical framework as an alternative to the all too familiar approach in professional ethics that advocates “stand-alone codes of ethics”. We believe that one outcome of this synergy between professional and ethical skills is simply better engineers. Moreover, since there are often different software solutions, which the engineer can provide to an issue at stake, the ethical framework provides a guiding principle, within the process of software development, that helps the engineer evaluate the advantages and disadvantages of different software solutions. It does not and cannot affect the end-product in and of-itself. However, it can and should, make the software engineer more conscious and aware of the ethical ramifications of certain engineering decisions within the process. (shrink)

It has been argued that it is in the best interests of IT professionals, to adopt and enforce professional codes in the work place. But there is no code for usability engineers, unless one accepts that it is a branch of software engineering. The new joint ACM/IEEE‐CS Software Engineering Code of Ethics is applied to actual usability cases. This enables usability engineers to interpret this code in their profession. This is achieved by utilizing four case studies (...) both directly in terms of the ethical issues involved and in the light of the code. Also examined are the short‐comings of the code for the domain of usability engineering, and suggestions are made for enhancements for future revisions of the code. (shrink)

Among the various contemporary schools of moral thinking, consequence-based ethics, as opposed to rule-based, seems to have a good acceptance among professionals such as software engineers. But naïve consequentialism is intellectually too weak to serve as a practical guide in the profession. Besides, the complexity of software systems makes it very hard to know in advance the consequences that will derive from professional activities in the production of software. Therefore, following the spirit of well-known codes of ethics (...) such as the ACM/IEEE’s, we advocate for a more solid position in the ethical education of software engineers, which we call ‘moderate deontologism’, that takes into account both rules and consequences to assess the goodness of actions, and at the same time pays an adequate consideration to the absolute values of human dignity. In order to educate responsible professionals, however, this position should be complemented with a pedagogical approach to virtue ethics. (shrink)

This article reveals that explanatory practice in software engineering is in accordance with pragmatic explanatory pluralism, which states that explanations should at least partially be evaluated by their practical use. More specifically, I offer a defense of the idea that several explanation-types are legitimate in software engineering, and that the appropriateness of an explanation-type depends on (a) the engineer’s interests, and (b) the format of the explanation-seeking question he asks, with this format depending on his interests. (...) This idea is defended by considering examples that are representative for explanatory practice in software engineering. Different kinds of technological explanation are spelled out, and the dependence of their appropriateness on interests and question-formats is extensively illustrated. (shrink)

Safety-critical systems manufacturers have the duty of care, i.e., they should take correct steps while performing acts that could foreseeably harm others. Commonly, industry standards prescribe reasonable steps in their process requirements, which regulatory bodies trust. Manufacturers perform careful documentation of compliance with each requirement to show that they act under acceptable criteria. To facilitate this task, a safety-centered planning-time framework, called ACCEPT, has been proposed. Based on compliance-by-design, ACCEPT capabilities permit to design Compliance-aware Engineering Process Plans, which are (...) able to show the planning-time allocation of standard demands, i.e., if the elements set down by the standard requirements are present at given points in the engineering process plan. In this paper, we perform a case study to understand if the ACCEPT produced models could support the planning of space software engineering processes. Space software is safety and mission-critical, and it is often the result of industrial cooperation. Such cooperation is coordinated through compliance with relevant standards. In the European context, ECSS-E-ST-40C is the de-facto standard for space software production. The planning of processes in compliance with project-specific ECSS-E-ST-40C applicable requirements is mandatory during contractual agreements. Our analysis is based on qualitative criteria targeting the effort dictated by task demands required to create a CaEPP for software development with ACCEPT. Initial observations show that the effort required to model compliance and processes artifacts is significant. However, such an effort pays off in the long term since models are, to some extend, reusable and flexible. The coverage level of the models is also analyzed based on design decisions. In our opinion, such a level is adequate since it responds to the information needs required by the ECSS-E-ST-40C framework. (shrink)

Knowledge must forever govern ignorance, and a people who would be their own governors must arm themselves with the power which knowledge gives. Popular government, without popular information, or the means of acquiring it, is but a Prologue to a Farce or a Tragedy—or perhaps both.—James Madison, 1815.

This article reveals that explanatory practice in software engineering is in accordance with pragmatic explanatory pluralism, which states that explanations should at least partially be evaluated by their practical use. More specifically, I offer a defense of the idea that several explanation-types are legitimate in software engineering, and that the appropriateness of an explanation-type depends on (a) the engineer’s interests, and (b) the format of the explanation-seeking question he asks, with this format depending on his interests. (...) This idea is defended by considering examples that are representative for explanatory practice in software engineering. Different kinds of technological explanation are spelled out, and the dependence of their appropriateness on interests and question-formats is extensively illustrated. (shrink)

On the basis of an earlier contribution to the philosophy of computer science by Amnon Eden, this essay discusses to what extent Eden’s ‘paradigms’ of computer science can be transferred or applied to software engineering. This discussion implies an analysis of how software engineering and computer science are related to each other. The essay concludes that software engineering can neither be fully subsumed by computer science, nor vice versa. Consequently, also the philosophies of computer (...) science and software engineering—though related to each other—are not identical branches of a general philosophy of science. This also implies that not all of Eden’s earlier arguments can be directly mapped from the domain of computer science into the domain of software science. After the discussion of this main topic, the essay also points to some further problems and open issues for future studies in the philosophy of software science and engineering. (shrink)

Over the past four decades, software engineering has emerged as a discipline in its own right, though it has roots both in computer science and in classical engineering. Its philosophical foundations and premises are not yet well understood. In recent times, members of the software engineering community have started to search for such foundations. In particular, the philosophies of Kuhn and Popper have been used by philosophically-minded software engineers in search of a deeper understanding (...) of their discipline. It seems, however, that professional philosophers of science are not yet aware of this new discourse within the field of software engineering. Therefore, this article aims to reflect critically upon recent software engineers’ attempts towards a philosophy of software engineering and to introduce our own philosophical thoughts in this context. Finally, we invite the professional philosophers of science to participate in this interesting new discourse. (shrink)

A major, but too-little-considered problem for Software Engineering is a lack of consensus concerning Computer Science and how this relates to developing unpredictable computing technology. We consider some implications for SE of computer systems differing scientific basis, exemplified with the International Standard Organisations Open Systems Interconnection layered architectural model. An architectural view allows comparison of computing technology components facilitating a view of computing as a continuum. For example, at one layer of computer architecture, components written in Turing-complete machine (...) language can be seen as deterministic and consistent with a theoretical paradigm of CS. At another layer, components closer to the human sphere have been seen as non-deterministic and inconsistent with theoretical CS. We compare unpredictable development of computing technology against the cyclic legacy of technological advance and scientific discovery, and suggest that SE indicates an enabling cycle, discernible in previous scientific revolution, is stalled or possibly hidden. The CS consequence of divorcing technological advance from scientific consensus is particularly concerning. For example human/computing events could be seen as unpredictable virtual phenomena that somehow extend the ontology of CS. Our approach challenges practical and philosophical boundaries by investigating if applying scientific method resolves any SE/Science dichotomy. (shrink)

Program comprehension is an essential part of software engineering. The paper describes the constructivist theory of comprehension, a process based on assimilation and accommodation of knowledge. Assimilation means that the new facts are either added to the existing knowledge or rejected. Accommodation means that the existing knowledge is reorganized in order to absorb new facts. These processes are illustrated by case studies of knowledge-level reengineering of a legacy program and of incremental change. In both cases, we constructed preliminary (...) knowledge from the program documentation, and then adjusted it by comprehending the actual code. The case studies supported constructivism as a suitable theory of program comprehension. (shrink)

The public interest should be a central ethical concern of members of the computer profession, and this would also result in the social status and power of software engineers being augmented. One attractive means to encourage and enforce ethical standards on the part of engineers and employers would be a system of licensing by internationally recognised professional bodies whose legitimacy stems from their capacity to act in the public interest. The author is Senior Lecturer in the Department of Computer (...) Science, School of Applied Sciences, Anglia Polytechnic University, East Road, Cambridge CB1 1PT, England; email [email protected] or [email protected]. (shrink)

This textbook presents an overview of the critically important ethical and legal issues that arise in the computing field and provides a professional perspective from software engineering. The author gained exposure to these aspects of computing while working as a software engineer at Motorola in Ireland, where he coordinated the patent programme and worked with several software suppliers. Topics and features: Presents a broad overview of ethics and the law Includes key learning topics, summaries, and review (...) questions in each chapter, together with a useful glossary Discusses the professional responsibility of computer professionals Explores ethics in various civilisations and religious traditions Discusses ethical software engineering and ethical outsourcing Considers what is fair and ethical in data science Describes ethical challenges that arise in social media and the AI field Reviews intellectual property including patents, copyright and trademarks This practical and easy-to-follow textbook/reference is ideal for computer science students seeking to understand legal and ethical aspects of computing. The text also serves as a concise self-study primer for software engineers and software managers. (shrink)

There has been a transition in the way software developers work. Mistakes in software have been treated as "normal" occurrences. "All software has bugs." However, software engineering is an emerging profession which as a profession has now said that a caviler approach to software errors is unacceptable. They have asserted a very strong ethical position in the Software Engineering Code of Ethics and Professional Practice, a position which mandates concern for all those (...) affected by their work. The Code has several unique elements as a professional Code. (shrink)

Conceptual engineering is a philosophical method that aims to design and spread conceptual and linguistic devices to cause meaningful changes in the world. So far, however, conceptual engineers have struggled to successfully spread the conceptual and linguistic entities they have designed to their target communities. This paper argues that conceptual engineering is far more likely to succeed if it incorporates empirical data and empirical methods. Because the causal factors influencing successful propagation of linguistic or conceptual devices (...) are as complicated and interwoven as they are, proper empirical research will greatly boost the likelihood that propagation is successful. In arguing for the superiority of empirical conceptual engineering over armchair-based conceptual engineering, this paper proposes a framework for understanding the causal forces at play in propagation. This is a three-part framework between the label of a lexical item, the psychological states associated with the lexical item, and the worldly things associated with the lexical item. By understanding the way causal forces affecting propagation play out at these three levels, conceptual engineers can better conceptualize, study, and harness the different causal forces affecting the success of their conceptual engineering projects. (shrink)

In this paper, I stress the utility of employing test-driven development (TDD) for conceiving logical systems. TDD, originally invented in the context of Extreme Programming, is a methodology widely used by software engineers to conceive and develop programs. Its main principle is to design the tests of the expected properties of the system before the development phase. I argue that this methodology is especially convenient in conceiving applied logics. Indeed, this technique is efficient with most decidable logics having a (...) software implementation. Having a clear list of the desired inferences right from the beginning makes it possible to refine the properties of the system step by step until its completion. I distinguish and detail seven advantages of the usage of TDD for the conception of a logical theory. Most importantly, this methodology increases the predictability of the inferential power of the theory. A second important benefit is that the time required for the conception of the logic goes down dramatically. This methodology will change both ideas and practices. Logic is no longer considered to be a formal science, but rather to be an empirical one. Research in the field is geared toward specific and concrete goals. Programs are considered tools used to verify the conformity of formal theories. To sum up, I defend the view that, in some situations, this way of designing a formal system brings significant benefits, and that the construction of new logics can be conducted similarly to the development of open source software. (shrink)

In this paper, I stress the utility of employing test-driven development (TDD) for conceiving logical systems. TDD, originally invented in the context of Extreme Programming, is a methodology widely used by software engineers to conceive and develop programs. Its main principle is to design the tests of the expected properties of the system before the development phase. I argue that this methodology is especially convenient in conceiving applied logics. Indeed, this technique is efficient with most decidable logics having a (...) software implementation. Having a clear list of the desired inferences right from the beginning makes it possible to refine the properties of the system step by step until its completion. I distinguish and detail seven advantages of the usage of TDD for the conception of a logical theory. Most importantly, this methodology increases the predictability of the inferential power of the theory. A second important benefit is that the time required for the conception of the logic goes down dramatically. This methodology will change both ideas and practices. Logic is no longer considered to be a formal science, but rather to be an empirical one. Research in the field is geared toward specific and concrete goals. Programs are considered tools used to verify the conformity of formal theories. To sum up, I defend the view that, in some situations, this way of designing a formal system brings significant benefits, and that the construction of new logics can be conducted similarly to the development of open source software. (shrink)

Most philosophers have largely downplayed any relevance of multiple meanings of the folk concept of truth in the empirical domain. However, confusions about what truth is have surged in political and everyday discourse. In order to resolve these confusions, we argue that we need a more accurate picture of how the term ‘true’ is in fact used. Our experimental studies reveal that the use of ‘true’ shows substantial variance within the empirical domain, indicating that ‘true’ is ambiguous between (...) a correspondence and a coherence reading. We then explore the consequences of these results for the project of re-engineering truth. (shrink)

Abstract: The massive redeployment hypothesis (MRH) is a theory about the functional topography of the human brain, offering a middle course between strict localization on the one hand, and holism on the other. Central to MRH is the claim that cognitive evolution proceeded in a way analogous to component reuse in software engineering, whereby existing components-originally developed to serve some specific purpose-were used for new purposes and combined to support new capacities, without disrupting their participation in existing programs. (...) If the evolution of cognition was indeed driven by such exaptation, then we should be able to make some specific empirical predictions regarding the resulting functional topography of the brain. This essay discusses three such predictions, and some of the evidence supporting them. Then, using this account as a background, the essay considers the implications of these findings for an account of the functional integration of cognitive operations. For instance, MRH suggests that in order to determine the functional role of a given brain area it is necessary to consider its participation across multiple task categories, and not just focus on one, as has been the typical practice in cognitive neuroscience. This change of methodology will motivate (even perhaps necessitate) the development of a new, domain-neutral vocabulary for characterizing the contribution of individual brain areas to larger functional complexes, and direct particular attention to the question of how these various area roles are integrated and coordinated to result in the observed cognitive effect. Finally, the details of the mix of cognitive functions a given area supports should tell us something interesting not just about the likely computational role of that area, but about the nature of and relations between the cognitive functions themselves. For instance, growing evidence of the role of “motor” areas like M1, SMA and PMC in language processing, and of “language” areas like Broca’s area in motor control, offers the possibility for significantly reconceptualizing the nature both of language and of motor control. (shrink)

This paper is concerned with the construction of theories of software systems yielding adequate predictions of their target systems’ computations. It is first argued that mathematical theories of programs are not able to provide predictions that are consistent with observed executions. Empirical theories of software systems are here introduced semantically, in terms of a hierarchy of computational models that are supplied by formal methods and testing techniques in computer science. Both deductive top-down and inductive bottom-up approaches in (...) the discovery of semantic software theories are refused to argue in favour of the abductive process of hypothesising and refining models at each level in the hierarchy, until they become satisfactorily predictive. Empirical theories of computational systems are required to be modular, as modular are most software verification and testing activities. We argue that logic relations must be thereby defined among models representing different modules in a semantic theory of a modular software system. We exclude that scientific structuralism is able to define module relations needed in software modular theories. The algebraic Theory of Institutions is finally introduced to specify the logic structure of modular semantic theories of computational systems. (shrink)