<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><font class="Apple-style-span" face="Courier"><div>********************************************************************</div><div> 9th AOSD Workshop on Aspects, Components, and Patterns</div><div> for Infrastructure Software (ACP4IS)</div><div><br></div><div> March 16, 2010</div><div> Rennes and Saint Malo, France</div><div><br></div><div> <a href="http://aosd.net/workshops/acp4is/2010">http://aosd.net/workshops/acp4is/2010</a></div><div><br></div><div> A one-day workshop to be held in conjunction with the</div><div> 9th International Conference on</div><div> Aspect-Oriented Software Development (AOSD'10),</div><div> March 15 -- March 19, 2010, Rennes and Saint Malo, France</div><div> <a href="http://aosd.net/conference">http://aosd.net/conference</a></div><div><br></div><div>********************************************************************</div><div><br></div><div>The importance of "systems infrastructure" software - including</div><div>application servers, virtual machines, middleware, compilers, and</div><div>operating systems - is increasing as application programmers demand</div><div>better and higher-level support for software development. Vendors</div><div>that provide superior support for application development have a</div><div>competitive advantage. The software industry as a whole benefits as</div><div>the base level of abstraction increases, thus decreasing the need</div><div>for application programmers to continually "reinvent the wheel".</div><div><br></div><div>These trends, however, mean that the demands on infrastructure</div><div>software are increasing. More and more features and requirements are</div><div>being "pushed down" into the infrastructure, and the developers of</div><div>systems software need better tools and techniques for handling these</div><div>increased demands. The design and implementation of systems-level</div><div>software presents unique opportunities and challenges for AOSD</div><div>techniques. These challenges include the need to address the</div><div>inherent complexity of infrastructure software; the need for strong</div><div>assurances of correct and predictable behavior; the need for maximum</div><div>run-time performance; and the necessity of dealing with the large</div><div>body of existing systems software components.</div><div><br></div><div>This workshop aims to provide a highly interactive forum for</div><div>researchers and developers to discuss the application of and</div><div>relationships between aspects, components, and patterns within</div><div>modern infrastructure software. The goal is to put aspects,</div><div>components, and patterns into a common reference frame and to build</div><div>connections between the software engineering and systems</div><div>communities.</div><div><br></div><div>This year's workshop puts special focus on the challenges in</div><div>system's programming introduced by multi-core platforms. As</div><div>hardware-supported parallelization becomes mainstream, there is an</div><div>increasing pressure on systems infrastructure to exploit this new</div><div>parallelism to its fullest. However, the non-modular nature of</div><div>parallel execution, and the numerous levels at which parallelism can</div><div>be achieved (application, systems infrastructure, hardware or even a</div><div>combination) make it hard to come up with an intuitive, yet</div><div>efficient parallel architecture. We solicit novel ideas and</div><div>experience reports on this emerging research area.</div><div><br></div><div>Other suggested topics for position papers include, but are not</div><div>restricted to:</div><div><br></div><div>- Approaches that combine or relate component-, pattern-, and</div><div> aspect-based techniques</div><div><br></div><div>- Dimensions of infrastructure software quality including</div><div> comprehensibility, configurability (by implementers),</div><div> customizability (by users), reliability, evolvability,</div><div> scalability, and run-time characteristics such as performance and</div><div> code size</div><div><br></div><div>- Merits and downsides of container-, ORB-, and system-based</div><div> separation of concerns</div><div><br></div><div>- Architectural techniques for particular system concerns, e.g.,</div><div> security, static and dynamic optimization, and real-time behaviour</div><div><br></div><div>- Design patterns for systems software</div><div><br></div><div>- Component, pattern, and aspect "mining" within systems code</div><div><br></div><div>- Application- or domain-specific optimization of systems</div><div><br></div><div>- Reasoning and optimization across architectural layers</div><div><br></div><div>- Quantitative and qualitative evaluations</div><div><br></div><div>AGENDA</div><div><br></div><div>The workshop will be structured to encourage fruitful discussions</div><div>and build connections between workshop participants. To this end,</div><div>approximately half of the workshop time will be devoted to short</div><div>presentations of accepted papers, with the remaining half devoted to</div><div>semi-structured discussion groups. Participants will be expected to</div><div>have read the accepted papers prior to the workshop, to help ensure</div><div>focused discussions.</div><div><br></div><div>A novelty at ACP4IS '10 is that we will invite workshop attendees to</div><div>give "spontaneous" short presentations on their work if they see a</div><div>relation to topics being presented and discussed at the workshop.</div><div>These presentations will be limited to about ten minutes, and are</div><div>intended to provide additional structured input to discussions.</div><div>Spontaneous presentations will be asked for during the workshop; no</div><div>paper needs to be submitted, and no publication is associated with</div><div>them. There will be a session dedicated to them, just prior to</div><div>discussion.</div><div><br></div><div>SUBMISSION GUIDELINES</div><div><br></div><div>Invitation to the workshop will be based on accepted position</div><div>papers, 3-5 pages in length. All papers must be submitted as PDF</div><div>documents in ACM format through the ACP4IS 2010 online submission</div><div>system found at:</div><div><br></div><div><a href="http://www.easychair.org/conferences/?conf=acp4is10">http://www.easychair.org/conferences/?conf=acp4is10</a>. </div><div><br></div><div>Paper submissions will be reviewed by the workshop program committee</div><div>and by designated reviewers. Papers will be evaluated based on</div><div>technical quality, originality, relevance, and presentation.</div><div><br></div><div>PUBLICATION OF PAPERS</div><div><br></div><div>All accepted papers will be posted at the workshop web site prior to</div><div>the workshop date, to give all participants the opportunity to read</div><div>them before the workshop. In addition, the Workshop Proceedings</div><div>will be published in a Technical Report (with ISBN/ISSN) issued by</div><div>Hasso-Plattner-Institut (<a href="http://www.hpi.uni-potsdam.de/welcome.html?L=1">http://www.hpi.uni-potsdam.de/welcome.html?L=1</a>)</div><div><br></div><div>IMPORTANT DATES</div><div><br></div><div>Paper submission deadline: December 21, 2009</div><div>Notification of acceptance: January 15, 2010</div><div>Final papers due: TBA</div><div>Workshop: March 16, 2010</div><div><br></div><div>PROGRAM COMMITTEE</div><div><br></div><div>- Mehmet Aksit, University of Twente</div><div>- Shigeru Chiba, Tokyo Institute of Technology</div><div>- Eric Eide, University of Utah</div><div>- Michael Engel, Technical University Dortmund</div><div>- Franz Hauck, Ulm University</div><div>- Julia Lawall, DIKU</div><div>- Hidehiko Masuhara, University of Tokyo</div><div>- Hridesh Rajan, Iowa State University</div><div>- Doug Simon, Sun Microsystems Laboratories</div><div>- Olaf Spinczyk, Technical University Dortmund</div><div>- Eric Wohlstadter, University of British Columbia</div><div>- Roel Wuyts, IMEC and K.U. Leuven</div><div><br></div><div><br></div><div>ORGANIZING COMMITTEE</div><div><br></div><div>- Bram Adams, Queen's University</div><div>- Michael Haupt, Hasso Plattner Institut</div><div>- Daniel Lohmann, FAU Erlangen-Nuremberg</div><div><br></div><div>STEERING COMMITTEE</div><div><br></div><div>- Eric Eide, University of Utah</div><div>- Olaf Spinczyk, University of Dortmund</div><div>- Yvonne Coady, University of Victoria</div><div>- David Lorenz, University of Virginia</div><div><br></div></font></div></div></body></html>