XP原则和实践-Planning-releaseplan.ppt

软件工程基础 敏捷开发 刘 驰 Outline Traditional life cycle vs. XP XP motto: “embrace change” How does this attitude compare with that implicit with traditional waterfall software life cycle? XP values XP practices Pair programming An XP development road map Extreme Programming (XP) Developed by Kent Beck “a light-weight methodology for small to medium-sized teams developing software in the face of vague or rapidly changing requirements.” Alternative to “heavy-weight” software development models (which tend to avoid change and customers) Extreme Programming turns the conventional software process sideways. Rather than planning, analyzing, and designing for the far-flung future, XP programmers do all of these activities a little at a time throughout development.”-- IEEE Computer , October 1999 Successes in Industry Chrysler Comprehensive Compensation system After finding significant, initial development problems, Beck and Jeffries restarted this development using XP principles The payroll system pays some 10,000 monthly-paid employees and has 2,000 classes and 30,000 methods, went into production almost on schedule, and is still operational today (Anderson 1998) Ford Motor Company VCAPS system Spent four unsuccessful years trying to build the Vehicle Cost and Profit System using traditional waterfall methodology XP developers successfully implemented that system in less than a year using Extreme Programming (Beck 2000). Embrace change In traditional software life cycle models, the cost of changing a program rises exponentially over time Why would it cost more to make large changes during testing than during requirements specification? A key assumption of XP is that the cost of changing a program can be hold mostly constant over time Hence XP is a lightweight (agile) process: Instead of lots of documentation nailing down what customer wants up front, XP emphasizes plenty of feedback Embrace change: iterate often, design and redesign, code and test frequently, keep th