xp极限模型 (Extreme programming).docVIP

Extreme programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development,[1][2][3] it advocates frequent releases in short development cycles, which is intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted. Other elements of extreme programming include: programming in pairs or doing extensive code review, unit testing of all code, avoiding programming of features until they are actually needed, a flat management structure, simplicity and clarity in code, expecting changes in the customers requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers.[2][3][4] The methodology takes its name from the idea that the beneficial elements of traditional software engineering practices are taken to extreme levels. As an example, Code reviews are considered a beneficial practice; taken to the extreme, code can be reviewed continuously, i.e. the practice of Pair programming. Critics have noted several potential drawbacks,[5] including problems with unstable requirements, no documented compromises of user conflicts, and a lack of an overall design specification or document. Contents 聽[hide]聽 1 History 1.1 Origins 1.2 Current state 2 Concept 2.1 Goals 2.2 Activities 2.2.1 Coding 2.2.2 Testing 2.2.3 Listening 2.2.4 Designing 2.3 Values 2.3.1 Communication 2.3.2 Simplicity 2.3.3 Feedback 2.3.4 Courage 2.3.5 Respect 2.4 Rules 2.5 Principles 2.5.1 Feedback 2.5.2 Assuming simplicity 2.5.3 Embracing change 3 Practices 3.1 Fine-scale feedback 3.2 Continuous process 3.3 Shared understanding 3.4 Programmer welfare 3.5 Coding 3.6 Testing 4 Controversial aspects 4.1 Scalability 4.2 Severability and responses 5 Criticism 6 See also 7 References 8 Further reading 9 External links History[edit] Extreme Programming was created by Kent