From: Paul C. Clements (clements@sei.cmu.edu)
Date: Wed Nov 17 2004 - 07:04:34 EST
Call for Workshop Participation
Early Aspects 2005: Workshop in
Aspect-Oriented Requirements Engineering and Architecture Design
March 14 or 15, 2005
Chicago, Illinois, USA
In conjunction with AOSD 2005
http://www.early-aspects.net/aosd05ws/
Early aspects are crosscutting concerns in the early life cycle phases including the requirements analysis, domain analysis and architecture design phases. Early aspects cannot be localized and tend to be scattered over multiple early life cycle modules. This reduces the modularity of the artifacts in the early life cycle which might consequently lead to serious maintenance problems. Unfortunately, conventional aspect-oriented software development approaches have mainly focused on identifying the aspects at the programming level and less attention has been taken on the impact of crosscutting concerns at the early phases of the software development. Obviously, the early software development phases actually set the early design decisions and have a large impact on the whole system. Coping with aspects at the early life cycle phases as such is a primary issue.
This workshop aims to support the cross-fertilization of ideas in requirements engineering, domain engineering, software architecture design and aspect-oriented software development in order to identify the problems and potential solutions of early aspects. It continues the work of four previous workshops on this topic held in conjunction with AOSD 2002-2004 and OOPSLA 2004, respectively. (Visit http://www.early-aspects.net/ to view results.)
Topics of interest for the workshop will include, but will not be limited to:
• Aspect-oriented requirements engineering
o How can we identify or model aspects at the requirements level? o What are ways to integrate and compose aspects with other modeling mechanisms, such as goals, viewpoints and use cases, and establish trade-offs? o How does one trace requirements aspects through later development stages and during re-engineering? o How are aspects identified at the requirements level validated?
• Aspect-Oriented domain engineering
o What are the criteria for domain aspect decomposition? o How can we derive aspects from domain knowledge? o How can we abstract and generalize domain aspects for reuse? o What are the composition relations between domain aspects? o How to represent domain aspects?
• Aspect-oriented architecture design
o How can aspects be used to support system quality attributes in the architecture? o How can we reason about architectures and aspects to know that the architecture is a good one? o How can we reason about trade-offs among aspects? o How can we model the architecture to take aspects into account? o When designing an architecture, how and when can we identify aspects? o How can we set the scope for a software product line architecture using aspects? o How do aspects fit in the Model-Driven Architecture approach?
• Mapping between aspects in requirements, domain analysis, and architecture
o Should the mapping be formal or informal? o To what is a requirements concern mapped onto? o What language features are required to support a mapping? o What are the pros and cons of mapping?
• Tool support and automation for aspect-orientation
o Which tools are there to support aspect-oriented development?
• Formalisms and notations for specifying early aspects
o What formalisms can be used at early software development stages?
Important Dates
Deadline for sending position papers: Monday, January 17, 2005.
Date of notification: Monday, February 7, 2005.
Planned Workshop Format
The workshop will be highly interactive. During the morning session there
will be short presentations by authors of accepted papers. The rest of the
morning and afternoon will be reserved for discussions and overall
conclusions. The participants will form groups that reflect specific
topics. Then, the discussions will proceed by raising and debating relevant
questions, with an overall goal of producing tangible results of interest
to the community at large. Finally, each group will present their
conclusions and recommendations. The workshop will conclude with a
cross-group summary and discussion about next steps, including effective
ways to publish results.
Submission guidelines
Prospective participants are invited to submit a 2-5-page position paper.
All submissions will be reviewed by members of the program committee and
the organizing committee for quality and relevance. Attendance is by
having a paper accepted, or by special invitation. Papers should use IEEE
Proceedings format, as described at
http://www.computer.org/cspress/instruct.htm, and submitted in PDF format
to clements@sei.cmu.edu. Authors of accepted papers will then be asked to
prepare and submit a 3-viewgraph presentation aimed at stimulating workshop
discussion and progress. Details will be sent with acceptance notices.
Workshop Program Committee
Mehmet Askit. University of Twente, The Netherlands
Charles Haley, The Open University, UK
Paulo Merson, Software Engineering Institute / Carnegie Mellon University, USA
Pete Sawyer, Lancaster University, UK
Stan Sutton, IBM T. J. Watson Research Center, USA
Jon Wittle, NASA Ames Research Center, USA
Rob Walker, University of Calgary, Canada
Organizing committee
Paul Clements (Primary Contact)
Software Engineering Institute
Carnegie Mellon University
USA
clements@sei.cmu.edu
Awais Rashid
Computing Department
Lancaster University
Lancaster LA1 4YR
UK
awais@comp.lancs.ac.uk
Elisa Baniassad
Distributed Systems Group
Dept of Computer Science
O'Reilly Institute, Trinity College
Dublin 2, Ireland
Elisa.Baniassad@cs.tcd.ie
Bedir Tekinerdogan
Department of Computer Science
University of Twente
The Netherlands
bedir@cs.utwente.nl
Ana Moreira
Departamento de Informática
Faculdade de Ciências e Tecnologia
Universidade Nova de Lisboa
2829-516 Caparica, Portugal
amm@di.fct.unl.pt
João Araújo
Departamento de Informática
Faculdade de Ciências e Tecnologia
Universidade Nova de Lisboa
2829-516 Caparica, Portugal
ja@di.fct.unl.pt
This archive was generated by hypermail 2.1.6 : Mon Nov 22 2004 - 09:00:22 EST