Software Development Summary

This semester Yang Hongli teacher brought us software development this lesson.

I've written a lot of code before this class. But those are not "software", but programs.

Because before the system to learn this lesson, I have to write about the code is not know why. Basically is the brain to think, go to the next, basically finished and then slowly debugging changes, so often in the end to find structural defects, or program large rewrite, or sacrifice performance, forcibly complete the program. Even the design is basically a flowchart design, and a class diagram of the idea.

But after learning this lesson is different, UML diagram in a variety of diagrams can be used to describe the structure of the program, before the program can be written in detail to visualize the function of the program, data changes. In this way, errors can be found in a timely manner before they are written, greatly reducing the cost of errors.

At the same time, the use of this knowledge in pairing projects and team projects has increased my mastery of him and has definitely increased my ability to solve practical problems.

Software Development Summary