Software Engineering major operations - personal summary
Project documentation process
GitHub link: https://github.com/SiriusZ-BOTTLE/MucMucMusic
UML diagrams and design Description: https://www.cnblogs.com/Sirius-Z/p/11885955.html
Prototyping: https://www.cnblogs.com/Sirius-Z/p/11973794.html
Project source code
mucmuc database: https://www.cnblogs.com/Sirius-Z/p/11885955.html
mucmuc distal Code: https://github.com/SiriusZ-BOTTLE/MucMucMusic/tree/master/Muc
mucmuc back-end code: https://github.com/SiriusZ-BOTTLE/MucMucMusic/tree/master/MucMucServer
I. Project Overview
The entire project, according to the first to write project needs analysis, and then draw UML diagrams of the project, and then a prototype design, and finally write code for the entire project. Because the front and rear end of the project need to interact, we used the back end springboot framework, database use mysql, Ali cloud deployed on the server, and use jdbc interact, front-end development of the app for Android.
II. Personal summary
2.1 Overview of work
I am responsible for the back-end coding.
2.1.1 design stage
We carried out the project in accordance with the software engineering process. But because it is the first time such a process, the way through a lot of discussion, and also a few detours. Needs analysis can help us understand the development objectives of the project and what needs to be done, so that we can make fewer mistakes in future programming. UML diagram of the entire system architecture and code architecture expressed. Prototyping probably demonstrates the software. While we design these steps are relatively simple, but through these steps, get a lot of help on making the entire project.
At the first regular meeting, we were members of the division of labor, as well as discuss other matters.
2.1.2 coding stage
Since we are not familiar with the framework, it is necessary to learn from scratch. I am responsible for the back-end programming, springboot framework. In the development of the project, we follow the substantially front and rear ends separably development, the front end sends a request, through the rear end of the http protocol, using the front end json interact return results. In this way, we can facilitate the work of the division of labor, and modify the code.
I write code layer by layer. storage layer entity entity class, DAO database layer persistence operations, just additions and deletions to achieve a change to the database search operation. the business service layer is a layer, storing service logic processing provides a method call controller layer. controller is a controller level, reception parameter pass over the front end of the operation, and return the results.
Writing dao layer in consideration of the query, update, and other operations may be required to determine the data by other attributes than the main key, it is empty to whether it is necessary to increase the sql statement this attribute through the attribute determination target in the preparation of the . For multi-table operation, we use the connector to create a view to obtaining data, to facilitate the operation. In the service layer, a mainly software implementation of the various specific operations. And, in an implementation, such an operation would need to consider whether additional information impact, and treated accordingly. At the same time, also need to return the information success and failure. In the controller layer, receiving objects passed over the front end with json format, and return the results. Because of the comment may need to require the user to query range or increases, song information, a plurality of parameters resulting in the need, after we discuss the operation map as a parameter in the controller layer.
In the latter part of another person's programming, back-end, Zhang Shurui when checking the code, the two of us because of the different coding style, and generated a lot of controversy. At the same time, because the writing is not standardized format, on the one hand to others reading caused trouble, but when modified also caused some problems.
2.2 Summary of work
I am responsible for the preparation of the back-end code. I think in the code writing specifications, our previous exchange is not enough. If you can determine a good writing specifications, and can make comments in writing on the way to enhance the readability of the code, not only makes the code more clean, modifying later, it can also be more efficient in the previous period.
2.3 Project Reflection
In the course of the entire project is completed, our group early progress is slow, the enthusiasm is not high enough, a lot of work is then hurried out. And the late programming began relatively late, so that we lags behind on progress. And, on with the work crew assignment is also not good enough, causing some crew workload, some of the team members more free situation. This also needs to be improved in the future. Achieve the manipulated image is a major problem of our project. We operate in base64 stored on the database, but the result, leading to comment on our Amway wall module loading slowly. I later on the Internet through the inquiry, in fact, the picture is more suitable for storage access by way of a path on a local or on a server.
2.4 Project Summary
Through this project, I had a productive session. The project is carried out, in accordance with the requirements of software engineering is carried out. And through this project, let us know the content of software engineering, software engineering experience to the meaning of a certain extent. And, let us know writing software should not be behind closed doors, the need constantly to learn from the experience of others. At the same time the team project, let us know in the programming process, how teams need to cooperate.
III. Courses
Check the class in each round, I think the teacher After reviewing the progress of each team can make a group or groups do better group show. In this way, on the one hand we know that the gap between themselves and other groups, on the other hand, also allows us to better understand the significance of each step.
Some of the more abstract concepts of software engineering, I think the teacher can also speak some more practical examples in business programming, let us know more about business in the actual programming, understanding some of the concepts of software engineering.