Undergraduate, graduate and professional education in software engineering in the '90's: a case study

The demands for graduate education in software engineering were clearly established in the late 1980's. Now, several years later, the practical imperative has emerged that information technology graduates are increasingly required in their first positions to work in large teams, to use new and quite complex tools and environments, and to be able to communicate effectively in their work environments. There is therefore a need for significant studies in software engineering at the undergraduate level. The paper describes recent developments in software engineering education at the Queensland University of Technology at undergraduate, postgraduate and professional levels and examines the alignment of the undergraduate and postgraduate curricula with those proposed by the ACM/IEEE-CS Joint Curriculum Task Force and the Software Engineering Institute at Carnegie-Mellon University

Core software engineering subjects: A case study ('86-'94)

The "software crisis" was first acknowledged in the mid 1960s. Some would claim that the software crisis is still with us. A recent issue of Scientific American ran a story on the currently infamous software disaster at the new Denver international airport. Software engineering has been heralded as the needed discipline that can improve software development to meet the needs of modern software requirements. This paper will look at the key subject at the Queensland University of Technology (QUT) that introduces students to software engineering. This subject will be compared to current model curricula. The success of this subject will be evaluated and a corollary drawn to the usefulness of the model curricula. Then this paper will look at software engineering project work at QUT and consider what are appropriate compromises to make to run a successful group project in a single semester