A Glossary of ExtremeProgramming Terms & Acronyms
Please keep entries in alphabetical order. Please keep discussion on the linked-to pages.
- a test written by the customer, (or QC on the customer's behalf) that tests the entire system to ensure that a specific piece of functionality is present and functions correctly.
- acronym for Acceptance Test
- "BigDesignUpFront"; part of WaterFall.
- Big, Up-Front Design. Variation on BDUF.
- (The literature is thin on this one) The primary stakeholder (on-site, in-the-lab) of the system undergoing the XP methodology. Provides the final acceptance criteria for any behavior in the system. Sometimes a team instead of one person. Less optimally, but often likely, this is a Business Analyst who, while they may be a Domain Expert, does not have the final say, but acts as the advocate of the real Customer who is not on-site. (Beware the Customer who knows the Business but does not have the Final Say).
- acronym for DesignByContract.
- "DoTheSimplestThingThatCouldPossiblyWork" A general XP heuristic on how complicated a design should be.
- "Don'tRepeatYourself" From ThePragmaticProgrammer, a more general version of OAOO.
- UserStory gets broken down into these smaller fragments by the developers.
- ErichGamma, RichardHelm, RalphJohnson, and JohnVlissides. Authors of the classic book "Design Patterns". See DesignPatternsBook.
- Abbreviation for "Gang of Four".
- What JavaUnit displays when all UnitTests run successfully. The bar is green, the code is clean.
- Green Book
- PlanningExtremeProgramming by KentBeck and MartinFowler.
- "OnceAndOnlyOnce" The state of a well designed program -- it says everything that currently needs to be said precisely once. Compare with DRY.
- acronym for PlanningExtremeProgramming (the green book).
- Pink Book
- ExtremeProgrammingInstalled by RonJeffries, AnnAnderson, and ChetHendrickson.
- acronym for PairProgramming.
- acronym for RationalUnifiedProcess.
- a quick (typically minutes or hours) exploration by coding of an area the development team lacks confidence in. The spike is concluded when you learn what you needed to learn. So-called because a spike is "end to end, but very thin", like driving a spike all the way through a log. See SpikeSolution, ArchitecturalSpike, SpikeDescribed.
- When you can't even go pee unless you have a GreenBar.
- "TestEverythingThatCouldPossiblyBreak" I haven't seen the acronym in common usage. Reference?
- a test that tests a single class, or a small cluster of classes in isolation.
- Broad description of a feature, created by the customer, estimated by developers, fits on a note card.
- acronym for UnitTest.
- White Book
- ExtremeProgrammingExplained by KentBeck.
- ExtremeProgrammingExplained by KentBeck (the white book).
- Communication, Simplicity, Feedback, and Courage.
- "YouArentGonnaNeedIt", said by XP coaches when developers get into overly baroque design territory.
Please keep entries in alphabetical ord er. Please keep discussion on the linked to pages.
EditText of this page (last edited March 29, 2005)
FindPage by browsing or searching
This page mirrored in ExtremeProgrammingRoadmap as of April 29, 2006