CN112581094B - Method for automatically retrieving and extracting reliability requirement - Google Patents

Method for automatically retrieving and extracting reliability requirement Download PDF

Info

Publication number
CN112581094B
CN112581094B CN202011540108.1A CN202011540108A CN112581094B CN 112581094 B CN112581094 B CN 112581094B CN 202011540108 A CN202011540108 A CN 202011540108A CN 112581094 B CN112581094 B CN 112581094B
Authority
CN
China
Prior art keywords
reliability
document
wiki
requirement
analysis package
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.)
Active
Application number
CN202011540108.1A
Other languages
Chinese (zh)
Other versions
CN112581094A (en
Inventor
李梅
刘晓
王蓓
张辉
郑京生
刘庆华
孔维杰
孙博龙
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.)
Casco Signal Ltd
Original Assignee
Casco Signal 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 Casco Signal Ltd filed Critical Casco Signal Ltd
Priority to CN202011540108.1A priority Critical patent/CN112581094B/en
Publication of CN112581094A publication Critical patent/CN112581094A/en
Application granted granted Critical
Publication of CN112581094B publication Critical patent/CN112581094B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/33—Querying
    • G06F16/335—Filtering based on additional data, e.g. user or group profiles
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Computational Linguistics (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Artificial Intelligence (AREA)
  • Databases & Information Systems (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention relates to a method for automatically retrieving and extracting reliability requirements, which realizes the automatic retrieval and extraction of the reliability of all required or wanted reliability requirement items through wiki, generates a reliability evaluation document on line, realizes the change management requirements of the reliability requirements, and can quickly provide effective evidence to prove that the reliability requirements meet the design requirements. Compared with the prior art, the method has the advantages of greatly shortening the time for evaluating the reliability requirement, avoiding the occurrence of missing detection and error detection and the like.

Description

Method for automatically retrieving and extracting reliability requirement
Technical Field
The invention relates to the field of automatic evaluation of system reliability, in particular to a method for automatically retrieving and extracting reliability requirements.
Background
The evaluation of the reliability requirements requires the provision of clear evidence to demonstrate that the reliability requirements are met by the design requirements. However, because of numerous projects, huge reliability requirements and short development period, the evidence materials formed by offline retrieval, copying and pasting in a purely manual mode are very easy to have the problems of missing retrieval or wrong input of retrieval words; secondly, the purely manual online operation is time-consuming, expensive and low in economic benefit.
Therefore, how to overcome the defects of long time consumption, high cost, low economic benefit, missed detection, false detection and the like existing in the pure manual on-line operation in the prior art becomes a technical problem to be solved.
Disclosure of Invention
The present invention is directed to a method for automatically retrieving and extracting reliability requirements, which overcomes the above-mentioned drawbacks of the prior art.
The purpose of the invention can be realized by the following technical scheme:
according to one aspect of the invention, a method for automatically retrieving and extracting reliability requirements is provided, the method realizes automatic retrieval and extraction of all required or wanted reliability requirement item reliabilities through wiki (wiki), generates a reliability evaluation document on line, realizes change management requirements of the reliability requirements, and can quickly provide effective evidence to prove that the reliability requirements meet design requirements.
As a preferred technical scheme, the method specifically comprises the following steps:
step S1, the state flow of the reliability distribution document, the reliability requirement document, the system design and system requirement document containing the reliability requirement is converted to be verified;
s2, establishing a reliability analysis package, adding the document in the S1 into the analysis package, and editing a corresponding baseline version;
step S3, copying the ID number of the reliability analysis package;
step S4, opening the reliability evaluation document, and adding a wiki table at the corresponding position;
step S5, opening the Wiki table, and pasting the ID to the Zbaseline position in the script;
and step S6, returning to the reliability evaluation document, and clicking to save, so that the reliability requirement label and the content in the step S1 can be automatically displayed in the reliability evaluation document.
Preferably, in step S2, if the next baseline version does not need the reliability requirement document extracted automatically, the reliability requirement document is deleted from the reliability analysis package, or the document version containing the reliability requirement in the reliability analysis package is updated according to the change of the baseline.
As a preferred technical solution, the step S2 of establishing the reliability analysis package specifically includes:
step S21, determining the document state containing the reliability requirement;
step S22, opening a newly-built item of the reliability analysis package under the baseline;
step S23, adding documents with reliability requirements, wherein the reliability analysis package is established with the position of the added documents, and the documents of the step S21 need to be added;
step S24, judging whether the documents under the baseline are completely added, if yes, executing step S25, and if not, returning to step S23;
step S25, selecting the document version number of the reliability requirement under the corresponding baseline, and determining the evaluated version of the document added in the step S23;
step S26, judging whether the version number under the baseline is correct, if so, executing step S27, and if not, returning to step S25;
step S27, saving and submitting, wherein the established reliability requirement analysis package is saved and submitted to generate the ID number of the analysis package;
in step S28, the ID number of the reliability analysis package is copied.
As a preferred technical solution, the automatic search and extraction of the ID number and the reliability requirement label of the analysis package in step S27 are in a one-to-one correspondence relationship.
As a preferred technical solution, the steps S4 and S5 specifically include:
step S31, setting the reliability evaluation document state as writing, and only writing the state can edit wiki and document;
step S32, inserting wiki macro and mark in corresponding position;
step S33, clicking to modify wiki content;
step S34, pasting the ID of the reliability analysis package at the Zbaseline position of the script;
step S35, click to save in the reliability evaluation document;
step S36, clicking the reliability mark to edit the contents of the columns in the wiki table except the contents of the other columns after automatic retrieval and extraction;
step S37, click to save, go to step S38, click to submit, go to step S40;
step S38, the wiki content can be edited;
step S39, clicking to submit, and going to step S40;
step S40, version locking.
As a preferred technical solution, the step S32 specifically includes: a wiki is inserted at the location of the reliability evaluation result and the corresponding macro script is copied into the blank wiki.
As a preferred technical solution, the step S33 specifically includes: and right clicking the mark of the wiki, clicking the modification, and entering the wiki script.
As a preferred technical solution, the version can be changed, and the change management process specifically includes:
step S41, establishing a reliability analysis packet to obtain the ID of the analysis packet;
step S42, editing and submitting the wiki list;
step S43, editing the reliability assessment document and submitting V1.0.0 version;
step S44, changing the reliability evaluation document state into writing;
step S45, newly establishing a reliability analysis package, wherein the ID obtained in the step S41 is different from that obtained in the step S41;
step S46, editing and submitting the wiki table, wherein the content of the wiki table is different from that of the wiki table in the step S42;
step S47, edit reliability assessment document and submit V1.1.0;
step S48, comparing the wiki list under the two reliability analysis packages ID with the document content;
in step S49, the difference is the content of V1.1.0 change at V1.0.0, and change management is realized.
As an optimal technical scheme, the method can check reliability evaluation results of different historical versions on line and generate an on-line reliability evaluation document.
Compared with the prior art, the invention has the following advantages:
1) the invention can automatically identify, extract and automatically fill the reliability requirement to be retrieved to the corresponding position of the appointed document, thereby greatly shortening the time for evaluating the reliability requirement;
2) the method can set a certain classification criterion, automatically search all the reliability requirements, quickly provide clear evidence to prove that the reliability requirements meet the design requirements, and overcome the problems of search omission and wrong search in the pure manual offline operation in the prior art;
3) the method can quickly and automatically retrieve and extract the label-level content with the reliability requirement, and solves the problems of long time consumption, high cost and low economic benefit of the existing pure manual operation;
4) the invention can automatically start to search the updated reliability requirement according to the change of the baseline or the change of the requirement, and can realize the requirement of change management;
5) the reliability evaluation method and the reliability evaluation system can check the reliability evaluation results of different historical versions on line, generate an on-line reliability evaluation document, and effectively improve the reliability requirement evaluation efficiency.
Drawings
FIG. 1 is a flow chart of the reliability analysis package setup of the present invention;
FIG. 2 is a flow chart of wiki real-time extraction according to the present invention;
FIG. 3 is a flow chart of a version change management implementation of the present invention;
FIG. 4 is a general flow chart of the reliability requirement automatic retrieval and extraction of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, shall fall within the protection scope of the present invention.
The invention overcomes the defects of long time consumption, high cost, low economic benefit, missing detection, wrong detection and the like of pure manual online operation. The invention provides a method for automatically retrieving and extracting reliability requirements, which adopts the modes of automatic identification, retrieval and extraction, realizes the automatic retrieval and extraction of the reliability of all required or wanted reliability requirement items through wiki, generates a reliability evaluation document on line, realizes the change management requirements of the reliability requirements, can quickly provide effective evidence to prove that the reliability requirements meet the design requirements, effectively improves the reliability requirement evaluation efficiency and has a certain degree of engineering practical value.
Referring to fig. 1-4, a technical solution of the present invention is described, first, referring to fig. 4, a general flow of a reliability requirement automatic retrieval and extraction method is described, and on this basis, referring to fig. 1-3, a flow of establishing a reliability analysis package, a wiki real-time extraction flow, and a flow of implementing version change management according to the present invention are described.
Referring first to fig. 1, a reliability analysis package establishing method according to the present invention is described, including the steps of:
step 501, determining a document state containing a reliability requirement, wherein the document state is change management of a baseline, namely a reliability requirement label needing to be included in a reliability evaluation range is verified;
step 502, opening a new item of the reliability analysis package under the baseline, namely, the establishment position of the reliability analysis package is under the baseline;
step 503, adding a document containing reliability requirements, wherein the position of the added document exists in the establishment of the reliability analysis package, and the document in the step 501 needs to be added;
step 504, judge whether the file under this baseline adds totally, if not totally, need to return to step 503;
step 505, selecting a document version number of the reliability requirement under a corresponding baseline, namely determining an evaluated version of the document added in the step 503;
step 506, judging whether the version number under the baseline is correct, if not, returning to step 505;
step 507, storing and submitting, wherein the established reliability requirement analysis package is stored and submitted, so that the ID number of the analysis package can be generated;
step 508, duplicate this reliability analysis ID number of the packet, because the automatic search and drawing of the reliability requirement label are the one-to-one corresponding relation with ID number of the analysis packet, so need duplicate, avoid the manual input;
referring first to fig. 2, a wiki real-time extraction method of the present invention is described, comprising the steps of:
step 509, setting the reliability evaluation document state as writing, wherein wiki and document can be edited only in writing state;
step 510, inserting wiki macros and marks at corresponding positions, generally inserting wiki at the position of the reliability evaluation result, and copying corresponding macro scripts to blank wiki;
step 511, clicking to modify wiki content, right-clicking the mark of wiki, clicking to modify and entering wiki script;
step 512, pasting the ID of the reliability analysis packet at the Zbaseline position of the script;
step 513, clicking to save in the reliability evaluation document, after inserting wiki macro, the reliability requirement will not be directly automatically retrieved and the result will not be displayed, and the document must be clicked to save;
step 514, clicking the reliability mark to edit contents of other columns in the wiki table except for the contents after automatic retrieval and extraction, wherein the evaluation of the reliability requirement has the columns of evidence, conclusion and the like besides the ID and the contents of the requirement, and the two columns of the ID and the contents of the requirement are automatically retrieved and extracted without editing and only other columns are edited;
step 515, saving, where there is a save and submit button after opening wiki, if the save is clicked, wiki list can be edited, if the save is not clicked, the submit is clicked, then go to step 518;
step 516, wiki content can be edited, which can be realized as long as the wiki content is submitted without clicking;
step 517, submitting, wherein the submitting is that a saving and submitting button is arranged after the wiki is opened, if the submitting is clicked, the wiki list can not be edited, then the step 518 is executed;
and 518, locking the version to realize change management, wherein if the wiki table content is not required to be edited any more, the version can be locked after clicking and submitting, and the version can be opened again and can not be edited.
Referring first to fig. 3, a version change management implementation flow of the present invention is described, which includes the following steps:
step 519, establishing a reliability analysis packet, which is consistent with the flow in fig. 1, in order to obtain an ID of the analysis packet;
step 520, edit and submit the wiki table, here consistent with the method of FIG. 2;
step 521, editing the reliability evaluation document and submitting V1.0.0 versions, generally going through a release process after the reliability evaluation document is submitted, and locking the content of the basic line;
step 522, changing the reliability evaluation document state into the writing state, and only in the writing state, editing the document and the wiki table content;
step 523, newly establishing a reliability analysis package, wherein the reliability analysis package is consistent with the method of the step 519, and the difference is that the ID is different from that of the step 519;
step 524, editing and submitting the wiki table, wherein the content of the required wiki table is changed and has difference with the content of the wiki table in the step 520, thereby facilitating the comparison of versions;
step 525, editing reliability assessment documents and submitting V1.1.0, consistent with the operation method of step 521;
step 526, comparing the contents of the two IDs of the same document, namely the wiki table and the document contents under the IDs of the two reliability analysis packages;
step 527, the difference is that the content changed in step V1.0.0 in V1.1.0, so as to realize change management;
referring first to fig. 4, a general flow chart for automatic retrieval and extraction of reliability requirements of the present invention is described, comprising the following steps:
step 528, the analyzed reliability document, here, the change management of the baseline, is confirmed, that is, the reliability requirement label to be included in the reliability evaluation range is necessarily verified, and the range needs to be determined;
step 529, determining the analyzed version, which is generally the latest version, but some scenes need to add other document new versions to the historical version, so that confirmation is needed;
step 530, establishing a reliability analysis package, as in fig. 1;
step 531, judging whether the documents are complete, if not, returning to step 528;
step 532, judging whether the version is correct or not, if not, returning to the step 529;
step 533, submitting the reliability analysis package, and automatically generating the ID of the analysis package only if submitting the reliability analysis package;
step 534, copying the reliability analysis packet ID, because the automatic retrieval and extraction of the reliability requirement label are in one-to-one correspondence with the ID number of the analysis packet, so that copying is required and manual input is avoided;
step 535, inserting a wiki macro and a mark in the reliability evaluation document, generally inserting a wiki in the position of the reliability evaluation result, and copying the corresponding macro script into a blank wiki;
step 536, pasting a reliability analysis package ID at the position of the wiki script ZBaseline;
537, clicking and saving the reliability evaluation document, inserting wiki macros, and then realizing the automatic retrieval and extraction result of the reliability requirement without directly displaying the reliability requirement, and only clicking and saving the document;
step 538, editing the contents of other columns in the wiki table except for the contents after automatic retrieval and extraction, wherein the evaluation of the reliability requirement has the columns of evidences, conclusions and the like besides the ID and the contents of the requirement, and the two columns of the ID and the contents of the requirement are automatically retrieved and extracted without editing and only the other columns are edited;
539, storing/submitting, wherein the wiki list can be stored and submitted after being edited; the file can be edited after being stored and can not be edited after being submitted;
and 540, editing/storing/submitting the reliability evaluation document, wherein after wiki submission, the document can be edited, stored, submitted and edited, and after submission, the document is transferred to review and release, and the like, so that version change management is realized.
While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (9)

1. The method is characterized in that the method realizes automatic retrieval and extraction of the reliability of all required or wanted reliability requirement items through wiki, generates a reliability evaluation document on line, realizes the change management requirement of the reliability requirement, and can quickly provide effective evidence to prove that the reliability requirement meets the design requirement;
the method specifically comprises the following steps:
step S1, the state flow of the reliability distribution document, the reliability requirement document, the system design and the system requirement document containing the reliability requirement is converted to be verified;
s2, establishing a reliability analysis package, adding the document in the S1 into the analysis package, and editing a corresponding baseline version;
step S3, copying the ID number of the reliability analysis packet;
step S4, opening the reliability evaluation document, and adding a wiki table at the corresponding position;
step S5, opening a Wiki table, and pasting the ID to the Zbaseline position in the script;
and step S6, returning the reliability assessment document, and clicking to save, so that the reliability requirement label and the content in the step S1 can be automatically displayed in the reliability assessment document.
2. The method according to claim 1, wherein in step S2, if the next baseline version does not need the automatically extracted reliability requirement document, the reliability requirement document is deleted from the reliability analysis package, or the document version containing the reliability requirement in the reliability analysis package is updated according to the change of the baseline.
3. The method for automatically retrieving and extracting reliability requirements according to claim 1, wherein the step S2 of establishing the reliability analysis package specifically comprises:
step S21, determining the document state containing the reliability requirement;
step S22, opening a newly-built item of the reliability analysis package under the baseline;
step S23, adding a document with reliability requirement, wherein the position of the added document exists in the establishment of the reliability analysis package, and the document in the step S21 needs to be added;
step S24, judging whether the documents under the baseline are completely added, if yes, executing step S25, and if not, returning to step S23;
step S25, selecting the document version number of the reliability requirement under the corresponding baseline, and determining the evaluated version of the document added in the step S23
Step S26, judging whether the version number under the baseline is correct, if so, executing step S27, and if not, returning to step S25;
step S27, saving and submitting, wherein the established reliability requirement analysis package is saved and submitted to generate the ID number of the analysis package;
in step S28, the ID number of the reliability analysis package is copied.
4. The method of claim 3, wherein the step S27 of automatically retrieving and extracting the ID number of the analysis package and the reliability requirement label is a one-to-one correspondence.
5. The method for automatically retrieving and extracting reliability requirements of claim 3, wherein the steps S4 and S5 specifically comprise:
step S31, setting the reliability evaluation document state as writing, and only writing the state can edit wiki and document;
step S32, inserting wiki macro and mark in corresponding position;
step S33, clicking to modify wiki content;
step S34, pasting the ID of the reliability analysis package at the Zbaseline position of the script;
step S35, click to save in the reliability evaluation document;
step S36, clicking the reliability mark to edit the contents of the columns in the wiki table except the contents of the other columns after automatic retrieval and extraction;
step S37, click to save, go to step S38, click to submit, go to step S40;
step S38, the wiki content can be edited;
step S39, clicking to submit, and going to step S40;
step S40, version locking.
6. The method for automatically retrieving and extracting reliability requirements according to claim 5, wherein the step S32 specifically comprises: a wiki is inserted at the location of the reliability evaluation result and the corresponding macro script is copied into the blank wiki.
7. The method for automatically retrieving and extracting reliability requirements according to claim 5, wherein the step S33 specifically comprises: and right clicking the mark of the wiki, clicking the modification, and entering the wiki script.
8. The method as claimed in claim 5, wherein the version can be changed, and the change management process comprises the following steps:
step S41, establishing a reliability analysis package to obtain the ID of the analysis package;
step S42, editing and submitting the wiki table;
step S43, editing the reliability assessment document and submitting V1.0.0 version;
step S44, changing the reliability evaluation document state into writing;
step S45, newly establishing a reliability analysis package, wherein the ID obtained in the step S41 is different from that obtained in the step S41;
step S46, editing and submitting the wiki table, wherein the content of the wiki table is different from that of the wiki table in the step S42;
step S47, editing reliability assessment document and submitting V1.1.0;
step S48, comparing the wiki list under the two reliability analysis packages ID with the document content;
in step S49, the difference is the content of V1.1.0 change at V1.0.0, and change management is realized.
9. The method for automatically retrieving and extracting reliability requirements of claim 5, wherein the method can check the reliability assessment results of different historical versions online and generate online reliability assessment documents.
CN202011540108.1A 2020-12-23 2020-12-23 Method for automatically retrieving and extracting reliability requirement Active CN112581094B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011540108.1A CN112581094B (en) 2020-12-23 2020-12-23 Method for automatically retrieving and extracting reliability requirement

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011540108.1A CN112581094B (en) 2020-12-23 2020-12-23 Method for automatically retrieving and extracting reliability requirement

Publications (2)

Publication Number Publication Date
CN112581094A CN112581094A (en) 2021-03-30
CN112581094B true CN112581094B (en) 2022-08-30

Family

ID=75139350

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011540108.1A Active CN112581094B (en) 2020-12-23 2020-12-23 Method for automatically retrieving and extracting reliability requirement

Country Status (1)

Country Link
CN (1) CN112581094B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011113217A (en) * 2009-11-25 2011-06-09 Mitsubishi Heavy Ind Ltd Reliability analysis device and method
CN109446504A (en) * 2018-10-19 2019-03-08 长沙科锐消防工程技术有限公司 A kind of fire Safety Assessment report automatic generation method and system
CN110674619A (en) * 2019-09-18 2020-01-10 北京达佳互联信息技术有限公司 Online document editing method, device, equipment and computer storage medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011113217A (en) * 2009-11-25 2011-06-09 Mitsubishi Heavy Ind Ltd Reliability analysis device and method
CN109446504A (en) * 2018-10-19 2019-03-08 长沙科锐消防工程技术有限公司 A kind of fire Safety Assessment report automatic generation method and system
CN110674619A (en) * 2019-09-18 2020-01-10 北京达佳互联信息技术有限公司 Online document editing method, device, equipment and computer storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Requirements Reasoning for Distributed Requirements Analysis Using Semantic Wiki;Peng Liang 等;《2009 Fourth IEEE International Conference on Global Software Engineering》;20090807;第388-393页 *
用户需求驱动的代码自动生成技术研究与应用;钱斌;《中国优秀博硕士学位论文全文数据库(硕士) 信息科技辑》;20130615(第06期);第I138-527页 *

Also Published As

Publication number Publication date
CN112581094A (en) 2021-03-30

Similar Documents

Publication Publication Date Title
CN102426519B (en) Linked data-based multiplexing method of business process execution language (BPEL) templates and services, and system thereof
CN105243108A (en) XBRL based intelligent reporting platform system
CN104657274B (en) software interface test method and device
CN106355375B (en) A kind of automatic materiel affirmation method
CN113282498B (en) Method, device, equipment and storage medium for generating test cases
WO2021164279A1 (en) Semiconductor automatic test equipment for improving test flow efficiency, and testing method
CN104391796A (en) Method for parsing test cases
CN111191429A (en) System and method for automatic filling of data table
CN112581094B (en) Method for automatically retrieving and extracting reliability requirement
CN112256238A (en) Modeled demand item management method based on FMEA
US20040002829A1 (en) Semiconductor test data analysis system
JP5747698B2 (en) Requirements management support device
JP5508872B2 (en) Manufacturing procedure information creation system and manufacturing procedure information creation program
JP4888534B2 (en) Program development support apparatus and processing method
CN115168347A (en) Method for combining data through rapid synchronization and abnormal rollback among multiple databases
JP2014102634A (en) Method and apparatus for supporting user operation
JP6993573B2 (en) Program analysis method, program analysis device and program analysis program
CN106844447A (en) The processing method and processing unit of nuclear power station alarm card
CN104778282A (en) Browser webpage fault-tolerance method and system for IPTV set top box
CN111475997A (en) Bit number arranging method, system, equipment and medium for printed circuit board diagram
CN110990561A (en) Method for automatically classifying defect texts of power equipment
Zhao et al. Peer-aided Repairer: Empowering Large Language Models to Repair Advanced Student Assignments
CN112596475B (en) System safety analysis system based on process control
CN117332760B (en) Verification plan auxiliary editing method, electronic equipment and storage medium
CN115269433A (en) HTML document processing method and device and HTML element positioning method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant