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 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)

It is argued that GDPR suffer from a practical problem of click-through consents, which developers of web browsers should resolve.

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)

Recent innovations in computer software development have produced a new breed of pet, AIBO 2, a robotic pet that simulates the behavior of real pets. This paper argues that software developers who create such simulations have ethical responsibilities to product users and to society. The paper concludes with some general ethical guidelines for software developers to follow when engaged in projects involving real-world simulations.

This open access book bridges the gap between ethical theory and software practice. It introduces foundational concepts in digital ethics, highlights the distinctive nature of software as a technology, and offers a systematic approach to integrating ethics into the development process. The book is structured in eight chapters: it starts with an Introduction presenting a historical overview that puts the relation between ethics and technology (with software as a special kind of technology) in context. Next, What (...) is (Digital) Technology? explores various philosophical perspectives on technology and underlines why software producers carry a significant ethical responsibility. Why develop Software ethically? then explores the ethical imperative for software development and advocates for a dynamic hybrid approach that combines universal ethical principles with context-sensitive, participatory methods, while What is Ethics? introduces the foundational concepts of ethics and explores their relevance for software development. Subsequently, Values and Software explores the central role of values in ethical software development discussions. Spotting the Right - Overcoming Moral Uncertainty then addresses the foundational phase of ethical practice and examines the epistemic challenge of identifying morally significant aspects in software design, and Deciding for the Good - Overcoming Moral Indecisiveness examines the challenges of ethical decision-making in software development and highlights the necessity of ethical deliberation to navigate value conflicts such as usability versus explainability, and safety versus autonomy. Eventually, Organization, People and Processes underlines the crucial role organizational structures play in enabling ethical deliberation within software development. The book offers practitioners a clear orientation in the increasingly bewildering landscape of normative demands, value lists, ethical guidelines, and codes of conduct that have emerged around ethically informed software development. It especially aims at practitioners, product managers, policymakers, and students who wish to understand the ethical dimensions of the software systems they develop or regulate. (shrink)

In this study, we explore the future of work by examining differences in productivity when teams are composed of only humans or both humans and machine agents. Our objective was to characterize the similarities and differences between human and human–machine teams as they work to coordinate across their specialized roles. This form of research is increasingly important given that machine agents are becoming commonplace in sociotechnical systems and playing a more active role in collaborative work. One particular class of machine (...) agents, bots, is being introduced to these systems to facilitate both taskwork and teamwork. We investigated the association between bots and productivity outcomes in open source software development through an analysis of hundreds of project teams. The presence of bots in teams was associated with higher levels of productivity and higher work centralization in addition to greater amounts of observed communication. The adoption of bots in software teams may have tradeoffs, in that doing so may increase productivity, but could also increase workload. We discuss the theoretical and practical implications of these findings for advancing human–machine teaming research. (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)

Two property regimes for software development may be distinguished. Within corporations, on the one hand, a Private Regime obtains which excludes all outsiders from access to a firm's software assets. It is shown how the protective instruments of secrecy and both copyright and patent have been strengthened considerably during the last two decades. On the other, a Public Regime among hackers may be distinguished, initiated by individuals, organizations or firms, in which source code is freely exchanged. It (...) is argued that copyright is put to novel use here: claiming their rights, authors write `open source licenses' that allow public usage of the code, while at the same time regulating the inclusion of users. A `regulated commons' is created. The analysis focuses successively on the most important open source licenses to emerge, the problem of possible incompatibility between them (especially as far as the dominant General Public License is concerned), and the fragmentation into several user communities that may result. (shrink)

Karina Kohl (Uber) and Rafael Prikladnicki (PUCRS).

This paper shows the relevance of hermeneutic philosophy to understand how info­communication technologies frame our contemporary lifeworld. It demonstrates that the programming languages are the result of collective interpretations of the general lifeworld of programmers, management and political decision-makers. By having been inscribed into the processes of language use, this general interpretation permeates the particular practices of understanding that are possible within the language framework.

In this paper, we explore how the choices of boundary work in software development influence the team autonomy enacted by team members. Boundary work is when people protect their professional individual autonomy, when they downplay that autonomy to collaborate over professional boundaries, and when they create new boundaries. Team autonomy is here defined as a team using their autonomy to collaborate in deciding their own output. We use an action research design, with varied methodologies carried out through three (...) action cycles. Our findings show that when collective, collaborative boundary work is not performed, a sort of individualized zone occurs where individuals either try to do collaborative boundary work by themselves or seek individual autonomy. We propose that individual autonomy can be divided into professional individual autonomy and situationally dependent individual autonomy. This research contributes theoretically by showing how the absence of collaborative boundary work can lead to an individualized zone. Practically, it can improve team autonomy by enhancing the understanding of why teams should perform collaborative boundary work. The value of the concept of boundary work used in this setting involves studying the intentions for collaboration, not whether collaboration actually takes place. (shrink)

This essay explores the controversy over peer-to-peer (p2p) software, examining the legal and ethical dimensions of allowing software companies to develop p2p technologies. It argues that, under the Supreme Court’s ruling in the Sony betamax case, technology developers must be accorded the freedom to innovate and develop technologies that are capable of substantial noninfringing uses. This doctrine, known as the Sony doctrine, provides an important safe harbor for technological development, including p2p. The safe harbor, however, does not (...) immunize conduct beyond the design, sale, or supply of the product. For other conduct that falls outside the Sony safe harbor, the traditional standards of secondary liability apply. (shrink)

This paper focuses on the study of the Software Development Life Cycle (SDLC) implementation of software development project in an insurance company name “Preeminence” in Jakarta, Indonesia. Initial findings in this corporation reveal that several key people who had using Agile SDLC, mentioned they need some accommodation when implementing Agile during a project. Previous studies had introduced the additional process to help a project using Agile. However, studies that explored the importance of experience-based learning process during (...) Agile implementation are noticeably lacking. The needs of the experience-based learning process to explore the learning process as a factor for adaptation of Agile implementation, which hopes to increase the success of a project when using the Agile framework. Methods carried out in this research are based on archival research strategy by examining extant research on Agile adaptation for software projects implementation which published from 1999. Many studies focus on Agile implementation related to content and context to put additional process as an accommodation to easier a project using Agile. However, only a few discussed the process, particularly the learning process which is mean that research gap exists in the area of Agile implementation relates to the learning process. (shrink)

Measuring and evaluating a learner’s learning ability is always the focus of every person whose aim is to develop strategies and plans for their learners to improve the learning process. For example, classroom assessments, self-assessment using computer systems such as Intelligent Tutoring Systems, and other approaches are available. Assessment of metacognition is one of these techniques. Having the ability to evaluate and monitor one’s learning is known as metacognition. An individual can then propose adjustments to their learning process based on (...) this assessment. By monitoring, improving, and planning their activities, learners who can manage their cognitive skills are better able to manage their knowledge about a particular subject. It is common knowledge that students’ metacognitive and self-assessment skills and abilities have been extensively studied, but no research has been carried out on the mistakes that novice developers make because they do not use their self-assessment abilities enough. This study aims to assess the metacognitive skills and abilities of novice software developers working in the industry and to describe the consequences of awareness of metacognition on their performance. In the proposed study, we experimented with novice software developers and collected data using Devskiller and a self-assessment log to analyze their use of self-regulation skills. The proposed study showed that when developers are asked to reflect upon their work, they become more informed about their habitual mistakes, and using a self-assessment log helps them highlight their repetitive mistakes and experiences which allows them to improve their performance on future tasks. (shrink)

Laboratory studies provide the classic examples of ethnography in Science and Technology Studies, however ethnographic methods can also offer insight into scientific and technological development that is geographically dispersed and mediated through computational tools and infrastructures. Sociologists of science studying software development projects are presented with a variety of infrastructures that together constitute the life of a software project. Such infrastructures include mailing lists, wikis, forums, and version control systems. In this chapter I consider how the (...) history of a project’s development, as recorded in its version control history (specifically, git and GitHub), can provide a useful resource to STS scholars interested in studying software development. I outline how git and GitHub can be used, what kinds of qualitative and quantitative data can be derived from them, and I evaluate the strengths and limitations of using this kind of data. (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)

To be successful, collaboration at work requires its participants to have a common sense about what is happening and where things are heading. But how can collaborators have such a sense in common if what is going on continuously changes? This study investigates the joint communicative work participants in collaborative activity do to remain aligned on how things are going and where things are at for the purpose of maintaining a ground in common. Our test case for illustrating this joint (...) work is the fluid and constantly changing world of software development. Our study uses a transactional approach to show how software developers working together continuously make available what they are attuned to, which constitutes their common ground that allows actions and talk to make sense. The common ground enables a common, inherently shared sense of what is happening and how things are going. Rather than having “meaning” in themselves, signifiers (words, gestures, body movements, cursor movements) create and are part of the common ground against which they make sense. Signifiers are motivated by and produce an accented visible that is available to all group members; and this accented visible (including the signs) makes for the common ground. (shrink)

The last years a growing body of research has been developed on tactile displays and interfaces, which can give physical form to digital information. In spite of the numerous tactile devices that h...

This paper outlines a critical, textual approach for the analysis of the relationship between different actors in information technology (IT) production, and further concretizes the approach in the analysis of the role of users in the open source software (OSS) development literature. Central concepts of the approach are outlined. The role of users is conceptualized as reader involvement aiming to contribute to the configuration of the reader (to how users and the parameters for their work practices are defined (...) in OSS texts). Afterwards, OSS literature addressing reader involvement is critically reviewed. In OSS context, the OSS writers as readers configure the reader and other readers are assumed to be capable of and interested in commenting the texts. A lack of OSS research on non-technical reader involvement is identified. Furthermore, not only are the OSS readers configured, but so are OSS writers. In OSS context while writers may be empowered, this clearly does not apply to the non-technical OSS readers. Implication for research and practice are discussed. (shrink)

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)

The proliferation of information and communication technologies (ICTs) into all aspects of life poses unique ethical challenges as our modern societies become increasingly dependent on the flawless operation of these technologies. As we increasingly entrust our privacy, our well-being and our lives to an ever greater number of computers we need to look more closely at the risks and ethical implications of these developments. By emphasising the vulnerability of software and the practice of professional software developers, we want (...) to make clear the ethical aspects of producing potentially flawed software. This paper outlines some of the vulnerabilities associated with software systems and identifies a number of social and organisational factors affecting software developers and contributing to these vulnerabilities. Scott A. Snook’s theory of practical drift is used as the basis for our analysis. We show that this theory, originally developed to explain the failure of a military organisation, can be used to understand how professional software developers “drift away” from procedures and processes designed to ensure quality and prevent software vulnerability. Based on interviews with software developers in two Norwegian companies we identify two areas where social factors compel software developers to drift away from a global set of rules constituting software development processes and methods. Issues of pleasure and control and difference in mental models contribute to an uncoupling from established practices designed to guarantee the reliability of software and thus diminish its vulnerability. (shrink)

PurposeOriginating in the USA and Northern Europe, Free and Open Source Software (FOSS) found on the internet its fertile environment. In more recent years, FOSS is becoming an increasingly important element in strategies for development and implementation of information and communication technologies also in developing countries. Mainstream research on FOSS has catered to the underlying principles or freedom, open organizational forms, and on its economical aspects. The purpose of this paper is to shed new light on the actual (...) consequences of FOSS, often left in the background.Design/methodology/approachThe paper examines where FOSS principles' assumptions are likely to be more evident: in contexts of developing countries, which are geographically and organizationally far from the original environment of FOSS. A mixed methodology characterizes this work: quantitative and qualitative methods bring readers' attention to unusual empirical settings and downplayed organizational processes of information technology (IT) implementation and adoption.FindingsThe consequences of FOSS on IT implementation and actual use are ambivalent. It is argued that FOSS adoption does not happen spontaneously, neither by decree, and that the relevance of open technologies as public goods remains in the different role of local actual technical and organizational capabilities, and environment conditions.Originality/valueSuch a focus complements existing studies on the economical relevance of FOSS, which are not the focus of this paper. (shrink)

Modern software is infested with flaws having information security aspects. Pervasive computing has made us and our society vulnerable. However, software developers do not fully comprehend what is at stake when faulty software is produced and flaws causing security vulnerabilites are discovered. To address this problem, the main actors involved with software vulnerability processes and the relevant roles inside these groups are identified. This categorisation is illustrated through a fictional case study, which is scrutinised in the (...) light of ethical codes of professional software engineers and common principles of responsibility attribution. The focus of our analysis is on the acute handling of discovered vulnerabilities in software, including reporting, correcting and disclosing these vulnerabilities. We recognise a need for guidelines and mechanisms to facilitate further improvement in resolving processes leading to and in handling software vulnerabilities. In the spirit of disclosive ethics we call for further studies of the complex issues involved. (shrink)

In this paper, we have developed an Excel package to be utilized for calculating neutrosophic data and analyze them. The use of object oriented programming techniques and concepts as they may apply to the design and development a new framework to implement neutrosophic data operations, the c# programming language, NET Framework and Microsoft Visual Studio are used to implement the neutrosophic classes. We have used Excel as it is a powerful tool that is widely accepted and used for statistical (...) analysis. Figure 1 shows Class Diagram of the implemented package. Figure 2 presents a working example of the package interface calculating the complement. Our implemented Neutrosophic package can calculate Intersection, Union, and Complement of the neutrosophic set. Figure 3 presents our neutrosophic package capability to draw figures of presented neutrosophic set. Figure 4 presents charting of Union operation calculation, and figure 5 Intersection Operation. neutrosophic set are characterized by its efficiency as it takes into consideration the three data items: True, Intermediate, and False. -/- . (shrink)

Design based research has been acknowledged as a productive approach for advancing educational technology. Coincidentally, open source software has been found to be a good fit for implementing design based research. This report presents a case study of a software project using a design-based research approach and free/open source software. The project, iSocial, is developing a 3D virtual environment for youth with autism spectrum disorders to develop social competence. The study illustrates how the flexibility and community features (...) of FOSS fit with the iterative nature of design-based research to benefit the development of iSocial, and the report also discusses challenges of implementing FOSS and DBR. (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 paper identifies that Information and Communication Technology (ICT) has a negative effect on software piracy rates in addition to consolidating prior research that economic development and the cultural dimension of individualism also negatively affect piracy rates. Using data for 59 countries from 2000 to 2005, the findings show that economic well-being, individualism and technology development as measured by ICT expenditures explain between 70% and 82% of the variation in software piracy rates during this period. The (...) research results provide important implications for policy makers and business practitioners to help reduce software piracy. (shrink)

This chapter explores the ethical imperative for software development, emphasizing the inherent embedding of values in technology and its profound impact on individual behavior and societal norms. Unlike traditional tools, software actively mediates user experiences and often operates beyond users’ awareness, shaping decisions and interactions through algorithms and interfaces. Recognizing this, the chapter argues for an anticipatory and proactive ethical stance, integrating ethical considerations from the outset of the development process through deployment and maintenance. The uniqueness (...) of software systems presents unique ethical challenges, notably the distribution and diffusion of responsibility. Responsibility cannot be adequately addressed by mere legal compliance or industry standards. Instead, it must encompass organizational culture, interdisciplinary collaboration, and ongoing ethical reflection throughout the software lifecycle. Practical approaches discussed include embedding ethical reflection into development processes, engaging diverse stakeholders, and fostering a shared sense of responsibility across development teams and organizational hierarchies. The chapter also critically assesses principle-based and bottom-up ethical frameworks, advocating for a dynamic hybrid approach that combines universal ethical principles with context-sensitive, participatory methods. This discursive approach emphasizes collaborative ethical deliberation, empowering developers, managers, and organizations to anticipate and address ethical concerns proactively. (shrink)

Software piracy, the illegal and unauthorized duplication, sale, or distribution of software, is a widespread and costly phenomenon. According to Business Software Alliance, over 41% of the PC software packages installed worldwide were unauthorized copies. Software piracy behavior has been investigated for more than 30 years. However, after a review of the relevant literature, there appears to be two voids in this literature: a lack of studies in non-Western countries and a scarcity of process studies. (...) This study contributes to literature by developing a software piracy model to better understand the decision-making process that underlies this unethical behavior. The model was tested using data collected from a sample of 323 undergraduate business students. Consistent with the Theory of Reasoned Action, attitudes toward software piracy and subjective norms were significant predictors of intention to pirate software. Also, the results suggested that ethical ideology, public self-consciousness, and low self-control moderated the effect of these variables on intention to pirate software. The results have important practical implications for the software industry and governments hoping to curtail software piracy. Limitations of the study and recommendations for future studies are discussed as well. (shrink)

One of the paradoxes of the free software ideology is its reliance on the legal institutions it was created to object to. One could argue that Free Software Foundation is using copyright to enforce their free software licenses as aggressively as the Business Software Alliance is enforcing its clients’ copyrights. We will show that the reality is more complex and that there is a significant difference: the free software community uses primarily non-legal enforcement methods and (...) trusts on social norms. We argue that free software could be used as a tool to make copyright more accepted in the less developed world because of its positive connection with copyright and community based approach. We explain why strong copyright is also in the interest of free software developers. The article concludes by suggesting that World Intellectual Property Organization should include free software into its development agenda. (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)

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)

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)

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)