1. The dynamic and demanding context of software engineering requires a code that is adaptable and relevant to new situations as they occur.
2. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer.
3. In particular, software engineers shall, as appropriate:Provide service in their areas of competence, being honest and forthright about any limitations of their experience and education.
4. 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.
5. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.
6. 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.
7. Identify, document, and report significant issues of social concern, of which they are aware, in software or related documents, to the employer or the client.
8. Work to develop software and related documents that respect the privacy of those who will be affected by that software.
9. Approve software only if they have a well-founded belief that it is safe, meets specifications, passes appropriate tests, and does not diminish quality of life, diminish privacy or harm the environment.
10. Disclose to appropriate persons or authorities any actual or potential danger to the user, the public, or the environment, that they reasonably believe to be associated with software or related documents.
1. Ensure that specifications for software on which they work have been well documented, satisfy the users’
2. Accept no outside work detrimental to the work they perform for their primary employer.
3. 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.
4. Ensure an appropriate method is used for any project on which they work or propose to work.
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. Review the work of others in an objective, candid, and properly-documented way.
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. 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. Keep private any confidential information gained in their professional work, where such confidentiality is consistent with the public interest and consistent with the law.
10. Work to develop software and related documents that respect the privacy of those who will be affected by that software.
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. Principle 2: CLIENT AND EMPLOYERSoftware engineers shall act in a manner that is in the best interests of their client and employer, consistent with the public interest.
3. 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.
4. 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.
5. 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.
6. 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.
7. Attract potential software engineers only by full and accurate description of the conditions of employment.
8. 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.
9. PRINCIPLESPrinciple 1: PUBLICSoftware engineers shall act consistently with the public interest.
10. 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.
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. 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.
3. Recognize that violations of this Code are inconsistent with being a professional software engineer.
4. Report significant violations of this Code to appropriate authorities when it is clear that consultation with people involved in these significant violations is impossible, counter-productive or dangerous.
5. 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.
6. Improve their knowledge of this Code, its interpretation, and its application to their work.
7. Support, as members of a profession, other software engineers striving to follow this Code.
8. Provide for due process in hearing charges of violation of an employer's policy or of this Code.
9. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer.
10. The Code is not a simple ethical algorithm that generates ethical decisions.
1. 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.
2. 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.
3. Not punish anyone for expressing ethical concerns about a project.
4. The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal.
5. The Principles identify the ethically responsible relationships in which individuals, groups, and organizations participate and the primary obligations within these relationships.
6. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.
7. In particular, software engineers shall, as appropriate:Help develop an organizational environment favorable to acting ethically.
8. Be careful to use only accurate data derived by ethical and lawful means, and use it only in ways properly authorized.
9. 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.
10. The Code is not a simple ethical algorithm that generates ethical decisions.