1. Treat all forms of software maintenance with the same professionalism as new development.
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. Moderate the interests of the software engineer, the employer, the client and the users with the public good.
4. 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.
5. 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.
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. Maintain professional objectivity with respect to any software or related documents they are asked to evaluate.
8. The Code helps to define those actions that are ethically improper to request of a software engineer or teams of software engineers.
9. Ensure that specifications for software on which they work have been well documented, satisfy the users’
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. The ultimate effect of the work should be to the public good.
2. Ensure adequate testing, debugging, and review of software and related documents on which they work.
3. Improve their knowledge of this Code, its interpretation, and its application to their work.
4. 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.
5. Improve their knowledge of relevant standards and the law governing the software and related documents on which they work.
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. Ensure proper and achievable goals and objectives for any project on which they work or propose.
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. 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.
10. 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.
1. Principle 7: COLLEAGUESSoftware engineers shall be fair to and supportive of their colleagues.
2. Support, as members of a profession, other software engineers striving to follow this Code.
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. 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.
5. Principle 3: PRODUCTSoftware engineers shall ensure that their products and related modifications meet the highest professional standards possible.
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. 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.
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. Attract potential software engineers only by full and accurate description of the conditions of employment.
10. 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.
1. Improve their knowledge of this Code, its interpretation, and its application to their work.
2. 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.
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. In particular, software engineers shall, as appropriate:Encourage colleagues to adhere to this Code.
5. Avoid associations with businesses and organizations which are in conflict with this code.
6. Recognize that violations of this Code are inconsistent with being a professional software engineer.
7. The dynamic and demanding context of software engineering requires a code that is adaptable and relevant to new situations as they occur.
8. The Code prescribes these as obligations of anyone claiming to be or aspiring to be a software engineer.
9. The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal.
10. It is not intended that the individual parts of the Code be used in isolation to justify errors of omission or commission.
1. Identify, define and address ethical, economic, cultural, legal and environmental issues related to work projects.
2. The Principles identify the ethically responsible relationships in which individuals, groups, and organizations participate and the primary obligations within these relationships.
3. Principle 5: MANAGEMENTSoftware engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance .
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. The Code provides an ethical foundation to which individuals within teams and the team as a whole can appeal.
6. Not punish anyone for expressing ethical concerns about a project.
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. 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.
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. In particular, software engineers shall, as appropriate:Help develop an organizational environment favorable to acting ethically.