Release judgment is the most important matter to guarantee the quality of software

26/07/2018Release Judgment

 

Release judgment is the first step in quality improvement

If your business goal was to improve the quality of your software, what would you start with?

There are many ways to improve the quality of your software, but which one is the most effective? Would you like to improve the planning of software in the most upstream process of development ? Or do you improve the software design process ? Or do you review the quality and quantity of the test ? All of them are very important for improving the quality of software.

However, Gutara’s father started by reviewing the software release judgment . In the world language of general products, it is a shipping decision. It’s not something that has a special idea, it’s a very common way of doing quality assurance organizations.

Release judgment means not to release poor quality software

In other words , releasing good quality software means not releasing bad quality software . Does it sound like a mere word game? Well, there is also such a side. However, the means to release good quality software is quite difficult because there are so many things to think about. But the idea of ​​not releasing bad quality software is simple. All you have to do is follow the rule that you should inspect before releasing and not release bad software , which is easy to understand as a methodology.

However, unlike mass-produced products that make the same product at the factory, it is difficult to check the quality of single- product software at the time of release . As I wrote elsewhere, in the case of mass-produced products , it has been decided that this should be correct . Sometimes called a golden sample. If it is the same as the golden sample, it can be judged that the quality is good, so various inspections and measurements are performed before shipping, and if there is no difference from the golden sample, it is a good product and shipped, and if the difference is large, it is judged as a defective product. You can take the method of not shipping.

However, there is no such thing as a golden sample in the software of one-off products . Although there are required specifications, the required specifications are not the finished software equivalent to the golden sample, so the method of measuring the difference from the golden sample and judging it as a defective product is easy to judge the quality of the software. can not use.

How to identify poor quality software

The quality of the software whether it has been a good level even if the release, if you determined to do?

Of course, for software, when the software is used, who uses it, what kind of effect it will have if there is a problem with the software, and so on. The level of quality required varies widely. However , I think the method of determining whether the quality of software has reached the required level will be similar to some extent.

Father Gutara checks the product quality status of the software, checks the process quality status, checks the test quality status , considers the impact of residual bugs on the market, and judges the software quality. I have decided whether it is okay to release it.

Software for the release decision is, for the software for the first time of release in the case of the conference attracted participants You may also be comprehensively judge to hear the people of the opinion of the various position performs, additional functions Ya If it was a release aimed at fixing bugs, I would sometimes decide by myself. In addition, the criteria for judgment have changed depending on whether the type of software used to judge the release is the official version, the evaluation version, or the beta version .

Introduction of Gutara father style release judgment

In the following articles classified as release judgment, I tried to organize as much as possible the information and judgment criteria necessary for software release judgment, so please have a look. 

At the beginning of the title of the article, there is a sub-category regarding software release judgment . The subtitle following the subcategory is the outline of the specific article. There is no particular rule on the order of reading, so please read the articles in order from the one you are interested in.

For a quick overview , check out the two articles outlining the sub-categories . If you want to know a little more about what is written in the summary article, please see the individual articles or read the individual articles linked from the end of the summary article in order.

  •   Overview・Four criteria for release judgment
  •   Overview・Four mechanisms for release judgment
  •   Release judgment criteria・The amount of test is measured by test density
  •   Release judgment criteria・Check the test execution rate when judging the amount of test
  •   Release judgment criteria・The first type of test is abnormal and semi-normal
  •   Release judgment criteria・The second type of test is stability and robustness
  •   Release judgment criteria・The third type of test is the RAS function
  •   Release judgment criteria・The fourth type of test is the version upgrade function
  •   Release judgment criteria・The fifth type of test is confirmation of past defects 
  •   Release judgment criteria・Test implementation status based on progress confirmation
  •   Release judgment criteria・See the status of bug detection for evaluate of testing
  •   Release judgment criteria・Bug is considered separately to potential bugs and obvious bug
  •   Release judgment criteria・Estimate how many potential bugs remain
  •   Release judgment criteria・Remaining bug 0 is not a mandatory condition
  •   Release judgment criteria・The reliability growth curve is reasonably usableThe reliability growth curve is reasonably usable
  •   Release judgment criteria・The importance of residual bugs is judged from the degree of impact on service provision
  •   Release judgment criteria・Estimate the number of call center calls from the remaining bugs
  •   Release judgment criteria・Estimate the number of call center calls from the remaining bugs(2-nd)
  •   Release judgment criteria・Estimate the number of call center calls from the remaining bugs(3-rd)
  •   Release judgment criteria・To check the product quality, first check the design quality
  •   Release judgment criteria・Check the code quality to check the product quality
  •   Release judgment criteria・Confirmation of process quality is based on development practice and development
  •   Release judgment criteria・To check the development management, first look at the development plan
  •   Release judgment criteria・Check the development management process by the design, implementation, and test plan
  •   Release judgment criteria・See also concern and risk management and baseline management
  •   Release judgment criteria・Is the maintenance system and contract clear?
  •   Release judgment criteria・Also check the implementation status of the gate process
  •   Release judgment mechanism・Two types of software releases, one for external and the other for internal
  •   Release judgment mechanism・External releases are subject to release judgment
  •   Release judgment mechanism・Release judgment is made by QA-Manager or Dev.-Manager or the president
  •   Release judgment mechanism・The best way to determine the release is the official review
  •   Release judgment mechanism・Release judgment is also possible two-department meeting or individual judgment
  •   Release judgment mechanism・Keep a record of the release judgment result in the checklist
  •   Release judgment others・Software may be released by special adoption
  •   Release judgment others・Special recruitment is judged by test status, latent bugs and residual bugs
  •   Release judgment others・Annoying relationship between testing and bugs
  •   Release judgment others・Product quality is important for software quality
  •   Release judgment is the most important matter to guarantee the quality of software