Soft audit Checklist・No5: Quality Assurance Process (2/2)
The fourth part of the development process checklist, the second half of quality assurance.
Continuing from the previous article, this article introduces (1) individual items of quality assurance in the development process of the software audit checklist . (The checklist itself can be found in the article on Software Audit Practice / Checklist Part 1: Development Process (Requirements Management) , so please refer to that.)
In the previous article, we introduced item numbers up to QA-5, so we will introduce items after QA-6.
[Item number: QA-06]
It would be nice to have a small number of bugs found in the test and fix them quickly, but usually a large number of bugs are found and the design team is just devoted to fighting them. At such times, blindly eye in front of rather than going to crush a bug Chan from an important bug with the priority is that going to fix is important. Make sure that the criteria for prioritizing bugs, how to prioritize them, and how to investigate and take countermeasures for bugs according to the priorities are properly decided and implemented as they are.
[Item number: QA-07]
After the test is over, the next is the release, but the release judgment as to whether or not it is okay to release is the most important judgment process as software. Regarding the method of judgment, for example, what kind of information is used to judge the product quality of software, what is the reference value when judging , who is the final person in charge of judgment, etc. Make sure that the rules for are set and implemented according to those rules.
[Item number: QA-08]
There are several types of software releases in addition to the official release. Alpha release to evaluate some features, beta release to evaluate usability with all features , bug FIX release to fix bugs , and other limited evaluations within the company and affiliated companies There is also an engine ring release for . There are various types of releases and it is troublesome, but the products made at the factory also have prototypes and free samples, so it is not limited to software.
However, if there are multiple types of software released by an organization, the purpose and purpose of each release must be properly defined . In addition, it is necessary to clarify the method of determining whether or not to release each release and the criteria for determining it. Otherwise, both inside and outside the company will be confused. So make sure you have a clear definition and release criteria for the type of release your organization is using.
[Item number: QA-09]
If you are outsourced to software development and the outsourced work includes tests, you need to inform the development contractor on a regular basis of information such as test plans and progress and bugs as a result . .. Find out what you are doing specifically about such activities.
[Item number: QA-10]
The software is invisible, so when we release it, we will provide the release notes together and explain what kind of software it is. The release notes describe the features and fixed bugs, but not only that, but what kind of tests were done to check the quality, the remaining bugs that were found in the tests but were not fixed in time by this release What kind of thing is in the software is very important for the recipient of the software. Make sure that the information works as described in the release notes.
[Item number: QA-11]
Release notes are an important document for the software. In terms of quality, information on remaining bugs (bug found in internal testing but not fixed by this lease) is very important. I hope that all such important information is included in the release notes . So where is the original information recorded and who picks it out and how to put it in the release notes? If the release notes are created by relying only on the memory in someone’s head, important items may be missed. Check the specific method of extracting the contents to be included in the release notes from what source information and how to extract the contents to be put on the release notes so that the information written in the release notes is not leaked.
[Item number: QA-12]
The last item is a little different from the other items. There are various methods for software development management, but there is also management using metrics (which is a software quality index when translated into Japanese ). If you have a small development team with a few people, you can understand the quality and progress without managing the metrics, but if multiple teams are working together and the total number is dozens , some metrics Without it, it will be difficult to control progress and quality . Check whether the organization of the other party manages development by soft metrics, and if you are using metrics, what metrics are used and what are the standards.
Next to quality assurance is configuration management
Next to quality assurance, we will introduce the items to be checked for configuration management in the next article.