1. 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.
2. Refuse to participate, as members or advisors, in a private, governmental or professional body concerned with software related issues, in which they, their employers or their clients have undisclosed potential conflicts of interest.
3. Cooperate in efforts to address matters of grave public concern caused by software, its installation, maintenance, support or documentation.
4. 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.
5. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.
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. Promote public knowledge of software engineering.
8. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.
9. 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.
10. Work to develop software and related documents that respect the privacy of those who will be affected by that software.
1. Review the work of others in an objective, candid, and properly-documented way.
2. 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.
3. 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.
4. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.
5. Obey all laws governing their work, unless, in exceptional circumstances, such compliance is inconsistent with the public interest.
6. Accept no outside work detrimental to the work they perform for their primary employer.
7. Accept no outside work detrimental to the work they perform for their primary employer.
8. Improve their knowledge of this Code, its interpretation, and its application to their work.
9. In particular, software engineers shall, as appropriate:Accept full responsibility for their own work.
10. Ensure that they are qualified for any project on which they work or propose to work by an appropriate combination of education and training, and experience.
1. Support, as members of a profession, other software engineers striving to follow this Code.
2. In particular, software engineers shall, as appropriate:Accept full responsibility for their own work.
3. 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.
4. Principle 4: JUDGMENTSoftware engineers shall maintain integrity and independence in their professional judgment.
5. In particular, those managing or leading software engineers shall, as appropriate:Ensure good management for any project on which they work, including effective procedures for promotion of quality and reduction of risk.
6. Principle 3: PRODUCTSoftware engineers shall ensure that their products and related modifications meet the highest professional standards possible.
7. In particular, software engineers shall, as appropriate:Strive for high quality, acceptable cost and a reasonable schedule, ensuring significant tradeoffs are clear to and accepted by the employer and the client, and are available for consideration by the user and the public.
8. Principle 7: COLLEAGUESSoftware engineers shall be fair to and supportive of their colleagues.
9. 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.
10. Software engineers are those who contribute by direct participation or by teaching, to the analysis, specification, design, development, certification, maintenance and testing of software systems.
1. As this Code expresses the consensus of the profession on ethical issues, it is a means to educate both the public and aspiring professionals about the ethical obligations of all software engineers.
2. Recognize that violations of this Code are inconsistent with being a professional software engineer.
3. 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.
4. The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal.
5. In particular, software engineers shall, as appropriate:Encourage colleagues to adhere to this Code.
6. Avoid associations with businesses and organizations which are in conflict with this code.
7. Report significant violations of this Code to appropriate authorities when it is clear that consultation with people involved in these significant violations is impossible, counter-productive or dangerous.
8. 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.
9. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer.
10. 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.
1. Not punish anyone for expressing ethical concerns about a project.
2. 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.
3. The Principles identify the ethically responsible relationships in which individuals, groups, and organizations participate and the primary obligations within these relationships.
4. 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.
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. The Code is not a simple ethical algorithm that generates ethical decisions.
7. 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.
8. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.
9. The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal.
10. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.