A technical method for urban rail signal contract requirements, traceability and closed loop

Abstract

The present invention discloses a technical method for urban rail information field, in particular, a contract requirement, tracing and closed loop of urban rail signal, comprising the following steps: S1.1: Based on existing subway signal project contracts of different lines, a standard requirement matrix is ​​formed to trace target one; S1.2: Standard requirement tracing is formed and then requirement verification and confirmation are performed; S1.3: After the integrity and correctness of the requirements are guaranteed, a unified use case number is used for coverage; S1.4: After the use case test, defects are found, problems are traced, and a demand closed loop process is formed. The present invention generates a standard requirement matrix based on existing delivered projects, has a unified reference standard, and reduces the labor cost of iterative updates in the requirement matrix. The unified use case number is matched between the project test outline traceability and the template, which saves the time of test outline tracing matching and can ensure the correctness and completeness of the existing function traceability. The improvement of the standard library reduces the pressure of project delivery and saves manpower.

Description

Technical Field

[0001] The present invention relates to the field of urban rail information, and in particular to a technical method for urban rail signal contract requirements, tracing and closed loop. Background Art

[0002] Currently, for subway signal project contracts on different lines, the contract terms for each project must be managed within a demand matrix. First, the integrity of the contract and meeting minutes must be ensured. Each contract, on average, contains approximately 2,000 clauses, covering five different disciplines: system-level, automatic train control subsystem (ATC), interlocking subsystem (CI), automatic train monitoring subsystem (ATS), maintenance support subsystem (MSS), and data communication system (DCS). Under current practices, due to differences in personnel qualifications across projects, each role in each project must be reviewed again. Due to the large volume of requirements involved (approximately 2,000), the work involved in tracing project requirements is severely wasted. Furthermore, problems that arise in one project often reappear in another, with no convergence. Furthermore, different people have inconsistent understandings of contract requirements. Summary of the Invention

[0003] The purpose of the present invention is to solve the defects mentioned in the above background technology by proposing a technical method for urban rail signal contract requirements, tracing and closed loop.

[0004] The technical solution adopted in the present invention is as follows:

[0005] Provide a technical method for urban rail signal contract requirements, traceability and closed loop, including the following steps:

[0006] S1.1: Based on existing subway signal project contracts for different lines, form a standard demand matrix to trace goal one;

[0007] S1.2: Form standard requirements traceability and then conduct requirements verification and confirmation;

[0008] S1.3: After the completeness and correctness of the requirements are ensured, use a unified use case number to cover them;

[0009] S1.4: After use case testing, defects are discovered, problems are traced, and a closed-loop demand process is formed.

[0010] As a preferred technical solution of the present invention: in the steps S1.1 and S1.2, when a new project appears, it is traced using a new contract and a standard demand matrix.

[0011] As a preferred technical solution of the present invention: when a new item appears, the following steps are performed:

[0012] S2.1: Convert the contract into a demand matrix to generate project demand matrix 1;

[0013] S2.2: Compare with the standard demand matrix to generate demand matrix 2;

[0014] S2.3: Confirm the coverage status of existing functions, supplement the traceability OR form for new functions, and generate the third demand matrix;

[0015] S2.4: Index the corresponding verification and confirmation conclusions according to the published requirement numbers, supplement the verification and confirmation of new functions, and generate verification reports and confirmation reports.

[0016] As a preferred technical solution of the present invention: when a new project appears, the new function and the meeting minutes of the new project are listed separately and allocated to each discipline for retrospective coverage.

[0017] As a preferred technical solution of the present invention: based on the existing delivered projects, a standard demand matrix is ​​generated, and through tool indexing, the content covered by downstream demand is matched according to the similarity of contract content, and covered after manual confirmation.

[0018] As a preferred technical solution of the present invention: in the step S1.2, based on the existing project contract, the supporting verification and confirmation records have been verified and confirmed in the existing project, and the verification and confirmation records are copied from the original project to form a standard requirement tracing and then to the requirement verification and confirmation process.

[0019] As a preferred technical solution of the present invention: in the step S1.3, for product requirements, the outline template and the project test outline use case are uniquely numbered, and when the use cases and requirements of a specific project are subsequently traced, the standard library is directly referenced.

[0020] As a preferred technical solution of the present invention: in step S1.4, the detailed steps are as follows:

[0021] S3.1: Based on the standard requirement matrix and the test outline templates of various professional standards, trace back to form a standard requirement traceability test outline template;

[0022] S3.2: Based on the project's requirements matrix and the standard requirements traceability test outline template, use the table traceability tool to identify the standard requirement number, index the corresponding use case number in the standard requirements traceability test outline template, and form the project's test outline traceability verification record;

[0023] S3.3: Perform closed-loop confirmation of the project's requirements matrix based on the project test report and general confirmation results.

[0024] As a preferred technical solution of the present invention: demand closed loop, common part, confirm the result analysis closed loop according to the common demand.

[0025] As a preferred technical solution of the present invention: the general part is closed after analysis based on the confirmation result corresponding to the associated general requirement number. When the general part requirement is passed, it is directly referenced. When it fails, the impact on the project is re-analyzed before deciding whether to close the loop; when it is a specific related part, the requirement closure result is given by the test results of the test report of the specific project.

[0026] Compared with the existing technology, the technical method for urban rail signal contract requirements, tracing and closed loop provided by the present invention has the following beneficial effects:

[0027] 1. Generate a standard requirement matrix based on existing delivered projects, which provides a unified reference standard and reduces the labor cost of iterative updates in the requirement matrix.

[0028] 2. The unified use case number is matched between the project test outline traceability and the template, which saves the time of test outline traceability matching and can ensure the correctness and completeness of the existing function traceability.

[0029] 3. The improvement of the standard library reduces duplication of work and issues caused by personnel cognition or changes, reduces the pressure of project delivery, and saves manpower. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 A flow chart of a method according to a preferred embodiment of the present invention;

[0031] Figure 2 This is a flow chart of demand matrix generation and baseline improvement in a preferred embodiment of the present invention;

[0032] Figure 3 This is an improved flow chart of the test outline traceability verification and requirement closed-loop confirmation in the preferred embodiment of the present invention;

[0033] Figure 4 It is a flow chart from the demand matrix to the entire demand closed loop in the preferred embodiment of the present invention;

[0034] Figure 5 This is a flow chart of demand matrix generation and baseline improvement in a preferred embodiment of the present invention;

[0035] Figure 6 This is a flow chart before improvement of test outline writing and requirement traceability verification in the preferred embodiment of the present invention. DETAILED DESCRIPTION

[0036] It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of this embodiment can be combined with each other. The technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0037] Reference Figure 1-3 The preferred embodiment of the present invention provides a technical method for urban rail signal contract requirements, tracing and closed loop, including the following steps:

[0038] S1.1: Based on existing subway signal project contracts for different lines, form a standard demand matrix to trace goal one;

[0039] S1.2: Form standard requirements traceability and then conduct requirements verification and confirmation;

[0040] S1.3: After the completeness and correctness of the requirements are ensured, use a unified use case number to cover them;

[0041] S1.4: After use case testing, defects are discovered, problems are traced, and a closed-loop demand process is formed.

[0042] In the steps S1.1 and S1.2, when a new project appears, it is traced using the new contract and standard requirement matrix.

[0043] When a new item appears, perform the following steps:

[0044] S2.1: Convert the contract into a demand matrix to generate project demand matrix 1;

[0045] S2.2: Compare with the standard demand matrix to generate demand matrix 2;

[0046] S2.3: Confirm the coverage status of existing functions, supplement the traceability OR form for new functions, and generate the third demand matrix;

[0047] S2.4: Index the corresponding verification and confirmation conclusions according to the published requirement numbers, supplement the verification and confirmation of new functions, and generate verification reports and confirmation reports.

[0048] When new projects emerge, new functions and meeting minutes of new projects are listed separately and assigned to each discipline for retrospective coverage.

[0049] Based on the existing delivered projects, a standard demand matrix is ​​generated. Through tool indexing, the downstream demand coverage is matched according to the similarity of the contract content, and coverage is carried out after manual confirmation.

[0050] In step S1.2, based on the existing project contract, the supporting verification and confirmation records have been verified and confirmed in the existing project. The verification and confirmation records are copied from the original project to form a standard requirement tracing and then requirement verification and confirmation process.

[0051] In step S1.3, for product requirements, the outline template and the project test outline use case are uniquely numbered, and when the use cases and requirements of a specific project are subsequently traced, the standard library is directly referenced.

[0052] In step S1.4, the detailed steps are as follows:

[0053] S3.1: Based on the standard requirement matrix and the test outline templates of various professional standards, trace back to form a standard requirement traceability test outline template;

[0054] S3.2: Based on the project's requirements matrix and the standard requirements traceability test outline template, use the table traceability tool to identify the standard requirement number, index the corresponding use case number in the standard requirements traceability test outline template, and form the project's test outline traceability verification record;

[0055] S3.3: Perform closed-loop confirmation of the project's requirements matrix based on the project test report and general confirmation results.

[0056] Demand closed loop, general part, directly confirm the result analysis closed loop based on general requirements.

[0057] The general part is closed after analysis based on the confirmation results corresponding to the associated general requirement numbers. When the general part requirement is passed, it is directly referenced. When it fails, the impact on the project is re-analyzed before deciding whether to close the loop. When it is a specific related part, the requirement closure result is given by the test results of the test report of the specific project.

[0058] In this embodiment, a standard requirements matrix traceability template is created based on existing project contracts. Then, when new projects emerge, the technical manager simply uses the new contract and standard requirements matrix for traceability. Meeting minutes for new features and projects can be individually listed and assigned to each discipline for traceability coverage. Because meeting minutes for new features and projects are discussed face-to-face with the client, the discipline manager's understanding of the requirements is consistent, making traceability easier.

[0059] When there is a standard requirement traceability matrix, the supporting verification and confirmation records have been verified and confirmed in the existing projects. The verification and confirmation records are directly copied from the original project to form a standard requirement traceability and then requirement verification and confirmation process.

[0060] Once the completeness and correctness of requirements are guaranteed, they need to be covered using unified use case numbers. For product requirements, test case numbers are unique. If the test case numbers for each specific project are unified, the requirements matrix can be traced back to standard use cases and gradually improved. There is no need to trace the use cases and requirements of subsequent specific projects separately; the standard library can be directly referenced.

[0061] When the test case is completed, there will definitely be some defects, which involves the demand closure loop, but the problem ticket will definitely be related to the demand. In this way, by tracing back, the process from demand tracing to use case to demand tracing and finally to demand closure loop can be completed.

[0062] Reference Figure 4-6 This represents the current requirements traceability, verification, and closed-loop requirements confirmation process. Table 1 shows a comparison of project time commitments before and after improvements. Based on specific project statistics and the time commitments for each professional activity before improvements, and calculated using the improved requirements activity baseline theory, the total reduction in work time is 147.5 - 51 = 96.5 person-days.

[0063] Table 1. Comparison of project investment time.

[0064]

[0065]

[0066] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above and that the invention can be embodied in other specific forms without departing from the spirit or essential characteristics of the invention. Therefore, the embodiments should be considered in all respects as illustrative and non-restrictive, and the scope of the invention is defined by the appended claims, not the foregoing description, and all variations within the meaning and range of equivalents of the claims are intended to be included therein. Any reference sign in a claim should not be construed as limiting the claim to which it relates.

[0067] In addition, it should be understood that although this specification is described in terms of implementation methods, not every implementation method contains only one independent technical solution. This narrative method of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment can also be appropriately combined to form other implementation methods that can be understood by those skilled in the art.

Claims

1. A technical method for urban rail signal contract requirements, traceability, and closed loop, characterized by: The steps include: S1.1: Based on existing subway signal project contracts for different lines, form a standard demand matrix to trace goal one; S1.2: Form standard requirements traceability and then conduct requirements verification and confirmation; S1.3: After the completeness and correctness of the requirements are ensured, use a unified use case number to cover them; S1.4: After use case testing, defects are discovered and the problems are traced to form a closed-loop process for requirements; In steps S1.1 and S1.2, when a new project appears, traceability is performed using the new contract and standard requirement matrix; When a new item appears, perform the following steps: S2.1: Convert the contract into a demand matrix to generate project demand matrix 1; S2.2: Compare with the standard demand matrix to generate demand matrix 2; S2.3: Confirm the coverage status of existing functions, supplement the traceability OR form for new functions, and generate the third demand matrix; S2.4: Index the corresponding verification and validation conclusions according to the published requirement numbers, perform additional verification and validation of new functions, and generate verification and validation reports; In step S1.4, the detailed steps are as follows: S3.1: Based on the standard requirement matrix and the test outline templates of various professional standards, trace back to form a standard requirement traceability test outline template; S3.2: Based on the project's requirements matrix and the standard requirements traceability test outline template, use the table traceability tool to identify the standard requirement number, index the corresponding use case number in the standard requirements traceability test outline template, and form the project's test outline traceability verification record; S3.3: Perform closed-loop confirmation of the project's requirements matrix based on the project test report and general confirmation results.

2. The technical method for urban rail signal contract requirements, tracing and closed loop according to claim 1 is characterized by: When new projects emerge, new functions and meeting minutes of new projects are listed separately and assigned to each discipline for retrospective coverage.

3. The technical method for urban rail signal contract requirements, tracing and closed loop according to claim 1 is characterized by: Based on the existing delivered projects, a standard demand matrix is ​​generated. Through tool indexing, the downstream demand coverage is matched according to the similarity of the contract content, and coverage is carried out after manual confirmation.

4. The technical method for urban rail signal contract requirements, tracing and closed loop according to claim 1 is characterized by: In step S1.2, based on the existing project contract, the supporting verification and confirmation records have been verified and confirmed in the existing project. The verification and confirmation records are copied from the original project to form a standard requirement tracing and then requirement verification and confirmation process.

5. The technical method for urban rail signal contract requirements, tracing and closed loop according to claim 1 is characterized by: In step S1.3, for product requirements, the outline template and the project test outline use case are uniquely numbered, and when the use cases and requirements of a specific project are subsequently traced, the standard library is directly referenced.

6. The technical method for urban rail signal contract requirements, tracing and closed loop according to claim 1 is characterized by: Demand closed loop, general part, confirm the result analysis closed loop based on general requirements.

7. The technical method for urban rail signal contract requirements, tracing and closed loop according to claim 6 is characterized by: The general part is closed after analysis based on the confirmation results corresponding to the associated general requirement numbers. When the general part requirement is passed, it is directly referenced. When it fails, the impact on the project is re-analyzed before deciding whether to close the loop. When it is a specific related part, the requirement closure result is given by the test results of the test report of the specific project.

Images