How to write Java project?

We usually say that the Java project are also JavaWeb, J2ee project; now that is JavaWeb.

　　The easiest way to look at other people in the project source code modification on the basis of someone else, and now you want to break apart a little bit and see.

　　1. project:

　　to do something, the last requirement is what do the breadth and depth that determine the boundaries and scope of the project

　　2. Technical feasibility:

　　What technical reserves needed to prepare what learning

　　3. Function:

　　System specific to achieve what features make the system use case describes

　　4. database design:

　　ER drawing out

　　4. system design:

　　three-tier model doing or what mode, which requires the construction,

　　5. self-test or tests to other people:

　　project whether there is a bug, and so on.

　　The project scenario is correct. (Best not to test yourself, other people need to own ------ programmers do not think they are wrong)

　　6. Fees are usually built himself a tomcat or iis server, and then back up as learning materials for subsequent late update or reference memories used.

　　7. Summary project

　　in the process learned anything, subsequent updates need to pay attention to what and where the inadequacies of the project is to develop any problems, solutions, software lifecycle for understanding the development prospects of the project and the project market survival period and so on.

　　Writing project or write a program to pay attention to a small detail, it is a commentary this thing is not just to see for himself but for others to see (later to yourself or a colleague), how to write comments should know, but we must Note there to write.

　　It is recommended when adding a comment

　　1. classes, interfaces, etc. must have created time, creator, version number, description and other comments.

　　2. Comments are not possible, such as: get / set methods do not need to write comments. Each line but do not need to write notes.

　　3. Notes the need to write a concise and easy to understand. In particular the method parameters and return values.

　　4. each modification, the corresponding comment should be synchronized.

　　5. In the class, interface, method, use should / ** * / javadoc comment. Because it does not require the caller to enter the internal method to know the usefulness of the method. Improve coding efficiency.

　　6. The method of code if the order of minutes, preferably also add code number, such as 1, 2, and so on.

　　7. Each enumeration value needs to add a comment.

　　Summary

　　written comments is a good habit to make themselves and the team will benefit, if you took a little bit of comment is not a project, then got in trouble on a programmer (N-word is omitted here), I wonder if you have not read through the source code open source projects, and that written comments in considerable detail, we can refer to a lot, we do not fight for a "bad" programmer.