I saw the programmer a few days ago, and there is still a way to see the Rational Uniform Process, just trying to be a small project, I feel that this opportunity to experience the test driver and iteration. I just wrote the first driver and iterative documentation, I feel very good. The project is divided into four large modules. The first iterative version is used to solve communication between the mobile phone module and the server module in the project. I am using Eclipse, open in a Workbench (new, but the word comparative image) has four projects. In fact, it turned out that it was built in a bag, but later found that the JDK would take part because of the project. Test drive is a very good idea. Feel this case, combine a method or class's demand instruction to test, so you don't need to test it, you will understand the demand, but use tests to use tests when you start. Code is description that may have ambiguous description. Of course, I feel that this test is only very effective in a certain field, such as for the interface, I feel that this test driver can't play too much. Iterative development is the inevitable result of this test driver, but this development model requires designers to have a considerable understanding of the entire project, and at this time, the individual feels important to the project's grasp of the project. Of course, natural this iterative development can minimize demand or technical risk, which should be something that the Earth people know.
