1. Consider issues of physical disabilities, allocation of resources, economic disadvantage and other factors that can diminish access to the benefits of software.
2. Improve their understanding of the software and related documents on which they work and of the environment in which they will be used.
3. Work to develop software and related documents that respect the privacy of those who will be affected by that software.
4. Be accurate in stating the characteristics of software on which they work, avoiding not only false claims but also claims that might reasonably be supposed to be speculative, vacuous, deceptive, misleading, or doubtful.
5. Recognize that personal violations of this Code are inconsistent with being a professional software engineer.
6. The Code contains eight Principles related to the behavior of and decisions made by professional software engineers, including practitioners, educators, managers, supervisors and policy makers, as well as trainees and students of the profession.
7. Ensure that there is a fair agreement concerning ownership of any software, processes, research, writing, or other intellectual property to which a software engineer has contributed.
8. Strive to fully understand the specifications for software on which they work.
9. Because of their roles in developing software systems, software engineers have significant opportunities to do good or cause harm, to enable others to do good or cause harm, or to influence others to do good or cause harm.
10. Identify, document, and report significant issues of social concern, of which they are aware, in software or related documents, to the employer or the client.
1. Obey all laws governing their work, unless, in exceptional circumstances, such compliance is inconsistent with the public interest.
2. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.
3. Ensure an appropriate method is used for any project on which they work or propose to work.
4. Ensure realistic quantitative estimates of cost, scheduling, personnel, quality and outcomes on any project on which they work or propose to work and provide an uncertainty assessment of these estimates.
5. Accept no outside work detrimental to the work they perform for their primary employer.
6. These Principles should influence software engineers to consider broadly who is affected by their work; to examine if they and their colleagues are treating other human beings with due respect; to consider how the public, if reasonably well informed, would view their decisions; to analyze how the least empowered will be affected by their decisions; and to consider whether their acts would be judged worthy of the ideal professional working as a software engineer.
7. Strive to fully understand the specifications for software on which they work.
8. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.
9. Work to follow professional standards, when available, that are most appropriate for the task at hand, departing from these only when ethically or technically justified.
10. Accept no outside work detrimental to the work they perform for their primary employer.
1. To ensure, as much as possible, that their efforts will be used for good, software engineers must commit themselves to making software engineering a beneficial and respected profession.
2. Principle 8: SELFSoftware engineers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession.
3. Not unfairly intervene in the career of any colleague; however, concern for the employer, the client or public interest may compel software engineers, in good faith, to question the competence of a colleague.
4. However, even in this generality, the Code provides support for software engineers and managers of software engineers who need to take positive action in a specific case by documenting the ethical stance of the profession.
5. Ensure that software engineers are informed of standards before being held to them.
6. Principle 7: COLLEAGUESSoftware engineers shall be fair to and supportive of their colleagues.
7. Ensure that software engineers know the employer's policies and procedures for protecting passwords, files and information that is confidential to the employer or confidential to others.
8. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.
9. PRINCIPLESPrinciple 1: PUBLICSoftware engineers shall act consistently with the public interest.
10. Because of their roles in developing software systems, software engineers have significant opportunities to do good or cause harm, to enable others to do good or cause harm, or to influence others to do good or cause harm.
1. Software Engineering Code of Ethics and Professional Practice (Full Version)PREAMBLEComputers have a central and growing role in commerce, industry, government, medicine, education, entertainment and society at large.
2. The Code is not simply for adjudicating the nature of questionable acts; it also has an important educational function.
3. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.
4. Recognize that violations of this Code are inconsistent with being a professional software engineer.
5. The dynamic and demanding context of software engineering requires a code that is adaptable and relevant to new situations as they occur.
6. Ensure that clients, employers, and supervisors know of the software engineer's commitment to this Code of ethics, and the subsequent ramifications of such commitment.
7. Support, as members of a profession, other software engineers striving to follow this Code.
8. In all these judgments concern for the health, safety and welfare of the public is primary; that is, the "Public Interest" is central to this Code.
9. In accordance with that commitment, software engineers shall adhere to the following Code of Ethics and Professional Practice.
10. These situations require the software engineer to use ethical judgment to act in a manner which is most consistent with the spirit of the Code of Ethics and Professional Practice, given the circumstances.
1. Be careful to use only accurate data derived by ethical and lawful means, and use it only in ways properly authorized.
2. Ethical tensions can best be addressed by thoughtful consideration of fundamental principles, rather than blind reliance on detailed regulations.
3. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.
4. Principle 8: SELFSoftware engineers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession.
5. However, even in this generality, the Code provides support for software engineers and managers of software engineers who need to take positive action in a specific case by documenting the ethical stance of the profession.
6. Principle 5: MANAGEMENTSoftware engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance .
7. Not punish anyone for expressing ethical concerns about a project.
8. The Code is not a simple ethical algorithm that generates ethical decisions.
9. Promote no interest adverse to their employer or client, unless a higher ethical concern is being compromised; in that case, inform the employer or another appropriate authority of the ethical concern.
10. These situations require the software engineer to use ethical judgment to act in a manner which is most consistent with the spirit of the Code of Ethics and Professional Practice, given the circumstances.