Advertisement

Adopting object oriented analysis for telecommunications systems development

  • Declan Martin
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1238)

Abstract

It has been accepted for some time that errors introduced in the early phases of software development are significantly more expensive to correct that those introduced at later stages. Therefore, development teams should emphasise the analysis phase to ensure that system requirements are captured correctly and documented unambiguously. This paper reports on initial experiences with the adoption of object oriented analysis (OOA) for the production of telecommunications systems. The purpose of the paper is to report the experiences gained, to offer some recommendations for those attempting to introduce object oriented analysis into their organisation, and to remind developers of important issues that are sometimes overlooked. Three main conclusions are drawn: adopting a methodological approach to object oriented analysis is difficult but beneficial, using existing telecommunications specific models within the context of an OOA method causes problems, and additional tool functionality supporting telecommunications systems development would be appreciated.

Keywords

Object Orientation Analysis Migration Lessons learned 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. [1]
    Basili V.R., and Perricone B.T., “Software Errors and Complexity: An Empirical Investigation,” Communications of the ACM, Vol. 27, No. 1, pp 42–52, January 1984.Google Scholar
  2. [2]
    Bell R., “Choosing Tools for Analysis and Design”, IEEE Software, May 1994, pp 121–125.Google Scholar
  3. [3]
    Boehm B.W., Software Engineering Economics, Prentice Hall, Englewood Cliffs, NJ, USA, 1981.Google Scholar
  4. [4]
    Booch G., Object-oriented Analysis and Design, 2nd Edition, Benjamin/Cummings Publishing Co., California, USA, 1994.Google Scholar
  5. [5]
    Chidamber S.R., and Kemerer C.F., “Towards a Metrics Suite for Object Oriented Design”, in OOPSLA '91, Proceedings of the 6th Annual Conference on Object Oriented Programming, Systems, Languages and Applications, ACM Press, 1991, pp 197–211.Google Scholar
  6. [6]
    Coleman D., et al., Object-oriented Development: The Fusion Method, Prentice Hall International, 1994.Google Scholar
  7. [7]
    DSDM Home Page URL: http://www.dsdm.org/Google Scholar
  8. [8]
    Fayad M.E., T.S. Tsai, and M.L. Fulghum “Transition to Object Oriented Software Development” in Communications of the ACM, Vol. 39, No 2., pp 108–121, February 1996.Google Scholar
  9. [9]
    Harwood R.J., “Use Case Formats: Requirements, Analysis and Design”, in Journal of Object Oriented Programming, January 1997, pp 54–57.Google Scholar
  10. [10]
    Johnson D., “The Important things are Always Simple”, Object Magazine, September 1996, pp 66–70.Google Scholar
  11. [11]
    Lewis J.A., Henry S.M., Kafura D.G., and Schulman R.S., “An Empirical Study of the Object Oriented Paradigm and Software Reuse”, in OOPSLA '91, Proceedings of the 6th Annual Conference on Object Oriented Programming, Systems, Languages, and Applications, pp 184–196, ACM Press, 1991.Google Scholar
  12. [12]
    McGibbon B., Managing Your Move to Object Technology, SIGS Books, 1996.Google Scholar
  13. [13]
    Network Management Forum (NMF), 1201 Mt. Kemble Avenue, Morristown, New Jersey 07960, Request for Proposal for Object Oriented Analysis and Design Tools, June 1996.Google Scholar
  14. [14]
    Paulk M., “Capability Maturity Model for Software Development, Version 1.1”, Tech. Report CMU/SEI-93-TR-24, Feb 1993.Google Scholar
  15. [15]
    Posten R.M., “Preventing Software Requirements Specification Errors with IEEE 830,” IEEE Software, Vol. 2 No. 1, pp 83–86, 1985.Google Scholar
  16. [16]
    Rumbaugh J., Blaha M., Premerlani W., Eddy F., Lorensen W., Object Oriented Modelling and Design, Prentice Hall, 1991.Google Scholar
  17. [17]
    The Unified Modelling Language (UML), Version 1.0, Rational Software Corporation, January 1997.Google Scholar
  18. [18]
    Collection of OOA tools can be found at URL: http://www.csse.swin.edu.au/manfred/allpages.html#oo_ooa_ood_toolsGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1997

Authors and Affiliations

  • Declan Martin
    • 1
  1. 1.Broadcom Eireann Research, Ltd.Dublin 2Ireland

Personalised recommendations