Twenty dirty tricks to train software engineers

ABSTRACT

Many employers find that graduates and sandwich students come to them poorly prepared for the every day problems encountered at the workplace. Although many university students undertake team projects at their institutions, an education environment has limitations that prevent the participants experiencing the full range of problems encountered in the real world. To overcome this, action was taken on courses at the Plessey Telecommunications company and Loughborough University to disrupt the students' software development progress. These actions appear mean and vindictive, and are labeled 'dirty tricks' in this paper, but their value has been appreciated by both the students and their employers. The experiences and learning provided by twenty 'dirty tricks' are described and their contribution towards teaching essential workplace skills is identified. The feedback from both students and employers has been mostly informal but the universally favourable comments received give strong indications that the courses achieved their aim of preparing the students for the workplace. The paper identifies some limitations on the number and types of 'dirty tricks' that can be employed at a university and concludes that companies would benefit if such dirty tricks were employed in company graduate induction programmes as well as in university courses.

REFERENCES

• 1: James Bach, Point-SE Education: We're on Our Own, IEEE Software, v.14 n.6, p.26, November 1997
• 2: Burgess, W.P., Can quality survive amidst adversity? in Proc. of Software Quality Management VII (Amsterdam, April 1998), Springer, 204-208
• 3: Chapman, N., Fox, M., Keravnou, E., Lee, M., Levene, M., Long, D., Rounce, P., Samet, P. and Winder,R., 'Slick systems' and 'happy hackers': experience with group projects at UCL, Softw.Eng.J., vol. 8,3 (1993) 132-136
• 4: R. J. Dawson , R. W. Newsham , R. S. Kerridge, Introducing new software engineering graduates to the “real world” at the GPT company, Software Engineering Journal, v.7 n.3, p.171-176, May 1992
• 5: Dawson, R.J., Newsham, R.W. and Fernley, B.W., 'Bringing the "Real World' of Software Engineering to University Undergraduate Courses, IEE Proc. in Software Engineering , 144,5-6 (1997) 287-290
• 6: Thomas B. Hilburn, Software Engineering Education: A Modest Proposal, IEEE Software, v.14 n.6, p.44-48, November 1997 [doi>10.1109/52.636650]
• 7: Jarke, M. and Pohl,K., Requirements engineering in 2001: (virtually) managing a changing reality, Softw.Eng.J., vol. 9,6 (1994), 257-266,
• 8: Laura M. Leventhal , Barbee T. Mynatt, Components of typical undergraduate software engineering courses: results from a survey, IEEE Transactions on Software Engineering, v.13 n.11, p.1193-1198, November 1, 1987 [doi>10.1109/TSE.1987.232869]
• 9: Mahmood, Z., Software engineering in the UK -Result of a pilot survey, in Proc. of INSPIRE IV, Training and Teaching for the Understanding of Software Quality (Heraklion, Crete, Sept. 1999), British Computer Society, 111-122
• 10: W. Michael McCracken, Counterpoint-SE Education: What Academia Can Do, IEEE Software, v.14 n.6, p.27, November 1997 [doi>10.1109/MS.1997.636593]
• 11: Milsom, F., Student Projects and Professionalism, in The Responsible Software Engineer, Chapter 32, 1996, Springer, London, 306-319
• 12: Saunders, B. and Georgiadou, E., Awareness and practice of information systems development methodologies in business today, in Proc. of Software Quality Management VIII (Southampton, UK, April 1999), British Computer Society, 133-144
• 13: Michiel van Genuchten, Why is Software Late? An Empirical Study of Reasons for Delay in Software Development, IEEE Transactions on Software Engineering, v.17 n.6, p.582-590, June 1991 [doi>10.1109/32.87283]

INDEX TERMS

Primary Classification:
  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.1 Project and People Management
          Subjects: Training

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Programming teams

  K. Computing Milieux
  K.3 COMPUTERS AND EDUCATION
      K.3.2 Computer and Information Science Education
          Subjects: Curriculum

General Terms:
Design, Human Factors, Management, Measurement, Performance, Theory

Keywords:
education, project, teamwork, training, work experience