Ethics in Software Engineering

When it comes to every job, there always are work ethics, and software engineering is not an exception. This is the short version.

For example, the Association for Computer Machinery (ACM) has their established code of ethics that every Software Engineer must follow:

Software engineers shall commit themselves to making the analysis, specification, design, development, testing and maintenance of software a beneficial and respected profession. 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.

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.

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.

5. MANAGEMENT – Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance.

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.

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.

 

Software engineering is a relatively young practice and compared with other engineering disciplines, its culture of professionalism is still developing. This is reinforced by the fact that most engineering ethics textbooks focus primarily on ethical issues faced by civil, mechanical or elecrical engineers. But software engineers build lines of code, not cars, rockets

bridges full of vulnerable human beings. Where is the comparison here? Well, one answer might already have occurred to you. How many cars or rockets are made today that do not depend upon critical software for their safe operation? How many bridges are built today without the use of sophisticated computer programs to calculate expected load, geophysical strain, material strength and design resilience? A failure of these critical software systems can result in death or grievous injury just as easily as a missing bolt or a poorly designed gas tank. This by itself is more than enough reason for software engineers to take seriously the ethics of their professional lives.