1. 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.
2. 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.
3. Software engineers are those who contribute by direct participation or by teaching, to the analysis, specification, design, development, certification, maintenance and testing of software systems.
4. Not ask a software engineer to do anything inconsistent with this Code.
5. 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.
6. Software engineers are those who contribute by direct participation or by teaching, to the analysis, specification, design, development, certification, maintenance and testing of software systems.
7. The dynamic and demanding context of software engineering requires a code that is adaptable and relevant to new situations as they occur.
8. 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.
9. Work to develop software and related documents that respect the privacy of those who will be affected by that software.
10. 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.
1. Keep private any confidential information gained in their professional work, where such confidentiality is consistent with the public interest and consistent with the law.
2. Accept no outside work detrimental to the work they perform for their primary employer.
3. Take responsibility for detecting, correcting, and reporting errors in software and associated documents on which they work.
4. 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.
5. Improve their knowledge of relevant standards and the law governing the software and related documents on which they work.
6. The ultimate effect of the work should be to the public good.
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. Improve their knowledge of this Code, its interpretation, and its application to their work.
9. Work to develop software and related documents that respect the privacy of those who will be affected by that software.
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. 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.
2. In particular, software engineers shall, as appropriate:Temper all technical judgments by the need to support and maintain human values.
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 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.
5. Attract potential software engineers only by full and accurate description of the conditions of employment.
6. 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.
7. 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.
8. Principle 3: PRODUCTSoftware engineers shall ensure that their products and related modifications meet the highest professional standards possible.
9. 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.
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. The Code is not simply for adjudicating the nature of questionable acts; it also has an important educational function.
2. Not ask a software engineer to do anything inconsistent with this Code.
3. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.
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. Not influence others to undertake any action that involves a breach of 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. Avoid associations with businesses and organizations which are in conflict with this code.
9. Recognize that personal violations of this Code are inconsistent with being a professional software engineer.
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. Not punish anyone for expressing ethical concerns about a project.
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. 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.
4. The Code is not a simple ethical algorithm that generates ethical decisions.
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. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of 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 is not a simple ethical algorithm that generates ethical decisions.
9. Ethical tensions can best be addressed by thoughtful consideration of fundamental principles, rather than blind reliance on detailed regulations.
10. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.