Abstract
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.
Similar content being viewed by others
References
American Society for Quality (ASQ) (1995), “Certified Quality Engineer,” Certification Brochure, Milwaukee, WI.
Aylor, J., M. Barbacci, F. Buckley, L. Druffel, W. Royce, N. Schneidewind, and S. Zweben (1993), “Report to the Board of Governors of the IEEE Society from the Steering Committee for the Establishment of Software Engineering as a Profession.”
Barbacci, M. (1994), “Panel Presents First Four Recommendations Aimed at Establishing Software Engineering as a Profession,” IEEE Computer 27, 2, 80–81.
Barbacci, M., F. Buckley, E. Chikofsky, L. Druffel, W. Royce, N. Schneidewind, and S. Zweben (1994), “Report to the Board of Governors of the IEEE Computer Society from the Steering Committee for the Establishment of Software Engineering as a Profession.”
Davis, M. (1995), “Defining ‘Engineer:’ How to do it and Why it Matters,” Journal of Engineering Education 85, 2, 97–101.
Douglas, P. and T. Cocchi (1997), “Report on Analyses of Pilot Software Engineer Survey Data,” Task Force on Body of SE Knowledge of the Steering Committee for the Establishment of Software Engineering as a Profession.
Ford, G. and N. Gibbs (1996), “A Mature Profession of Software Engineering,” Technical Report CMU/SEI-96-TR-004, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
Frailey, D.J. (1996), “Issues in Licensing of Software Engineers as Professionals,” Briefing on the Dallas/Fort Worth SPIN Meeting.
Gillespie, G. (1997), “ABET Asks the IEEE to Look at Software Engineering Accreditation,” IEEE – The Institute 21, 7, 1.
Learning Tree International (LT) (1996), “Professional Certification.”
Mead, N.R. (1997), “Issues in Licensing and Certification of Software Engineers,” In Proceedings of the 10th Conference on Software Engineering Education and Training, IEEE Computer Society Press, Los Alamitos, CA, pp. 150–160.
National Software Council (NSC) Forum (1996), “Should US Software Engineers be Licensed?,” In Proceedings of the National Software Council Forum, National Software Council, Burlington, MA.
Parnas, D.L. (1997a), “Teaching for Change,” In Proceedings of the 10th Conference on Software Engineering Education and Training, IEEE Computer Society Press, Los Alamitos, CA, pp. 174–175.
Parnas, D.L. (1997b), “Software Engineering: An Unconsummated Marriage,” Communications of the ACM 40, 9, 128.
Shaw, M. (1996), “An Initial Taxonomy for Certification,” Working Paper, Carnegie Mellon University, Pittsburgh, PA.
Texas Board of Professional Engineers (TBPE) (1998), “Board Establishes Software Engineering Discipline,” http://www.main.org/peboard/.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Mead, N.R., Turner, A.J. Current accreditation, certification, and licensure activities related to software engineering. Annals of Software Engineering 6, 167–180 (1998). https://doi.org/10.1023/A:1018973818744
Issue Date:
DOI: https://doi.org/10.1023/A:1018973818744