A capability feature based flight management system system requirement capture method

Abstract

The application discloses a kind of based on capability feature's flight management system system requirement capture method, contain (1) the principle and form of determining flight management system capability feature definition, identify capability feature, define capability feature;(2) select a certain capability feature, carry out requirement analysis, the connotation of capability feature is described, the basis of requirement capture of capability feature is analyzed, by respectively to relevant standard, upper layer input, aircraft system constraint, message, some assumptions and configuration are analyzed, the basis of requirement capture of capability feature is combed clearly;(3) based on the result of requirement analysis, carry out system requirement capture from man-machine interaction, interface, behavior, architecture and performance five angles, define requirement according to requirement definition standard.The requirement captured by the method has testability, meets correctness and integrity requirement, and has important practical application significance for complex system design activity.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of system engineering, and relates to a flight management system system requirement capturing method based on capability features. BACKGROUND

[0002] The flight management system is the top-level application of the cockpit to perform flight tasks, and has the functions of automation and pilot assistant decision-making. The flight management system supports the operation of the entire flight process from take-off to landing, and also undertakes the tasks of improving the automation of the flight process and improving the operation efficiency.

[0003] The flight management system involves a wide range of systems and has complex functions, and is a typical complex product system. The development cost of the flight management system is high, the scale is large, the research and development period is long, the technical content is high, and the management is complex. The flight management system life cycle process in accordance with ARP4754A can be divided into a planning process, a safety evaluation process, a requirement capturing process, a requirement confirmation process, an architecture design process, a requirement allocation process, a system implementation process, an implementation verification process, a process guarantee process, a configuration management process and an approval liaison process.

[0004] The requirement capturing process refers to a process of capturing system requirements according to aircraft-level requirements. The purpose of requirement capturing is to convert the capability perspective expected by the stakeholders and users into the technical perspective of the flight management system solution that meets the operational needs of the users. The flight management system requirements are the basis of system definition and the basis of architecture, integration and verification. The flight management system requirements clearly specify the features, attributes, functions and performance that meet the requirements of the stakeholders.

[0005] As the design input of the flight management system, whether the flight management system requirements are correct and complete directly affects the effectiveness of the design and research and development activities and the quality of the research and development products. At present, only a few companies in Europe and the United States have the ability to develop flight management systems that meet airworthiness requirements. In the wide-body and trunk line field, there are mainly Honeywell, GE and Thales, and in the branch line field, there are Honeywell, Collins and the like, and in the helicopter field, there are Thales, Honeywell, Collins, GARMIN and CMC.

[0006] Domestic research institutes and avionics companies have been catching up with the pace of technological development and have carried out a series of researches on system requirement capturing methods. For example, some research institutes have carried out researches on model-based system requirement capturing methods and introduced them into requirement capturing. However, the flight management system has its special complexity, and the model-based system requirement capturing method is not completely applicable, and a method based on capability features needs to be introduced to guide the capturing of the flight management system system requirements. SUMMARY

[0007] The application aims to provide a flight management system requirement capturing method based on capability features. In view of the direct appeal of airspace operation, pilots, airlines, main manufacturers and other stakeholders to the flight management system, the flight management system requirement capturing activities are effectively organized through the capability features, the thinking mode of the flight management system requirement capturing is led, and the system personnel are guided to analyze and capture the requirements from the aspects of human-machine interaction, interface, behavior, architecture and performance through the system requirement analysis and requirement capturing activities. The method comprehensively improves the system thinking when implemented, regards the flight management system as a black box, ignores the internal implementation of the system, focuses on the interaction between the system and the user and external systems, and therefore the captured requirements have testability, meet the correctness and completeness requirements.

[0008] The application aims to provide a flight management system requirement capturing method based on capability features. In view of the direct appeal of airspace operation, pilots, airlines, main manufacturers and other stakeholders to the flight management system, the flight management system requirement capturing activities are effectively organized through the capability features, the thinking mode of the flight management system requirement capturing is led, and the system personnel are guided to analyze and capture the requirements from the aspects of human-machine interaction, interface, behavior, architecture and performance through the system requirement analysis and requirement capturing activities. The method comprehensively improves the system thinking when implemented, regards the flight management system as a black box, ignores the internal implementation of the system, focuses on the interaction between the system and the user and external systems, and therefore the captured requirements have testability, meet the correctness and completeness requirements.

[0009] A flight management system requirement capturing method based on capability features, specifically comprising the following steps:

[0010] (1) determining the principles and forms of flight management system capability feature definition, identifying capability features, and defining capability features;

[0011] (2) selecting a certain capability feature, carrying out requirement analysis, describing the connotation of the capability feature, analyzing the requirement capturing basis of the capability feature, and analyzing the related standards, upper input, aircraft system constraints, messages, some assumptions and configurations to clarify the requirement capturing basis of the capability feature;

[0012] (3) based on the results of the requirement analysis, carrying out system requirement capturing from the aspects of human-machine interaction, interface, behavior, architecture and performance, and defining the requirements according to the requirement definition standards.

[0013] Preferably, the specific method of step (1) comprises:

[0014] (a) defining the principles of flight management system capability feature definition, including: considering product line and business, considering operation, considering function, and considering safety.

[0015] (b) defining the form of flight management system capability feature definition in the form of a table, the attribute column including technical attributes and management attributes, the technical attributes including the number of capability features, the name of capability features, the description of capability features, the traceability of standards, the functional hazard description, etc., and the management attributes including the complexity of the capability feature, the workload, the technology maturity, and whether it is optional.

[0016] (c) defining the capability features suitable for the project according to the principles defined in (a) and the form defined in (b).

[0017] Preferably, the specific method of step (2) comprises:

[0018] (a) describing the capability feature, detailing the content of the capability feature through the description of the operational level and the functional level, and framing the scope and boundaries of the capability feature.

[0019] (b) analyzing the standards, including the airworthiness certification basis and the design basis;

[0020] (c) analyzing the upper-layer input, including the product specification and the human-machine interaction requirement;

[0021] (d) analyzing the aircraft system constraints, including the interface and the architecture;

[0022] (f) analyzing the advisories and cautions triggered by relevant conditions;

[0023] (g) making some assumptions, including those that need to be further confirmed by the customer;

[0024] (h) considering the product platform, and analyzing the configuration of the airline and the aircraft manufacturer.

[0025] Preferably, the specific method of step (3) comprises:

[0026] (a) considering the human-machine interaction performance between the pilot and the cockpit component, capturing the human-machine interaction requirement of the flight management system page, the flight management system message, the primary flight display (PFD), the navigation display (ND), the vertical status display (VSD), and other flight management system-related human-machine interaction requirements;

[0027] (b) considering the data interaction between the flight management system and the relevant airborne external system, and capturing the flight management system interface requirement;

[0028] (c) considering the incentive / event response and system fault tolerance, and capturing the flight management system behavior requirement;

[0029] (d) considering the actual physical architecture of the flight management system product / system, and capturing the flight management system architecture requirement;

[0030] (e) considering the accuracy, real-time performance, integrity, and data throughput, and capturing the flight management system performance requirement.

[0031] The present application has the following beneficial effects:

[0032] The application provides a flight management system requirement capturing method based on capability features, which fully utilizes direct appeals of airspace operation, pilots, airlines, main manufacturers and other stakeholders to the flight management system, and captures flight management system requirements based on capability features. The method effectively organizes flight management system requirement capturing activities, leads the thinking mode of flight management system requirement capturing, and improves system thinking in implementation. The flight management system is regarded as a black box, the internal implementation mode is ignored, and the interaction between the system and the user and external systems is focused, so that the captured requirements have testability, meet the correctness and completeness requirements. The method is an engineering implementation method, which can be popularized to other systems, and has important practical application significance for complex system design activities. BRIEF DESCRIPTION OF DRAWINGS

[0033] Figure 1 A step schematic diagram of a flight management system requirement capturing method based on capability features. DETAILED DESCRIPTION

[0034] The application will be further described in detail below in combination with the drawings and examples.

[0035] The application provides a flight management system requirement capturing method based on capability features, which fully utilizes direct appeals of airspace operation, pilots, airlines, main manufacturers and other stakeholders to the flight management system, and captures flight management system requirements based on capability features. The method effectively organizes flight management system requirement capturing activities, leads the thinking mode of flight management system requirement capturing, and improves system thinking in implementation. The flight management system is regarded as a black box, the internal implementation mode is ignored, and the interaction between the system and the user and external systems is focused, so that the captured requirements have testability, meet the correctness and completeness requirements. The method is an engineering implementation method, which can be popularized to other systems, and has important practical application significance for complex system design activities.

[0036] (1) determining the principles and forms of flight management system capability feature definition, identifying capability features, and defining capability features. The specific method of step (1) includes:

[0037] (a) defining the principles of flight management system capability feature definition, including: considering product line and business, considering operation, considering function, and considering safety.

[0038] (b) defining the form of flight management system capability feature definition in the form of a table. The attribute column includes technical attributes and management attributes. The technical attributes include the number of capability features, the name of capability features, the description of capability features, the traceability of standards, the function hazard description and the like. The management attributes include complexity, workload, technology maturity, and whether it is optional.

[0039] (c) defining the capability features suitable for the project according to the principles defined in (a) and the forms defined in (b).

[0040] (2) Select a certain capability feature, carry out requirement analysis, describe the connotation of the capability feature, analyze the basis of capturing the requirement of the capability feature, and clarify the basis of capturing the requirement of the capability feature by respectively analyzing the related standards, upper-layer input, aircraft system constraints, messages, some assumptions and configurations. The specific method of step (2) includes:

[0041] (a) Describe the capability feature, and describe the connotation of the capability feature in detail through the description of the operational level and the functional level, and frame the range and boundary of the capability feature.

[0042] (b) Analyze the standards, including the airworthiness certification basis and the design basis;

[0043] (c) Analyze the upper-layer input, including product specifications, human-machine interaction requirements, etc.;

[0044] (d) Analyze the aircraft system constraints, including interfaces, architecture, etc.;

[0045] (f) Analyze the advisories, cautions, etc. triggered by related conditions;

[0046] (g) Make some assumptions, including those that need to be further confirmed by the customer;

[0047] (h) Consider the product platform, and analyze the configurations of airlines, aircraft manufacturers, etc.

[0048] (3) Based on the results of the requirement analysis, carry out system requirement capture from five angles of human-machine interaction, interface, behavior, architecture and performance, and define the requirements according to the requirement definition standards.

[0049] (a) Consider the human-machine interaction performance between the pilot and the cockpit components, capture the flight management system page, flight management system message, and human-machine interaction requirements related to the flight management system such as primary flight display (PFD), navigation display (ND) and vertical state display (VSD);

[0050] (b) Consider the data interaction between the flight management system and the related airborne external system, and capture the flight management system interface requirements;

[0051] (c) Consider the incentive / event response and system fault tolerance, and capture the flight management system behavior requirements;

[0052] (d) Consider the actual physical architecture of the flight management system product / system, and capture the flight management system architecture requirements;

[0053] (e) Consider the requirements of accuracy, real-time, integrity and data throughput, and capture the performance requirements of the flight management system.

[0054] It can be understood that, for those ordinary skilled in the art, equivalent replacements or changes can be made according to the technical solutions and the inventive concept of the present application, and all the changes or replacements shall fall within the protection scope of the appended claims of the present application.

Claims

1. A method for capability feature based flight management system system requirement capture, characterized in that The method comprises the following steps: (1) determining principles and forms of flight management system capability feature definition, identifying capability features, and defining capability features, comprising: (1a) defining principles of flight management system capability feature definition, comprising: considering product line and business, considering operation, considering function, and considering safety; (1b) defining forms of flight management system capability feature definition, defining in the form of a table, the attribute column comprising technical attribute and management attribute, the technical attribute comprising the number of capability features, the name of capability features, the description of capability features, the traceability of standards, and the functional hazard description, the management attribute comprising the complexity of the capability features, the workload, the technology maturity, and whether it is optional; (1c) defining the capability features suitable for the project according to the principles defined in (1a) and the forms defined in (1b); (2) selecting a certain capability feature, carrying out requirement analysis, describing the connotation of the capability feature, and analyzing the basis of capability feature requirement capture, through analyzing the related standards, upper input, aircraft system constraints, messages, some assumptions and configurations respectively, the basis of capability feature requirement capture is clarified; (3) based on the results of requirement analysis, carrying out system requirement capture from five angles of human-machine interaction, interface, behavior, architecture and performance, defining requirements according to the requirement definition standard, comprising: (3a) considering the human-machine interaction performance between the pilot and the cockpit components, capturing the human-machine interaction requirements related to the flight management system, including flight management system pages, flight management system messages, primary flight display PFD, navigation display ND, and vertical state display VSD; (3b) considering the data interaction between the flight management system and the related airborne external systems, capturing the flight management system interface requirements; (3c) considering incentive / event response and system fault tolerance, capturing the flight management system behavior requirements; (3d) considering the actual physical architecture of the flight management system, capturing the flight management system architecture requirements; (3e) considering accuracy, real-time, integrity and data throughput, capturing the performance requirements of the flight management system.

2. A capability features based flight management system system requirements capturing method as claimed in claim 1, wherein: The specific method of requirement analysis in step (2) comprises: (2a) describing the capability features, describing the connotation of the capability features in detail through the operation level and the function level, and framing the range and boundary of the capability features; (2b) analyzing the standards, comprising airworthiness audit basis and design basis; (2c) analyzing the upper input, comprising product specification and human-machine interaction requirement; (2d) analyzing the aircraft system constraints, comprising interface and architecture; (2f) analyzing the Advisory and Caution triggered by related conditions; (2g) making some assumptions, including those that need to be further confirmed by the customer; (2h) considering the product platform, analyzing the configurations of the airlines and aircraft manufacturers.

Images