1. 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.
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. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer.
4. 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.
5. Consider issues of physical disabilities, allocation of resources, economic disadvantage and other factors that can diminish access to the benefits of software.
6. 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.
7. Ensure adequate testing, debugging, and review of software and related documents on which they work.
8. Be fair and avoid deception in all statements, particularly public ones, concerning software or related documents, methods and tools.
9. 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.
10. Attract potential software engineers only by full and accurate description of the conditions of employment.
1. Ensure adequate documentation, including significant problems discovered and solutions adopted, for any project on which they work.
2. 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.
3. The ultimate effect of the work should be to the public good.
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. In particular, software engineers shall, as appropriate:Accept full responsibility for their own work.
6. 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.
7. Ensure adequate testing, debugging, and review of software and related documents on which they work.
8. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.
9. Assign work only after taking into account appropriate contributions of education and experience tempered with a desire to further that education and experience.
10. Credit fully the work of others and refrain from taking undue credit.
1. In particular, software engineers shall, as appropriate:Accept full responsibility for their own work.
2. 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.
3. Principle 3: PRODUCTSoftware engineers shall ensure that their products and related modifications meet the highest professional standards possible.
4. 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.
5. Attract potential software engineers only by full and accurate description of the conditions of employment.
6. 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.
7. In accordance with that commitment, software engineers shall adhere to the following Code of Ethics and Professional Practice.
8. 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.
9. 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.
10. Principle 6: PROFESSIONSoftware engineers shall advance the integrity and reputation of the profession consistent with the public interest.
1. Support, as members of a profession, other software engineers striving to follow this Code.
2. The Code is not a simple ethical algorithm that generates ethical decisions.
3. The Code is not simply for adjudicating the nature of questionable acts; it also has an important educational function.
4. In particular, software engineers shall, as appropriate:Encourage colleagues to adhere to this Code.
5. It is not intended that the individual parts of the Code be used in isolation to justify errors of omission or commission.
6. Recognize that violations of this Code are inconsistent with being a professional software engineer.
7. 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.
8. Express concerns to the people involved when significant violations of this Code are detected unless this is impossible, counter-productive, or dangerous.
9. Not ask a software engineer to do anything inconsistent with this Code.
10. 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.
1. Be careful to use only accurate data derived by ethical and lawful means, and use it only in ways properly authorized.
2. The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal.
3. Ethical tensions can best be addressed by thoughtful consideration of fundamental principles, rather than blind reliance on detailed regulations.
4. 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.
5. The Code is not a simple ethical algorithm that generates ethical decisions.
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. 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 Principles identify the ethically responsible relationships in which individuals, groups, and organizations participate and the primary obligations within these relationships.
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. The Code is not a simple ethical algorithm that generates ethical decisions.