Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
. XP khuyến khích bạn ném đi UML sơ đồ một khi bạn đã viết mã của bạn. Với những công cụ này, bạn có thể tạo ra chính xác, hiện tại UML bất kỳ thời điểm nào là cần thiết. 2.5.3.2 bảng trắng và giấy nháp Bạn không cần ưa thích, các công cụ đắt tiền UML sơ đồ. | If you really want up-to-date UML diagrams consider tools like JBuilder Enterprise Studio Together Control Center or Rational XDE. These types of tools can reverse-engineer your code and produce UML diagrams. These tools ensure that the diagrams stay in sync with your code. XP encourages you to throw away UML diagrams once you have written your code. With these tools you can generate correct current UML any time it is needed. 2.5.3.2 Whiteboards and scratch paper You don t need fancy expensive UML diagramming tools. A stack of index cards a whiteboard or even a scrap of paper can serve as a surprisingly effective design tool. Here is the process 1. Draw a diagram. 2. Write a unit test. 3. Write some code. 4. Repeat steps 2-3 until the feature is complete. 5. Throw away the diagram. This may seem silly but think back to the last project you worked on where a lot of diagrams were created. When you encountered a bug in the application did you generally turn to diagrams first or look at the code XP assumes that most programmers rely on the code because diagrams do not present enough detail and manually updated diagrams are almost always out of date with respect to the actual code. Throwing away diagrams does not imply that you throw away the design. The design itself is embodied in the working code and can only be thrown away if the code is erased. 2.6 Builds A good build environment is essential to XP teams. Constant refactoring collective code ownership and ever-changing pair programming teams require that each developer have the ability to reliably build the software using an identical configuration. If this is not the case then tests that pass for one developer may fail for everyone else. 2.6.1 Continuous Integration Continuous integration means that XP teams build the software application frequently often several times per day. In fact the Cruise Control tool mentioned in Chapter 1 performs a complete build of the application after every check-in to version .
