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. 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 Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.

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

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

6. Improve their ability to create safe, reliable, and useful quality software at reasonable cost and within a reasonable time.

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

9. Strive to fully understand the specifications for software on which they work.

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

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

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

3. Ensure proper and achievable goals and objectives for any project on which they work or propose.

4. Strive to fully understand the specifications for software on which they work.

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

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

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. Improve their knowledge of this Code, its interpretation, and its application to their work.

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

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

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

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

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

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

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

9. Software engineers are those who contribute by direct participation or by teaching, to the analysis, specification, design, development, certification, maintenance and testing of software systems.

10. Ensure that software engineers are informed of standards before being held to them.

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

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

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. In particular, software engineers shall, as appropriate:Encourage colleagues to adhere to this Code.

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

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

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

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 influence others to undertake any action that involves a breach of this Code.

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

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

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

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

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

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

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

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

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

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