Déjà client ? Identifiez-vous

Mot de passe oublié ?

Nouveau client ?

CRÉER VOTRE COMPTE
Extreme Programming Explained
Ajouter à une liste

Librairie Eyrolles - Paris 5e
Indisponible

Extreme Programming Explained

Extreme Programming Explained

Embrace Change

Kent Beck

190 pages, parution le 10/09/1999

Résumé

Software development projects can be fun, productive, and even daring. Yet they can
consistently deliver value to a business and remain under control.

Extreme Programming (XP) was conceived and developed to address the specific needs of
software development conducted by small teams in the face of vague and changing
requirements. This new lightweight methodology challenges many conventional tenets,
including the long-held assumption that the cost of changing a piece of software necessarily
rises dramatically over the course of time. XP recognizes that projects have to work to
achieve this reduction in cost and exploit the savings once they have been earned.

Fundamentals of XP include:

  • Distinguishing between the decisions to be made by business interests and those to be
    made by project stakeholders.
  • Writing unit tests before programming and keeping all of the tests running at all times.
  • Integrating and testing the whole system--several times a day.
  • Producing all software in pairs, two programmers at one screen.
  • Starting projects with a simple design that constantly evolves to add needed flexibility
    and remove unneeded complexity.
  • Putting a minimal system into production quickly and growing it in whatever directions
    prove most valuable.

Why is XP so controversial' Some sacred cows don't make the cut in XP:

  • Don't force team members to specialize and become analysts, architects,
    programmers, testers, and integrators--every XP programmer participates in all of
    these critical activities every day.
  • Don't conduct complete up-front analysis and design--an XP project starts with a
    quick analysis of the entire system, and XP programmers continue to make analysis
    and design decisions throughout development.
  • Develop infrastructure and frameworks as you develop your application, not
    up-front--delivering business value is the heartbeat that drives XP projects.
  • Don't write and maintain implementation documentation--communication in XP
    projects occurs face-to-face, or through efficient tests and carefully written code.

You may love XP, or you may hate it, but Extreme Programming Explained will force
you to take a fresh look at how you develop software.

Table of contents


Foreword
Preface
Section 1: The Problem
Chapter 1: Risk: The Basic Problem
Chapter 2: A Development Episode
Chapter 3: Economics of Software Development
Chapter 4: Four Variables
Chapter 5: Cost of Change
Chapter 6: Learning to Drive
Chapter 7: Four Values
Chapter 8: Basic Principles
Chapter 9: Back to Basics
Section 2: The Solution
Chapter 10: Quick Overview
Chapter 11: How Could This Work?
Chapter 12: Management Strategy
Chapter 13: Facilities Strategy
Chapter 14: Splitting Business and Technical Responsibility
Chapter 15: Planning Strategy
Chapter 16: Development Strategy
Chapter 17: Design Strategy
Chapter 18: Testing Strategy
Section 3: Implementing XP
Chapter 19: Adopting XP
Chapter 20: Retrofitting XP
Chapter 21: Lifecycle of an Ideal XP Project
Chapter 22: Roles for People
Chapter 23: 20–80 Rule
Chapter 24: What Makes XP Hard
Chapter 25: When to Try XP
Chapter 26: XP at Work
Chapter 27: Conclusion
Index

L'auteur - Kent Beck

Kent Beck is the founder and director of the Three Rivers Institute (TRI). TRI provides a harmonious environment for individuals from many disciplines to gather and investigate the principles underlying emergent software development and techniques for leveraging these principles. Mr. Beck has pioneered patterns for software development, the xUnit family of testing frameworks, the HotDraw drawing editor framework, CRC cards, refactoring, and most recently Extreme Programming. He is the author or co-author of Extreme Programming Explained (Addison-Wesley, 2000), Planning Extreme Programming (Addison-Wesley, 2000), and The Smalltalk Best Practice Patterns (Prentice Hall, 1996). He lives on 20 acres in rural southern Oregon with his wife, five children, four dogs, two sheep, and a variable number of domestic fowl. He received his undergraduate degree from the University of Oregon.

Autres livres de Kent Beck

Caractéristiques techniques

  PAPIER
Éditeur(s) Addison Wesley
Auteur(s) Kent Beck
Parution 10/09/1999
Nb. de pages 190
Format 18,7 x 23,5
Poids 352g
EAN13 9780201616415
ISBN13 978-0-201-61641-5

Avantages Eyrolles.com

Livraison à partir de 0,01 en France métropolitaine
Paiement en ligne SÉCURISÉ
Livraison dans le monde
Retour sous 15 jours
+ d'un million et demi de livres disponibles
satisfait ou remboursé
Satisfait ou remboursé
Paiement sécurisé
modes de paiement
Paiement à l'expédition
partout dans le monde
Livraison partout dans le monde
Service clients sav@commande.eyrolles.com
librairie française
Librairie française depuis 1925
Recevez nos newsletters
Vous serez régulièrement informé(e) de toutes nos actualités.
Inscription