Programming ethics - Revision history

2A04:EE41:0:40B5:9496:330B:4DBE:4859: added reference to exemplify wrong practices

2025-01-08T09:38:25Z

added reference to exemplify wrong practices

← Previous revision		Revision as of 09:38, 8 January 2025
Line 1:		Line 1:
	{{More citations needed\|date=June 2021}}		{{More citations needed\|date=June 2021}}
	This article gives an overview of professional ethics as applied to [[computer programming]] and [[software development]], in particular the ethical guidelines that developers are expected to follow and apply when writing programming code (also called [[source code]]), and when they are part of a programmer-customer or employee-employer relationship. These rules shape and differentiate good practices and attitudes from the wrong ones when creating [[software]] or when making decisions on a crucial or delicate issue regarding a programming project. They are also the basis for ethical decision-making skills in the conduct of professional work.		This article gives an overview of professional ethics as applied to [[computer programming]] and [[software development]], in particular the ethical guidelines that developers are expected to follow and apply when writing programming code (also called [[source code]]), and when they are part of a programmer-customer or employee-employer relationship. These rules shape and differentiate good practices and attitudes from the wrong ones<ref name="darkpatterns">{{cite book\|author=<!-- not stated -->\|title=Unethical Software Engineering: Dark Patterns\|publisher=LeanPub\|date=2024-12-25\|url=https://leanpub.com/unethical-software-engineering}}</ref> when creating [[software]] or when making decisions on a crucial or delicate issue regarding a programming project. They are also the basis for ethical decision-making skills in the conduct of professional work.

	== History ==		== History ==

195.194.74.162 at 09:23, 21 March 2024

2024-03-21T09:23:10Z

← Previous revision		Revision as of 09:23, 21 March 2024
Line 2:		Line 2:
	This article gives an overview of professional ethics as applied to [[computer programming]] and [[software development]], in particular the ethical guidelines that developers are expected to follow and apply when writing programming code (also called [[source code]]), and when they are part of a programmer-customer or employee-employer relationship. These rules shape and differentiate good practices and attitudes from the wrong ones when creating [[software]] or when making decisions on a crucial or delicate issue regarding a programming project. They are also the basis for ethical decision-making skills in the conduct of professional work.		This article gives an overview of professional ethics as applied to [[computer programming]] and [[software development]], in particular the ethical guidelines that developers are expected to follow and apply when writing programming code (also called [[source code]]), and when they are part of a programmer-customer or employee-employer relationship. These rules shape and differentiate good practices and attitudes from the wrong ones when creating [[software]] or when making decisions on a crucial or delicate issue regarding a programming project. They are also the basis for ethical decision-making skills in the conduct of professional work.

	== History ==@		== History ==

	The American scholar [[Norbert Wiener]], professor of Mathematics and Engineering at [[Massachusetts Institute of Technology]], was the first person to set the basis for a new type of		The American scholar [[Norbert Wiener]], professor of Mathematics and Engineering at [[Massachusetts Institute of Technology]], was the first person to set the basis for a new type of

195.194.74.162 at 09:22, 21 March 2024

2024-03-21T09:22:57Z

← Previous revision		Revision as of 09:22, 21 March 2024
Line 2:		Line 2:
	This article gives an overview of professional ethics as applied to [[computer programming]] and [[software development]], in particular the ethical guidelines that developers are expected to follow and apply when writing programming code (also called [[source code]]), and when they are part of a programmer-customer or employee-employer relationship. These rules shape and differentiate good practices and attitudes from the wrong ones when creating [[software]] or when making decisions on a crucial or delicate issue regarding a programming project. They are also the basis for ethical decision-making skills in the conduct of professional work.		This article gives an overview of professional ethics as applied to [[computer programming]] and [[software development]], in particular the ethical guidelines that developers are expected to follow and apply when writing programming code (also called [[source code]]), and when they are part of a programmer-customer or employee-employer relationship. These rules shape and differentiate good practices and attitudes from the wrong ones when creating [[software]] or when making decisions on a crucial or delicate issue regarding a programming project. They are also the basis for ethical decision-making skills in the conduct of professional work.

	== History ==		== History ==@

	The American scholar [[Norbert Wiener]], professor of Mathematics and Engineering at [[Massachusetts Institute of Technology]], was the first person to set the basis for a new type of		The American scholar [[Norbert Wiener]], professor of Mathematics and Engineering at [[Massachusetts Institute of Technology]], was the first person to set the basis for a new type of

Dirkbb: Reverted 1 edit by 103.186.255.146 (talk) to last revision by OAbot

2024-03-16T00:33:30Z

Reverted 1 edit by 103.186.255.146 (talk) to last revision by OAbot

← Previous revision		Revision as of 00:33, 16 March 2024
Line 13:		Line 13:
	In the early 1990s, [[Donald Gotterbarn]] claimed that computer ethics should be considered as professional ethics that could have the power to lead towards the development and advancement of standards of good practice and codes of conduct for computing professionals (Bynum).<ref name="Bynum" /> He worked with several professional-ethics advocates to write ethical guidelines for creating codes of Ethics. He formed part of the creation of Code of Ethics and Professional Conduct, adopted by the [[Association for Computing Machinery]] (ACM) in 1992, and Software Engineering Code of Ethics and Professional Practice, adopted by the [[IEEE\|Institute of Electrical and Electronics Engineers]] (IEEE) and the ACM as well. These codes also include Programming Ethics principles.		In the early 1990s, [[Donald Gotterbarn]] claimed that computer ethics should be considered as professional ethics that could have the power to lead towards the development and advancement of standards of good practice and codes of conduct for computing professionals (Bynum).<ref name="Bynum" /> He worked with several professional-ethics advocates to write ethical guidelines for creating codes of Ethics. He formed part of the creation of Code of Ethics and Professional Conduct, adopted by the [[Association for Computing Machinery]] (ACM) in 1992, and Software Engineering Code of Ethics and Professional Practice, adopted by the [[IEEE\|Institute of Electrical and Electronics Engineers]] (IEEE) and the ACM as well. These codes also include Programming Ethics principles.

	== ~~Proffesional~~ Programming Ethical Guidelines ==		== Programming Ethical Guidelines ==

	The [[Association for Computing Machinery\|Association for Computing Machinery (ACM)]] is the world's largest educational and scientific computing society. It has its own Code of Ethics and another set of ethical principles that were also approved by the [[IEEE]] as the standard for teaching and practicing [[software engineering]]. These codes are Code of Ethics and		The [[Association for Computing Machinery\|Association for Computing Machinery (ACM)]] is the world's largest educational and scientific computing society. It has its own Code of Ethics and another set of ethical principles that were also approved by the [[IEEE]] as the standard for teaching and practicing [[software engineering]]. These codes are Code of Ethics and

103.186.255.146: /* Programming Ethical Guidelines */

2024-03-14T16:28:32Z

Programming Ethical Guidelines

← Previous revision		Revision as of 16:28, 14 March 2024
Line 13:		Line 13:
	In the early 1990s, [[Donald Gotterbarn]] claimed that computer ethics should be considered as professional ethics that could have the power to lead towards the development and advancement of standards of good practice and codes of conduct for computing professionals (Bynum).<ref name="Bynum" /> He worked with several professional-ethics advocates to write ethical guidelines for creating codes of Ethics. He formed part of the creation of Code of Ethics and Professional Conduct, adopted by the [[Association for Computing Machinery]] (ACM) in 1992, and Software Engineering Code of Ethics and Professional Practice, adopted by the [[IEEE\|Institute of Electrical and Electronics Engineers]] (IEEE) and the ACM as well. These codes also include Programming Ethics principles.		In the early 1990s, [[Donald Gotterbarn]] claimed that computer ethics should be considered as professional ethics that could have the power to lead towards the development and advancement of standards of good practice and codes of conduct for computing professionals (Bynum).<ref name="Bynum" /> He worked with several professional-ethics advocates to write ethical guidelines for creating codes of Ethics. He formed part of the creation of Code of Ethics and Professional Conduct, adopted by the [[Association for Computing Machinery]] (ACM) in 1992, and Software Engineering Code of Ethics and Professional Practice, adopted by the [[IEEE\|Institute of Electrical and Electronics Engineers]] (IEEE) and the ACM as well. These codes also include Programming Ethics principles.

	== Programming Ethical Guidelines ==		== Proffesional Programming Ethical Guidelines ==

	The [[Association for Computing Machinery\|Association for Computing Machinery (ACM)]] is the world's largest educational and scientific computing society. It has its own Code of Ethics and another set of ethical principles that were also approved by the [[IEEE]] as the standard for teaching and practicing [[software engineering]]. These codes are Code of Ethics and		The [[Association for Computing Machinery\|Association for Computing Machinery (ACM)]] is the world's largest educational and scientific computing society. It has its own Code of Ethics and another set of ethical principles that were also approved by the [[IEEE]] as the standard for teaching and practicing [[software engineering]]. These codes are Code of Ethics and

OAbot: Open access bot: doi updated in citation with #oabot.

2023-11-07T11:48:27Z

Open access bot: doi updated in citation with #oabot.

← Previous revision		Revision as of 11:48, 7 November 2023
Line 27:		Line 27:
	* '''Honor confidentiality.''' Unless required by law or any other ethical guideline, a programmer must keep secret any additional information related to their employer that arises from working in a project.		* '''Honor confidentiality.''' Unless required by law or any other ethical guideline, a programmer must keep secret any additional information related to their employer that arises from working in a project.

	From Software Engineering Code of Ethics and Professional Practice<ref name="ieee">{{cite journal\|author=[[Donald Gotterbarn]], Keith Miller, and [[Simon Rogerson]]\|title=Software Engineering Code of Ethics and Professional Practice\|publisher=[[Association for Computing Machinery]], [[IEEE]]\|date=2013-09-28\|url=https://ethics.acm.org/code-of-ethics/software-engineering-code\|doi=10.1145/265684.265699\|s2cid=9789551 }}</ref> (IEEE, ACM):		From Software Engineering Code of Ethics and Professional Practice<ref name="ieee">{{cite journal\|author=[[Donald Gotterbarn]], Keith Miller, and [[Simon Rogerson]]\|title=Software Engineering Code of Ethics and Professional Practice\|publisher=[[Association for Computing Machinery]], [[IEEE]]\|date=2013-09-28\|url=https://ethics.acm.org/code-of-ethics/software-engineering-code\|doi=10.1145/265684.265699\|s2cid=9789551 \|doi-access=free}}</ref> (IEEE, ACM):

	* '''Approve software only if they have a well-founded belief it is safe and meets specifications.''' Programmers cannot assume that a system is ready to use only because it performs the tasks needed. They should make sure these systems are also safe and meet every specification required by the user. If programs are not safe, users are unprotected from hackers that could steal important information or money. Therefore, several tests should be performed in order to ensure a [[Computer security\|system's security]] before approving it.		* '''Approve software only if they have a well-founded belief it is safe and meets specifications.''' Programmers cannot assume that a system is ready to use only because it performs the tasks needed. They should make sure these systems are also safe and meet every specification required by the user. If programs are not safe, users are unprotected from hackers that could steal important information or money. Therefore, several tests should be performed in order to ensure a [[Computer security\|system's security]] before approving it.

81.2.103.240: /* Programming Ethical Guidelines */ grammar

2023-06-04T15:39:49Z

Programming Ethical Guidelines: grammar

Citation bot: Alter: template type. Add: s2cid, encyclopedia. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Abductive | #UCB_webform 2616/3850

2023-03-05T10:06:11Z

Alter: template type. Add: s2cid, encyclopedia. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Abductive | #UCB_webform 2616/3850

← Previous revision		Revision as of 10:06, 5 March 2023
Line 7:		Line 7:
	Ethics in the mid 1940s. He noticed that the innovations and advances in science and [[technology]], along with the fast-growing computer industry, were leading to the appearance of this type of Ethics that he named “cybernetics” (from the Greek word for the pilot of a ship). The emerging use of [[computer]]s and other technologies were bringing up new ethical issues that needed to be analyzed carefully using new ethical guidelines.		Ethics in the mid 1940s. He noticed that the innovations and advances in science and [[technology]], along with the fast-growing computer industry, were leading to the appearance of this type of Ethics that he named “cybernetics” (from the Greek word for the pilot of a ship). The emerging use of [[computer]]s and other technologies were bringing up new ethical issues that needed to be analyzed carefully using new ethical guidelines.

	Wiener wrote three books that lay down a foundation to a new division of [[Ethics]] after World War II ended. The books were Cybernetics (1948), The Human Use of Human Beings (1950) and God and Golem, Inc. (1963). Even though he never saw himself creating a new area of Ethics, Wiener gave detailed examples where some ethical and social issues and implications, which were generated by the use of [[computer]]s, could be identified. However, his ideas were not taken seriously by other scholars because they considered him an eccentric scientist that fantasized about Ethics (Bynum).<ref name="Bynum">{{cite ~~web~~\|author=Bynum, Terrel\|title=Computer and Information Ethics\|~~work~~=The Stanford Encyclopedia of Philosophy (Spring 2011 Edition)\|editor=[[Edward N. Zalta]]\|date=2015-10-26\|orig-date=2001-08-14\|access-date=2021-06-21\|url=https://plato.stanford.edu/archives/sum2020/entries/ethics-computer/}}</ref>		Wiener wrote three books that lay down a foundation to a new division of [[Ethics]] after World War II ended. The books were Cybernetics (1948), The Human Use of Human Beings (1950) and God and Golem, Inc. (1963). Even though he never saw himself creating a new area of Ethics, Wiener gave detailed examples where some ethical and social issues and implications, which were generated by the use of [[computer]]s, could be identified. However, his ideas were not taken seriously by other scholars because they considered him an eccentric scientist that fantasized about Ethics (Bynum).<ref name="Bynum">{{cite encyclopedia\|author=Bynum, Terrel\|title=Computer and Information Ethics\|encyclopedia=The Stanford Encyclopedia of Philosophy (Spring 2011 Edition)\|editor=[[Edward N. Zalta]]\|date=2015-10-26\|orig-date=2001-08-14\|access-date=2021-06-21\|url=https://plato.stanford.edu/archives/sum2020/entries/ethics-computer/}}</ref>

	In 1976, a new term regarding Ethics, named “computer ethics,” was proposed by Walter Maner based on the ideas and principles of [[Norbert Wiener]]. Maner felt it was necessary to have a field of Ethics for the computer industry just as the medical and business industries had at that moment. Maner also defined that field as one that “studies ethical problems aggravated, transformed or created by computer technology” (Bynum),<ref name="Bynum" /> and he even designed a computer ethics course that could be imparted to university students.		In 1976, a new term regarding Ethics, named “computer ethics,” was proposed by Walter Maner based on the ideas and principles of [[Norbert Wiener]]. Maner felt it was necessary to have a field of Ethics for the computer industry just as the medical and business industries had at that moment. Maner also defined that field as one that “studies ethical problems aggravated, transformed or created by computer technology” (Bynum),<ref name="Bynum" /> and he even designed a computer ethics course that could be imparted to university students.
Line 27:		Line 27:
	* '''Honor confidentiality.''' Unless required by law or any other ethical guideline, a programmer must keep secret any additional information related to his or her employer that arises from working in a project.		* '''Honor confidentiality.''' Unless required by law or any other ethical guideline, a programmer must keep secret any additional information related to his or her employer that arises from working in a project.

	From Software Engineering Code of Ethics and Professional Practice<ref name="ieee">{{cite ~~web~~\|author=[[Donald Gotterbarn]], Keith Miller, and [[Simon Rogerson]]\|title=Software Engineering Code of Ethics and Professional Practice\|publisher=[[Association for Computing Machinery]], [[IEEE]]\|date=2013-09-28\|url=https://ethics.acm.org/code-of-ethics/software-engineering-code\|doi=10.1145/265684.265699}}</ref> (IEEE, ACM):		From Software Engineering Code of Ethics and Professional Practice<ref name="ieee">{{cite journal\|author=[[Donald Gotterbarn]], Keith Miller, and [[Simon Rogerson]]\|title=Software Engineering Code of Ethics and Professional Practice\|publisher=[[Association for Computing Machinery]], [[IEEE]]\|date=2013-09-28\|url=https://ethics.acm.org/code-of-ethics/software-engineering-code\|doi=10.1145/265684.265699\|s2cid=9789551 }}</ref> (IEEE, ACM):

	* '''Approve software only if they have a well-founded belief it is safe and meets specifications.''' Programmers cannot assume that a system is ready to use only because it performs the tasks needed. They should make sure these systems are also safe and meet every specification required by the user. If programs are not safe, users are unprotected from hackers that could steal important information or money. Therefore, several tests should be performed in order to ensure a [[Computer security\|system's security]] before approving it.		* '''Approve software only if they have a well-founded belief it is safe and meets specifications.''' Programmers cannot assume that a system is ready to use only because it performs the tasks needed. They should make sure these systems are also safe and meet every specification required by the user. If programs are not safe, users are unprotected from hackers that could steal important information or money. Therefore, several tests should be performed in order to ensure a [[Computer security\|system's security]] before approving it.

Carchasm: removed Category:Ethics; added Category:Computer ethics using HotCat

2023-02-18T00:44:14Z

removed Category:Ethics; added Category:Computer ethics using HotCat

← Previous revision		Revision as of 00:44, 18 February 2023
Line 60:		Line 60:
	<!--- After listing your sources please cite them using inline citations and place them after the information they cite. Please see http://en.wikipedia.org/wiki/Wikipedia:REFB for instructions on how to add citations. --->		<!--- After listing your sources please cite them using inline citations and place them after the information they cite. Please see http://en.wikipedia.org/wiki/Wikipedia:REFB for instructions on how to add citations. --->

	[[Category:~~Ethics~~]]		[[Category:Computer ethics]]

ClueBot NG: Reverting possible vandalism by 64.19.104.231 to version by Wbm1058. Report False Positive? Thanks, ClueBot NG. (4193687) (Bot)

2022-11-22T04:32:09Z

Reverting possible vandalism by 64.19.104.231 to version by Wbm1058. Report False Positive? Thanks, ClueBot NG. (4193687) (Bot)

← Previous revision		Revision as of 04:32, 22 November 2022
Line 11:		Line 11:
	In 1976, a new term regarding Ethics, named “computer ethics,” was proposed by Walter Maner based on the ideas and principles of [[Norbert Wiener]]. Maner felt it was necessary to have a field of Ethics for the computer industry just as the medical and business industries had at that moment. Maner also defined that field as one that “studies ethical problems aggravated, transformed or created by computer technology” (Bynum),<ref name="Bynum" /> and he even designed a computer ethics course that could be imparted to university students.		In 1976, a new term regarding Ethics, named “computer ethics,” was proposed by Walter Maner based on the ideas and principles of [[Norbert Wiener]]. Maner felt it was necessary to have a field of Ethics for the computer industry just as the medical and business industries had at that moment. Maner also defined that field as one that “studies ethical problems aggravated, transformed or created by computer technology” (Bynum),<ref name="Bynum" /> and he even designed a computer ethics course that could be imparted to university students.

	In the early 1990s, [[Donald Gotterbarn]] claimed that computer ethics should be considered as professional ethics that could have the power to lead towards the development and advancement of standards of good practice and codes of conduct for computing professionals (Bynum).<ref name="Bynum" /> He worked with several professional-ethics advocates to write ethical guidelines for creating codes of Ethics. He formed part of the creation of Code of Ethics and Professional Conduct, adopted by the [[Association for Computing Machinery]] (ACM) in 1992, and Software Engineering Code of Ethics and Professional Practice, adopted by the [[IEEE\|Institute of Electrical and Electronics Engineers]] (IEEE) and the ACM as well. These codes also include Programming Ethics principles. ~~Don't use wikki~~		In the early 1990s, [[Donald Gotterbarn]] claimed that computer ethics should be considered as professional ethics that could have the power to lead towards the development and advancement of standards of good practice and codes of conduct for computing professionals (Bynum).<ref name="Bynum" /> He worked with several professional-ethics advocates to write ethical guidelines for creating codes of Ethics. He formed part of the creation of Code of Ethics and Professional Conduct, adopted by the [[Association for Computing Machinery]] (ACM) in 1992, and Software Engineering Code of Ethics and Professional Practice, adopted by the [[IEEE\|Institute of Electrical and Electronics Engineers]] (IEEE) and the ACM as well. These codes also include Programming Ethics principles.

	== Programming Ethical Guidelines ==		== Programming Ethical Guidelines ==

← Previous revision		Revision as of 15:39, 4 June 2023
Line 22:		Line 22:
	* '''Contribute to society and human well-being.''' Programmers should work to develop computer systems that can reduce negative consequences to society, such as threats to safety and health, and that can make everyday activities and work easier. It is “an obligation to develop to high standards” (Savage).<ref name="savage">{{cite web\|author=Savage, Brandon\|title=Ethics for Programmers?\|website=BrandonSavage.net\|date=2009-08-12\|access-date=2013-09-29\|url=https://www.brandonsavage.net/ethics-for-programmers}}</ref>		* '''Contribute to society and human well-being.''' Programmers should work to develop computer systems that can reduce negative consequences to society, such as threats to safety and health, and that can make everyday activities and work easier. It is “an obligation to develop to high standards” (Savage).<ref name="savage">{{cite web\|author=Savage, Brandon\|title=Ethics for Programmers?\|website=BrandonSavage.net\|date=2009-08-12\|access-date=2013-09-29\|url=https://www.brandonsavage.net/ethics-for-programmers}}</ref>
	* '''Avoid harm to others.''' Computer systems have an indirect impact on third parties. They can cause loss of information and resources that might result severely harmful for users, the general public, or employers. Therefore, software developers should minimize the risk of harming others due to [[Error code\|coding errors]], or security issues, by following standards to design and test systems (Code of Ethics and Professional Conduct).<ref name="ACM" />		* '''Avoid harm to others.''' Computer systems have an indirect impact on third parties. They can cause loss of information and resources that might result severely harmful for users, the general public, or employers. Therefore, software developers should minimize the risk of harming others due to [[Error code\|coding errors]], or security issues, by following standards to design and test systems (Code of Ethics and Professional Conduct).<ref name="ACM" />
	* '''Be honest and trustworthy.''' This principle encourages programmers to be honest and aware of their limitations in knowledge and education when writing computer systems. Also, if a programmer knows there is something wrong with a computer system, ~~he or she~~ should report it immediately to avoid undesirable consequences.		* '''Be honest and trustworthy.''' This principle encourages programmers to be honest and aware of their limitations in knowledge and education when writing computer systems. Also, if a programmer knows there is something wrong with a computer system, they should report it immediately to avoid undesirable consequences.
	* '''Give proper credit for intellectual property.''' It is mandatory for every software developer to never use and take credit for someone else's work, even when it has not been protected by a [[copyright]] law, [[patent]], etc. They must recognize and fully credit other people's works, and they should use their own ideas to develop software.		* '''Give proper credit for intellectual property.''' It is mandatory for every software developer to never use and take credit for someone else's work, even when it has not been protected by a [[copyright]] law, [[patent]], etc. They must recognize and fully credit other people's works, and they should use their own ideas to develop software.
	* '''Respect the privacy of others.''' Computer systems are wrongly used by some people to violate the privacy of others. Software developers should write programs that can protect users’ private information and that can avoid other undesired people to have unauthorized access to it (Code of Ethics and Professional Conduct).		* '''Respect the privacy of others.''' Computer systems are wrongly used by some people to violate the privacy of others. Software developers should write programs that can protect users’ private information and that can avoid other undesired people to have unauthorized access to it (Code of Ethics and Professional Conduct).
	* '''Honor confidentiality.''' Unless required by law or any other ethical guideline, a programmer must keep secret any additional information related to ~~his or her~~ employer that arises from working in a project.		* '''Honor confidentiality.''' Unless required by law or any other ethical guideline, a programmer must keep secret any additional information related to their employer that arises from working in a project.

	From Software Engineering Code of Ethics and Professional Practice<ref name="ieee">{{cite journal\|author=[[Donald Gotterbarn]], Keith Miller, and [[Simon Rogerson]]\|title=Software Engineering Code of Ethics and Professional Practice\|publisher=[[Association for Computing Machinery]], [[IEEE]]\|date=2013-09-28\|url=https://ethics.acm.org/code-of-ethics/software-engineering-code\|doi=10.1145/265684.265699\|s2cid=9789551 }}</ref> (IEEE, ACM):		From Software Engineering Code of Ethics and Professional Practice<ref name="ieee">{{cite journal\|author=[[Donald Gotterbarn]], Keith Miller, and [[Simon Rogerson]]\|title=Software Engineering Code of Ethics and Professional Practice\|publisher=[[Association for Computing Machinery]], [[IEEE]]\|date=2013-09-28\|url=https://ethics.acm.org/code-of-ethics/software-engineering-code\|doi=10.1145/265684.265699\|s2cid=9789551 }}</ref> (IEEE, ACM):

	* '''Approve software only if they have a well-founded belief it is safe and meets specifications.''' Programmers cannot assume that a system is ready to use only because it performs the tasks needed. They should make sure these systems are also safe and meet every specification required by the user. If programs are not safe, users are unprotected from hackers that could steal important information or money. Therefore, several tests should be performed in order to ensure a [[Computer security\|system's security]] before approving it.		* '''Approve software only if they have a well-founded belief it is safe and meets specifications.''' Programmers cannot assume that a system is ready to use only because it performs the tasks needed. They should make sure these systems are also safe and meet every specification required by the user. If programs are not safe, users are unprotected from hackers that could steal important information or money. Therefore, several tests should be performed in order to ensure a [[Computer security\|system's security]] before approving it.
	* '''Accept full responsibility for their own work.''' If a program presents errors, the software developer should accept full responsibility for ~~his or her~~ work, and should work on revising, correcting, modifying, and [[Test method\|testing]] it.		* '''Accept full responsibility for their own work.''' If a program presents errors, the software developer should accept full responsibility for their work, and should work on revising, correcting, modifying, and [[Test method\|testing]] it.
	* '''Not knowingly use software that is obtained or retained either illegally or unethically.''' If a computer system will be used as a base for the creation of another, then permission to do so should be asked by the programmer. This principle prohibits using any other software for any purpose if the way it was gotten is not clear or is known to be illegal or unethical.		* '''Not knowingly use software that is obtained or retained either illegally or unethically.''' If a computer system will be used as a base for the creation of another, then permission to do so should be asked by the programmer. This principle prohibits using any other software for any purpose if the way it was gotten is not clear or is known to be illegal or unethical.
	* '''Identify, define, and address ethical, economic, cultural, legal and environmental issues related to work projects.''' If a programmer notices and identifies that working on a project will lead to any kind of problems, then the programmer should report it to ~~his or her~~ employer before continuing.		* '''Identify, define, and address ethical, economic, cultural, legal and environmental issues related to work projects.''' If a programmer notices and identifies that working on a project will lead to any kind of problems, then the programmer should report it to their employer before continuing.
	* '''Ensure that specifications for software on which they work satisfy the users’ requirements and they have the appropriate approvals.''' Software developers should come to their employers to ask for the correspondent approval to the system they are creating before continuing working on the next part. If it doesn't meet the requirements, then a modification to the source code of the system should be made.		* '''Ensure that specifications for software on which they work satisfy the users’ requirements and they have the appropriate approvals.''' Software developers should come to their employers to ask for the correspondent approval to the system they are creating before continuing working on the next part. If it doesn't meet the requirements, then a modification to the source code of the system should be made.
	* '''Ensure adequate testing, [[debugging]] and review of software.''' Programmers should perform the appropriate tests to the pieces of software they work with, and should check for errors and system security holes to make sure that the programs are well implemented.		* '''Ensure adequate testing, [[debugging]] and review of software.''' Programmers should perform the appropriate tests to the pieces of software they work with, and should check for errors and system security holes to make sure that the programs are well implemented.