CSC/ECE 517 Fall 2012/ch2a 2w8 vp

From Expertiza_Wiki
Revision as of 20:44, 20 October 2012 by Ssinha3 (talk | contribs) (Created page with "=Extreme programming (XP)= This chapter focuses on explaining below points. Describe what extreme programming is. Concepts of XP. Four values in XP. Aspects in key practices s...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Extreme programming (XP)

This chapter focuses on explaining below points. Describe what extreme programming is. Concepts of XP. Four values in XP. Aspects in key practices such as pair programming, collective code ownership, stories, automated testing, small releases and continuous integration. Advantages and Disadvantages with XP. Comparison with waterfall model

What is extreme programming

Extreme Programming (XP) is a software development methodology created by Kent Beck during his work on the Chrysler Comprehensive Compensation System (C3) payroll project. Extreme Programming is intended to improve software quality and responsiveness to changing customer requirements. It is a one of the several types of agile software development processes. Extreme Programming is successful because it stresses customer satisfaction. Instead of delivering everything you could possibly want on some date far in the future this process delivers the software you need as you need it. Extreme Programming empowers developers to confidently respond to changing customer requirements, even late in the life cycle. Back to top

Concepts of XP

Goals

Back to top

Four values in XP

Back to top

Aspects in key practices

Back to top

Advantages of XP

Back to top

Disadvantages of XP

Back to top

Comparison with waterfall model

Back to top

Research Conclusion

Back to top

References

<references>

</references>