Adding control integration to PCTE
The PCTE interfaces provide data-integration services. In a good Software Engineering Environment (SEE), however, more is needed: control integration to automatically start tools and share services. We report on our intermediate practical experience of adding control integration to PCTE. More precisely, we show how Broadcast Message Services can be layered on the PCTE platform thus forming a SEE framework that spans the tool integration dimensions.
KeywordsCASE Software Engineering Environments PCTE Soft-Bench
Unable to display preview. Download preview PDF.
- A. Earl. A Reference Model for Computer Assisted Software Engineering Environment Frameworks. Technical Report ECMA/TR/90/55, ECMA, 17 August 1990.Google Scholar
- M. R. Cagan. The HP SoftBench Environment: An Architecture for a New Generation of Software Tools. Hewlett-Packard Journal, 41(3):36–47, June 1990.Google Scholar
- A. O. Deininger and C. V. Fernandez. Making Computer Behaviour Consistent: The OSF/Motif Graphical User Interface. Hewlett-Packard Journal, 41(3):6–26, June 1990.Google Scholar
- C. Gerety. A New Generation of Software Development Tools. Hewlett-Packard Journal, 41(3):48–58, June 1990.Google Scholar
- F.Gallo G.Boudier and I.Thomas. Overview of PCTE and PCTE+. ACM SIGPLAN Notices, 24(2), February 1989.Google Scholar
- I.Thomas. PCTE Interfaces: Supporting Tools in Software Engineering Environments. IEEE Software, November 1989.Google Scholar
- Brussels Commission of the European Communities. PCTE Functional Specifications, Version 1.5, November 1988.Google Scholar
- Software Sciences Ltd. GIE Emeraude, Selenia Industrie Elettroniche Associate. PCTE+ Functional Specification, Issue 3, October 1988.Google Scholar
- Portable Common Tool Environment — Abstract Specification. Technical Report ECMA Standard 149, ECMA, Geneva, December 1990.Google Scholar