Call For contributions and participations
Workshop on Architecture-Centric Methods and Agile Approaches
Co-located with the 10th International Conference on Agile Processes and
eXtreme Programming in Software Engineering (XP 2009) -
http://www2.xp2009.org/xp2009/ Sardinia, Italy, 25 - 29 May 2009
Deadline for contributions: 10 April, 2009
Workshop Theme and Goals
Agile software development approaches have had significant impact on
industrial software development practices. Many software development
companies, (e.g. Nokia, Philips, ABB, Volvo, Ericsson, SAP, Microsoft,
to name a few), across the globe are increasingly adopting agile
approaches with an intention to increase quality, productivity, and
Despite becoming widely popular, there is an increasing perplexity about
the role and importance of a system's software architecture in agile
approaches [1, 2]. Advocates of the vital role of architecture in
achieving quality goals of large-scale-software-intensive-systems are
skeptics of the scalability of any development approach that does not
pay sufficient attention to architectural issues, especially in domains
like automotive, telecommunication, finance, and medical devices.
However, the proponents of agile approaches usually perceive the upfront
design and evaluation of architecture as being of less value to the
customers of a system. According to them, for example, re-factoring can
help fix most of the problems. Many experiences show that large-scale
re-factoring often results in significant defects, which are very costly
to address later in the development cycle. It is considered that
re-factoring is worthwhile as long as the high-level design is good
enough to limit the need for large-scale re-factoring [1, 3, 4].
There is a growing recognition of the importance of paying more
attention to architectural aspects in agile approaches [4-7].
Researchers and practitioners have also identified the technical and
organizational challenges involved in integrating Agile approaches in
traditional software development methods [8, 9]. However, while
anecdotal evidence reveals that there are large organizations in the
midst of agile transformation and that the architectural issues are
somehow addressed, there has been no significant effort aimed at
synthesizing and presenting a reliable body of knowledge about the
architecture-centric challenges being faced by agile software
development projects and potential solutions to address those
Hence, it is an emerging consensus among researchers and practitioners
that there is a vital need for devising a research agenda for
identifying and dealing with architecture-centric challenges in agile
software development . Such research agenda is expected to make it
possible to guide the future research on integrating
architecture-centric methods in agile approaches and give advice to the
software industry on dealing with architecture related challenges.
The overall goal of this workshop is to refine and further develop the
research agenda developed in the previous workshop [10, 11]. Developing
such an agenda will require activities for brainstorming, discussion and
reaching consensus on important directions. To foster discussions at the
workshop, the accepted position statements will be put online before the
event and the prospective participants will be invited to read them as
preparation for the workshop. Moreover, we will also update the Wiki
setup for the last workshop to reflect the research progress that has
been made since the last workshop. During the previous workshop on this
topic, held at XP08, the organizers and participants identified several
research questions that are expected to stimulate the group discussions
in the workshop. These questions are:
* How has the role of software architecture and software
architects changed in projects using Agile approaches and its impact on
the quality of the products and processes?
* What are the key architecture-centric challenges to implementing
Agile processes for developing large scale systems and potential
solutions available to practitioners?
* How can the considerations for non functional requirements be
appropriately addressed while using Agile approaches?
* What are the prerequisites for integrating Architecture-Centric
methods in agile development and potential implications of such
integration on the processes and products?
* What kind of training needs to be provided in the areas of
architecture-centric technologies (methods, techniques, and tools),
customization and integration of architecture-centric approaches into
Agile software development process?
* How can the use of patterns by agile developers help address
architectural issues related to the required quality attributes?
* How does the architectural knowledge transfer from design to
implementation in agile software development settings?
The workshop will be divided in two parts:
Part one will include short presentations of position statements and
identification of controversial topics.
Part two will consist of focused brainstorming and discussion activities
in order to deliberate on the relevant issues and research questions
Guidelines for Submission
We are looking for two categories of submissions:
* short position papers, up to 4 pages.
* Position statements, up to 2 pages or powerpoinnt slides.
Every submitted position papers and statements will be evaluated based
on the potenial for stimulating lively and productive discussions.
be e-mailed in PDF to Ali Babar (malibaba "at" lero.ie) with
"Architecture-Agile 2009" in the subject line.
All the accepted position papers and statements will be made available
on the workshop Wiki before the workshop.
10 April 2009 - deadline for submission
13 April 2009 - notification
15 April 2009 - Registration
29 May 2009 - Workshop
* Muhammad Ali Babar, Lero, Ireland, [log in to unmask]
* Pekka Abrahamsson, University of Helsinki, Finland,
[log in to unmask]
To contribute to SEWORLD, send your submission to
<[log in to unmask]>.
http://www.cs.colorado.edu/serl/seworld provides more
information on SEWORLD as well as a complete archive of
messages posted to the list.
To subscribe to SEWORLD, send the following (as the body of
a message) to <[log in to unmask]>:
subscribe seworld <desired e-mail address>
To unsubscribe from SEWORLD, send the following (as the body
of a message) to <[log in to unmask]>:
unsubscribe seworld <registered e-mail address>