The issues associated with the accreditation, certification, and licensure of software engineers are, or at least should be, of great concern to the software engineering community. Perhaps as a result of publicity about safety-critical software disasters in the news media, some state legislatures have considered regulating the practice of software engineering, and some professionals believe that accreditation, certification, and licensure are inevitable. Yet there is no agreed-upon body of knowledge for software engineering on which to base accreditation, certification, or licensure, which makes implementing them difficult at best. In addition, it is not clear that these processes and possible mechanisms to support them are well understood within the software engineering community. This paper surveys how these three processes are conducted in other professions, summarizes the processes as they currently exist for computing in general, identifies some issues that are involved in implementing the processes for software engineering, and suggests possible actions that can be taken by the software engineering profession. The implications of accreditation, certification, and licensure for education are also discussed.
[1]
Michael Davis,et al.
Defining “Engineer:” How To Do It and Why It Matters
,
1996
.
[2]
David Lorge Parnas.
Teaching For Change
,
1997,
Proceedings Tenth Conference on Software Engineering Education and Training.
[3]
Norman E. Gibbs,et al.
A Mature Profession of Software Engineering.
,
1996
.
[4]
David Lorge Parnas,et al.
Software engineering: an unconsummated marriage
,
1997,
CACM.
[5]
Mario Barbacci.
Panel Presents First Four Recommendations Aimed at Establisting Software Engineering as a Profession
,
1994,
Computer.
[6]
Mario Barbacci.
Four recommendations; one challenge
,
1994
.
[7]
Nancy R. Mead.
Issues in licensing and certification of software engineers
,
1997,
Proceedings Tenth Conference on Software Engineering Education and Training.