A ship information system multi-level requirement tracing and verification method and device

Abstract

This invention discloses a multi-level requirement tracing and verification method for ship information systems, comprising: S1, constructing a unified requirement information architecture based on the Spring Boot framework to realize complex associations and tracing between requirement items, and statistical results of requirement quantity and requirement coverage; S2, achieving automated requirement checking through custom keywords and requirement verification conditions; S3, automatically scanning requirement documents and extracting unqualified requirements according to predefined verification criteria, and enabling multiple people to participate in requirement verification activities simultaneously through an online requirement review function, conducting manual checks on submitted requirements and recording review issues. This invention also discloses a multi-level requirement tracing and verification device for ship information systems. This invention supports rapid multi-level requirement logic consistency verification and dynamic updates, enabling checks on requirements to be changed from different dimensions, providing reasonable comprehensive evaluation results, and can be widely applied in the field of computer software technology.

Description

Technical Field

[0001] This invention relates to the field of computer software technology, and in particular to a method and apparatus for multi-level requirement tracing and verification of ship information systems. Background Technology

[0002] In the development of ship information systems, requirements are typically transmitted and managed hierarchically in document form. This lack of classification, hierarchical modeling, correlation, and traceability of system requirements results in low efficiency in requirements analysis and management, specifically manifested in the following aspects: (1) Lack of visual traceability methods for related information Existing visualization tools can only display static relationships in a single dimension, and cannot dynamically map the traceability relationship between requirement clauses, verification rules, and test cases, making it difficult to support the localization of systemic problems.

[0003] (2) Errors in the correctness, consistency, completeness and traceability of requirements are difficult to detect. Traditional requirement verification process relies heavily on the designer’s experience and requires manual verification of each requirement. It is impossible to automatically deduce and prove whether the requirement set covers correctness, consistency, completeness and traceability through formal methods, which can easily lead to repeated design in the later stages.

[0004] (3) Efficiency bottleneck caused by manual reliance in the verification process The system's multi-dimensional verification information is isolated and scattered. The verification results of requirements such as functionality, performance, and security lack a unified display medium, which requires designers to frequently switch between documents, models, and test cases. The average time spent on a single project accounts for 35%-45% of the development cycle. Summary of the Invention

[0005] The purpose of this invention is to overcome the shortcomings of the aforementioned background technology and provide a method and apparatus for tracing and verifying multi-level requirements of a ship information system, enabling it to support rapid multi-level requirement logic consistency verification and dynamic updates, and to check the requirements to be changed from different dimensions, providing a reasonable comprehensive evaluation result.

[0006] This invention provides a multi-level requirement tracing and verification method for ship information systems, comprising the following steps: S1, Requirement statistics and tracing: A unified requirement information architecture is constructed based on the Spring Boot framework to realize complex associations and tracing between requirement items, statistical results of requirement quantity and requirement coverage, and intuitively display requirement tracing relationships and requirement results; S2, Customization of requirement verification criteria and verification matrix: Based on requirement tracing and requirement results, automated requirement checks are achieved through custom keywords and requirement verification conditions; S3, Requirement rationality verification: Automated requirement inspection is achieved based on requirement verification criteria. Requirement documents are automatically scanned and unqualified requirements are extracted according to predefined verification criteria. Through the online requirement review function, multiple people can participate in requirement verification activities simultaneously, and manual checks are conducted on submitted requirements, recording review issues.

[0007] In the above technical solution, in step S1, the complex association and traceability between demand items, as well as the statistical results of demand quantity and demand coverage, are realized by fully constructing the demand traceability relationship at each level to form a ship information relationship overview diagram.

[0008] In the above technical solution, the specific process of constructing a complete overview of ship information relationships by establishing demand traceability relationships at all levels in step S1 is as follows: S11, constructing demand traceability relationships by analyzing the demand traceability relationships between the surface ship information system, subsystems, and equipment; S12, selecting a source entry in the current system and a target entry in the new association window to establish a relationship between the source entry and the target entry based on the selected link type and direction; S13, viewing the associated upstream and downstream demand entries through the link indicator, and penetrating to the project where the entry is located by clicking on the demand entry in the link indicator, and accurately locating the row of the corresponding entry.

[0009] In the above technical solution, the specific process of step S2 is as follows: S21, according to the ship information system's custom inspection rules, realize the automated screening of the correctness, completeness, consistency and traceability of requirements; S22, display the established and associated requirements information at all levels in a list in the form of attribute columns to form a complete requirement verification matrix.

[0010] In the above technical solution, in step S21, the custom inspection rules include setting keywords corresponding to the ship information system and logical operators such as "included" and "not included".

[0011] In the above technical solution, the specific process of step S22 is as follows: Based on the traceability relationship between system requirements, subsystem requirements and subsystem requirements, a requirement rationality verification matrix is ​​constructed for downstream solution domain requirements by creating a link analysis column, which displays the upstream requirement information associated with each downstream requirement.

[0012] In the above technical solution, the specific process of step S3 is as follows: S31, before submitting the requirement document for verification review, the requirement document is self-checked through the automated verification and inspection function. The inspection scope includes automated verification and inspection of correctness, consistency, completeness, and traceability, and generates a "non-compliant requirement list"; S32, after submitting the requirement review, the review tasks in the to-do list are received, the requirement verification matrix view of the submitted document is opened, multiple people fill in their respective review opinions on the requirement items in a submitted document in parallel, and provide overall review opinions on the submitted document through the requirement checklist. The requirements are modified according to the problem list in each requirement review record, and the requirement rationality verification activity is executed multiple times until all problems are resolved.

[0013] In the above technical solution, the specific process of repeatedly executing the requirement rationality verification activity until all problems are resolved in step S32 is as follows: the requirement item and the corresponding verification activity are traced back to each other, and finally the relevant attribute values ​​of the verification matrix of the requirement document are updated based on the results of the verification activities to determine whether the requirement has been verified.

[0014] In the above technical solution, the relevant attribute values ​​of the verification matrix in step S32 include: verification maturity, verification status, and verification rejection reason.

[0015] This invention provides a multi-level requirement tracing and verification device for ship information systems, which has a computer program that can execute a multi-level requirement tracing and verification method for ship information systems.

[0016] The multi-level requirement tracing and verification method and apparatus for ship information systems of the present invention have the following beneficial effects: This invention constructs a requirement rationality verification system based on Spring Boot, addressing issues such as traceability difficulties, inconsistent verification standards, and lack of closed-loop management in the verification of requirements for ship information systems. It establishes a complete system requirement rationality verification chain. The system, with data association technology at its core, significantly improves requirement traceability through multi-level requirement visualization and dynamic coverage statistics. It supports flexible configuration of automated inspection rules through customizable verification criteria and attributed verification matrices, achieving multi-dimensional attributed verification from requirements to design to implementation. Furthermore, it integrates automated scanning and online collaborative review mechanisms, innovatively constructing a closed-loop requirement rationality verification chain of "rule-driven automatic verification + manual review and iterative correction." This method effectively solves the pain points of traditional verification, such as low efficiency of manual verification, scattered verification standards, and unclear traceability relationships, improving requirement verification efficiency by more than 30% and increasing the compliance rate between design results and requirements to 98%. It provides a quantifiable, traceable, and closed-loop requirement association verification solution for ship information system development. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the overall process of the multi-level requirement tracing and verification method for ship information systems of the present invention; Figure 2 This is an overview diagram of the requirement tracing relationship in the multi-level requirement tracing and verification method for ship information systems of the present invention; Figure 3 This is the custom interface for automated inspection rules in the multi-level requirement tracing and verification method for ship information systems of the present invention. Figure 4 This is a schematic diagram of the requirement rationality verification matrix in the multi-level requirement tracing and verification method for ship information systems of the present invention; Figure 5 This is a schematic diagram of the requirement approval process based on manual review in the multi-level requirement traceability and verification method for ship information systems of the present invention; Figure 6 This is a schematic diagram illustrating the location and lookup of associated requirements in the multi-level requirement tracing and verification method for ship information systems of the present invention. Figure 7 This is a schematic diagram of the requirement checklist and check item definition interface in the multi-level requirement traceability and verification method for ship information systems of the present invention. Figure 8 This is a schematic diagram of the requirement review results in the multi-level requirement tracing and verification method for ship information systems of the present invention; Figure 9 This is a schematic diagram illustrating the construction of the association between verification activities and requirement items in the multi-level requirement tracing and verification method for ship information systems of the present invention; Figure 10 This is a schematic diagram illustrating the verification activities and verification results execution in the multi-level requirements tracing and verification method for ship information systems of the present invention. Figure 11 This is an output diagram showing the result update of the requirement matrix verification result in the multi-level requirement tracing and verification method for ship information systems of the present invention. Figure 12 This is a schematic diagram of the architecture of the multi-level requirement traceability and verification device for ship information system of the present invention. Detailed Implementation

[0018] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments, but these embodiments should not be construed as limiting the present invention.

[0019] This invention is a B / S architecture software developed and run in a Windows environment. It uses Java and the Spring Boot framework for backend logic development and Recat frontend framework + AntDesign enterprise-level UI component library for frontend display page development. It innovatively constructs a unified requirement information architecture and a multi-dimensional verification mechanism.

[0020] Example 1 See Figure 1 The main technical points of the multi-level requirement tracing and verification method for ship information systems of the present invention in this embodiment are as follows: (1) A demand statistics and traceability technology is proposed. A unified requirements information architecture is built based on the Spring Boot framework to store and manage requirements information and relationships at all levels. Data association technology is used to achieve complex relationships and traceability between requirements items, as well as statistics on the number of requirements and requirement coverage. The requirements traceability view and requirements statistics interface provide a clear visualization of requirements traceability relationships and results. An overview of requirements traceability relationships can be found here. Figure 2 .

[0021] (2) A requirement verification criterion and a custom verification matrix technique are proposed. This paper proposes a customizable requirement verification criterion and verification matrix technology. It supports automated requirement checks through custom keywords and verification conditions. Designers can customize inspection rules based on the ship's information system, enabling automated screening of requirement correctness, completeness, consistency, and traceability. The automated inspection rule customization interface can be found here. Figure 3 The established requirements at all levels are integrated and displayed in a list as attribute columns, forming a complete requirement verification view. See the requirement rationality matrix. Figure 4 Based on the aforementioned intuitive visualization method, verification work was carried out on the coverage of upstream and downstream requirements and the degree to which the design and implementation met those requirements.

[0022] (3) A demand rationality verification technique is proposed. This paper proposes an automated requirement rationality verification and review technology. On one hand, it enables automated requirement verification based on requirement verification rules, automatically scanning requirement documents and extracting non-compliant requirements according to predefined verification criteria. On the other hand, it allows multiple users to participate in requirement verification activities simultaneously through an online requirement review function. The requirement approval process based on manual review is described in [link to relevant documentation]. Figure 5 It can perform manual checks on submitted requirements using customized checklists and record review issues. This supports iterative revisions of the design results until the verification activity is successful.

[0023] Example 2 The main technical points of the multi-level requirement tracing and verification method for ship information systems of the present invention in this embodiment are as follows: (1) By analyzing the demand traceability relationship between the surface vessel information system, subsystems, and equipment, the demand traceability relationship can be constructed. In the current system, select the source item and the target item in the new association window to establish a link relationship of the selected link type and direction between the source and target items. View the associated upstream and downstream demand items through the link indicator, and by clicking on the demand item in the link indicator, you can penetrate to the project where that item is located and accurately locate the corresponding row. For details on demand relationship construction and the location of associated demands, see [link to relevant documentation]. Figure 6 By fully constructing the traceability and correlation relationships of requirements at all levels, a comprehensive overview of ship information relationships can be formed.

[0024] (2) Based on the requirements for ship information system verification, define automated inspection rules for requirements correctness, completeness, consistency, and traceability in the verification criteria library, including setting keywords and logical operators (include, exclude). See the requirements checklist and inspection item definition interface. Figure 7 Based on the traceability relationship between system requirements, subsystem requirements, and subsystem requirements, a requirement rationality verification matrix is ​​constructed for downstream solution domain requirements by creating a link analysis column, which intuitively displays the upstream requirement information associated with each downstream requirement.

[0025] (3) Before submitting the requirement documents for verification and review, the requirement documents can be self-checked through the automated verification and inspection function. The scope of the inspection mainly includes automated verification and inspection of correctness, consistency, completeness, traceability, etc., and generates a "list of non-conforming requirements".

[0026] (4) After the requirements review is submitted, reviewers receive the review tasks in their respective to-do lists, open the requirements verification matrix view of the submitted document in the task interface, and have multiple reviewers simultaneously fill in their respective review comments on the requirements items in a single submitted document, as well as provide overall review comments on the submitted document through the requirements checklist. System designers or requirements managers can modify the requirements based on the issue list in each requirements review record. After modification, the requirements rationality verification activity (including automated verification and manual verification) is executed again until all issues are closed. The requirements review results are shown in [link to relevant documentation]. Figure 8 .

[0027] (5) Construct a requirements verification plan based on the requirements verification needs of the ship information system, and define the requirements verification activities. Establish a traceability relationship between the verification plan and the requirements documents to be verified, and map the verification activities to the requirements items they cover through links. Through this link, a closed loop of content between the verification plan and the requirements documents is formed, and the requirements items and their corresponding verification activities can be traced back to each other. The association relationship between requirements activities and requirements items is constructed as follows: Figure 9As shown, the final analysis based on the verification activity results determines whether the requirements have been verified and updates the relevant attribute values ​​of the verification matrix in the requirements document (including: verification maturity, verification status, and verification rejection reasons). The requirement verification results and the updated requirements matrix verification results are as follows: Figure 10 and Figure 11 As shown.

[0028] Example 3 See Figure 12 The multi-level requirement traceability and verification device for ship information systems of the present invention includes the following components: The requirements statistics and traceability module is built on the Spring Boot framework to create a unified requirements information architecture. It enables complex relationships and traceability between requirements, as well as statistical results on the number of requirements and requirement coverage. It also provides an intuitive display of requirements traceability relationships and results. Custom module for requirement verification criteria and verification matrix: Based on requirement traceability and requirement results, automated requirement checking is achieved through custom keywords and requirement verification conditions; Requirement rationality verification module: Based on requirement verification criteria, it realizes automated requirement verification. According to predefined verification criteria, it automatically scans requirement documents and extracts non-compliant requirements. Through the requirement online review function, multiple people can participate in requirement verification activities at the same time. It also allows manual inspection of submitted requirements and recording of review issues.

[0029] Key technical points and principles of this invention: This invention belongs to the field of computer software technology for R&D management, specifically involving a method for verifying the rationality of requirements for a ship information system. Based on the Java language and the Spring Boot framework, it enables convenient visual analysis and verification of the completeness, consistency, correctness, and conformity (to upstream requirements) of the downstream formal requirement model description based on top-level requirements and verification criteria.

[0030] Therefore, this invention aims to study a formalized requirement rationality verification method tailored to the characteristics of ship information systems. This method enables the comprehensive management of detailed requirements generated during system design, constructs a requirement system, and assists system designers in confirming that system requirements are consistent and conflict-free, and that the system requirement descriptions are logically complete. Furthermore, when top-level system requirements change, this invention supports rapid multi-level requirement logic consistency verification and dynamic updates, allowing for the examination of requirements to be changed from different dimensions and providing reasonable comprehensive evaluation results.

[0031] This invention has been tested on a virtual-real fusion test platform of a ship information system, and the application effect is good.

[0032] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

[0033] The contents not described in detail in this specification are existing technologies known to those skilled in the art.

Claims

1. A method for multi-level requirement tracing and verification of a ship information system, characterized in that: Includes the following steps: S1. Requirements Statistics and Traceability: Based on the Spring Boot framework, a unified requirements information architecture is built to realize complex relationships and traceability between requirements items, as well as statistical results of the number of requirements and requirement coverage, and to intuitively display the requirements traceability relationship and requirements results. S2, Customization of Requirement Verification Criteria and Verification Matrix: Based on requirement traceability and requirement results, automated requirement checks are achieved through custom keywords and requirement verification conditions; S3. Requirement rationality verification: Based on requirement verification criteria, the requirement documents are automatically scanned and non-compliant requirements are extracted according to predefined verification criteria. Through the online requirement review function, multiple people can participate in the requirement verification activities at the same time. The submitted requirements are manually checked and review issues are recorded.

2. The method for multi-level requirement tracing and verification of ship information systems according to claim 1, characterized in that: In step S1, the complex relationships and traceability between demand items, as well as the statistical results of demand quantity and demand coverage, are realized by fully constructing the demand traceability relationship at each level to form a ship information relationship overview diagram.

3. The method for multi-level requirement tracing and verification of ship information systems according to claim 2, characterized in that: In step S1, the specific process of constructing a complete overview of ship information relationships by establishing the traceability relationships of each level of requirements is as follows: S11. By analyzing the demand traceability relationship between the surface vessel information system, subsystems, and equipment, the demand traceability relationship is constructed. S12. Select the source entry in the current system and the target entry in the new association window to establish the association relationship between the source entry and the target entry based on the selected link type and direction; S13. Use the link indicator to view the associated upstream and downstream requirement items, and click on the requirement item in the link indicator to penetrate to the project where the item is located, and accurately locate the row of the corresponding item.

4. The multi-level requirement traceability and verification method for ship information systems according to claim 3, characterized in that: The specific process of step S2 is as follows: S21. Based on the ship information system, customize inspection rules to achieve automated screening of the correctness, completeness, consistency, and traceability of requirements; S22. Display the established and associated requirements information at all levels in a list as attribute columns to form a complete requirements verification matrix.

5. The multi-level requirement traceability and verification method for ship information systems according to claim 4, characterized in that: In step S21, the custom verification rules include setting keywords corresponding to the ship information system and logical operators such as "included" and "not included".

6. The multi-level requirement traceability and verification method for ship information systems according to claim 5, characterized in that: The specific process of step S22 is as follows: Based on the traceability relationship between system requirements, subsystem requirements and subsystem requirements, a requirement rationality verification matrix is ​​constructed for downstream solution domain requirements by creating a link analysis column, which displays the upstream requirement information associated with each downstream requirement.

7. The method for multi-level requirement tracing and verification of ship information systems according to claim 6, characterized in that: The specific process of step S3 is as follows: S31. Before submitting the requirement documents for verification and review, the requirement documents shall be self-checked through the automated verification and inspection function. The scope of the inspection includes automated verification and inspection of correctness, consistency, completeness and traceability, and generates a "list of non-conforming requirements". S32. After submitting the requirements review, receive the review tasks in the to-do list, open the requirements verification matrix view of the submitted document, have multiple people fill in their respective review comments on the requirements items in a submitted document in parallel, and make overall review comments on the submitted document through the requirements checklist. Modify the requirements based on the problem list in each requirements review record, and perform the requirements rationality verification activity multiple times until all problems are resolved.

8. The method for multi-level requirement tracing and verification of ship information systems according to claim 7, characterized in that: In step S32, the specific process of repeatedly executing requirement rationality verification activities until all problems are resolved is as follows: requirement items and corresponding verification activities are traced back to each other, and finally, the results of the verification activities are analyzed to determine whether the requirement has been verified and the relevant attribute values ​​of the verification matrix in the requirement document are updated.

9. The method for multi-level requirement tracing and verification of ship information systems according to claim 8, characterized in that: In step S32, the relevant attribute values ​​of the verification matrix include: verification maturity, verification status, and verification rejection reason.

10. A multi-level requirement traceability and verification device for a ship information system, comprising a computer program, characterized in that: The computer program is capable of executing the multi-level requirement tracing and verification method for ship information systems as described in any one of claims 1 to 9.

Images