Yin Yue app- personal summary
introduction
github link: https://github.com/hideonbushhhhhhh/MusicAppSys
Requirements Document Link: https://www.showdoc.cc/hangzhouwh?page_id=3482265840936782
Blade prototype link: https://free.modao.cc/app/9d6afab630db73f204b02ff29474043a4e8a76d4
OtoEtsu app prototype: Https://Www.Cnblogs.Com/zucc31701087/p/11973760.Html
Yin Yue app project design: https://www.cnblogs.com/zucc31701087/p/11885443.html
Yin Yue app needs analysis: https://www.cnblogs.com/zucc31701087/p/11785844.html
First, the individual division
In this time of the project, the task I started was responsible for establishing the database work-related aspects of the database and draw ER diagrams, and later my main task was to prepare the backend API, and then and write the front end buddy buddy and is responsible for transfer solutions emerge the bug. By the way encountered a problem when the database change it, change some small problems.
Our group consists of four individuals. Group submitted a total of 75 amendment, which I had submitted a total of 28 times, adding more than 8,000 lines of code, compared with others may be a little too little, but the realization of functions gave true. I feel the back end of the work, starting from 0 bit difficult, but the writing will be more handy, wrote later feel no API is not written out, and significantly improved backend api proficiency.
Second, the individual project summary
1. The review process of the project, experience and effort when most is the standard project must be finalized as soon as possible, the database must be unified, at the earliest only when all the criteria are finalized, in order to save after work open to complete the follow-up work.
2. I was first built database, I also draw the ER diagram. But because of my ill-considered, and communicate within the group was not impressive enough, the problem has been to write database crawler students need to be stored into the database when it found problems, and major changes in a database at that time, after work or on there is a certain amount of influence.
3. Write on the back end, I would have to use Springboot comes with a generic Result class to pass parameters, but then I found this tested delivery methods to resolve them extremely troublesome, not only I accept such data deal with a lot of trouble, the front of the students to get processed after my return data it is also very troublesome, so early in our project, the process of docking the front end and back-end work appears in the work of a lot of problems, and therefore the progress of the project has been delayed a lot. So then my other companions in the group and, after discussions, decided to use JSONObject class of Alibaba FastJson to pass parameters so that the back end of my job smooth a lot, so sometimes encountered problems should be changed immediately, otherwise, the Result class has been used to write, I guess I have to step on a lot of the pit.
Things written in the course of some relatively cut to the heart of the back-end is 4: Database sometimes become; because of changes in demand for front-end, I want to change some of the back-end API. First, change the database will lead to my backend there are a lot of things have to change, database mapping file (Mybatis) to be changed, some of the functions to be changed, sql statement as well as some want to change, a lot of times a little pull a launch body feeling, so I think some standards still have to settle down as soon as possible, some basic things still can not want and change it in. Then change on the front end needs, this thing is to be divided into two types, some are very simple, just give a little more of what sql statement can be processed; but some changes are really very troublesome, I remember an API I had half an hour to finish, but later changes to the API took two hours. . . So I really think that a unified standard is still very important, be sure to set a good standard front-end, back-end API to write again, because the latter API to write really very fast.
Discussion, everyone's together 5. Overall, this project we are four people in a group together to complete, after the problems together and solve problems, are very rare experience. Middle had a quarrel, but we are still so go step by step down eventually because of the time failed to get web client finished to do it, but ios and Android end of the function, we have achieved and debugging Well, basically there is no large bug, so this time the feeling of soft labor job task for us is still up to par it.
Third, the recommended course
1. With regard to curriculum advice, to tell the truth because to rush project, so I basically listened to half the class, and then the remaining half of the time used to write the project, so I could not understand the depth of the content on the class, because our group there is one person responsible for writing the document, the rest of us are basically just with the completion of the document, so for example, I understand nothing of UML diagrams, but the group is still able to work to pay up, so it is recommended at least every lesson entitled to put forward a small test, subject to what may be a teaching assistant, do question the doctorz also convenient, single-handedly can count usually small test points (I was a demon).
2. With regard to hold a group meeting on a regular basis, I think it is not necessary, because the problem does not appear fixed at a certain time, but as you continue to promote the progress of the project gradually being discovered. To say our group, we have been created a micro-channel group chat, so what's the problem will soon ask directly, out of a problem, you need to how to operate, we will exchange the group, and then set the direction of the settlement. Because of the division of labor relations team, our group as well as a coordinated, global co-ordination of people, so we deal with the problem very quickly. Regular group meetings for us, in fact, the original question again the way, there is no new content, because in the group said, and because we are a group of three members of the same laboratory, so the exchange is particularly convenient, who is out of the question directly call him on it, so regular team meetings for it is our burden and feel futile. Because the project is to be completed will eventually, so I think mid-term examination and post-examination enough, and the document also turned over a lot, so I feel a little bit better when the group will solve the problem directly rather than wait out only a discussion group meeting on the results.
3. In response to the last question, I think we can find each class (not necessarily every lesson can be odd and even weeks) set up a ready ppt, set in a personal talk about the progress of the team, talk about the future prospects and direction , show you their results, then you can add good points and bad of what can be found in the Panel earlier, if the class how teams can sign what's too, too late what it held.