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. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer.

3. In particular, software engineers shall, as appropriate:Accept full responsibility for their own work.

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

5. Consider issues of physical disabilities, allocation of resources, economic disadvantage and other factors that can diminish access to the benefits of software.

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

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

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

10. Work to develop software and related documents that respect the privacy of those who will be affected by that software.

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

2. Work to develop software and related documents that respect the privacy of those who will be affected by that software.

3. Ensure adequate documentation, including significant problems discovered and solutions adopted, for any project on which they 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. 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.

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

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

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

9. Keep private any confidential information gained in their professional work, where such confidentiality is consistent with the public interest and consistent with the law.

10. Assign work only after taking into account appropriate contributions of education and experience tempered with a desire to further that education and experience.

1. Principle 6: PROFESSIONSoftware engineers shall advance the integrity and reputation of the profession consistent with the public interest.

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

3. In accordance with that commitment, software engineers shall adhere to the following Code of Ethics and Professional Practice.

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

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

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

7. Principle 7: COLLEAGUESSoftware engineers shall be fair to and supportive of their colleagues.

8. In particular, software engineers shall, as appropriate:Provide service in their areas of competence, being honest and forthright about any limitations of their experience and education.

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

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

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

2. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer.

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

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

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

6. The Code is not a simple ethical algorithm that generates ethical decisions.

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

9. Avoid associations with businesses and organizations which are in conflict with this code.

10. Provide for due process in hearing charges of violation of an employer's policy or of this Code.

1. The Code is not a simple ethical algorithm that generates ethical decisions.

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

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

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

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

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

8. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.

9. Not punish anyone for expressing ethical concerns about a project.

10. The Code is not a simple ethical algorithm that generates ethical decisions.