Teaching more comprehensive model-based software engineering: Experience with objectory's use case approach

  • Robert F. Coyne
  • Bernd Bruegge
  • Allen H. Dutoit
  • David Rothenberger
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 895)


This paper is an experience report and discussion of an experiment in teaching and using a comprehensive model-based methodology and tool (Objectory) in a large software project. The paper describes in detail the preparation of such an experiment, states our assumptions during the planning phase, and presents the results together with a discussion of the most important issues. We observed certain improvements in the productivity and understanding of the students, while discovering a number of non-trivial organizational and pedagogical issues still remaining to be solved (e.g. communication latency and breakdown; project set up time; training time etc.). We believe that this paper will provide valuable insights to the reader at a number of different levels: 1. To those interested in state of the art software engineering methodologies; 2. To those interested in Objectory per se; 3. To those interested in the issues of introducing a sophisticated modeling methodology into a pilot project involving a large number of participants.


Software Engineering Robustness Analysis Objectory Database Interaction Diagram Objectory Methodology 
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.
    S. Bilow: “Reflections on the state of object-oriented literature”, Journal of Object-Oriented Programming (JOOP), June, 1993, pp. 72-73.Google Scholar
  2. 2.
    G. Booch: Object-Oriented Design with Applications, Benjamin Cummings, NY, 1991.Google Scholar
  3. 3.
    G. Booch: The Booch Method Process and Pragmatics, Rational Inc., Santa Clara 1992.Google Scholar
  4. 4.
    B. Bruegge, J. Cheng and M. Shaw: “A software engineering course with a real client”, Carnegie Mellon University, Technical Report CMU-SEI-91-EM-4, July 1991.Google Scholar
  5. 5.
    B. Bruegge: “Teaching an industry-oriented software engineering course”, C. Sledge (Ed.), Software Engineering Education, Lecture Notes, in Computer Science, Vol 640, pp. 65–87, Springer Verlag, 1992.Google Scholar
  6. 5.
    B. Bruegge, J. Blythe, J. Jackson and J. Shufelt: “Object-oriented system modeling with OMT”, Conference on Object-Oriented Programming Systems, Languages and Applications (OOPSLA '92), Vancouver, October 1992.Google Scholar
  7. 6.
    B. Bruegge and R. Coyne: “Model-based software engineering in larger scale project courses”, Proceedings of the IFIP Working Conference on Software Engineering Education, Hong Kong, September 1993, Elsevier Science, Publisher.Google Scholar
  8. 7.
    B. Bruegge and R. Coyne: “Teaching iterative and collaborative design: lessons and directions”, Software Engineering Education, Lecture Notes in Computer Science, J. L. Diaz-Herrera (Ed.)., Springer Verlag, January 1994, 7th. SEI Conference on Software Engineering (CSEE), San Antonio, Texas, USA, January 1994.Google Scholar
  9. 8.
    P. Coad and E. Yourdon: Object-Oriented Analysis, Prentice Hall, 1991.Google Scholar
  10. 9.
    A. Cockburn: “In search of a METHODOLOGY”, Object Magazine, July–August, 1994, pp. 52–56, 76.Google Scholar
  11. 10.
    R. Coyne, U. Flemming, P. Piela and R. Woodbury: “Behavior modeling in design system development”, Proceedings of CAAD Futures '93, Conference, Carnegie Mellon University, July, 1993.Google Scholar
  12. 11.
    R. Coyne, A. Dutoit, J. Uzmack and K. O'Toole: “Requirements analysis for Information WEB (IWEB): an issue-based, information modeling and management environment for software engineering”, Technical Report, EDRC-05-87-94, Engineering Design Research Center, CMU, 1994.Google Scholar
  13. 12.
    R.Coyne and M. Ehrenberger: “Information modeling for software engineering: an illustrative project history”, Technical Report, EDRC-05-88-94, Engineering Design Research Center, CMU, 1994.Google Scholar
  14. 13.
    IEEE Computer Society:IEEE Standard for Developing Software Life Cycle Processes IEEE 1074-1991, Institute of Electrical and Electronics Engineers, Inc. 345 East 47th St. New York, NY, 1992.Google Scholar
  15. 14.
    I. Jacobson, M. Christerson, P. Jonsson and G. Overgaard: Object-Oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley Publishing Company, NY, 1992.Google Scholar
  16. 15.
    I. Jacobson and D. Bennett: “Life after methods: the software development process”, Object Magazine, Nov–Dec, 1993.Google Scholar
  17. 16.
    I. Jacobson: “Yes, there is life after methods: processes”, Keynote Address, Object Methods Conference, Objex, Boston, October 18–22, 1993.Google Scholar
  18. 17.
    J. Jeffcoate and I. Wesley: “Objects in use: meeting business needs”, Internal Report, Ovum, Ltd., London, England, 1992.Google Scholar
  19. 18.
    S. Levy, E. Subrahmanian, R. Coyne, S. Konda, A. Westerberg and Y. Reich: “An overview of the n-dim environment”, Technical Report, EDRC-05-65-93, Engineering Design Research Center, Carnegie Mellon University, January 1993.Google Scholar
  20. 19.
    T.F. Maleki and N. Hashemi-Nejad: “Evaluation of two major object-oriented methodologies and related tools”, Internal Report, AVEMCO Corporation, Frederick, Maryland, 1993.Google Scholar
  21. 20.
    Objective Systems, SF AB: Manuals for Objectory, Version 3.3, 1992, Box 1128, S-164 22 KISTA, Sweden.Google Scholar
  22. 21.
    John Ousterhout: An Introduction To Tcl and Tk, Addison-Wesley, NY, 1994.Google Scholar
  23. 22.
    James Rumbaugh: “Getting started: using use cases to capture requirements”, Journal of Object-Oriented Programming (JOOP), September 1994, Vol.7, No.5.Google Scholar
  24. 23.
    James Rumbaugh, Michael Blaha, William Premerlani, Frederick Eddy and William Lorensen: Object Modeling and Design, Prentice-Hall 1991.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1995

Authors and Affiliations

  • Robert F. Coyne
    • 1
  • Bernd Bruegge
    • 2
  • Allen H. Dutoit
    • 3
  • David Rothenberger
    • 4
  1. 1.Engineering Design Research CenterCarnegie Mellon UniversityPittsburgh
  2. 2.School of Computer ScienceCarnegie Mellon UniversityPittsburgh
  3. 3.Department of Electrical and Computer EngineeringCarnegie Mellon UniversityPittsburgh
  4. 4.School of Computer ScienceCarnegie Mellon UniversityPittsburgh

Personalised recommendations