Skip to main content
Log in

Integration issues elucidated in large-scale information systems development

  • Published:
Journal of Systems Integration

Abstract

This article explores some basic issues in system integration by examining the integration process with information systems. The article begins with a discussion of the domain of interest. Terms are defined, the software process is reviewed, and two system categories are established. It is shown that software is materially different from hardware. Moreover, these differences present opportunities for reducing the integration effort. Several methods that take advantage of software's special characteristics are identified, and a case study of one environment provides some empirical evidence that reveal the benefits that may follow. The article concludes with some observations regarding the transfer of the lessons learned with information systems to other application domains-both hardware and software.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  1. M. M. Lehman, “Life cycles and laws of program evolution,” inProc. IEEE, vol. 68, pp. 1060–1076, 1980.

  2. B.I. Blum, “Formalism and prototyping in the software process”,Info. and Decision Technol. vol. 15, pp. 327–341, 1989.

    Google Scholar 

  3. B.W. Boehm, “Software engineering,”IEEE Trans. Comp., Vol. C-25, pp. 1226–1241, 1976.

    Google Scholar 

  4. H. Gomaa and D.B.H. Scott, “Prototyping as a tool in the specification of user requirements”Proc. Int. Conf Soft. Eng. San Diego, CA, 1981, pp. 333–342.

  5. B.W. Boehm, “A spiral model of software development and enhancement”,Computer vol 21 (5), pp. 61–72, 1988.

    Google Scholar 

  6. T. Gilb,Principles of Software Engineering Management, Addison-Wesley; Reading, MA, 1988.

    Google Scholar 

  7. H.D. Mills, R.C. Linger, M. Dyer, and R.E. Quinnan, “The management of software engineering,IBM Systems J. vol. 24 (2), pp. 414–477, 1980.

    Google Scholar 

  8. D.N. Card with R.L. Glass,Measuring Software Design Quality, Prentice-Hall: Englewood Cliffs, NJ, 1990

    Google Scholar 

  9. B. Cohen, W.T. Harwood, and M.I. Jackson,The Specification of Complex Systems, Addison-Wesley: Reading, MA, 1986.

    Google Scholar 

  10. J.M. Wing, “A specifier's introduction to formal methods”,Computer vol. 23 (9), pp. 8–24, 1990.

    Google Scholar 

  11. S.L. Gerhart, “Application of formal methods: Developing virtuoso software,Software vol 7 (5), pp. 6–10, 1990.

    Google Scholar 

  12. C.B. Jones,Systematic Software Development Using VDM, Prentice-Hall: Englewood Cliffs, NJ, 1986.

    Google Scholar 

  13. J.M. Spivey,The Z Notation: A Reference Manual, Prentice-Hall, Englewood Cliffs, NJ, 1989.

    Google Scholar 

  14. J.V. Guttag, J.J. Horning, and J.M. Wing, “Larch in five easy pieces,” Technical Report 5, DEC Systems Research Center, July 1985.

  15. R. Locasso et al., “The Ina Jo reference manual”, Technical Report TM-(L)-6021/001/000 System Development Corp., Santa Monica, CA, 1980.

  16. H.D. Mills, M. Dyer, and R. Linger, “Cleanroom software engineering”,Software vol 4 (5), pp. 19–25, 1987.

    Google Scholar 

  17. P. Zave, “The operational versus the conventional approach to software development,”Comm. ACM vol. 27, pp. 104–118, 1984.

    Google Scholar 

  18. R. Balzer, T.E. Cheatham, Jr., and C. Green, “Software technology in the 1990s: Using a new paradigm,”Computer vol. 16 (11), pp. 39–45, 1983.

    Google Scholar 

  19. B.I. Blum, “A paradigm for developing information systems,” inIEEE Trans. Soft. Eng., vol. SE-13, pp. 432–439, 1987.

  20. J. Musa (ed.), “Stimulating software engineering progress, a report of the software engineering planning group”,ACM SIGSOFT SEN vol. 8 (2), pp. 29–54, 1983.

  21. B.I. Blum, “A tool for developing information systems”, in H.J. Schneider and A.I. Wasserman (eds.),Automated Tools for Information Systems Design, North-Holland Publishing Co., New Orleans, LA, 1982, pp. 215–235.

    Google Scholar 

  22. B.I. Blum,TEDIUM and the Software Process, MIT Press: Cambridge, MA, 1990.

    Google Scholar 

  23. J. Lewkowicz,The Complete MUMPS, Prentice-Hall: Englewood Cliffs, NJ, 1989.

    Google Scholar 

  24. B.I. Blum, “Knowledge-based software engineering: A different approach”, inProc. 2nd Int. Conf. Soft. Eng. and Knowledge Engl., Skokie, IL, 1990, pp. 1–6.

  25. B.I. Blum, “Volume, distance and productivity”,J. Systems and Software vol. 10, pp. 217–226, 1989.

    Google Scholar 

  26. B.W. Boehm, “An experiment in small-scale applications software engineering”, inIEEE, Trans. Soft. Eng., vol. SE-7, 1981, pp. 482–493.

  27. B.W. Boehm, W.T. Gray, and T. Seawaldt “Prototyping vs. specifying: A multi-project experiment”,IEEE Trans. Soft. Eng., vol. SE-10, 1984, pp. 290–303.

    Google Scholar 

  28. T.S. Kuhn,The Structure of Scientific Revolutions 2nd ed., University of Chicago Press: Chicago, 1970.

    Google Scholar 

  29. B.I. Blum, S.D. Diamond, M.G. Hammond, M.E. Perkins, and R.D. Semmel, “An intelligent navigational assistant for a decision resource database”, inProc. Expert Systems in Government, Washington, DC, 1987, pp. 19–25.

  30. J.P. Enterline, R.E. Lenhard, and B.I. Blum (eds.),A Clinical Information, System for Oncology, Springer-Verlag: New York, 1989.

    Google Scholar 

  31. S.W. Tu, M.G. Kahn, M.A. Musen, J.C. Ferguson, E.H. Shortliffe, and L.M. Fagan, “Episodic skeletalplan refinement based on temporal data”,Comm. ACM vol. 32, pp. 1439–1455, 1989.

    Google Scholar 

  32. B.I. Blum, “MUMPS, TEDIUM, and productivity,” inProc. MEDCOMP, Philadelphia, PA, 1982, pp. 200–209.

  33. J. Martin,Application Development Without Programmers, Prentice-Hall: Englewood Cliffs, NJ, 1982.

    Google Scholar 

  34. L.A. Belady and M.M. Lehman, “A model of large program development,”IBM Systems Journal vol. 15, pp. 225–252, 1976.

    Google Scholar 

  35. B.I. Blum, “Iterative development of information systems: A case study”,Software-Practice & Experience vol. 6, pp 503–515, 1986.

    Google Scholar 

  36. M.V. Wilkes, “It's all software, now”,Comm. ACM vol. 33, pp. 19–21, 1990.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Additional information

This work was supported in part by the U.S. Navy, Space and Naval Warfare Systems Command (SPAWAR) under contract N00039-89-C-001, task VMAR9 with the Office of Naval Research (ONR).

Rights and permissions

Reprints and permissions

About this article

Cite this article

Blum, B.I. Integration issues elucidated in large-scale information systems development. Journal of Systems Integration 1, 35–53 (1991). https://doi.org/10.1007/BF02265065

Download citation

  • Received:

  • Revised:

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF02265065

Key Words