I. Project Overview
1.1 Background
Music is an art, is organized by the tone people to express emotion, art reflects real life human emotions. Development of modern technology makes it possible to enjoy music anytime, anywhere using the Internet, but very few in today's Internet to a social platform as a medium of music. This team wanted to form "music + social", the development of a set of songs, dating and discussion as one of the online community - "Violet" music community. Violet multi-finger violet, can be described as shy people, this team aims to enhance this platform for people to exchange music, while narrowing the distance between people.
1.2 Technology Roadmap
Project as a whole with B / S architecture, and front and rear end of the separation technique.
Front-end Vue.js + ElementUI + axios
Flask + MySQL backend
1.3 achievement
User, single song song, circle post, thumbs, comments and other modules are basically achieved, there is a small part of the functionality redundant, duplicate effort, because time is limited, it will not be fully achieved our design. But most of all functional overall design has been achieved, the core functions, the main business to run. To achieve the basic goal of our project.
1.4 Project Documentation
- Violet music community needs analysis statement: https://www.cnblogs.com/Keadin/p/11791088.html
- Violet music community design documents: http://www.cnblogs.com/Keadin/p/11885656.html
- Violet music community API interface documentation: https://www.showdoc.cc/589304476235742
- Violet music community interface prototype Manual: https://www.cnblogs.com/Keadin/p/11974412.html
1.5 Project Source
- Violet music community front-end Source: https://github.com/KeadinZhou/se-violet-web
- Violet music community back-end Source: https://github.com/shysimon/violet
1.6 Project Outputs
- Violet music community interface prototype Demo: http://kealine.top/SE/demo/
- Violet music community complete version: http://kealine.top/violet/
Second, the personal work summary
2.1 Preliminary work
In the beginning of the project, I data structure and database design by PowerDesigner.
2.2 medium-term work
We completed the back-end write songs song unilateral, and the design of a single song song lazy import scheme (to ensure the rapid and breadth of local song music library in a single operation).
2.3 Late Work
Modular and improve overall back-end code (overall responsibility for the back-end). And front-end classmates improved backend API interface, backend bug fixes.
Third, the project summary
Before writing this project in my mind for how to provide the back-end to front-end services, has been conceived has two, one is to break up the data, a data request, the other is the data package, a request, the front end returns in its entirety. After this time, the practice of project, I know clearly the latter better, simplifies the front-end code, but also reduce the number of front and rear end of the transmission of data.
But not enough, I would imagine that a single query song, the song returns a single query song, the song returns. In fact after the start of work, in charge of the front of the students told me, id query by a single song, the best songs need to be under a single song information, song and single of all returns, thus reducing the workload of the front lot.
Because we are the first time to write such a project, before the actual hands-on, there are many difficulties useless foresee a meeting with the summary before the backend interface to achieve, after the start of work find better solutions, and then summed up together this itself is a learning process.
After this practice a project, I have a project for the development of a deeper understanding of the project development front and rear ends of the corresponding development time it takes a certain concept, also works the front end of a certain understanding, know how to integrate the data to reduce the front-end workload. By this time the team six teams collaborate with team members constantly running, but also exercise my teamwork skills.
Fourth, curriculum recommendations
From the beginning of the course "Building of the law" and "Mythical Man-Month" entry-level software engineering actually looking for improvement is limited, but read some of the knowledge, methods really stay in my mind, when I run into a wall programming, detours, a lot of duplication of time, naturally began to reflect, correct his own mistakes behavior, and ultimately enhance the level of software engineering in practice.Teachers and teaching assistants gave us great help throughout the course of the project, at times gave us constructive proposals in the class, regular meeting, let us take a lot less detours.
I recommend the course, usually can have some small tests, it is best not divided, that is the final exam of the training, after all, she went to get high scores, final exam can not fall, there is a lower proportion of the final exam.