WCOP seeks position papers on the important field of component-oriented programming (COP). WCOP 2007 is the twelfth event in a series of highly successful workshops, which took place in conjunction with every ECOOP since 1996.
COP has been described as the natural extension of object-oriented programming to the realm of independently extensible systems. Several important approaches have emerged over the recent years, including component technology standards, such as CORBA/CCM, COM/COM+, J2EE/EJB,.NET, and most recently software services, but also the increasing appreciation of software architecture for component-based systems, as in SOA, and the consequent effects on organizational processes and structures as well as the software development business as a whole.
COP aims at producing software components for a component market and for late composition. Composers are third parties, possibly the end users, who are not able or willing to change components. This requires standards to allow independently created components to interoperate, and specifications that put the composer into the position to decide what can be composed under which conditions. On these grounds, WCOP'96 led to the following definition:
A component is a unit of composition with contractually specified interfaces and explicit context dependencies only. Components can be deployed independently and are subject to composition by third parties.
After WCOP'96 focused on the fundamental terminology of COP, the subsequent workshops expanded into the many related facets of component software.
WCOP 2007 will discuss the black-box nature of components. On the one hand, for many, components became synonymously with the black-box building blocks of software. Technically, this means a component is described by the interfaces it provides and requires. On the other hand, for many reasons, an abstract description of specific aspects of the component’s behaviour in addition to the mere interface specification is needed. These reasons include architectural dependency analysis, the description of non-functional properties or the verification of the absence of deadlocks. Therefore, in WCOP 2007 we explicitly ask for positions statements discussing work related to the question:
“How dark should a component blackbox be?”
This includes position statements dealing with components or component-based systems or component infrastructures, which explicitly make use of information on components beyond mere provides and requires interfaces.
Finally, in addition to submissions addressing the theme, we explicitly solicit papers reporting on experience with component-oriented software systems in practice, where the emphasis is on interesting lessons learned, whether the actual project was a success or a failure.
Topics of interest to WCOP 2007 include, but are not limited to:
· Predictable assembly of components
· Performance/efficiency and reliability of component-based systems
· Systems for the description and prediction of non-functional component properties
· Deployment attribution / constraints
· COP and Model-driven Development (MDA)
· Role of composition frameworks
· Interoperation among component frameworks
· Dynamic composition of component-based systems
· Component-oriented development processes
· Relating architectural principles/approaches to component software
· Architecture description languages suitable to guide COP
· Addressing variability requirements in component-based solutions
· System design for independent extensibility
· System design for the use of third-party components
· Component versus application evolution
· Components in distributed embedded systems, incl. mobile phones and PDAs
· Domain-specific (vertical) standards
· Organizational aspects
· Business aspects
· What worked / what didn't work in practice and lessons learned
All submitted position papers received at least two reviews. A zipped archive of all accepted papers is available.
Relating Model-Based Adaptation and Implementation
Platforms: A Case Study with WF/.NET 3.0?
(Javier Cubo, Gwen Salaün, Carlos Canal, Ernesto Pimentel, University of Malaga, Spain; Pascal Poizat, Université d'Evry Val d'Essonne, France and INRIA Rocquencourt, France)
On the benefits of using model transformations to
describe components design process
(Eveline Kaboré and Antoine Beugnard, ENST Bretagne, France)
Reengineering of Software Component Models to
Enable Architectural Quality of Service Predictions
(Klaus Krogmann, Universität Karlsruhe (TH), Germany)
Predicting Software Component Performance: On
the Relevance of Parameters for Benchmarking Bytecode
(Michael Kuperberg and Steffen Becker, Universität Karlsruhe (TH), Germany)
Aspectual Dependencies: Towards Pure Black-Box
Aspect-Oriented Composition in Component Models
(Bert Lagaisse and Wouter Joosen, K.U.Leuven, Belgium)
A Seamless Extension of Components with Aspects
(Angel Núñez, Jacques Noyé, EMN-INRIA, Nantes, France)
AOCI: An Aspect-Oriented Component
(Guido Söldner and Rüdiger Kapitza, University of Erlangen-Nürnberg, Germany)
How dark should a component black-box be? The
(Jakob Henriksson and Florian Heidenreich and Jendrik Johannes and Steffen Zschaler and Uwe Aßmann, Technische Universität Dresden, Germany)
Black & White, Never Grey: On Interfaces,
Synchronization, Pragmatics, and Responsibilities
(Franz Puntigam, Technische Universität Wien, Austria)
Components have no Interfaces!
(Richard Rhinelander, University of Kitara, Australia)
Institute for Program Structures and Data
Universität Karlsruhe (T.H.)
Am Fasanengarten 5, D-76128 Karlsruhe, Germany
Reussner (at) ipd.uka.de
Clemens.Szyperski (at) microsoft.com
Independent Software Architect
Probusweg 9, CH-8057 Zürich,
Phone +41(79)419 74 36
Wolfgang.Weck (at) iaeth.ch