WCOP 2005
Tenth International Workshop on
Component-Oriented Programming
Monday, July
25, 2005 – at ECOOP 2005, Glasgow ,
Scotland
Venue – Motivation – Topics – Participation – Accepted Position Papers – Program – Workshop Co-Organizers
Venue
19th European Conference on Object-Oriented Programming
Official ECOOP information on this workshop
Motivation
WCOP 2005 seeks position papers on the important field of component-oriented programming (COP). WCOP 2005 is the tenth 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 was focused on the fundamental terminology of COP, the subsequent workshops expanded into the many related facets of component software. WCOP 2005 will emphasize the problem of assigning blame in failing compositions as well as the topics of component frameworks and tools. A continuing interest of the WCOP community is in component-oriented development processes. A service is a running instance (all the way down to supporting hardware and infrastructure) that has specific quality attributes, while a component needs to be deployed, installed, loaded, instantiated, composed, and initialized before it can be put to actual use. The commonalities and differences between service and component composition models are interesting and a proposed focus of this workshop.
Flexible development processes (such as agile ones) and component-based development support each other in that use of existing or of-the-shelf components reduces the amount of required development effort. On the other hand, however, deployment of such components typically has consequences for the remainder of the system. Such decisions and documents need to be produced early in the process and changing them later comes at considerable cost, presenting a clear risk for agile development processes.
One of the challenges in component-based software development is the establishment of system qualities. While it is already hard to establish functional properties under free composition of components, non-functional and non-technical aspects tend to emerge from composition and are thus even harder to control. This is especially the case when systems start to compose themselves dynamically.
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
Topics of interest to WCOP 2005 include, but are not limited to:
· blame assignment
· component frameworks
· dynamic composition of component-based systems
· component-oriented development processes
· components in distributed embedded systems, incl. mobile phones and PDAs
· components versus services
· relating architectural principles/approaches to component software
· 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
· interoperation among component frameworks
· quality attributes
· declarative forms of composition/configuration
· deployment attribution / constraints
· component versus application evolution
· domain-specific (vertical) standards
· dynamic architectures
· architecture description languages suitable to guide COP
· performance/efficiency of component-based systems
· organizational aspects
· business aspects
· what worked / what didn't work in practice and lessons learned
Participation
Attendance is by invitation only; all submitters of
position papers have been invited. Others who might be interested should
contact
Accepted Position Papers
All submitted position papers received at least two reviews. A zipped archive of all accepted papers.
Session 1: Platform Independence
·
Management of wireless software components
(Fabien Romeo and Franck Barbier, U de Pau et des Pays de l’Adour,
·
Towards platform-independent component
measurement
(Marcus Meyerhöfer and Frank Lauterwald, Friedrich-Alexander U of
Session 2: Quality Attributes
·
Quality attributes for a component quality model
(Alexandre Alvaro, Eduardo Santana de Almeida, and Silvio Romero de Lemos
Meira, Federal U of Pernambuco and C.E.S.A.R –
·
Transforming Operational Profiles of
Software Components for Quality of Service Predictions
(Heiko Koziolek, Steffen Becker, U
·
Using Stochastic Petri Nets to Predict
Quality of Service Attributes of Component-Based Software Architectures
(Jens Happe, Viktoria Firus, U
Session 3: Models and Methods
·
A lightweight process model and development
methodology for component frameworks
(Ansgar Scherp and Susanne Boll, OFFIS,
·
Applying a component model to grid application
services
(Rainer Schmidt, Siegfried Benkner, Ivona Brandic, and Gerhard Engelbrecht, U
Vienna, Austria)
·
A component-based approach
for supporting functional and non-functional analysis in control loop design
(Massimo Tivoli, U L'Aquila,
Session 4: Reliability
·
Towards reliable self-integrative
IT systems
(Dirk Niebuhr and Andreas Rausch, TU Kaiserslautern, Germany; Christian Peper,
·
In components we trust – programming language
support for weak protection
(Franz Puntigam, TU Vienna, Austria)
Program
As in past years, WCOP will run with distinct morning and afternoon programs. During the morning of the WCOP 2005 day, authors of accepted position papers will give ten brief presentations. The afternoon is then split into a breakout session and a closing/summary session. Workshop attendees are strongly encouraged to read the position papers ahead of the workshop to maximize the value of the brief presentations and of the breakout-group discussions in the afternoon.
The workshop will start at 9:30 and end
approximately at 17:15. Please note that the slots assigned to each
presentation include the time for (few quick) questions and plugging your
computer with the beamer – hence please keep your actual presentation within 9
minutes.
We are looking forward to meet you next Monday in
Workshop Co-Organizers
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/
Jan Bosch
VP, Head of Software and Application Technologies
Lab
Nokia Research Center
P.O. Box 407, FI-00045 NOKIA GROUP, Finland
Phone +358 7180 72007
Jan.Bosch (at) nokia.com
Ralf Reussner
Escherweg 2, D-26121 Oldenburg, Germany
Reussner (at) informatik.uni-oldenburg.de
http://se.informatik.uni-oldenburg.de/Members/ralf
Software Architect
Microsoft
CSzypers (at) microsoft.com
http://research.microsoft.com/~cszypers/