ACP4IS.09
ACP4IS.09-


Call For Papers -


Organizers -


Papers -


Program
Past Years
AOSD.09
8th Workshop on
Aspects, Components, and Patterns
for Infrastructure Software (ACP4IS '09)
| News and Announcements | Important Dates: Updated! |
|||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||
| List of accpeted papers posted | Feb. 16st 2009 | |||||||||
| Submission Deadline moved | Dec. 1st 2008 | |||||||||
| Website up | Oct 13th, 2008 | |||||||||
Aspect-oriented programming, component models, and design patterns are modern and actively evolving techniques for 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 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.
Building on the ACP4IS meetings at AOSD 2002-2008, 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.
