Release judgment mechanism・Keep a record of the release judgment result in the checklist
- 1. Release judgment leaves the judgment result for each item in the checklist
- 2. On the cover of the release judgment result, write what the judgment target is and what the judgment result is.
- 3. For ISO9001, this alone is fine, but this alone does not give a good idea of the reason for the judgment.
- 4. Let’s leave a list of judgment results for each of the confirmation items for various judgments
- 5.
- 6. In the checklist, process quality and product quality are checked and recorded item by item.
- 7. Special confirmation items are confirmation of points of concern
- 8. Confirmation result is good / good / bad 3 stages
- 9. Let’s leave the materials used for confirmation together with the judgment result
- 10. The top of the checklist is double, but don’t worry
Release judgment leaves the judgment result for each item in the checklist
In the previous articles, we have introduced three of the four criteria for release determination and the four mechanisms for release determination . With this, the information necessary for software release judgment, the judgment method, and the mechanism for carrying out the judgment are almost complete. By the way, how should we keep the result of the release judgment ? Gutara father, the cover of the release decision result and, check list, which records a judgment result of each judgment item because we have to leave the determination result using the, let’s introduce the content in this article.
It depends on each organization how to judge the release and what criteria to judge whether or not to release it. However, the fact that the result of the release judgment must be recorded is a common task required by all organizations.
How can may be leaving the result of the release decision in any manner, if to leave a long-awaited result, at a later what information based on, any idea how to determine the propriety of the release, easy to understand material left in It’s good to keep it. As the name of the material that records the release judgment result is generally a name such as “release judgment result", we will call it “release judgment result" in this article.
On the cover of the release judgment result, write what the judgment target is and what the judgment result is.
The “release judgment result" has various formats depending on the organization, but in general, there is a cover page (first page) with the following items written on it.
- Release judgment ID number (This is the release judgment result ID, which is often the document number)
- Software subject to release judgment (name and version are required for software)
- Release judgment result (pass or fail or conditionally pass or pass is recorded in an easy-to-understand manner)
- Approval of the person responsible for the release judgment (clarify who is responsible for the judgment with a seal, autograph or electronic signature)
- Approval of release judgment councilors (in the case of consensus, it is also necessary to record who participated)
- Date and time of release judgment (This is a required item for any document)
- Reason for release judgment (Write down the reason for passing or failing briefly)
For ISO9001, this alone is fine, but this alone does not give a good idea of the reason for the judgment.
This cover page alone is valid as a “release judgment result". The purpose of “Release Judgment Result" is to record for which software , on what month, on what day , who is responsible for the release, so the purpose is established only on this cover page. Whether it is ISO9001 or CMMI, there is no problem with the “release judgment result" that describes the above items.
But this alone makes me a little lonely. Especially when it is judged that the release is not possible, if you do not know clearly what went wrong, you will not know what to improve by the time of re-challenge. Also, even if you look at this judgment result at a later date, it is not clear what kind of information was used to make the pass / fail judgment. This cover alone is a bit unfriendly .
Let’s leave a list of judgment results for each of the confirmation items for various judgments
As introduced in the article on the four criteria for release judgment, the quality of the software is checked from various points of view, and the release is approved when there is no overall problem. If the result of the judgment regarding each viewpoint or the record remains, it is easy to understand not only the pass / fail of the release but also what points should be improved from the next time. Also, if you analyze the results of many release judgments, you can see the points for improvement as an organization.
Therefore, Father Gutara created the following checklist for each release judgment item and attached it to the second and subsequent pages of the “release judgment result". By looking at the record of this checklist, you can know what kind of software quality is sufficient and what part is lacking. I will put the checklist used by my father Gutara on it, so please refer to it.
Checklist example (click to open pdf)
In the checklist, process quality and product quality are checked and recorded item by item.
The main body of the checklist is divided into process process quality and product quality, and the necessary check items are itemized. For details on how to check each item and how to judge it, please refer to the article on 4 criteria for release judgment . Since there are various judgment items, it is easy to use if you select only the necessary items and make a list like this.
Process quality mainly consists of a column that describes the confirmation results of the development process implementation status of whether the planned process is being implemented as planned , the status of the process for monitoring the process and quality, in other words, the status of the management process. lining up.
Product quality, in the phase of each of the implementation and testing and design a product is, the quality of the design documents and source code and executable programs measure, to check the status of the comments and detection bug of design reviews and code reviews, There are columns for judging the necessity of quality.
Special confirmation items are confirmation of points of concern
Apart from process quality and product quality, there is also a column called special confirmation items . Process quality and product quality are lined up with items that must be checked at each release review. However, if you continue to release software, you may want to focus on a specific area at some point.
For example, when the signs of cyber attacks are increasing in the world, it is tempting to pay particular attention to the status of security functions. In such a case, add one item “Security" to this special confirmation item column and check carefully every time.
The embedded products that Gutara’s father had decided to release had to be careful about the RAS function and security , so these two items are included. The other item, " time bomb bug, " was coined by Father Gutara.
The problem of exhaustion of kernel resources such as memory and the problem of roll-up of counters often occur after a long time has passed since the software started running, so we called it a time bomb bug. The potential for this time bomb bug often causes defects in all products in the market, albeit slightly before or after the time of occurrence. And unfortunately it’s hard to find in pre-shipment tests. Therefore, it is included as an item to pay particular attention to.
Confirmation result is good / good / bad 3 stages
The judgment result according to each check item is recorded in 3 stages of good / good / bad . If there is no problem with the item, it is acceptable, if it is well done and there is a security supervisor, it is good, but if there is a quality problem, it is not possible.
As a software release judgment method , I think it is simple and clear that the release is permitted if there is no judgment that it is not possible .
Of course, it’s best if all the software isn’t possible, but the world doesn’t go that well. One, two, or three items may not be available. In such a case, on condition that the impossible items are improved to XXX , the release is conditionally permitted , or the application for special recruitment is switched to, and the range of influence on the market of the problem is reexamined before the release. It is also necessary to re-determine whether or not it is possible.
Let’s leave the materials used for confirmation together with the judgment result
In this checklist, each confirmation item also has a column labeled " Confirmation result and confirmation “. Here, it describes the actual article number and record the location of the server documentation class that was used to confirm, throat at what you’ve determined based on’m such information and record.
And I think it is better to record the ID number of the material or keep a copy of the material itself so that you can refer to the materials used for the release judgment without fail even after several years .
At the beginning, Gutara’s father recorded only the document number, but at one point when he tried to go back to the record of past release judgments, a little trouble occurred. Shall be deemed to be replaced design document of the document number is not on record, because had been also recorded storage location on the server, but that is the storage place went to see, there are the same document numbers in the same document name of , Multiple versions of the material were recorded.
Yes, as the development continues, the design documents are revised steadily, so multiple versions of the design documents were recorded , from the old version to the new version . The development team also registers the design documents used for the source code control system, so there is no confusion, but the quality assurance department retrieves the relevant design documents based on the tag number of the source code control system. It takes a lot of time and effort.
After that, my father Gutara decided to record a copy of all the materials confirmed at the time of release judgment in another folder as confirmation of release judgment . Fortunately, digitized materials are easy to copy, and unless they are audio or video, even if the amount of documents is a little large, you need to worry about the lack of storage space given the vast storage capacity of recent HDDs. There is no. So, although it’s a bit rough, I took the method of recording a copy of all the materials confirmed in the release judgment.
The top of the checklist is double, but don’t worry
At the top of the checklist, the content is duplicated with the first page of “Release Judgment Result", but there is a column to describe the software to be released and the judgment date and time.
At the time of actual release judgment, we first perform specific confirmation according to this checklist, comprehensively judge pass / fail based on the result, and write the result on the first page. I did. It can take several days to check the checklist, and the simple reason is that if you’re doing multiple tasks at the same time and you don’t have the minimum information about what the decision is, you’ll be confused.
I’ve introduced the four mechanisms for release judgment, but how was it? There are many items that need to be confirmed when releasing software. If possible, it would be nice if multiple people could share the work and work while reviewing each other.