Frank Griffel. Componentware. dpunkt-Verlag, Heidelberg, 1998. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Towards Device Driver Synthesis - Lehmann (2002) (Correct)
....types like char, integer, etc. of special services to other kernel components or drivers. Adaption components between two software interfaces can be generated with special synthesis techniques discussed in State of the Art in section 3 or with the design methods on component oriented software [40]. In the next sections the objectives of the device driver are depicted in more detail. 2.2 Resource Management One of the device drivers task is resource management. The device driver is developed as an adapter from a special hardware implementation, an instance of a device as specialisation of ....
....object to the device by the device name. Access to the device is given by means of method calls to that device object [107] In the case of a dynamic number of devices, for example the serial computer interfaces, the application asks the object by means of reflection methods (compare for example [40]) which devices (names) are available. One is selected and the object is bound to that device by an open call [107] So here the advantages of object oriented implementation are used. The management object can be a static part of the class which works as proxy for the device class. Each ....
[Article contains additional citation context not shown here]
Frank Griffel. Componentware. dpunkt-Verlag, Heidelberg, 1998.
Towards a Foundation of Component-Oriented Software Reference.. - Teschke, Ritter (2001) (1 citation) (Correct)
....software systems. 1 Introduction The notion of component based software development denotes an approach pursued in every mature engineering discipline: systems (here: software) shall be developed by reusing and combining well tried methods and tested products (here: software components) [Gri98]. Szyperski defines a software component (further on only referred to as component) as [ a unit of composition with contractually specified interfaces and explicit context dependencies only. A software component can be deployed independently and is subject to composition by third parties ....
F. Griffel. Componentware. dpunkt-Verlag, Heidelberg, 1998.
Interaction-Oriented Rule Management for Mobile Agent.. - Tu, Griffel, Merz.. Self-citation (Griffel) (Correct)
....but also applicable to software components in general, particularly those that can be dynamically assembled from building blocks which are themselves active, autonomous components. We will discuss the specific requirements for rule management mechanisms resulting from such a componentware view ([Gri98]) in another paper. ....
Frank Griffel. Componentware. dpunkt--Verlag, 1998. (In German).
A Plug-in Architecture Providing Dynamic Negotiation.. - Tu, Griffel, Merz.. (1998) (5 citations) Self-citation (Griffel) (Correct)
....always need a certain inititial phase to adapt so that they are not immediately ready for (effective) operation. 3 The DYNAMICS Architecture The general goal of the DYNAMICS (DYNAMIcally Configurable Software) project is the design and implementation of highly configurable software components [6] which can be used as building blocks to assemble ready to use applications in a dynamic manner. With regard to mobile agents, this means that the functionality of an agent can be composed of several independently developed components which are plugged together. Especially, the agents should ....
Frank Griffel. Componentware. dpunkt--Verlag, 1998. (In German).
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