6 citations found. Retrieving documents...
G. Boudier, F. Gallo, R. Minot, and I. Thomas. An overview of PCTE and PCTE+. ACM SIGPLAN Notices, 24(2):248-257,. 1989.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Expanding the Repertoire of Process-based Tool Integration - Valetto (1994)   (1 citation)  (Correct)

....data repository has been employed quite widely, for example also by several of the projects aimed to define standards for building generic tools with a high degree of portability and interoperability, and therefore widely reusable, even if only under the standard s specifications. PCTE [50] [17] is probably the most representative and generally accepted example of such standards. The goal of PCTE is to create a set of services and facilities, called a public tool interface, complete enough to support tool writers in very different situations and domains; many SDE prototypes and projects ....

F. Gallo, G. Boudier, and I. Thomas. Overview of PCTE and PCTE+. ACM SIGPLAN Notices, 24(2), February 1989.


Enveloping Sophisticated Tools into Process-Centered.. - Valetto, Kaiser (1996)   (8 citations)  (Correct)

....objectoriented data repository has been employed quite widely, including by several of the projects aimed to define standards for building generic tools with a high degree of portability and interoperability, and therefore widely reusable although only under the standard s specifications. PCTE [25] is probably the best known of such standards. The goal of PCTE is to create a set of services and facilities, called a public tool interface, complete enough to support tool implementors in very different situations and domains; many environment prototypes and projects (e.g. 63] 12] 27] ....

F. Gallo, G. Boudier, and I. Thomas. Overview of PCTE and PCTE+. ACM SIGPLAN Notices, 24(2), February 1989.


Classification of and Experimentation on Tool Interfacing in.. - Yang, Han (1996)   (Correct)

.... be required because the prover s internal representation is very different from that of the editor as in the case of integrating the Z editor Hippo [18] There are two basic approaches to pursuing looselycoupled interfacing: one is to use a purpose built database or object base as in PCTE [2] and CAIS [8] and the other is to use the message passing paradigm as in Field [11] and SoftBench [3] Some hybrid models combining these basic approaches have also been investigated [7, 10] In summary, the experimentation of this class can again be applied to the similar cases in the tool ....

G. Boudier, F. Gallo, R. Minot, and I. Thomas. An overview of PCTE and PCTE+. ACM SIGPLAN Notices, 24(2):248--257, Feb. 1989.


Expanding the Repertoire of Process-based Tool Integration - Valetto (1994)   (1 citation)  (Correct)

....their operations. Here, the message server and the interfaces constitute the subsystem in charge of tool integration. This component is often referred to as a message bus. Such an approach is used, among others, by Field [22] Conversation Builder [17] 7] and SoftBench [6] 13] PCTE [27] [11] is one of the most representative examples of efforts directed to define a widely recognized and accepted public standard for building tools with better portability. The aim is to create a set of services and facilities, called a public tool interface, complete enough to support tool writers in ....

F. Gallo, G. Boudier, and I. Thomas. Overview of PCTE and PCTE+. ACM SIGPLAN Notices, 24(2), February 1989.


Process Integration in CASE Environments - Peiwei Mi (1992)   (17 citations)  (Correct)

....Luo, and Yu ling Young contributed to implementation effort. 1 Introduction Current research in CASE Environments (CASEEs) has been focused on two kinds of integration: tool integration and object integration. Tool integration deals with the implicit invocation and control of development tools [BGMT89, GI90, Tho89]. Object integration, on the other hand, provides a consistent view of development artifacts and easy to use interfaces to generate, access, and control them [AHM89, CS91] This paper presents a higher level of integration called process integration that explicitly represents development ....

G. Boudier, F. Gallo, R. Minot, and I. Thomas. An Overview of PCTE and PCTE+. ACM SIGPLAN Notice, pages 226--227, Feb 1989.


and Jun Han Software Tool Interfacing - Productivity-Centred Approach For (1998)   (Correct)

No context found.

G. Boudier, F. Gallo, R. Minot, and I. Thomas. An overview of PCTE and PCTE+. ACM SIGPLAN Notices, 24(2):248-257,. 1989.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC