1 / 6

Extreme Programming

Extreme Programming. CS 490T Advanced Tablet Platform Applications. What is XP Programming?. It is a practical methodology for software development. It gives a list of rules that have been proven successful in software development.

ariana-dyer
Download Presentation

Extreme Programming

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Extreme Programming CS 490T Advanced Tablet Platform Applications

  2. What is XP Programming? • It is a practical methodology for software development. • It gives a list of rules that have been proven successful in software development. • Instead of emphasizing an straight “design- and-program” approach, it encourages an iterative approach.

  3. When to use XP Programming? • It is for projects that have some risk of completion • Design changes continuously. • Customer does not have a clear idea of what has to be accomplished. • Used for small groups (2-12 people) • Requires good communication between customers and programmers.

  4. Planning User Stories Release Planning Frequent Small Releases Measure Project Development Iterative Development Move People Around Daily Standup Meeting Fix XP when it breaks Coding Have customer available Follow coding standards Code unit-test first Use pair programming One code integration at a time Integrate often Collective ownership Leave optimization until the end. No overtime Rules and Practices of XP

  5. Designing Keep it Simple Choose System Metaphore Use CRC cards Create “Spike Solutions” Do not add functionality early Refactor Testing All code must have uni tests All code must pass all uni tests before integration When a bug is found create a test. Create acceptance tests Rules and Practices in XP (cont.)

  6. Bibliography • “Extreme Programming: A gentle introduction”; http://www.extremeprogramming.org/

More Related