[ecoop-info] CfP WCOP 2007, July 31st, Berlin

[Ralf Reussner]

Call for Position Statements

WCOP 2007

Twelfth International Workshop on Component-Oriented Programming
(in conjunction with ECOOP 2007)

Berlin, July 31st, 2007

http://research.microsoft.com/~cszypers/events/WCOP

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 notable 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
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

SUBMISSIONS AND PARTICIPATION
To enable lively and productive discussions, attendance will be limited 
to about 30
participants. To participate in the workshop, acceptance of a submitted 
position statement is
required. All submissions will be formally reviewed. High-quality 
position statements will be
considered for publication in conjunction with transcripts of workshop 
results. Authors of
accepted papers need to participate in the workshop. Position statements 
should clearly state
how they relate to the workshop theme, what particular problems they 
address, and what solutions
they envisage, and why the statement is expected to be relevant to both 
this workshop and the
community. Statements should be four to eight pages (single-spaced A4 or 
letter) long and state
the author's name, affiliation, and contact. Submissions should be 
e-mailed in PDF to Ralf
Reussner (reussner "at" ipd.uka.de) with "WCOP 2007" in the subject line.

IMPORTANT DATES
- Paper submissions: 13 May, 2007
- Notification of acceptance: 31 May, 2007
- Workshop handouts ready: 19 June, 2007

WORKSHOP CO-ORGANIZERS

Ralf Reussner
Institute for Program Structures and Data Organization
Universität Karlsruhe (T.H.)
Am Fasanengarten 5
D-76128 Karlsruhe, Germany
E-mail reussner "at" ipd.uka.de
Web http://sdq.ipd.uka.de

Clemens Szyperski
Microsoft
One Microsoft Way
Redmond, WA 98053, USA
E-mail clemens.szyperski "at" microsoft.com
Web: http://research.microsoft.com/~cszypers/

Wolfgang Weck
Independent Software Architect
Probusweg 9
CH-8057 Zürich,
Switzerland
E-mail wolfgang.weck "at" iaeth.ch
Web http://www.wolfgang-weck.ch

-- 
--------------------------------------------------------------
Prof. Dr. Ralf Reussner  -  Chair Software-Design and -Quality
Institute for Program Structures and Data Organization
Faculty of Informatics, Universitaet Karlsruhe (TH)
Am Fasanengarten 5, D-76131 Karlsruhe, Germany
Office 327, Main Computer Science Building (50.34)
Tel. +49 721 608 5993, Fax. +49 721 608 5990
http://sdq.ipd.uka.de
--------------------------------------------------------------