Ethical Standards and Codes of Conduct
Ethical Standards and Codes of Conduct
• Mechanism for educating for those entering the profession, companies and
clients.
The code also ensures collective responsibility, so that various parties do not
only think of individuals in the profession but rather a collective unit of the
profession. If a profession speaks out on an issue, it is more effective as a
group. Examples of this are issues such as protection of whistle blowers and
gender bias. what is right and what is wrong.
1.5 Respect the work required to produce new ideas, inventions, creative
works, and computing artifacts.
2. PROFESSIONAL RESPONSIBILITIES.
2.1 Strive to achieve high quality in both the processes and products of
professional work.
2.2 Maintain high standards of professional competence, conduct, and
ethical practice.
2.9 Design and implement systems that are robustly and usably secure.
3.1 Ensure that the public good is the central concern during all
professional computing work.
3.4 Articulate, apply, and support policies and processes that reflect the
principles of the Code.
PRINCIPLES
Principle 1: PUBLIC
1.03. 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. The ultimate effect of the
work should be to the public good.
1.06. Be fair and avoid deception in all statements, particularly public ones,
concerning software or related documents, methods and tools.
Software engineers shall act in a manner that is in the best interests of their
client and employer, consistent with the public interest. In particular,
software engineers shall, as appropriate:
2.02. Not knowingly use software that is obtained or retained either illegally
or unethically.
2.03. Use the property of a client or employer only in ways properly
authorized, and with the client’s or employer’s knowledge and consent.
2.04. Ensure that any document upon which they rely has been approved,
when required, by someone authorized to approve it.
2.06. Identify, document, collect evidence and report to the client or the
employer promptly if, in their opinion, a project is likely to fail, to prove too
expensive, to violate intellectual property law, or otherwise to be
problematic.
2.08. Accept no outside work detrimental to the work they perform for their
primary employer.
Principle 3: PRODUCT
Software engineers shall ensure that their products and related modifications
meet the highest professional standards possible. In particular, software
engineers shall, as appropriate:
3.01. 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.
3.02. Ensure proper and achievable goals and objectives for any project on
which they work or propose.
3.03. Identify, define and address ethical, economic, cultural, legal and
environmental issues related to work projects.
3.04. Ensure that they are qualified for any project on which they work or
propose to work by an appropriate combination of education and training,
and experience.
3.05. Ensure an appropriate method is used for any project on which they
work or propose to work.
3.06. 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.
3.07. Strive to fully understand the specifications for software on which they
work.
3.08. Ensure that specifications for software on which they work have been
well documented, satisfy the users’ requirements and have the appropriate
approvals.
3.12. Work to develop software and related documents that respect the
privacy of those who will be affected by that software.
3.13. Be careful to use only accurate data derived by ethical and lawful
means, and use it only in ways properly authorized.
3.15 Treat all forms of software maintenance with the same professionalism
as new development.
Principle 4: JUDGMENT
4.01. Temper all technical judgments by the need to support and maintain
human values.
4.05. Disclose to all concerned parties those conflicts of interest that cannot
reasonably be avoided or escaped.
Principle 5: MANAGEMENT
Software engineering managers and leaders shall subscribe to and promote
an ethical approach to the management of software development and
maintenance. In particular, those managing or leading software engineers
shall, as appropriate:
5.01 Ensure good management for any project on which they work, including
effective procedures for promotion of quality and reduction of risk.
5.02. Ensure that software engineers are informed of standards before being
held to them.
5.03. 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.
5.04. Assign work only after taking into account appropriate contributions of
education and experience tempered with a desire to further that education
and experience.
5.08. Not unjustly prevent someone from taking a position for which that
person is suitably qualified.
5.12. Not punish anyone for expressing ethical concerns about a project.
Principle 6: PROFESSION
6.05. Not promote their own interest at the expense of the profession, client
or employer.
6.09. 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.
6.10. Avoid associations with businesses and organizations which are in
conflict with this code.
6.11. Recognize that violations of this Code are inconsistent with being a
professional software engineer.
Principle 7: COLLEAGUES
7.03. Credit fully the work of others and refrain from taking undue credit.
7.07. 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.
7.08. In situations outside of their own areas of competence, call upon the
opinions of other professionals who have competence in that area.
Principle 8: SELF
8.02. Improve their ability to create safe, reliable, and useful quality software
at reasonable cost and within a reasonable time.
8.05. Improve their knowledge of relevant standards and the law governing
the software and related documents on which they work.
8.06 Improve their knowledge of this Code, its interpretation, and its
application to their work.
8.08. Not influence others to undertake any action that involves a breach of
this Code.
8.09. Recognize that personal violations of this Code are inconsistent with
being a professional software engineer.
C) IEEE Code of Ethics
E) Data Ethics
F) Cybersecurity Ethics
2. Key Principles and Values: Identify the key principles and values
articulated in the code of conduct. These may include honesty,
integrity, respect for others, confidentiality, fairness, accountability,
and professionalism. Pay attention to how these principles are defined
and elaborated upon within the document.
Group Activity
Discuss the possible implications for a business that does not have a
computer code of conduct in place
Code of ethics and practices must be dynamic, current and relevant if
they are to be practical worth. They must promote professionalism and
be effective challenge to malpractice. Develop a code of conduct for a
hypothetical computer project.