Nierstrasz, O. and Meijler, T. Requirements for a Composition Language. in Ciancarini, P., Nierstrasz, O.M. and Yonezawa, A. eds. Proceedings of the ECOOP '94 Workshop on Models and Languages for Coordination of Parallelism and Distribution, LNCS 924, Springer, New York, 1995, 147-161.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....definition does not describe the contract precisely enough to allow for reasoning about the contract itself, e.g. for step by step refinement of the system design. The need for enhancing the interface definition is reflected in efforts of the object oriented programming community, e.g. in [8, 41, 55]. As stated in [40] one of the widely accepted approaches is to specify sequences of method calls (communication through the interface) that an object can serve. The sequences constitute the object s protocol, a specification which should be an integral part of the object s interface ....

....approaches is to specify sequences of method calls (communication through the interface) that an object can serve. The sequences constitute the object s protocol, a specification which should be an integral part of the object s interface definition(s) typically modeled as a transition system [8, 19, 40, 41, 55]. In most of the approaches, checking the compliance of the calls to an object with its protocol is expected to be done at run time. As emphasized in [41] rather than simply raising exceptions when protocols are violated, it is desirable to validate clients conformance with protocols statically ....

[Article contains additional citation context not shown here]

O. Nierstrasz, T.D. Meijler, "Requirements for a Composition Language," in Proceedings of the ECOOP `94, Springer Verlag, LNCS 924, 1995, pp. 147--161.

....components is a recurring idea. Early evidence is provided by the utility attributed to UNIX shell scripting. The pipes and filters architecture of the UNIX shell in combination with a scripting language demonstrate the power of flexible composition via the pipelining of streams and commands. In [10], the authors introduce the rationale and requirements for a general purpose composition language. The authors describe a composition language as providing the integration framework between the computational and compositional views of a system. The composition language requirements proposed by the ....

Nierstrasz, O. and Meijler, T. Requirements for a Composition Language. in Ciancarini, P., Nierstrasz, O.M. and Yonezawa, A. eds. Proceedings of the ECOOP '94 Workshop on Models and Languages for Coordination of Parallelism and Distribution, LNCS 924, Springer, New York, 1995, 147-161.

....we can derive a metaprogram instantiating the pattern. For instance, moving features is fundamental to create new levels of indirection widely used in patterns. Architectural systems [SDZ95] allow to exchange connectors representing a communication association. Similarly, composition languages [NM95] focus on the wiring of software components. Metaprograms can easily exchange connectors or compose programs avoiding special languages. Generic programming allows to bind parameters embedded in the code with concrete syntactic content. Metaprogramming can simulate the instantiation of a ....

Oscar Nierstrasz and Theo Dirk Meijler. Requirements for a composition language. In O. Nierstrasz P. Ciancarini and A. Yonezawa, editors, ObjectBased Models and Languages for Concurrent Systems, LNCS 924, pages 147-161. Springer-Verlag, 1995.

....components is a recurring idea. Early evidence is provided by the utility attributed to UNIX shell scripting. The pipes and filters architecture of the UNIX shell in combination with a scripting language demonstrate the power of flexible composition via the pipelining of streams and commands. In [31], the authors introduce the rationale and requirements for a general purpose composition language. The authors describe a composition language as providing the integration framework between the computational and compositional views of a system. The composition language requirements proposed by the ....

Nierstrasz, O. and Meijler, T. Requirements for a Composition Language. in Ciancarini, P., Nierstrasz, O.M. and Yonezawa, A. eds. Proceedings of the ECOOP '94 Workshop on Models and Languages for Coordination of Parallelism and Distribution, LNCS 924, Springer, New York, 1995, 147-161.

....from components. Let us look at the languages for composition first. In [7] a contract language is used to specify reusable components that enables the software developer to explicitly specify the different component roles in a context. Requirements for a composition language are described in [4]. The requirements for a composition language correlate well with requirements on our composition method described later in this section. A source language can be used to specify compositions explicitly, or it can be used for writing a declarative specification of a composition (of a service in ....

....composition (of a service in our case) so that it will be generated automatically. The latter is our approach where services are built based on automatically generated proofs. A formal language for composition is proposed in [2] It follows the requirements for a composition language described in [4]. This language is based on an extension of the # calculus to overcome the limited reusability and extensibility due to position dependent parameters. Here the polyadic communication of names and tuples is replaced by monadic communication of forms. A number of composition frameworks, ....

Oscar Nierstrasz, Theo Dirk Meijler. Requirements for a Composition Language. ECOOP 1994.

....wecan derive a metaprogram instantiating the pattern. For instance, moving features is fundamental to create new levels of indirection widely used in patterns. Architectural systems [SDZ95] allow to exchange connectors representing a communication association. Similarly, composition languages [NM95] focus on the wiring of software components. Metaprograms can easily exchange connectors or compose programs avoiding special languages. Generic programming allows to bind parameters embedded in the code with concrete syntactic content. Metaprogramming can simulate the instantiation of a ....

Oscar Nierstrasz and Theo Dirk Meijler. Requirements for a composition language. In O. Nierstrasz P. Ciancarini and A. Yonezawa, editors, ####### ##### ###### ### ######### ### ########## #######, LNCS 924, pages 147-161. Springer-Verlag, 1995.

....From this perspective, one of the current concerns with components is that the usual signature based interface definitions do not describe the component communication precisely enough. The need for such a definition is reflected in efforts of the object oriented programming community, e.g. in [3, 16, 24, 26]. 1.1. Objects and protocols An object interface definition can be considered as a service definition. As stated in [15] the sequences of requests (method calls) that an object is capable of servicing constitute the object s protocol, a specification of which should be an integral part of the ....

....definition can be considered as a service definition. As stated in [15] the sequences of requests (method calls) that an object is capable of servicing constitute the object s protocol, a specification of which should be an integral part of the object s interface definition(s) A typical way [3, 7, 15, 16, 24, 28] to express the object s protocol is to model it as a finite state machine. There are three basic approaches to specify such a machine: 1) directly as a state transition system, e.g. 15, 24, 28] 2) via a parser accepting the valid request sequences, e.g. 7] 3) as a regular like ....

[Article contains additional citation context not shown here]

O. Nierstrasz, T.D. Meijler, "Requirements for a Composition Language," Proceedings of the ECOOP `94, Springer Verlag, LNCS 924, 1995, pp. 147--161.

....formally specify the behaviour of connectors. Sticking to certain connectors allows the application programmer to guarantee that certain system invariants hold. Ideally, these invariants hold by construction [1] see for example Section 2. 7) Connected components should be components again [12]. At the very end, we can describe an architectural style as an algebra. There are operators over components yielding new components. A style can also be compared to a object oriented framework. A black box framework defines a set of components and connectors. Making this composition algebra more ....

Oscar Nierstrasz and Theo Dirk Meijler, "Requirements for a Composition Language," ObjectBased Models and Langages for Concurrent Systems, P. Ciancarini, O. Nierstrasz and A. Yonezawa (Ed.), LNCS 924, Springer-Verlag, 1995, pp. 147-161.

....Excellent overviews of the software process [24] technology [39] and the academic state of the art [31] are available. Existing solutions primarily focus on software engineering processes (e.g. semiformal interface speci cations [25, 18] and language and architecture based approaches ([26, 30] and [8, 32, 38] respectively) Only recently has work begun to incorporate theoretically grounded compositional concepts into practice [29, 17, 37, 20] ....

O. Nierstrasz and T. Meijler. Requirements for a composition language. In ECOOP'94 Workshop on Models and Languages for Coordination of Parallelism and Distribution, pages 147-161. Springer{Verlag, 1995.

....non functional features of distributed computing can be combined with the functional features of an application in order to produce an executable program. Current object oriented programming languages do not adequately support the composition of software systems from their constituent elements[9, 16, 1, 2]. We are currently researching the use of reflection and meta level programming to support the composition of systems. In addition, we are examining how this support can be made adaptable and extensible, so that additional unsupported features can be added over time. With this aim in mind, a ....

O. Nierstrasz and T. Meijler. Requirements for a composition language. In Workshop on Models and Languages for Coordination of Parallelism and Distribution, pages 147--161, European Conference on Object-Oriented Programming, 1994. SpringerVerlag. LNCS 924.

....From this perspective, one of the current concerns with components is that the usual signature based interface definitions do not describe the component communication precisely enough. The need for such a definition is reflected in efforts of the object oriented programming community, e.g. in [2, 12, 17, 18]. 1.1. Objects and protocols An object interface definition can be considered as a service definition. As stated in [11] the sequences of requests (method calls) that an object is capable of servicing constitute the object s protocol, a specification of which should be an integral part of the ....

....definition can be considered as a service definition. As stated in [11] the sequences of requests (method calls) that an object is capable of servicing constitute the object s protocol, a specification of which should be an integral part of the object s interface definition(s) A typical way [2, 4, 11, 12, 20, 17] to express the object s protocol is to model it as a finite state machine. There are three basic approaches to specify such a machine: 1) directly as a state transition system, e.g. 11, 17, 20] 2) via a parser accepting the valid request sequences, e.g. 4] 3) as a regular like ....

[Article contains additional citation context not shown here]

O. Nierstrasz, T.D. Meijler, "Requirements for a Composition Language," Proceedings of the ECOOP `94, Springer Verlag, LNCS 924, 1995, pp. 147--161.

....The limitations of the standard service definition in many programming languages are that they do not take into account availability and responsiveness of services. As stated in [8] the sequences of requests that an object is capable of servicing constitute the object s protocol. A typical way [2, 3, 7, 8, 9, 11, 28, 32, 33] to express the object s protocol is to model it as a finite state machine. There are three basic approaches to specify such a machine: 1) directly as state transition system, e.g. 8, 29] 2) via a parser accepting the valid request sequences of the protocol, e.g. 7] 3) as a regular like ....

....and availability of object s service. In all these synchronization schemes, checking the compliance of calls to an object with its protocol was expected to be done at run time. However, in [8] it is proposed to specify object protocols as an integral part of an object interface. As emphasized in [9], rather than simply raising exceptions when protocols are violated, it would be desirable to statically validate clients conformance to protocols and to determine automatically if a protocol can be formally viewed as a subtype of another one. Moreover, in [8] a subtyping relationship on ....

Nierstrasz, O, Meijler, T. D.: Requirements for a Composition Language. In Proceedings of the ECOOP `94, Springer Verlag, LNCS 924, 1995, pp. 147-161.

.... as wel as the specification of architectural styl es by defining di#erent kinds of connectors.In our view, a compositionl anguage woul d be a combination of an architectural descriptionl anguage and a scriptingl anguage and coul al so serve as the back end to a visual composition environment [NM95] We are present l prototyping a compositionl anguage calH d Piccola ( Pi Cal cul us based Composition Language ) whoseformal semantics is specified in terms of the # cal ul s [Mil ] In our view, a general purpose compositionl anguage must beformal to support reasoning about component ....

Oscar Nierstrasz and Theo Dirk Meijl r.Requirements for a Composition Language. In Paol Ciancarini, Oscar Nierstrasz, and Akinori Yonezawa, editors, Object-Based Models and Languages for Concurrent Systems, LNCS 924, pages 147--161.Springer, 1995.

....them out of composable software components. Early work on this area concentrated on the role of multiple inheritance in supporting code reuse [18, 23] more recently, there has been a great deal of interest in system design by composition of components at an abstract level of system architecture [26, 4, 24], or design [4, 3] The parameterised approach described here seems especially useful and widely applicable [7, 29] We hope to pursue this area of research to support system design and construction through an extension of hidden parameterised programming to allow composition of modules with ....

Oscar Nierstrasz and Theo Dirk Meijer. Requirements for a composition language. In P. Ciancarini, O. Nierstrasz, and A. Yonezawa, editors, Proceedings of the ECOOP '94 Workshop on Coordination Languages. Springer-Verlag Lecture Notes in Computer Science, to appear, 1995.

....at the language level as features of a new object model. In particular it is argued that groupware applications required to inter work with other applications are best constructed as open systems. By this we mean that they are best constructed as recomposable compositions of collaborating objects [Nierstrasz, 1995]. The open systems approach is impeded by limitations of current object oriented and other programming techniques, in particular their failure to support object composition [Nierstrasz, 1995] For example, abstract data types provide no means of expressing inter object behavioural relationships ....

.... By this we mean that they are best constructed as recomposable compositions of collaborating objects [Nierstrasz, 1995] The open systems approach is impeded by limitations of current object oriented and other programming techniques, in particular their failure to support object composition [Nierstrasz, 1995]. For example, abstract data types provide no means of expressing inter object behavioural relationships [Sullivan and Notkin, 1992] These relationships lay buried in the code of methods. Thus the object oriented approach, while having many advantages, does not allow us to specify the behaviour ....

[Article contains additional citation context not shown here]

Nierstrasz, O. (1995). Requirements for a composition language. In Proceedings of the ECOOP 94 workshop on Models and Languages for Coordination and Parallelism and Distribution, LNCS. Springer Verlag.

.... was outlined in Viewing Objects as Patterns of Communicating Agents [NP90] Abacus was a first attempt to implement a Piccola like language [Nie90] A research agenda for developing a composition language was first described in the position paper Requirements for a Composition Language [NM95]. This led first of all to some experiments using Milner s # calculus [MPW92] and its implementation in the PICT programming language [PT95] to model various sorts of software abstractions [NSL96, LSN96] A key result of this work was the insight that extensible records, i.e. forms, provided a ....

Oscar Nierstrasz and Theo Dirk Meijler. Requirements for a composition language. In Paolo Ciancarini, Oscar Nierstrasz, and Akinori Yonezawa, editors, Object-Based Models and Langages for Concurrent Systems, volume 924 of LNCS, pages 147--161. Springer-Verlag, 1995.

....a clear separation of computational elements and their relationships. However, currently there exists no general purpose composition language that (i) offers explicit support for the paradigm introduced above and (ii) fulfills the requirements for a composition language elaborated previously [NM95a, NM95b, NSL96] Object oriented programming languages and design techniques, for example, go a long way towards supporting component based development, and the languages are nearly ideal for implementing components, but current practice actually hinders component based development in a number of ....

Oscar Nierstrasz and Theo Dirk Meijler. Requirements for a Composition Language. In Paolo Ciancarini, Oscar Nierstrasz, and Akinori Yonezawa, editors, Object-Based Models and Languages for Concurrent Systems, LNCS 924, pages 147--161. Springer, 1995.

....how this language can be used to plug components together. 1. 1 Introduction One of the key challenges for programming language designers today is to provide the tools that will allow software engineers to develop robust, flexible, distributed applications from plug compatible software components [NM95]. Current object oriented programming languages typically provide an ad hoc collection of mechanisms for constructing and composing objects, and they are based on ad hoc semantic foundations (if any at all) Nie93] A language for composing open systems, however, should be based on a rigorous ....

....open systems, however, should be based on a rigorous formal foundation in which concurrency, communication, abstraction, and composition are primitives. In fact, the development of both the formal foundation and the language will be driven by a set of key requirements for a composition language [NM95]: encapsulation, objects as processes, components as abstractions, plug compatibility, a formal object model, and scalability. Appeared in Foundations of Component based Systems, edited by Gary T. Leavens and Mularli Sitaraman, c # Cambridge University Press 2000, pp. 69 90. 2 Lumpe ....

Nierstrasz, O. and Meijler, T. D. Requirements for a Composition Language. In Ciancarini, P., Nierstrasz, O., and Yonezawa, A., editors, Object-Based Models and Languages for Concurrent Systems, LNCS 924, pages 147--161. Springer, 1995.

....known in advance due to changing needs and technological demands. Traditional application development methods are inadequate to the extent that they assume closed and fixed requirements, and therefore result in inflexible systems that cannot be easily adapted to unexpected changes in requirements [14]. We can distinguish between Open Systems Requirements that are essentially computational (i.e. dealing with functionality, distribution, concurrency, etc. and those that are essentially compositional (i.e. dealing with evolution, interoperability, etc. A complete approach should take ....

....or widely practised. A Component Oriented Software Lifecycle (figure 5) must take into account that application development (the construction of applications from component frameworks) is a separate activity from component engineering (the iterative development of the framework itself) [14]. Component engineering is capital investment whereas application development recovers the investment. Since application development is ideally driven by component engineering, analysis and design are largely done already. The hard parts are: identifying the appropriate component framework to ....

Oscar Nierstrasz and Theo Dirk Meijler, "Requirements for a Composition Language," Object -Based Models and Languages for Concurrent Systems, P. Ciancarini, O. Nierstrasz and A. Yonezawa (Ed.), LNCS 924, Springer-Verlag, 1995, pp. 147-161.

No context found.

Nierstrasz, O. and Meijler, T. Requirements for a Composition Language. in Ciancarini, P., Nierstrasz, O.M. and Yonezawa, A. eds. Proceedings of the ECOOP '94 Workshop on Models and Languages for Coordination of Parallelism and Distribution, LNCS 924, Springer, New York, 1995, 147-161.

No context found.

Oscar Nierstrasz and Theo Dirk Meijler. Requirements for a composition language. In Paolo Ciancarini, Oscar Nierstrasz, and Akinori Yonezawa, editors, Object-Based Models and Langages for Concurrent Systems, volume 924 of LNCS, pages 147--161. Springer-Verlag, 1995.

No context found.

Oscar Nierstrasz and Theo Dirk Meijler. Requirements for a composition language. In Proceedings of the ECOOP '94 workshop on Models and Languages for Coordination of Parallelism and Distribution, pages 147161. Springer-Verlag, 1995.

No context found.

Oscar Nierstrasz and Theo Dirk Meijler. Requirements for a composition language. In Paolo Ciancarini, Oscar Nierstrasz, and Akinori Yonezawa, editors, Object-Based Models and Langages for Concurrent Systems, volume 924 of LNCS, pages 147--161. Springer-Verlag, 1995.

No context found.

O. Nierstrasz and T. D. Meijler. Requirements for a Composition Language. In P. Ciancarini, O. Nierstrasz, and A. Yonezawa, editors, Object-Based Models and Languages for Concurrent Systems,LNCS 924, pages 147--161. Springer, 1995.

No context found.

Nierstrasz, O., and T.D. Meijler (1995). Requirements for a Composition Language. In Ciancarini, P., O. Nierstrasz, A. Yonezawa (Eds.). Object-Based Models and Langages for Concurrent Systems, 147---161. Springer-Verlag.

First 50 documents

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