Achieving balance in software engineering curricula

Achieving balance is an issue that faces all curriculum designers. The complexity of the software process demands a pluralistic approach to systems development. This pluralism must also be reflected in the education and training of future software engineers. How can we integrate the diverse views into a unified curriculum framework? How can we cover all topics that are deemed essential for the discipline. We must balance specialised software engineering topics with fundamental topics in computer science and we must also balance the variety of software engineering topics amongst themselves within the relatively short three-year undergraduate curriculum. Very often, what is left out is just as important as what is left in. The paper describes the process and outcomes of a recent attempt at Southern Cross University to develop a balanced software engineering course. Comparisons were made between this implementation and the ACM/IEEE model curriculum and other related efforts.

[1]  Undergraduate, graduate and professional education in software engineering in the '90's: a case study , 1994, Proceedings Software Education Conference (SRIG-ET'94).

[2]  Norman E. Gibbs,et al.  The SEI education program: the challenge of teaching future software engineers , 1989, CACM.

[3]  O. S. Plail,et al.  Education and training on the job , 1977 .

[4]  R. Pressman Software Engineering: a Practioner''s approach , 1987 .

[5]  Gary A. Ford The SEI undergraduate curriculum in software engineering , 1991, SIGCSE '91.

[6]  Rocky L. Stewart,et al.  Biosphere 2 nerve system , 1991, CACM.

[7]  Roger S. Pressman,et al.  Software engineering (3rd ed.): a practitioner's approach , 1992 .

[8]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[9]  H. Taba,et al.  Curriculum development; theory and practice , 1962 .

[10]  Pentti Kerola Knowledge about human information processing and learning styles in the education of systems architects , 1990 .

[11]  Paul T. Tymann,et al.  Developing an undergraduate software engineering program in a liberal arts college , 1994, SIGCSE '94.

[12]  Jr. Albert F. Case Information Systems Development: Principles of Computer-Aided Software Engineering , 1986 .

[13]  Ifip Tc,et al.  Methodologies of training data processing professionals and advanced end-users : proceedings of the IFIP TC 3/WG 3.4 Working Conference on Methodologies of Training Data Processing Professionals and Advanced End-users, Helsinki, Finland, 31 July-4 August 1989 , 1990 .

[14]  Peter J. Denning,et al.  Computing as a discipline , 1989, Computer.

[15]  Monica Snell Analysts Predict $3.79 Billion Market for Visual Development Tools by 1999 , 1995, Computer.

[16]  George M. Mohay,et al.  Core software engineering subjects: a case study ('86-'94) , 1994, Proceedings Software Education Conference (SRIG-ET'94).

[17]  Sue A. Conger,et al.  The new software engineering , 1993, notThenot Wadsworth series in management information series.

[18]  Bertrand Meyer,et al.  Object-Oriented Software Construction, 2nd Edition , 1997 .

[19]  James Martin,et al.  Fourth generation languages , 1985 .

[20]  John R. Pugh,et al.  Software engineering (2nd ed.): a programming approach , 1992 .

[21]  Douglas Bell Software Engineering: A Programming Approach , 1987 .

[22]  A. J. Hurst,et al.  Breadth versus depth in software engineering education , 1994, Proceedings Software Education Conference (SRIG-ET'94).

[23]  C. Finkelstein An Introduction to Information Engineering: From Strategic Planning to Information Systems , 1989 .

[24]  John Wordsworth Software development with Z - a practical approach to formal methods in software engineering , 1992, International computer science series.

[25]  Watts S. Humphrey Software and the factory paradigm , 1991, Softw. Eng. J..

[26]  Allen B. Tucker,et al.  Computing Curricula 1991 , 1991, CACM.

[27]  Capers Jones Legal Status of Software Engineering , 1995, Computer.

[28]  簡聰富,et al.  物件導向軟體之架構(Object-Oriented Software Construction)探討 , 1989 .

[29]  Barry W. Boehm,et al.  Software Risk Management , 1989, ESEC.