1. Project document links
2. Technical references
- Front-end: html, css (Ali icon library reference section), JS (jQuery) (frameless)
- Front and rear ends data exchange: ajax
- Backend: servlet
3. individual work
3.1 The final project is not reflected in part:
- Learning before and after the end of the technology (see Mu class, rookie tutorial to learn, practice native code)
- Find the right template and try to modify
- To the project design and realization player playback
3.2 The final project reflects part:
- The initial integration of front and rear ends of the formwork
- Search page front and rear side code (implement fuzzy query according to song title, artist, album, song list)
- Search History feature front and rear side code (search history can be recorded and reflected in the search page, delete)
- Modify found page image carousel feature
- Favorite song to increase user fields (to display the user's favorite song achieved after login)
- Front and rear ends of the landing registration function codes (for detecting the same name, the password is the format control)
- Front and rear side code page of personal information
- Front and rear ends of the modified code of personal information (birth date have limitations)
- Front and rear ends of the code Change password
- Modify the database design
- Page logic of perfect
4. problems encountered
Preliminary prototype design is not complete, only the main interface, which later led to the design of each functional interface needs to have to be adjusted according to the prototype can not determine a page directly; coding is a big problem, the front and rear end, tomcat, database coding best to start unification, or the latter may garbled, data before and after the end of the data transfer interaction may be garbled; there is the technology chosen our group was too late, on the one hand lead to some earlier learning technology is useless, but not useful science, on the other hand cause behind schedule will be very hurry; too few teams face to face communication, face to face communication can make the problem appear more clearly, but also to set Trimaran to quickly solve a problem; the group is not clear division of labor, the weight is not balanced workload.
5. personal summary
Before absolutely no contact with web development projects, the front and rear end is completely different from the previous method ecipse with swing and hibernate database design project courses, and front and rear side technology was good, so much the early learning costs; time-consuming to solve a lot of small bug effort, because they do not know the reason, there is no search or similar, or a bunch of similar, but not applicable, but spend a lot of time to resolve after a great sense of accomplishment; this team so that we complete the project experienced a close to real development process, let us escape textbook knowledge, to understand reality, but also class the teacher talked about a lot of experience in the real world happened programmers body, our future will definitely help.
6. Recommends
1. grouping should not be used freely team, but should focus on more factors (such as: the students learned related technology leader can do to take the lead, it's best to team members come from different classes different bedroom can force them to take the initiative AC)
2. can the time the project team in advance, reducing the proportion of performance (workload is relatively difficult to define, because some groups are some people write, some people write front-end back-end, while other groups are responsible for one module per person not only have to write to write front-end back-end function code should also be considered a data connection, Grading is subjective bias, different raters assessment standards are different), and personal items (a simplified version of the project team) as the last big operation (workload can be directly assessed, but also had a team project experience, the process will be accelerated).