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

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

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

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. Improve their understanding of the software and related documents on which they work and of the environment in which they will be used.

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

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. Recognize that violations of this Code are inconsistent with being a professional software engineer.

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

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

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

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

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

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

7. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. The Principles identify the ethically responsible relationships in which individuals, groups, and organizations participate and the primary obligations within these relationships.

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

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