Laser fusion ultrafast imaging instrument logic design method and system based on MBSE

Abstract

The invention belongs to the technical field of model-based system engineering, and relates to an MBSE-based laser fusion ultrafast imaging instrument logic design method and system, and the method comprises the steps: obtaining system indexes of an ultrafast imaging instrument through operation analysis based on the demand information of the ultrafast imaging instrument; based on system index identification, acquiring components required for achieving the system indexes, and configuring component indexes by decomposing the system indexes; modules required for achieving component indexes are obtained based on component index identification, and module indexes are configured by decomposing the component indexes. According to the method, a multilevel bidirectional traceable relation matrix is established in ultrafast imaging instrument collaborative development, bidirectional traceable links are established among user requirements, service cases and indexes of all levels, and it is ensured that any modification can be subjected to influence analysis, so that information consistency is improved; through standardized and visual models such as service cases and activity diagrams, an unambiguous common understanding basis is provided for different teams, and team cooperation is promoted.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of model-based system engineering, and discloses a laser fusion superfast imaging instrument logic design method and system based on MBSE. BACKGROUND

[0002] Inertial confinement fusion experiments need to use several superfast imaging instruments (i.e. diagnostic instruments) to diagnose and characterize transient microscale physical processes. With the deepening of the research on inertial confinement fusion, the fusion experiment requires that the diagnostic instrument can complete the design of a high-reliability instrument deeply matched with the physical scene in a shorter time.

[0003] Traditional diagnostic instrument architecture design mainly adopts a document-based design method. With the sharp increase in engineering scale and complexity, the traditional document-based design method gradually exposes problems such as low efficiency, inconsistent information, and difficult collaboration. Compared with document-based system engineering, model-based system engineering (MBSE) adopts a model-centered method and covers the entire life cycle of a complex system. By replacing traditional documents, voice recordings, videos and tables with models, the design requirements, interface requirements, performance requirements, functions, indexes and schemes are met, and a unified standard model is established for updating, so as to realize the maintenance and updating iteration of the complex system.

[0004] The application provides a laser fusion diagnostic instrument logic design method based on model-based system engineering (Model Based System, MBSE), so as to realize the model expression of key design elements such as requirements, behaviors, architectures and parameters by creating an executable and reusable system model, and to improve the design efficiency and solve the problem of difficult collaboration. SUMMARY

[0005] The application aims to provide a laser fusion superfast imaging instrument logic design method and system based on MBSE, solve the problem of low efficiency faced by the traditional diagnostic instrument architecture design which adopts a document-based design method, and the specific scheme is as follows: In a first aspect, a laser fusion superfast imaging instrument logic design method based on MBSE is provided, including the following steps: Based on the requirement information of the superfast imaging instrument, the system indexes of the superfast imaging instrument are obtained by running analysis; Based on the system index identification, the components required to achieve the system indexes are obtained, and the component indexes are configured by decomposing the system indexes; Based on the component index identification, the modules required to achieve the component indexes are obtained, and the module indexes are configured by decomposing the component indexes.

[0006] Further, the requirement information based on the ultrafast imaging instrument is obtained, and system indexes of the ultrafast imaging instrument are acquired through operation analysis, including: obtaining requirement information of the ultrafast imaging instrument, and identifying functional class requirements in the requirement information; obtaining service use cases of the ultrafast imaging instrument based on the functional class requirements, identifying participating objects through the service use cases, and associating the participating objects with corresponding service use cases, and configuring logical interfaces of the system and the participating objects based on interaction types; obtaining system indexes of the ultrafast imaging instrument based on the service use cases, the logical interfaces, and the participating objects interacting with the system when the service use cases are implemented.

[0007] Further, the required components for achieving the system indexes are identified based on the system indexes, and component indexes are configured through decomposition of the system indexes, including: classifying the system indexes to obtain a plurality of first sub-requirements, and establishing a bidirectional traceability relationship matrix among the first sub-requirements, the service use cases, and user requirements; obtaining a first activity graph for implementing the service use cases based on the plurality of first sub-requirements of the system indexes; the first activity graph includes a plurality of first flow nodes for implementing the service use cases, and each first flow node corresponds to a component requirement; identifying and obtaining components based on the first activity graph, associating the components with the first flow nodes in the first activity graph, configuring component functions, and configuring corresponding logical interfaces of the components based on interaction types; configuring component indexes based on process activities to be performed by the components.

[0008] Further, the required modules for achieving the component indexes are identified based on the component indexes, and module indexes are configured through decomposition of the component indexes, including: classifying the component indexes to obtain a plurality of second sub-requirements, and establishing a bidirectional traceability relationship matrix among the second sub-requirements, the service use cases, and system requirements; obtaining a second activity graph for implementing the system indexes based on the plurality of second sub-requirements of the component indexes; the second activity graph includes a plurality of second flow nodes for implementing the system indexes, and each second flow node corresponds to a module requirement; identifying and obtaining modules based on the second activity graph, associating the modules with the second flow nodes in the second activity graph, configuring module functions, and configuring corresponding logical interfaces of the modules based on interaction types; configuring module indexes based on process activities to be performed by the modules; classifying the module requirements to obtain a plurality of third sub-requirements, and establishing a bidirectional traceability relationship matrix among the third sub-requirements, the service use cases, and component requirements.

[0009] Further, the interaction types include matter, energy and information, wherein the matter interaction includes at least a physical installation interface with the vacuum chamber and an optical path interface, the energy interaction includes at least a power supply for the camera module, and the information interaction includes at least an image data stream, a trigger signal and a control instruction.

[0010] Further, when the first activity graph cannot completely express the behavior characteristics of the service use case, a state machine graph is used to express the behavior characteristics of the service use case. When the second activity graph cannot completely express the behavior characteristics of the component, a state machine graph is used to express the behavior characteristics of the component.

[0011] In a second aspect, an MBSE-based laser fusion ultrafast imaging instrument logic design system is provided, including: An operation analysis layer is configured to obtain system indexes of the ultrafast imaging instrument through operation analysis based on requirement information of the ultrafast imaging instrument. A system design layer is configured to identify components required to achieve the system indexes based on the system indexes, and configure component indexes through decomposition of the system indexes. A component design layer is configured to identify modules required to achieve the component indexes based on the component indexes, and configure module indexes through decomposition of the component indexes.

[0012] Further, the requirement information of the ultrafast imaging instrument is obtained through operation analysis to obtain the system indexes of the ultrafast imaging instrument, including: Requirement information of the ultrafast imaging instrument is obtained, and functional class requirements in the requirement information are identified. Service use cases of the ultrafast imaging instrument are obtained based on the functional class requirements, participating objects are identified through the service use cases, the participating objects are associated with corresponding service use cases, and logical interfaces between the system and the participating objects are configured based on interaction types. System indexes of the ultrafast imaging instrument are obtained based on the service use cases, the logical interfaces and the participating objects interacting with the system when the service use cases are implemented.

[0013] Further, the components required to achieve the system indexes are identified based on the system indexes, and the component indexes are configured through decomposition of the system indexes, including: The system indexes are classified to obtain a plurality of first sub-requirements, and a bidirectional traceability matrix between the first sub-requirements, the service use cases and user requirements is established. Based on the plurality of first sub-requirements of the system indexes, a first activity graph for implementing the service use cases is obtained; the first activity graph includes a plurality of first flow nodes for implementing the service use cases, and each first flow node corresponds to a component requirement. The component is associated with a first flow node in the first activity graph based on the first activity graph identification acquisition component, and the component function is configured, and the component corresponding logical interface is configured based on the interaction type; The component index is configured based on the process activity to be performed by the component.

[0014] Further, the module required to achieve the component index is identified based on the component index, and the module index is configured through the decomposition of the component index, including: The component index is classified to obtain a plurality of second sub-requirements, and a bidirectional traceability relationship matrix between the second sub-requirements, the service use case and the system requirement is established; The second activity graph for realizing the system index of the component is acquired based on the plurality of second sub-requirements of the component index; the second activity graph includes a plurality of second flow nodes for realizing the system index, and each second flow node corresponds to a module requirement; The module is associated with a second flow node in the second activity graph based on the second activity graph identification acquisition module, and the module function is configured, and the module corresponding logical interface is configured based on the interaction type; The module index is configured based on the process activity to be performed by the module. The module requirement is classified to obtain a plurality of third sub-requirements, and a bidirectional traceability relationship matrix between the third sub-requirements, the service use case and the component requirement is established.

[0015] The beneficial effects of the present application are: By establishing a multi-level bidirectional traceability relationship matrix, bidirectional traceable links are established between user requirements, service use cases, system indexes, component indexes and module indexes, so that any modification can be analyzed to improve information consistency; through standardized and visualized models such as service use cases and activity graphs, a common understanding basis without ambiguity is provided for different professional teams to promote team cooperation. BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1 The flow chart of the laser fusion superfast imaging instrument logic design method based on MBSE of the present application.

[0017] Figure 2 The activity graph instantiation example of the key activity "collecting experimental images" of the superfast imaging instrument.

[0018] Figure 3 The first activity graph modeling process when the service use case UC-001 "ICF transient image collection" is taken as an example.

[0019] Figure 4 The second activity graph modeling process when the imaging detection component "8-frame image collection" is taken as an example. DETAILED DESCRIPTION

[0020] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings can be arranged and designed in various different configurations.

[0021] Embodiment 1 A laser fusion ultrafast imaging instrument logic design method based on MBSE is provided, comprising the following steps: Based on the requirement information of the ultrafast imaging instrument, the system index of the ultrafast imaging instrument is obtained by running analysis; specifically including: obtaining the requirement information of the ultrafast imaging instrument, and identifying the functional class requirements in the requirement information, here the requirement management tool can be used, wherein the requirement information includes user requirements, and the user requirements mainly refer to the performance improvement expectations of the newly designed laser fusion ultrafast imaging instrument. The running analysis here mainly includes: obtaining the functional class requirements, constructing service use cases based on the functional class requirements, identifying the participating objects in the service use cases, and configuring the logic interfaces containing three types of interaction types of matter, energy and information based on the participating objects.

[0022] Based on the functional class requirements, the service use cases of the ultrafast imaging instrument are obtained, the participating objects are identified through the service use cases, and the participating objects are associated with the corresponding service use cases, and then the logic interfaces of the system and the participating objects are configured based on the interaction types.

[0023] It should be noted that the interaction types here and the interaction types later include three types of matter, energy and information; wherein the information interaction at least includes image data flow, trigger signal, control instruction, etc.; the energy interaction at least includes the power provided for the camera module; and the matter interaction at least includes the physical installation interface with the vacuum chamber and the optical path interface, etc.

[0024] Based on the service use cases, the logic interfaces and the participating objects interacting with the system when implementing the service use cases, the system index of the ultrafast imaging instrument is obtained.

[0025] Based on the system index, the components required to achieve the system index are identified, and the component indexes are configured through the decomposition of the system index; specifically including: classifying the system index to obtain a plurality of first sub-requirements, and establishing a bidirectional traceability relationship matrix between the first sub-requirements, the service use cases and the user requirements; that is, the bidirectional link with the upstream service use cases and the user requirements is established in the requirement traceability matrix, and the completeness of the requirement chain is ensured.

[0026] Based on the plurality of first sub-demands of the system index, a first activity graph for realizing the service use case is acquired; the first activity graph comprises a plurality of first flow nodes for realizing the service use case, and each first flow node corresponds to a component demand; it needs to be noted that the activity graph is a view used to convey the dynamic behavior of the system, objects model events, capabilities and data flow through activities, and the system behavior can be allocated to the system structure through activity graph partitioning. In the scheme of the present application, the key activities of the ultrafast imaging instrument in the typical activity "experimental data measurement" are as follows: starting the scanning working mode → setting the scanning gear → setting the CMOS camera external trigger working mode → CMOS camera external trigger image acquisition → closing the power supply of the camera module → acquiring experimental images → closing the power supply of the camera module.

[0027] Based on the first activity graph, a component is identified and acquired, the component is associated with the first flow node in the first activity graph, the component function is configured, and the logical interface corresponding to the component is configured based on the interaction type.

[0028] Based on the flow activity to be performed by the component, a component index is configured.

[0029] Based on the component index, a module required to achieve the component index is identified and acquired, and the module index is configured through decomposition of the component index; specifically, the component index is classified to obtain a plurality of second sub-demands, and a bidirectional traceability relationship matrix between the second sub-demands, the service use case and the system demand is established.

[0030] Based on the plurality of second sub-demands of the component index, a second activity graph for realizing the system index by the component is acquired; the second activity graph comprises a plurality of second flow nodes for realizing the system index, and each second flow node corresponds to a module demand; for example, in the first activity graph described above, taking the key activity "acquiring experimental images" of the ultrafast imaging instrument in the typical activity "experimental data measurement" as an example, the required components include an electron optics system component, a control system component and an imaging system component, each component contains specific activities, that is, each component is associated with the activity it is responsible for, and the component function is configured. For example, the function of the "imaging detection component" is defined as "receiving a trigger signal and exposing, and converting an optical signal into an electrical signal image". As shown in Figure 2 .

[0031] Based on the second activity graph, a module is identified and acquired, the module is associated with the second flow node in the second activity graph, the module function is configured, and the logical interface corresponding to the module is configured based on the interaction type; for example, an "LVDS trigger signal" interface is defined between the "high-speed control component" and the "imaging detection component".

[0032] Based on the flow activity to be performed by the module, a module index is configured.

[0033] The module requirements are classified to obtain a plurality of third sub-requirements, and a two-way traceable relationship matrix between the third sub-requirements, service use cases and component requirements is established.

[0034] It should be further explained that when the first activity diagram cannot completely express the behavior characteristics of the service use case, a state machine diagram is used to express the behavior characteristics of the service use case; and when the second activity diagram cannot completely express the behavior characteristics of the component, a state machine diagram is used to express the behavior characteristics of the component.

[0035] The state machine diagram defines the technical state of the component through a rectangular node, and embeds attribute information corresponding to the technical requirements in the document in the node to realize anchoring of the static behavior characteristics of the component; different state nodes are connected through a conversion edge with an arrow, and a trigger condition bound with the three types of interactions in the document is marked on the edge to realize visual expression of the dynamic behavior characteristics of the component; for the technical requirements of the multi-step process activities that the component needs to perform in the document, the state machine diagram expresses the hierarchical characteristics of the component behavior through nested sub-states (a sub-state machine is contained in the state node), and expresses the real-time behavior through an event response mechanism; the invariant constraint (a technical condition that needs to be continuously met during the state duration) is used to express the persistent behavior characteristics of the component in a certain state, and the constraint condition needs to be based on the technical specifications of the component in the document.

[0036] The scheme establishes a plurality of two-way traceable relationship matrices, establishes two-way traceable links between user requirements, service use cases, system indicators, component indicators and module indicators, ensures that any modification can be analyzed for influence, and then realizes improvement of information consistency; through standardized and visual models such as service use cases and activity diagrams, a common understanding basis without ambiguity is provided for different professional teams, and team cooperation is promoted.

[0037] For the convenience of understanding, the scheme is further illustrated below with an actual design case in combination with the above method scheme.

[0038] Taking an "inertial confinement fusion (ICF) experiment ultrafast frame imaging diagnostic instrument" as a design object, based on the "operation analysis layer -> system design layer -> component design layer" three-level process described in the method, and in combination with specific tools, models and quantitative indicators, the design implementation process is completely presented.

[0039] The design preparation mainly includes target scene definition and tool selection, wherein: The target scene definition is that: aiming at the diagnosis requirement of the "target ball compression transient process (duration ≤100ps, spatial scale ≤500μm)" in the ICF experiment, a ultrafast frame imaging diagnostic instrument is designed, which needs to realize the core functions of "high time resolution, high spatial resolution and real-time data back transmission".

[0040] The specific steps are as follows: I. Operation Analysis Layer: Obtain System Indicators Step 1: Collecting Requirement Information and Identifying Functional Requirements Requirement Information Entry (Create Requirement Module in Requirement Management Tool): User Requirements (from ICF Experimental Requirements): UR-001: Time Resolution ≤ 10 ps; UR-002: Spatial Resolution ≥ 50 lp / mm; UR-003: Single Experiment Can Collect ≥ 8 Frames of Images; UR-004: Image Data Needs to be Transmitted to Experimental Control Center within 1s.

[0041] Identifying Functional Requirements (Extract Executable Functions from User Requirements): FR-001: Receive ICF Target Chamber Trigger Signal and Start Image Acquisition; FR-002: Perform Multi-frame Ultrafast Imaging on Target Projectile Transient Process; FR-003: Convert Collected Image Data to Standard Format (such as TIFF); FR-004: Real-time Data Transmission to External Storage Server through Optical Fiber.

[0042] Step 2: Service Use Case Modeling and Participation Object Association Draw Service Use Case Diagram (Create UML Use Case Diagram in System Architecture Software): Core Service Use Cases: UC-001 "ICF Transient Image Acquisition", UC-002 "Data Format Conversion and Transmission"; Identify Participation Objects (Associated with Use Cases): External Object 1: ICF Target Chamber (Provides Trigger Signal, Associated with UC-001); External Object 2: Experimental Control Center Server (Receives Data, Associated with UC-002); Internal Object: Diagnostics Instrument System (Executes Use Cases UC-001, UC-002).

[0043] Configure Logical Interfaces, Configure According to Three Types of Interaction Types: Matter, Energy, Information, as Shown in Table 1: Table 1: Logical Interface Configuration Example

[0044] Step 3: Determine System Indicators Based on service use cases, logical interfaces and participation object requirements, decompose to obtain system-level quantitative indicators (enter system requirement module): SI-001: Time Resolution ≤ 10 ps (Match UR-001); SI-002: Spatial resolution ≥ 50 lp / mm (match UR-002); SI-003: Single acquisition frame number ≥ 8 frames (match UR-003); SI-004: Data transmission delay ≤ 1 s (match UR-004); SI-005: Trigger signal response time ≤ 1 ns (match trigger interface requirement).

[0045] II. System design layer: configuration components and component indicators Step 1: decompose system indicators into first sub-requirements, and establish a traceability matrix First sub-requirement splitting (decompose system indicators into component-level implementable requirements): SR-001 (corresponding to SI-001 / SI-002 / SI-003): imaging function sub-requirement - need to implement "10 ps exposure control + 50 lp / mm spatial resolution + 8 frame sequence acquisition"; SR-002 (corresponding to SI-005): control function sub-requirement - need to implement "≤ 1 ns trigger signal reception and distribution"; SR-003 (corresponding to SI-004): data processing sub-requirement - need to implement "image format conversion (≤ 500 ms) + 10 Gbps data transmission".

[0046] Establish a two-way traceability relationship matrix (create a two-way traceability table in a requirement management tool): Table 2: Two-way traceability relationship matrix

[0047] Step 2: draw the first activity diagram and identify the core components First activity diagram modeling (take service use case UC-001 "ICF transient image acquisition" as an example, system architecture software drawing) as shown in Figure 3 .

[0048] Identify core components (based on multiple first flow nodes of the first activity diagram, associate components with activities): Component 1: imaging detection component (associated with activities D, E, G - responsible for exposure control and image acquisition); Component 2: high-speed control component (associated with activities B, C - responsible for trigger signal reception and instruction distribution); Component 3: data processing component (associated with activities H, I, J - responsible for image conversion and transmission).

[0049] Step 3: configure component functions, logical interfaces, and component indicators Component function definition: Imaging detection component: receives exposure instructions, realizes 10 ps level ultrafast exposure and multi-frame image acquisition through MCP+CMOS; High-speed control component: receives ICF target chamber LVDS trigger signal, distributes to imaging component within ≤1 ns; Data processing component: receives raw images of imaging component, converts to TIFF format and transmits through 10 Gbps interface.

[0050] Component logic interface (continuation of three types of interaction): Table 3: Component logic interface interaction type configuration example

[0051] Component index configuration (quantify component performance requirements): Imaging detection component index (CI-001): exposure time ≤10 ps; spatial resolution ≥50 lp / mm; single acquisition frame number ≥8 frames; High-speed control component index (CI-002): trigger signal response time ≤1 ns; instruction distribution delay ≤500 ps; Data processing component index (CI-003): image format conversion time ≤500 ms; data transmission rate ≥10 Gbps.

[0052] III. Component design layer: configuration module and module index Step 1: decompose component index into second sub-requirements, establish traceability matrix Second sub-requirement splitting (take “imaging detection component” as an example, decompose CI-001): CR-001 (corresponding to CI-001 “exposure time”): need to realize “10 ps level shutter control”; CR-002 (corresponding to CI-001 “spatial resolution”): need to realize “50 lp / mm optical imaging”; CR-003 (corresponding to CI-001 “acquisition frame number”): need to realize “8 frames of sequence storage and output”.

[0053] Establish component level traceability matrix, as shown in Table 4 below: Table 4: Component level traceability matrix

[0054] Step 2: draw second activity diagram, identify core modules Second activity diagram modeling (take “8 frame image acquisition” of imaging detection component as an example), as shown in Figure 4 .

[0055] Identify core modules (based on multiple second flow nodes of second activity diagram, associate activities and modules): Module 1: MCP shutter module (associated activities B, G - achieve 10 ps exposure control); Module 2: Optical lens module (associated activity C - achieve 50 lp / mm spatial resolution); Module 3: CMOS sensor module (associated activity D - collect raw images); Module 4: Cache module (associated activities E, H - store 8 frames of data).

[0056] Step 3: Configure module functions, interfaces, and module indicators to establish the third sub-demand traceability Module functions and interfaces: MCP shutter module: receive exposure instructions, control MCP on-time (10 ps) through high-voltage pulse; Interface: TTL instruction input (from high-speed control component); Optical lens module: focus ICF target pellet image to CMOS target surface, focal length 100 mm, aperture F / 2.8; Interface: fiber optic input (from ICF target chamber); CMOS sensor module: convert optical signals to electrical signals, pixel count 2048x2048; Interface: analog signal output to cache module; High-speed cache module: store 8 frames of raw images, capacity ≥ 1 GB; Interface: PCIe 4.0 data output to data processing component.

[0057] Module indicator configuration (quantify module performance): MCP shutter module indicator (MI-001): on-time ≤ 10 ps; trigger delay ≤ 200 ps; Optical lens module indicator (MI-002): spatial resolution ≥ 50 lp / mm; distortion rate ≤ 1%; CMOS sensor module indicator (MI-003): pixel count 2048x2048; dark current ≤ 1 nA / cm²; High-speed cache module indicator (MI-004): storage capacity ≥ 1 GB; data read / write rate ≥ 8 Gbps.

[0058] Third sub-demand traceability matrix (take MCP shutter module as an example), as shown in the following Table 5: Table 5: Third sub-demand traceability matrix

[0059] It should be noted that for special scene processing, i.e. activity graph cannot fully express the corresponding behavior characteristics, state machine graph needs to be supplemented.

[0060] For example, when the behavior of the "high-speed control component" needs to reflect the "state switching logic" (which cannot be fully expressed by an activity diagram), a state machine diagram (system architecture software drawing) is used: Core states: standby state → trigger signal receiving state → instruction distribution state → standby state; Trigger event: Standby → Receive: ICF target chamber sends a trigger signal; Receive → Distribution: signal verification passes (frequency 1 kHz, delay ≤1 ns); Distribution → Standby: instruction sending is completed (feedback signal receiving).

[0061] The above scheme uses a three-level traceability matrix. If the "system indicator SI-001 (time resolution ≤10 ps → ≤8 ps)" is modified, the impact can be quickly located: first sub-requirement SR-001 → component indicator CI-001 → module indicator MI-001 (MCP conduction time ≤8 ps), without the need to check documents one by one; information consistency is improved. The service use case diagram and the activity diagram provide a unified model for the optical team (lens design), the electronic team (MCP control), and the software team (data transmission), avoiding collaboration problems such as "optical resolution not matching electronic control delay".

[0062] Embodiment 2 A laser fusion superfast imaging instrument logic design system based on MBSE is provided, comprising: A running analysis layer is configured to obtain system indicators of the superfast imaging instrument based on requirement information of the superfast imaging instrument through running analysis. Specifically, the requirement information of the superfast imaging instrument is obtained, and functional class requirements in the requirement information are identified. Here, a requirement management tool can be used. The requirement information includes user requirements, which mainly refer to the performance improvement expectations for the newly designed laser fusion superfast imaging instrument.

[0063] Service use cases of the superfast imaging instrument are obtained based on the functional class requirements. The participants are identified through the service use cases, and the participants are associated with the corresponding service use cases. Then, the logic interfaces of the system and the participants are configured based on interaction types.

[0064] It should be noted that the interaction types here and the interaction types later include three types of matter, energy, and information. The information interaction at least includes image data flow, trigger signal, and control instruction. The energy interaction at least includes the power provided for the camera module. The matter interaction at least includes the physical installation interface with the vacuum chamber and the optical path interface.

[0065] System indicators of the superfast imaging instrument are obtained based on the service use cases, the logic interfaces, and the participants interacting with the system when implementing the service use cases.

[0066] a system design layer, configured to identify components required to achieve system indicators based on the system indicators, and configure component indicators by decomposing the system indicators; specifically, the system indicators are classified to obtain a plurality of first sub-demands, and a bidirectional traceability matrix between the first sub-demands, service use cases and user demands is established; that is, the bidirectional links with upstream service use cases and user demands are established in the demand traceability matrix, to ensure the completeness of the demand chain.

[0067] Based on the plurality of first sub-demands of the system indicators, a first activity graph for implementing the service use cases of the system is obtained; the first activity graph includes a plurality of first flow nodes for implementing the service use cases, and each first flow node corresponds to a component demand; it should be noted that the activity graph is a view used to convey the dynamic behavior of the system, and objects model events, capabilities and data flows through activities, and system behaviors can be allocated to system structures through activity graph partitioning. In the scheme of the present application, the key activities of the ultrafast imaging instrument in the typical activity "experimental data measurement" are as follows: starting the scanning working mode → setting the scanning gear → setting the CMOS camera external trigger working mode → CMOS camera external trigger image acquisition → closing the power supply of the camera module → acquiring experimental images → closing the power supply of the camera module.

[0068] Based on the first activity graph, components are identified and obtained, the components are associated with the first flow nodes in the first activity graph, the component functions are configured, and the logical interfaces corresponding to the components are configured based on the interaction types.

[0069] Based on the flow activities to be performed by the components, component indicators are configured.

[0070] a component design layer, configured to identify and obtain modules required to achieve component indicators based on the component indicators, and configure module indicators by decomposing the component indicators; specifically, the component indicators are classified to obtain a plurality of second sub-demands, and a bidirectional traceability matrix between the second sub-demands, service use cases and system demands is established.

[0071] Based on the plurality of second sub-demands of the component indicators, a second activity graph for implementing the system indicators of the components is obtained; the second activity graph includes a plurality of second flow nodes for implementing the system indicators, and each second flow node corresponds to a module demand; for example, in the first activity graph described above, taking the key activity "acquiring experimental images" of the ultrafast imaging instrument in the typical activity "experimental data measurement" as an example, the components required for decomposition include an electron-optical system component, a control system component and an imaging system component, each component contains specific activities, that is, each component is associated with the activities it is responsible for, and the component functions are configured. For example, the function of the "imaging detection component" is defined as "receiving a trigger signal and exposing, and converting an optical signal into an electrical signal image". The specific configuration is shown in Figure 2 .

[0072] Based on the second activity graph identification acquisition module, the module is associated with the second flow node in the second activity graph, and the module function is configured, and then the logic interface corresponding to the module is configured based on the interaction type; for example, a "LVDS trigger signal" interface is defined between the "high-speed control component" and the "imaging detection component".

[0073] Based on the flow activity to be executed by the module, the module index is configured.

[0074] The module requirements are classified to obtain a plurality of third sub-requirements, and a bidirectional traceability relationship matrix between the third sub-requirements, the service use case and the component requirement is established.

[0075] It should be noted that when the first activity graph cannot completely express the behavior characteristics of the service use case, a state machine graph is used to express the behavior characteristics of the service use case; when the second activity graph cannot completely express the behavior characteristics of the component, a state machine graph is used to express the behavior characteristics of the component.

[0076] The above is only a preferred embodiment of the present application and is not used to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A logic design method for an ultrafast laser fusion imaging instrument based on MBSE, characterized in that, Includes the following steps: Based on the requirements of ultrafast imaging instruments, system indicators of ultrafast imaging instruments are obtained through operational analysis. Based on the identification of system indicators, the components required to achieve the system indicators are obtained, and the component indicators are configured by decomposing the system indicators. Based on component metric identification, the modules required to achieve the component metrics are obtained, and module metrics are configured by decomposing the component metrics.

2. The logic design method for an ultrafast laser fusion imaging instrument based on MBSE as described in claim 1, characterized in that, The system indicators of the ultrafast imaging instrument obtained through operational analysis based on the requirements information of the ultrafast imaging instrument include: Obtain the requirements information for ultrafast imaging instruments and identify the functional requirements within that information; Service use cases for ultrafast imaging instruments are obtained based on functional requirements. Participating objects are identified through service use cases, and the participating objects are associated with the corresponding service use cases. Then, the logical interface between the system and the participating objects is configured based on the interaction type. System metrics for ultrafast imaging instruments are obtained based on service use cases, logical interfaces, and the participating objects that interact with the system when implementing service use cases.

3. The logic design method for an ultrafast laser fusion imaging instrument based on MBSE as described in claim 1, characterized in that, The process of identifying and acquiring the components required to achieve system metrics based on system metric identification, and configuring component metrics through the decomposition of system metrics, includes: The system metrics are classified to obtain multiple first sub-requirements, and a bidirectional traceability matrix is ​​established between the first sub-requirements, service use cases, and user requirements. Based on multiple first sub-requirements of system metrics, a first activity graph for implementing service use cases is obtained; the first activity graph includes multiple first process nodes for implementing service use cases, and each first process node corresponds to a component requirement; The components are identified and obtained based on the first activity graph, the components are associated with the first process node in the first activity graph, the component functions are configured, and the logical interface corresponding to the component is configured based on the interaction type. Configure component metrics based on the process activities that the component will execute.

4. The logic design method for an ultrafast laser fusion imaging instrument based on MBSE as described in claim 1, characterized in that, The process of identifying and obtaining the modules required to achieve the component metrics based on component metric identification, and configuring module metrics through the decomposition of component metrics, includes: The component metrics are classified to obtain multiple second sub-requirements, and a bidirectional traceability matrix is ​​established between the second sub-requirements, service use cases, and system requirements. Based on multiple second sub-requirements of component metrics, a second activity diagram for the implementation of system metrics is obtained; the second activity diagram includes multiple second process nodes for implementing system metrics, and each second process node corresponds to a module requirement; Based on the second activity graph recognition and acquisition module, the module is associated with the second process node in the second activity graph, the module function is configured, and the corresponding logical interface of the module is configured based on the interaction type. Configure module metrics based on the process activities that the module needs to perform; The module requirements are categorized to obtain multiple third sub-requirements, and a bidirectional traceability matrix is ​​established between the third sub-requirements, service use cases, and component requirements.

5. The logic design method for an MBSE-based ultrafast laser fusion imaging instrument as described in any one of claims 2-4, characterized in that, The interaction types include three types: matter, energy, and information. Among them, matter interaction includes at least a physical installation interface with the vacuum chamber and an optical path interface; energy interaction includes at least a power supply to the camera module; and information interaction includes at least image data streams, trigger signals, and control commands.

6. The logic design method for an MBSE-based ultrafast laser fusion imaging instrument as described in claim 3 or 4, characterized in that, When the first activity diagram cannot fully express the behavioral characteristics of the service use case, a state machine diagram is used to express the behavioral characteristics of the service use case. When the second activity diagram cannot fully express the behavioral characteristics of the component, a state machine diagram is used to express the behavioral characteristics of the component.

7. A logic design system for an ultrafast laser fusion imaging instrument based on MBSE, characterized in that, include: The operation analysis layer is used to obtain the system indicators of the ultrafast imaging instrument through operation analysis based on the demand information of the ultrafast imaging instrument. The system design layer is used to identify the components required to achieve the system indicators based on system indicator identification, and to configure component indicators by decomposing the system indicators. The component design layer is used to identify the modules required to achieve the component metrics based on component metrics, and to configure module metrics by decomposing the component metrics.

8. The logic design system for an ultrafast laser fusion imaging instrument based on MBSE as described in claim 7, characterized in that, The system indicators of the ultrafast imaging instrument obtained through operational analysis based on the requirements information of the ultrafast imaging instrument include: Obtain the requirements information for ultrafast imaging instruments and identify the functional requirements within that information; Service use cases for ultrafast imaging instruments are obtained based on functional requirements. Participating objects are identified through service use cases, and the participating objects are associated with the corresponding service use cases. Then, the logical interface between the system and the participating objects is configured based on the interaction type. System metrics for ultrafast imaging instruments are obtained based on service use cases, logical interfaces, and the participating objects that interact with the system when implementing service use cases.

9. The logic design system for an ultrafast laser fusion imaging instrument based on MBSE as described in claim 7, characterized in that, The process of identifying and acquiring the components required to achieve system metrics based on system metric identification, and configuring component metrics through the decomposition of system metrics, includes: The system metrics are classified to obtain multiple first sub-requirements, and a bidirectional traceability matrix is ​​established between the first sub-requirements, service use cases, and user requirements. Based on multiple first sub-requirements of system metrics, a first activity graph for implementing service use cases is obtained; the first activity graph includes multiple first process nodes for implementing service use cases, and each first process node corresponds to a component requirement; The components are identified and obtained based on the first activity graph, the components are associated with the first process node in the first activity graph, the component functions are configured, and the logical interface corresponding to the component is configured based on the interaction type. Configure component metrics based on the process activities that the component will execute.

10. The logic design system for an ultrafast laser fusion imaging instrument based on MBSE as described in claim 7, characterized in that, The process of identifying and obtaining the modules required to achieve the component metrics based on component metric identification, and configuring module metrics through the decomposition of component metrics, includes: The component metrics are classified to obtain multiple second sub-requirements, and a bidirectional traceability matrix is ​​established between the second sub-requirements, service use cases, and system requirements. Based on multiple second sub-requirements of component metrics, a second activity diagram for the implementation of system metrics is obtained; the second activity diagram includes multiple second process nodes for implementing system metrics, and each second process node corresponds to a module requirement; Based on the second activity graph recognition and acquisition module, the module is associated with the second process node in the second activity graph, the module function is configured, and the corresponding logical interface of the module is configured based on the interaction type. Configure module metrics based on the process activities that the module needs to perform; The module requirements are categorized to obtain multiple third sub-requirements, and a bidirectional traceability matrix is ​​established between the third sub-requirements, service use cases, and component requirements.

Images