Software Engineering major operations - Association Management System Individual Project Summary

Software Engineering major operations - Association Management System Individual Project Summary

Project Overview

github link: https://github.com/yonginggg/StudentClubManagementSoftware

Design and implement a community management system, complete members, departments, activities, announcements and other management.

Personal main work

Early prototypes of the completed part of the ink knife is provided to achieve the front end reference point. In this process, we need to consider the user's habits, use of logic, aesthetics of the page, the front end of ease of implementation and so on.

Partially completed project timing diagram for the operation of the internal processes of the project have a deeper understanding.

The latter is responsible for the back-end part of the realization that more investigation excision community, community members, according to the specific needs of the front, gives the corresponding results are returned.

We used the front and rear ends and spring boot combination vue implementation framework. In the rear end portion, a combination of springboot + JPA + Mysql. springboot Javabeans inversion-based control container, and a Java JPA persistence specification, there is provided a tool object association, like Hibernate, allow developers to operate departing from DAO layer.

In the implementation of the back end, I learned these tools / frameworks / specifications of use in understanding the code base layers on the written part of the data processing code associations and community members, and the data alibaba.fastjson.JSONObject format returns to the front end.

Use of the postman written api tested.

Project Summary

In this project, the practice of the basic processes and teamwork development of software engineering.

When you configure the environment, due to configuration errors domestic maven mirror sites, resulting in failure of the jar package has been acquired, it took a little time to find out why.

At the beginning of back-end code to write, because the order parameter of the function call problem, there has been an error, but the layers are not familiar with the code, it took a little time to find the error.

Personally feel that team in the allocation of tasks, did not fully take into account the amount of work or do not work on clear and accurate predict that workload distribution is not balanced, the number of front-end too heavy workload. And I seem relatively easy backend.

Communication within the team still seems not enough. And, it might be a little delay, and no executive power within the team who has been a strong push everyone, causing a bit slow progress of the team.

Courses

• Before the big work, hoping to share previous works, so that we can understand the past, sister school seniors did, what with technology. Since the beginning of operations at large, in fact, it is still there, especially the loss of the web end one o'clock, before most people have no web development experience, learning costs actually quite large.

• In the mid big job, we can do a mid-term evaluation of the project in the form of technology sharing. Other groups used to know what technology, if you can refer to, their progress carried out to what extent, and so on.