The Role of Object-Oriented Modelling Methods in Requirements Engineering

  • Linda L. Dawson
  • Paul A. Swatman


In recent years many organisations have been moving to the use of object-oriented methods for the development of information systems. Many claims have been made about the efficacy of object-oriented methods for specifying and building software and information systems. Several studies have looked at small groups (often students) using object-oriented methods for small one-off exercises or problems. These studies lack information about how real systems are being developed in practice. There is a need to investigate the use of object-oriented methods by practising professionals in the production of requirements specifications for “real world” sized projects. In this paper firstly we outline a conceptual framework of “what might be happening” in professional object-oriented requirements engineering based on the common characteristics of published, well known objectoriented methods. Secondly, we describe a research plan for a set of case studies that are currently being undertaken.


Hunt Encapsulation Clarification 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Wegner, P.: Dimensions of object-based language design. In: OOPSLA. ACM, New York, 1987.Google Scholar
  2. 2.
    Dawson, L.L. and P.A. Swatman: Object-Oriented Requirements Engineering in Practice. In: Fifth European Conference on Information SystemsCork, Ireland, 1997.Google Scholar
  3. 3.
    Chaiyasut, P. and G. Shanks: Conceptual Data Modelling Process: A Study of Novice and Expert Data Modellers. In: First International Conference on Object Role ModellingMagnetic Island, Australia, 1994.Google Scholar
  4. 4.
    Guindon, R, Knowledge exploited by experts during software system design. International Journal of Man-Machine Studies, 1990; 33:: p. 279–304.CrossRefGoogle Scholar
  5. 5.
    Sutcliffe, A.G. and N.A.M. Maiden, Analysing the novice analyst: cognitive models in software engineering. International Journal of Man-Machine Studies, 1992: 36:: p. 719–740.CrossRefGoogle Scholar
  6. 6.
    Vitalari, N.P. and G.W. Dickson, Problem Solving for effective systems analysis: an experimental exploration Communications of the ACM, 1983; 26:(11).Google Scholar
  7. 7.
    Boehm-Davis, D. and L. Ross, Program design methodologies and the software development process. International Journal of Man-Machine Studies, 1992; 36:: p. 1–19.CrossRefGoogle Scholar
  8. 8.
    Lee, Y. and N. Pennington, The effects of paradigm on cognitive activities in design. International Journal of Human-Computer Studies, 1994; 40:: p. 577–601.CrossRefGoogle Scholar
  9. 9.
    Morris, M., C. Speier, and J. Hoffer: The impact of experience on individual performance and workload differences using object-oriented and processoriented systems analysis techniques. In: 29th Hawaii International Conference on System SciencesMaui, Hawaii, 1996.Google Scholar
  10. 10.
    Vessey, I. and S. Conger, Requirements specification: Learning object, process, and data methodologies. Communications of the ACM, 1994; 37: (5).Google Scholar
  11. 11.
    Ericsson, K.A. and H.A. Simon, Verbal Reports as Data. Psychological Review, 1980(87): p. 215–251.Google Scholar
  12. 12.
    Carroll, J. and P. Swatman: How Can the Requirements Engineering Process be Improved? In: Eighth Australasian Conference on Information Systems University of South Australia, Adelaide, South Australia, 1997.Google Scholar
  13. 13.
    Carroll, J. and P.A. Swatman, Case Notes, . 1997.Google Scholar
  14. 14.
    Carroll, J., B. Hunt, and P. Swatman, Producing quality applications for Webenabled Electronic Commerce, . 1998: submitted to 1 1 th International Bled Electronic Commerce Conference.Google Scholar
  15. 15.
    Khushalani, A., R. Smith, and S. Howard, What happens when designers don’t play by the rules: Towards a model of opportunistic behaviour and design. Australian Journal of Information Systems, 1994: p. 13–31.Google Scholar
  16. 16.
    Loucopoulos, P. and V. Karakostas, Systems Requirements Engineering. . McGraw-Hill. London, UK, 1995.Google Scholar
  17. 17.
    Macaulay, L., Requirements Engineering. . Springer-Verlag. London, 1996.MATHCrossRefGoogle Scholar
  18. 18.
    Boehm, B.W., Software Engineering. IEEE Transactions on Computers, 1976; 25: (12): p. 1226–1241.MATHCrossRefGoogle Scholar
  19. 19.
    Jackson, M.C.: Critical Systems Thinking and Information Systems Development. In: Eighth Australasian Conference on Information SystemsUniversity of South Australia, Adelaide, South Australia, 1997.Google Scholar
  20. 20.
    OASIG, Why do IT Projects so often Fail?, in OR Newsletter. 1996. p. 12–16.Google Scholar
  21. 21.
    Avison, D.E. and G. Fitzgerald, Information Systems Development: Methodologies, Techniques and Tools. 2 ed. McGraw Hill. , 1995.Google Scholar
  22. 22.
    Checkland, P. and J. Scholes, Soft Systems Methodology in Practice. . Wiley. Chichester, 1990.Google Scholar
  23. 23.
    Pohl, K.: The three dimensions of requirements engineering. In: Fifth International Conference on Advanced Information Systems Engineering (CAiSE’93). Springer-Verlag, Paris, 1993.Google Scholar
  24. 24.
    Booch, G., Object-Oriented Analysis and Design with Applications. Benjamin/Cummings. Redwood City, 1994.Google Scholar
  25. 25.
    Coad, P. and E. Yourdon, Object-Oriented Analysis. 2 ed. Yourdon Press/Prentice-Hall. Englewood Cliffs, NJ, 1991.Google Scholar
  26. 26.
    Henderson-Sellers, B. and J. Edwards, BOOKTWO of Object-Oriented Knowledge: The Working Object. . Prentice Hall. Englewood Cliffs, NJ, 1994.Google Scholar
  27. 27.
    Meyer, B., Object-Oriented Software Construction. . Prentice-Hall. Englewood Cliffs, NJ, 1988.Google Scholar
  28. 28.
    Boehm, B.W., A spiral model of software development and enhancement IEEE Computer, 1988; 25:(5): p. 61–72.Google Scholar
  29. 29.
    Henderson-Sellers, B., A Book of Object-Oriented Knowledge. 2 ed. PrenticeHall. Upper Saddle River, NJ, 1997.Google Scholar
  30. 30.
    Rumbaugh, J., et al., Object-Oriented Modeling and Design. . Prentice-Hall. Englewood Cliffs, NJ, 1991.Google Scholar
  31. 31.
    Wirfs-Brock, R.J., B. Wilkerson, and L. Wiener, Designing Object-Oriented Software. Prentice Hall. New York, USA, 1990.Google Scholar
  32. 32.
    Graham, I., Object Oriented Methods. Addison-Wesley. 1994.Google Scholar
  33. 33.
    Swatman, P.A., Formal object-oriented method — FOOM, in Specification of Behavioural Semantics in Object-Oriented Information Systems, W. Harvey, Editor. 1996, Kluwer Academic Publishers: Norwell, Massachucetts.Google Scholar
  34. 34.
    Jacobson, I., et al., Object-Oriented Software Engineering: A Use Case Driven Approach. . Addison-Wesley/ACM. New York, 1992.MATHGoogle Scholar
  35. 35.
    Shlaer, S. and S.J. Mellor, Modelling the World in States. Yourdon Press. Englewood Cliffs, NJ, 1991.Google Scholar
  36. 36.
    Fowler, D., P.A. Swatman, and E.N. Wafula, Formal methods in the IS domain:Introducing a notation for presenting Object-Z specifications. Object Oriented Systems, 1995; 2:(2).Google Scholar
  37. 37.
    Fowler, D., Formal Methods in a commercial information systems setting: the FOOM methodology, in Department of Information Systems. 1996, Swinburne University of Technology: Melbourne.Google Scholar
  38. 38.
    Wafula, E.N. and P.A. Swatman, FOOM: a diagrammatic illustration of Obiect-Z snecifications. Object Oriented Systems, 1996; 3:(4): p. 215–243.Google Scholar
  39. 39.
    Miles, M.B. and A.M. Huberman, Qualitative Data Analysis: A Sourcebook of New Methods. . Sage Publications Inc. Newbury Park, CA, 1984.Google Scholar
  40. 40.
    Yin, RK., Case Study Research: Design and Methods. Vol. 5. 2 ed. Applied Social Research Methods Series. Sage Publications Inc. Thousand Oaks, CA, 1994.Google Scholar

Copyright information

© Springer-Verlag London 1999

Authors and Affiliations

  • Linda L. Dawson
    • 1
  • Paul A. Swatman
    • 1
  1. 1.School of Management Information SystemsDeakin UniversityBurwoodAustralia

Personalised recommendations