21 citations found. Retrieving documents...
M. Maybee, D. Heimbigner, and L. Osterweil. Multilanguage Interoperability in Distributed Systems: Experience Report. University of Massachusetts Amherst, Report UM-CS-1995-075, August 1995.

 Home/Search   Document Details and Download   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Exploiting Architectural Style to Develop a Family of.. - Nenad Medvidovic And (1997)   (5 citations)  (Correct)

....(OS) process. The framework has been implemented in C and Java; 3 a subset is also available in Ada. The size of the framework in both C and Java is approximately 3000 commented source lines of code. We have been able to successfully reuse the Q interprocess communication (IPC) library [16] to enable message exchange between C2 components implemented in C and Ada. Similar functionality for Java C2 components is under development. 3. The C and Java frameworks and several simple applications developed with them are available at http: www.ics.uci.edu pub arch . Fig. 5. An OTS ....

....of other components in the architecture, an inter process (IPC) connector must be employed to enable their communication. A number of existing systems provide this capability. For example, we were able to accomplish this task for C and Ada components relatively easily using the Q software bus [16]. If the OTS component must execute in its own thread of control, an inter thread connector must be employed. This was accomplished in the case of the Java AWT graphics toolkit. If the OTS component executes in its own process, an IPC connector must again be employed. If the OTS component ....

M. J. Maybee, D. H. Heimbigner, and L. J. Osterweil. Multilanguage Interoperability in Distributed Systems:


Process Engine Interoperability: - An Experiment Jacky   (Correct)

....languages, and that there may not be a type correspondence from a language to another. For instance, CoShell language defines type real while Adele does not, Adele defines type set , not PW. The way we solved the problem was somehow ad hoc comparing to other more opened systems like CORBA or Q [MHO96] among other. Indeed, while these systems use a neutral intermediate representation for passing data between languageheterogeneous tools, we make direct correspondence on the two sides. 4.2 Activity integration Process Weaver has a modelling approach centered around activity: the process ....

M. Maybee, D. Heimbigner, and L. Osterwiel. Multilanguage interoperability in distributed systems: Experience report. In Proc. of the 18th Int'l Conf. on Software Engineering, Berlin, Germany, March 25-30 1996.


A Family of Software Architecture Implementation Frameworks - Nikunj (2002)   (1 citation)  (Correct)

.... these architectural approaches have consistently failed to address the relationship between the abstract architectural models and concrete system implementations [ 16] On the other hand, a number of software interoperability technologies have emerged primarily, though not exclusively (e.g. [11,22,25]) from industry [27,32,35] These technologies provide solutions for composing implementation level, coarse grain software components, giving developers powerful system building tools. However, although it has been shown that they indeed influence the architectural characteristics of systems [4] ....

....languages (multiple flavors of C , Ada, Java, and Python) allowing developers to select a framework based on their preferred programming language, instead of the other way around. The frameworks employ diffbrent OTS component interaction mechanisms (e.g. Java RMI [33] CORBA [18] Q [11], Polylith [25] giving developers the flexibility to select the interaction mechanism with which they are most familiar and or com fortable, or the mechanism that is the best fit for their current application needs. The frameworks leverage their explicit connectors and the OTS interaction ....

M. Maybee, D. Heimbigner, L.J. Osterweil. Multilanguage Interoperability in Distributed Systems: Experience Report. In Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, March 1996.


Chimera: Hypermedia for Heterogeneous Software.. - Anderson, Taylor.. (2000)   (9 citations)  (Correct)

....provide hierarchical composition. Since heterogeneous environments are most often multilingual (i.e. multiple programming and scripting languages) and distributed, the generic architecture and our implementation is client server based and a multilingual interprocess communication mechanism (Q [43]) is utilized in our implementation. Example. A simple example demonstrates the concepts discussed so far (See Figure 1) Three separate applications utilize hypermedia services to provide a simple SDE. An integrated text editor (XEmacs) allows anchors to be created over ASCII source code while ....

Maybee, M. J., Heimbigner, D. H., and Osterweil, L. J. (1996). Multilanguage Interoperability in Distributed Systems: Experience Report. In Proceedings of the Eighteenth International Conference on Software Engineering. Berlin, Germany.


Polylingual Systems: An Approach To Seamless Interoperability - Barrett (1998)   (1 citation)  (Correct)

....HRPC focuses on the dynamic, automatic location and activation of callees as they are needed. Mercury focuses on asynchronous RPC, using a mechanism called a call stream to guarantee that procedure calls and their return values reach their recipients in the same order that they were sent. Q [52] is an RPC mechanism that provides point to point communication between C and Ada programs. The promise approach [48] is similar to asynchronous remote procedure calls but uses the principle of lazy evaluation. In this approach, if a remote procedure call is made that should return a value of ....

Maybee, M. J., Heimbigner, D. M., and Osterweil, L. J. Multilanguage interoperability in distributed systems: Experience report. In Proceedings of the 18th International Conference on Software Engineering (Berlin, Mar. 1996).


Automated Support for Seamless Interoperability in.. - Barrett, Kaplan, Wileden (1996)   (10 citations)  (Correct)

....language to invoke a subprogram s written in another. The object code modules of p and s are linked, and the foreign function call is accomplished within a single address space. For calling across address spaces, remote procedure calls [BN84] have been extended to cross language boundaries (e.g. MHO96] Both foreign function calls and remote procedure calls represent relatively low level approaches to interoperability, and as a result they are generally far from seamless because application programmers frequently must deal with details of parameter marshalling and because complex data types ....

Mark J. Maybee, Dennis H. Heimbigner, and Leon J. Osterweil. Multilanguage interoperability in distributed systems. In Proceedings of the International Conference on Software Engineering, March 1996.


An Agent-Based Approach to Building Multidisciplinary Problem.. - Drashansky (1996)   (3 citations)  (Correct)

....triggers I O and communication. Their software library and run time system is called The Programmers Playground and is motivated by the development of a distributed multimedia application. Interoperability support for multilingual, heterogeneous component based software systems is presented in [MHO95] The system Q (developed in conjunction with the Arcadia project) provides the communication, translation, and invocation support for inter language remote procedure calls among software components written in different programming languages. An interesting approach to component integration ....

M. Maybee, D. Heimbigner, and L. Osterweil. Multilanguage Interoperability in Distributed Systems: Experience Report. Technical Report CU-CS-779-95, Department of Computer Science, University of Colorado at Boulder, August 1995.


Supporting Distributed Workflow Using HTTP - Kammer, Bolcer, al. (1998)   (1 citation)  (Correct)

....Our second application also reflects an instance where there are multiple participants in the process with different roles. In this web based learning (WBL) process, 1. Note that this raises key issues of interoperability that have been explored in depth by other authors. See, for example, [1, 12, 16, 19] developed for a workstation manufacturer, there are course designers who provide the overall structure of the activities, content providers who provide the information for the courses, students who review the material and are tested on it, and finally course managers who monitor ....

M. J. Maybee, D H. Heimbigner, and Leon J. Osterweil. Multilanguage interoperability in distributed systems: experience report. In Proceedings of the 18th International Conference on Software Engineering, March 1996.


Transparent Interoperability in Distributed Processing - Uszok, Zielinski, Czajkowski (1996)   (Correct)

....for different purposes. Thus an environment enabling integration of modules programmed in different computational models is very expected. One of the first attempts at constructing the multi paradigm environment was the Mixed language System [1] from the University of Arizona and the Q system [3] from the Colorado University. Now, CORBA complaint [5] systems are 1 This work was sponsored by the Polish State Committee of Scientific Research (KBN) under grant no. 8T11C01210 Grzegorz Czajkowski is currently at Department of Computer Science, Cornell University, Ithaca, NY 14853, email: ....

M. Maybee, D. Heinbigner, L. Osterweil, Multilanguage Interoperability in Distributed Systems: Experience Report, TR of Universityy of Colorado (1995)


A Component- and Message-Based Architectural Style.. - Taylor.. (1996)   (73 citations)  (Correct)

....of two kinds of implementation connectors. Connectors which provide communication between components in a single operating system process pass messages in memory as simple C data structures. Connectors which span multiple processes are implemented with the Q interprocess communication mechanism [17]. Argo generates one main procedure for each process in the implementation architecture. Each main procedure creates, connects, and schedules the implementation components for its process. Those processes can be run to form the executing system. The main procedure of the KLAX example and most of ....

M. J. Maybee, D. H. Heimbigner, and L. J. Osterweil. "Multilanguage Interoperability in Distributed Systems: Experience Report." In Proceedings of the Eighteenth International Conference on Software Engineering, Berlin, Germany, March 1996. Also issued as CU Technical Report CUCS -782-95.


A Classification and Comparison Framework for Software.. - Medvidovic (1996)   (94 citations)  (Correct)

....C2 applications are subclassed from the appropriate framework classes, allowing developers to focus on application level issues. The framework has been implemented in C and Java; its subset is also available in Ada. We have been able to successfully reuse the Q interprocess communication library [MHO96] to enable message exchange between C2 components implemented in C and Ada. As already discussed, Darwin, MetaH, and UniCon require preexisting component implementations in C , Ada, and C, respectively, in order to generate applications. Rapide can construct executable systems in the same ....

M. J. Maybee, D. H. Heimbigner, and L. J. Osterweil. Multilanguage Interoperability in Distributed Systems: Experience Report. In Proceedings of the Eighteenth International Conference on Software Engineering, Berlin, Germany, March 1996. Also issued as CU Technical Report CU-CS-782-95.


Software Environments in Support of Wide-Area Development - Heimbigner, King, Wolf (2000)   Self-citation (Heimbigner)   (Correct)

No context found.

M. Maybee, D. Heimbigner, and L. J. Osterweil, "Multilanguage Interoperability in Distributed Systems," Proc. of the 18th Intl. Conf. on Software Engineering, March 1996, Berlin, Germany.


Verifying Properties of Distributed Systems: Prospects for.. - Clarke, Osterweil (1998)   Self-citation (Osterweil)   (Correct)

....speed and response time, can increase robustness, and can provide the flexibility needed to facilitate component based(plug and play) approaches to software development. There has been considerable interest in developing glue technology or middleware to facilitate interoperability (e.g. 2] and [12]) to support component based development. Unfortunately, there has been far less interest in the critical issue of how these distributed systems are be validated to assure that they will perform acceptably. Because of non deterministic computation and the potential for the parallel execution of ....

M. J. Maybee, D. H.Heimbigner, and Leon J. Osterweil, "Multilanguage Interoperability in Distributed Systems: Experience Report ", Proceedings of the Eighteenth International Conference on Software Engineering, pp. 451-463, Berlin, Germany, March 25-30, 1996.


Software Release Management - van der Hoek, Hall, Heimbigner, Wolf (1996)   (9 citations)  Self-citation (Heimbigner)   (Correct)

....the release management process. 4.2.2 Modifying a Release SRM allows a developer to modify the information describing a release. One simple reason is that metadata, such as a contact person, may change. A more important reason is to allow underlying dependencies to change. For example, Q CORBA [13], as mentioned above, depends on Arpc [9] It happened that a new version of Arpc was created to fix a bug. This fix did not, however, affect the Arpc interface, so no changes to Q CORBA were required. Once it was determined that Q CORBA worked properly with the new version of Arpc, and only then, ....

....inter organization communication about interdependent components. 6 EXPERIENCE SRM has been implemented using a wide variety of technologies, including Java, MIF, HTML [12] and Tcl Tk. In addition, the underlying repository, NUCM, has been implemented as a CORBA object using the Q CORBA system [13]. Naturally, putting these technologies together and deploying the resulting system turned out to be a non trivial exercise. In fact, because some of the technologies are new, using them for a complex task such as SRM revealed significant problems for them in their own right. Below, we discuss the ....

M.J. Maybee, D.M. Heimbigner, and L.J. Osterweil. Multilanguage Interoperability in Distributed Systems. In Proceedings of the 18th International Conference on Software Engineering, pages 451--463. Association for Computer Machinery, March 1996.


Post-Deployment Configuration Management - Heimbigner, Wolf (1996)   (1 citation)  Self-citation (Heimbigner)   (Correct)

....can become a major overhead on the original installation task . We also note that the problem is complicated if (1) the local site already has some of the dependent software installed, and (2) if ranges of versions of dependent software can be used (i.e. version 3.1 through version 3. 3 of Q [3]) We are addressing this problem by constructing a release manager on top of NUCM [6] This release manager can maintain dependency information and help bring in proper versions of all required software. 274 4 Parameterization Software is usually parameterized to take local context into ....

....change the installation, parameterization, or instantiation of the system. We are just beginning to address the re configuration area and hope to build on the technology we develop for installation, parameterization, and instantiation, as well as enhancing our own distributed object technology (Q [3]) to support dynamic reconfiguration. Acknowledgements. This material is based upon work sponsored by the Air Force Materiel Command, Rome Laboratory, and the Advanced Research Projects Agency under Contract Number F30602 94 C 0253. The content of the information does not necessarily reflect the ....

Mark Maybee, Dennis Heimbigner, and Leon J. Osterweil. Multilanguage Interoperability in Distributed Systems. In Proceedings of the 18th International Conference on Software Engineering. IEEE Computer Society, March 1996.


A Reusable, Distributed Repository for.. - van der Hoek.. (1998)   (2 citations)  Self-citation (Heimbigner)   (Correct)

.... [46] Our initial approach was to experiment with a rather di#erent alternative, namely the CORBA standard for distributed object programming [12] For a variety of reasons, we implemented NUCM twice, first with the Orbeline CORBA engine [38] and subsequently with a CORBA implementation called Q [29]. However, in both cases it turned out that CORBA was not the right platform to build a distributed CM repository. The following two reasons are the primary sources of this mismatch. 1. CORBA is not well suited for bulk data transfer. The type system of CORBA does not include a type that allows ....

M.J. Maybee, D.M. Heimbigner, and L.J. Osterweil. Multilanguage Interoperability in Distributed Systems. In Proceedings of the 18th International Conference on Software Engineering, pages 451--463. Association for Computer Machinery, March 1996.


Software Release Management - van der Hoek, Hall, Heimbigner, Wolf (1997)   (9 citations)  Self-citation (Heimbigner)   (Correct)

....retrieve the component when needed. 168 Modifying a Release. SRM allows a developer to modify the information describing a release. One simple reason is that metadata, such as a contact person, may change. A more important reason is to allow underlying dependencies to change. For example, Q 3. 3 [12], as mentioned above, depends on Arpc 403.4 [9] It happened that a new version of Arpc was created to fix a bug. This fix did not, however, affect the Arpc interface, so no changes to Q 3.3 were required. Once it was determined that Q 3.3 worked properly with the new version of Arpc, and only ....

M.J. Maybee, D.M. Heimbigner, and L.J. Osterweil. Multilanguage Interoperability in Distributed Systems. In Proceedings of the 18th International Conference on Software Engineering, pages 451--463. Association for Computer Machinery, March 1996.


Maintaining Semantics In The Integration Of Network Interoperable.. - Kern (1997)   (Correct)

No context found.

M. Maybee, D. Heimbigner, and L. Osterweil. Multilanguage Interoperability in Distributed Systems: Experience Report. University of Massachusetts Amherst, Report UM-CS-1995-075, August 1995.


Analysis Of Application Of Multi-Language Design.. - Stuikys.. (2003)   (Correct)

No context found.

M. Maybee, D. M. Heimbigner, L. Osterweil. Multilanguage Interoperability in Distributed Systems. Proc. of 18th Int. Conference on Software Engineering, March 1996.


Interoperability and Distribution of Process-Sensitive Systems - Estublier, Barghouti (1998)   (Correct)

No context found.

M. Maybee, D. Heimbigner, and L. Osterweil. Multilanguage Interoperability in Distributed Systems: Experience report. In Proc. ICSE18, 18th International Conference. on Software Engineering, Berlin, Germany, March 25-30 1996.


tion of components allows the architecture of the.. - Acknowledgments The..   (Correct)

No context found.

Maybee, Mark J., Dennis H. Heimbigner, Leon J. Osterweil, "Multilanguage Interoperability in Distributed Systems: EXPERIENCE REPORT" Proceedings of the 18th International Conference on Software Engineering (ICSE-18), March 25-29, 1996, pp 451-463.

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