Modeling teamwork in an academic environment

  • J. P. Jacquot
  • J. Guyard
  • L. Boidot
Part of the Lecture Notes in Computer Science book series (LNCS, volume 423)


Teaching software engineering is a challenge, mostly because students should have come up against practical problems to be able to understand the important concepts of the field. Unfortunately, a factory environment (through training courses) can bear out the problems but does not ensure a good pedagogic management whereas an academic environment provides a pedagogic management but does not meet the requirements in software developments of industrial size. This paper presents our experiment: the teamwork project. It tries to deal with the preceding difficulty in our academic environment.

The first part of the paper presents the aim a software engineering course should try to reach from our point of view: namely, teaching students to build and manage coherent and evolving structures. The different kinds of structures are discussed.

The second part presents the teamwork project. The main idea is to consider this project as a scale model whose parameters can be exhibited and modified actively by the students. Then our emphasis is not on the delivery of a product but on the building of a well-running and efficient team of more than ten members.


Software Engineering Scale Model Software Project Academic Environment Team Structure 
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. [DGHKL80]
    V. Donzeau-Gouge, G. Huet, G. Kahn, and B. Lang. Programming environnement based on structure editors: The MENTOR experience. In Proc. Workshop on Programming Environments, Ridge Fields, LT, June 1980.Google Scholar
  2. [HW77]
    J.J. Horning and D.B. Wortman. Software hut: a computer program engineering project in a form of a game. IEEE — Trans. Soft Eng, 3(4):325–330, 1977.Google Scholar
  3. [JB89]
    A. Jones and M. Birtle. An individual assessment technique for group projects in software engineering. Software Engineering Journal, 4(4):225–232, 1989.Google Scholar
  4. [Kin89]
    P.J.B. King. Experiences with group project in software engineering. Software Engineering Journal, 4(4):221–225, 1989.Google Scholar
  5. [Lam86]
    L. Lamport LATEX User's Guide & Reference Manual. Addison-Wesley, 1986.Google Scholar
  6. [MB73]
    H.D. Mills and F.T. Baker. Chief programmer teams. Datamation, 19(12):58–61, DECEMBER 1973.Google Scholar
  7. [Tom89]
    B. Tompsett. The system cottage — a multidisciplinary engineering group practical. Software Engineering Journal, 4(4):209–220, 1989.CrossRefGoogle Scholar
  8. [WF76]
    A.I. Wasserman and P. Freeman, editors. Towards Improving Software Engineering Education. Springer-Verlag, New-York, 1976.Google Scholar
  9. [Wor87]
    D.B. Wortman. Software projects in an academic environment. IEEE — Trans. Soft. Eng, 13(11):1176–1181, 1987.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1990

Authors and Affiliations

  • J. P. Jacquot
    • 1
  • J. Guyard
    • 1
  • L. Boidot
    • 2
  1. 1.Université de Nancy I — ISIAL — CRIN Campus V. GrignardVandœuvre-lès-NancyFrance
  2. 2.Cegelec/RedClamartFrance

Personalised recommendations