software

work

engineers

code

ethical

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

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

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

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

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

7. The dynamic and demanding context of software engineering requires a code that is adaptable and relevant to new situations as they occur.

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. Extend software engineering knowledge by appropriate participation in professional organizations, meetings and publications.

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

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

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

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. Work to develop software and related documents that respect the privacy of those who will be affected by that software.

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

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. Ensure an appropriate method is used for any project on which they work or propose to work.

10. The ultimate effect of the work should be to the public good.

1. Principle 6: PROFESSIONSoftware engineers shall advance the integrity and reputation of the profession consistent with the public interest.

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

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

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

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. Attract potential software engineers only by full and accurate description of the conditions of employment.

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

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

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. In particular, software engineers shall, as appropriate:Help develop an organizational environment favorable to acting ethically.

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

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

3. The dynamic and demanding context of software engineering requires a code that is adaptable and relevant to new situations as they occur.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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