Call for Papers
Aspects have made a visible impact on software design and programming. This is because the concept contributes to our understanding of system construction, modularization, and the articulation of important functional and non-functional concerns. The question for this workshop is "How do aspects influence the description of architectures?" This is of interest for both software architecture and system architectures [2].
The on-going revision of IEEE 1471 (now also ISO/IEC DIS 42010), Recommended practice for the architectural description of software-intensive systems [3], provides an opportunity for the aspects community to influence thinking in architecture, particularly with respect to how aspect concepts interact with the use of architectural viewpoints and the ability of aspects to capture non-functional concerns about architectures within architectural descriptions.
As demonstrated in the Early Aspects series of workshops, aspects have applicability for specifying architectural properties; both emergent properties of the system as a whole and the contributions of architectural components to emergent properties, including the ability to check architectural components against aspect 'requirements' for that component. The results of this workshop should offer insights, guidance, and examples for the community using aspects and serve as useful input into the revision of ISO/IEC DIS 42010.
Topics of Interest
Questions of interest to this workshop:
- How do aspects influence the description of architectures? How do we specify aspects within an architectural description?
- How do aspects relate to other practices of architectural description? Currently, architectural descriptions are often organized into views each addressing one or more concerns? How do aspects interact with this approach?
- Can aspects be used within, between views?
- How do aspects contribute to/participate in viewpoint definitions?
- How do aspects relate to views and viewpoints, viewtypes [1], perspectives [6] and textures [5]?
- Are aspects useful in systems architecture as well as in software?
- How are aspects and architectural decisions [4] related? Can aspects be used to record certain types of architectural decisions? Can aspects be used for "model checking" or "contract checking" of components within an architecture to ensure the component meets the intent of the architecture?
- What aspect combinators (e.g., before, after) make sense with architectural aspects?
- In a multi-viewpointed architectural description, what is the base for architectural aspects? Is the base a particular view (e.g., components-and-connectors), any view, all views?
It is hoped this workshop will attract participants familiar with current approaches to architectural description and participants interested in aspect-oriented development who seek to extend this paradigm to architecture.
Submissions
Submissions, addressing one or more of the topics identified above, should be 2 to 4 pages in length. Papers should be submitted in PDF to r.hilliard@computer.org. Papers will be selected based upon the issues and ideas raised that react to those topics.
Workshop format
To stimulate informed discussion among the participants, the selected position papers will be posted on the workshop's website prior to the workshop. Based on the themes of the submissions, some will be selected for presentation at the workshop to initiate discussion and reflection. These themes will also serve as a basis for one or more working sessions during the workshop. Following the workshop, all materials produced at the workshop will be published on the workshop website.
Workshop website: http://aosd.net/workshops/aarch/2007/
Important Dates
Submissions due: 22 January 2007
Notification of acceptance: 29 January 2007
Early Registration Deadline for AOSD: 9 February 2007
Workshop: 12 March 2006
Organizers
Paul Clements (Software Engineering Institute)
David Emery (DSCI, Inc.)
Rich Hilliard (workshop contact: r.hilliard@computer.org)
Philippe Kruchten (University of British Columbia)
References
[1] Clements, P., et al. (2002). Documenting Software Architectures: Views and Beyond, Boston: Addison-Wesley.
[2] Hilliard, R. (1999). Aspects, Concerns, Views, ... Proceedings of the OOPSLA'99 Workshop on Multi-Dimensional Separation of Concerns.
[3] IEEE Std 1471:2000–Recommended practice for architectural description of software-intensive systems. Los Alamitos, CA: IEEE.
[4] Kruchten, P., Lago, P., and van Vliet, H. (2006). Building up and reasoning about architectural knowledge. In C. Hofmeister (ed.), Proceedings of QoSA 2006 (LNCS Vol. 4214, pp. 43-58). Berlin: Springer-Verlag.
[5] Ran, A., (2000). ARES Conceptual Framework for Software Architecture. In Jazayeri, M., Ran, A., van der Linden, F. (eds.), Software Architecture for Product Families Principles and Practice. Addison-Wesley, Boston, pp. 1-29.
[6] Rozanski, N., and Woods, E. (2005). Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives. Boston: Addison-Wesley.