Model-based nuclear reactor demand analysis method
Through a model-based demand analysis method, the life cycle stage, stakeholders and their needs of the nuclear reactor are identified, and dynamic interactive analysis is carried out to solve the problem of incomplete requirements in the existing technology, ensuring that the nuclear reactor design covers all requirements and achieves high quality. Efficient design.
Patent Information
- Application Number
- CN202411328516.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-23
- Publication Date
- 2024-12-31
AI Technical Summary
The existing nuclear reactor design methods focus on design analysis and fail to fully consider the changes in demand, resulting in incomplete demand and some demands being ignored and difficult to trace.
A model-based nuclear reactor requirement analysis method is used to determine the task scenarios, stakeholders and their needs for all life cycle stages of the nuclear reactor, and dynamic interactive scenario analysis is carried out to determine the model requirements of the nuclear reactor.
A more comprehensive analysis of nuclear reactor requirements is achieved, ensuring that the design covers all requirements, avoiding the need to be ignored, providing clear design goals, and ensuring high-quality and efficient product delivery.
Smart Images
Figure CN119228415A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of nuclear reactor technology, and specifically to a model-based nuclear reactor demand analysis method. Background Art
[0002] The statements herein merely provide background information related to the present application and do not necessarily constitute prior art.
[0003] As nuclear reactor models become more diverse and their complexity and performance continue to increase, the demand for nuclear reactors is constantly changing. Changing demands have become the norm in the nuclear reactor design process and should be taken into consideration in nuclear reactor design.
[0004] The nuclear reactor design methods commonly used in related technologies focus on design analysis rather than demand analysis, resulting in problems such as incomplete requirements, neglect of some requirements, and difficulty in tracing requirements. Summary of the invention
[0005] A brief overview of the present application is provided below in order to provide a basic understanding of certain aspects of the present application. It should be understood that this overview is not an exhaustive overview of the present application. It is not intended to identify the key or important parts of the present application, nor is it intended to limit the scope of the present application. Its purpose is merely to present certain concepts in a simplified form as a prelude to a more detailed description discussed later.
[0006] In response to the above problems, an embodiment of the present application provides a model-based nuclear reactor demand analysis method, which includes: S1. Determining the task scenarios of all life cycle stages of the nuclear reactor based on the power supply and heating capacity requirements of the nuclear reactor; S2. Determining the stakeholders of each task scenario corresponding to each life cycle stage of the nuclear reactor based on the task scenarios of all life cycle stages of the nuclear reactor; S3. Determining the stakeholder needs of the nuclear reactor based on the stakeholders of each task scenario corresponding to each life cycle stage of the nuclear reactor; S4. Performing dynamic interactive scenario analysis based on the task scenarios of all life cycle stages of the nuclear reactor and the needs of the nuclear reactor stakeholders to determine the model requirements of the nuclear reactor.
[0007] The method provided in the embodiment of the present application can carry out demand analysis based on the power supply and heating capacity requirements, take into account the entire life cycle stages of the nuclear reactor, determine the task scenarios of all life cycle stages, and determine the stakeholders based on the task scenarios of all life cycle stages. Then, determine the stakeholder needs based on the stakeholders of each task scenario, and perform dynamic scenario interaction analysis to determine the model requirements of the nuclear reactor, which is conducive to a more comprehensive analysis of the needs of the nuclear reactor and the determination of clearer and complete nuclear reactor requirements, thereby providing clear design goals for nuclear reactor designers to minimize the situation where the designed nuclear reactor cannot cover all needs or some needs are ignored.
[0008] The embodiment of the present application establishes a model-based nuclear reactor requirements analysis method, which takes the full life cycle business scenario as the starting point, guides the implementation of processes such as stakeholder identification, model requirement definition, and mission scenario analysis, and carries out design, manufacturing, integration, and verification based on demand to ensure high-quality and efficient delivery of products that meet user requirements. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Other objects and advantages of the present application will become apparent from the following description of the embodiments of the present application with reference to the accompanying drawings, and will help to provide a comprehensive understanding of the present application.
[0010] Figure 1 It is a flow chart of the nuclear reactor demand analysis method provided in the embodiment of the present application.
[0011] Figure 2 It is a flow chart of analyzing the requirements of a reactor using a model provided in an embodiment of the present application.
[0012] Figure 3 It is a schematic diagram of the dynamic interaction scenario of power operation.
[0013] Figure 4 It is a schematic diagram of the external interface of the power operation dynamic interaction scenario.
[0014] Description of reference numerals:
[0015] 31. Power generation control command; 32. Power generation adjustment command; 33. Power generation command; 34. Electric energy; 35. Seawater; 36. Waste heat; 37. Status monitoring feedback information; 38. Initial startup power supply;
[0016] 101. Command interface; 102. Status interface; 103. Water source interface; 104. Power interface; 105. Output power interface; 106. Waste heat discharge interface;
[0017] 13. Operators; 15. Power supply; 16. Power grid; 17. Ocean;
[0018] 20. Nuclear reactor.
[0019] It should be noted that the drawings are not necessarily drawn to scale, but are merely shown in a schematic manner that does not affect the reader's understanding. DETAILED DESCRIPTION
[0020] Exemplary embodiments of the present application will be described below in conjunction with the accompanying drawings. For the sake of clarity and conciseness, not all features of the actual implementation are described in the specification. However, it should be understood that many implementation-specific decisions must be made in the process of developing any such actual implementation in order to achieve the developer's specific goals, such as meeting those constraints related to the system and business, and these constraints may vary from implementation to implementation. In addition, it should be understood that although the development work may be very complex and time-consuming, it is only a routine task for those skilled in the art who benefit from the content of this application.
[0021] It is also necessary to explain here that, in order to avoid obscuring the present application due to unnecessary details, only the device structure and / or processing steps closely related to the scheme according to the present application are shown in the accompanying drawings, while other details that are not very relevant to the present application are omitted.
[0022] The embodiment of the present application provides a model-based nuclear reactor demand analysis method, see Figure 1 , which includes: S1. Determine the mission scenarios of the entire life cycle stages of the nuclear reactor according to the power supply and heating capacity requirements of the nuclear reactor; S2. Determine the stakeholders of each mission scenario of the nuclear reactor corresponding to each life cycle stage according to the mission scenarios of the entire life cycle stages of the nuclear reactor; S3. Determine the stakeholder needs of the nuclear reactor according to the stakeholders of each mission scenario of the nuclear reactor corresponding to each life cycle stage; S4. Perform dynamic interactive scenario analysis based on the mission scenarios of the entire life cycle stages of the nuclear reactor and the stakeholder needs of the nuclear reactor to determine the model requirements of the nuclear reactor.
[0023] The method provided in the embodiment of the present application can carry out demand analysis based on the power supply and heating capacity requirements, take into account the entire life cycle stages of the nuclear reactor, determine the task scenarios of all life cycle stages, and determine the stakeholders based on the task scenarios of all life cycle stages. Then, determine the stakeholder needs based on the stakeholders of each task scenario, and perform dynamic scenario interaction analysis to determine the model requirements of the nuclear reactor, which is conducive to a more comprehensive analysis of the needs of the nuclear reactor and the determination of clearer and complete nuclear reactor requirements, thereby providing clear design goals for nuclear reactor designers to minimize the situation where the designed nuclear reactor cannot cover all needs or some needs are ignored.
[0024] In the demand analysis of related technologies, stakeholders are directly identified based on the entire life cycle. Compared with identifying stakeholders based on the entire life cycle, the demand analysis method of the embodiment of the present application starts with the analysis of the task scenarios of the entire life cycle. The method of using scenarios can more accurately and comprehensively identify stakeholders, and then sort out the needs of stakeholders. In addition, the embodiment of the present application performs dynamic scenario interaction analysis from the perspective of the task scenarios of the entire life cycle, and can comprehensively identify the external interfaces that the nuclear reactor should meet in various scenarios, thereby more comprehensively sorting out the model requirements of the nuclear reactor. In some embodiments, step S1 includes step S11 and step S12. S11. Determine the entire life cycle stages of the nuclear reactor based on the power supply and heating capacity requirements of the nuclear reactor; S12. Determine the task scenarios of the entire life cycle stages of the nuclear reactor based on the entire life cycle stages of the nuclear reactor.
[0025] In some embodiments, all life cycle stages of the nuclear reactor in step S11 may include: a procurement stage, a deployment stage, an operation stage, a support stage, and a withdrawal stage.
[0026] In some embodiments, all life cycle stages can be further divided according to the nuclear reactor mission requirements. For example, the acquisition stage may include the manufacturing stage and the purchasing stage; the deployment stage may include the installation stage, the commissioning stage, and the test stage; the operation stage may include the start-up stage and the power increase stage; the support stage may include the maintenance stage; and the exit stage may include the decommissioning stage.
[0027] In some embodiments, in step S12, when determining the corresponding mission scenario for each life cycle stage, the mission scenario can be determined based on the five life cycle stages of acquisition, deployment, operation, support, and exit, considering that the nuclear reactor "does something" in each life cycle stage.
[0028] Specifically, the task scenarios corresponding to the procurement stage include: transportation scenarios, etc.; the task scenarios corresponding to the deployment stage include: assembly and integration scenarios, debugging and testing scenarios, etc.; the task scenarios corresponding to the operation stage include: start-up scenarios, power increase scenarios, power operation scenarios, etc.; the task scenarios corresponding to the support stage include: maintenance scenarios, etc.; the task scenarios corresponding to the exit stage include: decommissioning scenarios, etc.
[0029] In some embodiments, in step S2, stakeholder identification may be performed based on various mission scenarios of the nuclear reactor to determine all stakeholders of the nuclear reactor.
[0030] Specifically, the identified stakeholders may include transportation regulatory authorities related to transportation scenarios, installers and nuclear safety regulatory authorities related to assembly and integration scenarios, and nuclear safety regulatory authorities, operators, surrounding residents, external environment, and oceans related to power operation scenarios. When identifying stakeholders for each mission scenario corresponding to each life cycle stage of a nuclear reactor, the integrity of the stakeholders should be ensured to avoid missing any stakeholders.
[0031] In some embodiments, step S2 may include: clustering and abstracting high-level stakeholders according to the same type of stakeholders from stakeholders of each task scenario in all life cycle stages based on their relationship with the nuclear reactor.
[0032] In some embodiments, in step S2, before clustering and abstracting high-level stakeholders according to the same type of stakeholders, it also includes: eliminating unnecessary stakeholders according to the task requirements of the nuclear reactor. In some embodiments, after determining all stakeholders of each task scenario corresponding to each life cycle stage, unnecessary stakeholders can be eliminated in combination with the task requirements of the nuclear reactor. For example, in the power operation scenario, the stakeholder of the surrounding residents is identified. In combination with the actual application scenario, if there are no residents around the operation site, this stakeholder is considered to be removed.
[0033] In some embodiments, when clustering and abstracting, attention should be paid to the uniformity of the number, and the number of high-level stakeholders is generally 7±2. In some embodiments, the high-level stakeholders of the cluster may be regulators, and the low-level stakeholders may be nuclear safety regulators, environmental protection departments, transportation regulatory departments, etc. In some embodiments, the above method can be implemented using a model.
[0034] In some embodiments, in step S3, a stakeholder demand analysis is performed on stakeholders of each task scenario corresponding to each life cycle stage of the nuclear reactor to determine the demands of each stakeholder of the nuclear reactor.
[0035] In some embodiments, for example, the stakeholders of the assembly and integration scenario in the deployment phase may be installers, and the installer requirements may be requirements for the installers to reserve installation space for the nuclear reactor, and the installation size may be proposed to be no less than a certain size; the stakeholders of the power operation scenario in the operation phase may be the environmental protection department, and the environmental protection department requirements may be requirements for the environmental protection department to require that the emissions of nuclear reactor waste gas, waste liquid, and waste solid do not exceed a specific threshold value; the stakeholders of the power operation scenario may also be users, and the user requirements may be requirements for users to require that the nuclear reactor can provide a certain amount of electrical energy; the stakeholders of the maintenance scenario in the support phase may be maintenance personnel, and the maintenance personnel requirements may be requirements for the maintenance personnel to reserve maintenance space for the nuclear reactor, and the size of the maintenance space may be no less than a certain size; the stakeholders of the decommissioning scenario in the exit phase may be the decommissioning support department, and the decommissioning support department requirements may be requirements for the decommissioning support department to reserve a disassembly and assembly interface for the nuclear reactor.
[0036] In some embodiments, step S4 includes step S41 and step S42. S41. According to the mission scenarios of all life cycle stages of the nuclear reactor, dynamic scenario interaction analysis is performed to define the external interface of the nuclear reactor. S42. According to the stakeholder needs and external interface of the nuclear reactor, the model requirements of the nuclear reactor are determined.
[0037] In some embodiments, in step S42, the requirements of stakeholders may be converted into model requirements of nuclear reactors or the external interface may be converted into model requirements of nuclear reactors to determine the model requirements of nuclear reactors. For example, the user's requirement that the nuclear reactor can provide a certain amount of electrical energy may be converted into the power generated by the nuclear reactor, or the waste heat discharge interface may be converted into an external interface requirement that the nuclear reactor must have to discharge waste heat to the external environment.
[0038] In some embodiments, see Figure 2 , step S1 may also include: S101, using SysML state machine diagram to build a nuclear reactor life cycle model, the nuclear reactor life cycle model uses SysML state machine diagram to represent all life cycle stages of the nuclear reactor. In some embodiments, step S1 may also include steps S102 and S103. S102, according to the nuclear reactor life cycle model, determine the task scenario corresponding to each life cycle stage of the nuclear reactor; S103, use SysML module definition diagram / use case diagram to build a task scenario model.
[0039] Specifically, step S101 also includes: using the power supply and heating capacity requirements of the nuclear reactor as input, identifying the life cycle stages of the nuclear reactor, and dividing the life cycle into five categories: acquisition, deployment, operation, support, and exit. According to the mission requirements of the nuclear reactor, the five life cycles are further divided, such as the acquisition stage is divided into the manufacturing stage, the procurement stage, etc., the deployment is divided into the installation stage, the commissioning stage, the test stage, etc., the operation is divided into the start-up stage, the power increase stage, etc., the support is divided into the maintenance stage, etc., and the exit is divided into the decommissioning stage, etc. The nuclear reactor life cycle stages represented by the SysML state machine diagram (i.e., the nuclear reactor life cycle model is constructed using the SysML state machine diagram) are used as output.
[0040] In some embodiments, in step S102, when determining the task scenarios corresponding to each life cycle stage, it is possible to consider the nuclear reactor "doing something" in each life cycle stage based on the five life cycle stages of acquisition, deployment, operation, support and exit, identify task scenarios, such as assembly and integration scenarios, debugging and test scenarios, reactor criticality scenarios, power increase scenarios, power operation scenarios, maintenance scenarios, etc., and use SysML module definition diagrams / use case diagrams to represent them.
[0041] Specifically, in step S103, the life cycle represented by the SysML state machine diagram can be used as input to obtain the task scenario represented by the SysML module definition diagram / use case diagram, such as transportation scenario, assembly integration scenario, debugging test scenario, stack startup scenario, power increase scenario, maintenance scenario, decommissioning scenario, etc.
[0042] In some embodiments, step S2 may also include: determining the stakeholders of the task scenarios of the nuclear reactor corresponding to each life cycle stage based on the task scenario model of all life cycle stages of the nuclear reactor; and constructing the stakeholder model of each task scenario of the nuclear reactor corresponding to all life cycle stages using the SysML module definition diagram.
[0043] In some embodiments, step S2 may also include: for the obtained stakeholders, clustering and abstracting high-level stakeholders according to the same type of stakeholders. Specifically, the nuclear reactor life cycle stage represented by the SysML state machine diagram can be used as input, and based on the task scenarios of the five life cycle stages of the nuclear reactor, such as procurement, deployment, operation, support, and exit, stakeholders can be identified, such as the transportation regulatory department related to the transportation scenario, the installers and nuclear safety regulatory department related to the assembly and integration scenario, the nuclear safety regulatory department, operators, surrounding residents, external environment, ocean, etc. related to the power operation scenario, to ensure the integrity of the stakeholders, and use the SysML module definition diagram to build a stakeholder model for each task scenario. The nuclear reactor stakeholders represented by the SysML module definition diagram are used as output.
[0044] Afterwards, a large number of stakeholders were obtained through task scenario identification. Not all stakeholders are directly related to nuclear reactors. Combined with the nuclear reactor model task, unnecessary stakeholders were eliminated.
[0045] After screening the stakeholders, the obtained stakeholders can be clustered and abstracted. Specifically, for stakeholders of the same type, high-level stakeholders are clustered and abstracted. An important requirement for clustering is the uniformity of quantity, and generally 7±2 high-level stakeholders are appropriate. For example, the high-level stakeholders of the cluster are regulators, and the low-level stakeholders are nuclear safety regulators, environmental protection departments, transportation regulators, etc.
[0046] In some embodiments, step S2 may also include: establishing a traceability relationship that reflects the association between the nuclear reactor life cycle and stakeholders, and using the SysML general matrix to construct a traceability matrix model of the nuclear reactor life cycle and stakeholders.
[0047] In some embodiments, step S3 may include: determining stakeholder requirements based on a stakeholder model of task scenarios in each life cycle stage of the nuclear reactor; and constructing a stakeholder requirement model using a SysML requirement diagram.
[0048] Specifically, the nuclear reactor stakeholders represented by the SysML module definition diagram can be used as input, the stakeholder requirements template can be used to define the stakeholder requirements, and the stakeholder requirements model can be represented by the SysML requirement diagram as output.
[0049] When defining stakeholder requirements, the stakeholder requirements template can be used to define stakeholder requirements. The stakeholder requirements template can be: <stakeholder> (who) should be able to / need to <do / get> (what or how) at <life cycle stage> (when and / or where) with <expected performance level> (degree). Nuclear reactor stakeholder requirements can be shown in Table 1.
[0050] Table 1 Examples of stakeholder needs
[0051]
[0052] In some embodiments, step S3 may further include: using a SysML general matrix to construct a traceability matrix model between stakeholders and stakeholder requirements, where the traceability matrix model may reflect the associated traceability relationship between stakeholders and stakeholder requirements.
[0053] In some embodiments, step S4 may also include: determining the dynamic interaction process between the stakeholders and the nuclear reactor based on the task scenario model, and constructing a dynamic interaction scenario model using a SysML sequence diagram; performing dynamic scenario interaction analysis based on the dynamic interaction scenario model, determining the external interface of the nuclear reactor, and constructing an external interface model using a SysML internal block diagram; determining the model requirements of the nuclear reactor based on the stakeholder requirement model and the external interface model, and constructing a model requirement model of the nuclear reactor using a SysML requirement diagram / requirement list.
[0054] Specifically, the task scenario model of the whole life cycle stage and the stakeholder demand model are used as input, and the SysML sequence diagram is used to analyze the dynamic interaction process between stakeholders and nuclear reactors.
[0055] In some embodiments, taking the power operation dynamic interaction scenario as an example, the dynamic interaction process between stakeholders and the nuclear reactor is analyzed, such as Figure 3 As shown, the operator 13 sends a power generation control instruction 31 to the nuclear reactor 20; the power supply 15 can provide the nuclear reactor 20 with an initial startup power supply 38; the ocean 17 can provide seawater 35 to the nuclear reactor 20; the nuclear reactor 20 receives the power generation control instruction 31, and outputs a power generation adjustment instruction 32 and a power generation instruction 33 to itself according to the power generation control instruction 31, so as to adjust the power generation power and generate electricity, and then the nuclear reactor 20 outputs electric energy 34 to the power grid 16, and discharges waste heat 36 to the ocean 17; the nuclear reactor 20 can also send status monitoring feedback information 37 to the operator 13.
[0056] According to the dynamic interaction process between stakeholders and the nuclear reactor, the external interface of the nuclear reactor is determined, and the external interface model is constructed using the SysML internal block diagram. The external interfaces of the nuclear reactor are determined, such as the command interface, status interface, output power interface, waste heat discharge interface, water source interface, power supply interface, etc.
[0057] In some embodiments, taking the external interface of the power operation dynamic interaction scenario as an example, the schematic diagram of the external interface of the nuclear reactor is determined as follows: Figure 4 As shown, the operator 13 can send instructions to the nuclear reactor 20 through the instruction interface 101; the nuclear reactor 20 can send status information to the operator 13 through the status interface 102; the power supply 15 can provide power to the nuclear reactor 20 through the power supply interface 104; the ocean 17 can provide water to the nuclear reactor 20 through the water source interface 103; the nuclear reactor 20 transfers heat to the ocean 17 through the waste heat discharge interface 106; the nuclear reactor 20 outputs electrical energy to the power grid 16 through the output power interface 105.
[0058] In some embodiments, after the external interface is determined, the stakeholder requirement model represented by the SysML requirement diagram and the external interface model represented by the SysML internal block diagram are used as inputs to construct the model requirement model of the nuclear reactor using the SysML requirement diagram / requirement list. The model requirement model of the nuclear reactor can be constructed using the SysML requirement diagram / requirement list as output.
[0059] In some embodiments, when using the SysML requirement list to construct a model requirement model for a nuclear reactor, the requirements of stakeholders and external interfaces of the nuclear reactor can be sorted out to determine the model requirements of the nuclear reactor. Specifically, the requirements of stakeholders can be converted into the model requirements of the nuclear reactor. For example, if a user requires that the nuclear reactor can provide electrical energy xx (corresponding to the requirements of stakeholders), the requirement can be converted into the power generation of the nuclear reactor xx (corresponding to the model requirements of the nuclear reactor). For another example, the nuclear reactor needs to have an interface for discharging waste heat to the external environment.
[0060] In some embodiments, the model requirements of the sorted nuclear reactors can be classified with reference to the demand classification method, for example, they can be divided into functional requirements, performance requirements, interface requirements, etc. Among them, the functional requirements may include that the power generation power of the nuclear reactor is a certain power, the nuclear reactor can discharge residual heat, and the nuclear reactor can operate and control; the performance requirements may include the weight of the nuclear reactor, the size of the nuclear reactor, the reliability requirements of the nuclear reactor, and the life of the nuclear reactor; the interface requirements may include that the nuclear reactor must have an interface for discharging waste heat to the external environment, and the nuclear reactor must have an interface for power supply and distribution. Examples of model requirements for nuclear reactors are shown in Table 2.
[0061] Table 2 Examples of model requirements for nuclear reactors
[0062]
[0063]
[0064] In some embodiments, step S4 may further include: using the SysML general matrix to construct a traceability matrix model of the model requirements of the nuclear reactor and the needs of stakeholders; the traceability matrix model may reflect the associated traceability relationship between the model requirements of the reactor and the needs of stakeholders.
[0065] The method provided according to the embodiment of the present application can finally output a dynamic interaction scenario model represented by a SysML sequence diagram and a model requirement of a nuclear reactor represented by a SysML requirement diagram / requirement list.
[0066] The demand analysis method of the embodiment of the present application establishes the associated traceability of task scenarios, stakeholders, stakeholder requirements, and model requirements throughout the entire life cycle, so that the model requirements of the nuclear reactor can be changed when user requirements or application scenarios change.
[0067] Regarding the embodiments of the present application, it should also be noted that, in the absence of conflict, the embodiments of the present application and the features therein can be combined with each other to obtain new embodiments.
[0068] The above are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. The protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A model-based nuclear reactor demand analysis method, characterized in that: include: S1. Determine the mission scenarios of all life cycle stages of the nuclear reactor according to the power supply and heating capacity requirements of the nuclear reactor; S2. Determine the stakeholders of each task scenario corresponding to each life cycle stage of the nuclear reactor according to the task scenarios of all life cycle stages of the nuclear reactor; S3, determining the stakeholder needs of the nuclear reactor according to the stakeholders of each task scenario corresponding to each life cycle stage of the nuclear reactor; S4. Perform dynamic interactive scenario analysis based on the mission scenarios of all life cycle stages of the nuclear reactor and the needs of stakeholders of the nuclear reactor to determine the model requirements of the nuclear reactor.
2. The method according to claim 1, characterized in that The S1 step includes: S11, determining the entire life cycle stages of the nuclear reactor according to the power supply and heat supply capacity requirements of the nuclear reactor; S12. Determine the mission scenarios of all life cycle stages of the nuclear reactor according to all life cycle stages of the nuclear reactor.
3. The method according to claim 1, characterized in that The S2 step further includes: According to the relationship with the nuclear reactor, the stakeholders of each task scenario in all life cycle stages are clustered and abstracted into high-level stakeholders according to the same type of stakeholders.
4. The method according to claim 2, characterized in that: The entire life cycle phases of the nuclear reactor in step S11 include: procurement phase, deployment phase, operation phase, support phase and exit phase.
5. The method according to claim 1, characterized in that: The S4 step includes: S41, performing dynamic scenario interaction analysis according to the mission scenarios of all life cycle stages of the nuclear reactor, and defining the external interface of the nuclear reactor; S42. Determine the model requirements of the nuclear reactor according to the stakeholder requirements and external interfaces of the nuclear reactor.
6. The method according to claim 1, characterized in that The step S1 further includes: constructing a nuclear reactor life cycle model using a SysML state machine diagram, wherein the nuclear reactor life cycle model uses a SysML state machine diagram to represent all life cycle stages of the nuclear reactor.
7. The method according to claim 6, characterized in that The S1 step further includes: Determining, according to the reactor life cycle model, mission scenarios for all life cycle stages of the nuclear reactor; Use SysML module definition diagram / use case diagram to build task scenario model.
8. The method according to claim 7, characterized in that The S2 step further includes: Determining stakeholders of the task scenario model of the nuclear reactor corresponding to each of the life cycle stages according to the task scenario model; The stakeholder model of each task scenario corresponding to each life cycle stage of the nuclear reactor is constructed using SysML module definition diagram.
9. The method according to claim 8, characterized in that The S3 step further includes: Determining stakeholder needs based on a stakeholder model of mission scenarios corresponding to each life cycle stage of the nuclear reactor; Build stakeholder requirements model using SysML requirement diagrams.
10. The method according to claim 9, characterized in that The S4 step further includes: According to the task scenario model, determining the dynamic interaction process between the stakeholder and the nuclear reactor, and constructing the dynamic interaction scenario model using a SysML sequence diagram; Performing dynamic interaction scenario analysis according to the dynamic interaction scenario model, determining the external interface of the nuclear reactor, and constructing the external interface model using a SysML internal block diagram; According to the stakeholder requirement model and the external interface model, the model requirements of the nuclear reactor are determined, and the model requirement model of the nuclear reactor is constructed using a SysML requirement diagram / requirement list.