System demand analysis method based on system scene

Abstract

The invention discloses a system demand analysis method based on a system scene. The method comprises the following steps: analyzing a task scene; scene operation description; establishing a system capability network; the task scene analysis comprises the steps of selecting an initial scene, defining a scene role and determining a scene high-level concept, and the scene operation description comprises scene operation activity description, scene operation time sequence description and role state description. The establishment of the system capability network comprises capability framework selection, activity-capability mapping and capability relationship description, and the system function division and demand analysis comprises system function description, system function analysis and function-demand mapping. According to the method, a good solution is provided for system demand argumentation with scenes as input in engineering application, and the problems that in the prior art, complex system demand argumentation is difficult to promote, and a scene-based system demand analysis methodology is lacked are solved.

Description

Technical Field

[0001] The present invention relates to a model-based system engineering and a process method for conducting system demand analysis in the early stage of model-based system engineering system development, belongs to the field of system engineering, and specifically relates to a system demand analysis method based on system scenarios. Background Art

[0002] With the increasing complexity of application requirements and application scenarios and the continuous expansion of system structures, the complexity and diversified requirements of systems are becoming more prominent than ever before. In the process of system design, designers are often faced with the influence of external roles in the scenario and the interweaving of multiple task requirements. In order to cope with this complex challenge, the design concept of system engineering came into being. System engineering systematically describes multiple systems and their mutual combinations, starts from a more macro perspective, and comprehensively analyzes and designs the system from a task-oriented perspective. How to effectively utilize the scenario analysis ideas contained in system engineering and use them to guide the development of complex systems is an urgent problem to be solved in the field of system engineering and system engineering.

[0003] In the system development life cycle, for new systems, the effectiveness of the demand demonstration process is directly related to the quality and efficiency of subsequent system development. In the demand demonstration stage, how to capture and analyze the effective system requirements for the system operation scenario is a key link. Through the smooth implementation of this process, the system requirements development work under the task scenario can be completed in a targeted and efficient manner. Effective system requirements analysis not only lays a solid foundation for the forward design of the system, but also promotes the simulation and verification of the system digital twin prototype, shortens the development cycle and improves system reliability and adaptability. In order to quickly and effectively realize the transformation from scenario analysis to system requirements, a scientific methodology needs to be adopted to guide this process.

[0004] In recent years, the construction of combat systems and the research and development of key combat systems have become increasingly important parts of national defense and military construction. In the development of some emerging combat equipment, unlike the traditional single equipment design ideas, the system environment on which the equipment operates is often taken into consideration, and the basic needs that the equipment needs to meet are explored from a larger perspective of equipment research and development demonstration. The combat system design has gradually evolved from the combat dimension of a single combat field or a single weapon system to a global, diversified, and broad system dimension, and the demonstration system has changed from the demonstration of equipment to a higher-level system demonstration. The design method based on the combat system can shift the idea of ​​designing equipment from a narrow single equipment to a broader combat system perspective. After the combat system is interpreted, the application scenarios and basic characteristics of the equipment are first grasped to a certain extent, and then the equipment monomer design or equipment demand capture content is transferred to make the equipment demand capture process more complete and reliable, so that the designed equipment is more suitable for a specific scenario.

[0005] In this context, the DoDAF framework, as a standardized system architecture tool, demonstrates its significant advantages in the development of complex systems. DoDAF can comprehensively express the system structure, capabilities, and role relationships in the scenario through multiple views, thereby providing strong support in system construction and system analysis. By using the UPDM language to describe the process view, multi-level expression and analysis from task scenarios to system requirements can be achieved. This method provides effective theoretical and tool support for system construction and system analysis, making the demand demonstration process from task scenarios to system capabilities and then to system requirements more smoothly implemented, and ultimately achieving the systematization and standardization of system requirements analysis.

[0006] The existing system modeling and MBSE modeling methods mainly belong to the forward modeling methodology. In general, the system requirements are relatively clear, and there is a lack of demand verification methodology that starts with system operation scenarios and analyzes complex systems in the conceptual stage.

[0007] Based on the basic views of the DoDAF framework, the present invention proposes a step-by-step and clear system requirement analysis method. The analysis work starts from the proposed task scenario, and then some DoDAF viewpoints and related views are selected to carry out modeling work using the DoDAF multi-view modeling idea, completing the step-by-step construction and analysis work from task scenario-system capability-system requirement. This solves the problems of lack of relevant methodological support in the task scenario input modeling process and insufficient comprehensiveness and standardization in the initial capability analysis process of system demonstration. Summary of the invention

[0008] In view of the problems in the prior art that the effectiveness of the complex system requirement demonstration process is poor, the requirement demonstration process is difficult to promote, and there is a lack of scenario-based system requirement analysis methodology, the purpose of the present invention is to provide a system requirement analysis method based on system scenarios, and with the help of the existing DoDAF system modeling framework, using system engineering and the standardization idea of ​​system engineering, the existing DoDAF views are tailored, and the commonly used views in the scenario modeling and system requirement analysis process are selected for analysis, and a DoDAF system modeling method is determined. The system requirement analysis based on the system scenario is completed through standardized construction work, which is convenient for engineering personnel to quickly complete the system requirement analysis work based on this method, so as to carry out the next step of system design.

[0009] In view of the above-mentioned technical problems and the purpose of the present invention, a system requirement analysis method based on system scenario is proposed, which includes the following parts: Step A: task scenario analysis, wherein the specific method of the task scenario analysis is: analyzing the operation scenarios that play a key role in the system to be analyzed and the task execution status that the demand analysis party is concerned about; Step B: Scenario operation description, wherein the specific method of the scenario operation description is: analyzing and describing the activities, timing, and role status of the scenario operation in the running scenario; Step C: Establishing a system capability network, wherein the specific method of establishing the system capability network is: taking the task scenario in step A as the goal to be achieved, according to the scenario operation description formed in step B, decomposing the operating scenario environment conditions required to meet the goal into the capabilities that each scenario role should meet, and arranging the capabilities according to a certain orderly organizational structure, so as to establish the system capability network; Step D: System function division and demand analysis, wherein the specific approach of the system function division and demand analysis is: convert the indicators contained in the system capabilities into the elements required for system development, and divide the functional components required to meet the system functions, and on the basis of the system functions, analyze the system requirements that the system should meet the corresponding functions.

[0010] Preferably, the task scenario analysis includes the following steps: Step A1: Selecting an initial scenario, wherein the specific method of selecting the initial scenario is: selecting a suitable system actual operation scenario to carry out system demand analysis according to the task requirements and the need for the system to carry out conceptual design; Step A2: clarifying the scene roles, wherein the specific method of clarifying the scene roles is: according to the initial scene selected in step A1, the scene life cycle boundary is selected using the system engineering concept, and all the participating roles within the selected scene are clearly selected; Step A3: Determine the high-level concept of the scenario, wherein the specific method of determining the high-level concept of the scenario is: based on the assumed results of steps A1 and A2, describe the interactive relationship between the system and the external environment and between systems contained in the scenario.

[0011] Preferably, the scenario operation description includes the following steps: Step B1: Scenario operation activity description, wherein the specific method of the scenario operation activity description is: based on the initial scenario, scenario roles and scenario high-level concepts conceived in steps A1-A3, the scenario operation activities of the system and external environment roles are analyzed, and the important role activities are analyzed and described in detail according to the needs below; Step B2: Scenario running timing description, wherein the specific method of the scenario running timing description is: based on the initial scenario, scenario roles and scenario high-level concepts conceived in steps A1-A3, referring to the scenario running activity description carried out in step B1, the scenario running timing of the system and external environment roles is analyzed; Step B3: role status description, wherein the specific method of the role status description is: based on the initial scene, scene role and scene high-level concept conceived in steps A1-A3, refer to the scene operation activity description and scene operation timing description carried out in steps B1 and B2, and analyze the operation status of the system of concern.

[0012] Preferably, the establishment of the system capability network comprises the following steps: Step C1: Selection of capability framework, wherein the specific method of selecting the capability framework is: according to the system capabilities and object indicators of concern, a system top-level capability classification method is selected as a container that encompasses all capabilities to describe the system capability structure; Step C2: Activity-capability mapping, wherein the specific method of the activity-capability mapping is: according to the scenario operation activity description formed in step B1, the system capabilities that are required and supportive for the execution of a scenario activity corresponding to the execution role swim lane are assumed, and the support relationship between the activities and the capabilities is expressed in the form of a mapping matrix; Step C3: Description of capability relationships, wherein the specific method of the capability relationship description is as follows: according to the system capabilities assumed from the activities in step C2 and the top-level system capabilities selected in step C1, all existing capability granularities are allocated to the roles related to them, and the hierarchical relationships and dependency relationships between capabilities are assumed to be described, thereby forming a multi-view system capability network.

[0013] Preferably, the system function division and demand analysis includes the following steps: Step D1: system function description, wherein the specific method of the system function description is: according to the system capabilities allocated to the system of concern in step C3, the support relationship between the system function components and the system capabilities associated with the system of concern is mapped, and a system function component description is formed; Step D2: System function analysis, wherein the specific method of the system function analysis is: according to the scenario operation activity description determined in step B1 and the role status description determined in step B3, a system function activity diagram is established with functional components as role swim lanes, and the full life cycle function operation process of the system corresponding to the role in the scenario is analyzed; Step D3: Function-requirement mapping, wherein the specific method of the function-requirement mapping is: according to the system function component description formed in step D1 and the system function analysis formed in step D2, based on the existing functional components of the system, the system requirements required to meet a certain function of the system are assumed, and the supporting relationship between the system function components and the assumed system requirements is mapped, thereby completing the system requirement description.

[0014] Through the above steps, this method proposes a system requirements analysis method based on system scenarios, which solves the problem of the difficulty in promoting complex system requirements demonstration in the existing technology and the lack of scenario-based system requirements analysis methodology. From the perspective of system engineers and system engineers, the system requirements analysis work based on system scenarios is completed. The modeling rules established by this method can be reused in complex system designs in multiple fields, and can provide a scenario-based demand condition input framework for subsequent system digital twin design and system digital prototype simulation.

[0015] The innovations of this system requirement analysis method based on system scenarios are mainly reflected in the following aspects: 1. Scenario-based requirements analysis: This method introduces scenario-based system requirements analysis, which is a non-forward system engineering modeling approach. It flexibly selects known conditions and describes the task scenarios to ensure that system requirements and capability analysis are closely integrated with actual scenarios, thus improving the effectiveness and pertinence of requirements demonstration.

[0016] 2. Introduce multi-view modeling to assist demand analysis after DoDAF tailoring: Perform demand-based tailoring on the existing DoDAF system modeling framework, select views related to scenario modeling and system demand analysis, reduce unnecessary view construction in the forward system engineering and system engineering design process, and conduct demand analysis on the system through an effective multi-view perspective, thereby improving modeling efficiency.

[0017] 3. Combination of system engineering and system engineering: Combining the ideas of system engineering and system engineering, through standardized processes and steps, ensure the comprehensiveness and scientificity of demand analysis, and provide a standardized and structured demand analysis method.

[0018] In summary, this system requirement analysis method based on system scenarios provides a good solution for system requirement justification with scenarios as input in engineering applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1 The present invention is a flow chart of the method. DETAILED DESCRIPTION

[0021] The method of the present invention is further described below in conjunction with the accompanying drawings and specific implementation examples. It should be understood that the implementation examples described herein are only used to illustrate and explain the present invention and are not limited to the present invention.

[0022] The purpose of this invention is to provide a system requirement analysis method based on system scenarios. Considering that it is difficult to complete the process of capability analysis of key roles in the scenario based on scenario input, combined with the DoDAF view framework, the scenario analysis and the task effectiveness that the system should have are first discussed, and then the constructed scenario activities and system effectiveness are transformed to form an analysis process for the system, so that the requirement demonstration process is linked together, the effectiveness and pertinence of the process demonstration are improved, and the rapidity and continuity of engineering analysis are maintained. It has good practical application value.

[0023] The present invention will be further described below in conjunction with the accompanying drawings and specific implementation methods.

[0024] The embodiment of the present invention takes a certain close-range strike system as an example, and takes a small glide guided bomb of a UAV as a research object of concern to illustrate the method of the present invention. In terms of the needs of close support and close-range strike, the UAV is required to use a suitable ammunition to perform close-range strikes on the enemy. Based on this demand, the research of low-cost, small-yield, and precise strike weapons of UAVs has become an urgent action for both warring parties. Based on this mission requirement, it is now necessary to analyze the system scenario, thereby leading to the concern demand of small glide guided bombs.

[0025] In order to achieve the above object, the technical solution adopted by the method of the present invention is: The present invention provides a system requirements analysis method based on system scenarios, and its process is as follows Figure 1 As shown, the steps are as follows: Step A: Task scenario analysis; Step B: Scenario operation description; Step C: Establish a system capability network; Step D: System function division and requirements analysis.

[0026] Through the above steps, this method solves the problem of gradually advancing from scenario analysis and gradually pulling out system concern capabilities through task requirements. In addition, this method uses a modeling process based on the DoDAF framework with strong reusability, which facilitates the further development and implementation of subsequent model-based capability analysis and has good practical application value.

[0027] The specific method of the task scenario analysis described in step A is to analyze the operation scenarios that play a key role in the system to be analyzed and the task execution status that the demand analysis party is concerned about. The task scenario analysis described in step A includes the following steps: Step A1: Select the initial scene; Step A2: Identify the scene roles; Step A3: Determine the high-level concept of the scene; The specific steps of selecting the initial scenario in step A1 are as follows: according to the task requirements and the need for the system to carry out conceptual design, select a suitable system actual operation scenario to carry out system requirements analysis, and carry out description work with the help of the AV-1 view of the DoDAF2.0 view in this step; The specific method of clarifying the scene roles in step A2 is as follows: according to the initial scene selected in step A1, the scene life cycle boundary is selected using the system engineering concept, and all the participating roles within the selected scene are clarified; The high-level concept of the scenario described in step A3 has the following specific meanings: The term high-level concept of the scenario is derived from the broad extension of the high-level operational concept in the DoDAF view, which is expressed in a combination of graphics and text to highlight the interactive relationship between the system and the external environment and between systems in the scenario, and provide conceptual assumptions for the large-scale architecture model involving multiple roles; The specific steps for determining the high-level concept of the scenario in step A3 are as follows: Based on the results of steps A1 and A2, describe the interaction between the system and the external environment and between the systems in the scenario. In this step, the description can be carried out with the help of the OV-1 view of the DoDAF2.0 view; Among them, for step A, the initial scenario selected is the UAV close-range strike system. Based on the unmanned close-range strike system, the AV-1 scenario overview view and the OV-1 scenario high-level combat concept diagram are established. In the specific implementation case, the detailed description of the establishment of the view is as follows: The AV-1 overview view used reflects the initial system scenario goals, the elements included in the initial system scenario architecture, and the initial system scenario concerns, so as to facilitate further analysis based on the system scenario in the following text. In the case, it is reflected as the tasks that the close-range strike system should complete and the architecture of the close-range strike system. The OV-1 scenario high-level conceptual view is used to depict the important interactions of the roles contained in the scenario. While establishing the prototype of the scenario analysis, the OV-1 view analysis can clarify the information flow and the performance of the role interactions. In the case, it is reflected in the performance of the scenario roles of the close strike system and the important interactive relationships between the roles.

[0028] The specific method of the scenario operation description in step B is: analyzing and describing the activities, timing, and role status of the scenario operation in the running scenario. The scenario operation description in step B includes the following steps: Step B1: Scenario running activity description; Step B2: Scenario running timing description; Step B3: Character status description; The specific steps for describing the scenario operation activities in step B1 are as follows: Based on the initial scenario, scenario roles and scenario high-level concepts conceived in steps A1-A3, analyze the scenario operation activities of the system and external environment roles, and conduct detailed analysis and description of important role activities according to the needs below. In this step, the description work can be carried out with the help of the OV-5b view of the DoDAF2.0 view; The specific method of describing the scenario running timing in step B2 is as follows: based on the initial scenario, scenario roles and scenario high-level concepts conceived in steps A1-A3, refer to the scenario running activity description carried out in step B1, analyze the scenario running timing of the system and external environment roles, and the description work can be carried out with the help of the OV-6c view of the DoDAF2.0 view in this step; The specific steps of the role status description in step B3 are as follows: based on the initial scenario, scenario roles and high-level scenario concepts envisioned in steps A1-A3, refer to the scenario operation activity description and scenario operation timing description carried out in steps B1 and B2 to analyze the operation status of the system of concern. In this step, the description work can be carried out with the help of the SV-10b view of the DoDAF2.0 view.

[0029] Among them, for step B, in a specific implementation case, a detailed description of establishing a view is as follows: In the OV-5 operational activity view used, the operational activities of the entire scenario are analyzed based on the related views constructed in step A of the case, including the description of the high-level concepts of the scenario and the activities of the role objects. In the case, it is reflected in the description of the entire process of activities from discovering important enemy targets to the strike of unmanned aerial vehicles in the close-range strike system; In the OV-6c runtime view used, based on the related view constructed in case step A and the scenario operation activity diagram constructed in step B1, the scenario runtime is further analyzed, including the description of the signal evolution and execution sequence of each role based on the scenario runtime, which is reflected in the case as the timing description of the relevant roles in the entire process of the selected close-range strike system activity; In the SV-6c role status view used, based on the related views constructed in case step A and the scenario operation activity diagram and scenario operation timing diagram constructed based on case steps B1 and B2, the system's concern capability system to be captured is further analyzed, including a description of the execution status, state evolution strategy, and state jump signal of the system of concern. In the case, it is reflected in the status description of the system of concern of the selected close-range strike system - the glide guided bomb system.

[0030] The specific method of establishing the system capability network in step C is: taking the task scenario in step A as the goal to be achieved, according to the scenario operation description formed in step B, decomposing the operating scenario environment conditions required to meet the goal into the capabilities that should be met by each scenario role, and arranging the capabilities according to a certain orderly organizational structure, so as to establish the system capability network. The establishment of the system capability network in step C includes the following steps: Step C1: Selection of competency framework; Step C2: Activity-capability mapping; Step C3: capability relationship description; The specific steps for selecting the capability framework described in step C1 are as follows: According to the system capabilities and indicators of the concerned objects, a system top-level capability classification method is selected as a container that encompasses all capabilities to describe the system capability structure. In this step, the description work can be carried out with the help of the CV-1 view in the DoDAF2.0 view; The specific steps of the activity-capability mapping described in step C2 are as follows: Based on the scenario operation activity description formed in step B1, the system capabilities that are required and supportive for the execution of a scenario activity corresponding to the execution role swim lane are assumed, and the support relationship between activities and capabilities is expressed in the form of a mapping matrix. In this step, the description work can be carried out with the help of the CV-6 view in the DoDAF2.0 view; The capability relationship described in step C3 specifically means: the cross-linking relationship between system capabilities, including the superior-subordinate relationship and the dependency relationship; The specific steps of describing the capability relationship in step C3 are as follows: according to the system capabilities assumed from the activities in step C2 and the top-level system capabilities selected in step C1, all existing capability granularities are allocated to the roles related to them, and the hierarchical relationships and dependencies between the capabilities are described, thereby forming a multi-view system capability network. In this step, the description work can be carried out with the help of the CV-2 and CV-4 views in the DoDAF2.0 view; Among them, for step C, in a specific implementation case, a detailed description of establishing a view is as follows: In the CV-1 capability top-level view used, based on the related views constructed in case steps A and B, a top-level capability classification method suitable for the case is selected to facilitate capability allocation and stratification needs. There are many common system effectiveness or system top-level capability classification methods, such as the six-character capability classification method, the joint combat regulations requirement classification method, and the US military C4ISR requirement classification method. In the case, due to the need to reflect the relevant capabilities of close-range strike operations, the commonly used military framework C4ISR is selected as the basic system capability classification idea, and the various capabilities that the close-range strike system needs to meet are divided into command, communication, reconnaissance and combat capabilities, and are allocated to their related roles as the top-level classification method of capabilities; In the CV-6 activity-capability mapping matrix view used, based on the scenario operation description related view constructed in step B of the case, according to the capability top-level view established in step C1, the capabilities that need to be met for the important scenario operation activities are assumed, and the mapping relationship is carried out in the view, and the capabilities that the assumed activities should meet are classified according to the classification method of the scenario top-level capabilities according to the classification method of the top-level framework. In the case, according to the scenario operation description in step B, the allocation relationship between the included scenario activities and the capabilities that the activities should meet is defined, and finally the CV-6 activity-capability mapping matrix view is formed.

[0031] In the CV-2 capability classification view used, based on the scenario operation description related views constructed in case steps A and B, the capabilities are further allocated to roles according to the capability top-level view established in step C1 and the activity-capability mapping matrix view established in step C2, and the capability description that each role needs to meet in the system is supplemented, thereby establishing a description of the hierarchical relationship between capabilities and capabilities. In the case, based on the capability top-level view established in step C1 and the activity-capability mapping matrix view established in C2, a description view of the hierarchical relationship of the close-range strike system capabilities is formed.

[0032] In the CV-4 capability dependency description view used, based on the scenario operation description related views constructed in case steps A and B, the capabilities that need to be met by each activity and the dependency relationship between the capabilities are described according to the activity-capability mapping matrix view established in step C2, which is used as a supplementary view of the CV-2 capability classification view used to illustrate the cross-linking relationship between system capabilities and capabilities. In the case, according to the activity-capability mapping matrix view established in C2 and referring to the close-range strike system activity diagram, the dependent capabilities of the system-related system capabilities are described. For example, for the target damage capability in the system, this capability depends on the target guidance capability of satellites and guided bombs, the maneuverability of guided bombs, the bomb payload capability, the maneuverability of drones, and the payload capability of drones. The target damage capability can be improved by focusing on its dependent capabilities.

[0033] The specific method of system function division and demand analysis described in step D is: converting the indicators contained in the system capability into the elements required for system development, and dividing the functional components required to meet the system functions, and on the basis of the system functions, analyzing the system requirements that the system should meet the corresponding functions. The system function division and demand analysis described in step D includes the following steps: Step D1: system function description; Step D2: System function analysis; Step D3: Function-requirement mapping; The specific method of the system function description in step D1 is as follows: according to the system capabilities assigned to the system of concern in step C3, the support relationship between the system function components and the system capabilities associated with the system of concern is mapped, and a description of the system function components is formed. In this step, the description work can be carried out with the help of the SV-4 view in the DoDAF2.0 view; The specific method of the system function analysis in step D2 is as follows: according to the scenario operation activity description determined in step B1 and the role status description determined in step B3, a system function activity diagram is established with the function component as the role swimlane, and the full life cycle function operation process of the system corresponding to the role in the scenario is analyzed. In this step, the description work can be carried out with the help of SysML activity diagram; Among them, the function-requirement mapping described in step D3 is specifically done as follows: according to the system function component description formed in step D1 and the system function analysis formed in step D2, based on the existing functional components of the system, the system requirements required to meet a certain function of the system are assumed, and the supporting relationship between the system functional components and the assumed system requirements is mapped. In this step, the description work can be carried out with the help of the CV-6 view in the DoDAF2.0 view, thereby completing the system requirement description.

[0034] Among them, for step D, in a specific implementation case, a detailed description of establishing a view is as follows: In the SV-4 system function description view used, based on the system capability network constructed in step C of the case, the system capabilities of the system to be analyzed are extracted, and the system functional component description is formed according to the system capabilities to be met and the actual design requirements of the system, and the system functions are completed and the system concerned can complete the system capabilities related to the system according to the functional components, thereby forming a system functional description. In the case, according to the close-range strike system capability network constructed in step C, with reference to the actual system composition of the glide guided bomb, the functional component description of the glide guided bomb system is formed, and the corresponding concerned capabilities and functions that need to be realized by the system are allocated, explaining the allocation relationship between functional components and system capabilities.

[0035] In the SysML activity diagram used, based on the scenario operation description related views constructed in step B of the case, according to the system functional component description formed in step D1, the scenario operation activity description established in step B1 corresponds to the activities of the system swim lane and is further described in the system functional component, changing from the perspective of system activities to the perspective of system internal functions, thereby realizing system functional analysis. In the case, the entire process of the guided bomb system from power-on to delivery and detonation in a close-range strike is re-described from the perspective of the system internal functions, showing the internal mechanism relationship of the guided bomb system.

[0036] In the CV-6 activity-capability mapping matrix view used, based on the system function description view established in step D1 and the functional analysis results conducted in step D2, the system requirements that should be implemented by each functional component of the system are assumed, and the system function-requirement mapping matrix view is completed. Through the representation of this view, the traceability relationship between system requirements and system functions is established. In this case, the system requirements that the system function realization depends on are used as the main capability division perspective. Through the established guided bomb system functional description and combined with the guided bomb system functional analysis results, the guided bomb system requirements are analyzed.

[0037] According to the above steps, the specific implementation of the system requirements analysis method based on system scenarios can be completed. It should be noted that the figures involved in this article are only analysis examples involving a single scenario and a single complex system to be analyzed. When conducting system requirements analysis for multiple scenarios, it is necessary to construct various scenario operation descriptions of multiple scenarios in step B; when conducting analysis for multiple complex systems to be analyzed, it is necessary to construct system requirements analysis descriptions for multiple systems in step D.

[0038] The above is a detailed description of a system requirement analysis method based on a system scenario provided by the present application. This article uses specific examples to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and its core idea of ​​the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

Claims

1. A system requirements analysis method based on system scenarios, characterized in that: The method comprises the following steps: Step A: task scenario analysis, wherein the specific method of the task scenario analysis is: analyzing the operation scenarios that play a key role in the system to be analyzed and the task execution status that the demand analysis party is concerned about; Step B: Scenario operation description, wherein the specific method of the scenario operation description is: analyzing and describing the activities, timing, and role status of the scenario operation in the running scenario; Step C: Establishing a system capability network, wherein the specific method of establishing the system capability network is: taking the task scenario in step A as the goal to be achieved, according to the scenario operation description formed in step B, decomposing the operating scenario environment conditions required to meet the goal into the capabilities that each scenario role should meet, and arranging the capabilities according to a certain orderly organizational structure, so as to establish the system capability network; Step D: System function division and demand analysis, wherein the specific approach of the system function division and demand analysis is: convert the indicators contained in the system capabilities into the elements required for system development, and divide the functional components required to meet the system functions, and on the basis of the system functions, analyze the system requirements that the system should meet the corresponding functions.

2. A system requirement analysis method based on system scenario as claimed in claim 1, characterized in that: The task scenario analysis includes the following steps: Step A1: Selecting an initial scenario, wherein the specific method of selecting the initial scenario is: selecting a suitable system actual operation scenario to carry out system demand analysis according to the task requirements and the need for the system to carry out conceptual design; Step A2: clarifying the scene roles, wherein the specific method of clarifying the scene roles is: according to the initial scene selected in step A1, the scene life cycle boundary is selected using the system engineering concept, and all the participating roles within the selected scene are clearly selected; Step A3: Determine the high-level concept of the scenario, wherein the specific method of determining the high-level concept of the scenario is: based on the assumed results of steps A1 and A2, describe the interactive relationship between the system and the external environment and between systems contained in the scenario.

3. A system requirement analysis method based on system scenario as claimed in claim 2, characterized in that: The scenario operation description includes the following steps: Step B1: Scenario operation activity description, wherein the specific method of the scenario operation activity description is: based on the initial scenario, scenario roles and scenario high-level concepts conceived in steps A1-A3, the scenario operation activities of the system and external environment roles are analyzed, and the important role activities are analyzed and described in detail according to the needs below; Step B2: Scenario running timing description, wherein the specific method of the scenario running timing description is: based on the initial scenario, scenario roles and scenario high-level concepts conceived in steps A1-A3, referring to the scenario running activity description carried out in step B1, the scenario running timing of the system and external environment roles is analyzed; Step B3: role status description, wherein the specific method of the role status description is: based on the initial scene, scene role and scene high-level concept conceived in steps A1-A3, refer to the scene operation activity description and scene operation timing description carried out in steps B1 and B2, and analyze the operation status of the system of concern.

4. A system requirement analysis method based on system scenario as claimed in claim 3, characterized in that: The establishment of the system capability network includes the following steps: Step C1: Selection of capability framework, wherein the specific method of selecting the capability framework is: according to the system capabilities and object indicators of concern, a system top-level capability classification method is selected as a container that encompasses all capabilities to describe the system capability structure; Step C2: Activity-capability mapping, wherein the specific method of the activity-capability mapping is: according to the scenario operation activity description formed in step B1, the system capabilities that are required and supportive for the execution of a scenario activity corresponding to the execution role swim lane are assumed, and the support relationship between the activities and the capabilities is expressed in the form of a mapping matrix; Step C3: Description of capability relationships, wherein the specific method of the capability relationship description is as follows: according to the system capabilities assumed from the activities in step C2 and the top-level system capabilities selected in step C1, all existing capability granularities are allocated to the roles related to them, and the hierarchical relationships and dependency relationships between capabilities are assumed to be described, thereby forming a multi-view system capability network.

5. A system requirement analysis method based on system scenario as claimed in claim 4, characterized in that: The system function division and demand analysis includes the following steps: Step D1: system function description, wherein the specific method of the system function description is: according to the system capabilities allocated to the system of concern in step C3, the support relationship between the system function components and the system capabilities associated with the system of concern is mapped, and a system function component description is formed; Step D2: System function analysis, wherein the specific method of the system function analysis is: according to the scenario operation activity description determined in step B1 and the role status description determined in step B3, a system function activity diagram is established with functional components as role swim lanes, and the full life cycle function operation process of the system corresponding to the role in the scenario is analyzed; Step D3: Function-requirement mapping, wherein the specific method of the function-requirement mapping is: according to the system function component description formed in step D1 and the system function analysis formed in step D2, based on the existing functional components of the system, the system requirements required to meet a certain function of the system are assumed, and the supporting relationship between the system function components and the assumed system requirements is mapped, thereby completing the system requirement description.

Images