• Like
  • Save
Xp exterme-programming-model
Upcoming SlideShare
Loading in...5
×
 

Xp exterme-programming-model

on

  • 848 views

 

Statistics

Views

Total Views
848
Views on SlideShare
848
Embed Views
0

Actions

Likes
0
Downloads
12
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Xp exterme-programming-model Xp exterme-programming-model Presentation Transcript

    • XP ( EXTREME ProgrammingModel )by : Ali masudianPourSoftware Engineer Lab
    • What is XP Model ?• Extreme Programming (XP) is a software developmentmethodology which is intended to improve software qualityand responsiveness to changing customer requirements.
    • Goals• Extreme Programming Explained describes ExtremeProgramming as a software development discipline thatorganizes people to produce higher quality software moreproductively.
    • Activity• XP describes 5 basic activities that are performed within thesoftware development process:• Planning• Managing• Designing• Coding• Testing• Each of those activities is important.
    • Planning• User stories are written.• Release planning creates the release schedule.• Make frequent small releases.• The project is divided into repeated levels .• repeated levels planning starts on each repeated level.
    • Managing• Give the team a dedicated open work space.• Set a untrack time for pace .• A stand up meeting starts each day.• The Project Velocity is measured.• Move people around.• Fix XP when it breaks.
    • Designing• Make it simple.• Choose a system metaphor.• Use CRC cards for design sessions.• Create spike solutions to reduce risk.abshar• No functionality is added early.• Refactor whenever and wherever possible.
    • Coding• The customer is always available.• Code must be written to agreed standards.• Code the unit test first.• All production code is pair programmed.(2 person)• Set up a dedicated integration computer.• Use collective codes.
    • Testing• All code must have unit tests.• All code must pass all unit tests before it can be released.• When a bug is found tests are created.
    • END!• Best regards;• Ali MasudianPour• References:• http://extremeprogramming.org• http://wikipedia.com