Transcript Slide 1
Information Technology Morality and Ethics Prof.Dr. Srisakdi Charmonman President Computer Association of Thailand Under the Royal Patronage of HM the King [email protected]
www.charm.au.edu
Assumption University of Thailand 26 January 2008
IT Morality and Ethics
1. Introduction.
2. Sample Companies Violating Ethical Principles.
3. Five Problems in Information Societies 4. IT Trends that Increases Moral Problems.
5. Thai Freedom of Information.
2
IT Morality and Ethics
(Cont.) 6. IT Code of Ethics.
7. Sample Cases of IT Ethics.
8. Intellectual Properties.
9. Concluding Remarks.
3
1. Introduction.
IT is the central nervous system of any and all organizations.
Any organization not using IT can neither compete nor survive.
IT is changing very fast.
IT may be used immorally or unethically.
4
2. Sample Companies Violating Morality. 2.1 WorldCom Case.
2.2 Microsoft US Antitrust Case.
5
2.1 WorldCom Case.
WorldCom is an American telecommunications company. It was formed in 1983.
Formerly known as LDDS (Long Distance Services, Inc.).
6
WorldCom (Cont.)
In 1995, the company name was changed to WorldCom.
In 1997, WorldCom has acquired MCI Communications for about 37 billion bahts.
In 2001, the company had to lay off about 6,000 employees worldwide.
7
WorldCom (Cont.)
In 2002, Bernard Ebbers, the CEO, was fired.
In June, 2002, the company had to lay off about 17,000 employees.
8
WorldCom (Cont.)
The company was about 570,000 million baths in debt.
WorldCom declared bankruptcy in 2002.
9
WorldCom (Cont.)
In March, 2005, Ebbers received a sentence of 25 years in prison.
In March, 2007, the US Supreme Court refused to hear Ebbers’s appeal.
The 65-years-old Ebbers is scheduled to be released from prison in 2028 at the age of 85 (if still alive).
10
2.2 Microsoft US Antitrust Case.
Late 1990’s, the US government initiated antitrust proceedings against Microsoft.
Microsoft was distributing IE free of charge with its Windows OS.
Netscape protested.
11
Microsoft US Antitrust (Cont.)
In 2000, the US Department of Justice (DOJ) ruled that Microsoft be divided into two smaller companies to prevent it from indulging in anti competition practices.
In 2001, the US Court of Appeals reversed the ruling but stated that Microsoft had violated US antitrust law.
12
Microsoft US Antitrust (Cont.)
In August 2001, Microsoft appealed to the US Supreme Court to overturn the ruling that it was an illegal monopoly.
On November 12, 2002, the final judgment was agreed upon.
13
Microsoft US Antitrust (Cont.)
The final judgment stated that Microsoft shall not retaliate against an OEM by - altering relation with that OEM.
14
Microsoft US Antitrust (Cont.) - withholding newly introduced forms of non-monetary consideration from that OEM because the OEM is or is contemplating: * developing, distributing, promoting, using, selling, or licensing, software that compete with Microsoft.
15
Microsoft US Antitrust (Cont.) * shipping PC that included both Microsoft and non-Microsoft products.
* exercising any of the options or alternations provided for under this final judgment.
16
3. Five Problems in Information Society.
3.1 Information Rights.
3.2 Intellectual Property.
3.3 Responsibilities and Controls.
3.4 System Quality.
3.5 Quality of Life.
17
3.1 Information Rights.
An individual may exercise his rights when: - his private data is used without his authorization. - his private data is stolen because the system is not properly secured.
Etc.
18
Information Rights (Cont.)
Information Rights may be considered in terms of: 1) Ethical Aspect.
2) Societal Aspect.
3) Political Aspect.
19
1) Ethical Aspect.
Invasion of privacy may be: - Legal invasion, e.g. by the government.
- Marketing research.
- Eavesdropping.
- Concealing of data when applying for a job.
Etc.
20
2) Societal Aspect.
Society should establish standards of privacy.
Society should promote limitation of privacy relating to: - use of eMail.
- use of mobile phone.
- use of network.
Etc.
21
3) Political Aspect.
Government should establish rules and regulations concerning privacy.
The law should be enforced fairly.
There have been many violations such as in: - Personal data. - Organizational data.
Etc.
22
Information Rights (Cont.)
For personal data, there have been illegal access and illegal modification in: - eMail.
- Financial account.
- Personal files.
Etc.
23
Information Rights (Cont.)
For organizational data, there have been illegal access and illegal modification in: - Marketing data.
- Trade data.
- Accounting data.
Etc.
24
3.2 Intellectual Property.
Intellectual Property includes copyright, patent, trade secret, and trademark.
There must be law to protect Intellectual Property in the digital society.
Protection of Intellectual Property on the Internet is very difficult because it may not even be known that violation has occurred.
25
Intellectual Property (Cont.)
Violators should be prosecuted and punished accordingly as specified by the law.
Intellectual Property may be considered in terms of: 1) Ethical Aspect.
2) Societal Aspect.
3) Political Aspect.
26
1) Ethical Aspect of Intellectual Property.
Protection should be given to: - Software.
- eBook.
- Digital music.
- Digital video.
Etc.
27
Ethical Aspect (Cont.)
There should be law concerning: - Copyright.
- Patent.
- Trade Secret.
- Trademark.
Etc.
28
2) Societal Aspect of Intellectual Property.
Society must accept IP law.
Society must realize that it is easy to violate IP on the Internet.
29
3) Political Aspect of Intellectual Property.
Parliament must pass the law to protect Intellectual Property.
Parliament must pass the law to protect investors of IP-related products and services.
There may have to be special laws to protect Intellectual Property on the Internet.
30
3.3 Responsibilities and Controls.
Parliament must pass the law to cover responsibilities and controls of Intellectual Property.
Violators of personal privacy and intellectual property must be responsible for the damages occurred.
31
Responsibilities (Cont.)
Responsibilities and controls may be considered in terms of: 1) Ethical Aspect.
2) Societal Aspect.
3) Political Aspect.
32
1) Ethical Aspect of Responsibilities and Controls.
Any individual or organization producing digital goods must be ethical and responsible for the results of using the products or services.
33
2) Societal Aspect of Responsibilities and Controls.
Society should expect to see development of Information Systems.
Society should support development of Information Systems to increase efficiency and to reduce errors.
Society should realize the importance of IT services and the effects of new IT development.
34
3) Political Aspect of Responsibilities and Controls.
The government should try to resolve conflicts among IT users and providers such as: - Software producers.
- Internet service providers.
Etc.
35
Political Aspect (Cont.)
Parliament should pass law to protect IT users such as: - Individual. - Organization.
Etc.
36
3.4 System Quality.
IT systems must be of high standards to provide high quality.
Every organization must improve IT systems continually.
New IT systems must have high quality.
Every organization should use the Internet to improve its quality.
37
System Quality (Cont.)
System Quality may be considered in terms of: 1) Ethical Aspect.
2) Societal Aspect.
3) Political Aspect.
38
1) Ethical Aspect of System Quality.
Producers of Information Systems must be ethical in order to produce IT systems with high standards and efficiency.
39
2) Society Aspect of System Quality.
Society expects to have reliable IT systems.
Reliable IT systems contribute to better development of society.
Society expects to have answers and data to members of society.
40
3) Political Aspect of System Quality.
The parliament must pass the law to enforce: - Quality of IT system.
- Reliability of IT system.
- Responsibility of IT system administrators.
Etc.
41
Political Aspect (Cont.)
The government must establish an organization to develop and enforce: - Software quality.
- Hardware quality.
- Data quality.
Etc.
42
Political Aspect (Cont.)
The government must promote cooperation of all parties concerned to assure high quality of IT system.
The government should support replacement of low quality systems by high quality IT systems.
43
3.5 Quality of Life.
New Information Technology supports behavior and culture to promote better quality of life.
Development of IT systems contributes to better efficiency in organization, and thus, better quality of life.
44
Quality of Life (Cont.)
However, IT systems may have negative effects to culture.
The US Department of Defense established the DoD Quality of Life Information Technology Center to promote better quality of life in DoD
45
4. IT Trends that Increases Moral Problems.
4.1 Computer abilities.
4.2 Storage device prices.
4.3 Data analysis.
4.4 Network and the Internet.
46
4.1 Computer Abilities.
Modern computer can rapidly process such as: - In 1958, 5 million times/second.
- In 1967, 10 million times/second.
- In 1969, 25 million times/second.
- In 1974 - 1979, 33 million times/second.
- In 1978 - 1982, 200 million times/second.
47
Computer Abilities (Cont.) - In 1986, 233 - 300 million times/second.
- In 1988, 450 million times/second.
- In 1989, 1,000 million times/second.
- In 2001, 2,000 - 2,200 million times/second. - In 2004, 3,000 - 3,200 million times/second.
- In 2008, billion times/second
48
4.2 Storage Device Prices.
Earlier, the memory was very expensive. For example: - In 1958, 2 KB of memory approximately 1 million baths.
Etc.
49
Storage Device Prices (Cont.)
Later, memory is cheaper such as: - 256 MB of memory about 1,290 baths.
- 512 MB of memory about 2,470 baths.
- 1024 MB of memory about 4,490 baths.
- 2048 MB of memory about 8,980 baths.
Etc.
In 2008, Gigabytes of memory for a few hundred baths.
50
4.3 Data Analysis.
Because of the progress of technology, it is easy and fast to analyze data.
The possibility of violation increases.
Corporations and organizations have adopted the technology of data analysis to manage their document.
51
4.4 Network and Internet
Over 1,400 million computers are linked to the Internet.
Criminals can use a remote computer to access any other computer in the network.
52
5. Thai Freedom of Information Act.
The law was passed in the year 1997.
Information may be arranged in the form of a document, file, report, book, diagram, map, drawing, photograph, film, visual or sound record, or recording by a computer or any other method which can be displayed.
53
Thai Freedom of Information Act (Cont.) What the Government knows, the citizen must be able to have access to.
Official information which may jeopardize the Royal Institution shall not be disclosed.
54
Thai Freedom of Information Act (Cont.) Official information which may endanger the life or safety of any person shall not be disclosed.
A medical report or personal information in which the disclosure may unreasonably encroach upon the right of privacy shall not be disclosed.
55
Thai Freedom of Information Act (Cont.) A government agency shall not disclose personal information in its control to other government agencies or other persons without prior consent given in writing from the person who is the owner of the information.
56
Thai Freedom of Information Act (Cont.) A person shall have the right to get access to personal information relating to him.
When such person makes a request in writing, the government agency in control of such information shall allow him or his authorized representative to inspect or obtain a copy of the same.
57
Thai Freedom of Information Act (Cont.) Personal information means individual facts which can identify the owner in a direct or indirect way.
Protecting personal information is a part of individual rights.
58
6. IT Code of Ethics.
6.1 Association for Computing Machinery.
6.3 IEEE Computer Association 6.4 Internet Society
.
6.5 Computer Society and ACM Approve Software Engineering Code of Ethics.
59
6.1 Association for Computing Machinery.
ACM is widely recognized as the premier membership organization for computing professionals, delivering resources that advance computing as a science and a profession; enable professional development; and promote policies and research that benefit society.
60
ACM (Cont.)
ACM hosts the computing industry's leading Digital Library and Guide to Computing Literature, and serves its global members and the computing profession with journals and magazines, conferences, workshops, electronic forums, and Online Books and Courses.
61
ACM (Cont.)
Commitment to ethical professional conduct is expected of every member (voting members, associate members, and student members) of the Association for Computing Machinery (ACM).
Thailand Chapter of the ACM is located at “Srisakdi Charmonman IT Center” with Prof. Srisakdi Charmonman as the Founding and Present President.
62
ACM Code of Ethics.
This Code, consisting of 24 imperatives formulated as statements of personal responsibility, identifies the elements of such a commitment. It contains many, but not all, issues professionals are likely to face.Section 1 outlines fundamental ethical considerations, while Section 2 addresses additional, more specific considerations of professional conduct.
63
ACM (Cont.)
Statements in Section 3 pertain more specifically to individuals who have a leadership role, whether in the workplace or in a volunteer capacity such as with organizations like ACM. Principles involving compliance with this Code are given in Section 4.
64
ACM (Cont.)
The Code shall be supplemented by a set of Guidelines, which provide explanation to assist members in dealing with the various issues contained in the Code.
It is expected that the Guidelines will be changed more frequently than the Code.
65
ACM (Cont.)
The Code and its supplemented Guidelines are intended to serve as a basis for ethical decision making in the conduct of professional work.
Secondarily, they may serve as a basis for judging the merit of a formal complaint pertaining to violation of professional ethical standards.
66
ACM (Cont.)
It should be noted that although computing is not mentioned in the imperatives of Section 1, the Code is concerned with how these fundamental imperatives apply to one's conduct as a computing professional.
67
ACM (Cont.)
These imperatives are expressed in a general form to emphasize that ethical principles which apply to computer ethics are derived from more general ethical principles.
68
ACM (Cont.)
It is understood that some words and phrases in a code of ethics are subject to varying interpretations, and that any ethical principle may conflict with other ethical principles in specific situations.
69
ACM (Cont.)
Questions related to ethical conflicts can best be answered by thoughtful consideration of fundamental principles, rather than reliance on detailed regulations.
70
ACM (Cont.) Content & Guidelines 1) General Moral Imperatives. 2) More Specific Professional Responsibilities. 3) Organizational Leadership Imperatives.
4) Compliance with the Code. Acknowledgments.
71
1) ACM General Moral Imperatives.
(1.1) Contribute to society
and human well-being. This principle concerning the quality of life of all people affirms an obligation to protect fundamental human rights and to respect the diversity of all cultures.
72
ACM Moral Imperatives (Cont.)
An essential aim of computing professionals is to minimize negative consequences of computing systems, including threats to health and safety.
73
ACM Moral Imperatives (Cont.)
When designing or implementing systems, computing professionals must attempt to ensure that the products of their efforts will be used in socially responsible ways, will meet social needs, and will avoid harmful effects to health and welfare.
74
ACM Moral Imperatives (Cont.)
In addition to a safe social environment, human well-being includes a safe natural environment. Therefore, computing professionals who design and develop systems must be alert to, and make others aware of, any potential damage to the local or global environment.
75
ACM Moral Imperatives (Cont.) (1.2) Avoid harm to others.
"Harm" means injury or negative consequences, such as undesirable loss of information, loss of property, property damage, or unwanted environmental impacts.
76
ACM Moral Imperatives (Cont.)
This principle prohibits use of computing technology in ways that result in harm to any of the following: users, the general public, employees, employers.
77
ACM Moral Imperatives (Cont.)
Harmful actions include intentional destruction or modification of files and programs leading to serious loss of resources or unnecessary expenditure of human resources such as the time and effort required to purge systems of "computer viruses."
78
ACM Moral Imperatives (Cont.)
Well-intended actions, including those that accomplish assigned duties, may lead to harm unexpectedly. In such an event the responsible person or persons are obligated to undo or mitigate the negative consequences as much as possible.
79
ACM Moral Imperatives (Cont.)
One way to avoid unintentional harm is to carefully consider potential impacts on all those affected by decisions made during design and implementation.
80
ACM Moral Imperatives (Cont.)
To minimize the possibility of indirectly harming others, computing professionals must minimize malfunctions by following generally accepted standards for system design and testing.
81
ACM Moral Imperatives (Cont.)
Furthermore, it is often necessary to assess the social consequences of systems to project the likelihood of any serious harm to others.
82
ACM Moral Imperatives (Cont.)
If system features are misrepresented to users, coworkers, or supervisors, the individual computing professional is responsible for any resulting injury.
83
ACM Moral Imperatives (Cont.)
In the work environment the computing professional has the additional obligation to report any signs of system dangers that might result in serious personal or social damage.
84
ACM Moral Imperatives (Cont.)
If one's superiors do not act to curtail or mitigate such dangers, it may be necessary to "blow the whistle" to help correct the problem or reduce the risk.
However, capricious or misguided reporting of violations can, itself, be harmful.
85
ACM Moral Imperatives (Cont.)
Before reporting violations, all relevant aspects of the incident must be thoroughly assessed. In particular, the assessment of risk and responsibility must be credible.
It is suggested that advice be sought from other computing professionals. See principle 2.5 regarding thorough evaluations.
86
ACM Moral Imperatives (Cont.) (1.3) Be Honest and Trustworthy.
Honesty is an essential component of trust.
Without trust an organization cannot function effectively.
87
ACM Moral Imperatives (Cont.)
The honest computing professional will not make deliberately false or deceptive claims about a system or system design, but will instead provide full disclosure of all pertinent system limitations and problems.
88
ACM Moral Imperatives (Cont.)
A computer professional has a duty to be honest about his or her own qualifications, and about any circumstances that might lead to conflicts of interest.
89
ACM Moral Imperatives (Cont.)
Membership in volunteer organizations such as ACM may at times place individuals in situations where their statements or actions could be interpreted as carrying the "weight" of a larger group of professionals.
90
ACM Moral Imperatives (Cont.)
An ACM member will exercise care to not misrepresent ACM or positions and policies of ACM or any ACM units.
91
ACM Moral Imperatives (Cont.) (1.4) Be fair and take action not to discriminate.
The values of equality, tolerance, respect for others, and the principles of equal justice govern this imperative.
92
ACM Moral Imperatives (Cont.)
Discrimination on the basis of race, sex, religion, age, disability, national origin, or other such factors is an explicit violation of ACM policy and will not be tolerated.
93
ACM Moral Imperatives (Cont.)
Inequities between different groups of people may result from the use or misuse of information and technology.
In a fair society,all individuals would have equal opportunity to participate in, or benefit from, the use of computer resources regardless of race, sex, religion, age, disability, national origin or other such similar factors.
94
ACM Moral Imperatives (Cont.)
However, these ideals do not justify unauthorized use of computer resources nor do they provide an adequate basis for violation of any other ethical imperatives of this code.
95
ACM Moral Imperatives (Cont.) (1.5) Honor property rights including copyrights and patent.
Violation of copyrights, patents, trade secrets and the terms of license agreements is prohibited by law in most circumstances.
96
ACM Moral Imperatives (Cont.)
Even when software is not so protected, such violations are contrary to professional behavior.
Copies of software should be made only with proper authorization. Unauthorized duplication of materials must not be condoned.
97
ACM Moral Imperatives (Cont.) (1.6) Give proper credit for intellectual property.
Computing professionals are obligated to protect the integrity of intellectual property.
Specifically, one must not take credit for other's ideas or work, even in cases where the work has not been explicitly protected by copyright, patent, etc.
98
ACM Moral Imperatives (Cont.) (1.7) Respect the privacy of others.
Computing and communication technology enables the collection and exchange of personal information on a scale unprecedented in the history of civilization.
Thus there is increased potential for violating the privacy of individuals and groups.
99
ACM Moral Imperatives (Cont.)
It is the responsibility of professionals to maintain the privacy and integrity of data describing individuals.
This includes taking precautions to ensure the accuracy of data, as well as protecting it from unauthorized access or accidental disclosure to inappropriate individuals.
100
ACM Moral Imperatives (Cont.)
Furthermore, procedures must be established to allow individuals to review their records and correct inaccuracies.
101
ACM Moral Imperatives (Cont.)
This imperative implies that only the necessary amount of personal information be collected in a system, that retention and disposal periods for that information be clearly defined and enforced, and that personal information gathered for a specific purpose not be used for other purposes without consent of the individual(s).
102
ACM Moral Imperatives (Cont.)
These principles apply to electronic communications, including electronic mail, and prohibit procedures that capture or monitor electronic user data, including messages, without the permission of users or bona fide authorization related to system operation and maintenance.
103
ACM Moral Imperatives (Cont.)
User data observed during the normal duties of system operation and maintenance must be treated with strictest confidentiality, except in cases where it is evidence for the violation of law, organizational regulations, or this Code.
104
ACM Moral Imperatives (Cont.)
In these cases, the nature or contents of that information must be disclosed only to proper authorities.
105
ACM Moral Imperatives (Cont.) (1.8) Honor confidentiality.
The principle of honesty extends to issues of confidentiality of information whenever one has made an explicit promise to honor confidentiality or, implicitly, when private information not directly related to the performance of one's duties becomes available.
106
ACM Moral Imperatives (Cont.)
The ethical concern is to respect all obligations of confidentiality to employers, clients, and users unless discharged from such obligations by requirements of the law or other principles of this Code.
107
2) ACM More Specific Professional Responsibilities. (2.1) Strive to achieve the highest quality, effectiveness and dignity in both the process and products of professional work.
108
ACM Specific Responsibilities (Cont.)
Excellence is perhaps the most important obligation of a professional.
The computing professional must strive to achieve quality and to be cognizant of the serious negative consequences that may result from poor quality in a system.
109
ACM Specific Responsibilities (Cont.) (2.2) Acquire and maintain professional competence.
Excellence depends on individuals who take responsibility for acquiring and maintaining professional competence.
110
ACM Specific Responsibilities (Cont.)
A professional must participate in setting standards for appropriate levels of competence, and strive to achieve those standards.
111
ACM Specific Responsibilities (Cont.)
Upgrading technical knowledge and competence can be achieved in several ways:doing independent study; attending seminars, conferences, or courses; and being involved in professional organizations.
112
ACM Specific Responsibilities (Cont.) (2.3) Know and respect existing laws pertaining to professional work.
ACM members must obey existing local, state,province, national, and international laws unless there is a compelling ethical basis not to do so.
113
ACM Specific Responsibilities (Cont.)
Policies and procedures of the organizations in which one participates must also be obeyed.
But compliance must be balanced with the recognition that sometimes existing laws and rules may be immoral or inappropriate and, therefore, must be challenged.
114
ACM Specific Responsibilities (Cont.)
Violation of a law or regulation may be ethical when that law or rule has inadequate moral basis or when it conflicts with another law judged to be more important.
115
ACM Specific Responsibilities (Cont.)
If one decides to violate a law or rule because it is viewed as unethical, or for any other reason, one must fully accept responsibility for one's actions and for the consequences.
116
ACM Specific Responsibilities (Cont.) (2.4) Accept and provide appropriate professional review.
Quality professional work, especially in the computing profession, depends on professional reviewing and critiquing.
Whenever appropriate, individual members should seek and utilize peer review as well as provide critical review of the work of others.
117
ACM Specific Responsibilities (Cont.) (2.5) Give comprehensive and thorough evaluations of computer systems and their impacts, including analysis of possible risks.
Computer professionals must strive to be perceptive, thorough, and objective when evaluating, recommending, and presenting system descriptions and alternatives.
118
ACM Specific Responsibilities (Cont.)
Computer professionals are in a position of special trust, and therefore have a special responsibility to provide objective, credible evaluations to employers, clients, users, and the public.
119
ACM Specific Responsibilities (Cont.)
When providing evaluations the professional must also identify any relevant conflicts of interest, as stated in imperative 1.3.
120
ACM Specific Responsibilities (Cont.)
As noted in the discussion of principle 1.2 on avoiding harm, any signs of danger from systems must be reported to those who have opportunity and/or responsibility to resolve them.
See the guidelines for imperative 1.2 for more details concerning harm,including the reporting of professional violations.
121
ACM Specific Responsibilities (Cont.) (2.6) Honor contracts, agreements, and assigned responsibilities.
Honoring one's commitments is a matter of integrity and honesty.
For the computer professional this includes ensuring that system elements perform as intended.
122
ACM Specific Responsibilities (Cont.)
Also, when one contracts for work with another party, one has an obligation to keep that party properly informed about progress toward completing that work.
A computing professional has a responsibility to request a change in any assignment that he or she feels cannot be completed as defined.
123
ACM Specific Responsibilities (Cont.)
Only after serious consideration and with full disclosure of risks and concerns to the employer or client, should one accept the assignment.
The major underlying principle here is the obligation to accept personal accountability for professional work.
On some occasions other ethical principles may take greater priority.
124
ACM Specific Responsibilities (Cont.)
A judgment that a specific assignment should not be performed may not be accepted.
Having clearly identified one's concerns and reasons for that judgment, but failing to procure a change in that assignment, one may yet be obligated, by contract or by law, to proceed as directed.
125
ACM Specific Responsibilities (Cont.)
The computing professional's ethical judgment should be the final guide in deciding whether or not to proceed.
Regardless of the decision, one must accept the responsibility for the consequences.
126
ACM Specific Responsibilities (Cont.)
However, performing assignments "against one's own judgment" does not relieve the professional of responsibility for any negative consequences.
127
ACM Specific Responsibilities (Cont.) (2.7) Improve public understanding of computing and its consequences.
Computing professionals have a responsibility to share technical knowledge with the public by encouraging understanding of computing, including the impacts of computer systems and their limitations.
128
ACM Specific Responsibilities (Cont.)
This imperative implies an obligation to counter any false views related to computing.
129
ACM Specific Responsibilities (Cont.) (2.8) Access computing and communication resources only when authorized to do so.
Theft or destruction of tangible and electronic property is prohibited by imperative1.2 - "Avoid harm to others." Trespassing and unauthorized use of a computer or communication system is addressed by this imperative.
130
ACM Specific Responsibilities (Cont.)
Trespassing includes accessing communication networks and computer systems, or accounts and files associated with those systems, without explicit authorization to do so. Individuals and organizations have the right to restrict access to their systems so long as they do not violate the discrimination principle.
131
ACM Specific Responsibilities (Cont.)
No one should enter or use another's computer system, software, or data files without permission.
One must always have appropriate approval before using system resources, including communication ports, file space, other system peripherals, and computer time.
132
3) ACM Organizational Leadership Imperatives. Background note:
This section draws extensively from the draft IFIP Code of Ethics, especially its sections on organizational ethics and international concerns.
133
ACM Leadership (Cont.)
The ethical obligations of organizations tend to be neglected in most codes of professional conduct, perhaps because these codes are written from the perspective of the individual member.
This dilemma is addressed by stating these imperatives from the perspective of the organizational leader.
134
ACM Leadership (Cont.)
In this context "leader" is viewed as any organizational member who has leadership or educational responsibilities.
These imperatives generally may apply to organizations as well as their leaders.
135
ACM Leadership (Cont.)
In this context "organizations" are corporations, government agencies,and other "employers," as well as volunteer professional organizations.
136
ACM Leadership (Cont.) (3.1) Articulate social responsibilities of members of an organizational unit and encourage full acceptance of those responsibilities.
Because organizations of all kinds have impacts on the public, they must accept responsibilities to society.
137
ACM Leadership (Cont.)
Organizational procedures and attitudes oriented toward quality and the welfare of society will reduce harm to members of the public, thereby serving public interest and fulfilling social responsibility.
Therefore,organizational leaders must encourage full participation in meeting social responsibilities as well as quality performance.
138
ACM Leadership (Cont.) (3.2) Manage personnel and resources to design and build information systems that enhance the quality of working life.
Organizational leaders are responsible for ensuring that computer systems enhance, not degrade, the quality of working life.
139
ACM Leadership (Cont.)
When implementing a computer system, organizations must consider the personal and professional development, physical safety, and human dignity of all workers.
Appropriate human-computer ergonomic standards should be considered in system design and in the workplace.
140
ACM Leadership (Cont.) (3.3) Acknowledge and support proper and authorized uses of an organization's computing and communication resources.
Because computer systems can become tools to harm as well as to benefit an organization, the leadership has the responsibility to clearly define appropriate and inappropriate uses of organizational computing resources.
141
ACM Leadership (Cont.)
While the number and scope of such rules should be minimal, they should be fully enforced when established.
142
ACM Leadership (Cont.) (3.4) Ensure that users and those who will be affected by a system have their needs clearly articulated during the assessment and design of requirements; later the system must be validated to meet requirements.
143
ACM Leadership (Cont.)
Current system users, potential users and other persons whose lives may be affected by a system must have their needs assessed and incorporated in the statement of requirements. System validation should ensure compliance with those requirements.
144
ACM Leadership (Cont.) (3.5) Articulate and support policies that protect the dignity of users
and others affected by a computing system.
Designing or implementing systems that deliberately or inadvertently demean individuals or groups is ethically unacceptable.
145
ACM Leadership (Cont.)
Computer professionals who are in decision making positions should verify that systems are designed and implemented to protect personal privacy and enhance personal dignity.
146
ACM Leadership (Cont.) (3.6) Create opportunities for members
of the organization to learn the principles and limitations of computer systems.
This complements the imperative on public understanding. Educational opportunities are essential to facilitate optimal participation of all organizational members.
147
ACM Leadership (Cont.)
Opportunities must be available to all members to help them improve their knowledge and skills in computing, including courses that familiarize them with the consequences and limitations of particular types of systems.
148
ACM Leadership (Cont.)
In particular, professionals must be made aware of the dangers of building systems around oversimplified models, the improbability of anticipating and designing for every possible operating condition, and other issues related to the complexity of this profession.
149
4) ACM Compliance with the Code.
(4.1) Uphold and promote the principles of this Code.
The future of the computing profession depends on both technical and ethical excellence.
150
ACM Compliance (Cont.)
Not only is it important for ACM computing professionals to adhere to the principles expressed in this Code, each member should encourage and support adherence by other members.
151
ACM Compliance (Cont.) (4.2) Treat violations of this code as inconsistent with membership in the ACM.
Adherence of professionals to a code of ethics is largely a voluntary matter.
However, if a member does not follow this code by engaging in gross misconduct, membership in ACM may be terminated.
152
6.2 IEEE Code of Ethics.
The Institute of Electrical and Electronics Engineering has - more than 370,000 members, including more than 80,000 students, in over 160 countries; - 319 sections in ten geographic regions worldwide;
153
IEEE Code of Ethics (Cont.) - 1676 chapters that unite local members with similar technical interests; - more than 1,526 student branches at colleges and universities in 80 countries; - 39 societies and 5 technical councils representing the wide range of technical interests;
154
IEEE Code of Ethics (Cont.) - 132 transactions, journals and magazines; - more than 450 IEEE sponsored or cosponsored conferences worldwide each year; - over 900 active IEEE standards and more than 400 in development.
155
IEEE Code of Ethics (Cont.)
The IEEE Computer Society (IEEE CS) has - Nearly 90,000 members - The world's leading organization of computer professionals.
- Founded in 1946.
- The largest of the 39 societies of the IEEE.
156
IEEE Code of Ethics (Cont.)
The IEEE Computer Society's vision is to be the leading provider of technical information, community services, and personalized services to the world's computing professionals.
157
IEEE Code of Ethics (Cont.)
The Society is dedicated to advancing the theory, practice, and application of computer and information processing technology.
158
IEEE Code of Ethics (Cont.)
Through its conferences, applications related and research-oriented journals, local and student chapters, e-learning campus, technical committees, and standards working groups, the Society promotes an active exchange of information, ideas, and technological innovation among its members.
159
IEEE Code of Ethics (Cont.)
In addition, the Society maintains close ties with the US Computing Sciences Accreditation Board and Accreditation Board for Engineering and Technology, monitoring and evaluating curriculum accreditation guidelines.
160
IEEE Code of Ethics (Cont.)
With about 40 percent of IEEE CS members living and working outside the United States, the Computer Society fosters international communication, cooperation, and information exchange.
161
IEEE Code of Ethics (Cont.)
To meet the needs of our members conveniently and efficiently, the Society maintains a service center office in Tokyo, Japan; a publications office in Los Alamitos, California; and its headquarters in Washington, DC.
162
IEEE Code of Ethics (Cont.)
Thailand Joint Chapter of the Computer Society and the Engineering Management Society is located at “Srisakdi Charmonman IT Center” with Prof. Srisakdi Charmonman as the Founding and Present President.
163
IEEE Code of Ethics (Cont.)
We, the members of the IEEE, in recognition of the importance of our technologies in affecting the quality of life throughout the world, and in accepting a personal obligation to our profession, its members and the communities we serve, do hereby commit ourselves to the highest ethical and professional conduct and agree:
164
IEEE Code of Ethics (Cont.) 1. To accept responsibility in making decisions consistent with the safety, health and welfare of the public, and to disclose promptly factors that might endanger the public or the environment.
2. To avoid real or perceived conflicts of interest whenever possible, and to disclose them to affected parties when they do exist.
165
IEEE Code of Ethics (Cont.) 3. To be honest and realistic in stating claims or estimates based on available data.
4. To reject bribery in all its forms.
5. To improve the understanding of technology, its appropriate application, and potential consequences.
166
IEEE Code of Ethics (Cont.) 6. To maintain and improve our technical competence and to undertake technological tasks for others only if qualified by training or experience, or after full disclosure of pertinent limitations.
167
IEEE Code of Ethics (Cont.) 7. To seek, accept, and offer honest criticism of technical work, to acknowledge and correct errors, and to credit properly the contributions of others.
8. To treat fairly all persons regardless of such factors as race, religion, gender, disability, age, or national origin.
168
IEEE Code of Ethics (Cont.) 9. To avoid injuring others, their property, reputation, or employment by false or malicious action.
10. To assist colleagues and co-workers in their professional development and to support them in following this code of ethics.
169
•
6.3 Ethics and Human Right in the Information Society.
The Internet Society (ISOC) is a professional membership society with more than 80 organizations and over 26,000 individual members in more than 180 countries.
170
ISOC (Cont.)
Since its inception in 1992, ISOC has promoted the evolution and growth of the Internet as a global communications infrastructure, provided support for the Internet Engineering Task Force (IETF), and encouraged the responsible and effective use of the Internet through education, discussion and advice to public policy makers.
171
ISOC (Cont.)
ISOC’s activities - particularly in developing countries - help expand the reach of the Internet and bring benefits to people around the world.
172
ISOC (Cont.)
ISOC’s activities: - particularly in developing countries - help expand the reach of the Internet and bring benefits to people around the world.
173
ISOC (Cont.)
At the Internet Society, we believe that that global success of the Internet reflects the important of a series of considerations that emerged from developing the technology and the protocols that enabled it.
174
ISOC (Cont.)
Those considerations have become the core values of our organization. In promoting the Internet and access to it across the world, we seek to promote those values.
175
ISOC (Cont.)
Thailand Chapter of the Internet Society is located at “Srisakdi Charmonman IT Center” with Prof. Srisakdi Charmonman as the Founding and Present President.
Assumption University is the only Founding Member in Southeast Asia of the Internet Society.
176
ISOC (Cont.)
ISOC’s vision of “The Internet is for everyone” is based upon the following core values: (1) The Quality of Life. (2) Informed Individuals.
(3) Innovation and Creativity.
(4) Global and Local.
177
ISOC (Cont.) (5) Open and Transparent Processes.
(6) Excessively Restrictive Government or Private Controls.
178
ISOC (Cont.)
(1) The Quality of Life. The quality of life for people in all parts of the world is enhanced by their ability to enjoy the benefits of an open and global Internet.
179
ISOC (Cont.)
(2) Informed Individuals. Well informed individuals make up the foundation of an open and global Internet society.
180
ISOC (Cont.)
(3) Innovation and Creativity.
The Internet’s open and decentralized nature is the prerequisite for it to continue being a platform for innovation and creativity.
181
ISOC (Cont.)
(4) Global and Local.
Promoting the open development, evolution and use of the Internet for the benefit of all implies a combination of global initiatives and the local engagement of people in their home regions.
182
ISOC (Cont.)
(5) Open and Transparent Processes. Technical standards and Internet operating procedures should be developed and asserted through open and transparent processes, with access to information and incentives to participate for everyone.
183
ISOC (Cont.) (6) Excessively Restrictive Government or Private Controls.
The social, political, and economic benefits of the Internet are substantially diminished by excessively restrictive government or private controls on computer hardware or software, telecommunications infrastructure or Internet content, constantly affirmed and promoted an ethical information society.
184
ISOC (Cont.)
The Internet Society also promotes a set of user-related abilities that echo and illustrate these fundamental principles : (1) The Ability to Connect.
(2) The Ability to Speak.
(3) The Ability to Innovate.
(4) The Ability to Share. (5) The Ability to Choose. (6) The Ability to Trust.
185
ISOC (Cont.)
(1) The Ability to Connect.
The edge-dominant end-to-end architecture of the Internet is essential to its utility as a platform for: - Innovation.
- Creativity.
- Economic opportunity.
186
The Ability to Connect (Cont.)
To preserve this quality, we will oppose efforts to establish standards or practices that would make it difficult or impossible for some users of the Internet to use the full range of Internet applications of all kinds.
187
ISOC (Cont.)
(2) The Ability to Speak.
The Internet is a powerful mass medium for self-expression which depends on the ability of its users to speak freely.
188
The Ability to Speak (Cont.)
ISOC believe that the Internet must support private: - where appropriate, anonymous - means of communication and collaboration among individuals and groups
It will oppose efforts to restrict the type or content of information exchanged on the Internet.
189
ISOC (Cont.)
(3) The Ability to Innovate The remarkable growth of the Internet and the limitless variety of Internet applications follow directly from the open model of Internet connectivity and standards development.
190
The Ability to Innovate (Cont.)
Any individual, organization, or company can develop and distribute a new Internet application that can be used by anyone.
ISOC recognize the enormous value of this innovation, and oppose governmental or non-governmental restrictions on the evolution and use of Internet technology.
191
ISOC (Cont.)
(4) The Ability to Share. The many-to-many architecture of the Internet makes it a powerful tool for sharing, education, and collaboration. It has enabled the global open source community to develop and enhance many of the key components of the Internet, such as the Domain Name System and the World-Wide Web, and has made the vision of digital libraries a reality.
192
The Ability to Share (Cont.)
To preserve these benefits we will oppose technologies and legislation that would inhibit the freedom to develop and use open source software or limit the well-established concept of fair use, which is essential to scholarship, education, and collaboration.
193
ISOC (Cont.)
(5) The Ability to Choose. Government regulation and the economic power of incumbent telecommunication monopolies can delay or prevent the growth of the Internet by limiting the ability of competitors to provide new, better, cheaper, or more innovative Internet related services.
194
The Ability to Choose (Cont.)
ISOC advocate policies that promote competition in telecommunications, Internet services, Internet-related software, and e-commerce applications.
195
ISOC (Cont.)
(6) The Ability to Trust.
Everyone’s ability to connect, speak, innovate, share, and choose depends on the Internet’s ability to support trustworthy internetworking - ensuring the security, reliability, and stability of increasingly critical and pervasive applications and services.
196
6.4 Computer Society and ACM Software Engineering Code of Ethics.
Software engineering has evolved over the past several years from an activity of computer engineering to a discipline in its own right.
197
Software Code of Ethics (Cont.)
With an eye toward formalizing the field, the IEEE Computer Society has engaged in several activities to advance the professionalism of software engineering, such as establishing certification requirements for software developers.
198
Software Code of Ethics (Cont.)
To complement this work, a joint task force of the Computer Society and the ACM has recently established another linchpin of professionalism for software engineering: a code of ethics.
199
Software Code of Ethics (Cont.)
After an extensive review process, version 5.2 of the Software Engineering Code of Ethics and Professional Practice, recommended last year by the IEEECS/ACM Joint Task Force on Software Engineering Ethics and Professional Practices, was adopted by both the IEEE Computer Society and the ACM.
200
Software Code of Ethics (Cont.) Purpose
The Software Engineering Code of Ethics and Professional Practice, intended as a standard for teaching and practicing software engineering, documents the ethical and professional obligations of software engineers.
201
Software Code of Ethics (Cont.)
The code should instruct practitioners about the standards society expects them to meet, about what their peers strive for, and about what to expect of one another.
202
Software Code of Ethics (Cont.)
In addition, the code should inform the public about the responsibilities that are important to the profession.
Adopted by the Computer Society and the ACM—two leading international computing societies—the code of ethics is intended as a guide for members of the evolving software engineering profession.
203
Software Code of Ethics (Cont.)
The code was developed by a multinational task force with additional input from other professionals from industry, government posts, military installations, and educational professions.
204
Software Code of Ethics (Cont.) Changes to the code
Major revisions were made between version 3.0 widely distributed through
Computer
(Don Gotterbarn, Keith Miller, and Simon Rogerson, “Software Engineering Code of Ethics, Version3.0,” November 1997, pp. 88-92) and Communications of the ACM and version 5.2, the recently approved version.
205
Software Code of Ethics (Cont.)
The preamble was significantly revised to include specific standards that can help professionals make ethical decisions.
To facilitate a quick review of the principles, a shortened version of the code was added to the front of the full version.
206
Software Code of Ethics (Cont.)
This shortened version is not intended to be a standalone abbreviated code.
The details of the full version are necessary to provide clear guidance for the practical application of these ethical principles.
207
Software Code of Ethics (Cont.)
In addition to these changes, the eight principles were reordered to reflect the order in which software professionals should consider their ethical obligations:
Version 3.0’s first principle concerned the product, while version 5.2 begins with the public.
208
Software Code of Ethics (Cont.)
The primacy of well-being and quality of life of the public in all decisions related to software engineering is emphasized throughout the code.
209
Software Code of Ethics (Cont.)
This obligation is the final arbiter in all decisions: “In all these judgements concern for the health, safety and welfare of the public is primary; that is, the ‘Public Interest’ is central to this Code.”
210
Software Code of Ethics (Cont.)
For example, the whistle-blowing clauses describe a software engineer’s obligations when public safety is threatened by defective software development and describe steps to meet those obligations.
211
Software Code of Ethics (Cont.)
The code now contains an open-ended clause against using prejudices or bias in any decision making, written broadly enough to include consideration of new social concerns.
212
Software Code of Ethics (Cont.)
Finally, the code includes specific language about the importance of ethical behavior during the maintenance phase of software development.
213
Software Code of Ethics (Cont.)
The new text reflects the amount of time a computer professional spends modifying and improving existing software and also makes clear that we need to treat maintenance maintenance with the same professionalism as new development.
214
Software Code of Ethics (Cont.)
The quality of maintenance depends upon the professionalism of the software engineer, because maintenance is more likely to be scrutinized only locally , whereas new development is generally reviewed at a broader corporate level.
215
Software Code of Ethics (Cont.)
In the same spirit that created the code of ethics, the Computer Society and the ACM continue to support the software engineering profession through the Software Engineering Professionalism and Ethics Project (computer.org/tab/swecc/Sepec.htm) .
216
Software Code of Ethics (Cont.)
This project will help make the code an effective practical tool by publishing case studies, supporting further corporate adoption of the code, developing curriculum material, running workshops, and collaborating with licensing bodies and professional
217
Software Code of Ethics (Cont.) Short version: Preamble
The short version of the code summarizes aspirations at a high level of abstraction.
The clauses that are included in the full version give examples and details of how these aspirations change the way we act as software engineering professionals.
218
Software Code of Ethics (Cont.)
Without the aspirations, the details can become legalistic and tedious; without the details, the aspirations can become highsounding but empty; together, the aspirations and the details form a cohesive code.
219
Software Code of Ethics (Cont.)
Software engineers shall commit themselves to making the analysis, specification, design, development, testing, and maintenance of software a beneficial and respected profession.
220
Software Code of Ethics (Cont.)
In accordance with their commitment to the health, safety, and welfare of the public, software engineers shall adhere to the following eight Principles: 1. Public. Software engineers shall act consistently with the public interest.
221
Software Code of Ethics (Cont.) 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.
222
Software Code of Ethics (Cont.) 3. Product. Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.
4. Judgment.
Software engineers shall maintain integrity and independence in their professional judgment.
223
Software Code of Ethics (Cont.) 5. Management.
Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance.
224
Software Code of Ethics (Cont.) 6. Profession. Software engineers shall advance the integrity and reputation of the profession consistent with the public interest.
7. Colleagues. Software engineers shall be fair to and supportive of their colleagues.
225
Software Code of Ethics (Cont.) 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.
226
Software Code of Ethics (Cont.) Full version: Preamble
Computers have a central and growing role in commerce, industry, government, medicine, education, entertainment, and society at large.
227
Software Code of Ethics (Cont.)
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.
228
Software Code of Ethics (Cont.)
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.
229
Software Code of Ethics (Cont.)
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.
230
Software Code of Ethics (Cont.)
In accordance with that commitment, software engineers shall adhere to the following Code of Ethics and Professional Practice.
231
Software Code of Ethics (Cont.)
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.
232
Software Code of Ethics (Cont.)
The Principles identify the ethically responsible relationships in which individuals, groups, and organizations participate and the primary obligations within these relationships.
233
Software Code of Ethics (Cont.)
The Clauses of each Principle are illustrations of some of the obligations included in these relationships.
234
Software Code of Ethics (Cont.)
These obligations are founded in the software engineer’s humanity, in special care owed to people affected by the work of software engineers, and in the unique elements of the practice of soft-ware engineering.
235
Software Code of Ethics (Cont.)
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.
236
Software Code of Ethics (Cont.)
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.
237
Software Code of Ethics (Cont.)
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.
238
Software Code of Ethics (Cont.)
These situations require the software engineer to use ethical judgment to act in a manner that is most consistent with the spirit of the Code of Ethics and Professional Practice, given the circumstances.
239
Software Code of Ethics (Cont.)
Ethical tensions can best be addressed by thoughtful consideration of fundamental principles, rather than blind reliance on detailed regulations.
240
Software Code of Ethics (Cont.)
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.
241
Software Code of Ethics (Cont.) - to analyze how the least empowered will be affected by their decisions.
- to consider whether their acts would be judged worthy of the ideal professional working as a software engineer.
242
Software Code of Ethics (Cont.)
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.
243
Software Code of Ethics (Cont.)
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.
244
Software Code of Ethics (Cont.)
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.
245
Software Code of Ethics (Cont.)
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.
246
Software Code of Ethics (Cont.) Principles 1) Principle 1: Public.
2) Principle 2: Client and employer.
3) Principle 3: Product.
4) Principle 4: Judgment.
247
Software Code of Ethics (Cont.) 5) Principle 5: Management.
6) Principle 6: Profession.
7) Principle 7: Colleagues.
8) Principle 8: Self.
248
1) 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.02. Moderate: * the interests of the software engineer. * the employer.
* the client.
* the users with the public good.
249
Principle 1: Public (Cont.) - 1.03. Approve software only if they have a well-founded belief that it is * safe.
* meets specifications.
* passes appropriate tests.
* does not diminish quality of life, diminish privacy, or harm the environment.
250
Principle 1: Public (Cont.) - 1.04. 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.
251
Principle 1: Public (Cont.) - 1.05. Cooperate in efforts to address matters of grave public concern caused by software, its installation, maintenance, support, or documentation.
- 1.06. Be fair and avoid deception in all statements, particularly public ones, concerning software or related documents, methods, and tools.
252
Principle 1: Public (Cont.) - 1.07. Consider issues of physical disabilities, allocation of resources, economic disadvantage, and other factors that can diminish access to the benefits of software.
- 1.08. Be encouraged to volunteer professional skills to good causes and to contribute to public education concerning the discipline.
253
2) 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.
254
Client and employer (Cont.)
In particular, software engineers shall, as appropriate: - 2.01. Provide service in their areas of competence, being honest and forthright about any limitations of their experience and education.
- 2.02. Not knowingly use software that is obtained or retained either illegally or unethically.
255
Client and employer (Cont.) - 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.
256
Client and employer (Cont.) - 2.05. Keep private any confidential information gained in their professional work, where such confidentiality is consistent with the public interest and consistent with the law.
257
Client and employer (Cont.) - 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.
258
Client and employer (Cont.) - 2.07. Identify, document, and report significant issues of social concern, of which they are aware, in software or related documents, to the employer or the client.
- 2.08. Accept no outside work detrimental to the work they perform for their primary employer.
259
Client and employer (Cont.) - 2.09. 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.
260
3) Principle 3: Product.
Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.
261
Principle 3: Product ( Cont.)
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.
262
Principle 3: Product ( Cont.) - 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.
263
Principle 3: Product ( Cont.) - 3.04. Ensure that they are qualified for any project on which they work or propose to work, by an appropriate combination of education, training, and experience.
- 3.05. Ensure that an appropriate method is used for any project on which they work or propose to work.
264
Principle 3: Product ( Cont.) - 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.
265
Principle 3: Product ( Cont.) - 3.08. Ensure that specifications for software on which they work have been well documented, satisfy the user’s requirements, and have the appropriate approvals.
266
Principle 3: Product ( Cont.) - 3.09. 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.
267
Principle 3: Product ( Cont.) - 3.10. Ensure adequate testing, debugging, and review of software and related documents on which they work.
- 3.11. Ensure adequate documentation, including significant problems discovered and solutions adopted, for any project on which they work.
268
Principle 3: Product ( Cont.) - 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.
269
Principle 3: Product ( Cont.) - 3.14. Maintain the integrity of data, being sensitive to outdated or flawed occurrences.
- 3.15. Treat all forms of software maintenance with the same professionalism as new development.
270
4) 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.
271
Principle 4: Judgment (Cont.) - 4.02. Only endorse documents either prepared under their supervision or within their areas of competence and with which they are in agreement.
- 4.03. Maintain professional objectivity with respect to any software or related documents they are asked to evaluate.
272
Principle 4: Judgment (Cont.) - 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.
273
Principle 4: Judgment (Cont.) - 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.
274
5) Principle 5: Management.
Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance.
275
Principle 5: Management (Cont.)
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.
276
Principle 5: Management (Cont.) - 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.
277
Principle 5: Management (Cont.) - 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.
278
Principle 5: Management (Cont.) - 5.05. 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.
279
Principle 5: Management (Cont.) - 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.
280
Principle 5: Management (Cont.) - 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.
281
Principle 5: Management (Cont.) - 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.
282
6) 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.
283
6) Principle 6: Profession.
- 6.02. Promote public knowledge of software engineering.
- 6.03. Extend software engineering knowledge by appropriate participation in professional organizations, meetings, and publications.
284
6) Principle 6: Profession.
- 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.
285
6) Principle 6: Profession.
- 6.06. Obey all laws governing their work, unless, in exceptional circumstances, such compliance is inconsistent with the public interest.
286
6) Principle 6: Profession.
- 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.
287
6) Principle 6: Profession.
- 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.
288
6) Principle 6: Profession.
- 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.
289
6) Principle 6: Profession.
- 6.12. Express concerns to the people involved when significant violations of this Code are detected unless this is impossible, counterproductive, or dangerous.
290
6) Principle 6: Profession.
- 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, counterproductive, or dangerous.
291
7) 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.
292
Principle 7: Colleagues (Cont.) - 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.
293
Principle 7: Colleagues (Cont.) - 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.
294
Principle 7: Colleagues (Cont.) - 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.
295
Principle 7: Colleagues (Cont.) - 7.08. In situations outside of their own areas of competence, call upon the opinions of other professionals who have competence in those areas.
296
8) 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.
297
Principle 8: Self (cont.)
In particular, software engineers shall continually endeavor to: - 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.
298
Principle 8: Self (cont.) - 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.
299
Principle 8: Self (cont.) - 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.
300
Principle 8: Self (cont.) - 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.
301
Principle 8: Self (cont.) - 8.09. Recognize that personal violations of this Code are inconsistent with being a professional software engineer.
302
7. Sample Cases of IT Ethics.
7.1 Former Employee of Viewsonic Pleaded Guilty to Hacking into Company’s Computer, Destroying Data. 7.2 Federal Judge Sentences Ex Official of Local Internet Service Provider to Prison for Computer Attack. 7.3 Spyware in Popular Webs.
303
Sample Cases of IT Ethics (Cont.) 7.1 Former Employee of Viewsonic Pleads Guilty to Hacking into Company’s Computer, Destroying Data.
According to court documents, on April 14, 2002.
Approximately two weeks after Andrew Garcia (39 years old) was terminated.
304
Hacking into Viewsonic (Cont.)
Garcia accessed Viewsonic’s computer system and deleted critical files on one of the servers that he had maintained while he was employed by the company.
The loss of these files rendered the server inoperative, and Viewsonic’s Taiwan office was unable to access important data for several days.
305
Hacking into Viewsonic (Cont.)
Garcia pleaded guilty before United States District Judge John F. Walter, who is scheduled to sentence the defendant on January 12, 2004. Garcia faces a maximum possible sentence of five years in federal prison and a fine of $250,000.
306
Sample Cases of IT Ethics (Cont.) 7.2 Federal Judge Sentences Ex-Official of Local Internet Service Provider to Prison for Computer Attack.
According to court documents, on January 2003.
307
ISP (Cont.)
David N. Kelley, US Attorney for the Southern District of New York, announced that Peter Borghard, a former network administrator of a Manhattan-based internet service provider called Netline Services, Inc., stemming from Borghard’s electronic attack on Netline’s computer system in January 2003.
308
ISP (Cont.)
Borghard’s attack on Netline destroyed portions of Netline’s computer hardware and temporarily deprived its customers of internet service, causing Netline to suffer approximately $118,000 in losses .
309
ISP (Cont.)
Borghard was sentenced in Manhattan federal court by United States District Judge George B. Daniels to 5 months in prison and 5 months of home confinement, and ordered to pay $118,030 in restitution.
310
Sample Cases of IT Ethics (Cont.) 7.3 Spyware in Popular Webs.
Loading songs or games via some popular webs on the Internet, the users might get infected by spyware.
Spyware may also be included when downloading popular software.
311
8. Intellectual Property.
Intellectual Property includes: (1) Copyright.
(2) Patent.
(3) Trade Secret.
(4) Trademark.
(5) Estimated US Loss.
312
Intellectual Property (Cont.) (1) Copyright.
For creative and artistic works (Books, Movies, Music, Paintings, Photographs, and Software).
For Thailand, the copyright protection include literacy work and software.
Protected for 50 years.
313
Intellectual Property (Cont.) (2) Patent.
New, useful, and non-obvious invention.
In Thailand, protection for patent - New invention 20 years.
- New product design 10 years.
There is also mini-patent with 6 years protection, extendable for 2 years with maximum of 2 extensions, totaling 10 years of protection.
314
Intellectual Property (Cont.) (3) Trade Secret.
Secret, non-public information concerning: - Commercial practices - Proprietary knowledge of business Etc.
No limit on the number of years of protection.
315
Intellectual Property (Cont.) (4) Trademark.
Distinctive sign or mark used for brand of products or services, to distinguish the product or service of different businesses.
316
Intellectual Property (Cont.) (5) Estimated US Loss.
10 years protection.
Extendable 10 years at a time, as many time as the owner wishes.
317
Estimates US Loss (Cont.)
International Intellectual Property Alliance issued its report in February 2007 about estimated trade losses due to copyright piracy in Thailand for the year 2006: - Records and Music 20.7 million US$ - Business Software 164 million US$ - Books 35 million US$ Total 219.7 million US$ (About 7,294 million bahts)
318
9. Concluding Remarks.
Comparing to other fields of study, Information Technology is: - very much different.
- changing very fast.
- requiring new understanding.
- requiring new laws.
Etc.
319
Concluding Remarks (Cont.)
Special care and consideration must be given to Information Technology morality and ethics.
All parties concerned must cooperate for the benefits of themselves, their countries, and the world.
320