SYSML-based airborne CNS sensor function demand analysis method and system
The SysML model-driven requirements analysis method solves the problems of opaque requirements analysis and difficulty in covering interactive relationships in traditional methods, realizes the systematic capture and verification of CNS system sensor function requirements, and ensures the reliability and effectiveness of the system in different operating modes.
Patent Information
- Application Number
- CN202510847596.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-24
- Publication Date
- 2025-10-17
AI Technical Summary
Traditional airborne CNS system sensor demand analysis methods are unable to fully cover the complex interactions between systems, cannot effectively respond to changes in system demand under different operating modes, and lack intuitive visualization tool support and centralized management of demand information.
A SysML-based approach is used to systematically capture and verify the functional requirements of CNS system sensors by building a system model and combining normal operation scenario and abnormal scenario analysis. SysML use case diagrams and block definition diagrams are used to classify and define them in detail, establish a relationship table between sensors and aircraft mission phases, and plan the priority and retention strategy of functional sensors.
A comprehensive analysis and design of the CNS system sensor functional requirements have been achieved, ensuring the reliability and effectiveness of the system under various flight conditions, and providing scientific development guidance and transparency and traceability of demand management.
Smart Images

Figure CN120805299A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the field of avionics system engineering, and more particularly, to a CNS sensor function requirement analysis method and system based on SYSML. BACKGROUND
[0002] System engineering is widely used in equipment development, and the development of airborne CNS (communication, navigation and surveillance) system is a typical complex system engineering due to its high degree of integration, cross-disciplinary, high cost, long cycle and other characteristics. Whether a set of equipment is successful or not depends on whether the needs and requirements of stakeholders are met throughout the life cycle. Stakeholders are any entity, individual or organization that has a legitimate interest in the system. In the development process of airborne sensor functions, stakeholders to be considered include but are not limited to: users: airlines, flight crew, passengers, etc.; operators: airlines, airport management agencies, etc.; decision-making agencies: government departments, civil aviation authorities, etc.; standard-setting agencies: ICAO, IATA, etc.; research and development agencies: aircraft manufacturers, system suppliers, etc.; support units; the public, etc.
[0003] The traditional requirement analysis method mainly relies on a large number of documents for stage achievement description and review, and the document-driven development mode has the following limitations: 1) the requirement analysis process is not transparent; 2) the requirement information is scattered in different documents, which is difficult to manage and track uniformly; 3) there is a lack of intuitive visualization tool support; 4) it is difficult to quickly respond and adjust when the requirements change.
[0004] In the traditional aircraft development process, the requirement analysis of CNS system function sensors usually relies on a device-centered requirement capture method, which proposes functional performance requirements by analogy with similar products. However, CNS system is a complex collaborative system involving internal systems of the aircraft (such as radar, photoelectric, weapons, etc.), flight crew, other aircraft in the air and ground command center, etc. The complex interaction between systems cannot be fully covered by this traditional method, and the changes in system requirements under different operating modes cannot be effectively addressed. SUMMARY
[0005] The purpose of the present application is to overcome the shortcomings of the prior art and provide a CNS sensor function requirement analysis method and system based on SYSML, which realizes the functional requirement analysis of complex avionics system by constructing a system model, and provides structured guidance for system design and development.
[0006] The purpose of the present application is achieved by the following scheme: A CNS sensor function requirement analysis method based on SYSML, comprising the following steps: The SysML model is constructed, normal operation scene and abnormal scene analysis are combined, and the functional requirements of the CNS system sensor are systematically captured and verified; wherein, by building a use case and an activity scene model, the needs and requirements of stakeholders are analyzed, and then the system requirements are captured; the scene model is abstractly described for the physical relationship of equipment at different levels, so as to realize the capture of equipment requirements and the transmission of system design.
[0007] Further, the SysML model is constructed, normal operation scene and abnormal scene analysis are combined, and the functional requirements of the CNS system sensor are systematically captured and verified; wherein, by building a use case and an activity scene model, the needs and requirements of stakeholders are analyzed, and then the system requirements are captured; the scene model is abstractly described for the physical relationship of equipment at different levels, so as to realize the capture of equipment requirements and the transmission of system design, and specifically includes the following sub-steps: Normal operation scene analysis: starting from the operation scene of the aircraft, the stakeholders are identified, and the functional requirements of the CNS system sensor are classified by using the use case diagram of SysML; Abnormal scene analysis: the functional requirements are defined in detail by using the block definition diagram BDD of SysML, and the relationship table of the CNS system functional sensor and the aircraft task stage is established by combining the use scene analysis, so as to clearly define the application range of each functional sensor in different task stages.
[0008] Further, the functions of the CNS system sensor include communication functions, navigation functions, monitoring functions and system control management functions.
[0009] Further, in the abnormal scene, the working state of the CNS system includes a normal working mode, a backup working module, an emergency working module and a degraded working mode.
[0010] Further, in the analysis of the abnormal scene, the sub-steps of planning the priority of each functional sensor and dynamically adjusting the function reservation strategy according to the actual resources and liquid cooling state are included.
[0011] Further, the use case diagram of SysML is used to classify the functional requirements of the CNS system sensor, and specifically includes the following sub-steps: User requirements are refined by use cases and use case scenarios, the system use case is defined by using the use case diagram UC of SysML, the system use case contains one or more functions based on the scene and according to the use scene, the stakeholders of the CNS system are identified, and the sensor functions are classified into four categories of communication, navigation, monitoring and control management according to the services provided for external stakeholders; The total item of the function contained in the CNS system identified after the use case analysis is defined by using the block definition diagram BDD of SysML; The function flow of the use case is analyzed from the perspective of external objects, in the process of analyzing the function flow, the interaction between the current interested system and the external objects, based on the analysis of the running scene, the swim lane of each stakeholder is created, and the series of actions of each sensor function of the aircraft onboard system are arranged to express the behavior of each sensor function of the aircraft onboard system.
[0012] Further, when the activity has a subdivided scene, another activity graph is embedded in the specific activity Action of the item, and the branches are described in detail.
[0013] Further, the creation of the swim lane of each stakeholder specifically includes: when the demand analysis of the system stakeholders is performed, a comprehensive application scene is created, and each stakeholder is taken as a swim lane.
[0014] Further, the creation of the swim lane of each stakeholder specifically includes: when the demand analysis of the system stakeholders is performed, the current CNS system corresponds to a swim lane, and the function flow activity is defined on each swim lane, and the function flow activity is placed on which swim lane indicates that the activity is completed by the stakeholder corresponding to the swim lane.
[0015] Further, the function requirement is defined in detail by using the block definition diagram BDD of SysML, and the relationship table of the CNS system function sensor and the aircraft task stage is established by combining the use scene analysis, and the application range of each function sensor in different task stages is clear, and the specific steps include: The interface relationship between the stakeholders in each swim lane in the scene is defined by using the internal block diagram IBD of SysML, so as to sort out the external interface and transmission content of the system; if there is an interaction item between each swim lane, the type of the interaction item is defined by using the signal model element.
[0016] Further, the function requirement is defined in detail by using the block definition diagram BDD of SysML, and the relationship table of the CNS system function sensor and the aircraft task stage is established by combining the use scene analysis, and the application range of each function sensor in different task stages is clear, and the specific steps include: The abnormal scenarios are used to further capture system requirements that cannot be captured in normal operation scenarios; wherein, when the FC bus of the avionics display control fails, the backup bus communicates with the cockpit system, and at this time, data transmission is realized through the RS485 serial bus interconnected with the cockpit system; when the 270V main power supply system of the aircraft fails, the CNS system is powered by the battery and has no liquid cooling, part of the hardware resources are closed, and only basic communication, navigation and monitoring sensor functions are provided; when the internal hardware of the CNS subsystem fails or over-temperature protection, or the liquid cooling fails, it is decided whether the function is retained according to the resource health state, the priority of each communication, navigation and monitoring sensor function is planned, and according to the actual resource and liquid cooling condition, the high-priority function is preferentially ensured to work.
[0017] Further, the CNS system enters different working modes according to different working conditions in normal operation scenarios and abnormal scenarios; meanwhile, according to the user demand, the sensor function items that the system needs to have in different working modes are analyzed, so as to further supplement and perfect the system requirements.
[0018] Further, the signal element model is divided into two types of "analog signal" and "digital signal" according to types, and different symbols are used to represent them.
[0019] A CNS sensor function requirement analysis system based on SYSML, comprising a computer device, the computer device comprising a processor and a memory, the memory storing a computer program, when the computer program is loaded by the processor and executes the method as claimed in any one of the above.
[0020] The beneficial effects of the present application include: The present application scheme can be comprehensively analyzed and designed, covering requirement analysis, architecture design, simulation and abnormal processing, and ensuring the reliability and effectiveness thereof in various flight conditions. BRIEF DESCRIPTION OF DRAWINGS
[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor.
[0022] Figure 1 The scene analysis method for the airborne communication navigation monitoring (CNS) system of the embodiment of the present application; Figure 2 The sensor function use case diagram for the airborne communication navigation monitoring (CNS) system of the embodiment of the present application; Figure 3This is a diagram of sensor function classification of an airborne communication, navigation and surveillance (CNS) system according to an embodiment of the present invention; Figure 4 A flowchart of the software architecture design of an embodiment of the present invention; Figure 5 This is a simulation analysis flow chart of an embodiment of the present invention; Figure 6 Analyze the airborne air traffic control response function from the perspective of external objects in an embodiment of the present invention; Figure 7 Defining functional process activities on a swim lane for an embodiment of the present invention; Figure 8 It is an external interface of the system using IBD diagram definition in the embodiment of the present invention; Figure 9 These are normal and abnormal operating scenarios of an airborne communication, navigation and surveillance (CNS) system according to an embodiment of the present invention. DETAILED DESCRIPTION
[0023] All features disclosed in all embodiments in this specification, or steps in all methods or processes implicitly disclosed, except for mutually exclusive features and / or steps, can be combined and / or expanded or replaced in any manner.
[0024] In light of the issues raised in this background, the inventors of this application believe that, with the development of systems engineering methodologies, SysML-based requirements analysis methods have demonstrated unique advantages. As a modeling language for systems engineering, SysML can explicitly express the mapping relationship between stakeholder requirements and system functional requirements by constructing models such as use case diagrams and activity diagrams. This model-based requirements analysis approach not only improves the visibility and traceability of requirements analysis, but also enables the centralized management of requirements information and seamless integration with system design.
[0025] Requirements analysis is an important part of system engineering, but there are not many studies on equipment requirements analysis based on the SysML language. Therefore, this application intends to propose a solution to this problem. In the specific invention concept, this application analyzes the needs and requirements of stakeholders by building use case and activity scenario models, and then captures system requirements. The scenario model realizes the capture of equipment requirements and the transmission of system design through abstract description of the physical relationships of equipment at different levels. Compared with the traditional requirements analysis method (describing and reviewing phased results through a large amount of documents, and document-driven R&D process), the requirements analysis process and method are more explicit through the construction of use case and activity scenario models, and the requirements are centrally managed in the tool and will not be scattered in various documents. At the same time, this application uses the thinking method of system engineering and regards requirements analysis as a profession to ensure that every requirement is designed and every design has a source of requirements.
[0026] In a further inventive concept, a system modeling language (SysML) based airborne communication navigation surveillance (CNS) system sensor function requirement analysis method is specifically provided. The method systematically captures and verifies the function requirements of the CNS system sensor by constructing a SysML model, combining normal operation scenario analysis and abnormal scenario analysis, and provides scientific basis and effective guidance for the development of complex systems.
[0027] One of the cores of the present application is to introduce SysML model driving and improve the requirement analysis method of the corresponding analysis process, in which the function requirements of the CNS system sensor are systematically analyzed by building models such as use case diagram, activity diagram and block definition diagram (BDD), and the main specific implementation steps involved include normal operation scenario analysis and abnormal operation scenario analysis.
[0028] 1) Normal operation scenario analysis: First, the stakeholders (participants) are identified from the operation scenario of the aircraft, and the function requirements of the CNS system sensor are classified by using the use case diagram of SysML. The functions include the following categories: Communication functions: support intra-aircraft communication (between crew members) and external communication (with other aircraft, ground command center, tower, etc.). According to the transmission distance, it can be divided into line-of-sight communication and out-of-sight communication; according to the transmission content, it can be divided into voice communication and data communication. Navigation functions: provide real-time information such as aircraft attitude, speed and position for the flight crew, support safe flight and task execution. According to the use scenario, it can be divided into en route navigation and terminal area navigation; en route navigation includes TACAN, radio altimeter and GPS functions; terminal area navigation includes instrument landing, microwave landing, radio beacon and precision ranging functions. Surveillance functions: realize real-time perception and control of the surrounding situation information, and assist the detection equipment such as airborne radar to complete target recognition. The specific functions include broadcast automatic dependent surveillance function, ship automatic identification function, air traffic control response function and air traffic early warning and collision avoidance function. System control and management functions: receive avionics task system planning and control instructions, realize parameter setting, mode switching and state monitoring of communication, navigation, surveillance and other functions. Including control management and health management functions. Subsequently, the function requirements are defined in detail by using the block definition diagram (BDD) of SysML, and the relationship table of CNS system function sensor and aircraft task phase is established by combining use scenario analysis, to clarify the application range of each function sensor in different task phases.
[0029] 2) Abnormal scenario analysis: In abnormal scenarios, the system may face problems such as power failure, liquid cooling system failure or communication bus interruption, and further requirements of the system in abnormal state need to be captured. According to the working mode of the system, the CNS subsystem is divided into the following four working states: Normal working mode: The system receives avionics control commands and reports data through the FC bus, and realizes all functions. Backup working mode: When the FC bus fails, the system switches to the backup bus (such as RS485 serial bus) to communicate with the cockpit system. Emergency working mode: When the 270V main power system fails, the CNS system is powered by the battery and has no liquid cooling, the system shuts down part of the hardware resources, only provides basic communication, navigation and monitoring functions to support the emergency landing of the aircraft. Degraded working mode: When the internal hardware of the CNS subsystem fails, over-temperature protection or the liquid cooling system fails, the system needs to shut down part of the resources, and priority is given to the operation of high-priority functions. In the abnormal scene analysis, the priority of each functional sensor is planned, and the function reservation strategy is dynamically adjusted according to the actual resources and the liquid cooling state, so that the system can still maintain the stable operation of the core function under the limited conditions.
[0030] Through the above analysis steps, the application can systematically capture the functional requirements of the CNS system sensors, and verify the integrity and consistency of the requirements through the SysML model, providing scientific basis and technical support for the development of complex systems.
[0031] More specifically, as shown in Figure 1 In the requirement analysis technical solution of the application, first, as many as possible normal operation scenarios and abnormal operation scenarios of the CNS system in each task phase of the aircraft are listed and summarized, including: a) Normal operation scenario: In different stages of flight (such as take-off, cruising, landing), the CNS system is responsible for providing navigation, communication and monitoring functions to ensure the safe flight of the aircraft.
[0032] b) Abnormal operation scenario: When the aircraft encounters a failure or other unexpected situation (such as system failure, weather change), the CNS system needs to have an emergency response mechanism to ensure flight safety.
[0033] As shown in Figure 2 User requirements are refined through use cases and use case scenarios. Compared with user requirements, use cases more accurately describe what people expect from the system and the implementation logic of the function expectations. The use case diagram UC (Function Use Case Diagram) of SysML is used to define system use cases. Use cases are high-level functions of the system, which are based on scenarios, contain one or more functions, and identify the stakeholders of the airborne communication navigation surveillance (CNS) system according to the use scenarios, including the flight crew, other aircraft, various ground stations, ships and satellites. According to the services that the system can provide for external stakeholders, the sensor functions are classified into four categories: communication, navigation, monitoring and control management.
[0034] As shown in Figure 3As shown, the total items of functions of the CNS system identified after the use case analysis are defined by using the block definition diagram (BDD) of SysML. This classification helps the modular management of the system design, improves the efficiency and maintainability.
[0035] Table 1 is a mapping table of the relationship between the sensors of the CNS system and the task stages. Referring to Table 1, according to the normal operation scenarios of the CNS system in each task stage of the aircraft and the total items of functions, the table lists in detail the sensors required to be used in each flight task stage, and summarizes the mapping table of the relationship between the sensors of the CNS system and the task stages. It is ensured that each stage has corresponding sensor support, and the overall efficiency of the system is improved.
[0036] Table 1
[0037] As Figure 4 shown, the function flow of the use case is analyzed from the perspective of external objects in the present inventive concept. During the analysis of the function flow, the interaction activities between the current system of interest and the external objects are analyzed. Based on the above operation scenario analysis, the swim lanes of each stakeholder are created, and a series of actions of the sensors of the aircraft onboard system are arranged to express the behaviors of the sensors of the aircraft onboard system. Taking the ATC response function of the onboard CNS system as an example, the activity diagram (Activity Diagram) based on SysML is used to describe the sequence of actions in the process of executing a certain function by the participants. First, the ground ATC tower alternately inquires in A / C / S mode, and the onboard ATC responder detects the valid inquiry signal, and generates the corresponding response signal within the specified time.
[0038] As Figure 5 shown, when an activity has a subdivisible scenario, another activity diagram (Activity Diagram) can be embedded in the specific activity Action. The branches are described in detail. The ATC S-mode uplink inquiry format can be specifically divided into height request UF=4, identification request UF=5, only S-mode full call UF=11, Comm-A height request UF=20, Comm-A identification request UF=21 inquiry, and the onboard ATC responder needs to select the corresponding downlink DF response mode according to the current inquiry mode.
[0039] As Figure 6As shown, when the demand analysis of the system stakeholders is performed, a comprehensive application scenario is created, each stakeholder is taken as a swimlane, and the tower controller, one of the system stakeholders, is taken as an example. When the tower controller wants to quickly identify a specific aircraft on the radar screen, the pilot is required to press the "special position identification pulse (SPI)" switch in the form of voice. At this time, the airborne ATC transponder automatically adds an identification pulse in the response pulse for 15-30 seconds. The pulse makes the bright spot on the ground station screen wider, thereby helping the controller to quickly identify and distinguish the specific aircraft from the numerous flight targets.
[0040] As shown, Figure 7 As shown, when the demand analysis of the system stakeholders is performed, a comprehensive application scenario is created, each stakeholder is taken as a swimlane, and the tower controller, one of the system stakeholders, is taken as an example. When the tower controller wants to quickly identify a specific aircraft on the radar screen, the pilot is required to press the "special position identification pulse (SPI)" switch in the form of voice. At this time, the airborne ATC transponder automatically adds an identification pulse in the response pulse for 15-30 seconds. The pulse makes the bright spot on the ground station screen wider, thereby helping the controller to quickly identify and distinguish the specific aircraft from the numerous flight targets.
[0041] As shown, Figure 8 As shown, the interface relationship between the stakeholders in each swimlane in the above scenario is defined by using the internal block diagram IBD (Internal Block Diagram) of SysML, thereby the external interface and transmission content of the system are sorted out. According to the process and method proposed in the application, each external communication object can be efficiently identified and defined, and corresponds to a swimlane. The current system (CNS system) also corresponds to a swimlane. In the future, we will define the function flow activities on each swimlane. The function flow activities placed on which swimlane indicate that the activity is completed by the system (or external object) corresponding to the swimlane. If there is an interaction item between the swimlanes, the type of the interaction item is defined by using the signal (Signal) model element. The signal meta-model can be divided into two types of "analog signal" and "digital signal" according to the type, and different symbols are used to represent them.
[0042] As Figure 9 shown, the abnormal scenario is further captured to capture system requirements that cannot be captured in normal operation scenarios. When the FC bus of the avionics display control fails, a backup bus is needed to communicate with the cockpit system, and data transmission is realized through the RS485 serial bus interconnected with the cockpit system. When the 270V main power supply system of the aircraft fails, the CNS system is powered by the battery and has no liquid cooling, and part of the hardware resources need to be closed to provide only basic communication, navigation and monitoring sensor functions. When the internal hardware of the CNS subsystem fails or over-temperature protection, or the liquid cooling fails, it is necessary to decide whether to retain the function according to the resource health status, and to plan the priority of each communication, navigation and monitoring sensor function, and to ensure the high-priority function to work according to the actual resource and liquid cooling condition.
[0043] Table 2 is a mapping table of each function sensor of the airborne communication navigation monitoring (CNS) system and each working mode. Referring to Table 2, the CNS system will enter different working modes according to different working conditions in normal and abnormal scenarios. At the same time, according to the user demand analysis, the system needs to have sensor function items in different working modes, thereby further supplementing and perfecting the system requirements.
[0044] Table 2
[0045] Through the above steps, the CNS system can be comprehensively analyzed and designed, covering requirement analysis, architecture design, simulation and abnormal handling, to ensure its reliability and effectiveness in various flight conditions.
[0046] It should be noted that the following embodiments can be combined and / or extended, replaced, in any way that is consistent with the logic, within the scope of protection defined in the claims of the present application, such as the disclosed technical principles, disclosed technical features or implied disclosed technical features.
[0047] Embodiment 1 A CNS sensor function requirement analysis method based on SYSML, comprising the following steps: A SysML model is constructed, and the function requirements of the CNS system sensors are captured and verified systematically by combining normal operation scenarios and abnormal scenario analysis; wherein, by building a use case and activity scenario model, the needs and requirements of stakeholders are analyzed, and then the system requirements are captured; the scenario model is abstractly described by the physical relationship of different levels of equipment to realize the capture of equipment requirements and the transmission of system design.
[0048] Embodiment 2 On the basis of embodiment 1, the SysML model is constructed, and the function requirements of the CNS system sensor are systematically captured and verified in combination with normal operation scene analysis and abnormal scene analysis; wherein, by constructing a use case and an activity scene model, the needs and requirements of stakeholders are analyzed, and then the system requirements are captured; the scene model is abstractly described by means of different levels of physical relations of equipment, so as to realize the capture of equipment requirements and the transmission of system design, and specifically includes the following sub-steps: Normal operation scene analysis: starting from the operation scene of the aircraft, the stakeholders are identified, and the function requirements of the CNS system sensor are classified by means of the use case diagram of SysML; Abnormal scene analysis: the function requirements are defined in detail by means of the block definition diagram BDD of SysML, and in combination with the use scene analysis, a relationship table of the CNS system function sensor and the aircraft task stage is established, and the application range of each function sensor in different task stages is clarified.
[0049] Embodiment 3 On the basis of embodiment 2, the functions of the CNS system sensor include communication functions, navigation functions, monitoring functions and system control management functions.
[0050] Embodiment 4 On the basis of embodiment 2, under the abnormal scene, the working states of the CNS system include a normal working mode, a backup working module, an emergency working module and a degraded working mode.
[0051] Embodiment 5 On the basis of embodiment 2, in the analysis of the abnormal scene, the sub-steps of planning the priority of each function sensor and dynamically adjusting the function reservation strategy according to the actual resources and the liquid cooling state are included.
[0052] Embodiment 6 On the basis of embodiment 2, the function requirements of the CNS system sensor are classified by means of the use case diagram of SysML, and specifically include the following sub-steps: The user requirements are refined by means of a use case and a use case scene, the system use case is defined by means of the use case diagram UC of SysML, the system use case contains one or more functions based on a scene, and according to the use scene, the stakeholders of the CNS system are identified, and the sensor functions are classified into four categories of communication, navigation, monitoring and control management according to the services provided for external stakeholders; The total item of the functions contained in the CNS system identified after the use case analysis is defined by means of the block definition diagram BDD of SysML; The function flow of the use case is analyzed from the perspective of the external object, in the process of analyzing the function flow, the interaction between the current interested system and the external object, based on the analysis of the running scene, the swim lane of each stakeholder is created, and the series of actions of the functions of each sensor of the aircraft onboard system are arranged to express the behaviors of the functions of each sensor of the aircraft onboard system.
[0053] Embodiment 7 On the basis of embodiment 6, when the activity has a subdivided scene, another activity graph is embedded in the item specific activity Action of the activity, and the branches thereof are described in detail.
[0054] Embodiment 8 On the basis of embodiment 6, the creation of the swim lane of each stakeholder specifically includes: when the demand analysis of the system stakeholders is performed, a comprehensive application scene is created, and each stakeholder is taken as a swim lane.
[0055] Embodiment 9 On the basis of embodiment 6, the creation of the swim lane of each stakeholder specifically includes: when the demand analysis of the system stakeholders is performed, the current CNS system corresponds to a swim lane, the function flow activity is defined on each swim lane, and the function flow activity is placed on which swim lane indicates that the activity is completed by the stakeholder corresponding to the swim lane.
[0056] Embodiment 10 On the basis of embodiment 6, the function demand is defined in detail by using the block definition diagram BDD of SysML, and the relationship table of the function sensor of the CNS system and the aircraft task stage is established by combining the use scene analysis, the application range of each function sensor in different task stages is clarified, and the specific steps include: The interface relationship between the stakeholders in each swim lane in the scene is defined by using the internal block diagram IBD of SysML, so as to sort out the external interface and transmission content of the system; if there is an interaction item between each swim lane, the type of the interaction item is defined by using the signal model element.
[0057] Embodiment 11 On the basis of embodiment 2, the function demand is defined in detail by using the block definition diagram BDD of SysML, and the relationship table of the function sensor of the CNS system and the aircraft task stage is established by combining the use scene analysis, the application range of each function sensor in different task stages is clarified, and the specific steps include: The abnormal scene is further used to capture system requirements that cannot be captured in the normal operation scene; wherein, when the FC bus of the avionics display control fails, the backup bus communicates with the cockpit system, and at this time, data transmission is realized through the RS485 serial bus interconnected with the cockpit system; when the 270V main power supply system of the aircraft fails, the CNS system is powered by the battery and has no liquid cooling, part of the hardware resources are closed, and only basic communication, navigation and monitoring sensor functions are provided; when the internal hardware of the CNS sub-system fails or over-temperature protection, or the liquid cooling fails, it is decided whether the function is retained according to the resource health state, the priority of each communication, navigation and monitoring sensor function is planned, and according to the actual resource and liquid cooling condition, the high-priority function is preferentially ensured to work.
[0058] Embodiment 12 On the basis of embodiment 2, the CNS system enters different working modes according to different working conditions in the normal operation scene and the abnormal scene; meanwhile, according to the user demand, it is analyzed that the system needs to have sensor function items in different working modes, so as to further supplement and perfect the system requirements.
[0059] Embodiment 13 On the basis of embodiment 10, the signal element model is divided into two types of 'analog signal' and 'digital signal' according to the type, and different symbols are used to represent.
[0060] Embodiment 14 A CNS sensor function requirement analysis system based on SYSML, comprising a computer device, the computer device comprising a processor and a memory, the memory storing a computer program, when the computer program is loaded by the processor and executes the method as described in any one of embodiments 1-12.
[0061] The units described in the embodiments of the present application can be implemented in the form of software, or can be implemented in the form of hardware, and the described units can also be arranged in a processor. In some cases, the names of these units do not constitute a limitation on the units themselves.
[0062] According to an aspect of an embodiment of the present application, a computer program product or computer program is provided, which includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method provided in the various optional implementation manners.
[0063] As another aspect, the embodiments of the present application also provide a computer readable medium, which can be included in the electronic device described in the above embodiments, or exist independently without being assembled into the electronic device. The computer readable medium carries one or more programs, which, when executed by the electronic device, enable the electronic device to implement the method described in the above embodiments.
Claims
1. A SYSML-based airborne CNS sensor functional requirements analysis method, characterized by: The following steps are involved: Construct a SysML model, combine normal operation scenario and abnormal scenario analysis, and systematically capture and verify the functional requirements of CNS system sensors. Specifically, by building use case and activity scenario models, analyze the needs and requirements of stakeholders and then capture system requirements. The scenario model realizes the capture of equipment requirements and the transmission of system design through the abstract description of the physical relationships at different levels of equipment.
2. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 1, characterized in that: The SysML model is constructed, combining normal operation scenario and abnormal scenario analysis to systematically capture and verify the functional requirements of CNS system sensors. Specifically, by building use case and activity scenario models, the needs and requirements of stakeholders are analyzed to capture system requirements. The scenario model abstractly describes the physical relationships at different levels of equipment to achieve the capture of equipment requirements and the delivery of system design. Specifically, it includes the following sub-steps: Normal operation scenario analysis: Starting from the aircraft's operational scenarios, identify stakeholders and classify the functional requirements of CNS system sensors using SysML use case diagrams; Abnormal scenario analysis: Use SysML's block definition diagram (BDD) to define functional requirements in detail. Combined with usage scenario analysis, establish a relationship table between the CNS system's functional sensors and aircraft mission phases, and clarify the application scope of each functional sensor in different mission phases.
3. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 2, characterized in that: The functions of the CNS system sensors include communication functions, navigation functions, monitoring functions and system control and management functions.
4. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 2, characterized in that: In abnormal scenarios, the working states of the CNS system include normal working mode, backup working module, emergency working module and degraded working mode.
5. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 2, characterized in that: The analysis of abnormal scenarios includes the following sub-steps: planning the priority of each functional sensor and dynamically adjusting the function retention strategy based on actual resources and liquid cooling status.
6. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 2, characterized in that: The use of SysML use case diagrams to classify the functional requirements of CNS system sensors specifically includes the following sub-steps: User requirements are refined through use cases and use case scenarios. System use cases are defined using SysML's use case diagram UC. System use cases contain at least one or more functions based on scenarios. Based on the usage scenarios, the stakeholders of the CNS system are identified. Sensor functions are classified into four categories: communication, navigation, monitoring, and control management according to the services provided to external stakeholders. Use SysML's Block Definition Diagram (BDD) to define the total functionality of the CNS system identified after use case analysis; The functional flow of the use case is analyzed from the perspective of external objects. In the process of analyzing the functional flow, the interaction activities between the current system of interest and the external objects are analyzed. Based on the analysis of the operation scenario, the swim lanes of each stakeholder are created, and a series of actions of the sensor functions of the aircraft onboard system are choreographed to express the behavior of the sensor functions of the aircraft onboard system.
7. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 6, characterized in that: When an activity has further subdivided scenarios, another activity diagram is embedded in its specific activity Action to describe its branches in detail.
8. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 6, characterized in that: The creating of swim lanes for various stakeholders specifically includes: when conducting a demand analysis on system stakeholders, creating a comprehensive application scenario with various stakeholders as swim lanes.
9. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 6, characterized in that: The creation of lanes for each stakeholder specifically includes: when conducting demand analysis on system stakeholders, the current CNS system corresponds to a lane, and functional process activities are defined on each lane. The lane in which the functional process activity is placed indicates that the activity is completed by the stakeholder corresponding to the lane.
10. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 6, characterized in that: The functional requirements are defined in detail using SysML's block definition diagram (BDD). Combined with scenario analysis, a relationship table between the CNS system's functional sensors and aircraft mission phases is established to clarify the application scope of each functional sensor in different mission phases. The specific steps include the following: Use SysML's internal block diagram (IBD) to define the interface relationships between stakeholders in each lane in the scenario, thereby sorting out the system's external interface and transmission content; if there are interactions between lanes, use signal model elements to define the types of the interactions.
11. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 2, characterized in that: The functional requirements are defined in detail using SysML's block definition diagram (BDD). Combined with scenario analysis, a relationship table between the CNS system's functional sensors and aircraft mission phases is established to clarify the application scope of each functional sensor in different mission phases. The specific steps include the following: Abnormal scenarios are used to further capture system requirements that cannot be captured in normal operating scenarios. Among them, when the FC bus with the avionics display and control fails, the backup bus communicates with the cockpit system. At this time, data transmission is realized through the RS485 serial bus interconnected with the cockpit system. When the aircraft's 270V main power system fails and the CNS system is powered by a battery without liquid cooling, some hardware resources are shut down and only basic communication, navigation and surveillance sensor functions are provided. When the internal hardware of the CNS subsystem fails or over-temperature protection occurs, or the liquid cooling fails, whether the function will be retained is determined based on the health status of the resources, and the priority of each communication, navigation and surveillance sensor function is planned. According to the actual resources and liquid cooling conditions, high-priority functions are given priority.
12. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 2, characterized in that: The CNS system enters different working modes according to different working conditions in normal operation scenarios and abnormal scenarios. At the same time, based on user needs, it analyzes the sensor functions that the system needs to have in different working modes, thereby further supplementing and improving system requirements.
13. The SYSML-based airborne CNS sensor function requirement analysis method according to claim 10, characterized in that: The signal element model is divided into two categories according to type: "analog signal" and "digital signal", and is represented by different symbols.
14. A SYSML-based airborne CNS sensor function requirement analysis system, characterized by: The method comprises a computer device comprising a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is loaded by the processor, the method according to any one of claims 1 to 12 is executed.