Software engineering 2004

[1]  Robert L. Glass.  A big problem in academic software engineering and a potential outside-the-box solution , 2003, IEEE Software.

[2]  James E. Tomayko,et al.  Norm Gibbs and his contribution to software engineering education through the SEI curriculum modules , 2003, Proceedings 16th Conference on Software Engineering Education and Training, 2003. (CSEE&T 2003)..

[3]  G.W. Hislop,et al.  Engineering an introductory Software Engineering curriculum , 2003, Proceedings 16th Conference on Software Engineering Education and Training, 2003. (CSEE&T 2003)..

[4]  Ardis Hanson,et al.  Distance learning , 2003 .

[5]  Jean-Loup Baer.  Mutual exclusion , 2003 .

[6]  Mary Shaw,et al.  What makes good research in software engineering? , 2002, International Journal on Software Tools for Technology Transfer.

[7]  T. Dean Hendrix,et al.  Software Process in the Classroom: The Capstone Project Experience , 2002, IEEE Softw..

[8]  Watts S. Humphrey,et al.  The impending changes in software education , 2002, IEEE Software.

[9]  Hossein Saiedian,et al.  Software Engineering Programs: Dispelling the Myths and Misconceptions , 2002, IEEE Softw..

[10]  Michael R. Clarkson,et al.  Formal Methods Application: An Empirical Tale of Software Development , 2002, IEEE Trans. Software Eng..

[11]  Gerard O’Regan,et al.  The Capability Maturity Model , 2002 .

[12]  Dennis R. Wixon,et al.  Task analysis , 2002 .

[13]  Mikael Lindvall.  in Software Engineering , 2002 .

[14]  Mary Shaw,et al.  The coming-of-age of software architecture research , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[15]  Bertrand Meyer,et al.  Software Engineering in the Academy , 2001, Computer.

[16]  Hanan Lutfiyya,et al.  Experiences with a software maintenance project course , 2000, IEEE Trans. Educ..

[17]  Guy Tremblay.  Formal methods: mathematics, computer science or software engineering? , 2000, Thirteenth Conference on Software Engineering Education and Training.

[18]  David Lorge Parnas,et al.  Software Engineering Programs Are Not Computer Science Programs , 1999, IEEE Softw..

[19]  Michael J. Lutz,et al.  Guidelines for Software Engineering Education Version 1.0 , 1999 .

[20]  Rex Black.  Managing the Testing Process , 1999 .

[21]  S. Mcconnell,et al.  PROFESSIONAL SOFTWARE ENGINEERING : FACT OR FICTION? , 1999 .

[22]  James E. Tomayko,et al.  Forging a discipline: An outline history of software engineering education , 1999, Ann. Softw. Eng..

[23]  Zhi-Xiong Cai,et al.  Types of Defects , 1998 .

[24]  Tom J. van Weert,et al.  Informatics in Higher Education, Views on informatics and non-informatics curricula, IFIP TC3/WG3.2 International Conference on Informatics (computer science) as a Discipline and in Other Disciplines: waht is common? 17-20 August 1997, Enschede, The Netherlands , 1998, Informatics in Higher Education.

[25]  Edward A. Lee,et al.  Engineering and Education for the Future , 1998, Computer.

[26]  T. B. Hilburn,et al.  Software engineering education: a modest proposal , 1997 .

[27]  Jakob Nielsen,et al.  Usability engineering , 1997, The Computer Science and Engineering Handbook.

[28]  Henry MacKay Walker,et al.  A revised model curriculum for a liberal arts degree in computer science , 1996, CACM.

[29]  Keith W. Miller,et al.  Implementing a tenth strand in the CS curriculum , 1996, CACM.

[30]  Allison Coleman,et al.  Professional issues in software engineering (2nd ed.) , 1996 .

[31]  Michael H. Hoeflich.  Undergraduate Research & Intellectual Property Rights , 1996 .

[32]  R. Dekle,et al.  Planning for Change , 1995 .

[33]  Peter G. Neumann,et al.  Computer-related risks , 1994 .

[34]  Kathryn A. Ingle,et al.  Reverse Engineering , 1996, Springer US.

[35]  Peter J. Denning,et al.  Educating a new engineer , 1992, CACM.

[36]  Harald Reiterer,et al.  Evaluation of user interfaces , 1992 .

[37]  Mary Shaw,et al.  We Can Teach Software Better , 1992 .

[38]  Mary Shaw,et al.  Prospects for an engineering discipline of software , 1990, IEEE Software.

[39]  Howard K. Lane.  A Position Paper On , 1989, SIGD.

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

[41]  W. W. Royce,et al.  Managing the development of large software systems: concepts and techniques , 1987, ICSE '87.

[42]  Arto Salomaa,et al.  Formal languages , 1973, Computer science classics.

[43]  Norman E. Gibbs,et al.  A model curriculum for a liberal arts degree in computer science , 1986, CACM.

[44]  Mary Shaw,et al.  The Carnegie-Mellon Curriculum for Undergraduate Computer Science , 1985, Springer New York.

[45]  Gerald J. Sussman,et al.  Structure and interpretation of computer programs , 1985, Proceedings of the IEEE.

[46]  Elliot B. Koffman,et al.  Recommended curriculum for CS1, 1984 , 1984, CACM.

[47]  J. Daniel Couger,et al.  Information systems curriculum recommendations for the 80s: undergraduate and graduate programs , 1982, CACM.

[48]  John Dustin Kemper,et al.  Engineers and Their Profession , 1982 .

[49]  Anthony I. Wasserman,et al.  A proposed curriculum for software engineering education , 1978, ICSE '78.

[50]  Richard H. Austing,et al.  Recommendations for the Undergraduate Program in Computer Science , 1978 .

[51]  Michael C. Mulder.  Model Curicula for Four-Year Computer Science and Engineering Programs: Bridging the Tar Pit , 1975, Computer.

[52]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[53]  William F. Atchison,et al.  An undergraduate program in computer science—preliminary recommendations , 1965, CACM.

[54]  Benjamin S. Bloom,et al.  Taxonomy of Educational Objectives: The Classification of Educational Goals. , 1957 .