Developing Java Web platform-type Project Spit slot __java

developing Java Web Platform-type project vomit slot

     

I am a graduate student of 985 University, after studying, have little time to do scientific research writing thesis. Most of the time is spent on projects developed by mentor.

Originally I also enjoy this, because learn computer. Should pay attention to hands-on ability, do some work is understandable. Most of the previous contacts were. NET project,

Projects that rarely participate in the Java Web orientation. Since last year took over the current project, only then realized what is the real software PRODUCT. What is user demand? Specification

The importance of coding. After the process of the apes do not repeat my mistakes, tread I have trodden the pit.

Next, I have encountered problems in the development of the summary.

1. Before taking over the project, we must first understand the level of their technical strength, assess the overall difficulty of the project, to achieve targeted. Can develop some less difficult project first practice practicing, and then connect large-scale complex project development, accumulate and hone technical strength. I lead the project difficult to estimate the difficulty, the user requirements are too high, the program Ape Edge learning side of development, inefficient, resulting in serious project delays, caused by party a dissatisfaction.

2. Need to do a good job analysis, eager to start, will let you lose the candle, go more detours. Here is a hint: Software engineering This book is how important AH. It turned out to be really ignoring it.

3. The user needs to have a general judgement, the refusal of "unreasonable" demand. Although most of the time, the user may not be very clear about the needs. He needs the program ape to show example demo, and then decide whether to follow this style development. If necessary, it is best to allow users to sign the requirements specification, in case of change, so that the program ape annoying annoying. I do this project, party a led the initial proposed a page style, feeling dissatisfied, changed 5 times, made 5 demo, and finally changed back to the first edition. Let the program ape Laugh and cry.

4. "It is said that the best way to make a program ape go mad is to change it two times." That's a really good thing. The development project, should maintain the good patience, has the good understanding to the user changes the demand. To realize that it is not normal to change, there are problems to be exposed as soon as possible, the accumulation of more, finally can not get.

5. The team should have a clear division of labor, a strict project schedule. Strictly follow the development schedule.

6. For the need to butt the third party system, to leave a good interface in advance, so as not to be difficult to add interface in the project later.

7. Project code writing to standardize, strict sub-module development, in order to prevent late code too difficult to manage, documents, sub-directory is very necessary.

8. Algorithm Foundation and Mathematics Foundation Forever is the procedure Ape's sword, must study well. Of course, English is also very important.

9. Sometimes social relationships are more important than writing code, and how to make users aware of the impact of changes in requirements on the progress of the project. How to get users to adjust the online program. All of these require good communication.

10. Finally, the importance of accumulation. Whether it is technical accumulation, or other disciplines of knowledge accumulation is extremely important. Look at other excellent product design instructions for less detours.

        above is my little basic experience on project management, Welcome to the Great God Spit groove.