Professional Ethics In Computing

Some of the disagreements that arise in computer ethics are based on approaching ethics from two apparently contradictory directions; one a virtue based ethics and the other a rights-duty based ethics. My recent experience with the development of the Software Engineering Code of Ethics and Professional Practice leads me to believe that if the differences between these ethical positions is made clear then some of the problems in reasoning about computer ethics will be reduced. The ACM and the IEEE-Computer Society have recently adopted the Software Engineering Code of Ethics and Professional Practice as the standard for the teaching and practice of software engineering. The ACM/IEEE-CS task force on Software Engineering Ethics and Professional Practices developed this code[ appendix 1] for a sub-specialization within the constituencies of both of the professional societies. The composition of the task force is multinational in both citizenship and in membership in professional computing organizations. There were two ethical approaches of by members of the task force to this project, but there was an achievement of consensus between them. Several of the ethical discussions about the Code are related to the relative position of rights/obligations based ethics versus virtue based ethics. This is reflected, for example, in different values placed on privacy. This difference between rights and virtue based ethics as a primary assumption was reflected in differing views on the actual and acceptable roles of governments in the software development process and reflected in different values or obligations related to the roles of government and individuals in protecting data integrity. The lessons learned from developing of the Software Engineering Code of Ethics (www-cs.etsu.edu/seeri) and relating these approaches to ethics provide indications on how to improve the ethics education of computer professionals. The observations in this paper were made during my tenure as chair of the task force developing this Code of Ethics. The generalizations in this paper, like all generalizations are subject to exceptions. With this cautionary word, I will now venture to blatantly categorize ethical approaches. The developme nt of the Code was an iterative process. The task force examined several existing codes of ethics from computing societies, engineering societies and other professions such as accounting. [1] We also considered the goals and functions of these codes and then, via e-mail, selected out various imperatives to be placed in the software engineering code. We also contributed new imperatives related to our knowledge of software engineering. There was immediately a discernable difference between North American and Northern European contributions and concerns. As we circulated early drafts to colleagues for comment, the colleagues' responses seemed to also reflect a difference their approach to ethics; one was a virtue based ethics and the other was a rights/obligations based ethics. The draft Code of Ethics that resulted reflected these two different approaches to ethics. The members of the task force did not mention these two schools of ethics, but their responses could easily be categorized as belonging