Over the past 50 years, Nelson algebras have been extensively studied by distinguished scholars as the algebraic counterpart of Nelson's constructive logic with strong negation. Despite these studies, a comprehensive survey of the topic is currently lacking, and the theory of Nelson algebras remains largely unknown to most logicians. This paper aims to fill this gap by focussing on the essential developments in the field over the past two decades. Additionally, we explore generalisations of Nelson algebras, such as N4-lattices which (...) correspond to the paraconsistent version of Nelson's logic, as well as their applications to other areas of interest to logicians, such as duality and rough set theory. A general representation theorem states that each Nelson algebra is isomorphic to a subalgebra of a rough set-based Nelson algebra induced by a quasiorder. Furthermore, a formula is a theorem of Nelson logic if and only if it is valid in every finite Nelson algebra induced by a quasiorder. (shrink)

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.

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.

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)

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)

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)

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)

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)

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 (...) class='Hi'>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)

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)

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)

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.

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

Digital artifacts often fail to perform as expected. It has recently been argued that this should not be analyzed as software malfunctioning. Rather, every case that is not the result of hardware failures would be due to design errors. This claim, which hinges on the notion of ‘implementation’, highlights a potential fundamental difference between software and other technical artifacts. It also implies that software engineers have more extensive responsibilities than creators of other artifacts. After reconstructing the argument, (...) we show that it rests on two presuppositions regarding the nature of software and the activities of its creators, which we call ‘complete control’ and ‘self-containedness’. Software is taken to be a self-contained unit through which the software engineer exerts complete control over a machine’s behavior. These two presuppositions as well as the usage of implementation and strong claims regarding responsibility can be found throughout the literature on software engineering. Still, we argue that the presuppositions are untenable in light of current practices. For one thing, software engineers cannot exert complete control because software has become too complex for any technique to reliably locate every fault in it. For another, the creation and running of software are nowadays heavily mediated processes involving many agential activities. As a result, the performance of digital artifacts may vary, often in undesirable ways, without either hardware failures or design errors. This undermines the conclusion that software cannot malfunction, while also revealing the complications in developing a metaphysical account of software that fits contemporary practices. (shrink)

Sustainability in systems refers to applying sustainable principles and practices to create more resilient, efficient, and equitable systems that promote the well-being of people and the planet. Sustainability is an essential topic in contemporary software engineering, and its relationship with the characteristics and properties of a system or product called quality attributes is still an open question since each researcher has established their definition of sustainability in software. This has created diverse terms and concepts for distinct application environments (...) and scopes, creating ambiguity and misconceptions. This work defines a domain ontology of Sustainability in Software named SinSO to address these issues. SinSO was implemented in OWL, using competency-based questions to validate. The findings show that this proposal satisfies several quality and content requirements. Also, using Protégé and the Hermit reasoner, we verified that SinSO is consistent since the ontology statements are coherent and do not lead to conflicting or contradictory conclusions. In addition, competency questions allowed us to demonstrate that SinSO does fulfill its purpose. FOCA methodology allowed us to evaluate SinSO quality. Also, SinSO was used in two case studies, one about software for senior-citizen smart-home, and the other, a simulator to develop and test smart-city applications, achieving positive outcomes. To verify its accuracy, completeness, and maintainability, further evaluations of SinSO are needed in real case studies. We conclude that SinSO can significantly contribute to reducing ambiguity and enhancing comprehension in this area. Furthermore, SinSO can be an effective tool for engineers to recognize the concepts and relationships in the sustainable domain to consider in the systems development life cycle to build sustainable systems. (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)

Should software be sold “as is”, totally guaranteed, or something else? This paper suggests that “informed consent”, used extensively in medical ethics, is an appropriate way to envision the buyer/developer relationship when software is sold. We review why the technical difficulties preclude delivering perfect software, but allow statistical predictions about reliability. Then we borrow principles refined by medical ethics and apply them to computer professionals.

Computation of seismic parameters and its interpretation from the recorded earthquake signal is empowered by digital data acquisition systems. This enables seismologist to automatically compute all the relevant parameters. Futuristic applications require extensive software development to implement seismic prediction and forecasting models. While developing such models, software developer prefer to write their own in-house analysis & modeling software with complete control over the required computations and models. This paper presents simplified mathematical framework of the seismic events and (...) back-end computational software logic & algorithm to provide a simple framework to software engineers develop customized seismic analysis & computation software. (shrink)

The distinction between the modeling of information and the modeling of data in the creation of automated systems has historically been important because the development tools available to programmers have been wedded to machine oriented data types and processes. However, advances in software engineering, particularly the move toward data abstraction in software design, allow activities reasonably described as information modeling to be performed in the software creation process. An examination of the evolution of programming languages and development (...) of general programming paradigms, including object-oriented design and implementation, suggests that while data modeling will necessarily continue to be a programmer's concern, more and more of the programming process itself is coming to be characterized by information modeling activities. (shrink)

Software systems play an ever more important role in our lives and software engineers and their companies find themselves in a position where they are held responsible for ethical issues that may arise. In this paper, we try to disentangle ethical considerations that can be performed at the level of the software engineer from those that belong in the wider domain of business ethics. The handling of ethical problems that fall into the responsibility of the (...) class='Hi'>engineer has traditionally been addressed by the publication of Codes of Ethics and Conduct. We argue that these Codes are barely able to provide normative orientation in software development. The main contribution of this paper is, thus, to analyze the normative features of Codes of Ethics in software engineering and to explicate how their value-based approach might prevent their usefulness from a normative perspective. Codes of Conduct cannot replace ethical deliberation because they do not and cannot offer guidance because of their underdetermined nature. This lack of orientation, we argue, triggers reactive behavior such as “cherry-picking,” “risk of indifference,” “ex-post orientation,” and the “desire to rely on gut feeling.” In the light of this, we propose to implement ethical deliberation within software development teams as a way out. (shrink)