[aosd-announce] Final CFP: AOSD Workshop on Aspects, Components, and Patterns for Infrastructure Software

[Eric Eide]

				CALL FOR PAPERS

	   First AOSD Workshop on Aspects, Components, and Patterns
			  for Infrastructure Software

				April 23, 2002
			   Enschede, The Netherlands
	 http://www.st.informatik.tu-darmstadt.de/~ostermann/aosd2002/

	     A one-day workshop to be held in conjunction with the
		       First International Conference on
	       Aspect-Oriented Software Development (AOSD 2002),
		 April 22-26, 2002, Enschede, The Netherlands
		     http://trese.cs.utwente.nl/aosd2002/


Aspect-oriented programming, component models, and design patterns are modern
and actively evolving techniques to improving the modularization of complex
software.  In particular, these techniques hold great promise for the
development of ``systems infrastructure'' software, e.g., application servers,
middleware, virtual machines, compilers, operating systems, and other software
that provides general services for higher-level applications.  The developers
of infrastructure software are currently faced with increasing demands from
application programmers needing higher-level support for application
development.  Meeting these demands requires careful use of software
modularization techniques, since infrastructural concerns are notoriously hard
to modularize.

Aspects, components, and patterns provide very different means to deal with
infrastructure software, but despite their differences, they have much in
common.  For instance, component models try to free the developer from the need
to deal directly with services like security or transactions.  These are
primary examples of crosscutting concerns, and modularizing such concerns are
the main target of aspect-oriented languages.  Similarly, design patterns like
Visitor and Interceptor facilitate the clean modularization of otherwise
tangled concerns.

This workshop aims to provide a highly interactive forum for researchers and
developers to discuss the application of and relationships between aspects,
components, and patterns within modern infrastructure software.  The goal is to
put aspects, components, and patterns into a common reference frame and to
build connections between the software engineering and systems communities.
Suggested topics for position papers include, but are not restricted to:

  * Approaches that combine or relate component-, pattern-, and aspect-based
    techniques
  * Dimensions of infrastructure software quality including comprehensibility,
    configurability (by implementors), customizability (by users), reliability,
    evolvability, scalability, and run-time characteristics such as performance
    and code size
  * Merits and downsides of container-, ORB-, and system-based separation of
    concerns
  * Architectural techniques for particular system concerns, e.g., security,
    static and dynamic optimization, and real-time
  * Design patterns for systems software
  * Component, pattern, and aspect ``mining'' within systems code
  * Application- or domain-specific optimization of systems
  * Reasoning and optimization across architecture layers
  * Quantitative and qualitative evaluations

AGENDA

Our goal is to have fruitful discussions.  Each of the papers chosen for
presentation will have two assigned commentators from the program committee
that will be responsible for triggering the discussion after the presentation
by shortly summarizing what they like and dislike about the paper and to make
very detailed comments on the paper.  The underlying idea is to help people
improve their papers and ideas via the discussion with the others and on the
other side, to give a broader audience a better understanding of the ideas in
the paper.  Each presentation will have 5-20 minutes, depending on the content
and the quality of the paper.  This is a little bit in the vein of ``writers
workshops'' as for example successfully applied at EuroPlop conferences.  If
necessary, we will split in groups based on the topics of interest in order to
have parallel presentations.

The last session of the workshop will be 1 hour relaxed coffee time where
people should form groups of two or three based on their interests to discuss
about topics they find interesting.

SUBMISSION GUIDELINES

Position papers should be 3-6 pages.  All papers must be submitted
electronically in PDF, Postscript, or MS Word format.  The papers should be
emailed to: <aosd-submit at ccs.neu.edu>.  Paper submissions will be reviewed by
the program committee using criteria appropriate to their category.  The
submitted papers will be evaluated based on their originality, relevance,
technical quality and presentation.

All accepted papers will be posted at the workshop website prior to the
workshop date to give all participants the opportunity to read them before the
workshop.  In addition, the accepted papers will be published in a Workshop
Proceedings as a University of British Columbia technical report.

IMPORTANT DATES

  Submission Deadline:		March  1, 2002
  Notification of Acceptance:	March 21, 2002
  Workshop:			April 23, 2002

WORKSHOP PROGRAM COMMITTEE

  Frank Buschmann, Siemens AG
  Siobhan Clarke, Trinity College
  Yvonne Coady, University of British Columbia
  Eric Eide, University of Utah
  Erik Ernst, University of Aalborg
  Stephan Herrmann, Berlin Technical University
  Guenter Kniesel, University of Bonn
  Doug Lea, SUNY Oswego
  David Lorenz, Northeastern University
  Joseph Loyall, BBN Technologies
  Mira Mezini, Darmstadt Technical University
  Klaus Ostermann, Siemens AG
  Roman Pichler, Siemens AG
  Calton Pu, Georgia Tech
  Vugranam C. Sreedhar, IBM T. J. Watson Research Center

WORKSHOP ORGANIZING COMMITTEE

  Yvonne Coady, University of British Columbia
  Eric Eide, University of Utah
  David Lorenz, Northeastern University
  Mira Mezini, Darmstadt Technical University
  Klaus Ostermann, Siemens AG
  Roman Pichler, Siemens AG