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

Workshop March 22, 2004, Lancaster, UK

Call for Papers
Organising Committee
Program Committee
Workshop Program
Workshop Papers
Related Links

Early Aspects

In conjunction with 3rd International Conference on Aspect-Oriented Software Development 
March 22-26, 2004,
Lancaster, UK

Supported by


Workshop Program

You can download the program as a pdf document.

This workshop will provide attendees with a forum for discussing issues that can lead to a better understanding of how aspects can be used to support systematic and rigorous development of software from the very early stages such as requirements engineering and architecture design.

The workshop aims on the one hand to highlight the ongoing research on the workshop topics and on the other hand intends to provide an interactive event with ample opportunity for discussions. These two goals will be reflected in the program. The morning session will include presentations on the accepted papers for the workshop and will reflect the novel achievements in early aspect-oriented software development. The afternoon session will be completely organised around discussions. To support the interactions some creativity techniques will be applied goal of the discussions is to describe a complete life-cycle aspect-oriented approach to software system engineering that seamlessly bridges early aspects, design/implementation aspects, and aspects during deployment. To make the ideas concrete we will use one example case throughout the discussion sessions. This will also help to validate the identified problems and the provided solutions. At the end of the workshop we should have a common understanding and vision on the topic of early aspects.


8:45-9:00 Introduction to workshop (start 15 minutes earlier!)
Bedir Tekinerdoğan
09:00 - 10:30 Presentation Session
  Aspect-Oriented Requirements Engineering
Ana Moreira
9:00-9:15 Finding Aspects in Requirements with Theme/Doc
E. Baniassad, S. Clarke 
9:15-9:30 Integrating the NFR framework in a RE model
I.Brito, A. Moreira
9:30-9:45 Tracing aspects in goal driven requirements of process control systems
I. El-Maddah, T. Maibaum
  Aspect-Oriented Architecture Design
: Bedir Tekinerdoğan/Paul Clements
9:45-10:00 Generating Aspect-Oriented Agent Architectures
U. Kulez
sa, A. Garcia, C. Lucena
10:00-10:15 Identifying Aspects Using Architectural Reasoning
L. Bass, M. Klein & L. Northrop
10:15-10:30 Problems, subproblems and concerns
M. Jackson

Morning Break

11:00-14:30 Discussion Session I Key Problems and Motivations
11:00-12:30 Discussions in sub-groups
Moderator: Bedir Tekinerdoğan

Goal: Provide a common agreement on the identified problems;
How: Use the example case study together with the given and/or new scenarios and define in a concrete way what the most fundamental problems are within each group.

Split the group into four sub-groups:
     Requirements Engineering
B.     Software Architecture Design
C.     Domain Engineering/Application Domain
D.     Specifying Early Aspects

The sessions should deliver (1) a mindmap and (2) a set of problem descriptions:

(1) Mindmap: Draw one mindmap that shows the context of the described problems/domain.  A mindmap represents related ideas and concepts (more info)
(2) The problems should be described in the following form:

: describe textually what the problem is.
Why is it a problem?:
 Motivate why this is a fundamental problem.      
: Use the example case to explain the problem. You may use scenarios here.


14:00-14:30 Plenary Session: Presenting Fundamental Problems
: Ana Moreira/Paul Clements
Results of Discussion Session I are presented plenary and shortly discussed. The problems are ordered in the life-cycle model.
14:30-16:30    Discussion Session II Promising Solutions

Discussions in sub-groups
Regroup the previous sub-groups to pollinate the ideas

Moderator: Ana Moreira/Paul Clements
: Show potential solutions for the presented problems.
:  Provide a list of solutions using the example case.

The session should deliver a set of solution descriptions. A solution description should be in the following format:

: Describe the solution to the fundamental problems in session one.
Knowledge Domain: List the related knowledge domains/related work
for this solution
Example: Use the example case to explain the solution. If no solution exists yet, describe the possible ways for finding a solution.
Fail Criteria: describe when the solution will fail
Open issues: Describe what needs still to be done; open issues/consequences

15:30 - 16:00

Afternoon break

16:00 16:30

Plenary Session: Show the result of Session II (Solutions)                             Moderator: Joo Arajo

16:30-17:30    Discussion Session III Setting the Research Agenda
16:30-17:00 Discussions in sub-groups
Moderator: Joo Arajo

Goal: Describe the open problems/research issues that must be addressed in the
coming years with respect to early aspects topic
:  Provide a list of research topics.
What should be in the research agenda of early aspects? Show with example case.
17:00-17:30 Plenary Session: Presenting the Research Agenda for next years