Efficient program composition on Parix by the Ensemble methodology

Abstract

Abstract

Associating composition of Petri net specifications with application designs in GRADE

“…There can be seen six Selectors around the Servers. Three of them connected to "Serv[3]" (named "Selector [4]", "Selector [5]" and "Selector [6]"), two of them connected to "Serv[2]" (named "Selector[2]" and "Selector[3]") and only one of them connected to "Serv[1]". The application is executed directly from this environment.…”

“…Our long-term aim is to create an integrated software engineering support tool for the development of reliable message passing applications. Selector [4] Selector [5] Selector [6] Server …”

“…However, this approach had the disadvantage that GRAPNEL code of processes could not be reused through different application. To overcome this problem, w e have decided to follow the concept of re-usable program components similarly to that of Ensemble methodology [1] [4] [5]. In this way, the programmer can create and use processes individually as reusable program components which can be embedded into various applications using different inter connection schemes.…”

Specification composition for the verification of message passing program composition

“…We have only outlined the aspects of Ensemble methodology and its tools which are relevant in the context of this paper. A detailed description of Ensemble in PVM and Parix may be found in (Cotronis, 1996a) and (Cotronis, 1996b), respectively.…”

“…We have developed a message passing program implementation methodology, called Ensemble (Cotronis, 1996a;Cotronis 1996b), by which message passing applications are composed out of reusable software components by binding their communication channels. The emergence of Message Passing Environments (MPE), such as PVM (Geist et al, 1994), MPI (McBryan, 1994), Parix, provide a useful abstraction of the underlying architecture simplifying implementation.…”