JPS626332A - Evaluation system for quality of software - Google Patents
Evaluation system for quality of softwareInfo
- Publication number
- JPS626332A JPS626332A JP60144717A JP14471785A JPS626332A JP S626332 A JPS626332 A JP S626332A JP 60144717 A JP60144717 A JP 60144717A JP 14471785 A JP14471785 A JP 14471785A JP S626332 A JPS626332 A JP S626332A
- Authority
- JP
- Japan
- Prior art keywords
- work
- quality
- bugs
- software
- testing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Debugging And Monitoring (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
(57)【要約】本公報は電子出願前の出願データであるた
め要約のデータは記録されません。(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.
Description
【発明の詳細な説明】
〔発明の利用分野〕
本発明はソフトウェアの品質評価方式に係り、特にコン
ピュータ・ソフトウェアに好適なテストで摘出されるバ
グの内容に関する。DETAILED DESCRIPTION OF THE INVENTION [Field of Application of the Invention] The present invention relates to a software quality evaluation method, and more particularly to the contents of bugs detected by tests suitable for computer software.
従来のバグの内容に関する文献は、（１）「アプリケー
ションプログラム開発での品質管理事例」八１）信（富
士通）〔日科技連第３回シンポジウム） Ｐ−ａｌ、ｔ
：２）ｒプランニングアンドメジャリングプログラムイ
ンプリメンテイション」エツチレマス（アイビーエム）
フロシーデイングスオプソフトウエアエンジニアリング
エンバイアンメンツ、ランスディン、シャーマニー６゜
１９８０ベージ１０ （ＩＰＬａｎｎｉｔｓｇ ａｎｄ
ｙｎａｔｒｂｒｉｎｇ ｐｒｏｇｒａｍｉｍｐｌｔｍ
ａｎｔａｔｉｏｎＪ Ｈ、Ｒｉｍａｔａ （ＩＢＭ）
ｐｒｏｃｅｅｄｉｎｇｓ ｏｆＪμルー１９８０Ｐ、１
０）Ｋ記載のように設計工程で摘出されるエラー中心に
目標設定の考え方もある。しかしテスト工程で摘出され
るバグに絞って（ドキエメント不良でなくプログラムネ
良主体）、設計工程・作業に対応してテスト工程・作業
も区分されることを前提忙、それらのテスト工程・作業
では対応する設計工程で作込んだバグの割合いが最も多
いとい５基準を設け、それを利用して自動的に品質評価
する点については配慮さ〔発明の目的〕
本発明の目的はバグを作込む設計工程と摘出するテスト
工程について、品質を維持向上させるための適正な工程
・作業分割とそれらの相互関係を追究して、各テスト工
程・作業で摘出されるバグ内容に基くソフトウェアの品
質評価方式を提供することにある。The literature regarding the contents of conventional bugs is (1) "Example of quality control in application program development" 81) Shin (Fujitsu) [3rd Symposium of Japan Federation of Science and Technology] P-al, t
:2) "R Planning and Measuring Program Implementation" Etsuchiremas (IBM)
IPLannitsg and Shermany 6° 1980 Page 10
ynatrbring programimpltm
antation J H, Rimata (IBM)
proceedings of Jμ 1980P, 1
0) As described in K, there is also a concept of goal setting centered on errors identified in the design process. However, it is assumed that the testing process and work will be categorized according to the design process and work, focusing on bugs that are found in the testing process (mainly due to bad programming rather than defective documentation). The purpose of the present invention is to set five criteria based on the highest proportion of bugs created in the corresponding design process, and to automatically evaluate quality using these criteria.[Object of the Invention] The purpose of the present invention is to We investigate the appropriate process/work division and their interrelationships in order to maintain and improve quality, and evaluate the software quality based on the bugs identified in each testing process/work, regarding the design process that incorporates and the testing process that removes bugs. The purpose is to provide a method.
コーディング完了時点でソフトウェアの品質を評価する
ことは現実的忙は難しく、それ以降のテスト工程でバグ
摘出方法の適正さを判断しながらバグの件数と内容から
品質評価していくことが現実的である。本発明はバグの
内容に関するものだが、ソフトウェアの作り方とテスト
方法の関係を追究し、品質面・効率面で最適なテストを
ねらいとし、合わせて品質評価の自動化を図るも めあ
る。It is difficult to evaluate the quality of software at the point when coding is completed; it is practical to evaluate the quality based on the number and content of bugs while determining the appropriateness of the bug extraction method in the subsequent testing process. be. This invention relates to the content of bugs, but it also investigates the relationship between how software is created and testing methods, aims at optimal testing in terms of quality and efficiency, and also aims to automate quality evaluation.
〔発明の実施例〕
以下、本発明の一実施例を第１〜第４図により説明する
。方法・手順により設計工程をＦＳ。[Embodiment of the Invention] An embodiment of the present invention will be described below with reference to FIGS. 1 to 4. FS of the design process using methods and procedures.
ＤＳ、Ｆ、Ｃの４つの工程に区分し、それらの工程に対
応したテスト工程としてＳＫ、ＳＤ、ＣＤ、ＪＩｙ）４
つの工程を設定する。設計工程が一般に全体から部分と
いう順で行なわれるのに対し、テスト工程は部分から全
体という順で行なわれることから、それぞれの実施順は
第１図に示すとおりとする。ある製品のテスト完了時点
に全摘出バグ数を、作込設計工程別に分類したものを第
１図の設計工程別の棒グラフとする。摘出テスト工程別
に分類したものを第１図のテスト工程別の棒グラフとす
れば、ＵＤ、ＣＤ、ＳＤ、ＳＫのいずれの工程において
も対応設計工程のバグの割合が最大なので１品質もテス
ト方法も一応問題ないと判定する。この判定はプログラ
ムにより自動的に行なうことができる。第２〜第４図は
それぞれＵＤ、ＣＤ、ＳＤ工程で対応設計工程以外のバ
グの割合が最大となっているので、品質又はテスト方法
に問題があると判定する。It is divided into four processes: DS, F, and C, and the test processes corresponding to these processes are SK, SD, CD, and JIy)4.
Set up two processes. Since the design process is generally performed from the whole to the parts, and the test process is performed from the parts to the whole, the order of implementation is as shown in FIG. The bar graph for each design process in FIG. 1 shows the total number of bugs extracted at the time of completion of testing for a certain product, categorized by manufacturing design process. If the classification by extraction test process is shown as a bar graph by test process in Figure 1, the proportion of bugs in the corresponding design process is the highest in any of the UD, CD, SD, and SK processes, so it is clear that both quality and test method are the same. It is determined that there is no problem. This determination can be made automatically by a program. In FIGS. 2 to 4, the proportion of bugs in processes other than the corresponding design process is highest in the UD, CD, and SD processes, respectively, so it is determined that there is a problem with the quality or the testing method.
なお、各テスト工程において対応設計工程以外のバグの
割合いも経験値から設定できれば（但し、品質の良い製
品の実績データの分析・検証が必要）、その割合い又は
割合いの順位を基準としてプログラムによりさらに精度
の高い評価を行なうことができる。In addition, if the proportion of bugs other than the corresponding design process in each test process can be set from empirical values (however, it is necessary to analyze and verify the performance data of high-quality products), then the program will be based on that proportion or the ranking of the proportion. This allows for even more accurate evaluation.
本実施例によればテスト工程の早い段階で品質又はテス
ト方法の問題を検知し、基準よりバグの多い設計工程の
見直しを行なう等の具体的な対策にも効果がある。According to this embodiment, problems in quality or testing methods can be detected at an early stage of the testing process, and specific countermeasures can be taken, such as reviewing design processes that have more bugs than the standard.
本発明によれば、コーディング完了後の机上テハッグも
含めデバッグ拳テストの早い［１９から自動的に品質評
価でき、評価結果が悪い場合はその原因となる設計工程
・作業を指摘できるので、ソフトウェアの定量的評価・
品質向上・効率向上の効果がある。According to the present invention, it is possible to automatically evaluate the quality of the debugging test, including the desk-based hand-hugging after the completion of coding. Quantitative evaluation/
It has the effect of improving quality and efficiency.
第１〜第４図は本発明の実施例の作業工程別冷ｌ必
副Ｉ 第５図 第４０
テズトエ第１→ プストエ丁Ｉ→
テストエｆｉ−−−。Figures 1 to 4 show the working process of the embodiment of the present invention in terms of cooling lubricant I. Figure 5.
Test fi---.
Claims (1)
ングまでとデバッグ・テストの２つに大きく分けるもの
において、各テスト工程・作業での摘出バグに占める作
込み設計工程・作業の割合いを目標値として経験値等に
より与え、各テスト工程・作業において実績値を与え、
その対応設計工程・作業での作込みバグについて当該テ
スト工程・作業の目標値との比較、他テスト工程・作業
での実績値との比較等により自動的に評価することを特
徴とするソフトウェアの品質評価方式。1. When the software development process is broadly divided into two parts: from consideration of specifications to coding, and debugging/testing, the target value is the ratio of the built-in design process/work to the bugs detected in each testing process/work. It is given based on experience values, etc., and actual values are given in each test process/work.
The software is characterized by automatically evaluating built-in bugs in the corresponding design process/work by comparing it with the target value of the relevant test process/work, comparing with the actual value of other test processes/work, etc. Quality evaluation method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP60144717A JPS626332A (en) | 1985-07-03 | 1985-07-03 | Evaluation system for quality of software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP60144717A JPS626332A (en) | 1985-07-03 | 1985-07-03 | Evaluation system for quality of software |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| JPS626332A true JPS626332A (en) | 1987-01-13 |
Family
ID=15368660
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| JP60144717A Pending JPS626332A (en) | 1985-07-03 | 1985-07-03 | Evaluation system for quality of software |
Country Status (1)
| Country | Link |
|---|---|
| JP (1) | JPS626332A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS63172122U (en) * | 1987-04-28 | 1988-11-09 |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS5858346B2 (en) * | 1982-03-11 | 1983-12-24 | 東川 哲郎 | Method for producing substituted benzamide compounds |
-
1985
- 1985-07-03 JP JP60144717A patent/JPS626332A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS5858346B2 (en) * | 1982-03-11 | 1983-12-24 | 東川 哲郎 | Method for producing substituted benzamide compounds |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS63172122U (en) * | 1987-04-28 | 1988-11-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110221983B (en) | Test method, test device, computer readable storage medium and computer equipment | |
| CN108491321B (en) | Method and device for determining test case range and storage medium | |
| CN110543420B (en) | A software testing method, system, terminal and storage medium | |
| US20180196742A1 (en) | System and method for end to end performance response time measurement based on graphic recognition | |
| CN109992511B (en) | Device and method for obtaining code test coverage rate | |
| CN115185752B (en) | Verification methods, verification apparatus, equipment, and storage media for processors. | |
| CN112527573A (en) | Interface testing method, device and storage medium | |
| JPS626332A (en) | Evaluation system for quality of software | |
| JPS6126112A (en) | System abnormality diagnosis method | |
| CN114816999B (en) | HIL test automatic execution method | |
| CN101901185A (en) | An Object-Oriented Program Defect Location Method Based on Class-Organized Execution Tracks | |
| CN115858354A (en) | Test coverage rate calculation method, system, terminal and storage medium | |
| CN114676061A (en) | An automatic firmware detection method based on knowledge graph | |
| CN111177014B (en) | Software automatic test method, system and storage medium | |
| CN115543786A (en) | Test application screening method, device, computer equipment and readable storage medium | |
| CN107402883A (en) | A kind of data test treating method and apparatus | |
| CN1402323A (en) | Embedded memory test platform device and test method thereof | |
| CN121387753B (en) | A test case screening method, apparatus, medium, product, and equipment. | |
| CN112597041A (en) | Cross-branch merging method, system, equipment and storage medium for code coverage rate | |
| CN118642949A (en) | A testing method and system based on automated regression test case tuning | |
| CN117591394A (en) | Automatic test system and method | |
| JPH0357034A (en) | Program testing system | |
| CN119336644A (en) | Software testing method, device, equipment, storage medium and computer program product | |
| CN121301203A (en) | A code coverage statistics method, apparatus, computer device, and storage medium | |
| CN118409912A (en) | Solid state drive testing method, device, equipment and computer readable storage medium |