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)

Software is a ubiquitous artifact, yet not much has been done to understand its ontological nature. There are a few accounts offered so far about the nature of software. I argue that none of those accounts give a plausible picture of the nature of software. I draw attention to the striking similarities between software and musical works. These similarities motivate to look more closely on the discussions regarding the nature of the musical works. With the lessons (...) drawn from the ontology of musical works I offer a novel account of the nature of software. In this account, software is an abstract artifact. I elaborate the conditions under which software comes into existence; how it persists; how and on which entities its existence depends. (shrink)

Free and open source software is taking an increasingly significant role in our software infrastructure. Yet many questions still exist about whether a software economy based on FOSS would be viable. We argue that contemporary trends definitively demonstrate this viability. Claiming that an economy must be evaluated as much by the ends it brings about as by its size or vigor, we draw on widely accepted notions of redistributive justice to show the ethical superiority of a (...) class='Hi'>software economy based on FOSS. (shrink)

Claims about the potential of free software to reform the production and distribution of software are routinely countered by skepticism that the free software community fails to engage the pragmatic and economic ‘realities’ of a software industry. We argue to the contrary that contemporary business and economic trends definitively demonstrate the financial viability of an economy based on free software. But the argument for free software derives its true normative weight from social justice considerations: (...) the evaluation of the basis for a software economy should be guided by consideration of the social and cultural states which are the ultimate goals of any economic arrangement. That is, the software economy should be evaluated in light of its ability to provide justice. We conclude with a discussion of possible avenues for reform. (shrink)

Conceptual models are descriptions of our ideas about a problem, used to shape the implementation of a solution to it. Everyone who builds complex information systems uses such models - be they requirements analysts, knowledge modellers or software designers - but understanding of the pragmatics of model design tends to be informal and parochial. Lightweight uses of logic can add precision without destroying the intuitions we use to interpret our descriptions. Computing with logic allows us to make use of (...) this precision in providing automated support tools. Modern information scientists need to know what these methods are for and may need to build their own. This book gives you a place to begin. Where do you start when building models in a precise language like logic? One way is by following standard paradigms for design and adapting these to your needs. Some of these come from an analysis of existing informal notations. Others are from within logic itself. We take you through a sample of these, from more commonplace styles of formal modelling to non-standard methods such as techniques editing and argumentation. Each of these provides a window onto broader areas of applied logic and gives you a basis for adapting the method to your own needs. (shrink)

This paper argues that the difference between contemporary software intensive scientific practice and more traditional non-software intensive varieties results from the characteristically high conditionality of software. We explain why the path complexity of programs with high conditionality imposes limits on standard error correction techniques and why this matters. While it is possible, in general, to characterize the error distribution in inquiry that does not involve high conditionality, we cannot characterize the error distribution in inquiry that depends on (...) software. Software intensive science presents distinctive error and uncertainty modalities that pose new challenges for the epistemology of science. (shrink)

Researchers in virtually every discipline rely on sophisticated proprietary software for their work. However, some researchers are unable to afford the licenses and instead procure the software illegally. We discuss the prohibition of software piracy by intellectual property laws, and argue that the moral basis for the copyright law offers the possibility of cases where software piracy may be morally justified. The ethics codes that scientific institutions abide by are informed by a rule-consequentialist logic: by preserving (...) personal rights to authored works, people able to do so will be incentivized to create. By showing that the law has this rule-consequentialist grounding, we suggest that scientists who blindly adopt their institutional ethics codes will commit themselves to accepting that software piracy could be morally justified, in some cases. We hope that this conclusion will spark debate over important tensions between ethics codes, copyright law, and the underlying moral basis for these regulations. We conclude by offering practical solutions for researchers. (shrink)

This article integrates previously missing components of government quality into the governance-piracy nexus in exploring governance mechanisms by which global obligations for the treatment of IPRs are effectively transmitted from international to the national level in the battle against piracy. It assesses the best governance tools in the fight against piracy and upholding of intellectual property rights (IPRs). The instrumentality of IPR laws (treaties) in tackling piracy through good governance mechanisms is also examined. Findings demonstrate that: (1) while all governance (...) tools under consideration significantly decrease the incidence of piracy, corruption-control is the most effective weapon; (2) but for voice and accountability, political stability and democracy, IPR laws (treaties) are instrumental in tackling piracy through government quality dynamics of rule of law, regulation quality, government effectiveness, corruption-control, and press freedom. Hence, the need for a policy approach most conducive to expanding development is to implement an integrated system of both IPRs and corollary good governance policies. Moreover, our findings support the relevance of good governance measures in developing countries wishing to complement their emerging IPR regimes. (shrink)

The possible relationship between widespread unauthorized copying of microcomputer software (also known as software piracy) and level of moral judgment is examined through analysis of over 350 survey questionnaires that included the Defining Issues Test as a measure of moral development. It is hypothesized that the higher one''s level of moral judgment, the less likely that one will approve of or engage in unauthorized copying. Analysis of the data indicate a high level of tolerance toward unauthorized copying and (...) limited support for the hypothesis. The most plausible explanation for these findings is that software copying is perceived as an issue of low moral intensity. This study calls into question the software industry''s strategy of concentrating exclusively on institutional compliance with copyright rules, rather than working to raise the perceived moral intensity about software piracy at the individual level. As long as the issue remains low in moral intensity, the industry cannot expect significant shifts in copying behaviors. Individuals must become more aware of and concerned about the nature and magnitude of harm to society and to the rightful copyright owners from unauthorized copying before their attitudes and behaviors come to reflect higher levels of moral judgment. (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 neural correlates of software programming skills have been the target of an increasing number of studies in the past few years. Those studies focused on error-monitoring during software code inspection. Others have studied task-related cognitive load as measured by distinct neurophysiological measures. Most studies addressed only syntax errors. However, a recent functional MRI study suggested a pivotal role of the insula during error-monitoring when challenging deep-level analysis of code inspection was required. This raised the hypothesis that the (...) insula is causally involved in deep error-monitoring. To confirm this hypothesis, we carried out a new fMRI study where participants performed a deep source-code comprehension task that included error-monitoring to detect bugs in the code. The generality of our paradigm was enhanced by comparison with a variety of tasks related to text reading and bugless source-code understanding. Healthy adult programmers participated in this 3T fMRI experiment. The activation maps evoked by error-related events confirmed significant activations in the insula [p < 0.05]. Importantly, a posterior-to-anterior causality shift was observed concerning the role of the insula: in the absence of error, causal directions were mainly bottom-up, whereas, in their presence, the strong causal top-down effects from frontal regions, in particular, the anterior cingulate cortex was observed. (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.

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)

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 paper contributes to the computer ethics debate on software ownership protection by examining the ontological, methodological, and ethical problems related to property right infringement that should come prior to any legal discussion. The ontological problem consists in determining precisely what it is for a computer program to be a copy of another one, a largely neglected problem in computer ethics. The methodological problem is defined as the difficulty of deciding whether a given software system is a copy (...) of another system. And the ethical problem corresponds to establishing when a copy constitutes, or does not constitute, a property right infringement. The ontological problem is solved on the logical analysis of abstract machines, and the latter are argued to be the appropriate level of abstraction for software at which the methodological and the ethical problems can be successfully addressed. (shrink)

This e-book set includes two winning guides on Nik Software tools Designed to save time in the digital workflow, Nik Software?s entire suite of products (Dfine 2.0, Color Efex Pro 4.0, Sharpener Pro 3.0, Silver Efex Pro 2, VIVEZA 2.0, and ...

Software ownership allows the owner to restrict the distribution of software and to prevent others from reading the software’s source code and building upon it. However, free software is released to users under software licenses that give them the right to read the source code, modify it, reuse it, and distribute the software to others. Proponents of free software such as Richard M. Stallman and Eben Moglen argue that the social disutility of (...) class='Hi'>software ownership is a sufficient justification for prohibiting it. This social disutility includes the social instability of disregarding laws and agreements covering software use and distribution, inequality of software access, and the inability to help others by sharing software with them. Here I consider these and other social disutility claims against withholding specific software rights from users, in particular, the rights to read the source code, duplicate, distribute, modify, imitate, and reuse portions of the software within new programs. I find that generally while withholding these rights from software users does cause some degree of social disutility, only the rights to duplicate, modify and imitate cannot legitimately be denied to users on this basis. The social disutility of withholding the rights to distribute the software, read its source code and reuse portions of it in new programs is insufficient to prohibit software owners from denying them to users. A compromise between the software owner and user can minimise the social disutility of withholding these particular rights from users. However, the social disutility caused by software patents is sufficient for rejecting such patents as they restrict the methods of reducing social disutility possible with other forms of software ownership. (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.

Free software introduces a challenge to the classical conception of individual rights. The model of software licensing given by the General Public License generates the question whether it constitutes an exercise or a wavering of copyright. It is argued in this paper that the later alternative is entrenched in the classical concept of freedom as autonomy, which, by its turn, is reflected in a classical conception of individual rights based on the model of propriety as a dominion over (...) an exclusive object (res). We provide grounds for a concept of non-exclusive individual rights, based on the notion of freedom as reciprocity, in order to obtain more solid legal foundations for the free licensing of software. The concept of freedom as reciprocity and the corresponding reconstruction of non-exclusive subjective rights achieved in this paper is an exercise in general theory of law and thus may be applied to other legal fields where the classical notion of freedom and the property of exclusivity do not fit properly. (shrink)

What role can technology play in cultivating a disciplinary stance — raising questions, planning investigations, interpreting data and constructing explanations in a way that reflects disciplinary values and principles? How can overt and tacit expert scientific knowledge be captured, represented and used to design software that enables novices to assume a disciplinary stance in their investigations? We present The Galapagos Finches software designed to foster a biological and evolutionary stance. Our approach, Discipline-Specific Strategic Support , translates the main (...) variable types, comparison types and relationships in a discipline into manipulable objects in the interface. Pre/post-tests show how DSSS helps achieve a balance between content and process goals. A contrastive-case microanalysis of high, medium and low-achieving students' inquiry shows progress toward a disciplinary stance. Our study shows how software representations carry multiple levels of meaning, and that the efficacy of learning technologies hinges on reflection at both the navigation and disciplinary-signification levels. (shrink)

Design and Development of software controlled stand-alone instruments have been identified as the most vital component of national and international programs on earthquake hazard and risk management. For in depth investigation and studies, the development of precise instruments designed around computer is emerging very fast. Interfacing of personal computer with seismic instrument is an important design task. A design technique based on minimum hardware has been worked out around the parallel printer interface of computer. Hardware and Software for (...) this purpose has been designed to make the instrument interact with computer through parallel port interface. Incorporation of software for seismic signal analysis has been considered the extremely powerful tool to view and analyze seismic data collected by seismic instruments. In this paper efforts have been made to describe the various design aspects for interfacing of Seismic Data Recorder and Analyser to computer through parallel printer port and computation steps incorporated in the software tool for seismic data analysis. (shrink)

El empleo de softwares, aplicaciones y programas especializados ha cambiado la forma de desarrollar investigaciones, por lo que, en el ámbito universitario cobra especial importancia la inserción de estas herramientas en el aula. Así, en este trabajo se presentan dos programas informáticos ampliamente usados en la investigación lingüística y se expone la metodología seguida para su inclusión en una asignatura concreta. Finalmente, se comentan los resultados obtenidos y el grado de aceptación por parte del alumnado, a partir de los cuales (...) se extraen las conclusiones finales. (shrink)

Our freedoms in cyberspace are those granted by code and the protocols it implements. When man and machine interact, co-exist, and intermingle, cyberspace comes to interpenetrate the real world fully. In this cyborg world, software retains its regulatory role, becoming a language of interaction with our extended cyborg selves. The mediation of our extended selves by closed software threatens individual autonomy. We define a notion of freedom for software that does justice to our conception of it as (...) language, sketching the outlines of a social and political philosophy for a cyborg world. In a cyberspace underwritten by free software, political structures become contingent and flexible: the polity can choose to change the extent and character of its participation. The rejection of opaque power is an old anarchist ideal: free software, by making power transparent, carries the potential to place substantive restrictions on the regulatory power of cyborg government. (shrink)

For over 50 years, since the development of nuclear-armed ICBMs, the USA has sought a way to defend against them. These efforts evolved through various strategies and technologies: from nuclear-tipped rockets through space-based laser weapons to today’s system of ground-based kinetic-kill interceptors. Public debate around these issues reached a peak in the 1980s with President Reagan’s Strategic Defense Initiative, popularly known as Star Wars.Rebecca Slayton examines this history in Arguments that Count, a valuable and well-told account of a particular aspect (...) of missile defense: computer software. Missile defense required identifying a hostile missile launch, keeping track of thousands of incoming warheads on their ballistic trajectories, and directing interceptors to the right place—and doing all this in less than 30 minutes. From the outset, designers turned to computers to do the complex calculations quickly enough. But missile defense presented an additional factor, in that any m .. (shrink)

“Free software” is software that respects the users’ freedoms by granting them access to the source code, and allowing them to modify and redistribute the software at will. Richard Stallman, founder of the Free software movement, has argued that creating and distributing non-Free software is always a moral injustice. In this essay, I try to identify the ethical foundations of Stallmanism. I identify three major trends in Stallman’s thinking—libertarian, utilitarian, and communitarian—and I argue that none (...) is sufficient to justify the radical claim that distributing non-Free software is always wrong. I recommend thinking of Stallmanism as an attempt to optimize the satisfaction of a number of core values, including freedom, cooperation, and happiness, and I stress the importance of connecting the Free software movement to other political struggles against oppression. (shrink)

The use of Requirements at Runtime (RRT) is an emerging research area. Many methods and frameworks that make use of requirements models during software execution can be found in the literature. How...

Artefacts do not always do what they are supposed to, due to a variety of reasons, including manufacturing problems, poor maintenance, and normal wear-and-tear. Since software is an artefact, it should be subject to malfunctioning in the same sense in which other artefacts can malfunction. Yet, whether software is on a par with other artefacts when it comes to malfunctioning crucially depends on the abstraction used in the analysis. We distinguish between “negative” and “positive” notions of malfunction. A (...) negative malfunction, or dysfunction, occurs when an artefact token either does not or cannot do what it is supposed to. A positive malfunction, or misfunction, occurs when an artefact token may do what is supposed to but, at least occasionally, it also yields some unintended and undesirable effects. We argue that software, understood as type, may misfunction in some limited sense, but cannot dysfunction. Accordingly, one should distinguish software from other technical artefacts, in view of their design that makes dysfunction impossible for the former, while possible for the latter. (shrink)

The “free” in “free software” refers to a cluster of four specific freedoms identified by the Free Software Definition. The first freedom, termed “Freedom Zero,” intends to protect the right of the user to deploy software in whatever fashion, towards whatever end, he or she sees fit. But software may be used to achieve ethically questionable ends. This highlights a tension in the provision of software freedoms: while the definition explicitly forbids direct restrictions on users’ (...) freedoms, it does not address other means by which software may indirectly restrict freedoms. In particular, ethically-inflected debate has featured prominently in the discussion of restrictions on digital rights management and privacy-violating code in version 3 of the GPL (GPLv3). The discussion of this proposed language revealed the spectrum of ethical positions and valuations held by members of the free software community. In our analysis, we will provide arguments for upholding Freedom Zero; we embed the problem of possible uses of software in the broader context of the uses of scientific knowledge, and go on to argue that the provision of Freedom Zero mitigates against too great a moral burden—of anticipating possible uses of software—being placed on the programmer and that, most importantly, it facilitates deliberative discourse in the free software community. (shrink)

We suggest that the issue of constructing andverifying social procedures, which we suggestively call socialsoftware, be pursued as systematically as computer software is pursued by computer scientists. Certain complications do arise withsocial software which do not arise with computer software, but thesimilarities are nonetheless strong, and tools already exist which wouldenable us to start work on this important project. We give a variety ofsuggestive examples and indicate some theoretical work which alreadyexists.

A mass balance based model has been derived to represent the dynamical behavior of the ecosystem contained in an anaerobic digester. The model considers two bacterial populations: acidogenic and methanogenic bacteria. It forms the basis for the design of a software sensor considering both a model of the biological system and on-line gaseous measurements. The software sensor computes the concentration of inorganic carbon and volatile fatty acids (VFA) in the digester. Another software sensor is dedicated to the (...) estimation of the bacterial biomasses. The predictions of the software sensors for a real experiment are very close to the actual off-line measurements. The software sensors monitor the accumulation of VFA and thus very early detect a destabilization of the digester due to overloading. The presented methodology demonstrates the usefulness of advanced monitoring techniques for an improved understanding of the internal working of a biological system. (shrink)

Paper-based privacy policies fail to resolve the new changes posed by electronic healthcare. Protecting patient privacy through electronic systems has become a serious concern and is the subject of several recent studies. The shift towards an electronic privacy policy introduces new ethical challenges that cannot be solved merely by technical measures. Structured Patient Privacy Policy (S3P) is a software tool assuming an automated electronic privacy policy in an electronic healthcare setting. It is designed to simulate different access levels and (...) rights of various professionals involved in healthcare in order to assess the emerging ethical problems. The authors discuss ethical issues concerning electronic patient privacy policies that have become apparent during the development and application of S3P. (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)

O artigo tenta compreender como o software livre tornou-se vetor de um movimento social militante para criação e difusão de bens comuns. Como, para além de suas características de “meio” esses softwares foram transformados em questões de política, economia, sociedade, cultura e ética? São emergência, os modos de organização e as ideologias desse movimento que o artigo se propõe a analisar.

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)

This book engages directly in close readings of technical texts and computer code in order to show how software works. It offers an analysis of the cultural, political, and philosophical implications of software technologies that demonstrates the significance of software for the relationship between technology, philosophy, culture, and society.

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)

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)

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

Software piracy is a serious problem in the software industry. Software authors and publishing companies lose revenue when pirated software rather than legally purchased software is used. Policy developers are forced to invest time and money into restricting software piracy. Much of the published research literature focuses on software piracy by end-users. However, end-users are only able to copy software once the copy protection has been removed by a ‘cracker’. This research aims (...) to explore why, if copy protection is so difficult to remove, do crackers invest their skill and time in this activity instead of more lucrative and legal employment. This study develops a framework of neutralisation, justification and motivation and goes directly to the initial software crackers to determine what motivates their activities. The study first applies this framework in an anonymous online survey of crackers. The study then conducts cognitive interviews with eight crackers to explore and further validate the survey’s findings. The study finds the challenge of removing the copy protection from software as the strongest motivation for the actions of crackers. Desire for social participation, while found to be rewarding, was considered unnecessary for crackers to continue their actions. Higher social status was not a motivational factor but was a perceived by-product of cracking. The study also raises areas for future research. (shrink)

This paper analyzes both philosophical and practical assumptions underlying claims for the dual nature of software, including software as a machine made of text, and software as a concrete abstraction. A related view of computer science as a branch of pure mathematics is analyzed through a comparative examination of the nature of abstraction in mathematics and computer science. The relationship between the concrete and the abstract in computer programs is then described by exploring a taxonomy of approaches (...) borrowed from philosophy of mind. (shrink)

. Computational chemistry grew in a new era of “desktop modeling,” which coincided with a growing demand for modeling software, especially from the pharmaceutical industry. Parameterization of models in computational chemistry is an arduous enterprise, and we argue that this activity leads, in this specific context, to tensions among scientists regarding the epistemic opacity transparency of parameterized methods and the software implementing them. We relate one flame war from the Computational Chemistry mailing List in order to assess in (...) detail the relationships between modeling methods, parameterization, software and the various forms of their enclosure or disclosure. Our claim is that parameterization issues are an important and often neglected source of epistemic opacity and that this opacity is entangled in methods and software alike. Models and software must be addressed together to understand the epistemological tensions at stake. (shrink)

Software piracy is a damaging and important moral issue, which is widely believed to be unchecked in particular areas of the globe. This cross-cultural study examines differences in morality and behavior toward software piracy in Singapore versus the United States, and reviews the cultural histories of Asia versus the United States to explore why these differences occur. The paper is based upon pilot data collected in the U.S. and Singapore, using a tradeoff analysis methodology and analysis. The data (...) reveal some fascinating interactions between the level of ethical transgression and the rewards or consequences which they produce. (shrink)

This paper examines the impact of the level of economic development, income inequality, and five cultural variables on the rate of software piracy at the country level. The study finds that software piracy is significantly correlated to GNP per capita, income inequality, and individualism. Implications for anti-piracy programs and suggestions for future research are developed.

Push: Software Design and the Cultural Politics of Music Production shows how changes in the design of music software in the first decades of the twenty-first century shaped the production techniques and performance practices of artists working across media, from hip-hop and electronic dance music to video games and mobile apps. Emerging alongside developments in digital music distribution such as peer-to-peer file sharing and the MP3 format, digital audio workstations like FL Studio and Ableton Live introduced design affordances (...) that encouraged rapid music creation workflows through flashy, "user-friendly" interfaces. Meanwhile, software such as Avid's Pro Tools attempted to protect its status as the "industry standard," "professional" DAW of choice by incorporating design elements from pre-digital music technologies. Other software, like Cycling 74's Max, asserted its alterity to "commercial" DAWs by presenting users with nothing but a blank screen. These are more than just aesthetic design choices. Push examines the social, cultural, and political values designed into music software, and how those values become embodied by musical communities through production and performance. It reveals ties between the maximalist design of FL Studio, skeuomorphic design in Pro Tools, and gender inequity in the music products industry. It connects the computational thinking required by Max, as well as iZotope's innovations in artificial intelligence, with the cultural politics of Silicon Valley's "design thinking." Finally, it thinks through what happens when software becomes hardware, and users externalize their screens through the use of MIDI controllers, mobile media, and video game controllers. Amidst the perpetual upgrade culture of music technology, Push provides a model for understanding software as a microcosm for the increasing convergence of globalization, neoliberal capitalism, and techno-utopianism that has come to define our digital lives. (shrink)