Understanding integration in a software development environment: Issues and illustrations
- 28 Downloads
In the past ten years there has been a great deal of interest in the concept of a Software Development Environment (SDE) as a complete, unifying framework of services supporting most (or all) phases of software development and maintenance. We identify three levels at which the issue of integration in a SDE arises as a key concept—at the mechanism level (interoperability of the hardware and basic software), at the end-user services level (combining the methods and paradigms of the various tools), and at the process level (adapting end-user services to the working practices of different users, projects and organizations).
In this article we examine SDEs from an integration perspective, describing the previous work in this area and analyzing the integration issues that must be addressed in an SDE. For illustrative purposes, a particular focus of the paper is the configuration management aspects of a SDE.
Key WordsSoftware Development Environment Configuration management CASE IPSE integration
Unable to display preview. Download preview PDF.
- 1.E.H. Bersoff, V.D. Henderson, and S.G. Siegel,Software Configuration Management. Prentice-Hall, 1980.Google Scholar
- 2.G. Boudier, T. Gallo, R. Minot, and I. Thomas, An overview of PCTE and PCTE+,” inProceedings of ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Engineering Environments, Boston, MA, 1988.Google Scholar
- 3.A.W. Brown (ed.), “Integrated project support environments: the Aspect project,”The APIC Series. Academic Press Ltd.: London, England, 1991.Google Scholar
- 4.M.R. Cagan, “The HP SoftBench environment: an architecture for a new generation of software tools,”Hewlett-Packard Journal, pp. 36–47, June 1990.Google Scholar
- 5.W. Courington,The Network Software Environment, Sun Microsystems, Inc., Mountain View, CA., 1989.Google Scholar
- 6.S. Dart, “Concepts in configuration management systems,”Proceedings of the 3rd International Workshop on Software Configuration Management, pp. 1–18, June 1991.Google Scholar
- 7.M. Dowson, “ISTAR—an integrated project support environment,”Proceedings of 2nd ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Engineering Environments, December, 1986.Google Scholar
- 8.P. Feiler, S. Dart, and G. Downey,Evaluation of the Rational Environment. Tech. Rept. CMU/SEI-88-TR-15, ADA 198934. Software Engineering Institute, Carnegie mellon University, July, 1988.Google Scholar
- 9.P.H. Feiler,Configuration Management Models in Commerical Environments. Tech. Rept. CMU/SE191-TR-7, Software Engineering Institute, Carnegie Mellon University, March, 1991.Google Scholar
- 10.M. Graham and D. Miller,ISTAR Evaluation. Tech. Rept. CMU/SEI-88-TR-3, ADA201345, Software Engineering Institute, Carnegie Mellon University, 1989.Google Scholar
- 11.D. Leblang, and R. Chase, “Computer-aided software engineering in a distributed workstation environment,”Proceedings of the SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, Pittsburgh, PA, pp. 104–112, April, 1984.Google Scholar
- 12.W. Paseman, “Tools on a new level,”Unix Review 7, vol. 6 pp. 69–77, June 1989.Google Scholar
- 13.M.H. Penedo, and E.D. Stuckle, “PMBD—a project master database for software engineering environments,”Proceedings of 8th International IEEE Conference on Software Engineering, London, England, August, 1985.Google Scholar
- 14.T. Strelich, “The Software Life Cycle Support Environment (SLCSE): A Computer Based Fraemwork for Developing Software Systems,”Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, Boston, MA., November, 1988.Google Scholar
- 15.I. Thomas, “Tool integration in the PACT environment,”Proceedings of 11th International IEEE Conference on Software Engineering, May, 1989.Google Scholar
- 16.A. Wasserman, “Tool integration in software engineering environments,” inSoftware Engineering Environments, F. Long, (ed.), Springer-Verlag, NY, 1990, pp. 138–150.Google Scholar