Community management system - personal summary
First, the source code for the link
Front-end code: https: //github.com/hzhq1255/clubsystem
Back-end code: https: //github.com/dozoroy/-
Second, the document links
Demand link: https://www.cnblogs.com/31701085yc/p/11778257.html
uml design link: https://www.cnblogs.com/31701085yc/p/11885464.html
Prototype Link: https://www.cnblogs.com/zucc31701081/p/11970157.html
Third, the personal division of labor
1. Demand collaboratively design stage crew
2.uml design stage, drawing timing diagram
Write 3.web interactive front-end registration, financial management, information management and back-end of the page
4. Compose section of the document
Fourth, the project summary
1. Technical Summary
The project we chose to develop the web end, and take before and after the end of the separation strategy. The main use of a variety of powerful front-end components Vue.js framework of binding elementui; backend spring boot framework, entity classes and types of interfaces written in the Java language, database using mysql, in order to simplify the operation of the database, we use the JPA, no need to manually build SQL statements, but only need to provide the name of the method in accordance with the specification can be achieved additions and deletions to change search the database. The client uses axios json data transfer between front and rear ends. Front-end development tools webstorm, the back-end using idea, interface data usage postman debugging, database use navicat management. But because we do not have a complete front and back end web project development experience, so most of the content need to educate yourself, very time-consuming.
2. Work Summary
In the early project development, we are not familiar with the project, led to the people is not clear division of labor, the project stalled progress. After determining the division of labor, work content and progress of communication between team members remains an important issue, because the development is the same project, ultimately bound to be integrated, so many modules and unified framework to be determined at the initial stage, or eventually even page format can not match, such as our design is unreasonable in the database, leading to a series of functions to achieve very complex, only the latter part of the database and then modified so that each person must modify the code, adding to the burden. Although the use of front and rear end of the separation policy, but still have to exchange data transmission, so the back end api to do the test feedback using the corresponding demand for front-end, front-end interfaces to api and the right to send and read the correct data and demand data format, which requires the front and rear end members often communicate in the development process, the differences are unavoidable, to update the code when members meet each other always feel someone else to write bad place, these need to communicate in a regular meeting, timely and express their opinions, ask questions, and ultimately improve the quality of the project.
V. Courses
- For the regular meeting, the proposal directly once a week or more, I think this group project, communication is so important, let team members know their work next focus, promote the enthusiasm of team members, improve work efficiency and quality of projects .
- Due to the small software development experience, most of the content can only be self-study, a variety of small problems can only Baidu, time-consuming trial and error, I hope the teacher can give some examples of project development, architecture, as well as the basic source tool framework. In this way it will not be too tired to learn.
- Course schedule should be a little more compact, requirements analysis and prototyping phases of time to pull a little longer, the encoding time slightly nervous.