[abc] AO Book 2006: (fwd)

any thoughts?

---------- Forwarded message ----------
Date: Mon, 22 Aug 2005 21:13:33 +0200 (CEST)
From: Sami Beydeda <beydeda@gmx.de>
To: Oege de Moor <Oege.de.Moor@comlab.ox.ac.uk>
Subject: AO Book 2006:

Dear Oege,

we would like to invite you to submit a chapter to the book "Testing
and Analysis in Aspect-Oriented Software Development" we are
currently editing. We are inviting you in particular due to your
deep insight in testing and analysis in this area which you have
showed in numerious publications.

Please feel free to forward this invitation to others who might be
interested in submitting a chapter and do not hesitate to contact us
for additional information.

With best regards,

      Sami

CALL FOR CHAPTERS
Chapter submission deadline: November 1st, 2005
Notification deadline: January 1st, 2006

Testing and Analysis in Aspect-Oriented Software Development
======= === ======== == ====== ======== ======== ===========

A book edited by
Sami Beydeda, Bundesamt fuer Finanzen (Federal Finance Office),
Germany
Volker Gruhn, University of Leipzig, Germany

URL: http://www.paperdyne.com/aobook06.html

Introduction
------------

One of the problems frequently met in the development of a software
system with an industrial scale size is to ensure system properties
whose implementation "cross-cut" the implementation of that system's
functionality. "Cross-cut" refers in the terminology used in
aspect-oriented development to adverse effects on, e.g.,
maintainability. A prominent sample of such properties is
efficiency.

An approach to tackle this problem is aspect-oriented software
development proposed by Kiczales et al. It avoids this problem by
handling implementation of system functionality orthogonally from
the implementation of the property desired. Both system
functionality and the property desired are formulated in the
specific languages and the system is obtained by "weaving" them.
Thus, the property desired is ensured without the adverse effects
usually encountered.

The Overall Objective of the Book
---------------------------------

The objective of the book is twofold. Firstly, It aims at outlining
the problems and open issues encountered in testing and analysis in
aspect-oriented development. Aspect-oriented development
significantly differs from other paradigms and has its own specific
problems not encountered in other paradigms. The differences are not
always obvious and need to be outlined. Secondly, it aims at
summarizing current research in the area of testing and analysis in
aspect-oriented development. In recent years, significant progress
has been achieved in this area at a conceptual as well as a
technical level.

The Target Audience
-------------------

The target audience will be professionals and researchers working in
the area of aspect-oriented development. The problems and open
issues outlined together with the summary of achievements will give
a clear insight into the area of testing and analysis in
aspect-oriented development. This insight into the area can lead
professionals in concrete software development projects and can be a
basis for further work for researchers.

The Contents of the Book
------------------------

The book will have four parts. Each of these four parts will address
specific perspectives of aspect-oriented development.

Part I: Introduction
This part of the book will give a brief introduction to
aspect-oriented development. More important, this part aims at
explaining the issues which make testing and analysis in
aspect-oriented development different to testing and analysis in
other development paradigms. Discussion of fault models specific to
aspect-oriented development can be an example for this part.

Part II: Dynamic testing and analysis techniques
The second part of the book will be dedicated to techniques in
testing and analysis which require execution of the program under
consideration. This part will in particular encompass techniques of
traditional testing, for instance, based on data-flow analysis.

Part III: Static testing and analysis techniques
In contrast to the second part of the book, this part will focus on
static techniques of testing and analysis of programs developed
according to the aspect-oriented paradigm. Typical examples of such
techniques are formal verification and model checking.

Part IV: Case studies and experience from industry
Finally, this part will give case studies which have been conducted
to study techniques for testing and analysis in the development of
aspect-oriented programs. Furthermore, this part will also give
space for researchers and practitioners from industry who can
formulate their experience but also their requirements.

Submission Procedure
--------------------

Chapter submission deadline: November 1st, 2005
Notification deadline: January 1st, 2006

Researchers and practitioners are invited to submit a chapter on or
before November 1st. The submissions will undergo a thorough review
process and authors will be notified by January 1st, 2006.

Submission URL: http://www.paperdyne.com/aobook06.html

Publication
-----------

The editors are in contact with Springer to publish accepted
chapters as a book similar to "Testing Commercial-off-the-Shelf
Components and Systems"
(http://www.springeronline.com/sgw/cda/frontpage/0,11855,5-146-22-33835936-0,00.html).

Contact Info
------------

Inquiries and submissions can be forwarded electronically to:

Sami Beydeda
E-mail: sb@stecc.de

Volker Gruhn
E-mail: gruhn@ebus.informatik.uni-leipzig.de
Received on Tue Aug 23 13:22:00 2005