14th International Workshop on Component-Oriented Programming, East Stroudsburg, Vereinigte Staaten

<p class="MsoBodyTextIndent">WCOP seeks position papers in the important field of component&#8211;oriented programming (COP)&#046; WCOP 2009 is the fourteenth event in a series of highly successful workshops&#046; After twelve years of successful annual affiliation with ECOOP, WCOP has now joined the CompArch series of federated events with their specific focus on components and architecture&#046; WCOP 2009 will be the second WCOP held as part of CompArch&#046;</p> <p class="MsoBodyTextIndent">COP has been described as the natural extension of programming to the realm of independently extensible systems&#046; A wide range of technologies has emerged over the years starting with CORBA/CCM and COM/COM+, leading to J2EE/EJB and &#046;NET, and including more recent developments such as the Eclipse RCP with its underlying OSGi framework, or the upcoming MEF in &#046;NET 4&#046;0&#046;</p> <p class="MsoBodyTextIndent">At the same time, components met architecture as well as models and services, leading to important insights on how to think about components, especially pre&#8211;existing ones, in an architectural context, in a model&#8211;driven environment, and for composable services as a center piece in modern large&#8211;scale systems of systems&#046;</p> <p class="MsoBodyTextIndent">COP aims at producing software components for a component market and for late composition&#046;<span style=&#8243;> </span>Composers are third parties, possibly the end users, who are not able or not willing to change components&#046; 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&#046; On these grounds, WCOP&#8242;96 led to the following definition that held up over the years: </p> <p class="MsoBodyTextIndent"><i style=&#8243;>“A component is a unit of composition with contractually specified interfaces and explicit context dependencies only&#046; Components can be deployed independently and are subject to composition by third parties&#046;”</i></p> <p class="MsoBodyTextIndent"><span class="GramE">After WCOP&#8242;96 focused on the fundamental terminology for COP, the subsequent workshops expanded into the many related facets of component software&#046;</span> WCOP 2009 will discuss components in the context of large systems that need to evolve over time, are sustained by distributed development, and can never be taken down or replaced in their entirety&#046; COP offers a unique value proposition in such a context, especially when embedded in appropriate architectural, model&#8211;driven, and service&#8211;oriented context&#046;</p> Finally, in addition to submissions addressing the theme, we explicitly solicit papers reporting on experience with component&#8211;oriented software systems in practice, where the emphasis is on interesting lessons learned, whether the actual project was a success or a failure&#046;