1. Consider issues of physical disabilities, allocation of resources, economic disadvantage and other factors that can diminish access to the benefits of software.
2. Maintain professional objectivity with respect to any software or related documents they are asked to evaluate.
3. Work to develop software and related documents that respect the privacy of those who will be affected by that software.
4. Treat all forms of software maintenance with the same professionalism as new development.
5. 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.
6. 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.
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. These obligations are founded in the software engineer’
9. Recognize that personal violations of this Code are inconsistent with being a professional software engineer.
10. Not ask a software engineer to do anything inconsistent with this Code.
1. In particular, software engineers shall, as appropriate:Accept full responsibility for their own work.
2. Keep private any confidential information gained in their professional work, where such confidentiality is consistent with the public interest and consistent with the law.
3. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.
4. Ensure an appropriate method is used for any project on which they work or propose to work.
5. Accept no outside work detrimental to the work they perform for their primary employer.
6. 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.
7. 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.
8. 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.
9. Improve their knowledge of relevant standards and the law governing the software and related documents on which they work.
10. Improve their understanding of the software and related documents on which they work and of the environment in which they will be used.
1. 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.
2. Principle 7: COLLEAGUESSoftware engineers shall be fair to and supportive of their colleagues.
3. Support, as members of a profession, other software engineers striving to follow this Code.
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. In particular, software engineers shall, as appropriate:Encourage colleagues to adhere to this Code.
6. Principle 4: JUDGMENTSoftware engineers shall maintain integrity and independence in their professional judgment.
7. 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.
8. 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.
9. In particular, software engineers shall, as appropriate:Help develop an organizational environment favorable to acting ethically.
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. The Code is not simply for adjudicating the nature of questionable acts; it also has an important educational function.
2. It is not intended that the individual parts of the Code be used in isolation to justify errors of omission or commission.
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. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer.
5. The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal.
6. Express concerns to the people involved when significant violations of this Code are detected unless this is impossible, counter-productive, or dangerous.
7. In accordance with that commitment, software engineers shall adhere to the following Code of Ethics and Professional Practice.
8. 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.
9. Recognize that personal violations of this Code are inconsistent with being a professional software engineer.
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.
1. 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.
2. Not punish anyone for expressing ethical concerns about a project.
3. In particular, software engineers shall, as appropriate:Help develop an organizational environment favorable to acting ethically.
4. Be careful to use only accurate data derived by ethical and lawful means, and use it only in ways properly authorized.
5. The Principles identify the ethically responsible relationships in which individuals, groups, and organizations participate and the primary obligations within these relationships.
6. The Code is not a simple ethical algorithm that generates ethical decisions.
7. Ethical tensions can best be addressed by thoughtful consideration of fundamental principles, rather than blind reliance on detailed regulations.
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. 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.