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

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

3. Be fair and avoid deception in all statements, particularly public ones, concerning software or related documents, methods and tools.

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. Not knowingly use software that is obtained or retained either illegally or unethically.

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

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

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

9. Extend software engineering knowledge by appropriate participation in professional organizations, meetings and publications.

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

1. Improve their knowledge of relevant standards and the law governing the software and related documents on which they work.

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

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

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

5. Review the work of others in an objective, candid, and properly-documented way.

6. Improve their knowledge of this Code, its interpretation, and its application to their work.

7. Ensure adequate documentation, including significant problems discovered and solutions adopted, for any project on which they work.

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

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

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

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

3. Attract potential software engineers only by full and accurate description of the conditions of employment.

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

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

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

8. Principle 3: PRODUCTSoftware engineers shall ensure that their products and related modifications meet the highest professional standards possible.

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

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

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

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

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

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

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

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

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

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

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

10. Improve their knowledge of this Code, its interpretation, and its application to their work.

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 5: MANAGEMENTSoftware engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance .

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

4. Ethical tensions can best be addressed by thoughtful consideration of fundamental principles, rather than blind reliance on detailed regulations.

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

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