Confusion and reflection on the 13-17 chapters of the Law of construction--modern software engineering

The 13th Chapter Software test

Testing principles

First, the test should be carried out as early as possible, preferably at the demand stage, because the most serious error is that the system can not meet the needs of users.

Second, programmers should avoid checking their own programs, software testing should be the responsibility of third parties.

Third, the design of test cases should take into account the legal input and illegal input and various boundary conditions, in special cases do not create extreme state and unexpected state.

Four, we should pay full attention to the cluster phenomenon in the test.

Five, the countermeasure is a confirmation process to the error result. The error usually tested by a, must be confirmed by B. Serious errors can convene a review meeting to discuss and analyze, the test results to be strictly confirmed, whether there is really this problem and the severity of the.

Six, to develop a rigorous test plan. Be sure to make a test plan and be instructive. The test schedule is as loose as possible, and you don't want to have a high level of testing done in a very short period of time.

Seven, save the test plan, test case, error statistics and final analysis report, which is convenient for maintenance.

14th Chapter Quality Assurance

Software quality = Program Quality + Software engineering quality

Chapter 15th stability and release phase

15.2 After the release--hindsight conference

At the heart of the conference: "If you can do it again, what can you do better?" "Since there is hindsight Zhuge Liang, it certainly has the prior Zhuge Liang, but in advance no matter how comprehensive, or there will be deficiencies." So the hindsight meeting is very important.

16th. Innovation in IT Industry

16.2 Time to innovate

We can understand from G-number this game 3 points: 1, winner take all. 2, weak hand versus. 3, only one step ahead. We know the more games we play, the smaller the answer. So it is very important to seize the opportunity of innovation.

17th. People, Performance and professional ethics

17.5.2 running-in stage

Handle problems correctly

1) Members who are technically competent and recognized through practical work should be encouraged to play a more technical leadership role.

(2) For some people who often have different opinions, Maverick, seemingly drag the team hind legs, then should not be judged, in fact, they are probably good employees, but not the appropriate way to express their opinions, do not know how to persuade others, should encourage them to find and team coexistence, work together the way.

(3) Although some members are able to cope with their own work, they do not like to discuss, share experience, and seem to have no higher requirements. For this type of person, they should be able to work with a more confident and motivated colleague, give them a higher job, and inspire their enthusiasm with challenging work.

(4) Some of the members in the actual work show poor skills, not competent to work. For such members, consider arranging what they do, adjusting their position in the team, and doing their best.

Confusion and reflection on the 13-17 chapters of the Law of construction--modern software engineering