1. Maintain professional objectivity with respect to any software or related documents they are asked to evaluate.

2. 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.

3. Not knowingly use software that is obtained or retained either illegally or unethically.

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. Work to develop software and related documents that respect the privacy of those who will be affected by that software.

6. Moderate the interests of the software engineer, the employer, the client and the users with the public good.

7. Recognize that personal violations of this Code are inconsistent with being a professional software engineer.

8. 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.

9. In particular, software engineers shall, as appropriate:Encourage colleagues to adhere to this Code.

10. 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.

1. Ensure an appropriate method is used for any project on which they work or propose to work.

2. Accept no outside work detrimental to the work they perform for their primary employer.

3. 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.

4. Credit fully the work of others and refrain from taking undue credit.

5. The ultimate effect of the work should be to the public good.

6. Ensure that specifications for software on which they work have been well documented, satisfy the users’

7. 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.

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. 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.

10. Improve their understanding of the software and related documents on which they work and of the environment in which they will be used.

1. 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.

2. Principle 4: JUDGMENTSoftware engineers shall maintain integrity and independence in their professional judgment.

3. 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.

4. 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.

5. Principle 2: CLIENT AND EMPLOYERSoftware engineers shall act in a manner that is in the best interests of their client and employer, consistent with the public interest.

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. Ensure that software engineers are informed of standards before being held to them.

8. 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.

9. In particular, software engineers shall, as appropriate:Help develop an organizational environment favorable to acting ethically.

10. 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.

1. Support, as members of a profession, other software engineers striving to follow this Code.

2. Not influence others to undertake any action that involves a breach of this Code.

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. Express concerns to the people involved when significant violations of this Code are detected unless this is impossible, counter-productive, or dangerous.

5. Not ask a software engineer to do anything inconsistent with this Code.

6. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a 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. It is not intended that the individual parts of the Code be used in isolation to justify errors of omission or commission.

9. 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.

10. The Code is not simply for adjudicating the nature of questionable acts; it also has an important educational function.

1. 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.

2. 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.

3. The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal.

4. The Principles identify the ethically responsible relationships in which individuals, groups, and organizations participate and the primary obligations within these relationships.

5. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.

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. Not punish anyone for expressing ethical concerns about a project.

8. Principle 5: MANAGEMENTSoftware engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance .

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. 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.