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

2. Treat all forms of software maintenance with the same professionalism as new development.

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

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

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

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

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

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

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

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

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. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.

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

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

6. Obey all laws governing their work, unless, in exceptional circumstances, such compliance is inconsistent with the public interest.

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

8. Assist colleagues in being fully aware of current standard work practices including policies and procedures for protecting passwords, files and other confidential information, and security measures in general.

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

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

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

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:Accept full responsibility for their own work.

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

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

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

8. In particular, software engineers shall, as appropriate:Temper all technical judgments by the need to support and maintain human values.

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

10. PRINCIPLESPrinciple 1: PUBLICSoftware engineers shall act consistently with the public interest.

1. It is not intended that the individual parts of the Code be used in isolation to justify errors of omission or commission.

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

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

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

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

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

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

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

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 is not a simple ethical algorithm that generates ethical decisions.

4. Be careful to use only accurate data derived by ethical and lawful means, and use it only in ways properly authorized.

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. Ethical tensions can best be addressed by thoughtful consideration of fundamental principles, rather than blind reliance on detailed regulations.

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

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

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

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