T. Meijler and O. Nierstrasz. Beyond Objects: Components. In WCOP'98 Proceedings of the Third International Workshop on Component-Oriented Programming, 1998.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....by the developer to support the functionality required from a given application domain. The framework further distinguishes between the notions of compound interactions, coordination of concurrency, and synchronization. Such notions are studied in interactive systems using object oriented [NGT92, MN98, Joh97, Sch95, SFJ96] or agent oriented [SC99] techniques. In this case, our work is intended as a study investigating how to support similar techniques in computational logic setting. Compared with our previous formulation of games using object level programs [SS97, Sta96] this work introduces metaprograms to ....

T. D. Meijler and O. Nierstrasz. Beyond objects: Components. In P. Papazoglou and G. Schlageter, editors, Cooperative Information Systems: Trends and Directions. Academic Press, 1998.

....3 Email: frederic duclosds fr.com ( 2002 Published by Elsevier Science B. V. other fields each targeting more or less specific problems. There have been many trials to describe the concepts behind CBSE, either from a technical point of view [1] or from a more conceptual one [9,8]. It is interesting to point out that industrial component models contain important concepts, but unfortunately they are often obscured by abundant implementation details which makes them hard to understand, to master and to modify. These limitations have led us to develop a small component ....

Theo Dirk Meijler and Oscar Nierstrasz. Beyond Objects: Components. In M.P. Papazoglou and G. Schlageter, editors, Cooperative Information Systems: Current Trends and Directions, pages 49-78. Academic Press, November 1997.

....to support transactions, there must be a transaction manager readily available somewhere in the system. This is important architectural knowledge that should be prefabricated such that it can be reused for the implementation of different transaction algorithms. Component framework technology [25, 17] supports this idea by providing the system developer with a semicomplete architecture that is tailored for a specific application domain or family of applications, incorporating support for only those non functional requirements that are relevant for that specific application domain. Certain ....

T. D. Meijler, O. Nierstrasz, "Beyond Objects: Components", in Cooperative Information Systems: Current Trends and Directions, M.P. Papazoglou, G. Schlageter (Ed.), Academic Press, November 1997, pp. 49-78.

....on the complete system. Static checks can only be done within individual components. All other checking the checking of the complete system must be deferred until composition time, leading to late detection of errors. 1 Introduction An important contribution of component frameworks [19, 10] is support for independent extensibility. A system is called independent extensible if it can cope with the late addition of components without requiring a global integrity check [18] In [24] one points out that components can be developed by different people in complete ignorance of each other ....

T. D. Meijler, O. Nierstrasz, "Beyond Objects: Components", in Cooperative Information Systems: Current Trends and Directions, M.P. Papazoglou, G. Schlageter (Ed.), Academic Press, November 1997, pp. 49-78.

....reconfigurable software applications. Changing requirements of software applications can also be referred to as evolution [ND95] Adaptability may also be viewed as a form of reusability, because existing structures (e.g. applications) can be reused to create slightly different applications [MN96]. 2.3.3 Security Security has many different facets within computer science and computer security itself is a very large research topic. Important areas of security are for instance data loss (hardware errors, software errors) and protection of system resources . Because we are interested in ....

....evolve. Some of the problems addressed are mainly research topics in the Software Composition Group at the University of Berne 13 . Especially solutions in the direction of software composition, for instance composition languages, composition environments and visual composition environments [NT95, MN96]. Other topics discussed like distributed object systems [Mic95, Obj92, Vin93] and mobile agent systems [HCK95, Har95, Hoh95] are already well understood. The previous discussion about available technologies shows that mobility remains as a central property in the field of open, flexible ....

T. Meijler and O. Nierstrasz. Beyond Objects: Components. 1996.

....there is a growing interest for software applications that execute computation while moving around the network. Not surprisingly, the structure of such applications is highly distributed. Since distributed systems are very complex in general, software abstractions are needed to simplify the task [20]. In ##, components are natural units of distribution that abstract from the di#erence between local and remote communication. Local interaction takes places amongst objects that are instances of classes within the same component (i.e. likely to be located at the same site) while remote ....

T.D. Meijler and O. Nierstrasz. Beyond objects: components. In M.P. Papazoglou and G. Schlageter (eds.), Cooperative Information Systems: Current Trends and Directions, Academic Press, 1997.

....the functionality they require, purchases the appropriate atomic architectural components, and assembles a system from them within the confines of a given architecture. This proposes that composition is a connection oriented activity, which may be sub divided into static and dynamic aspects (Meijler and Nierstrasz 1998). The prominent means of static composition is based on the binding of provided and required interfaces, which may be viewed as an extension of the traditional approaches of interface definition languages and or module interconnection languages. A component makes explicit the interfaces that it ....

....behaviour. These may include deciding where requests should be placed, co ordinating concurrent (or simultaneous) access to shared resources, establishing valid execution orders for requests, maintaining consistency of persistent state and gathering and integrating results from various resources (Meijler and Nierstrasz 1998). Essentially, these relate to the non functional requirements of a system that need to be addressed in addition to the functionality provided by components. Certain classes of non functional requirements, such as performance or fault containment, may be inherent in the design of a component. ....

Meijler, T. D., and Nierstrasz, O. (1998). Beyond Objects: Components. Cooperative Information Systems, M. Papazoglou, ed., Academic Press, London. In press.

....the software under development reuses 1 functionality already available, or built from scratch where the software under development is augmented with new functionality. Work, both at a theoretical and practical level, aims at making the componentoriented development of software systematic [6, 11, 13, 18]. We develope complex interactive systems from simple components by extending an existing logic programming framework, presented in [22 26] based on games. This framework was introduced to address inadequacies of existing logic programming approaches to develop interactive systems, particularly ....

T. D. Meijler and O. Nierstrasz, Beyond Objects: Components, In P. Papazoglou and G. Schlageter (Eds), Cooperative Information Systems: Trends and Directions, Academic Press, 1998.

....etc. A detailed list of ORB features can be found in [10] By separating the architectural structure of the composition of components on the one hand from the component instances that make part of this composition, the composition process can be encapsulated in an ORB component framework [11][12] as a generic architecture for a family of ORB implementations. This separation is enabled by defining the basic architecture of an ORB in terms of architectural entities that abstract away from concrete implementation details. These architectural entities explicitly uncouple the type of an ....

T. D. Meijler, O. Nierstrasz, "Beyond Objects: Components", in Cooperative Information Systems: Current Trends and Directions, M.P. Papazoglou, G. Schlageter (Ed.), Academic Press, Nov., 1997, pp. 49-78.

....the machine. Introduction With the advances in Object Oriented technology, the construction of off the shelf components that can be used and re used for the construction of large software systems has become fashionable. This leads to a new style of software construction called component oriented (Meijler Nierstrasz 1998), Buschmann et al. 1996) In parallel, especially for distributed applications, another style of programming is often used, called agent oriented. In this style of programming the entities of the application are viewed as agents which are capable of accomplishing complex tasks. A number of ....

Meijler, T. D., and Nierstrasz, O. 1998. Beyond Objects: Components. In Papazoglou, M., ed., Cooperative Information Systems. Academinc Press.

....systems has become fashionable. The re use can be employed either at the design level which involves abstract patterns( 2] or at the more concrete level that involves components implemented in some specific language. This leads to a new style of software construction called component oriented ([12]) In parallel, especially for distributed applications, another style of programming is often used, called agent oriented. In this style of programming the entities of the application are viewed as agents which are capable of accomplishing complex tasks. A number of software architectures have ....

....6 Discussion and Conclusions Software construction these days increasingly follows a component oriented style, where components are constructed and used off the shelf for the construction of complex software systems. The construction of agent systems could also follow this philosophy ( 6] [12]) In this paper, an agent architecture is proposed that can be used to integrate pre existing components. Even components written in a conventional language such as C can be integrated by providing an front end process that accepts our KQML style messages, mapping them into internal procedure ....

T. D. Meijler and O. Nierstrasz. Beyond Objects: Components. In M. Papazoglou and G. Schlageter, editors, Cooperative Information Systems: Trends and Directions. Academinc Press, 1998.

....systems has become fashionable. The re use can be employed either at the design level which involves abstract patterns( 2] or at the more concrete level that involves components implemented in some specific language. This leads to a new style of software construction called component oriented ([15]) In parallel, especially for distributed applications, another style of programming is often used, called agent oriented. In this style of programming the entities of the application are viewed as agents which are capable of accomplishing complex tasks. A number of software architectures have ....

....by the platform. 6 Discussion and Conclusions Software construction increasingly follows a component oriented style, where components are constructed and used off the shelf for the construction of complex software systems. The construction of agent systems could also follow this philosophy ( 8] [15]) In this paper, an agent architecture is proposed that can be used to integrate pre existing components. Even components written in a conventional language such as C can be integrated by providing a wrapper that accepts our KQML style messages, mapping them into internal procedure calls, and ....

T. D. Meijler and O. Nierstrasz. Beyond Objects: Components. In M. Papazoglou and G. Schlageter, editors, Cooperative Information Systems: Trends and Directions. Academinc Press, 1998.

....in other kinds of re engineering efforts: factoring out genericity from application specific aspects makes for better adaptability and maintainability of the software. Frameworks A framework is a software structure which provides a skeletal software architecture and a library of components[15] [25]. The skeletal architecture factors out the commonalities of a family of applications and can be specialized for creating a specific application. The component library provides an extensible collection of software artefacts addressing a particular application domain. Successful frameworks are ....

Meijler, T.D., Nierstrasz, O., "Beyond Objects: Components". In Cooperative Information Systems, M. Papazoglou (ed.), Academic Press, London, to appear.

....just parts of distributed, inter operable and flexible software systems. Distribution and interoperability are relatively easy to obtain, because these requirements are known at design time. Flexibility is the most difficult to meet, because not all application requirements can be known in advance[26]. The problem we address in this thesis are the difficulties that exist in the development and evolution of open systems as described above. We particularly address the coordination aspects of these systems. In general systems can be described as computational parts that interact with each ....

....the architecture more explicit and manipulable. A description of which components are used and how they are put together and parameterized, provides a high level description of what happens where in a system 1 . This makes a system easier to understand and easier adaptable to new requirements[26]. Object oriented programming languages(OOPLs) go a long way towards supporting components. Objects hide their implementation and there are numerous object oriented design patterns that exploit the possibilities of run time object composition[9] There is, however, still to do a lot in this area ....

[Article contains additional citation context not shown here]

T.D. Meijler and O. Nierstrasz, "Beyond Objects: Components", Cooperative Information Systems, M. Papazoglou (Ed.), Academic Press, London, to appear.

No context found.

T. Meijler and O. Nierstrasz. Beyond Objects: Components. In WCOP'98 Proceedings of the Third International Workshop on Component-Oriented Programming, 1998.

No context found.

Theo Dirk Meijler and Oscar Nierstrasz. Beyond objects: Components. In M. P. Papazoglou and G. Schlageter, editors, Cooperative Information Systems: Current Trends and Directions, pages 49--78. Academic Press, 1997. Also available as: http://homepages.cwi.nl/~marcello/ SAPapers/MN97.pdf. 22

No context found.

T. D. Meijler and O. Nierstrasz. Beyond Objects: Components. In M. Papazoglou and G. Schlageter, editors, Cooperative Information Systems: Trends and Directions. Academinc Press, 1998.

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