Skip to main content

Code of Ethics and Professional Practice

This code of ethics was developed by the IEEE-CS/ACM joint task force on Software Engineering Ethics and Professional Practices . It was jointly approved by the ACM and the IEEE-CS as the standard for teaching and practicing software engineering.

This summary version of the code of ethics summarizes aspirations at a high level of abstraction. The clauses included in the full version of this code give examples and details of how these aspirations change the way we act as software engineering professionals. Without the aspirations, the details can become legalistic and tedious; without the details, the aspirations can become high sounding but empty; together, the aspirations and the details form a cohesive code.

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:

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.

Comments

Popular posts from this blog

The High Cost of Low Software Estimates

Estimating too low on a software development project can destroy your budget and ruin your project schedule. Here's the reason why. I have been developing software for more than twenty years, and I have experienced first-hand the consequences of estimating too low (and estimating too high). Estimates at the beginning of a software project are rarely accurate, given the team's limited knowledge of the project. More often than not, users don't yet know all of their own requirements for the system to be developed, and developers don't yet know everything about the domain in which the solution will operate. Building software is a process of continuous improvement, and a well-run project attacks the areas of highest variability first in order to reduce uncertainties as quickly as possible. Ideally, your estimate for a software project should be allowed to evolve along with the software itself. And remember: the potential for an exponential overrun on cost and/or sche...

How to Download Messages from an IMAP Server Using C#

This article provides a solution to automate the download of email messages (including embedded files and attachments) from an IMAP server using C# and MailBee.NET. Download Source Code - 10 KB Introduction This week I completed an interesting year-end assignment for another software company, InSite Systems . For the purposes of safe-keeping and due diligence, copies of all email messages sent from (and received by) team members had to be downloaded from the company's IMAP mail server and stored on an offline file system. I created a simple C# console application to do the job, and I thought I'd share the source code with readers here. You will need an IMAP class library for this solution. I found a great set of components from a company called AfterLogic: MailBee.NET Objects The solution downloads only one folder for one user at a time, so if you want to automate the download of multiple folders and/or multiple users then you'll need to roll some additional...