Szyperski, C., & P ster, C. (1997). Workshop on ComponentOriented Programming, Summary. In MuhlHauser M. (Ed.) Special Issues in Object-Oriented Programming - ECOOP96 Workshop Reader. Dpunkt Verlag, Heidelberg. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
An Experiment in Component Adaptation - Heineman, Ohlenbusch (1999) (Correct)
....them into a target application. Consider the following definition: Asoftware component is 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. [29] The componentinterface provides no insightinto adaptation, and the definition does not even admit to components being subject to such adaptation. A component can be released with a special source code license allowing code modifications. The Hot Java Component from javasoft.com, for example, is ....
C. Szyperksi and C. Pfister. Workshop on Component-Oriented Programming, Summary. in muhlhauser M. (ed.) special issues in objectorientedprogramming - ecoop'96 workshop reader.
A Java Component User Interface for the Minstrel Push System - Umlauft (2000) (2 citations) (Correct)
....Software in a Nutshell This chapter provides an overview of component oriented software design [Szy99] The design goals for the component framework developed for this thesis are being defined and existing technologies are evaluated in respect to our project requirements [GT00] 4. 1 Definitions [SP97] defines a software component as follows: A software component is 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. A component framework can ....
C. Szyperski and C. Pfister. Workshop on component-oriented programming, summary. In M. Muhlhauser, editor, Special Issues in Object-Oriented Programming -- ECOOP96 Workshop Reader, Heidelberg, 1997. dpunkt Verlag.
Component-based Software Engineering - New Challenges in.. - Crnkovic (Correct)
....the start point is to understand what a component is and what a component is not. As a generic term the definition is pretty clear a component is a part of something. This definition is however too weak to be useful. There have been many discussions about the component specification [11][12] We shall take Szyperski s definition [13] that is mostly used today and that is most appropriate to implementations in different component models: A software component is a unit of composition with contractually specified interface and explicit context dependencies only. A software ....
Szyiperski C. and Pfister C., Workshop on Component-Oriented Programming, Summary. In Mhlhuser M. (ed.) Special Issues in Object-Oriented Programming -- ECOOP96 Workshop Reader, Springer 1997
Contract-based Component System Design - Giese (2000) (4 citations) (Correct)
....basic concepts and their implications in mind. Besides the pure off the shelf component notion, there may exist several levels of component usage, which are of interest, too. Imported and exported types of a component are a relevant aspect as well as its connections with the environment. Szyperski [37, 38] defines a component as follows: A Software component is an 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. For each interface a component has ....
C. Szyperski and C. Pfister. Workshop on ComponentOriented Programming, Summery. In M. Mulhauser, editor, Special Issues in Object-Oriented Programming -- ECOOP'96 Workshop Reader. dpunkt, Heidelberg, 1997.
Automated Architectural Transformation: Objects to Components - Lorenz, Vlissides (2000) (Correct)
....into a componentized JavaBeans system. These techniques can aid in transforming existing systems to implicit invocation systems. 7. 1 Component Based Systems There is rising interest in architectural design and construction of component based systems beyond ad hoc reuse of unrelated components [3]. In the current absence of lingual support for component based programming, and in the absence of good component system design tools, component generators can play a leading role. In this respect, the role of component generators can be compared to the role of compiler compilers (e.g. YACC [2] ....
J. Bosch, C. Szyperski, and W. Weck. Workshop on component oriented programming, ECOOP, 2000. Upcoming event.
Communication as a Means to Differentiate Objects.. - Deugo, Oppacher.. (1999) (1 citation) (Correct)
....even a socket as physical examples of a blackboard. 3. Component Communication Patterns In order to discuss component communication patterns, we begin with a working definition of a component. We agree with the definition formulated at the 1996 European Conference on Object Oriented Programming [13]: A software component is a unit of composition with contractually specified interfaces and explicit context dependencies. A software component can be deployed independently and is subject to composition by their parties. The belief is that a component is one abstraction level above an ....
Szyperski, C. and Pfister C., Workshop on Component-Oriented Programming, Summary, In M. Mhlhuser (ed.) Special Issues on Object-Oriented Programming -- ECOOP 96 Workshop Reader, Springer-Verlag, Heidelberg, 1997.
The Use of DL in Component Libraries - First Experiences - Van Der Straeten, Casanova (Correct)
No context found.
Szyperski, C., & P ster, C. (1997). Workshop on ComponentOriented Programming, Summary. In MuhlHauser M. (Ed.) Special Issues in Object-Oriented Programming - ECOOP96 Workshop Reader. Dpunkt Verlag, Heidelberg.
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