Method for automatically extracting urban rail signal system interface requirements and macro tool
By importing macro tools in the interface requirements verification report template in Excel format, the requirements content in the interface specifications are automatically extracted and filled in, which solves the inefficiency problem in the interface requirements management of signal systems and external systems, and achieves efficient and accurate requirements management.
Patent Information
- Application Number
- CN202510547347.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-28
- Publication Date
- 2025-08-12
AI Technical Summary
In the prior art, the demand management of the interface between urban rail transit signal systems and external systems mainly relies on manual copying and pasting, which has a large workload and is prone to omissions or errors, resulting in low work efficiency.
The interface requirements verification report template is adopted in Excel format and imported into the macro tool. VBA programming is used to automatically extract the requirements content in the interface specification book and fill it into the report template, including judging the paragraph type and writing it in columns.
It realizes automated management of interface requirements, reduces manual operations, improves work efficiency, ensures the integrity and correctness of requirements, and simplifies the operation process.
Smart Images

Figure CN120471032A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of urban rail transit signal systems, and in particular to a method, a macro tool, an electronic device, and a readable storage medium for automatically extracting interface requirements of an urban rail transit signal system. Background Art
[0002] The contract requirements for urban rail transit signaling systems include both signaling system technical requirements and requirements for interfaces with external systems. These technical requirements primarily concern the various subsystems within the signaling system and are currently managed through the Project Technical Requirement Design Validation Table (PTR-DVT), achieving automated requirements management. However, the management of requirements for interfaces with external systems relies primarily on manual copy-and-paste, leaving work efficiency open.
[0003] The external systems that interface with the signal system mainly include the platform door system, large screen system, passenger guidance system, clock system, wired broadcast system, integrated monitoring system, car wash system, and interfaces with other lines. The signal systems of unmanned lines or interconnected subway lines have more external interfaces, with the number exceeding twenty. The interface requirement management between the signal system and external systems mainly relies on the verification and confirmation of the interface specifications between the signal system and each external system to ensure that the actual interface of the subway project is implemented in accordance with the requirements of the interface specifications. Each interface specification is compiled according to a unified template. Chapter 1 is an overview, which mainly introduces the purpose of writing and abbreviation definitions. It does not involve specific technical requirements and does not require requirement confirmation. Therefore, interface requirement management starts from Chapter 2. The specific approach is: define each title in the interface specification as a requirement number, and define the content under the title as the corresponding requirement content, and then copy and paste the requirement number and requirement content one by one into the interface requirement verification report template to form the first version of the interface requirement verification report. Subsequently, each requirement in the first version of the interface requirement verification report will be classified (categories include on-site debugging, system-level testing, ATS (Automatic Train Supervision, automatic train monitoring system) subsystem testing, ATC (Automatic Train Control, automatic train control) subsystem testing, interlocking subsystem testing, etc.), covered and verified to form an interface requirement confirmation report for the project.
[0004] Due to the large number of external interfaces, manual copying and pasting is required, which is very labor-intensive and prone to omissions or errors caused by human misoperation. This increases the workload of downstream indoor testing and on-site interface debugging, increases rework costs, and greatly reduces work efficiency. Summary of the Invention
[0005] The purpose of the present invention is to provide a method, device, electronic device and readable storage medium for automatically extracting interface requirements of urban rail signal systems, which can automatically extract the requirements in the interface specification and fill them into the interface requirement verification report template, thereby improving work efficiency.
[0006] In order to achieve the above objectives, the present invention is implemented through the following technical solutions:
[0007] A method for automatically extracting interface requirements of an urban rail signal system, comprising:
[0008] Create an interface requirement verification report template in Excel format;
[0009] Importing a macro tool into the interface requirement verification report template;
[0010] Start the macro tool so that the macro tool: calls the interface specification of the requirements to be extracted, extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template, wherein the interface specification is in Word format.
[0011] Optionally, the macro tool is generated using VBA programming.
[0012] Optionally, in the interface requirement verification report template, each row in the first column is used to write the name of each requirement, and each row in the second column is used to write the specific content of the requirement.
[0013] Optionally, extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template includes:
[0014] Perform the following processing on one or more target sections in the interface specification, where the target section is a section used to describe interface requirements:
[0015] Determine whether each paragraph in the target chapter belongs to the outline level or the main text level;
[0016] Write the contents of the paragraphs belonging to the outline level into each row of the first column of the interface requirement verification report template in turn, and write the contents of all paragraphs belonging to the body text below the paragraph into the corresponding rows of the second column of the interface requirement verification report template.
[0017] Optionally, the calling of the interface technical specification of the requirement to be extracted includes:
[0018] The macro tool generates a first user selection interface, wherein the first user selection interface allows the user to select the interface specification document of the requirement to be extracted;
[0019] Call the interface specification selected by the user.
[0020] Optionally, the method further includes: the macro tool generating a second user selection interface, the second user selection interface allowing the user to select whether to write the table in the interface specification into the interface requirement verification report template;
[0021] The extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template includes:
[0022] If the user chooses to write the tables in the interface specification into the interface requirement verification report template, then when extracting the paragraph content corresponding to each requirement from the interface specification, the paragraph content together with the tables therein will be written into the interface requirement verification report template;
[0023] If the user chooses not to write the tables in the interface specification into the interface requirement verification report template, the paragraph content corresponding to each requirement will be extracted from the interface specification, and the tables will be skipped and written into the interface requirement verification report template.
[0024] Optionally, the method also includes: the macro tool generates a copy progress display interface, and the copy progress display interface is used to display the progress information, current time information and estimated remaining time information of the entire process of extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template.
[0025] Optionally, the progress information is the ratio of the number of processed paragraphs to the total number of paragraphs in the interface specification;
[0026] The current time information is provided by the countdown time function of the macro tool;
[0027] The estimated remaining time information is obtained in the following manner: assuming that each paragraph takes the same amount of time, the timing value of the countdown time function is divided by the number of paragraphs that have been processed to obtain an estimated time for each paragraph, and then the estimated time is multiplied by the number of remaining paragraphs to obtain an estimated value of the remaining time.
[0028] A macro tool for automatically extracting interface requirements for urban rail signal systems. The macro tool is integrated into the interface toolbar of an interface requirement verification report template in Excel format. When the macro tool is started, the macro tool is used to: call the interface specification document for the requirements to be extracted, extract the paragraph content corresponding to each requirement from the interface specification document, and write the content into the interface requirement verification report template. The interface specification document is in Word format.
[0029] Optionally, the macro tool is generated using VBA programming.
[0030] Optionally, in the interface requirement verification report template, each row in the first column is used to write the name of each requirement, and each row in the second column is used to write the specific content of the requirement.
[0031] Optionally, the macro tool extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template, including:
[0032] The macro tool performs the following processing on one or more target sections in the interface specification, wherein the target section is a section used to describe interface requirements:
[0033] Determine whether each paragraph in the target chapter belongs to the outline level or the main text level;
[0034] Write the contents of the paragraphs belonging to the outline level into each row of the first column of the interface requirement verification report template in turn, and write the contents of all paragraphs belonging to the body text below the paragraph into the corresponding rows of the second column of the interface requirement verification report template.
[0035] Optionally, the macro tool calls the interface technical specification of the requirements to be extracted, including:
[0036] The macro tool generates a first user selection interface, wherein the first user selection interface allows the user to select the interface specification document of the requirement to be extracted;
[0037] Call the interface specification selected by the user.
[0038] Optionally, the macro tool further generates a second user selection interface, wherein the second user selection interface allows the user to select whether to write the table in the interface specification into the interface requirement verification report template;
[0039] The macro tool extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template, specifically including:
[0040] If the user chooses to write the tables in the interface specification into the interface requirement verification report template, the macro tool extracts the paragraph content corresponding to each requirement from the interface specification and writes it together with the tables into the interface requirement verification report template;
[0041] If the user chooses not to write the tables in the interface specification into the interface requirement verification report template, the macro tool will skip the tables when extracting the paragraph content corresponding to each requirement from the interface specification and write them into the interface requirement verification report template.
[0042] Optionally, the macro tool also generates a copy progress display interface, which is used to display the progress information, current time information and estimated remaining time information of the entire process of extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template.
[0043] Optionally, the progress information is the ratio of the number of processed paragraphs to the total number of paragraphs in the interface specification;
[0044] The current time information is provided by the countdown time function of the macro tool;
[0045] The estimated remaining time information is obtained in the following manner: assuming that each paragraph takes the same amount of time, the timing value of the countdown time function is divided by the number of paragraphs that have been processed to obtain an estimated time for each paragraph, and then the estimated time is multiplied by the number of remaining paragraphs to obtain an estimated value of the remaining time.
[0046] On the other hand, the present invention further provides an electronic device, comprising a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method described above is implemented.
[0047] In another aspect, the present invention further provides a readable storage medium, wherein the readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described above is implemented.
[0048] Compared with the prior art, the present invention has the following advantages:
[0049] 1. The present invention imports a macro tool into the interface requirement verification report template in Excel format, which can realize one-click conversion of the Word version of the interface specification document into an Excel version file of specific specifications, automatically extract the interface requirements, and is simple to operate. Moreover, the macro tool is developed based on the verification strategy of the external interface requirements of the signal system, and does not require additional manual operation. The time taken for the entire requirement extraction process is greatly shortened compared with the traditional method, thereby improving work efficiency.
[0050] 2. The present invention automatically extracts the requirements on each interface specification into the interface requirement verification report template one by one in a specific format, greatly reducing the content omissions and errors caused by manual copying and pasting, and ensuring the integrity, correctness and traceability of external interface requirements.
[0051] 3. The macro tool is developed using the VBA programming language and is directly integrated into the Excel interface toolbar. There is no need to switch interfaces when using it. It is convenient and fast, and the interface is simple.
[0052] 4. The present invention solves the difficult problem in the interface requirement management process between the signal system and the external system, and provides a powerful reference for the verification and confirmation automation of the entire signal system contract requirements. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] In order to more clearly illustrate the technical solution of the present invention, the following briefly introduces the drawings required for the description. Obviously, the drawings described below are one embodiment of the present invention. Those skilled in the art can also derive other drawings based on these drawings without inventive effort:
[0054] Figure 1 A flowchart of a method for automatically extracting interface requirements of an urban rail signaling system provided by one embodiment of the present invention;
[0055] Figure 2 A schematic diagram of an interface requirement verification report template provided by an embodiment of the present invention;
[0056] Figure 3 A schematic diagram of writing requirements into an interface requirement verification report template provided by one embodiment of the present invention. DETAILED DESCRIPTION
[0057] The scheme proposed in the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. According to the following description, the advantages and features of the present invention will be clearer. It should be noted that the drawings are in a very simplified form and use non-precise proportions, which are only used to conveniently and clearly assist in explaining the purpose of the implementation methods of the present invention. In order to make the purposes, features and advantages of the present invention more obvious and easy to understand, please refer to the accompanying drawings. It should be noted that the structures, proportions, sizes, etc. illustrated in the drawings of this specification are only used to match the contents disclosed in the specification for people familiar with this technology to understand and read, and are not used to limit the limiting conditions for the implementation of the present invention, so they have no technical substantive significance. Any structural modification, change in proportional relationship or adjustment of size, without affecting the efficacy and purpose that can be achieved by the present invention, should still fall within the scope of the technical content disclosed by the present invention.
[0058] Since the interface specification is a Word document and the interface requirement verification report is an Excel document, most Word to Excel conversion tools on the market have a single conversion function, such as converting each line of Word content to each line of Excel, or converting by page, etc. Existing conversion tools do not have the function of converting according to the format requirements of the interface requirement verification report, and need to be manually adjusted, which is inconvenient and time-consuming. In order to solve the above problems, based on the verification strategy of the external interface requirements of the signal system, the present invention provides a method and a macro tool for automatically extracting the interface requirements of the urban rail signal system, which can automatically extract the requirements in the interface specification to the interface requirement verification report template, thereby improving work efficiency.
[0059] like Figure 1 As shown, the present invention provides a method for automatically extracting interface requirements of an urban rail signal system, comprising the following steps S1 to S3.
[0060] Step S1: Create an interface requirement verification report template in Excel format.
[0061] like Figure 2 As shown, this is a schematic diagram of the interface requirement verification report template. In the interface requirement verification report template, each row of the first column (for example, column A) is defined for writing the name of each requirement (i.e., requirement label Req ID), and each row of the second column (for example, column B) is defined for writing the specific content of the requirement (i.e., Text).
[0062] In addition, other columns in the interface requirement verification report template may be used to define other items related to the requirements. This facilitates extracting the requirements from the interface specification into the interface requirement verification report template. After forming a preliminary version of the interface requirement verification report, the preliminary version of the interface requirement verification report can be used to subsequently classify, verify, and confirm each requirement.
[0063] For example, in Figure 2In the ValidationAllocation section, define Column C to fill in the category (ValidationAllocation) for each requirement coverage allocation. Categories can include on-site commissioning, system-level testing, ATS subsystem testing, ATC subsystem testing, interlocking subsystem testing, etc. Define Column D to fill in comments (comments). Define Column E to fill in the specific document name involved in the test (Test procedure or test sheet reference). If an interface requirement is assigned to on-site commissioning or installation, fill in the commissioning procedure or installation procedure in this column; if the interface requirement is assigned to indoor testing, fill in the use case document name in this column. Define Column F to fill in the test case number (Test Case ID). If it is commissioning or installation, fill in the specific content of the commissioning procedure or installation procedure that covers the interface requirement in this column. Define Column G to fill in whether columns E and F fully cover the interface requirements (Status). If so, fill in YES in Column G; if not, fill in NO, and fill in the reason in Column H (Justification).
[0064] Step S2: importing a macro tool into the interface requirement verification report template.
[0065] In this embodiment, the macro tool can be developed using the VBA (Visual Basic for Applications) programming language. VBA is a macro language of Visual Basic, a programming language developed by Microsoft to perform common automation (OLE) tasks in its desktop applications. It is primarily used to extend the functionality of Windows applications, particularly Microsoft Office software. Using the VBA macro tool, you can write custom macro code to automate a series of operations through macros, such as calling a Word file and extracting content from the Word file to populate an Excel spreadsheet.
[0066] In other embodiments, other programming languages may also be used to develop the macro tool, and the present invention does not limit this.
[0067] Step S3, starting the macro tool so that the macro tool: calls the interface specification of the requirements to be extracted, extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template, wherein the interface specification is in Word format.
[0068] Specifically, after launching the macro tool, the macro tool can generate a first user selection interface, which allows the user to select the interface specification document to be extracted. As described in the background technology, there are multiple external systems that interface with the urban rail signal system, and multiple interface specifications involved. The user can select the interface specification document to be extracted in the first user selection interface. Once the user selects an interface specification document, the macro tool calls the user-selected interface specification document as the interface specification document to be extracted and performs subsequent extraction steps.
[0069] In addition, there may be tables in the interface specification, and the user can also choose whether to extract the tables into the interface requirement verification report template according to actual conditions. Specifically, the macro tool can also generate a second user selection interface, and the second user selection interface allows the user to choose whether to write the tables in the interface specification into the interface requirement verification report template. If the user chooses yes, when extracting the paragraph content corresponding to each requirement from the interface specification, the paragraph content together with the tables therein will be written into the interface requirement verification report template. If the user chooses no, when extracting the paragraph content corresponding to each requirement from the interface specification, the paragraph content will be skipped and written into the interface requirement verification report template.
[0070] In step S3, extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template specifically includes:
[0071] Perform the following processing on one or more target sections in the interface specification, where the target section is a section used to describe interface requirements:
[0072] Determine whether each paragraph in the target chapter belongs to the outline level or the main text level;
[0073] Write the contents of the paragraphs belonging to the outline level into each row of the first column of the interface requirement verification report template in turn, and write the contents of all paragraphs belonging to the body text below the paragraph into the corresponding rows of the second column of the interface requirement verification report template.
[0074] As mentioned in the background technology, the interface specification is compiled according to a unified template. Chapter 1 is an overview, which mainly introduces the purpose of writing and abbreviation definitions. It does not involve specific technical requirements and does not require requirement confirmation. Therefore, interface requirement management starts from Chapter 2. Chapter 2 and subsequent chapters are used as target chapters, and requirements are extracted according to the above method. Please refer to Figure 3, showing a schematic diagram of extracting requirements from the interface specification ATS-PANNEL and writing them into the interface requirement verification report template, wherein the two requirements 2.1 Interface Description and 2.2 Software Constraints in Chapter 2 and their specific contents are extracted and written into columns A and B of the interface requirement verification report template respectively; the two requirements 3.1 ATS Party Responsibility and 3.2 Large Screen Party Responsibility in Chapter 3 and their specific contents are extracted and written into columns A and B of the interface requirement verification report template respectively.
[0075] Furthermore, the method also includes: the macro tool generates a copy progress display interface, and the copy progress display interface is used to display the progress information, current time information and estimated remaining time information of the entire process of extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template, so that the user can understand the extraction progress.
[0076] like Figure 3 As shown, when the macro tool starts to extract, the copy progress display interface is generated and placed on the interface requirement verification report template interface. In the copy progress display interface, the progress information is the ratio of the number of processed paragraphs to the total number of paragraphs in the interface specification. The number of currently processed paragraphs can be updated in real time during the extraction process to display the progress information. The current time information is provided by the countdown time function of the macro tool. When the macro tool starts to extract, the countdown time function is triggered to start running, and the real-time data of the countdown time function is displayed as the current time information. The estimated remaining time information is obtained in the following way: assuming that each paragraph takes the same time, the timing value of the countdown time function is divided by the number of processed paragraphs to obtain an estimated time for each paragraph, and then the estimated time is multiplied by the number of remaining paragraphs to obtain an estimated value of the remaining time.
[0077] like Figure 2 、 3 As shown, the interface requirement verification report template file in Excel format contains multiple worksheets, each worksheet corresponds to an interface specification. When an interface specification needs to be extracted, the macro tool is started in the corresponding worksheet interface, and the interface specification is selected. It can be completed with one click to convert the Word version of the interface specification into an Excel version file of specific specifications, and the interface requirements therein are automatically extracted.
[0078] When the macro tool extracts all the requirements in the interface specification into the interface requirement verification report template, a preliminary version of the interface requirement verification report is formed. Users (such as managers responsible for verification and confirmation) can organize relevant personnel to cover the interface requirements with corresponding documents. For example, requirements assigned to debugging need to be covered with debugging procedures or debugging reports; requirements assigned to indoor testing need to be covered with test cases or test reports. Then, the manager collects the preliminary version of the interface requirement verification report after the interface requirements are covered, and verifies and confirms it. If the verification and confirmation fails, it will be returned to the corresponding personnel for further modification until the verification and confirmation passes. Finally, after the manager verifies and confirms it, the preliminary version of the interface requirement verification report will be upgraded to a formal report.
[0079] Based on the same inventive concept, this embodiment also provides a macro tool for automatically extracting the interface requirements of the urban rail signal system. The macro tool is integrated into the interface toolbar of the interface requirement verification report template in Excel format. When the macro tool is started, the macro tool is used to: call the interface specification of the requirements to be extracted, extract the paragraph content corresponding to each requirement from the interface specification and write it into the interface requirement verification report template. The interface specification is in Word format.
[0080] In some feasible implementations, the macro tool is developed using VBA programming language.
[0081] In some feasible implementations, in the interface requirement verification report template, each row in the first column is used to write the name of each requirement, and each row in the second column is used to write the specific content of the requirement.
[0082] In some feasible implementations, the macro tool extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template, including:
[0083] The macro tool performs the following processing on one or more target sections in the interface specification, wherein the target section is a section used to describe interface requirements:
[0084] Determine whether each paragraph in the target chapter belongs to the outline level or the main text level;
[0085] Write the contents of the paragraphs belonging to the outline level into each row of the first column of the interface requirement verification report template in turn, and write the contents of all paragraphs belonging to the body text below the paragraph into the corresponding rows of the second column of the interface requirement verification report template.
[0086] In some feasible implementations, the macro tool calls the interface technical specification of the requirements to be extracted, including:
[0087] The macro tool generates a first user selection interface, wherein the first user selection interface allows the user to select the interface specification document of the requirement to be extracted;
[0088] Call the interface specification selected by the user.
[0089] In some feasible implementations, the macro tool further generates a second user selection interface, wherein the second user selection interface allows the user to select whether to write the table in the interface specification into the interface requirement verification report template;
[0090] The macro tool extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template, specifically including:
[0091] If the user chooses to write the tables in the interface specification into the interface requirement verification report template, the macro tool extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template together with the tables therein;
[0092] If the user chooses not to write the tables in the interface specification into the interface requirement verification report template, the macro tool will skip the tables when extracting the paragraph content corresponding to each requirement from the interface specification and write them into the interface requirement verification report template.
[0093] In some feasible implementations, the macro tool also generates a copy progress display interface, which is used to display the progress information, current time information, and estimated remaining time information of the entire process of extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template.
[0094] In some feasible implementations, the progress information is a ratio of the number of processed paragraphs to the total number of paragraphs in the interface specification;
[0095] The current time information is provided by the countdown time function of the macro tool;
[0096] The estimated remaining time information is obtained in the following manner: assuming that each paragraph takes the same amount of time, the timing value of the countdown time function is divided by the number of paragraphs that have been processed to obtain an estimated time for each paragraph, and then the estimated time is multiplied by the number of remaining paragraphs to obtain an estimated value of the remaining time.
[0097] On the other hand, this embodiment further provides an electronic device, including a processor and a memory; the memory stores a computer program, and when the computer program is executed by the processor, the method of automatically extracting the interface requirements of the urban rail signal system as described above is implemented.
[0098] On the other hand, this embodiment further provides a readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method for automatically extracting the interface requirements of the urban rail signal system as described above is implemented.
[0099] In summary, the present invention can realize the one-click conversion of the Word version of the interface specification document into an Excel version file of specific specifications by importing a macro tool into the interface requirement verification report template in Excel format, automatically extract the interface requirements, and is simple to operate. Moreover, the macro tool is developed based on the verification strategy of the external interface requirements of the signal system, and does not require additional manual operation. The time taken for the entire requirement extraction process is greatly shortened compared to the traditional method, thereby improving work efficiency. The present invention automatically extracts the requirements on each interface specification document into the interface requirement verification report template one by one according to a specific format, greatly reducing the omissions and errors of content caused by manual copying and pasting, and ensuring the integrity, correctness and traceability of the external interface requirements. The macro tool is developed using the VBA programming language and is directly integrated into the Excel interface toolbar. There is no need to switch interfaces when using it, which is convenient and fast, and the interface is simple. The present invention solves the difficult problems in the interface requirement management process between the signal system and the external system, and provides a powerful reference for the automation of verification and confirmation of the contract requirements of the entire signal system.
[0100] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.
[0101] Although the present invention has been described in detail through the above preferred embodiments, it should be understood that the above description is not intended to limit the present invention. After reading the above description, various modifications and substitutions of the present invention will become apparent to those skilled in the art. Therefore, the scope of protection of the present invention should be defined by the appended claims.
Claims
1. A method for automatically extracting interface requirements of urban rail signal systems, characterized in that: include: Create an interface requirement verification report template in Excel format; Importing a macro tool into the interface requirement verification report template; Start the macro tool so that the macro tool: calls the interface specification of the requirements to be extracted, extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template, wherein the interface specification is in Word format.
2. The method for automatically extracting interface requirements of an urban rail signal system according to claim 1, characterized in that: The macro tool is developed using VBA programming language.
3. The method for automatically extracting interface requirements of an urban rail signal system according to claim 1, wherein: In the interface requirement verification report template, each row in the first column is used to write the name of each requirement, and each row in the second column is used to write the specific content of the requirement.
4. The method for automatically extracting interface requirements of an urban rail signal system according to claim 3, wherein: The extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template includes: Perform the following processing on one or more target sections in the interface specification, where the target section is a section used to describe interface requirements: Determine whether each paragraph in the target chapter belongs to the outline level or the main text level; Write the contents of the paragraphs belonging to the outline level into each row of the first column of the interface requirement verification report template in turn, and write the contents of all paragraphs belonging to the body text below the paragraph into the corresponding rows of the second column of the interface requirement verification report template.
5. The method for automatically extracting interface requirements of an urban rail signal system according to claim 1, wherein: The interface technical specification for calling the requirements to be extracted includes: The macro tool generates a first user selection interface, wherein the first user selection interface allows the user to select the interface specification document of the requirement to be extracted; Call the interface specification selected by the user.
6. The method for automatically extracting interface requirements of an urban rail signal system according to claim 1, wherein: Also includes: The macro tool generates a second user selection interface, wherein the second user selection interface allows the user to select whether to write the table in the interface specification into the interface requirement verification report template; The extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template includes: If the user chooses to write the tables in the interface specification into the interface requirement verification report template, then when extracting the paragraph content corresponding to each requirement from the interface specification, the paragraph content together with the tables therein will be written into the interface requirement verification report template; If the user chooses not to write the tables in the interface specification into the interface requirement verification report template, the paragraph content corresponding to each requirement will be extracted from the interface specification, and the tables will be skipped and written into the interface requirement verification report template.
7. The method for automatically extracting interface requirements of an urban rail signal system according to claim 1, wherein: The method also includes: the macro tool generates a copy progress display interface, and the copy progress display interface is used to display the progress information, current time information and estimated remaining time information of the entire process of extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template.
8. The method for automatically extracting interface requirements of an urban rail signal system according to claim 7, characterized in that: The progress information is the ratio of the number of processed paragraphs to the total number of paragraphs in the interface specification; The current time information is provided by the countdown time function of the macro tool; The estimated remaining time information is obtained in the following manner: assuming that each paragraph takes the same amount of time, the timing value of the countdown time function is divided by the number of paragraphs that have been processed to obtain an estimated time for each paragraph, and then the estimated time is multiplied by the number of remaining paragraphs to obtain an estimated value of the remaining time.
9. A macro tool for automatically extracting interface requirements for urban rail signal systems, characterized in that: The macro tool is integrated into the interface toolbar of the interface requirement verification report template in Excel format. When the macro tool is started, the macro tool is used to: call the interface specification of the requirements to be extracted, extract the paragraph content corresponding to each requirement from the interface specification and write it into the interface requirement verification report template. The interface specification is in Word format.
10. The macro tool for automatically extracting urban rail signal system interface requirements according to claim 9, characterized in that: The macro tool is developed using VBA programming language.
11. The macro tool for automatically extracting interface requirements of urban rail signal systems according to claim 9, characterized in that: In the interface requirement verification report template, each row in the first column is used to write the name of each requirement, and each row in the second column is used to write the specific content of the requirement.
12. The macro tool for automatically extracting urban rail signal system interface requirements according to claim 11, characterized in that: The macro tool extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template, including: The macro tool performs the following processing on one or more target sections in the interface specification, wherein the target section is a section used to describe interface requirements: Determine whether each paragraph in the target chapter belongs to the outline level or the main text level; Write the contents of the paragraphs belonging to the outline level into each row of the first column of the interface requirement verification report template in turn, and write the contents of all paragraphs belonging to the body text below the paragraph into the corresponding rows of the second column of the interface requirement verification report template.
13. The macro tool for automatically extracting urban rail signal system interface requirements according to claim 9, characterized in that: The macro tool calls the interface technical specification of the requirements to be extracted, including: The macro tool generates a first user selection interface, wherein the first user selection interface allows the user to select the interface specification document of the requirement to be extracted; Call the interface specification selected by the user.
14. The macro tool for automatically extracting urban rail signal system interface requirements according to claim 9, characterized in that: The macro tool further generates a second user selection interface, wherein the second user selection interface allows the user to select whether to write the table in the interface specification into the interface requirement verification report template; The macro tool extracts the paragraph content corresponding to each requirement from the interface specification and writes it into the interface requirement verification report template, specifically including: If the user chooses to write the tables in the interface specification into the interface requirement verification report template, the macro tool extracts the paragraph content corresponding to each requirement from the interface specification and writes it together with the tables into the interface requirement verification report template; If the user chooses not to write the tables in the interface specification into the interface requirement verification report template, the macro tool will skip the tables when extracting the paragraph content corresponding to each requirement from the interface specification and write them into the interface requirement verification report template.
15. The macro tool for automatically extracting interface requirements of urban rail signal systems according to claim 9, characterized in that: The macro tool also generates a copy progress display interface, which is used to display the progress information, current time information and estimated remaining time information of the entire process of extracting the paragraph content corresponding to each requirement from the interface specification and writing it into the interface requirement verification report template.
16. The macro tool for automatically extracting interface requirements of urban rail signal systems according to claim 15, characterized in that: The progress information is the ratio of the number of processed paragraphs to the total number of paragraphs in the interface specification; The current time information is provided by the countdown time function of the macro tool; The estimated remaining time information is obtained in the following manner: assuming that each paragraph takes the same amount of time, the timing value of the countdown time function is divided by the number of paragraphs that have been processed to obtain an estimated time for each paragraph, and then the estimated time is multiplied by the number of remaining paragraphs to obtain an estimated value of the remaining time.
17. An electronic device, characterized in that: The method comprises a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method according to any one of claims 1 to 8 is implemented.
18. A readable storage medium, characterized in that The readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.