Summary of mid-term study of software engineering

After half a semester of software engineering study, last week also conducted a mid-term defense, and some of their own feelings. I have a re-understanding of the software engineering course, because most of the courses are based on discussion and group practice, not on theoretical knowledge as I imagined. In the group project, the teacher plays the role of a product manager to make requests, and also plays the role of a mentor to provide the underlying data building knowledge. I think pre-project preparation, such as demand analysis and database design, is more important than real code implementations and takes time. Some groups after listening to the teacher's homework, a week to set up a good framework, the result is wrong demand and re-come, so that is not worth the candle, should be the need to clear up, step by step to the bottom of the database building, roughly the route after the start to write code, to avoid unnecessary detours, to achieve efficient development.

The understanding of software engineering is like teaching how to get a team to develop projects according to certain rules. There is certainly a lot of problems with the technical aspects of project development, which are related to their own development experience and basic knowledge. In this period of time, feel their ability to improve a lot, previously only like to do the interface and application of the upper aspects of things, this time I am also responsible for writing background data aspects, so to learn the underlying framework of knowledge, learning how to conduct business logic analysis. This course of learning problems and shortcomings should be in the team's communication, the team everyone's research direction is not the same, the foundation is uneven, communication is a bit difficult.

Summary of mid-term study of software engineering