JPH0619714A - Example base inference method - Google Patents

Example base inference method

Info

Publication number
JPH0619714A
JPH0619714A JP4176693A JP17669392A JPH0619714A JP H0619714 A JPH0619714 A JP H0619714A JP 4176693 A JP4176693 A JP 4176693A JP 17669392 A JP17669392 A JP 17669392A JP H0619714 A JPH0619714 A JP H0619714A
Authority
JP
Japan
Prior art keywords
case
model
corrected
cases
retrieval
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
Application number
JP4176693A
Other languages
Japanese (ja)
Inventor
Kayako Oomura
佳也子 大村
Toshihiko Watanabe
俊彦 渡辺
Shinya Shozaki
信也 庄崎
Kazuyoshi Maeoka
和義 前岡
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kobe Steel Ltd
Original Assignee
Kobe Steel Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Kobe Steel Ltd filed Critical Kobe Steel Ltd
Priority to JP4176693A priority Critical patent/JPH0619714A/en
Publication of JPH0619714A publication Critical patent/JPH0619714A/en
Pending legal-status Critical Current

Links

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

PURPOSE:To provide an example base inference method by which the number of retrieval examples is reduced and retrieval time is shortened through the use of a model example which does not include a mistake. CONSTITUTION:The example base inference method is to input the specification (a) of a problem (input of specification 1) at the time of solving the problem, to retrieve an example (b) which is most similar to the specification (a) among the plural examples (b), (d),... which are previously stored in an example base 2 in a prescribed priority 3 (retrieval of example 4), to alter the example (b) on a difference between the specification (a) and the example (b) based on an alteration rule 5 (correction of example 6), to output a correction plan (c) (output of correction plan 7), to add the model example obtained by extracting a success example from a corrected example to a storage at the time of adding the corrected example (addition of example 8). The number of retrieval examples is reduced by using the model example which does not include the mistake and retrieval time can be shortened with the constitution.

Description

【発明の詳細な説明】Detailed Description of the Invention

【0001】[0001]

【産業上の利用分野】本発明は事例ベース推論方法に係
り,詳しくは各種プラントの診断,設計,計画などに適
用可能な事例ベース推論方法に関するものである。
BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a case-based reasoning method, and more particularly to a case-based reasoning method applicable to diagnosis, design and planning of various plants.

【0002】[0002]

【従来の技術】事例ベース推論とは,過去の成功または
失敗の事例をもとに,問題に応じた修正を加えて効率よ
く解を得る周知の手法である。図5は従来の事例ベース
推論方法の一例における概略構成を示す説明図,図6は
従来の事例ベース推論方法による問題解決の手順を示す
フローチャートである。図5に示す如く,従来の推論方
法は主として以下の〔 〕内に示される各過程により構
成されている。この方法による問題解決に際しては,ま
ず問題の仕様aを入力する〔仕様の入力1〕。次に,こ
の仕様aと事例ベース2に予め記憶された複数の過去事
例b,d,…とを照合し,所定の優先順位3にて最も条
件が似ている事例bを検索する〔事例の検索4〕。そし
て,検索された過去事例bを基本にして仕様aと異なる
部分について,問題に固有の変更ルール5を用いて変更
を加える〔事例の補正6〕。このような手順で得られた
修正案cがシステム解であり出力される〔修正案の出力
7〕。この解は実際に適用して効果を確認するか,又は
シミュレーションなどで効果を確認することにより評価
してから,その結果(成功または失敗)とともに修正案
cを再び過去事例bとして事例ベース2に記憶する〔事
例の追加8〕。この方法による問題解決の手順を図6に
示す。即ち,図中の各ステップS1,S2,…の順に上
記各過程〔仕様の入力1〕,〔事例の検索4〕,〔事例
の補正6〕,〔修正案の出力7〕,〔事例の追加8〕が
実行され,問題解決がなされる。このような従来の事例
ベース推論方法では,過去事例を使っているために, (1)推論時間が早い (2)知識獲得が容易である (3)適用前に成功失敗の目処が付く などの利点がある。従って,従来の方法は,各種プラン
トの診断,設計,計画などに広く適用されていた。
2. Description of the Related Art Case-based reasoning is a well-known technique for efficiently solving a problem based on past successes or failures and making corrections according to the problem. FIG. 5 is an explanatory diagram showing a schematic configuration in an example of a conventional case-based reasoning method, and FIG. 6 is a flowchart showing a problem solving procedure by the conventional case-based reasoning method. As shown in FIG. 5, the conventional inference method is mainly composed of the steps shown in the following []. In solving a problem by this method, first, the specification a of the problem is input [specification input 1]. Next, the specification a is collated with a plurality of past cases b, d, ... Stored in the case base 2 in advance, and a case b having the most similar condition is searched in a predetermined priority order 3 [case Search 4]. Then, based on the retrieved past case b, the part different from the specification a is modified using the modification rule 5 unique to the problem [case correction 6]. The correction plan c obtained by such a procedure is a system solution and is output [correction plan output 7]. This solution is actually applied to confirm the effect, or evaluated by confirming the effect by a simulation or the like, and then, together with the result (success or failure), the correction plan c is again set as the past case b in the case base 2 Remember [Addition 8]. The procedure for problem solving by this method is shown in FIG. That is, the steps [Specification input 1], [Case search 4], [Case correction 6], [Correction output 7], [Case addition] in the order of steps S1, S2, ... 8] is executed and the problem is solved. In such a conventional case-based reasoning method, since past cases are used, (1) reasoning time is fast (2) knowledge acquisition is easy (3) there is a prospect of success or failure before application. There are advantages. Therefore, the conventional method has been widely applied to diagnosis, design, planning, etc. of various plants.

【0003】[0003]

【発明が解決しようとする課題】上記したような従来の
事例ベース推論方法では,事例ベース2に記憶される過
去事例bの質と量とが性能を左右するため,次のような
問題があった。 (1)実際の事例には間違いが含まれている可能性が高
いが,その間違いが認識されていない場合がある。 (2)仕様は年々厳しくなる傾向にあるため,何年も前
の事例では現状に合わない場合がある。 (3)事例追加を毎回行なうと膨大なメモリが必要にな
るが,処理数が多くなればなる程重複事例が推論速度を
遅くする。本発明はこのような従来の技術における課題
を解決するために,事例ベース推論方法を改良し,間違
いを含まないモデル事例を用いることにより検索事例数
を少なくして検索時間を短縮し得る事例ベース推論方法
の提供を目的とするものである。
The conventional case-based reasoning method as described above has the following problems because the quality and quantity of the past case b stored in the case base 2 influence the performance. It was (1) There is a high possibility that an actual case includes a mistake, but there are cases where the mistake is not recognized. (2) The specifications tend to be stricter year by year, so in the case of many years ago, the current situation may not be met. (3) A huge memory is required if the case is added every time, but the larger the number of processes, the slower the inference speed of the duplicate case. In order to solve the problems in the conventional technique, the present invention improves the case-based reasoning method and reduces the number of search cases by using a model case that does not include an error, thereby reducing the search time. The purpose is to provide an inference method.

【0004】[0004]

【課題を解決するための手段】上記目的を達成するため
に本発明は,問題解決に際し,予め記憶された複数の事
例の内上記問題に最も似ている事例を検索し,上記問題
と上記事例との異なる部分について所定のルールに基づ
いて該事例を補正の上出力し,上記補正後の事例を記憶
に追加する事例ベース推論方法において,上記補正後の
事例から成功事例を抽出したモデル事例を上記記憶に追
加することを特徴とする事例ベース推論方法として構成
されている。
In order to achieve the above object, the present invention, when solving a problem, searches for a case most similar to the above problem from among a plurality of cases stored in advance, and searches for the above problem and the above case. In a case-based reasoning method in which the case is corrected and output based on a predetermined rule with respect to a part different from the above, and the corrected case is added to the memory, a model case in which a successful case is extracted from the corrected case is It is configured as a case-based reasoning method characterized by adding to the above memory.

【0005】[0005]

【作用】本発明によれば,問題解決に際し,予め記憶さ
れた複数の事例の内上記問題に最も似ている事例を検索
し,上記問題と上記事例との異なる部分について所定の
ルールに基づいて該事例を補正の上出力し,上記補正後
の事例を上記記憶に追加する時,上記補正後の事例から
成功事例を抽出したモデル事例が上記記憶に追加され
る。このように間違いを含まないモデル事例を用いるこ
とにより検索事例数を少なくして検索時間を短縮するこ
とができる。
According to the present invention, when solving a problem, a case most similar to the above-mentioned problem is retrieved from a plurality of pre-stored cases, and a different rule between the above-mentioned problem and the above-mentioned case is searched based on a predetermined rule. When the corrected case is output and the corrected case is added to the storage, a model case obtained by extracting a successful case from the corrected case is added to the storage. By using the model case that does not include an error, the number of search cases can be reduced and the search time can be shortened.

【0006】[0006]

【実施例】以下,添付図面を参照して本発明を具体化し
た実施例につき説明し,本発明の理解に供する。尚,以
下の実施例は,本発明を具体化した一例であって,本発
明の技術的範囲を限定する性格のものではない。ここに
図1は本発明の一実施例に係る事例ベース推論方法の概
略構成を示す説明図,図2は実際の注文事例を示す一覧
表,図3はモデル事例を示す一覧表,図4は本実施例の
事例ベース推論方法による設計例を示す各過程での入出
力フォーマットを示す。また前記図5に示した従来の事
例ベース推論方法の概略構成を示す説明図と共通する要
素には同一符号を使用する。図1に示す如く,本実施例
に係る事例ベース推論方法は主として以下の〔 〕内に
示される各過程により構成されている。この方法による
問題解決に際してはまず問題の仕様を入力し〔仕様の入
力1〕,次にこの仕様aと事例ベース2に予め記憶され
た複数の事例b,d,…とを照合し,所定の優先順位3
にて最も条件が似ている事例bを検索し〔事例の検索
4〕,検索された事例bを基本にして仕様aと異なる部
分について変更ルール5を用いて変更を加え〔事例の補
正6〕,こうして得られた修正案cを出力し〔修正案の
出力7〕,評価してから修正案cを事例ベース2に記憶
する〔事例の追加8〕。これらの過程はいずれも従来例
と同様であり,この方法による問題解決の手順も従来例
と同様である(図6参照)。しかし,本実施例では事例
ベース2に記憶される事例bに過去事例を直接使わずモ
デル事例を参照している点と,これに関係して失敗事例
をモデル事例として記憶せず成功事例のみを抽出して記
憶する点で従来例と異なる。ただし,実際には失敗事例
を全く除外するのではなく,必要に応じて修正を行った
上でモデル事例として追加しても良い。本実施例の推論
方法を,厚板の品質設計に適用した例について以下に説
明する。厚板とは,6mm以上の厚みの鋼板のことであ
り,船舶・橋梁・タンクなどの構造部材に使われるもの
である。又厚板の品質設計とは,設計仕様でサイズ・用
途・強度・製品の加工方法(溶接,曲げ,...)など
が指定されたとき,それらに応じた化学成分・加工方法
・検査基準などを決定することである。この品質設計
は,継続のオーダについては従来よりすべて自動設計さ
れていたが,非継続のオーダや特別注文のあったオーダ
については自動化は難しく,又この設計業務は鋼板製造
工程のすべてに影響を及ぼすため熱練スタッフが設計を
担当していたものである。
Embodiments of the present invention will be described below with reference to the accompanying drawings for the understanding of the present invention. The following embodiments are examples of embodying the present invention and are not intended to limit the technical scope of the present invention. FIG. 1 is an explanatory diagram showing a schematic configuration of a case-based reasoning method according to an embodiment of the present invention, FIG. 2 is a list showing actual order cases, FIG. 3 is a list showing model cases, and FIG. The input / output format in each process showing the design example by the case-based reasoning method of the present embodiment is shown. Further, the same symbols are used for the elements common to the explanatory view showing the schematic configuration of the conventional case-based reasoning method shown in FIG. As shown in FIG. 1, the case-based reasoning method according to this embodiment is mainly configured by the steps shown in the following []. When solving a problem by this method, first, the specification of the problem is input [specification input 1], and then this specification a is collated with a plurality of cases b, d, ... Priority 3
The case b having the most similar conditions is searched [case search 4], and the changed part 5 is changed based on the searched case b using the change rule 5 [correction of case 6]. The correction plan c thus obtained is output [correction plan output 7] and evaluated, and then the correction plan c is stored in the case base 2 [addition of case 8]. All of these processes are the same as in the conventional example, and the procedure for problem solving by this method is also the same as in the conventional example (see FIG. 6). However, in the present embodiment, the case b stored in the case base 2 is referred to the model case without directly using the past case, and in connection with this, the failure case is not stored as the model case and only the successful case is stored. It is different from the conventional example in that it is extracted and stored. However, actually, the failure case may not be excluded at all, but may be added as a model case after being corrected as necessary. An example in which the inference method of this embodiment is applied to the quality design of thick plates will be described below. Thick plates are steel plates with a thickness of 6 mm or more, and are used for structural members such as ships, bridges, and tanks. In addition, quality design of thick plate means the chemical composition, processing method, and inspection standard corresponding to the size, application, strength, and product processing method (welding, bending, ...) Designated in the design specifications. And so on. This quality design has always been automatically designed for continuous orders, but it is difficult to automate it for discontinued orders and special orders, and this design work affects all of the steel plate manufacturing process. The heat training staff was in charge of the design in order to exert the influence.

【0007】まず,モデル事例の作成過程について以下
に説明する。一般に,厚板の品質設計の注文は図2のよ
うな入出力フォーマットで表わすことができる。ここ
で,用途加工区分とは,よく似た用途ごとに加工方法を
まとめたものであり,例えばK00の如く,パイプ・水
道管・構造用管などの用途について加工方法などを決め
ている。この内水道管については特に曲げ加工が多く,
また曲げ部分に亀裂が発生すると水洩れの原因となるた
め構造用管などに比べて品質を十分に保証する必要があ
る。そこで,用途が水道管である場合に限り,特別な設
計(靱性に関係する成分の強化・検査基準の強化)を加
えている。この実際の注文事例に基づいて作成したモデ
ル事例を図3に示す。モデル事例では,出力に影響を及
ぼさない入力項目については削除している。また,モデ
ル事例では特定の材料規格名や板厚に関係して決まる品
質設計No.や成分の数値に関しては,一般的に定義を
している(即ちモデル化している)。例えば,モデル事
例内の(ランクアップ:1)や(最高品質)が該当す
る。ここで,(ランクアップ:1)とは,標準で定めら
れている成分値よりランクを1段階上げるという意味で
ある。これらの具体的値は,変更ルール5により詳細に
決定される。このモデル事例を用いて設計した例を図1
における各過程の順に示すと図4のようになる。即ち,
図1における〔仕様の入力1〕で入力される仕様aは図
4の(1)のフォーマットで与えられる。同様に〔事例
の検索4〕で検索された事例bは図4の(2)のフォー
マットで,〔事例の補正6〕で変更途中の事例b´は図
4の(3)のフォーマットで,〔修正案の出力7〕で出
力される修正案cは図4の(4)のフォーマットでそれ
ぞれ与えられる。そして,修正案cの内,成功事例(又
は修正された失敗事例)が抽出され,モデル化されて事
例ベース2に記憶される。従って,〔事例の追加8〕で
事例ベース2に追加される成功事例(又は修正された失
敗事例)のフォーマットは図4の(2)と同様のモデル
事例となる。但し,事例ベース2に追加されるモデル事
例と同一の事例が先に記憶されている場合は,重複して
記憶されず,新規の事例のみが記憶される。以上のよう
に,本実施例では間違いを含まないモデル事例を定義
し,これを事例検索に用いて基本設計を行い,変更ルー
ルにより詳細を設計する。これにより,事例の重複がな
くなり,検索事例数は少なくなるため検索時間を短縮す
ることができる。またモデル事例を使っているため,事
例検索時に矛盾した事例の処理を考慮する必要がないう
え,間違いが含まれていないので導出解の正当性が保証
される。その結果,問題を確実にかつ迅速に解決するこ
とができる。
First, the process of creating a model case will be described below. Generally, an order for a quality design of a thick plate can be expressed by an input / output format as shown in FIG. Here, the application processing classification is a collection of processing methods for each similar application. For example, the processing method is determined for applications such as pipes, water pipes, and structural pipes like K00. There are many bending processes for this water supply pipe,
Also, if cracks occur in the bent part, it may cause water leakage, so it is necessary to sufficiently guarantee the quality compared with structural pipes. Therefore, a special design (strengthening of components related to toughness, strengthening of inspection standards) is added only when the application is a water pipe. FIG. 3 shows a model case created based on this actual order case. In the model case, input items that do not affect the output are deleted. Moreover, in the model case, the quality design No. determined according to the specific material standard name and the plate thickness. The numerical values of and components are generally defined (that is, modeled). For example, (rank up: 1) or (highest quality) in the model case corresponds to this. Here, (rank up: 1) means that the rank is raised by one step from the component value defined by the standard. These specific values are determined in detail by the modification rule 5. An example of designing using this model case
FIG. 4 shows the order of each step in FIG. That is,
The specification a input in [Specification input 1] in FIG. 1 is given in the format of (1) in FIG. Similarly, the case b searched in [Case search 4] is in the format of (2) in FIG. 4, and the case b ′ in the middle of change in [Correction of case 6] is in the format of (3) in FIG. The amendment plan c output by the amendment plan output 7] is given in the format of (4) in FIG. Then, the success case (or the corrected failure case) is extracted from the correction plan c, modeled and stored in the case base 2. Therefore, the format of the successful case (or corrected failed case) added to the case base 2 in [Add Case 8] is the same model case as (2) in FIG. However, when the same case as the model case added to the case base 2 is stored first, it is not stored redundantly and only a new case is stored. As described above, in the present embodiment, a model case that does not include an error is defined, this is used for case search to perform a basic design, and details are designed by a change rule. As a result, duplication of cases is eliminated and the number of search cases is reduced, so that the search time can be shortened. In addition, since model cases are used, it is not necessary to consider the processing of inconsistent cases when searching for cases, and since the errors are not included, the validity of the derived solution is guaranteed. As a result, the problem can be solved reliably and promptly.

【0008】[0008]

【発明の効果】本発明に係る事例ベース推論方法は,上
記したように構成されているため,事例の重複がなくな
り,検索事例数は少なくなるため検索時間を短縮するこ
とができる。またモデル事例を使っているため,事例検
索時に矛盾した事例の処理を考慮する必要がないうえ,
間違いが含まれていないので導出解の正当性が保証され
る。その結果,問題を確実にかつ迅速に解決することが
できる。
Since the case-based inference method according to the present invention is configured as described above, the duplication of cases is eliminated and the number of search cases is reduced, so that the search time can be shortened. Moreover, since model cases are used, it is not necessary to consider the processing of inconsistent cases when searching for cases, and
Since the error is not included, the correctness of the derived solution is guaranteed. As a result, the problem can be solved reliably and promptly.

【図面の簡単な説明】[Brief description of drawings]

【図1】 本発明の一実施例に係る事例ベース推論方法
の概略構成を示す説明図。
FIG. 1 is an explanatory diagram showing a schematic configuration of a case-based reasoning method according to an embodiment of the present invention.

【図2】 実際の注文事例を示す一覧表。FIG. 2 is a table showing actual order examples.

【図3】 モデル事例を示す一覧表。FIG. 3 is a list showing model cases.

【図4】 本実施例の事例ベース推論方法による設計例
を示す各過程での入出力フォーマット。
FIG. 4 is an input / output format in each process showing a design example by the case-based reasoning method of the present embodiment.

【図5】 従来の事例ベース推論方法の一例における概
略構成を示す説明図。
FIG. 5 is an explanatory diagram showing a schematic configuration of an example of a conventional case-based reasoning method.

【図6】 従来の事例ベース推論方法による問題解決の
手順を示すフローチャート。
FIG. 6 is a flowchart showing a procedure for problem solving by a conventional case-based reasoning method.

【符号の説明】[Explanation of symbols]

1…仕様の入力 2…事例ベース 3…優先順位 4…事例の検索 5…変更ルール 6…事例の補正 7…修正案の出力 8…事例の追加 1 ... Specification input 2 ... Case base 3 ... Priority 4 ... Case search 5 ... Change rule 6 ... Case correction 7 ... Correction output 8 ... Case addition

───────────────────────────────────────────────────── フロントページの続き (72)発明者 前岡 和義 加古川市金沢町1番地 株式会社神戸製鋼 所加古川製鉄所内 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Kazuyoshi Maeoka 1 Kanazawa-machi, Kakogawa City Kobe Steel Works, Ltd. Kakogawa Works

Claims (1)

【特許請求の範囲】[Claims] 【請求項1】 問題解決に際し,予め記憶された複数の
事例の内上記問題に最も似ている事例を検索し,上記問
題と上記事例との異なる部分について所定のルールに基
づいて該事例を補正の上出力し,上記補正後の事例を記
憶に追加する事例ベース推論方法において,上記補正後
の事例から成功事例を抽出したモデル事例を上記記憶に
追加することを特徴とする事例ベース推論方法。
1. When solving a problem, a case most similar to the above-mentioned problem is searched out of a plurality of cases stored in advance, and the case is corrected based on a predetermined rule with respect to a part different from the above-mentioned problem. In the case-based reasoning method of outputting the above, and adding the corrected case to the memory, the model-based reasoning method is characterized in that a model case in which a successful case is extracted from the corrected case is added to the memory.
JP4176693A 1992-07-03 1992-07-03 Example base inference method Pending JPH0619714A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP4176693A JPH0619714A (en) 1992-07-03 1992-07-03 Example base inference method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP4176693A JPH0619714A (en) 1992-07-03 1992-07-03 Example base inference method

Publications (1)

Publication Number Publication Date
JPH0619714A true JPH0619714A (en) 1994-01-28

Family

ID=16018089

Family Applications (1)

Application Number Title Priority Date Filing Date
JP4176693A Pending JPH0619714A (en) 1992-07-03 1992-07-03 Example base inference method

Country Status (1)

Country Link
JP (1) JPH0619714A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08194618A (en) * 1995-01-18 1996-07-30 Kobe Steel Ltd Case base inferring device
JP2003081598A (en) * 2001-09-14 2003-03-19 Toyoda Mach Works Ltd Power assist device

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0488530A (en) * 1990-07-31 1992-03-23 Mitsubishi Electric Corp Concept design job supporting device

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0488530A (en) * 1990-07-31 1992-03-23 Mitsubishi Electric Corp Concept design job supporting device

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08194618A (en) * 1995-01-18 1996-07-30 Kobe Steel Ltd Case base inferring device
JP2003081598A (en) * 2001-09-14 2003-03-19 Toyoda Mach Works Ltd Power assist device

Similar Documents

Publication Publication Date Title
CN101981575B (en) Method and apparatus for copying objects in an object-oriented environment using a multiple-transaction technique
JP2783729B2 (en) Maintenance support device
CN112231133A (en) Data restoration processing method and device and electronic equipment
CN114357961A (en) Project feasibility research report generation method, device, equipment and storage medium
JPH0619714A (en) Example base inference method
JP2005148783A (en) Process simulation system
CN115599908A (en) Method and system for labeling unstructured data document
JPH0397030A (en) Program correcting system
JP2003091431A (en) System, method and program for selecting and executing test scenario
JP2723314B2 (en) Search system
JPH10171875A (en) Method for automatically calculating price for whole process by inputting data of preceding and succeeding processes
JPH08194618A (en) Case base inferring device
JPH0546378A (en) Correction processing method for program
JP2595815B2 (en) Program correction amount judgment processing device
CN112685891B (en) Method for establishing regional augmentation high-technology enterprise prediction model
CN118012831A (en) Method and system for repairing damage of Trados file specific tag
CN112905866B (en) Historical data tracing and crawling method and terminal without manual participation
JP3085365B2 (en) Process procedure automatic adjustment method, process procedure automatic adjustment system, and recording medium recording process procedure automatic adjustment program
Stufflebeam Coping with the point of entry problem in evaluating projects
CN116841909A (en) Template-based universal automatic data inspection method and test case module
JPS60136836A (en) Patch post-processing method of program
CN115809087A (en) Version updating method, version updating device, version updating equipment and storage medium
CN113722555A (en) Data annotation item quality inspection method and system
CN113468155A (en) Problem data processing method and device
Visaggio Relationships between documentation and maintenance activities

Legal Events

Date Code Title Description
FPAY Renewal fee payment (prs date is renewal date of database)

Year of fee payment: 9

Free format text: PAYMENT UNTIL: 20070911

FPAY Renewal fee payment (prs date is renewal date of database)

Free format text: PAYMENT UNTIL: 20080911

Year of fee payment: 10

FPAY Renewal fee payment (prs date is renewal date of database)

Year of fee payment: 10

Free format text: PAYMENT UNTIL: 20080911

FPAY Renewal fee payment (prs date is renewal date of database)

Free format text: PAYMENT UNTIL: 20090911

Year of fee payment: 11

LAPS Cancellation because of no payment of annual fees