Architecture and design in extreme programming; introducing “developer stories”

Authors:
Rolf Njor Jensen;Thomas Møller;Peter Sönder;Gitte Tjørnehøj
Affiliations:
Department of Computer Science, Aalborg University, Aalborg Ø, Denmark;Department of Computer Science, Aalborg University, Aalborg Ø, Denmark;Department of Computer Science, Aalborg University, Aalborg Ø, Denmark;Department of Computer Science, Aalborg University, Aalborg Ø, Denmark
Venue:
XP'06 Proceedings of the 7th international conference on Extreme Programming and Agile Processes in Software Engineering
Year:
2006

Citing 9
Cited 0

Extreme programming explained: embrace change

Extreme programming explained: embrace change
Embracing Change with Extreme Programming

Computer
Reducing Coupling

IEEE Software
Requirements Engineering and Agile Software Development

WETICE '03 Proceedings of the Twelfth International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises
Who Needs an Architect?

IEEE Software
XP Culture: Why the twelve practices both are and are not the most significant thing

ADC '03 Proceedings of the Conference on Agile Development
Continuous Design

IEEE Software
Extreme Programming Explained: Embrace Change (2nd Edition)

Extreme Programming Explained: Embrace Change (2nd Edition)
Metaphor design spaces

XP'03 Proceedings of the 4th international conference on Extreme programming and agile processes in software engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

This article introduces a new practice to eXtreme Programming (XP): Developer stories. The goal of these stories and their creation process is to incorporate architectural planning to XP thus ensuring a viable architecture. By conducting a small development project using XP, we find that establishing a viable architecture might be problematic. Arguing that architectural quality criteria in XP are traceable to traditional criteria, and by pointing to related work regarding incremental continous design, requirements management and large-scale refactorings, we find support for this claim. We proceed by describing the new practice ensuring that it embraces the values, and supports existing practices of XP.