SPECIAL OFFER
Use code BACKTOLEARN during checkout to save 50% on books, eBooks, & videos. Shop now.
Register your product to gain access to bonus material or receive a coupon.
Extreme Programming (XP) is a flexible programming discipline that emphasizes constant integration, frequent small releases, continual customer feedback, and a teamwork approach. With considerable fanfare, XP has taken the mainstream of software engineering by storm. It has been adopted by an increasing number of development organizations worldwide. At the first annual Conference on Extreme Programming and Flexible Processes in Software Engineering, held in Italy in June of 2000, leading theorists and practitioners came together to share principles, techniques, tools, best practices for XP, and other flexible methodologies.
Extreme Programming Examined gathers the 33 most insightful papers from this conference into one volume. With contributions from several visionaries in the field, these papers together represent the state-of-the-art in XP methodology as well as a glimpse at the future of XP.
Individual articles are organized into cohesive categories that allow the reader to learn and apply this material easily. Extreme Programming Examined addresses some of the most vital issues facing XP developers. It offers a high-level examination of XP programming theory and discusses specific methodologies, processes, techniques, tools, and case studies. You will find articles exploring specificand often misunderstoodtopics, including:
Extreme Programming Examined is a valuable resource that offers the practical techniques and deeper understanding that developers and programmers need to initiate and implement successful XP projects.
Introduction.
I. FOUNDATIONS OF XP AND FLEXIBLE TECHNIQUES.
1. Is Design Dead?, Marttin Fowler.II. METHODOLOGY AND PROCESS.
3. A Comparison of the Value Systems of Adaptive Software Development and Extreme Programming: How Methodologies May Learn from Each Other, Dirk Riehle.III. FLEXIBLE TECHNIQUES AND UML.
<P>Chapter 9. XP Inside the Trojan Horse: Refactoring the Unified Software Development Process, Jutta Eckstein and Rolf F. Katzenberger.IV. PAIR PROGRAMMING, TESTING, AND REFACTORING.
<P>Chapter 14. The Costs and Benefits of Pair Programming, Alistair Cockburn and Laurie Williams.Appendix: The "Expert-In-Earshot" Project Management Pattern.
15. Unit Testing in a Java Project, Peter Gassmann.Sample Code.
16. Retrofitting Unit Tests with JUnit, Kevin Rutherford.V. TOOLS FOR XP DEVELOPMENT.
Chapter 19. Developing the Refactoring Browser, Ralph Johnson.VI. PRACTICAL EXPERIENCES.
23. The VCAPS Project: An Example of Transitioning to XP, Don Wells and Trish Buckley.VII. XP AND BEYOND.
28. Learn XP: Host a Boot Camp, Christian Wege and Frank Gerhardt.
Only geniuses can make difficult things simple, while any idiot can make a simple task difficult! Albert Einstein used to say something like that and we think that it applies quite well to extreme programming. Extreme programming aka XP, (and other flexible methodologies) are an extreme attempt to dramatically simplify the process of developing software systems, focusing on what delivers value: the requirements for the system and the code that implements the system. There isn't much else!
In extreme programming everything starts with the requirements in the form of user stories. The customers deliver and prioritize the user stories. The developers analyses such stories and write tests for them.
... and everything ends with code. The code is developed in pairs of developers to increase quality. The code is refactored to make it simpler. The code is tested against requirements, constantly.
... and there is nothing in between!
Both requirements and code are subject to a careful scrutiny: as mentioned, the code does exactly what the user stories tell and nothing more and is always maintained to highest possible form.
This collection contains experiences in extreme programming and other flexible methodologies. It discusses what is in extreme programming -requirements and code, and how we can improve it.
The flow of the topics in the volume is top down. We start with the foundations, then we move to process, practices, tool support, experiences, to end with possible new avenues for exploration.
The volume starts with a discussion of the essence of XP and other flexible methodologies. Martin Fowler argues about the role of design. Peter Merel synthesizes the principles of XP.
The second section focuses on methodologies and processes. After a discussion of the value system of XP by Dirk Riehle and other methodologies and of the role of just-in-time software development by Alistair Cockburn, a comprehensive analysis of frameworks and other large software development practice take place through the contributions of Lars-Göran Andersson, Mark Collins-Cope, Carsten Jacobi, Even-André Karlsson, Martin Lippert, Hubert Matthews, Stefan Roock, Bernhard Rumpe, Henning Wolf, and Heinz Züllighoven.
In the third section, several authors attempt to combine what other people consider not compatible: flexible methodologies with UML. Jutta Eckstein and Rolf Katzenberger compare the Unified Software Development Proces (USDP) to XP; Michele Marchesi and Giuliano Armano present experience in the field inside newly created companies. Marko Boger, Toby Baier, and Frank Wienberg detail an interesting approach to fast modeling software systems. Focardi and the two of us explain why XP is different using the formalism of stochastic graphs. Joshua Kerievsky conciliates design patterns with XP.
The fourth section contains experiences and consideration on three key practices of XP: pair programming (Alistair Cockburn and Laurie Williams), testing (Philip Craig, Steve Freeman, Peter Gassmann, Tim Mackinnon, and Kevin Rutherford), and refactoring (Neelam Soundarajan).
The fifth section reviews existing tools to support pair programming with focus on refactoring (Ralph Johnson); XP specific team support (Jim des Rivières, Erich Gamma, Ivan Moore, Kai-Uwe Mätzel, Jan Schümmer, Till Schümmer, André Weinand, and John Wiegand) testing (Renato Cerqueira and Roberto Ierusalimschy).
Karl Boutin, Michael Kircher, Manfred Lange David Levine, Peter Sommerlad, and Don Wells present their experiences in XP in section 6.
Champagne at the end! Sparkling ideas on how to address some terrifying aspects of XP are presented in the end of the book! Christian Wege and Frank Gerhardt outline their approach to teaching XP. Arie van Deursen, Tobias Kuipers, and Leon Moonen address the issue of legacy code. Paolo Predonzani, Giancarlo Succi, and Tullio Vernazza discuss how to handle the management of variants in an extreme environment. The inherent extreme flexibility of software agents is discussed by Luigi Benedicenti, Raman Paranjape, Kevin Smith. Jason Yip, Giancarlo Succi, Eric Liu explain how several products developed using XP can be organized in a line of production, without becoming heavy weighted.
A
Abstract data types (ADTs) versus pair programming, 111112
ACE (Adoptive Communication Environment), 463464
code ownership, 474
development by DOC group, 467
refractoring, 475476
testing, 475
XP for large project, 476479
The ACE ORB. See TAO
Activities (USDP), 141, 149151
Activity explorer, 370372
Adaptive Leadership-Collaboration model, 39
Adaptive Software Development. See ASD
Adoptive Communication Environment (ACE), 463464
code ownership, 474
development by DOC group, 467
refractoring, 475476
testing, 475
XP for large project, 476479
ADTs (abstract data types) versus pair programming, 111112
Aglets distributed agent system, 538
Apcon Workplace Solutions Ltd. (JWAM), 104105
APIs (application programing interfaces), XP in open-source projects, 469
Application development. See Software development
Application layer, architectural reference model, 5758
Architectural layering, reference model, 5254
application layer, 5758
basics, 5457
compromises, 6667
domain layer, 58
infrastructure layer, 5859
interface layer, 57
Architectural layering
motivation, 54
platform software layer, 59
requirements, 6465
rules, 59
semantics, 5961
support of XP, 6266
USDP, 143144, 166
ArgoUML tool, 187188
Artifacts (USDP), 141, 151153
activities, 149
ASD (Adaptive Software Development). See also Software development; XP
basics, 3941
emergence, 37
value systems model, 4445
XP, comparison, 3839, 43, 4546
XP, compatibility, 4648
Automated testing
C++ project, integrating XP, 453
external customers, 430431
transitioning to XP project, 416417
Automated testing, CORBA-based distributed system
basics, 379381
Distributed Sonar Simulator project, 381385
LuaOrb tool, basics, 385390
LuaOrb tool, test implementation, 390392
Awareness model, 360, 363364
activity explorer, 370372
cooperative browsers, 369370
FLECSE tools, 372373
project examples, 365368
B
Backward compatibility, versioning, 7477
Baselines for scheduling, framework development, 107108
Bespoke components, infrastructure layer, architectural reference model, 58
C
C++
conversions between classes, 526527
policy classes, 519522
policy classes, combining multiple classes, 523526
policy classes, generic behavior, 522523
templates as design constraints, 518519
C++ project, integrating XP
design strategies, 455
error simulations, 454
pair programming, 459460
problems to be solved, 450
refractoring, 456458
testing, automated, 453
testing, interfaces, 452
testing, multithreaded, 451452
Capability Maturity Model
(CMM), 43
CAS (Complex Adaptive Systems), 39
Cayley tree, 198199
Center for Distributed Object Computing (DOC) and XP, 464467
40-hour week guideline, 476
group roles, 473474
Center of gravity, applications, defined, 60
Change curve, software development, 67
Chime tool, 372373
Class browser, 369370
Class-Responsbility Collaboration (CRC) cards, 14, 166167
VCAPS project, 406408
Classes
C++ policy classes, 519522
C++ policy classes, combining multiple classes, 523526
C++ policy classes, conversions between classes, 526527
C++ policy classes, generic behavior, 522523
versus interfaces, 209
refractoring, 306310
"Clever code," 10
CloneDr tool, 505
CMM (Capabililty Maturity Model), 43
Coaching in software development, 2527
VCAPS transitioning project, 412413
COAST groupware framework, TUKAN development, 364
Code and fix development, 3
team communication, 157
Code ownership
team practices (XP),
335336
transitioning to XP, VCAPS project, 409
XP in open-source projects, 474
Coding, basic XP approach, 86
Collaborative programming. See Pair Programming
Compatibility, versioning in framework development, 7477
Complex Adaptive Systems (CAS), 39
Components of applications, defined, 5455
Confucius, doctrines compared to traditional software development, 1920
Construction phase, USDP, 140, 167169
Control flags, refractoring, 311312
Cooperative class browser, 369370
CORBA-based distributed system, automated testing
basics, 379381
Distributed Sonar Simulator project, 381385
LuaOrb tool, basics,
385390
LuaOrb tool, test implementation, 390392
Corvette framework, unit testing in JUnit, 271
CRC (Class-Responsbility Collaboration) cards, 14, 166167
VCAPS project, 406408
Crystal, 37
D
Daily builds, Ericssons GSM division project, 121125
design impact, 126129
testing advantages, 129130
Data-change information (DCI), 123
Deprecated tags, framework development, 77, 79
Design strategies
based on end-user functionality or system modules, 126127
C++ project, integrating XP, 455
code and fix, 3
multiple solutions, 517518
planned versus evolutionary, 46
Simple Design, 810
templates as constraints, 518519
up-front, 3
Design strategies (XP)
approach, 86
lightweight methodology, 8788
open-source projects, 469470
practices, 67
skills required, 16
Design view of components, 55
Diagrams
Front Door use case, 23
XP and UML, 1315
Diagrams, UML
documentation, 1415
execution, 177179
interactions, 179180
interactions with code, 180
layered architecture, 5253
Distribution, XP
communication-centered view, 357363
problems, 361
DOC (Center for Distributed Object Computing) and XP, 464467
40-hour week guideline, 476
group roles, 473474
DocGen tool, 504505
Documentation, UML diagrams, 1415
Domain layer, architectural reference model, 58
DRY ("Dont Repeat Yourself") practice, 10
E
Economics, XP for external customers, 426
Elaboration phase, USDP,
166167
ENVY
versus TUKAN, 372
TUKAN development, 364
Evolutionary design,
Only geniuses can make difficult things simple, while any idiot can make a simple task difficult! Albert Einstein used to say something like that, and we think that it applies quite well to extreme programming. Extreme programmingaka XP(and other flexible methodologies) are an extreme attempt to dramatically simplify the process of developing software systems, focusing on what delivers value: the requirements for the system and the code that implements the system. There isnt much else!
In extreme programming everything starts with the requirements, in the form of user stories. The customers deliver and prioritize the user stories. The developers analyze such stories and write tests for them.
. . . and everything ends with code. The code is developed by pairs of developers to increase quality. The code is refactored to make it simpler.
The code is tested against requirements, constantly.
. . . and there is nothing in between!
Both requirements and code are subject to careful scrutiny: as mentioned, the code does exactly what the user stories tell and nothing more and is always maintained to its highest possible form.
This collection contains experiences in extreme programming and other flexible methodologies. It discusses what is in extreme programmingrequirements and codeand how we can improve it.
The flow of the topics in this book is top down. We start with the foundations, then we move to process, practices, tool support, and experiences, and end with possible new avenues for exploration.
This book starts with a discussion of the essence of XP and other flexible methodologies. Martin Fowler argues about the role of design. Peter Merel synthesizes the principles of XP.
The second part focuses on methodologies and processes. After a discussion of the value systems of XP and other methodologies by Dirk Riehle a comprehensive analysis of frameworks and other large software development practices take place through the contributions of Lars- Göran Andersson, Mark Collins-Cope, Carsten Jacobi, Even-André Karlsson, Martin Lippert, Hubert Matthews, Stefan Roock, Bernhard Rumpe, Henning Wolf, and Heinz Züllighoven.
In the third part, several authors attempt to combine what other people consider incompatible: flexible methodologies and UML. Jutta Eckstein and Rolf Katzenberger compare the Unified Software Development Process (USDP) with XP; Giuliano Armano and Michele Marchesi present experience in the field inside newly created companies. Marko Boger, Toby Baier, Frank Wienberg, and Winfried Lamersdorf detail an interesting approach to fast modeling software systems. Sergio Focardi and the two of us explain why XP is a genetically different way of developing software using the formalism of stochastic graphs. Joshua Kerievsky conciliates design patterns with XP.
The fourth part contains experiences and consideration of three key practices of XP: pair programming (Alistair Cockburn and Laurie Williams), testing (Philip Craig, Steve Freeman, Peter Gassmann, Tim Mackinnon, and Kevin Rutherford), and refactoring (Neelam Soundarajan).
The fifth part reviews existing tools for supporting pair programming with a focus on refactoring (Ralph Johnson); XP-specific team support (Jim des Rivières, Erich Gamma, Ivan Moore, Kai-Uwe Mätzel, Jan Schümmer, Till Schümmer, André Weinand, and John Wiegand); and testing (Renato Cerqueira and Roberto Ierusalimschy).
Karl Boutin, Michael Kircher, Manfred Lange, David Levine, Peter Sommerlad, and Don Wells present their experiences in XP in Part 6.
Champagne at the end! Sparkling ideas on how to address some terrifying aspects of XP are presented at the end of the book! Christian Wege and Frank Gerhardt outline their approach to teaching XP. Arie van Deursen, Tobias Kuipers, and Leon Moonen address the issue of legacy code. Andrei Alexandrescu explains how flexible methodologies can be implemented in C++. Paolo Predonzani, Giancarlo Succi, and Tullio Vernazza discuss how to handle the management of variants in an extreme environment. The inherent extreme flexibility of software agents is discussed by Luigi Benedicenti, Raman Paranjape, and Kevin Smith. Jason Yip, Giancarlo Succi, and Eric Liu explain how several products developed using XP can be organized in a line of production, without becoming heavyweight.