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

Abstract

The present application belongs to the technical field of model-based system engineering, and relates to a laser fusion superfast imaging instrument logic design method and system based on MBSE, which comprises: based on the demand information of the superfast imaging instrument, system indexes of the superfast imaging instrument are obtained through operation analysis; based on the system index identification, components required to achieve the system indexes are obtained, and component indexes are configured through decomposition of the system indexes; based on the component index identification, modules required to achieve the component indexes are obtained, and module indexes are configured through decomposition of the component indexes. The method establishes a multi-level two-way traceable relationship matrix in the collaborative development of the superfast imaging instrument, establishes a two-way traceable link among user demand, service use case and indexes at each level, ensures that any modification can be subjected to impact analysis, and improves information consistency; through standardized and visualized models such as service use case and activity diagram, a common understanding basis without ambiguity is provided for different teams, and team collaboration is promoted.

Description

Technical Field

[0001] This invention relates to the field of model-based systems engineering technology, and specifically discloses a logic design method and system for a laser fusion ultrafast imaging instrument based on MBSE. Background Technology

[0002] Inertial confinement fusion experiments require the use of several ultrafast imaging instruments (i.e., diagnostic instruments) to diagnose and characterize transient microscale physical processes. As research into inertial confinement fusion continues to deepen, fusion experiments demand that diagnostic instruments be designed with high reliability and a deep match to the physical scene in a shorter time.

[0003] Traditional diagnostic instrument architecture design primarily employs a document-based approach. However, with the rapid increase in project scale and complexity, this approach has become increasingly inefficient, prone to inconsistencies, and hindering collaboration. In contrast to document-based systems engineering, model-based systems engineering (MBSE) adopts a model-centric approach, covering the entire lifecycle of complex systems. It replaces traditional documents, audio recordings, videos, and tables with models to meet design requirements, interface requirements, performance requirements, functionalities, metrics, and solutions. Furthermore, it establishes standardized models for continuous updates, facilitating the maintenance and iterative updates of complex systems.

[0004] This application proposes a Model Based System (MBSE) approach for the logical design of laser fusion diagnostic instruments. The aim is to create an executable and reusable system model, enabling the modeling of key design elements such as requirements, behavior, architecture, and parameters. This will improve design efficiency and address the challenges of collaboration. Summary of the Invention

[0005] The purpose of this invention is to provide a logic design method and system for laser fusion ultrafast imaging instruments based on MBSE, solving the problem of low efficiency faced by traditional document-based design methods for diagnostic instrument architecture; the specific solution is as follows:

[0006] Firstly, a logic design method for an ultrafast laser fusion imaging instrument based on MBSE is provided, including the following steps:

[0007] Based on the requirements of ultrafast imaging instruments, system indicators of ultrafast imaging instruments are obtained through operational analysis.

[0008] 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.

[0009] 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.

[0010] Furthermore, the system indicators of the ultrafast imaging instrument obtained through operational analysis based on the requirements information of the ultrafast imaging instrument include:

[0011] Obtain the requirements information for ultrafast imaging instruments and identify the functional requirements within that information;

[0012] 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.

[0013] 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.

[0014] Furthermore, the step of identifying and obtaining the components required to achieve the system indicators based on system indicator identification, and configuring component indicators through the decomposition of system indicators, includes:

[0015] 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.

[0016] 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;

[0017] 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.

[0018] Configure component metrics based on the process activities that the component will execute.

[0019] Furthermore, the step of identifying and obtaining the modules required to achieve the component metrics based on component metrics, and configuring module metrics by decomposing the component metrics, includes:

[0020] 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.

[0021] 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;

[0022] 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 logical interface corresponding to the module is configured based on the interaction type.

[0023] Configure module metrics based on the process activities that the module needs to perform;

[0024] The module metrics 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.

[0025] Furthermore, the interaction type includes three types: matter, energy, and information; wherein, matter interaction includes at least a physical installation interface and an optical path interface with the vacuum chamber, energy interaction includes at least a power supply for the camera module, and information interaction includes at least image data streams, trigger signals, and control commands.

[0026] Furthermore, 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.

[0027] 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.

[0028] Secondly, a logic design system for an ultrafast laser fusion imaging instrument based on MBSE is provided, including:

[0029] 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.

[0030] 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.

[0031] 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.

[0032] Furthermore, the system indicators of the ultrafast imaging instrument obtained through operational analysis based on the requirements information of the ultrafast imaging instrument include:

[0033] Obtain the requirements information for ultrafast imaging instruments and identify the functional requirements within that information;

[0034] 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.

[0035] 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.

[0036] Furthermore, the step of identifying and obtaining the components required to achieve the system indicators based on system indicator identification, and configuring component indicators through the decomposition of system indicators, includes:

[0037] 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.

[0038] 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;

[0039] 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.

[0040] Configure component metrics based on the process activities that the component will execute.

[0041] Furthermore, the step of identifying and obtaining the modules required to achieve the component metrics based on component metrics, and configuring module metrics by decomposing the component metrics, includes:

[0042] 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.

[0043] 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;

[0044] 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 logical interface corresponding to the module is configured based on the interaction type.

[0045] Configure module metrics based on the process activities that the module needs to perform;

[0046] The module metrics 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.

[0047] The beneficial effects of this invention are:

[0048] By establishing a multi-level, bidirectional, traceable relationship matrix, a bidirectional traceable link is created between user requirements, service use cases, system metrics, component metrics, and module metrics, ensuring that any modification can be analyzed for its impact, thereby improving information consistency. Through standardized and visualized models such as service use cases and activity diagrams, an unambiguous common understanding basis is provided for different professional teams, thereby promoting team collaboration. Attached Figure Description

[0049] Figure 1 This is a flowchart of the logic design method for the laser fusion ultrafast imaging instrument based on MBSE according to the present invention.

[0050] Figure 2 This is a graphical example of the key activity of "acquiring experimental images" for ultrafast imaging instruments.

[0051] Figure 3 This is the first activity graph modeling process when using service use case UC-001 "ICF transient image acquisition" as an example.

[0052] Figure 4 The second active graph modeling process is used as an example when the imaging detection component acquires 8 frames of images. Detailed Implementation

[0053] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0054] Example 1

[0055] A logic design method for an ultrafast laser fusion imaging instrument based on MBSE is provided, including the following steps:

[0056] Based on the requirements information of the ultrafast imaging instrument, system indicators of the ultrafast imaging instrument are obtained through operational analysis. Specifically, this includes: acquiring the requirements information of the ultrafast imaging instrument and identifying the functional requirements within that information. Requirements management tools can be used here. The requirements information includes user requirements, which mainly refer to the expected performance improvements of the newly designed laser fusion ultrafast imaging instrument. The operational analysis here mainly involves: acquiring the functional requirements, constructing service use cases based on these requirements, identifying the participating objects in the service use cases, and configuring logical interfaces containing three interaction types: matter, energy, and information, based on the participating objects.

[0057] 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.

[0058] It should be noted that the interaction types here, as well as the subsequent interaction types, include three types: matter, energy, and information. Among them, information interaction includes at least image data streams, trigger signals, and control commands; energy interaction includes at least the power supply provided to the camera module; and matter interaction includes at least the physical installation interface and optical path interface with the vacuum chamber.

[0059] 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.

[0060] Based on system metric identification, the components required to achieve the system metrics are obtained, and component metrics are configured by decomposing the system metrics. Specifically, this includes classifying the system metrics to obtain multiple first sub-requirements, and establishing a bidirectional traceable relationship matrix between the first sub-requirements, service use cases, and user requirements. That is, a bidirectional link is established between the requirement traceability matrix and the upstream service use cases and user requirements to ensure the integrity of the requirement chain.

[0061] Based on multiple first sub-requirements of system metrics, a first activity diagram for implementing service use cases is obtained. The first activity diagram includes multiple first process nodes for implementing service use cases, each corresponding to a component requirement. It should be noted that an activity diagram is a view used to convey the dynamic behavior of a system. Objects model events, capabilities, and data flows through activities, and system behaviors can be assigned to the system structure through activity diagram partitioning. In the scheme of this application, the key activities of the ultrafast imaging instrument in the typical activity "Experimental Data Measurement" are as follows: Start scanning mode → Set scan level → Set CMOS camera external trigger mode → CMOS camera external trigger image acquisition → Turn off camera module power supply → Acquire experimental images → Turn off camera module power supply.

[0062] The components are identified and obtained based on the first activity graph, associated with the first process node in the first activity graph, and the component functions are configured. Then, the logical interface corresponding to the component is configured based on the interaction type.

[0063] Configure component metrics based on the process activities that the component will execute.

[0064] Based on component metric identification, the modules required to achieve the component metric are obtained, and module metrics are configured by decomposing the component metric; specifically, the component metric is classified to obtain multiple second sub-requirements, and a bidirectional traceable relationship matrix is ​​established between the second sub-requirements, service use cases and system requirements.

[0065] Based on multiple second sub-requirements of component metrics, a second activity diagram is obtained to realize the system metrics. The second activity diagram includes multiple second process nodes for realizing the system metrics, each corresponding to a module requirement. For example, in the aforementioned first activity diagram, taking the key activity "acquiring experimental images" of the ultrafast imaging instrument within 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 its component functions are configured. For example, the function of the "imaging detection component" is defined as "receiving trigger signals and exposing, converting light signals into electrical signal images." Specifically, as follows... Figure 2 As shown.

[0066] Based on the second activity graph recognition and acquisition module, the module is associated with the second process node in the second activity graph, and the module function is configured. Then, 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".

[0067] Configure module metrics based on the process activities that the module needs to perform.

[0068] The module metrics 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.

[0069] It should also be noted 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.

[0070] State machine diagrams define the technical states of components using rectangular nodes and embed attribute information corresponding to the technical requirements in the documentation within the nodes, thus anchoring the static behavioral characteristics of the components. Different state nodes are connected by arrowed transition edges, with trigger conditions bound to the three types of interaction in the documentation marked on the edges, providing a visual representation of the dynamic behavioral characteristics of the components. For the technical requirements of components in the documentation to perform multi-step process activities, state machine diagrams express the hierarchical characteristics of component behavior through nested sub-states (state nodes containing sub-state machines), and the real-time nature of behavior through event response mechanisms. Invariant constraints (technical conditions that must be continuously satisfied during the state's existence) express the persistent behavioral characteristics of the component in a certain state, and these constraints must be based on the component's technical specifications in the documentation.

[0071] This invention establishes a multi-level, bidirectional, traceable relationship matrix, creating bidirectional traceable links between user requirements, service use cases, system metrics, component metrics, and module metrics. This ensures that any modification can be analyzed for its impact, thereby improving information consistency. Furthermore, through standardized and visualized models such as service use cases and activity diagrams, it provides a shared, unambiguous understanding basis for different professional teams, promoting team collaboration.

[0072] To facilitate understanding, the above methods and solutions are further illustrated with the following examples using actual design cases.

[0073] Taking the "Ultrafast Frame Imaging Diagnostic Instrument for Inertial Confinement Fusion (ICF) Experiment" as the design object, this paper presents the complete design and implementation process based on the three-level process of "operational analysis layer → system design layer → component design layer" described in this method, combined with specific tools, models and quantitative indicators.

[0074] The initial design preparation mainly includes defining the target scenario and selecting tools, among which:

[0075] The target scenario is defined as follows: To address the diagnostic requirements of "target compression transient process (duration ≤ 100ps, spatial scale ≤ 500μm)" in ICF experiments, an ultrafast frame imaging diagnostic instrument is designed, which needs to achieve the core functions of "high temporal resolution, high spatial resolution, and real-time data transmission".

[0076] The specific steps are as follows:

[0077] I. Operational Analysis Layer: Obtaining System Indicators

[0078] Step 1: Requirements Information Collection and Functional Requirements Identification

[0079] Requirements information entry (creating a requirements module in the requirements management tool):

[0080] User requirements (from ICF experimental requirements):

[0081] UR-001: Time resolution ≤10ps;

[0082] UR-002: Spatial resolution ≥50 lp / mm;

[0083] UR-003: Can acquire ≥8 frames of images in a single experiment;

[0084] UR-004: Image data must be transmitted to the experimental control center within 1 second.

[0085] Functional requirement identification (extracting executable functions from user requirements):

[0086] FR-001: Receives the ICF target chamber trigger signal and starts image acquisition;

[0087] FR-002: Performs multi-frame ultrafast imaging of the transient process of a target pellet;

[0088] FR-003: Converts acquired image data into a standard format (such as TIFF);

[0089] FR-004: Transmits data to an external storage server in real time via fiber optic cable.

[0090] Step 2: Service use case modeling and participant association

[0091] Draw service use case diagrams (create UML use case diagrams in the system architecture software):

[0092] Core service use cases: UC-001 "ICF transient image acquisition", UC-002 "data format conversion and transmission";

[0093] Participant identification (associated with use cases):

[0094] External object 1: ICF target chamber (provides trigger signal, associated with UC-001);

[0095] External object 2: Experimental control center server (receives data, associated with UC-002);

[0096] Internal object: Diagnostic instrument system (execution cases UC-001, UC-002).

[0097] Configure the logical interfaces according to the three interaction types: "matter, energy, and information," as detailed in Table 1 below:

[0098] Table 1: Logical Interface Configuration Example

[0099]

[0100] Step 3: Determine system indicators

[0101] Based on service use cases, logical interfaces, and the requirements of participating objects, system-level quantitative indicators are obtained (entered into the system requirements module):

[0102] SI-001: Time resolution ≤10ps (matches UR-001);

[0103] SI-002: Spatial resolution ≥50lp / mm (matches UR-002);

[0104] SI-003: ≥8 frames per acquisition (matches UR-003);

[0105] SI-004: Data transmission delay ≤1s (matches UR-004);

[0106] SI-005: Trigger signal response time ≤ 1ns (matching trigger interface requirements).

[0107] II. System Design Layer: Configuration Components and Component Indicators

[0108] Step 1: Decompose the system indicators into the first sub-requirements and establish a traceability matrix.

[0109] First sub-requirement breakdown (breaking down system metrics into component-level implementable requirements):

[0110] SR-001 (corresponding to SI-001 / SI-002 / SI-003): Imaging function sub-requirements - need to achieve "10ps exposure control + 50lp / mm spatial resolution + 8-frame sequence acquisition";

[0111] SR-002 (corresponding to SI-005): Control function sub-requirement - must achieve "≤1ns trigger signal reception and distribution";

[0112] SR-003 (corresponding to SI-004): Data processing sub-requirement - "Image format conversion (≤500ms) + 10Gbps data transmission" must be achieved.

[0113] Establish a two-way traceability matrix (create a two-way traceability table in the requirements management tool):

[0114] Table 2: Two-way traceability matrix

[0115]

[0116] Step 2: Draw the first activity diagram and identify the core components.

[0117] The first activity diagram modeling (taking service use case UC-001 "ICF transient image acquisition" as an example, system architecture software drawing) is as follows: Figure 3 As shown.

[0118] Identify core components (based on multiple first process nodes in the first activity graph, associating components with activities):

[0119] Component 1: Imaging Detection Component (related to activities D, E, and G – responsible for exposure control and image acquisition);

[0120] Component 2: High-speed control component (related to activities B and C – responsible for trigger signal reception and command distribution);

[0121] Component 3: Data processing component (related to activities H, I, and J – responsible for image conversion and transmission).

[0122] Step 3: Configure component functionality, logical interfaces, and component metrics

[0123] Component function definition:

[0124] Imaging detection component: Receives exposure commands and achieves 10ps-level ultra-fast exposure and multi-frame image acquisition through MCP+CMOS;

[0125] High-speed control component: Receives the LVDS trigger signal from the ICF target chamber and distributes it to the imaging component within ≤1ns;

[0126] Data processing component: Receives the raw images from the imaging component, converts them into TIFF format, and transmits them via a 10Gbps interface.

[0127] Component logic interface (continuing the three interaction types):

[0128] Table 3: Example of Component Logic Interface Interaction Type Configuration

[0129]

[0130] Component metric configuration (quantifying component performance requirements):

[0131] Imaging detection component specifications (CI-001): Exposure time ≤10ps; Spatial resolution ≥50lp / mm; Number of frames per acquisition ≥8 frames;

[0132] High-speed control component specifications (CI-002): Trigger signal response time ≤ 1ns; Command distribution delay ≤ 500ps;

[0133] Data processing component metrics (CI-003): Image format conversion time ≤ 500ms; Data transmission rate ≥ 10Gbps.

[0134] III. Component Design Layer: Configuration Modules and Module Indicators

[0135] Step 1: Decompose the component metrics into the second sub-requirements and establish a traceability matrix.

[0136] Second sub-requirement breakdown (taking "imaging detection component" as an example, breaking down CI-001):

[0137] CR-001 (corresponding to CI-001 "exposure time"): requires "10ps shutter speed control";

[0138] CR-002 (corresponding to CI-001 "spatial resolution"): requires "50 lp / mm optical imaging";

[0139] CR-003 (corresponding to CI-001 "Number of Acquisition Frames"): Requires "8-frame sequence storage and output".

[0140] Establish a component-level traceability matrix, as shown in Table 4 below:

[0141] Table 4: Component-level traceability matrix

[0142]

[0143] Step 2: Draw the second activity diagram and identify the core modules.

[0144] The second activity graph modeling (taking the imaging detection component's "8-frame image acquisition" as an example) is as follows: Figure 4 As shown.

[0145] Identify the core modules (based on multiple second process nodes in the second activity diagram, associating activities and modules):

[0146] Module 1: MCP shutter module (associated with activities B and G – to achieve 10ps exposure control);

[0147] Module 2: Optical Lens Module (Related Activity C – Achieving 50 lp / mm Spatial Resolution);

[0148] Module 3: CMOS Sensor Module (Associated Activity D - Acquiring Raw Images);

[0149] Module 4: Cache module (associated with activities E and H – storing 8 frames of data).

[0150] Step 3: Configure module functions, interfaces, and module metrics, and establish third-party sub-requirement traceability.

[0151] Module functions and interfaces:

[0152] MCP shutter module: Receives exposure commands and controls the MCP conduction time (10ps) via high-voltage pulses; Interface: TTL command input (from high-speed control component).

[0153] Optical lens module: focuses the ICF target image onto the CMOS target surface, with a focal length of 100mm and an aperture of F / 2.8; interface: fiber optic input (from the ICF target chamber).

[0154] CMOS sensor module: converts light signals into electrical signals, with a pixel count of 2048×2048; interface: analog signal output to the buffer module;

[0155] Cache module: Stores 8 frames of raw images, with a capacity of ≥1GB; Interface: PCIe 4.0 data output to the data processing component.

[0156] Module metric configuration (quantifying module performance):

[0157] MCP shutter module specifications (MI-001): On-time ≤10ps; Trigger delay ≤200ps;

[0158] Optical lens module specifications (MI-002): Spatial resolution ≥50 lp / mm; Distortion rate ≤1%;

[0159] CMOS sensor module specifications (MI-003): 2048×2048 pixels; dark current ≤1nA / cm²;

[0160] Cache module metrics (MI-004): Storage capacity ≥ 1GB; Data read / write speed ≥ 8Gbps.

[0161] The third sub-demand traceability matrix (taking the MCP shutter module as an example) is shown in Table 5 below:

[0162] Table 5: Third Sub-Requirement Traceability Matrix

[0163]

[0164] It should also be noted that for special scenarios, where the activity diagram cannot fully express the corresponding behavioral characteristics, a state machine diagram is needed to supplement the application.

[0165] For example, when the behavior of a "high-speed control component" needs to reflect "state transition logic" (which cannot be fully expressed by an activity diagram), a state machine diagram (drawn by the system architecture software) is used:

[0166] Core states: Standby state → Trigger signal receiving state → Command distribution state → Standby state;

[0167] Triggering event:

[0168] Standby → Receive: ICF target chamber sends trigger signal;

[0169] Receive → Distribute: Signal verification passed (frequency 1kHz, delay ≤1ns);

[0170] Distribution → Standby: Command sent (feedback signal received).

[0171] The above solution utilizes a three-level traceability matrix. If the "system indicator SI-001 (time resolution ≤10ps → ≤8ps)" is modified, the impact can be quickly located: first sub-requirement SR-001 → component indicator CI-001 → module indicator MI-001 (MCP conduction time ≤8ps), without needing to check documents one by one; thus improving information consistency. Service use case diagrams and activity diagrams provide a unified model for the optics team (lens design), the electronics team (MCP control), and the software team (data transmission), avoiding collaboration issues caused by "optical resolution mismatch with electronic control delay."

[0172] Example 2

[0173] A logic design system for an ultrafast laser fusion imaging instrument based on MBSE is provided, including:

[0174] The operational analysis layer is used to obtain system indicators of the ultrafast imaging instrument based on its requirements information through operational analysis. Specifically, this includes: acquiring the requirements information of the ultrafast imaging instrument and identifying functional requirements within that information, which can be achieved using a requirements management tool; the requirements information includes user requirements, primarily referring to expectations for performance improvements in the newly designed laser fusion ultrafast imaging instrument.

[0175] 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.

[0176] It should be noted that the interaction types here, as well as the subsequent interaction types, include three types: matter, energy, and information. Among them, information interaction includes at least image data streams, trigger signals, and control commands; energy interaction includes at least the power supply provided to the camera module; and matter interaction includes at least the physical installation interface and optical path interface with the vacuum chamber.

[0177] 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.

[0178] The system design layer is used to identify and obtain the components required to achieve the system indicators based on system indicators, and to configure component indicators by decomposing the system indicators; specifically, it includes: classifying the system indicators to obtain multiple first sub-requirements, and establishing a bidirectional traceable relationship matrix between the first sub-requirements, service use cases and user requirements; that is, establishing a bidirectional link between the requirement traceability matrix and the upstream service use cases and user requirements to ensure the integrity of the requirement chain.

[0179] Based on multiple first sub-requirements of system metrics, a first activity diagram for implementing service use cases is obtained. The first activity diagram includes multiple first process nodes for implementing service use cases, each corresponding to a component requirement. It should be noted that an activity diagram is a view used to convey the dynamic behavior of a system. Objects model events, capabilities, and data flows through activities, and system behaviors can be assigned to the system structure through activity diagram partitioning. In the scheme of this application, the key activities of the ultrafast imaging instrument in the typical activity "Experimental Data Measurement" are as follows: Start scanning mode → Set scan level → Set CMOS camera external trigger mode → CMOS camera external trigger image acquisition → Turn off camera module power supply → Acquire experimental images → Turn off camera module power supply.

[0180] The components are identified and obtained based on the first activity graph, associated with the first process node in the first activity graph, and the component functions are configured. Then, the logical interface corresponding to the component is configured based on the interaction type.

[0181] Configure component metrics based on the process activities that the component will execute.

[0182] The component design layer is used to identify and obtain the modules required to achieve the component metrics based on component metrics, and to configure module metrics by decomposing the component metrics. Specifically, this includes: classifying component metrics to obtain multiple second sub-requirements, and establishing a bidirectional traceability matrix between the second sub-requirements, service use cases, and system requirements.

[0183] Based on multiple second sub-requirements of component metrics, a second activity diagram is obtained to realize the system metrics. The second activity diagram includes multiple second process nodes for realizing the system metrics, each corresponding to a module requirement. For example, in the aforementioned first activity diagram, taking the key activity "acquiring experimental images" of the ultrafast imaging instrument within the typical activity "experimental data measurement" as an example, its 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 its component functions are configured. For example, the function of the "imaging detection component" is defined as "receiving trigger signals and exposing, converting light signals into electrical signal images." Specifically, as follows... Figure 2 As shown.

[0184] Based on the second activity graph recognition and acquisition module, the module is associated with the second process node in the second activity graph, and the module function is configured. Then, 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".

[0185] Configure module metrics based on the process activities that the module needs to perform.

[0186] The module metrics 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.

[0187] It should also be noted 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.

[0188] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for laser fusion ultrafast imaging instrument logic design based on MBSE, characterized in that, The method comprises the following steps: Based on the requirement information of the ultrafast imaging instrument, the system index of the ultrafast imaging instrument is obtained through operation analysis; Based on the system index, the components required to achieve the system index are identified, and the component index is configured by decomposing the system index, specifically: the system index is classified to obtain a plurality of first sub-requirements, and a bidirectional traceability relationship matrix between the first sub-requirements, service use cases and user requirements is established; Based on the plurality of first sub-requirements of the system index, a first activity graph for implementing the service use cases of the system is obtained; the first activity graph comprises a plurality of first flow nodes for implementing the service use cases, and each first flow node corresponds to a component requirement; Based on the first activity graph, the components are identified and associated with the first flow nodes in the first activity graph, and the component functions are configured, and then the logical interfaces corresponding to the components are configured based on the interaction types; based on the process activities to be performed by the components, the component index is configured; Based on the component index, the modules required to achieve the component index are identified, and the module index is configured by decomposing the component index, specifically: the component index is classified to obtain a plurality of second sub-requirements, and a bidirectional traceability relationship matrix between the second sub-requirements, service use cases and system requirements is established; based on the plurality of second sub-requirements of the component index, a second activity graph for implementing the system index of the component is obtained; the second activity graph comprises a plurality of second flow nodes for implementing the system index, and each second flow node corresponds to a module requirement; based on the second activity graph, the modules are identified and associated with the second flow nodes in the second activity graph, and the module functions are configured, and then the logical interfaces corresponding to the modules are configured based on the interaction types; Based on the process activities to be performed by the modules, the module index is configured; the module index is classified to obtain a plurality of third sub-requirements, and a bidirectional traceability relationship matrix between the third sub-requirements, service use cases and component requirements is established.

2. The laser fusion ultrafast imaging instrument logic design method based on MBSE of claim 1, wherein, The system index of the ultrafast imaging instrument is obtained based on the requirement information of the ultrafast imaging instrument through operation analysis, which comprises: Obtaining the requirement information of the ultrafast imaging instrument, and identifying the functional class requirements in the requirement information; Based on the functional class requirements, the service use cases of the ultrafast imaging instrument are obtained, the participants are identified through the service use cases, and the participants are associated with the corresponding service use cases, and then the logical interfaces of the system and the participants are configured based on the interaction types; Based on the service use cases, the logical interfaces and the participants interacting with the system when implementing the service use cases, the system index of the ultrafast imaging instrument is obtained.

3. The MBSE-based logical design method of a laser fusion ultrafast imaging instrument according to any one of claims 1-2, wherein, The interaction types include three types of matter, energy and information; wherein the matter interaction at least includes the physical installation interface with the vacuum chamber and the optical path interface, the energy interaction at least includes the power provided for the camera module, and the information interaction at least includes the image data stream, the trigger signal and the control instruction.

4. The method of claim 1, wherein the method further comprises: When the first activity graph cannot completely express the behavior characteristics of the service use cases, a state machine graph is used to express the behavior characteristics of the service use cases; When the second activity graph cannot completely express the behavior characteristics of the components, a state machine graph is used to express the behavior characteristics of the components. 5.A system for laser fusion ultrafast imaging instrument logic design based on MBSE, characterized in that, It comprises: The running analysis layer is configured to acquire system indexes of the ultrafast imaging instrument through running analysis based on requirement information of the ultrafast imaging instrument. The system design layer is configured to identify components required to achieve the system indexes through decomposition of the system indexes and configuration of component indexes based on the system indexes. Specifically, the system indexes are classified to obtain a plurality of first sub-requirements, and a bidirectional traceability relationship matrix between the first sub-requirements, 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 of the system is acquired. 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. Based on the first activity graph, components are identified, the components are associated with the first flow nodes in the first activity graph, and component functions are configured. Then, logical interfaces corresponding to the components are configured based on interaction types. Based on process activities to be performed by the components, component indexes are configured. The component design layer is configured to identify modules required to achieve the component indexes through decomposition of the component indexes and configuration of module indexes based on the component indexes. Specifically, the component indexes are classified to obtain a plurality of second sub-requirements, and a bidirectional traceability relationship matrix between the second sub-requirements, service use cases and system requirements is established. Based on the plurality of second sub-requirements of the component indexes, a second activity graph for implementing the system indexes of the components is acquired. 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. Based on the second activity graph, modules are identified, the modules are associated with the second flow nodes in the second activity graph, and module functions are configured. Then, logical interfaces corresponding to the modules are configured based on interaction types. Based on process activities to be performed by the modules, module indexes are configured. The module indexes are classified to obtain a plurality of third sub-requirements, and a bidirectional traceability relationship matrix between the third sub-requirements, service use cases and component requirements is established.

6. The MBSE-based laser fusion ultrafast imaging instrument logic design system of claim 5, wherein, The requirement information of the ultrafast imaging instrument is acquired, and functional class requirements in the requirement information are identified. Based on the functional class requirements, service use cases of the ultrafast imaging instrument are acquired. Participants are identified through the service use cases, and the participants are associated with corresponding service use cases. Then, logical interfaces between the system and the participants are configured based on interaction types. Based on the service use cases, the logical interfaces and the participants interacting with the system when implementing the service use cases, system indexes of the ultrafast imaging instrument are acquired. ​

Images