Software Engineering-Course Summary

This semester's software engineering class is about to end, unconsciously another semester passed, we have reached the end of the junior year, is about to enter the senior year, we will also enter the soft to learn. Looking back at this semester's software engineering class, we learned a lot about our professional knowledge.

I have basically found the answer to the questions raised during the course:

1, software engineer how to improve.

A: More practice programming, read more about the Program class books, more understanding of other people's procedures.

2, the development of software, team division of the specific how to do.

A: This depends on the number of teams and the software being produced.

3. How much does MSF help the team?

A: MSF is a large-scale system development guide that describes how to develop applications for client/server structures with team models, process models, and application models, and is a reference for building and developing distributed enterprise system applications based on Microsoft tools and technologies. The largest feature of MSF is commercialization and is reflected throughout the implementation of the project.

4, the user's needs and their own design contradictions, should be how to deal with.

A: Priority to ask the user's opinion, after all, software design to take into account the needs of users.

5, when the development of software differences, the team should be how to deal with.

A: Discussion, after careful study and find information, choose better.

At the beginning, I do not know why there is software engineering This course, in my opinion, as long as it can be written to write, but after studying this course, I began to understand the importance of software engineering, every time to make software, always have an initial plan, if not even a simple plan is not, There is no way to talk about the production software, in the beginning, we are made by the individual to make a relatively simple four operational procedures, relatively speaking is a relatively simple exercise, I did not do anything too complicated planning, just made a very simple four operation program, but then, our task is to add this program function, At first it was very simple, but as the function increased, the program became more and more complex, which led me to have the idea, but there is a sense of not starting up, fortunately, after the pair programming, after a teammate's help, the program has become simple, we have a plan, with the production program, in 2 people's efforts, We finally completed the process of production. In the second half of the course, we started the team project. At the beginning, I am not used to, after all, only a program, divided into a number of people, the final program will be because of the number of people and no way to integrate, but the software engineering class gave us a lot of inspiration, we use the teacher in class and the introduction of the book, Division of labor, do not seem so laborious. Everyone is responsible for the part, and in the case of code specification, our integration is much simpler. It also has a good guide to our future development.

　　

I have nothing to suggest for the software engineering lesson. But I think it's possible to decorate some simple little programs occasionally, and then let's add features or improve others ' programs. Understanding other people's procedures is also a point in our study of software engineering code specifications.

Software Engineering-Course Summary