1. Approve software only if they have a well-founded belief that it is safe, meets specifications, passes appropriate tests, and does not diminish quality of life, diminish privacy or harm the environment.
2. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.
3. Principle 5: MANAGEMENTSoftware engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance .
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. s humanity, in special care owed to people affected by the work of software engineers, and the unique elements of the practice of software engineering.
6. In particular, software engineers shall continually endeavor to:Further their knowledge of developments in the analysis, specification, design, development, maintenance and testing of software and related documents, together with the management of the development process.
7. These obligations are founded in the software engineer’
8. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.
9. In particular, software engineers shall, as appropriate:Encourage colleagues to adhere to this Code.
10. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.
1. 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.
2. Obey all laws governing their work, unless, in exceptional circumstances, such compliance is inconsistent with the public interest.
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. 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. The ultimate effect of the work should be to the public good.
6. 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.
7. Accept no outside work detrimental to the work they perform for their primary employer.
8. 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.
9. Assist colleagues in being fully aware of current standard work practices including policies and procedures for protecting passwords, files and other confidential information, and security measures in general.
10. Ensure an appropriate method is used for any project on which they work or propose to work.
1. 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.
2. Support, as members of a profession, other software engineers striving to follow this Code.
3. PRINCIPLESPrinciple 1: PUBLICSoftware engineers shall act consistently with the public interest.
4. Principle 7: COLLEAGUESSoftware engineers shall be fair to and supportive of their colleagues.
5. In particular, software engineers shall, as appropriate:Help develop an organizational environment favorable to acting ethically.
6. Ensure that software engineers are informed of standards before being held to them.
7. 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.
8. 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.
9. s humanity, in special care owed to people affected by the work of software engineers, and the unique elements of the practice of software engineering.
10. In particular, software engineers shall, as appropriate:Temper all technical judgments by the need to support and maintain human values.
1. In accordance with that commitment, software engineers shall adhere to the following Code of Ethics and Professional Practice.
2. Recognize that violations of this Code are inconsistent with being a professional software engineer.
3. The dynamic and demanding context of software engineering requires a code that is adaptable and relevant to new situations as they occur.
4. 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.
5. Support, as members of a profession, other software engineers striving to follow this Code.
6. 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.
7. 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.
8. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer.
9. In particular, software engineers shall, as appropriate:Encourage colleagues to adhere to this Code.
10. It is not intended that the individual parts of the Code be used in isolation to justify errors of omission or commission.
1. Ethical tensions can best be addressed by thoughtful consideration of fundamental principles, rather than blind reliance on detailed regulations.
2. 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.
3. The Code is not a simple ethical algorithm that generates ethical decisions.
4. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.
5. 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.
6. 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.
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. The Code is not a simple ethical algorithm that generates ethical decisions.
9. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.
10. 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.