Software Engineering-Summary _ Basics

Look at their own set of this goal plan, 50 set of soft work video in my stumbled in the reading, the overall reason or time management did not do properly.

Sometimes you can concentrate on four or five episodes a day, sometimes for days without looking at them. The middle has to find a teacher, a lot better. I started to do 3-5 days of planning, every day have insisted on watching, fortunately, every day to complete their own set of plans.

In a professional examination of the pressure, their summary summed up five days, think of their own look is really not good, or do not have to sum up when such a waste of time. Soft work video is the most of their own pictures of a study, the following is the final summary of the diagram, just do the most preliminary thinking.

Here is a larger picture, there may be a bit of chaos, click to see the big Picture:

A good software engineering is to allow users to recognize and satisfaction. In the feasibility study, we should stand on the user's point of view, and consider four feasibility.

Software planning is a prerequisite is a necessary link, only the plan passed to have the reason to continue, is the preparation of demand analysis.

Requirements analysis begins to analyze what the software is doing.

Software design is more important, because some high-quality software is designed, not behind the management. Just like "All imperialism is paper tiger" can be concluded that "poor system design must produce poor software systems." Therefore, we must strive to ensure that the system design "root is Miao red", all left-leaning, right-wing design trend of thought to eliminate in the embryonic state. There is an interesting analogy:

Just like any part of a person's body design is not good enough to be a qualified person, like a software system, each piece is linked to each other. When you design the system, it is necessary to embody the idea of serving the people wholeheartedly, or it will probably destroy a "person".

Program coding is to embody the quality of a programmer, from code specifications are all programming style, a good code is not who can not see the embodiment of you are very cow, it is your code programming people can read, you can use, you can continue your work, and have a good standard, is really skilled.

Software testing, if the preparation of the front to do well, in the test phase of the error page will be very little, the corresponding maintenance of the cost will be very low, due to the design phase of the error caused in the maintenance phase to pay more than 10 times times the price, which is more visible than the weight.

Software maintenance, accounting for the entire system life cycle of 70%, software maintenance of the difficult factors are determined by the designers and users.

Finally, the specification of the document, a normative document directly determines the next step of the software understanding of the software and the completion of the good or bad. So to develop their own ability to write standardized documents.

Although the study of software engineering is stumbling, there is always no practical feeling, then continue to work hard.

Cao's son Cao Shu had suggested: "A man when learning weiqing, Huo go to disease, meritorious desert, drove hundreds of thousands of, freely, how can for the doctor Yes." "There are so many things to regret that you have to be diligent now. Knowing he is not good, but willing to mend, and strive to learn deeper and wider. The little woman was more so.