In this paper, the author explains the need for, and importance of, certification based on generally accepted software engineering practices (GASEP) for software professionals. Software professionals usually gain competency in their fields by learning on the job, and from senior colleagues who act as mentors. This informal learning is neither scientific nor systematic, and the quality of the knowledge gained will vary depending on factors like the mentor’s competence, job environment, and so on. It is also a costly way of gaining knowledge, since novices learn by trial and error, thus wasting resources, and could make mistakes, leading to cost and time overruns, and even project failures.

The author argues that a GASEP certification is needed for clients, as well as the general public, to trust software professionals and their work. The existing certifications, like the Capability Maturity Model (CMM), International Organization for Standardization (ISO), and so on, do not directly assess competency and excellence in individuals, since they are given to organizations.

According to the author, the software industry has seen enough project failures to recognize the need for GASEP proficiency among its members. This can be done only by adopting an approach similar to that in other fields, like accountancy, engineering, and medicine, where new entrants are tested and certified before they can start practicing. The success and popularity of certification by companies like Novell and Microsoft is an indication of the need for a unified GASEP certification.

The author acknowledges efforts like the Institute of Electrical and Electronics Engineers’ Certified Software Development Professional (CSDP) program, which is based on the draft version of the software engineering body of knowledge (SWEBOK), as a step in the right direction. The SWEBOK can be used as a starting point, but should be made more comprehensive and detailed before using it for GASEP certification.

The software community should form a Software Engineering Standards Board (SESB) to officially endorse the GASEP certification, and should periodically review the contents to ensure that they are current and reflect the state of the art. Instituting such a certification would benefit practitioners, clients, and the industry.

This article sheds light on the most important cause of software project failures, and offers a time-tested solution: get the job done by qualified people. This is an essential read for the decision makers in standards bodies, user groups, and organizations, and for anybody interested in the betterment of the software profession and industry.