The method of construction read Note 06

14th Chapter Quality Assurance

The quality of software, software to meet the needs of users and stakeholders. Software quality = Program Quality + Software engineering quality. The quality of the program, the quality of the program is reflected in the quality of software external functions. To measure the function of the software, the basic judgment can be judged by "yes | no". The development process of software engineering has three main features: "Good", "fast", "cheap". Software development process risk control, software development process has a variety of dependencies, some of the progress of projects are often interrupted by these factors, to control these risks. The quality of software engineering, how to measure the quality of software engineering as a result, one of the more mature theory is CMMI. CMMI First level, initial level. CMMI level two, management level. CMMI Level Three, explicit (defined) level. CMMI level Four, quantitative management level.        CMMI level five, optimization level. Quality of the cost, to achieve a certain degree of software quality, is to pay the cost.

Test roles are independent, the division of labor is the result of social and industry evolution, development and testing is actually two branches of software engineering, for different software/services, testing the way and degree of difference.

Chapter 15th stability and release phase

A team has gone through the planning/design/development phases to achieve the goal of code complete, and it seems that the next thing is going to be the case. In fact, the final stage of the software life cycle is often the most Test team, not only Test team project management level, strain capacity, but also test the team's "blood type."

The Consultation group (Triage team), each role representative of the software team (PM/DEV/TEST/UX, etc.) formed a consultation group to deal with every issue affecting the release of the product. Complex project consultation, at the beginning of the stabilization phase, when the team decides which defects need to be repaired, the team members perform the necessary design, implementation, testing work, and check in the code changes. However, as the project progresses and the release date approaches, the team also ensures that the modification will not adversely affect the product.

In our team, in the stability and release phase, also found a lot of bugs, some because of the problem set, some of the problems of the program. We'll start with some important bug changes and then modify the small ones, some of which require refactoring, and we'll put them in the next version.

A few tricks: tricks 1 design changes, tricks 2:ZBB, tricks 3: The final regression test, Tricks 4: Fixed the threshold of the bug gradually improved, tricks 5: Gradually frozen

Chapter 16 Innovation in the IT industry

Innovation is sometimes the spark of the thing, it may be to see the thought, there is inspiration. Sometimes it is the efforts of several generations. People do not necessarily like innovation, innovation, and may be blocked by some old-fashioned ideas. Innovators are not all lead. Some companies are also up-and-comer, but they do better than their predecessors. Not necessarily experts in the field can innovate, experts are not necessarily credible. Innovation should be followed by an analysis of the data to find the most appropriate opportunities and goals. In order to carry out effective innovation.

The method of construction read Note 06