Putting into practice advanced software engineering techniques through students project

  • Naji Habra
  • Eric Dubois
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 750)


The paper describes an experience of software engineering education concerning the guidance of students project during about ten years. The project aims mainly at putting into practice the concepts, methods and techniques taught in a software engineering course through the development -by teams of students- of an actual, practical, real-size case. The concerned course involves several advanced topics, e.g., semi-formal requirements, formal specifications, transformational development process, Object-Oriented design,... which are sometimes considered as purely academic topics. Therefore, the main feature of the students project is to illustrate the applicability of these topics in a realistic project and thus to achieve an integration of modern techniques with more classical ones.


Software Engineer Hospital Information System Requirement Document Student Project Dynamic Design 
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.
    F. Baker. Chief programming team management of production programming. IBM Journal, 11(1):58, 1972.Google Scholar
  2. 2.
    R. Balzer. Transformational Implementation: an Example. IEEE Transactions on Software Engineering, 7(1):3–14, 1981.Google Scholar
  3. 3.
    R. Balzer, D. Cohen, M.S. Feather, N. Goldman, W. Swartout, and D. Wile. Operational Specification as the Basis for Specification Validation. In D. Ferrari, M. Bolognani, and J. Goguen, editors, Theory and Practice of Software Technology, pages 21–49. North-Holland, 1983.Google Scholar
  4. 4.
    R. Balzer, N. Goldman, and D. Wile. On the Transformational Implementation Approach to Programming. In Proc. Second IEEE International Conference on Software Engineering, pages 337–349, San Francisco, CA, USA, October 1976. The CS IEEE Press.Google Scholar
  5. 5.
    R. Balzer, N. Goldman, and D. Wile. Operational Specification as the Basis for Rapid Prototyping. ACM Sigsoft Software Engineering Notes, 7(5):3–16, 1982.CrossRefGoogle Scholar
  6. 6.
    D. Bjørner and C.B. Jones. The Vienna Development Method. The metalanguage, volume 61 of LNCS. Springer-Verlag, 1978.Google Scholar
  7. 7.
    F. Bodart and Y. Pigneur. Conception assistée des applications informatiques. Première partie: Etude d'opportunité et analyse conceptuelle. Masson, Paris, 1983.Google Scholar
  8. 8.
    B. Boehm. Software engineering. IEEE Transactions on Computers, 25(12), 1976.Google Scholar
  9. 9.
    G. Booch. Object Oriented Design with Applications. The Benjamin Cunnings Publishing Company, 1991.Google Scholar
  10. 10.
    Richard E. Fairley. Software Engineering Concepts. Mc Graw-Hill, 1984.Google Scholar
  11. 11.
    C. Ghezzi. Fundamentals of Software Engineering. Prentice Hall, 1991.Google Scholar
  12. 12.
    Raise Language Group. The RAISE Specification Language. BCS Practitioner Series. Prentice-Hall, 1992.Google Scholar
  13. 13.
    Ian Hayes. Specification case studies. Prentice-Hall International, 1987.Google Scholar
  14. 14.
    M.A. Jackson. System Development. Prentice-Hall, 1983.Google Scholar
  15. 15.
    C.B. Jones. Systematic Software Development Using VDM. Prentice-Hall Series in Computer Science. Prentice-Hall, 1986.Google Scholar
  16. 16.
    G. Longworth and D. Nicholls. SSADM manual. Technical report, National Computing Center, UK, 1987.Google Scholar
  17. 17.
    T. De Marco. Structured Analysis and System Specification. Prentice Hall, Englewood Cliffs, N.J., 1981.Google Scholar
  18. 18.
    D.L. Parnas. On the criteria to be used in decomposing systems into modules. Commuications of the ACM, 15(12), 1972.Google Scholar
  19. 19.
    D.L. Parnas. A technique for software module specification with examples. Commuications of the ACM, 15(5), 1972.Google Scholar
  20. 20.
    A. Rochfeld and H. Tardieu. MERISE: an information system design and development methodology. Information & Management, 6(3):143–159, June 1983.Google Scholar
  21. 21.
    A. Sernadas, C. Sernadas, and H.-D. Ehrich. Abstract object types: a temporal perspective. In B. Banieqbal, H. Barringer, and A. Pnueli, editors, Proc. of the colloquium on temporal logic and specification, pages 324–350. LNCS 398, Springer-Verlag, 1989.Google Scholar
  22. 22.
    Amílcar Sernadas, Cristina Sernadas, and Hans-Dieter Ehrich. Object-oriented specification of databases: an algebraic approach. In Peter Hammersley, editor, Proceedings of the 13th international conference on very large data bases, pages 107–116, Brighton (UK), September 1–4, 1987.Google Scholar
  23. 23.
    J.M. Spivey. The Z notation — a reference manual. Prentice-Hall International, 1989.Google Scholar
  24. 24.
    H. Tardieu, A. Rochfeld, R. Coletti, G. Panet, and G. Vahee. La méthode MERISE vol 1 and 2. Editions Hommes et Techniques, Paris, 1985.Google Scholar
  25. 25.
    A. van Lamsweerde. Cadre général pour un modèle de cycle de vie d'un projet informatique. Technical report, University of Namur, Namur (Belgium), 1985.Google Scholar
  26. 26.
    A.I. Wasserman, P.A. Pircher, and D.T. Shewmake. Building reliable interactive information systems. IEEE Transactions on Software Engineering, 12(1), 1986.Google Scholar
  27. 27.
    A.I. Wasserman, P.A. Pircher, D.T. Shewmake, and M.L. Kersten. Developing interactive information systems with the user software engineering methodologie. IEEE Transactions on Software Engineering, 12(2), 1986.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1993

Authors and Affiliations

  • Naji Habra
    • 1
    • 2
  • Eric Dubois
    • 1
    • 2
  1. 1.Facultés Universitaires Notre-Dame de la PaixInstitut d'InformatiqueFrance
  2. 2.Institut d'InformatiqueNamurBelgium

Personalised recommendations