Got 30 seconds to spare? Make a no cost food donation to the United Nation
s World Food Programme

CIS3090 - Social and Professional Issues in Computing

Lectures 9 & 10 - Regulation of Professions

Christopher Staff, Department of Computer Science and AI

References: Computer Ethics, Chapter 3
Legislation: Education Act

Accountancy Profession Act

Medical and Kindred Professions Ordinance

Engineering Profession Act
Codes of Ethics: Computer Society of Malta

Chamber of Professional Engineers, Malta

Association for Computing Machinery

Institute for Electronics and Elecrical Engineers

IEEE-CS/ACM Software Engineering Code of Ethics and Professional Practice

British Computer Society
Other:
Department of Computer Science and AI Position Statement on the Warranting of IT Professionals

Introduction

Some professions are strongly differentiated. What mechanisms are there for ensuring that members of the profession can perform actions which would be illegal if performed by others? What mechanisms are there for ensuring that professionals do not abuse their power? A profession can have a Code of Ethics, but just because a group of people get together and decide that they have a collective right to perform some action is not sufficient. The State must recognise the organisation, and must legislate its activities.

Codes of Ethics

A Code of Ethics is a public declaration of the aims, objectives, and standards that the public can expect from the organisation, and the members belonging to the organisation. The Code of Ethics is also a reminder to the organisation's members of the standards and good practices that they should maintain.

One of the earliest examples of a Code of Ethics is the Hippocratic Oath, although medical ethics has evolved beyond the Hippocratic Oath to cater for changes in attitude to what can and cannot be done "for the good of society".

Many organisations have a Code of Ethics which is not enforceable at law. This means that following such a code of ethics is voluntary, and the worst that may happen to offenders is their membership of the organisation is terminated. In organisations that are recognised by the State, there may be legislation through which violations of the Code of Ethics may result in at least loss of the right to practice the profession, and at most, a fine and/or jail sentence together with the revocation of the warrant or license.

A code of ethics is established as a first attempt to make a claim about the professionalism of a group of people who come together with a common goal. Unless the members of the group uphold the ethics of the group, then society will be unwilling to accept them. However, do not be fooled into believing that everything that has a Code of Ethics is necessarily a profession! The Ten Commandments in Christianity are about a way of life, and the way that practicing Christians should behave with respect to each other. The Mafia also have a Code of Honour, which is also about a way of life, and the way that practicing Mafiosi should behave with respect to each other. A Company can also have a Code of Ethics, usually called a Customer Charter (and Governments have Citizens Charters). These are effectively a form of social contract about the type of service that a client or customer can expect, but, importantly, the rights that receivers of these services can expect to have if the organisation fails to deliver.

Codes of Ethics, Charters, etc., are only as good as the members who uphold them. It is pointless declaring that "the client's interests are always put first" if it is patently untrue and the client has no remedy to acquire an improved service. A Code of Ethics is unlikely to provide remedies to every ethically questionable situation that arises, but there should be a Committee or a Commission which is able to sit and assess claims of unethical behaviour, and to be prepared to update the Code of Ethics. In particular, breaches of the Code of Ethics should be viewed as serious misconduct, and at the very least should be investigated by a Disciplinary Board.

Comparison of Codes of Ethics in Computing and Related Fields

This is a brief comparison of the Codes of Ethics of the following organisations:

British Computer Society (BCS), Computer Society of Malta (CSM), Association for Computing Machinery (ACM), Institute for Electrical and Electronics Engineers (IEEE), IEEE-CS/ACM Software Engineering Code of Ethics and Professional Practice, Chamber of Professional Engineers (Malta). The Chamber of Professional Engineers (Malta) is provided merely because BCS and IEEE-CS are affiliated to professional engineering bodies, and the CSM is affiliated to the BCS (and, consequently, to an engineering body).

In general, a code of ethics covers the relationship that a member has with society, with clients, with employers, and with other members of the profession. The code will also specify general principles, and may include a section on discipline.


BCS IEEE CPE CSM ACM SE
Act in the public interest x x x x x x
Act in the best interest of the client/employer x - x x x x
Use best possible standards x ? x x ?* x
Maintain integrity and independence in professional judgement x x x x x x
Managers and leaders to subscribe to and promote Code of Ethics - - x - x x
Advance integrity and reputation of profession x x x x x x
Be fair to and supportive of colleagues x x x x - x
Participate in lifelong learning and promote Code of Ethics x x x x x x
Avoid harm to others - x x x x x
Honour property rights x x x x x x
Maintain confidentiality x x x x x x
Improve public understanding of discipline and its consequences x x - x x x
Breaches of the Code will be disciplined x - x - x -
Care for the environment - - x x - x
No soliciting for work - - x - - -
Do only what trained to do x x x x - x
Period of apprenticeship - - x - - x
Understand all legislation relevant to profession x - x x - x
Disclose promptly if employer/client insists on dangerous action x x x x - x

Key:
BCS = British Computer Society
IEEE = Institute for Electrical and Electronics Engineers
CPE = Chamber of Professional Engineers (Malta)
CSM = Computer Society of Malta
ACM = Association for Computing Machinery
SE = IEEE-CS/ACM Software Engineering Code of Ethics and Professional Practice

One noteworthy point to make about the Computer Society of Malta Code of Conduct (Ethics) is the statement that members must avoid any activity incompatible with professional status. IT and none of its disciplines are yet recognised as having a Professional Status in Malta, but including such statements in Codes of Ethics can have the undesirable effect of misleading the public, employers, and clients - which is itself an action in breach of the Code of Ethics!

Certification and Warranting

What's the difference between certification and warranting? A certificate is granted to an individual who can demonstrate a certain level of proficiency in a testable topic, or who meets certain criteria. For instance, a university degree is a certificate which indicates that the certificate holder has satisfied examiners over a period of time that a certain body of knowledge has been acquired, assimilated, and can be applied. An 'O'-level is also a certificate, and also demonstrates that a certain proficiency in the subject has been obtained. It is normally possible to compare the likely aptitudes of the certificate holder. The holder of an 'O'-level in Italian is not likely to be a fluent speaker, but somebody with an undergraduate degree in Italian is likely to be fluent. On the other hand, a certificate may be awarded simply because the candidate has satisfied some criteria. An example is a "certificate of attendance".

Although certificates are a convenient way for potential employers to determine that an interviewee really has the skills that are claimed, not having a certificate is not sufficient proof that the interviewee does not have the required skills. It remains to be seen whether a company can discriminate against someone on the basis that they do not have a certificate in some technical area (note that this does not apply to formal educational qualifications, like 'O'- and 'A'-levels and university degrees, because these are recognised by the State). Certainly, the failure to have a (non-educational) certificate should not be used to block access to a job, unless there is legislation to support this.

A warrant, on the other hand, can be obtained only if the applicant is able to satisfy certain criteria. These criteria may be related to educational and non-educational qualifications and/or experience. The warrant can be used to block access to a job (or a profession), because at law it will be illegal to hire personnel to fulfil certain job functions, unless they are warranted to do so, and also illegal to perform those job functions except by a warrant holder. A warrant can create a strongly differentiated profession, but certificates, on their own, cannot do so.

The IEEE-CS Certified Software Development Professional

The IEEE-CS and ACM jointly produced the Software Engineering Code of Ethics and Professional Practice. However, ACM and IEEE-CS disagree about certifying Software Engineers. IEEE-CS offers a certification process, whereas ACM states that the "ACM Council has completed its study and deliberation on the question of whether software engineers should be licensed. Following the work of a Professional Licensing and Software Engineering Advisory Panel and task forces on Body of Knowledge Issues and Safety Critical Software Issues, ACM Council has decided that ACM should withdraw from efforts that promote licensing of software engineers as professional engineers." (ACM: Computing and Public Policy). The primary reason for this is that most efforts to license Software Engineering have occurred within a general framework of professional engineering, and that to continue in this vein would require software engineers to be examined over subjects that they are not necessarily exposed to, nor are likely to need to practice competently; that licensing software engineering will have no effect on the safety of software produced; knowledge of software engineering for safety-critical systems is excluded from the attempts to license Software Engineering; and, it is not possible to certify Software Engineering indiscriminately across all industries (Summary of the ACM Position on Software Engineering as a Licensed Engineering Profession, July 2000). Further, ACM concludes that improperly conceived licensing would have a "significant chance of reducing the public's understanding of, confidence in, and assurances about key properties of software".

We will shortly consider the ethics of a discipline which may not be licensable, especially as computer software plays increasingly important roles in controlling everyday devices. However, we will first look at the requirements needed to become an IEEE-CS Certified Software Development Professional. Certification requires passing an exam, but before one can even apply for the exam, a candidate must have a university degree and a proven track record of 9,000 hours of experience in at least 6 of the following 11 fields. (Assuming you work in Software Engineering for 40 hours per week, 50 weeks a year, it will take 4.5 years to satisfy the 9,000 hour requirement):

Once the prerequisites have been satisfied, a candidate may apply to sit for the exam. The exam itself consists of 180 multiple-choice questions. Upon successful completion of the exam, the candidate will be certified as a Certified Software Engineering Professional. The Certification is valid for 3 years. During this time, already certified professionals must acquire at least 30 "Professional Development Units" and pay a recertification fee. Professional Development Units are acquired by working in Software Engineering, publishing books and papers, self-study, active involvement in professional organisations, and involvement in the education and training of others (all in areas related to Software Engineering).

Attaining certification in software engineering is therefore an arduous process. Not only must professional software engineers be university graduates, but they must have considerable experience in software engineering (initially obtained during the practical equivalence of an apprenticeship), and must remain up-to-date on software engineering practices and contribute to the body of knowledge of software engineering to remain certified. However, certifying an individual's proficiency in a particular discipline must not be confused with limiting access to the profession by introducing a warrant or a license to practice. We must also not forget that software engineering is only a small part of computing. Regulating a sub-discipline of computing as though it were an Engineering Profession will create problems in the future as software engineering itself, and other disciplines of computing, mature.

What is the future of computing as a profession if it is not possible to warrant it?

Arguments against warranting computing (or its sub-disciplines, such as software engineering) include the recognition that the discipline is not mature enough, and that it would give society improper assurances regarding the extent to which computing products can be certified (e.g., ACM Panel on Professional Licensing in Software Engineering: Report to Council (1999). It is hard to prove arbitrary programs correct, so the most that can be certified is that "best practices" have been used to design and implement programs. However, whereas engineering principles are well established, this is not the case in computing in general. Most engineering standards are subjected to many years of testing before they can be utilised by professional engineers. Technology in computing still undergoes revolutions far too rapidly for any methodology to be properly evaluated before it is released for use. Many software engineering methodologies, for instance, are not applicable to all programming paradigms. For software engineers to be able to certify products, well-known and well-tested approaches only could be certified - the results, and especially the interactions between different components, would otherwise be uncertifiable. However, new technical solutions are released into the computing world with increasing frequency, promising greater benefits to industry. The industrial take-up of these solutions, to replace existing solutions, would need to slow down to allow the standards to be developed and evaluated before releasing them for general use. A trivially equivalent situation in computing would be for a "professional" to know how certain pre-designed, implemented, and possibly already compiled, modules function, and how they can be installed safely into a computational environment. However, most IT practitioners, at some stage of their careers, are involved in the analysis, design, implementation, and testing of complex systems, which implies team responsibility for the construction of such systems, rather than the responsibility of an individual (e.g., in law, engineering, auditing, etc.).

Regulation of the Professions

A Code of Ethics principally describes the "honourable" practices of the profession. Essentially, conforming to, or complying with, the Code is frequently an individual decision. In some professions, compliance with the Code is an obligation because failure could mean loss of the right to practice the profession. However, this is enforcible only if the State i) recognises the profession, and ii) provides suitable legislation.

A warrant or a license to practice a profession is granted to indicate to the general public, employers and clients that the State, through a professional organisation, recognises the competence of the warrant holder to act "professionally". This means that the warrant holder has at least the knowledge and skill to practice the profession and he or she will also behave professionally while practicing. The Code of Ethics is prepared by a professional organisation to guide its members. A Code of Ethics cannot provide guidelines for all types of activity, so members of a profession must be able to determine whether an action is likely to be ethical or not. In cases of doubt, the professional is expected to seek adive from a properly constituted Board within their organisation. Failure to provide this first line of support to members should cast doubt on the intentions of the professional organisation in the first place. Is it really interested in protecting the public, and ensuring that clients and employers are treated fairly? Or is the profession's main concern being seen to be interested?

The most relevant regulated profession in Malta is the Engineering Profession. This is regulated by the Engineering Profession Act. The State, through the Act, recognises the Engineering Board as the Designated Authority for the Profession, and recognises the Chamber of Professional Engineers as an association of warranted engineers. As long as as least two-thirds of all warranted engineers are members of the Chamber of Professional Engineers, the Chamber's Code of Ethics will be used to regulate the professional behaviour of warrant holders, in addition to the legistation in the Engineering Profession Act. Effectively, this means that the code of ethics will automatically become law as long as at least two-thirds of warranted engineers are members of the Chamber of Professional Engineers. The Act also provides that the Minister (responsible for infrastructure, and the Engineering Board itself) can amend the code of ethics or even withdraw recognition of it at any time. This apparent lack of complete autonomy, and the lack of a legal requirement for all warranted engineers to belong to the professional organisation seem to be in conflict with the basics of Professional Ethics, and the recognition of professions.

The Engineering Board is responsible for, among other things, considering applications for warrants; considering accusations of professional misconduct; withdrawing or suspending warrants; and, advising the Minister.

The legislation provides for the constitution of the Engineering Board and specifies its powers; regulates how "partnerships of engineers" may be formed and practice; that warranted engineers must insure themselves against indemnity; makes payments to secure a contract illegal; allows the warrant to be withdrawn if the holder is convicted of certain crimes, or professional misconduct; the penalties applicable if a warrant is procured illegally or if an unauthorised person impersonates an engineer.

The Act applies specifically to the fields of Electrical and Mechanical Engineering, although the Minister (or the Engineering Board) may extend its applicability to other fields of the Engineering profession.


For further information e-mail cstaff@cs.um.edu.mt

Date last amended: Monday, 1st December, 2003