Xp Slideshow

Extreme ProgrammingExtreme ProgrammingImproving software engineering !Improving software engineering !

Extreme ProgrammingExtreme Programming

Hello! My Name is Gilbert :DAny one have an idea

what is XP?


•Software development methodology.•Focuses on “ The simplest thing that could possibly work” ! • was created by Kent Beck while he was working on the Chrysler Comprehensive Compensation System (C3) Payroll.

WHAT IS XPWHAT IS XP ??


OtherOtherXPXPRequirements

Gathering (done once at start)

Continuous: Planning Game (every Iteration), Release Planning

Once it approved by the customer and start working it never changes !!!

Changeable during iterations

doesn’t prescribe any engineering practices

XP does !

IS A SET OF GOOD SOFTWARE ENGINEERING PRACTICES!

PlanningRefactoringSimple DesignSmall ReleaseTestingPair ProgrammingCollective OwnershipContinues integrationOn-site CustomerCoding Standards

Practices:Practices:


Planning:Planning:Planning is critical; without it, software projects can quickly fall apart Release programming

iteration Planning

Simple Design:Simple Design:Developers uses the simplest Designs .. WHY?

the reason for this is that the system requirements changed dramatically!


Pair Programming:Pair Programming: Is a Software developer technique 2 programmer work in one station and produced the same code All significant development is done in pairs Process is FASTER !!

Coding Standards:Coding Standards: Rules should be used to write the system The entire team should agree on using these standards The software would be as a single developer wrote the code in one session


Small release:Small release:development team launched the system quickly to the market with the essential requirements (minimum requirements), and then they it is updated on a regular basis

Testing:Testing:The developers here writes test plan for the system before

starting in programming phase making it easier for the application of the required tests

this feature makes XP different than others• Unit Testing

• Acceptance Tests


1.1.Simplicity Simplicity 2.2.CommunicationCommunication3.3.RespectRespect4.4.FeedbackFeedback

XP VALUES:XP VALUES:

1.1.Simplicity:Simplicity:doing what is exactly needed, extra functions can be added later. simplicity value causes some problems because when the client request changes, this frequently leads to radical changes in what has already been implemented ..


2.Communication2.Communication::since threes no documentation in XP, since threes no documentation in XP, communication is a core value. Every member in the communication is a core value. Every member in the team works together in every step team works together in every step and meets frequently.and meets frequently.


3.Respect:3.Respect:Team members respect each other,Team members respect each other, the clients ,and their work by always lookingthe clients ,and their work by always looking for high quality and seeking for the best for high quality and seeking for the best design for the solution.design for the solution.

4.feedback:4.feedback:Ensure rapid progress, rapid development,Ensure rapid progress, rapid development, teamteam confidence, and discover bugs early.confidence, and discover bugs early. XP includes three types of feedbackXP includes three types of feedback


Distinguish between decisions made by business stakeholders and developers.

Keep design as simple as possible. Write automated test code before writing

production code and keep all tests running. Pair programming The code can be changed by anyone.

FundamentalsFundamentals

XP have several potential drawbacks including:

Problems with unstable requirements. Working in pair is slow. Lack of documentation that addressed by

agile modeling. Simple design may have faults and

omissions.

DRAW BACKSDRAW BACKS

We Hope you We Hope you enjoyedenjoyedYour time !Your time !

DONE BYDONE BY::

Ghadah Al-RabeeahHessah Al-RashedNouf Al-MobarakNoura Al-HamidRawan BaBaierReem Al-FayezSadeem Al-SudaisShahad Al-Harbi

Technology

Xp Slideshow