In conjunction with second Aspect-Oriented Software Development (AOSD)  Conference, Boston, USA,
March 17-21,
 2003
 

Early Aspects 2003: 
Aspect-Oriented Requirements Engineering and Architecture Design

Workshop, March 17 - Boston, USA

Call for Papers Organizing Comittee Program Committee Workshop Program Workshop Papers Workshop Report Related Links




These pages are maintained by: Bedir Tekinerdogan

Call for Papers

Prospective participants are invited to submit a 4-6 pages position paper. All submissions will be reviewed by members of the program committee and the organising committee for quality and relevance. Three or four papers will be chosen to be presented during the workshop with the aim to foster discussions. Attendance is by having a paper accepted, or by special invitation.

The workshop will elaborate on the topics of the first early aspects workshop in 2002. Topics of interest for this workshop will include, but will not be limited to: 

bullet

Aspect-oriented requirements engineering
- How to identify aspects at the requirements level?
- How to model aspects at the requirements level?
- How to integrate and compose aspects with other modelling mechanisms, such as goals, viewpoints and use cases, and establish trade-offs?
- How to trace requirements level aspects through later development stages and during re-engineering?
- How to validate aspects identified at the requirements level?

 

bullet

Aspect-Oriented domain engineering
- What are the criteria for domain aspect decomposition?
- How can we derive aspects from domain knowledge?
- How can we abstract and generalize domain aspects for reuse?
- What are the composition relations between domain aspects?
- How to represent domain aspects?

 

bullet

Mapping between aspect-oriented requirements, domain analysis and architecture
- Should the mapping be formal or informal?
- To what is a requirements concern mapped onto?
- What are the language’ features required to support a mapping?
- What is the benefit ratio of mapping/coding?

 

bullet

Aspect-oriented architecture design
- How to support evolution in the architecture using aspects?
- How to reason about architectures and aspects to know that the architecture is a good one (trade-offs between aspects)?
- How to model the architecture to take aspects into account?
- When designing an architecture, how and when to identify aspects?
 

bullet

Tool support and automation for aspect-orientation
- Which tools are there to support aspect-oriented development?
 

bullet

Formalisms and notations for specifying aspects
- What formalisms can be used at early software development stages?

E-mail

Submissions should be sent to ja@di.fct.unl.pt and should be in either PDF, Postscript,  or Word format.

Important Dates

Deadline for sending position papers: January 27, 2003

Date of notification: February 10, 2003