Software Engineering Code of Ethics and Professional Practice

Roll Numbers:
SE Code of Ethics and Professional ACM Code of Conduct Clauses Your Comments on Mismatches
Practice
PREAMBLE
Computers have a central and growing role
in commerce, industry, government,
medicine, education, entertainment and
society at large. 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. 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. 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. In accordance
with that commitment, software engineers
shall adhere to the following Code of Ethics
and Professional Practice.

The Code contains eight Principles related

to the behavior of and decisions made by
professional software engineers, including
practitioners, educators, managers,
supervisors and policy makers, as well as
trainees and students of the profession.
The Principles identify the ethically
responsible relationships in which
Page 1 of 15
individuals, groups, and organizations
participate and the primary obligations
within these relationships. The Clauses of
each Principle are illustrations of some of
the obligations included in these
relationships. These obligations are
founded in the software engineer’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. The Code prescribes
these as obligations of anyone claiming to
be or aspiring to be a software engineer.

It is not intended that the individual parts of

the Code be used in isolation to justify
errors of omission or commission. The list
of Principles and Clauses is not exhaustive.
The Clauses should not be read as
separating the acceptable from the
unacceptable in professional conduct in all
practical situations. The Code is not a
simple ethical algorithm that generates
ethical decisions. In some situations
standards may be in tension with each
other or with standards from other sources.
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.

Ethical tensions can best be addressed by

thoughtful consideration of fundamental
principles, rather than blind reliance on
detailed regulations. These Principles
should influence software engineers to
consider broadly who is affected by their
Page 2 of 15
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. 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.

The dynamic and demanding context of

software engineering requires a code that is
adaptable and relevant to new situations as
they occur. 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. The Code provides an ethical
foundation to which individuals within teams
and the team as a whole can appeal. The
Code helps to define those actions that are
ethically improper to request of a software
engineer or teams of software engineers.

The Code is not simply for adjudicating the

nature of questionable acts; it also has an
important educational function. 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.
Page 3 of 15
PRINCIPLES
Principle 1: PUBLIC
Software engineers shall act consistently with the public
interest. In particular, software engineers shall, as appropriate:

1.01. Accept full responsibility for their own work. 1.1 Contribute to society and to human 1.1 and 1.3 are Partially Mapping
…………………………………………………………………………. well-being, acknowledging that all 2.4 is Fully Mapping
people are stakeholders in computing.
1.3 Be honest and trustworthy.
2.4 Accept and provide appropriate
professional review:

1.02. Moderate the interests of the software engineer, the 1.1 Contribute to society and to human 1.1 and 3.1 are Fully Mapping
employer, the client and the users with the public good. well-being. 1.4 is Partially Mapping
3.1 Ensure that the public good is the
central concern during all professional
computing work.
1.4 Be fair and take action not to
discriminate.

1.03. Approve software only if they have a well-founded belief 1.1 Contribute to society and to human 1.1,1.2 and 3.1 are fully Mapping.
that it is safe, meets specifications, passes appropriate tests, well-being. 3.1 and 1.5 are Partially Mapping
and does not diminish quality of life, diminish privacy or harm 1.2 Avoid harm.
the environment. The ultimate effect of the work should be to 1.4 Be fair and take action not to
the public good. discriminate.
3.1 Ensure that the public good is the
central concern during all professional
computing work.
1.5 Respect the work required to
produce new ideas, inventions, creative
works, and computing artifacts.

1.04. Disclose to appropriate persons or authorities any actual 1.2 Avoid harm. 1.2, 1.3 and 2.4 are Fully Mapping
or potential danger to the user, the public, or the environment, 1.3 Be honest and trustworthy. 2.8 is Partially Mapping
that they reasonably believe to be associated with software or 2.4 Accept and provide appropriate
related documents. professional review.
2.8 Access computing and
Page 4 of 15
 communication resources only when
authorized or when compelled by the
public good.

1.05. Cooperate in efforts to address matters of grave public 1.1 Contribute to society and to human 1.1, 3.1, and 1.2 are Fully
concern caused by software, its installation, maintenance, well-being. Mapping
support or documentation. 1.2 Avoid harm. 1.3 is Partially Mapping
1.3 Be honest and trustworthy.
3.1 Ensure that the public good is the
central concern during all professional
computing work

1.06. Be fair and avoid deception in all statements, particularly 1.3 Be honest and trustworthy. 1.3 and 1.4 are Fully Mapping
public ones, concerning software or related documents, 1.4 Be fair and take action not to 2.1 and 3.3 are Partially Mapping
methods and tools. discriminate.
2.1 Strive to achieve high quality in
both the processes and products of
professional work.
3.3 Manage personnel and resources
to enhance the quality of working life.

1.07. Consider issues of physical disabilities, allocation of 1.1 Contribute to society and to human 1.1 and 3.3 are Fully Mapping
resources, economic disadvantage and other factors that can well-being. 1.4, 2.7 and 3.7 are Partially
diminish access to the benefits of software. 1.4 Be fair and take action not to Mapping
discriminate.
2.7 Foster public awareness and
understanding of computing, related
technologies, and their consequences.
3.7 Recognize and take special care of
systems that become integrated into
the infrastructure of society.
3.3 Manage personnel and resources
to enhance the quality of working life.

1.08. Be encouraged to volunteer professional skills to good 1.1 Contribute to society and to human 1.1 and 2.7 are Fully Mapping
causes and contribute to public education concerning the well-being. 3.5 and 2.7 are Partially Mapping
discipline. 1.7 Honor confidentiality.
3.5 Create opportunities for members
of the organization or group to grow as
professionals.
Page 5 of 15
 2.7 Foster public awareness and
understanding of computing, related
technologies, and their consequences.

Principle 2: CLIENT AND EMPLOYER

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.01. Provide service in their areas of competence, being 1.3 Be honest and trustworthy. 1.3, 2.6 are Fully Mapping
honest and forthright about any limitations of their experience 2.6 Perform work only in areas of 2.8 is Partially Mapping
and education. competence.
2.8 Access computing and
communication resources only when
authorized or when compelled by the
public good.

2.02. Not knowingly use software that is obtained or retained 1.2 Avoid harm. 1.2 is Fully Mapping
either illegally or unethically. 2.3 Know and respect existing rules 2.3 is Partially Mapping
pertaining to professional work.

2.03. Use the property of a client or employer only in ways 1.3 Be honest and trustworthy. 1.3 is Fully Mapping
properly authorized, and with the client's or employer's 2.8 Access computing and 2.8 is Partially Mapping
knowledge and consent. communication resources only when
authorized or when compelled by the
public good.

2.04. Ensure that any document upon which they rely has been 1.3 Be honest and trustworthy. 1.3 and 2.4 are Fully Mapping
approved, when required, by someone authorized to approve it. 2.4 Accept and provide appropriate
professional review.

2.05. Keep private any confidential information gained in their 1.7 Honor confidentiality. 1.7 is Fully Mapping
professional work, where such confidentiality is consistent with 2.3 Know and respect existing rules 2.3 is Partially Mapping
the public interest and consistent with the law. pertaining to professional work.

2.06. Identify, document, collect evidence and report to the 2.4 Accept and provide appropriate 2.4 and 2.5 are Fully Mapping
client or the employer promptly if, in their opinion, a project is professional review. 3.2 is Partially Mapping
likely to fail, to prove too expensive, to violate intellectual 2.5 Give comprehensive and thorough

Page 6 of 15
property law, or otherwise to be problematic. evaluations of computer systems and
their impacts.
3.2 Articulate, encourage acceptance
of, and evaluate fulfillment of social
responsibilities by members of the
organization or group.

2.07. Identify, document, and report significant issues of social 1.1 Contribute to society and to human 1.1 and 3.1 are Fully Mapping
concern, of which they are aware, in software or related well-being. 3.2 is Partially Mapping
documents, to the employer or the client. 3.1 Ensure that the public good is the
central concern during all professional
computing work.
3.2 Articulate, encourage acceptance
of, and evaluate fulfillment of social
responsibilities by members of the
organization or group.

2.08. Accept no outside work detrimental to the work they 1.4 Be fair and take action not to 2.6 is Fully Mapping
perform for their primary employer. discriminate. 1.4 is Partially Mapping
2.6 Perform work only in areas of
competence.

2.09. Promote no interest adverse to their employer or client, 1.4 Be fair and take action not to 1.7 and 2.6 are Fully Mapping
unless a higher ethical concern is being compromised; in that discriminate. 1.7 is Partially Mapping
case, inform the employer or another appropriate authority of 1.7 Honor confidentiality.
the ethical concern. 2.6 Perform work only in areas of
competence.

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 2.1 Strive to achieve high quality in 2.1 and 2.4 are Fully Mapping
schedule, ensuring significant tradeoffs are clear to and both the processes and products of 2.5 is Partially Mapping
accepted by the employer and the client, and are available for professional work.
consideration by the user and the public. 2.4 Accept and provide appropriate
professional review.
2.5 Give comprehensive and thorough

Page 7 of 15
 evaluations of computer systems and
their impacts.

3.02. Ensure proper and achievable goals and objectives for 2.1 Strive to achieve high quality in 2.1 and 2.6 are Fully Mapping
any project on which they work or propose. both the processes and products of
professional work.
2.6 Perform work only in areas of
competence.

3.03. Identify, define and address ethical, economic, cultural, 1.1 Contribute to society and to human 1.1 and 3.1 are Fully Mapping
legal and environmental issues related to work projects. well-being. 1.4 and 4.2 are Partially Mapping
1.4 Be fair and take action not to
discriminate.
3.1 Ensure that the public good is the
central concern during all professional
computing work.
3.2 Articulate, encourage acceptance
of, and evaluate fulfillment of social
responsibilities by members of the
organization or group.

3.04. Ensure that they are qualified for any project on which 2.2 Maintain high standards of 2.2 and 2.6 are Fully Mapping
they work or propose to work by an appropriate combination of professional competence, conduct, and
education and training, and experience. ethical practice.
2.6 Perform work only in areas of
competence.

3.05. Ensure an appropriate method is used for any project on 2.1 Strive to achieve high quality in 2.1 is Fully Mapping
which they work or propose to work. both the processes and products of 2.4 is Partially Mapping
professional work.
2.4 Accept and provide appropriate
professional review.

3.06. Work to follow professional standards, when available, 2.1 Strive to achieve high quality in 2.1 and 2.3 are Fully Mapping
that are most appropriate for the task at hand, departing from both the processes and products of
these only when ethically or technically justified. professional work.
2.3 Know and respect existing rules
pertaining to professional work.

Page 8 of 15
3.07. Strive to fully understand the specifications for software 2.1 Strive to achieve high quality in 2.1 and 2.2 are Fully Mapping
on which they work. both the processes and products of
professional work.
2.2 Maintain high standards of
professional competence, conduct, and
ethical practice.

3.08. Ensure that specifications for software on which they work 2.4 Accept and provide appropriate 2.5 is Fully Mapping
have been well documented, satisfy the users’ requirements professional review. 2.4 is Partially Mapping
and have the appropriate approvals. 2.5 Give comprehensive and thorough
evaluations of computer systems and
their impacts, including analysis of
possible risks.

3.09. Ensure realistic quantitative estimates of cost, scheduling, 2.1 Strive to achieve high quality in 2.1 and 3.1 are Fully Mapping
personnel, quality and outcomes on any project on which they both the processes and products of
work or propose to work and provide an uncertainty professional work.
assessment of these estimates. 3.1 Strive for high quality, acceptable
cost, and a reasonable schedule.

3.10. Ensure adequate testing, debugging, and review of 2.1 Strive to achieve high quality in 2.1 is Fully Mapping
software and related documents on which they work. both the processes and products of 2.5 is Partially Mapping
professional work.
2.5 Give comprehensive and thorough
evaluations of computer systems and
their impacts, including analysis of
possible risks.

3.11. Ensure adequate documentation, including significant 2.1 Strive to achieve high quality in 2.1 and 2.4 are Fully Mapping
problems discovered and solutions adopted, for any project on both the processes and products of
which they work. professional work.
2.4 Accept and provide appropriate
professional review.

3.12. Work to develop software and related documents that 1.6 Respect privacy. 1.6 and 1.7 are Fully Mapping
respect the privacy of those who will be affected by that 1.7 Honor confidentiality. 2.5 is Partially Mapping
software. 2.5 Give comprehensive and thorough
evaluations of computer systems and
their impacts, including analysis of

Page 9 of 15
 possible risks.

3.13. Be careful to use only accurate data derived by ethical 1.3 Be honest and trustworthy. 1.3 and 1.4 are Fully Mapping
and lawful means, and use it only in ways properly authorized. 1.4 Be fair and take action not to 1.6 and 1.7 are Partially Mapping
discriminate.
1.6 Respect privacy.
1.7 Honor confidentiality.

3.14. Maintain the integrity of data, being sensitive to outdated 1.1 Contribute to society and to human 1.1, 1.7 and 1.3 are Fully Mapping
or flawed occurrences. well-being. 1.5 is Partially Mapping
1.3 Be honest and trustworthy.
1.5 Respect the work required to
produce new ideas, inventions, creative
works, and computing artifacts.
1.7 Honor confidentiality.

3.15 Treat all forms of software maintenance with the same 2.1 Strive to achieve high quality in 2.1 and 2.2 are Fully Mapping
professionalism as new development. both the processes and products of 2.5 is Partially Mapping
professional work.
2.2 Maintain high standards of
professional competence, conduct, and
ethical practice.
2.5 Give comprehensive and thorough
evaluations of computer systems and
their impacts, including analysis of
possible risks.

Principle 4: JUDGMENT
Software engineers shall maintain integrity and independence
in their professional judgment. In particular, software engineers
shall, as appropriate:

4.01. Temper all technical judgments by the need to support

and maintain human values.

4.02 Only endorse documents either prepared under their

supervision or within their areas of competence and with which
they are in agreement.

Page 10 of 15
4.03. Maintain professional objectivity with respect to any
software or related documents they are asked to evaluate.

4.04. Not engage in deceptive financial practices such as

bribery, double billing, or other improper financial practices.

4.05. Disclose to all concerned parties those conflicts of interest

that cannot reasonably be avoided or escaped.

4.06. Refuse to participate, as members or advisors, in a

private, governmental or professional body concerned with
software related issues, in which they, their employers or their
clients have undisclosed potential conflicts of interest.

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.05. Ensure realistic quantitative estimates of cost, scheduling,

personnel, quality and outcomes on any project on which they
Page 11 of 15
work or propose to work, and provide an uncertainty
assessment of these estimates.

5.06. Attract potential software engineers only by full and

accurate description of the conditions of employment.

5.07. Offer fair and just remuneration.

5.08. Not unjustly prevent someone from taking a position for

which that person is suitably qualified.

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

5.10. Provide for due process in hearing charges of violation of

an employer's policy or of this Code.

5.11. Not ask a software engineer to do anything inconsistent

with this Code.

5.12. Not punish anyone for expressing ethical concerns about

a project.

Principle 6: PROFESSION
Software engineers shall advance the integrity and reputation of
the profession consistent with the public interest. In particular,
software engineers shall, as appropriate:

6.01. Help develop an organizational environment favorable to

acting ethically.

6.02. Promote public knowledge of software engineering.

6.03. Extend software engineering knowledge by appropriate

participation in professional organizations, meetings and
publications.
Page 12 of 15
6.04. Support, as members of a profession, other software
engineers striving to follow this Code.

6.05. Not promote their own interest at the expense of the

profession, client or employer.

6.06. Obey all laws governing their work, unless, in exceptional

circumstances, such compliance is inconsistent with the public
interest.

6.07. 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.08. Take responsibility for detecting, correcting, and reporting

errors in software and associated documents on which they
work.

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.

6.12. Express concerns to the people involved when significant

violations of this Code are detected unless this is impossible,
counter-productive, or dangerous.

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

Page 13 of 15
Principle 7: COLLEAGUES
Software engineers shall be fair to and supportive of their
colleagues. In particular, software engineers shall, as
appropriate:

7.01. Encourage colleagues to adhere to this Code.

7.02. Assist colleagues in professional development.

7.03. Credit fully the work of others and refrain from taking
undue credit.

7.04. Review the work of others in an objective, candid, and

properly-documented way.

7.05. Give a fair hearing to the opinions, concerns, or

complaints of a colleague.

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

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
Software engineers shall participate in lifelong learning
regarding the practice of their profession and shall promote an
ethical approach to the practice of the profession. In particular,
software engineers shall continually endeavor to:

Page 14 of 15
8.01. 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.

8.02. Improve their ability to create safe, reliable, and useful

quality software at reasonable cost and within a reasonable
time.

8.03. Improve their ability to produce accurate, informative, and

well-written documentation.

8.04. Improve their understanding of the software and related

documents on which they work and of the environment in which
they will be used.

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.07 Not give unfair treatment to anyone because of any

irrelevant prejudices.

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.

This Code was developed by the ACM/IEEE-CS joint task force on

Software Engineering Ethics and Professional Practices (SEEPP):

Page 15 of 15