Extreme programming introduction

Extreme Program 08001211 Xu Yuan 2004-12-25 Extreme Programming (XP) Extreme Programming (XP) Full-name Extreme Programming, a lightweight, flexible method. XP is a way to develop software as a software that meets changes in customers. Its success has benefited from its special emphasis on customer satisfaction. XP makes developers to respond more efficient to customer demand changes. In the later stage of the software life cycle.

Extreme programming introduction is a software development method that has experienced many practical tests. It has been successful in many large companies such as: Bayeris Che Landesbank, Credit Swis S Life, DaiMlerchrysler, First Union National Bank, Ford Motor Company and Ubs .

Extreme Programming Development 1990s, Kent Beck and Ward Cunningham together had experienced an approach to software development that made every thing seem simple and more efficient. March, 1996, Kent started a project at DaimlerChrysler using new concepts in software development. The result was the Extreme Programming (XP) methodology. What Kent came to realize is that there are four dimensions along which one can improve any software project, which are Communication, Simplicity, Feedback, and Courage. These are the four values ​​sought out by XP programmers.XP of Twelve practical methods XP 12 practice method development plan (SMALL RELESES) Metaphor (Testing) Reconstruction (PAIR Programming) Collective Ownership (40-Hour Week continuous integration (40-seat customer) XP's 12 practice MethodChlica-SMALL Releases Iterative version of the customer's release system determines which functional units have important impact on the user service and can introduce the important feature of the system early to the user, and the "Getting" system obtained by the development team. The shorter it. Pair programming All published code is done by two programmers to develop together on one machine. The best way to program the program is that the two are sitting in front of the display, slide the keyboard and the mouse "slide", one considers the method created (Method), and the other person considers how this method is obtained in the class. Better reflection. Adapting to the programming requirement, you must spend the embarrassment of the beginning

The benefits of the pair [Node] usually indicate that two developers share a computer, a monitors, a keyboard and a mouse (I found two monitors, two keyboards, and two mouse more interesting, but one Set of facilities can also be well done). You and your partner sit in front of the keyboard. A man driving ("driver"), another person navigates ("navigator" or "partner"). If the driver is stagnant or settled or lost, the navigator and the driver can interchange the role. In fact, this role interchange should occur frequently, sometimes it may be interchanged every few minutes (even more frequent). Once you are used to this approach, and adapt to the specific person with you, you will enter this process and naturally come back to the play. Collective Ownership "Collective Ownership" encourages everyone to make new ideas for all parts of the project, any developers can change any code to increase the function, modifying errors, no one will become changed bottleneck collective code ownership Personal pride -> The team is proud to prevent "punishment is not responsible", but it is necessary to prevent "everyone is responsible" to become "no one has" formulation plan (Planning Game) to develop a copy of Release Planning Meeting The release plan release plan detailed in detail the various versions required by the user, this is very simple for the back iteration plan, and provides very good information and excellent manipulation control; there is no 90% in XP Complete: A characteristic story is either completed, or no complete.

Metaphor (Metaphor) Select a Metaphor to make a unified naming for the development team. Named way is easy to understand. Simple Design Negues No increase the function of not included in progress " "In fact, it is not simple Test (Testing) Code The Unit Test First First First First First First First First First First First First First First First First First First First First First First First First First First First First First First Test Forms Creating Unit Tests can help developers clearly realize what truly needs is made by test activities.

Refactoring can re-consider the designs, simple, simple, simple enough to understand, modify and expand all things, simply understand, modify and expand all things, only expressing a good system, a good system. In the later stage, I can't catch the progress request

Continuous Integration Developers should constantly integrate code into the code base. One hour, no more than 1 day everyone needs to operate on the final version to continue to integrate or discover some compatibility problems in early times. "What is the money now pay more?" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" Directors directly participated in the development group to "hung", and cultivate customers as an expert by newbie, the development group needs expert