SysML modeling design method for ship pump valve control system

Abstract

The invention discloses a SysML modeling design method for a ship pump valve control system, and belongs to the field of digital modeling design, and the method comprises the steps: building a user demand diagram of the ship pump valve control system through a modeling software tool based on a SysML modeling language, building a top-layer use case diagram of the ship pump valve control system based on the user demand diagram, and building a top-layer use case diagram of the ship pump valve control system based on the top-layer use case diagram; the method comprises the following steps: constructing a function demand graph and a performance demand graph corresponding to the function demand graph based on a user demand graph and a top-layer use case graph, establishing a corresponding module definition graph according to each function demand in the function demand graph based on the performance demand graph so as to realize a physical entity of a corresponding function, and further carding the module definition graphs to obtain a physical entity of the corresponding function; and obtaining an object implementation module corresponding to each function demand in the function demand diagram, thereby constructing a hardware equipment scheme, and completing SysML modeling design of the ship pump valve control system. The traceability and consistency in the ship system design process are enhanced, and effective assistance is provided for rapid iteration updating of a design scheme.

Description

Technical Field

[0001] The present application relates to the technical field of digital modeling and design, and more specifically, to a SysML modeling and design method for a ship pump and valve control system. Background Art

[0002] Marine pump and valve systems provide various circulating power and control mechanisms for ship operations, and are crucial for ensuring the normal and stable operation of marine systems. During the development of marine pump and valve control systems, they require a thorough design demonstration. Current design methods are mostly document-based, resulting in a series of design documents. These methods have several drawbacks, such as the fact that design information is implicit within the documents, making it difficult to effectively communicate across design stages and making it difficult to consistently update information as it changes.

[0003] Model-based systems engineering (MBSE) is a systems engineering approach to product design that applies modeling. It can be used to support system requirements, design, and verification, and possesses design capabilities across all stages of a product's lifecycle. This effectively enhances traceability and consistency throughout the product design process, and facilitates the rapid iterative design and verification of different solutions. In the practice of MBSE, a modeling language is used to create models of a system's requirements, structure, behavior, and constraints. SysML, a graphical modeling language, is a commonly used modeling language. It can be used to visualize and communicate the design of sociotechnical systems of all sizes—systems composed of hardware, software, data, people, and processes. It can be used to specify, analyze, design, verify, and test complex systems engineering projects.

[0004] Traditional ship pump and valve control system design mostly adopts document-based methods. The design results are not intuitive, it is difficult to effectively transmit design information at each design stage, and it is difficult to update the design consistently when changes occur. Summary of the Invention

[0005] An embodiment of the present invention provides a SysML modeling and design method for a ship pump and valve control system, which is used to solve the problems in the prior art that traditional ship pump and valve control system designs mostly adopt a document-based method, resulting in unintuitive design results, difficulty in effectively transmitting design information at various design stages, and difficulty in consistent updating when the design changes. It enhances the traceability and consistency of the ship system design process and effectively facilitates the rapid iterative update of design solutions.

[0006] An embodiment of the present invention provides a SysML modeling and design method for a ship pump and valve control system, the method comprising: A user requirement diagram for a ship pump and valve control system is established using a modeling software tool based on the SysML modeling language; the user requirement diagram is used to indicate the control requirement information of crew members in different positions on the ship pump and valve control system; Constructing a top-level use case diagram of a ship pump and valve control system based on the user demand diagram; constructing a functional requirement diagram and a performance requirement diagram corresponding to the functional requirement diagram based on the user demand diagram and the top-level use case diagram; Based on the performance requirement diagram and according to each functional requirement in the functional requirement diagram, a corresponding module definition diagram is established to realize a physical entity of the corresponding function; Comb through the module definition diagram to obtain the object implementation module corresponding to each functional requirement in the functional requirement diagram; Based on the physical implementation module, a hardware equipment solution is established to complete the SysML modeling design of the ship pump and valve control system.

[0007] According to the SysML modeling and design method of the ship pump and valve control system, the functional requirement diagram includes: parameter measurement function, manual control function, remote operation function, automatic control function, and operation monitoring function.

[0008] According to the SysML modeling and design method for the ship pump and valve control system, a functional requirement diagram and a performance requirement diagram corresponding to the functional requirement diagram are constructed based on the user requirement diagram and the top-level use case diagram, including: Construct a functional requirement diagram based on the user requirement diagram and the top-level use case diagram according to the requirement relationship; the requirement relationship includes inclusion, tracking, inheritance, improvement, satisfaction and verification; Based on the functional requirement diagram, a corresponding performance requirement diagram is constructed according to the performance requirements; the performance requirements include but are not limited to ambient temperature, control algorithm performance, measurement accuracy and usage time.

[0009] According to the SysML modeling and design method of the ship pump and valve control system, the top-level use case diagram of the ship pump and valve control system is constructed based on the user requirement diagram; Establish user-triggered functional scenarios based on the user needs to define how users trigger system functions; The functional scenarios are constructed based on the functional scenarios to define how the system responds and acts on the controlled objects, thereby obtaining a top-level use case diagram.

[0010] According to the SysML modeling and design method for the ship pump and valve control system, the top-level use case diagram includes a monitoring use case diagram, which is used to indicate the operation monitoring information of the crew and the ship pump and valve control system.

[0011] According to the SysML modeling and design method for the ship pump and valve control system, after establishing a corresponding module definition diagram based on the performance requirement diagram and each functional requirement in the functional requirement diagram to realize the physical entity of the corresponding function, it also includes constructing an internal module diagram for the module definition diagram to indicate the specific device model of the target equipment or device.

[0012] According to the SysML modeling and design method of the ship pump and valve control system, the hardware equipment solution is established based on the physical implementation module, including: Based on the physical implementation modules, build the upper-level module definition diagram to form the target device or apparatus; Combining is performed based on the target device or apparatus to obtain the target device or apparatus.

[0013] According to the SysML modeling and design method of the ship pump and valve control system, the modeling software tools include Cameo Systems Modeler, Rhapsody and ZESOFT.

[0014] In general, the above technical solutions conceived by the present invention can achieve the following beneficial effects compared with the prior art: This application can systematically integrate the differentiated needs of crew members in different positions through the construction of user requirement diagrams. In the linkage modeling of the top-level use case diagram and the functional requirement diagram, the interaction scenarios between crew members and the system are accurately mapped to the functional logic chain, ensuring that the functional closed-loop verification is achieved in the early stage of design, reducing the risk of rework in the later stage. Through the collaborative design of the performance requirement diagram and the module definition diagram, the abstract description in the functional requirements is decomposed layer by layer into quantifiable performance indicators and corresponding physical modules. In addition, the hierarchical construction mechanism of the module definition diagram supports the modular reorganization of physical entities, and ultimately forms a flexible and configurable hardware equipment solution, which significantly reduces the hardware reconstruction cost caused by design iterations. It is possible to optimize algorithm parameters or adjust hardware redundancy strategies in the model stage, and solve defects in traditional ship design that can only be discovered through physical prototype testing in the early stage of design, shorten the development cycle, enhance the traceability and consistency in the ship system design process, and provide effective support for the rapid iteration and update of design solutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0016] Figure 1 A flowchart of an optional SysML modeling and design method for a ship pump and valve control system provided in an embodiment of the present application; Figure 2 A schematic diagram of the structure of the functional requirements of an optional ship pump and valve control system provided in an embodiment of the present application; Figure 3A schematic diagram of the module definition structure of an optional monitoring console device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0017] In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely for the purpose of explaining the present invention and are not intended to limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.

[0018] The terms "first," "second," "third," and the like in the specification and claims of this application and the accompanying drawings are used to distinguish between different objects, not to describe a particular order. Furthermore, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0019] Below, the exemplary embodiments according to the present application will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application, and it should be understood that the present application is not limited to the exemplary embodiments described herein.

[0020] Application Overview Traditional ship pump and valve control system design often uses a document-based approach, resulting in non-intuitive design results, making it difficult to effectively communicate design information across the design stages, and making it difficult to consistently update design changes. This application proposes a SysML modeling and design approach for ship pump and valve control systems that enhances traceability and consistency during the ship system design process and facilitates rapid iteration and updating of design solutions.

[0021] Exemplary Methods Figure 1 A flowchart illustrating a SysML modeling and design method for a ship pump and valve control system according to an embodiment of the present application is shown. like Figure 1 As shown, the SysML modeling and design method of the ship pump and valve control system according to the embodiment of the present application includes: S101, establish the user requirement diagram of the ship pump and valve control system using modeling software tools based on the SysML modeling language.

[0022] Among them, the user demand diagram is used to indicate the control demand information of crew members in different positions for the ship's pump and valve control system.

[0023] S102: Construct a top-level use case diagram of a ship pump and valve control system based on the user demand diagram.

[0024] S103, constructing a functional requirement diagram and a performance requirement diagram corresponding to the functional requirement diagram based on the user requirement diagram and the top-level use case diagram; S104, establishing a corresponding module definition diagram according to each functional requirement in the functional requirement diagram based on the performance requirement diagram, so as to realize a physical entity of the corresponding function; S105, combing the module definition diagram to obtain the object implementation module corresponding to each functional requirement in the functional requirement diagram; S106: Based on the physical implementation module, a hardware equipment solution is established to complete the SysML modeling design of the ship pump and valve control system.

[0025] During the implementation process, model-based systems engineering (MBSE) is a design method whose practice requires modeling languages ​​and tools. Choose the SysML modeling language and a suitable modeling software tool. Common modeling software tools include Cameo Systems Modeler and IBM's Rhapsody. You can also choose domestically produced modeling software tools developed by domestic companies.

[0026] This application adheres to the principles of MBSE (Model-Based Systems Engineering) and utilizes the SysML modeling language to enable full lifecycle requirements tracking and design iteration. For example, in S101, Cameo Systems Modeler can be used to create a user requirements diagram, distinguishing the differing requirements of different roles, such as the chief engineer, operator, and maintenance engineer. The chief engineer focuses on system-level safety redundancy (e.g., dual-pump backup logic), the operator requires interface operation steps to be no more than three clicks, and the maintenance technician requires standardized fault diagnosis codes. These requirements are tied to subsequent design elements using SysML "trace" relationships to ensure design traceability. Functional requirements are mapped to physical entities using module definition diagrams. For example, the "automatic control function" can be broken down into PLC control modules and signal isolation modules. Specific model parameters, such as the ABB ACS880 inverter, are specified using internal module diagrams. Ultimately, this is combined into a hardware solution for a distributed control cabinet, completing the SysML modeling design of the ship's pump and valve control system.

[0027] Preferably, the functional requirements diagram should include parameter measurement, manual control, remote operation, automatic control, and operation monitoring. The parameter measurement function must define the sensor type and data interface, such as a PT100 temperature sensor using the Modbus RTU protocol. The manual control function must clearly define the emergency operation priority, such as independent control of the "emergency stop" button through a hardwired loop. The remote operation function must specify the communication protocol (such as OPC UA) and encryption mechanism. The "historical query" subfunction of the operation monitoring function must be associated with a database module, such as the SQLite embedded database, and demonstrated through a "satisfy" relationship that it meets the user requirement of "data storage ≥ 30 days."

[0028] Preferably, the step of constructing a functional requirement diagram and a performance requirement diagram corresponding to the functional requirement diagram based on the user requirement diagram and the top-level use case diagram includes: Construct a functional requirement diagram based on the user requirement diagram and the top-level use case diagram according to the requirement relationship; the requirement relationship includes inclusion, tracking, inheritance, improvement, satisfaction and verification; Based on the functional requirement diagram, a corresponding performance requirement diagram is constructed according to the performance requirements; the performance requirements include but are not limited to ambient temperature, control algorithm performance, measurement accuracy and usage time.

[0029] For example, the "automatic control function" inherits the underlying driver interface of the "manual control function" through the "inherit" relationship; the "measurement accuracy" requirement is linked to the AD converter resolution (such as a 16-bit ADC) in the module definition diagram through the "verify" relationship. The performance requirement diagram should quantify environmental adaptability indicators and verify design rationality through thermodynamic simulation parameter diagrams.

[0030] Preferably, the top-level use case diagram of the ship pump and valve control system is constructed based on the user demand diagram; Establish user-triggered functional scenarios based on the user needs to define how users trigger system functions; The functional scenarios are constructed based on the functional scenarios to define how the system responds and acts on the controlled objects, thereby obtaining a top-level use case diagram.

[0031] When creating a top-level use case diagram for a ship's pump and valve control system, it's necessary to establish crew inputs to the control system, such as switch operation, button operation, and automatic operation, as well as outputs from the control system, such as control signals. For example, in the "Automatic Operation" use case, after the crew triggers automatic mode, the system must execute a self-check process (use case extension point), verifying that the pump and valve are in normal condition and then initiating the PID control algorithm. When refining the operation monitoring sub-use case diagram, for example, the "Touch Switch" input must be mapped to the multi-touch protocol of the HMI, while the "Monitoring Information Display" output must meet the visibility requirements of the MIL-STD-1472G military standard (character height ≥ 4.8mm).

[0032] Preferably, the top-level use case diagram includes a monitoring use case diagram, which is used to indicate the operation monitoring information of the crew and the ship's pump and valve control system.

[0033] If detailed system design is required, the use case diagram can be further refined. For example, for the operation monitoring function of a ship's pump and valve control system, an operation monitoring sub-use case diagram can be created, including the crew and the operation monitoring portion of the ship's pump and valve control system. Crew input to the operation monitoring portion, such as keyboard operation and touch switching, can be established, as well as output from the operation monitoring portion, such as the display of monitoring information. For example, the "Alarm Log Display" sub-use case needs to define an alarm classification strategy: a level 1 alarm (such as a pump overload) triggers an audible and visual alarm and automatically stops the pump, while a level 2 alarm (such as a clogged filter) simply flashes the screen. These sub-use cases are included in the top-level use case through an "include" relationship.

[0034] Preferably, after establishing a corresponding module definition diagram based on the performance requirement diagram and each functional requirement in the functional requirement diagram to realize the physical entity of the corresponding function, it also includes constructing an internal module diagram for the module definition diagram to indicate the specific device model of the target equipment or device.

[0035] When building the internal module diagram of the touch screen, you need to define the ITO coating thickness of the capacitive touch panel (such as 100nm), the driver IC model (such as CY8C4014), and allocate the refresh rate indicator (60Hz) to the display chip (such as RA8875) through the "allocate" relationship.

[0036] Preferably, establishing a hardware device solution based on the physical implementation module includes: Based on the physical implementation modules, build the upper-level module definition diagram to form the target device or apparatus; Combining is performed based on the target device or apparatus to obtain the target device or apparatus.

[0037] For example, a centralized solution uses a Siemens SIMATIC PCS 7 integrated controller to integrate all functions; a distributed solution separates remote I / O stations (using the WAGO 750 series) and independent monitoring terminals (Advantech PPC-3150), connected via a redundant PROFINET ring. Both solutions require verification of communication latency (≤100ms) through inter-block interface definitions in the SysML model.

[0038] Preferably, the DoDAF plug-in of Cameo Systems Modeler is used to implement compliance checks with ship design specifications (such as GL rules), while the collaborative modeling function of Rhapsody supports parallel development by multiple teams, such as automatically generating the IEC 61131-3 structured text code framework through the requirements matrix.

[0039] The following is a specific example for explanation.

[0040] In the specific implementation process, the following steps can be used to implement the SysML modeling design method of the ship pump and valve control system: Step 1, select the SysML modeling language and choose a suitable modeling software tool.

[0041] Step 2: Use modeling software tools to establish a user requirement diagram for the ship pump and valve control system, listing the requirements of crew members in different positions for the ship pump and valve control system, such as operation requirements, monitoring requirements, maintenance requirements, etc.

[0042] Step 3: Use the modeling software tool to create a top-level use case diagram for the ship pump and valve control system, including the crew, the controlled ship pump and valve, and the ship pump and valve control system. Here, the crew's input to the control system is established, such as switch operation, button operation, automatic operation, etc., and the output of the control system is established, such as control signals.

[0043] Step 4. If detailed design of the system is required, the use case diagram can be further refined. For example, for the operation monitoring function of the ship's pump and valve control system, an operation monitoring sub-use case diagram can be established, including the crew and the operation monitoring part of the ship's pump and valve control system, and the crew's input to the operation monitoring part can be established, such as keyboard operation, touch switching, etc., and the output of the operation monitoring part can be established, such as monitoring information display.

[0044] Step 5: After building the use case diagram, start building the requirement diagram. There are two types of requirement diagrams: functional requirement diagram and performance requirement diagram. First, build the functional requirement diagram of the ship pump and valve control system, including what functions the control system needs to have, such as parameter measurement function, manual control function, automatic control function, operation monitoring function, etc. Figure 2 shown.

[0045] In step 6, when modeling the requirements graph, you may also use six types of requirements relationships: include, trace, inherit, improve, satisfy, and verify. After establishing a relatively high-level requirements graph, you can further develop detailed functional requirements graphs for situations that require detailed design. For example, you can develop a functional requirements graph for the operation monitoring function and specifically list relevant functional requirements, such as interactive input, parameter display, curve display, and historical query.

[0046] Step 7: After establishing the functional requirements diagram, a corresponding performance requirements diagram should also be established. Establishing a performance requirements diagram for the ship's pump and valve control system involves quantitative indicator requirements, including ambient temperature, control algorithm performance, measurement accuracy, and operating time.

[0047] Step 8: For the performance requirements diagram, if there are detailed design requirements, the performance requirements diagram can be further refined. For example, for the operation monitoring subsystem, its performance requirements diagram includes the number of display parameters, screen types, screen size, refresh rate, font size, etc.

[0048] Step 9: Complete the requirements modeling and proceed with the structural diagram modeling. For each functional requirement listed in the functional requirements diagram, create a corresponding module definition diagram to represent the physical entity used to implement the corresponding function. For functional requirements diagrams at different levels, corresponding module definition diagrams can be created at different levels. Modules with functional inheritance relationships between different levels can be merged and reorganized. Based on experience, a better approach is to select the next level functional requirements diagram of the top-level functional requirements to construct the initial module definition diagram.

[0049] Step 10: For the ship pump and valve control system, a module definition diagram is constructed from the requirement diagram level of its parameter measurement function, manual control function, automatic control function, and operation monitoring function.

[0050] Taking the operation monitoring function as an example, based on its interactive input, parameter display, curve display, historical query and other functional requirements, a corresponding module definition diagram is constructed to implement its functions.

[0051] For example, for interactive input, its module definition diagram includes keyboard, touch screen, etc., and the module definition diagram for parameter display includes LCD screen.

[0052] Step 11: After obtaining the module definition diagram corresponding to the functional requirements, the corresponding performance parameter design can be further specified for the relevant modules in the module definition diagram according to the technical indicators listed in the performance requirement diagram.

[0053] Step 12: After completing the module definition diagram, if you need to carry out module development or have requirements for specific device models, you can continue to build an internal module diagram for the module definition diagram, such as building an internal module diagram for a touch screen, including components such as the panel, resistors, capacitors, and display chips.

[0054] Step 13: After sorting out the module definition diagram, the object implementation modules corresponding to the basic functional performance requirements are obtained. These modules are independent physical modules. There are duplications between them during the control system implementation process, and there is also the possibility of merging.

[0055] Step 14: For each module in the module definition diagram, according to the layout and design requirements of the control system, an upper-level module definition diagram can be further constructed. The main purpose is to organize the relevant physical entity modules to form a typical device or apparatus. For example, the keyboard and touch screen for interactive input, the switches and buttons for manual control functions, and the LCD screen for parameter display functions can be combined to form a module definition diagram for the monitoring console device, such as Figure 3 shown.

[0056] In step 15, the modules in each module definition diagram can be combined from different perspectives and approaches to form different hardware solutions for the ship pump and valve control system. For example, it can be implemented as a single large-scale monitoring device with complete measurement, control, and operation monitoring functions; it can also be implemented as three independent devices that perform measurement and acquisition, control algorithms, and operation monitoring functions respectively, or other equipment organization design methods can be used.

[0057] Step 16: At this point, the SysML modeling design for the ship pump and valve control system has been completed, including use cases, functional requirements, performance requirements, module composition, and equipment solutions. Subsequent changes can be updated uniformly within the modeling tool, allowing for linked updates of design results with include, trace, and inheritance relationships.

[0058] In summary, the SysML modeling and design method for a ship pump and valve control system proposed in this application can enhance the traceability and consistency of the ship system design process and facilitate the rapid iterative update of the design scheme.

[0059] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0060] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0061] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0062] In the several embodiments provided in this application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interface, and the indirect coupling or communication connection of the device or unit can be electrical or other forms.

[0063] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0064] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0065] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a memory and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned memory includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, magnetic disk, or optical disk, etc., various media that can store program code.

[0066] Those skilled in the art will appreciate that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable memory, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0067] The above is only an exemplary embodiment of the present disclosure and cannot be used to limit the scope of the present disclosure. That is, any equivalent changes and modifications made according to the teachings of the present disclosure are still within the scope of the present disclosure. After considering the specification and practicing the disclosure herein, those skilled in the art will easily think of the implementation scheme of the present disclosure. This application is intended to cover any variation, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the art that are not recorded in the present disclosure. The description and examples are to be regarded as exemplary only, and the scope and spirit of the present disclosure are defined by the claims.

[0068] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0069] It will be easily understood by those skilled in the art that the above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A SysML modeling and design method for a ship pump and valve control system, characterized in that: include: Based on the SysML modeling language, a modeling software tool is used to establish the user requirements diagram of the ship pump and valve control system; The user demand diagram is used to indicate the control demand information of crew members in different positions on the ship's pump and valve control system; Constructing a top-level use case diagram of a ship pump and valve control system based on the user demand diagram; constructing a functional requirement diagram and a performance requirement diagram corresponding to the functional requirement diagram based on the user demand diagram and the top-level use case diagram; Based on the performance requirement diagram and according to each functional requirement in the functional requirement diagram, a corresponding module definition diagram is established to realize a physical entity of the corresponding function; Comb through the module definition diagram to obtain the object implementation module corresponding to each functional requirement in the functional requirement diagram; Based on the physical implementation module, a hardware equipment solution is established to complete the SysML modeling design of the ship pump and valve control system.

2. The SysML modeling and design method for a ship pump and valve control system according to claim 1, characterized in that: The functional requirement diagram includes: parameter measurement function, manual control function, remote operation function, automatic control function, and operation monitoring function.

3. The SysML modeling and design method for a ship pump and valve control system according to claim 2, characterized in that: Constructing a functional requirement diagram and a performance requirement diagram corresponding to the functional requirement diagram based on the user requirement diagram and the top-level use case diagram, including: Construct a functional requirement diagram based on the user requirement diagram and the top-level use case diagram according to the requirement relationship; the requirement relationship includes inclusion, tracking, inheritance, improvement, satisfaction and verification; Based on the functional requirement diagram, a corresponding performance requirement diagram is constructed according to the performance requirements; the performance requirements include but are not limited to ambient temperature, control algorithm performance, measurement accuracy and usage time.

4. The SysML modeling and design method for a ship pump and valve control system according to claim 1, characterized in that: The top-level use case diagram of the ship pump and valve control system is constructed based on the user demand diagram; Establish user-triggered functional scenarios based on the user needs to define how users trigger system functions; The functional scenarios are constructed based on the functional scenarios to define how the system responds and acts on the controlled objects, thereby obtaining a top-level use case diagram.

5. The SysML modeling and design method for a ship pump and valve control system according to claim 1, characterized in that: The top-level use case diagram includes a monitoring use case diagram, which is used to indicate operation monitoring information of crew members and ship pump and valve control systems.

6. The SysML modeling and design method for a ship pump and valve control system according to claim 1, characterized in that: The method of establishing a corresponding module definition diagram based on the performance requirement diagram according to each functional requirement in the functional requirement diagram to realize the physical entity of the corresponding function also includes constructing an internal module diagram for the module definition diagram to indicate the specific device model of the target equipment or device.

7. The SysML modeling and design method for a ship pump and valve control system according to claim 1, characterized in that: The step of establishing a hardware device solution based on the physical implementation module includes: Based on the physical implementation modules, build the upper-level module definition diagram to form the target device or apparatus; Combining is performed based on the target device or apparatus to obtain the target device or apparatus.

8. The SysML modeling and design method for a ship pump and valve control system according to claim 1, characterized in that: The modeling software tools include Cameo Systems Modeler, Rhapsody and ZESOFT.

Images