Venue – Motivation – Topics – Participation – Important Dates – Workshop Co-Organizers
20th European Conference on Object-Oriented Programming
Official ECOOP information on this workshop
WCOP 2006 seeks position papers on the important field of component-oriented programming (COP). WCOP 2006 is the eleventh 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, and most recently .NET, but also the increasing appreciation of software architecture for component-based systems, 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 2006 will emphasize reasons for using components beyond re-use. While consider software components a technical means to increase software re-use, other reasons for investing into component technology tend to be overseen. For example, components play an important role in framework and product-lines to enable configurability (even if no component is re-used).
Another role of components beyond re-use is to use components to increase the predictability of the properties of a system. The use of components as contractually specified building blocks of software restricts the degrees of freedom during software development compared to classic line-by-line programming. However, this restriction is beneficial for the predictability of system properties. For an engineering approach to software design, it is important to understand the implications of design decisions on the system's properties. Therefore, approaches to evaluate and predict properties of systems by analyzing its components and its architecture are of high interest.
To strengthen the relation between architectural descriptions of systems and components, a comprehensible mapping to component-oriented middleware platforms is important. Model-driven development, with its use of generators, can provide a suitable link between architectural views and technical component execution platforms.
Finally, in addition to submissions addressing the themes, 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 2006 include, but are not limited to:
· predictable assembly of components
· performance/efficiency and reliability of component-based systems
· 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
· system design for hot-swappable 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
Attendance is by invitation only; all submitters of position papers have been invited. Others who might be interested should contact Ralf Reussner.
All submitted position papers received at least two reviews. A zipped archive of all accepted papers.
·
On the Benefits of using Aspect Technology in
Component-Oriented Architectures
(Maarten Bynens, Wouter Joosen, KU Leuven, Belgium)
·
A Safe Aspect-Oriented Programming Support for
Component-Oriented Programming
(Nicolas Pessemier, Lionel Seinturier, Laurence Duchien, INRIA/LIFL;
·
Leveraging Component-Oriented Programming with
Attribute-Oriented Programming
(Romain Rouvoy, Jacquard Project – INRIA
·
Automated Component
Bridge Generator
(Dominik Glaser, Gregor Fischer, Jürgen Wolff von Gudenberg, U Wuerzburg,
Germany)
·
Component Adaptation: Specification and Verification
(Inès Mouakher, Arnaud Lanoix, Jeanine
Souquières, LORIA – CNRS – Université Nancy 2, France)
·
Profitability-oriented Component Specialization
(Ping Zhu, Siau Cheng Khoo, National U of Singapore,
·
Putting Components into Context -- Supporting
QoS-Predictions with an explicit Context Model
(Steffen Becker, U Karlsruhe; Jens Happe, Heiko Koziolek, U Oldenburg, Germany)
·
An Architectural Component-Based model to
solve the Heterogeneous Interoperability of Component-Oriented Middleware
Platforms
(Francisco Domínguez-Mateos, Raquel Hijón-Neira, U Rey Juan Carlos,
·
Automated Deployment of Component Architectures with
Versioned Components
(Leonel Aguilar Gayard, Paulo Astério de Castro Guerra, Ana Elisa de Campos Lobo,
Cecília Mary Fischer Rubira, UNICAMP,
·
Describing
Framework Static Structure: promoting interfaces with UML annotations
(Sérgio Lopes, Adriano Tavares, João Monteiro and Carlos Silva, U Minho,
Portugal)
·
Interactive Component Assembly with SuperGlue
(Sean McDirmid, EPFL,
·
Active Documents – Taking advantage of
component-orientation beyond pure reuse
(Markus Reitz, U Kaiserslautern, Germany)
·
Component based method for enterprise application
design
(Emmanuel Renaux, U Lille, France; Eric Lefebvre, École de Technologie
Independent Software Architect
Probusweg 9, CH-8057 Zürich,
Phone +41(79)419 74 36
Wolfgang.Weck (at) iaeth.ch
http://www.wolfgang-weck.ch/
Ralf Reussner
Institute for Program Structures and
Am Fasanengarten 5, D-76128 Karlsruhe, Germany
Reussner (at) ipd.uka.de
http://se.informatik.uni-oldenburg.de/Members/ralf
Software Architect
Microsoft
Clemens.Szyperski (at) microsoft.com
http://research.microsoft.com/~cszypers/