The process of teaching process

  • J. -P. Jacquot
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 895)


In this paper, I propose a personal analysis of the teaching of software process. It is based on two ideas: (1) what is new with software process is not the concept but the realization that it could be an artifact, and (2) the comparison of engineering software with engineering physical artifacts can provide us with guidelines to design better curricula. I outline two examples of courses which have been built along those ideas.


Software Engineering Software Engineer Software Process Capability Maturity Model Software Quality Management 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    D. Berry. Academic legitimacy of the software engineering discipline. Tech. Report CMU/SEI-92-TR-34, SEI — Carnegie Mellon University, 1992.Google Scholar
  2. 2.
    F.P. Brooks. The mythical man-month. Addison Wesley, 1975.Google Scholar
  3. 3.
    T. de Marco. Structured analysis and System specification. Prentice Hall, 1978.Google Scholar
  4. 4.
    W.S. Humphrey. Managing the Software Process. Addison-Wesley, 1989.Google Scholar
  5. 5.
    M. Jackson. Principles of Program Design. Academic Press, 1975.Google Scholar
  6. 6.
    J.-P. Jacquot and N. Lévy. Software engineering perspective in an introductory computer science course. Tech. Report 93-R-083, CRIN, 1993.Google Scholar
  7. 7.
    J.P. Jacquot, J. Guyard, and L. Boidot. Modeling teamwork in an academic environment. In L. Deimel, editor, Proc. of SEI'90 Conference, pages 110–122. SEI, Lecture Notes in Computer Science, 1990.Google Scholar
  8. 8.
    C.B. Jones. Systematic software development using VDM. Prentice Hall, 1986.Google Scholar
  9. 9.
    D.H. Kitson and S.M. Masters. An analysis of SEI software process assessment results: 1987–1991. In IEEE, editor, Proc. 15th ICSE, 1993.Google Scholar
  10. 10.
    H.D. Mills and F.T. Baker. Chief programmer teams. Datamation, 19(12):58–61, DECEMBER 1973.Google Scholar
  11. 11.
    J.M. Spivey. The Z notation: a reference manual. Prentice Hall, 1992.Google Scholar
  12. 12.
    J.F. Stay. HIPO and integrated program design. IBM System Journal, 15(2), 1976.Google Scholar
  13. 13.
    H. Tardieu, A. Rochfeld, and R. Colletti. La méthode MERISE. Editions d'Organisation, Paris, 1983.Google Scholar
  14. 14.
    W. Tichy. Design, implementation, and evaluation of a revision control system. In IEEE, editor, Proc. 6th ICSE, 1982.Google Scholar
  15. 15.
    J.-D. Warnier. The logical construction of programs. Van Nostrand, 1976.Google Scholar
  16. 16.
    G.M. Weinberg. The psychology of Computer Programming. Van Nostrand Reinhold, 1971.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1995

Authors and Affiliations

  • J. -P. Jacquot
    • 1
  1. 1.Université de Nancy 1 - ESIAL - CRINVandœuvre-lès-Nancy CedexFrance

Personalised recommendations