Software engineering (SE) is maturing as a discipline and profession, but three decades after the first NATO Conference on Software Engineering, it is still not regarded by some to be a legitimate, respectable engineering profession. In 1995, Gary Ford and Norman Gibbs of the Software Engineering Institute evaluated what it means for a profession to be mature and how SE was doing. Their study found that, relative to other fields and engineering branches, most elements that make SE a profession were quite immature. Five years later, SE has had countless practitioners (a.k.a. software developers), thousands of published articles, dozens of conferences and workshops, and a respectable number of education and training programs. But despite all this progress, SE, while recognizable, is still immature-- as evidenced by the significant gap among vision, education, and standard practice. The reasons are legion, but they boil down to one simple fact: The field is still young. The authors present their assessment of SE immaturity in this article. Although they believe time will eventually mature SE, a calculated push can accelerate the maturation process. By "push," they mean defining, accrediting, and evaluating new curricula that stress CS and SE fundamentals.
1. G. Ford, and N.E. Gibbs, "A Mature Profession of Software Engineering," Tech. Report CMU/SEI-96-TR-004, Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, 1996.
2. P. Bourque, et al., "The Guide to the Software Engineering Body of Knowledge," IEEE Software, Nov./Dec. 1999, pp. 35-44.
3. D. Gotterbarn, "How the New Software Engineering Code of Ethics Affects You," IEEE Software, Nov./Dec. 1999, pp. 58-64.
4. G.L. Engel, "Program Criteria for Software Engineering Accreditation Programs," IEEE Software, Nov./Dec. 1999, pp. 31-34.
5. G. Pour, and A. Hambaba, "An Undergraduate Software and Information Engineering Curriculum under Development
at San Jose State University," Proc. Frontiers in Education (FIE) Conf., IEEE CS Press, Los Alamitos, Calif., 1999, CD-ROM.
6. D.L. Parnas, "Software Engineering Programs Are Not Computer Science Programs," IEEE Software, Nov./Dec. 1999, pp. 19-30.
7. M.J. Lutz, and J.F. Naveda, "The Road Less Traveled: A Baccalaureate Degree in Software Engineering," Proc. 28th SIGCSE Technical Symp. Computer Science Eduation, ACM Press, New York, 1997, pp. 287-291.
8. M. Jackson, "Will There Ever Be Software Engineering," IEEE Software, Jan./Feb. 1998, pp. 36-39.
9. A. Wasserman, "Software Processes and Software Professionals in the 21st Century," Cutter IT J., Sept. 1999, pp. 17-23.
10. M.L. Griss, "Letter from the SIGSOFT Executive Committee," ACM SIGSOFT Software Eng. Notes, Sept. 1998, pp. 1-2.
11. J.R. Speed, "What Do You Mean I Can't Call Myself a Software Engineer?" IEEE Software, Nov./Dec. 1999, pp. 45-50.
12. D.J. Bagert, "Texas Board Votes to License Software Engineers," ACM SIGSOFT Software Eng. Notes, Sept. 1998, p. 7.