Flight management system demand capturing method based on capability characteristics

Abstract

The invention discloses a method for capturing system requirements of a flight management system based on capability characteristics, which comprises the following steps of: (1) determining principles and forms of capability characteristic definition of the flight management system, identifying the capability characteristics, and defining the capability characteristics; (2) selecting a certain capability feature, carrying out demand analysis, carrying out description on the connotation of the capability feature, carrying out analysis on capability feature demand capture basis, and sorting out the capability feature demand capture basis by respectively analyzing related standards, upper-layer input, aircraft system constraints, messages, some hypotheses and configurations; and (3) based on a demand analysis result, carrying out system demand capture from five aspects of human-computer interaction, interface, behavior, architecture and performance, and defining a demand according to a demand definition standard. The requirements captured through the method have testability, the requirements for correctness and integrity are met, and the method has important practical application significance for complex system design activities.

Description

Technical Field

[0001] The invention belongs to the technical field of system engineering and relates to a method for capturing system requirements of a flight management system based on capability characteristics. Background Art

[0002] The flight management system is the top-level application in the cockpit for executing flight missions, taking into account both automation and driver-assisted decision-making functions. It supports the operation of the entire flight process from takeoff to landing, and also undertakes the task of improving the automation of the flight process and improving operational efficiency.

[0003] The flight management system involves a wide range of aspects, has many interconnected systems, and has complex functions. It is a typical complex product system with high development costs, large scale, long R&D cycle, high technical content, and complex management. The flight management system life cycle process that complies with ARP4754A can be divided into: planning process, safety assessment process, requirement capture process, requirement confirmation process, architecture design process, requirement allocation process, system implementation process, implementation verification process, process assurance process, configuration management process, and certification liaison process.

[0004] The requirements capture process refers to the process of capturing system requirements based on aircraft-level requirements. The purpose of requirements capture is to convert the capability perspective expected by stakeholders and users into a technical perspective of a flight management system solution that meets the operational needs of users. Flight management system requirements are the basis for system definition and the basis for architecture, integration, and verification. Flight management system requirements clearly define the features, attributes, functions, and performance that meet the requirements of 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 development activities and the quality of the research and development products. Currently, 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 fields, there are mainly three companies: Honeywell, GE, and Thales. In the regional line field, there are Honeywell, Collins, etc. 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 conducted a series of studies on system requirements capture methods. For example, some research institutes have conducted research on model-based system requirements capture methods and introduced them into requirements capture. However, the flight management system has its own special complexity, and the model-based system requirements capture method is not completely applicable. It is necessary to introduce the method of capability characteristics to drive the capture of flight management system system requirements. Summary of the invention

[0007] The purpose of the invention is to provide a method for capturing flight management system requirements based on capability characteristics. In view of the direct demands of stakeholders such as airspace operations, pilots, airlines, and main manufacturers on the flight management system, the capability characteristics are used to effectively organize the flight management system system requirement capture activities, guide the thinking mode of flight management system system requirement capture, and guide system personnel to analyze and capture requirements from the aspects of human-computer interaction, interface, behavior, architecture, and performance through system requirement analysis and requirement capture activities. This method comprehensively improves system thinking during implementation, regards the flight management system as a black box, ignores the internal implementation method of the system, and focuses on the interaction between the system and users and external systems. Therefore, the captured requirements are testable and meet the requirements of correctness and completeness.

[0008] The object of the present invention is achieved through the following technical solutions:

[0009] A method for capturing system requirements of a flight management system based on capability characteristics specifically comprises the following steps:

[0010] (1) Determine the principles and forms for defining the capability characteristics of the flight management system, identify the capability characteristics, and define the capability characteristics;

[0011] (2) Select a capability feature, conduct a demand analysis, describe the connotation of the capability feature, and analyze the basis for capturing the capability feature requirements. By analyzing the relevant standards, upper-level inputs, aircraft system constraints, messages, some assumptions, and configurations, the basis for capturing the capability feature requirements can be clarified.

[0012] (3) Based on the results of the requirements analysis, system requirements are captured from five perspectives: human-computer interaction, interface, behavior, architecture, and performance, and requirements are defined according to the requirements definition standards.

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

[0014] (a) Clarify the principles for defining the capability characteristics of the flight management system, including consideration of product lines and business, consideration of operations, consideration of functions, and consideration of safety.

[0015] (b) The form of defining the capability characteristics of the flight management system shall be clarified and defined in a table. The attribute columns shall include technical attributes and management attributes. The technical attributes shall include the capability characteristic number, capability characteristic name, capability characteristic description, standard traceability, functional hazard description, etc. The management attributes shall include the complexity, workload, technical maturity, and whether it is optional, etc. of the capability characteristic.

[0016] (c) Define the competency characteristics applicable to this project, based on the principles defined in (a) and the forms defined in (b).

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

[0018] (a) Describe the capability characteristics. Through descriptions at the operational and functional levels, describe in detail the connotation of the capability characteristics and define the scope and boundaries of the capability characteristics.

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

[0020] (c) Analyze upper-level inputs, including product specifications, human-computer interaction requirements, etc.;

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

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

[0023] (g) make some assumptions, including those that require further confirmation from the client;

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

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

[0026] (a) Consider the human-computer interaction between the pilot and the cockpit components, capture the human-computer interaction requirements related to the flight management system, such as flight management system pages, flight management system messages, primary flight display PFD, navigation display ND, vertical status display VSD, etc.;

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

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

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

[0030] (e) Capture the flight management system performance requirements by taking into account requirements such as accuracy, real-time performance, integrity, and data throughput.

[0031] The beneficial effects of the present invention are:

[0032] The present invention proposes a method for capturing flight management system requirements based on capability characteristics, making full use of the direct demands of stakeholders such as airspace operations, pilots, airlines, and main manufacturers on the flight management system, and capturing the flight management system system requirements based on capability characteristics. This method effectively organizes flight management system system requirement capture activities, drives the thinking mode of flight management system system requirement capture, and comprehensively improves system thinking during implementation through system requirement analysis and requirement capture activities, treating the flight management system as a black box, ignoring the internal implementation method of the system, and focusing on the interaction between the system and users and external systems. Therefore, the captured requirements are testable and meet the requirements of correctness and completeness. This method is a method that is easy to implement in engineering and can be extended to other systems. It has important practical application significance for complex system design activities. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 A schematic diagram of the steps of a method for capturing system requirements for a flight management system based on capability characteristics. DETAILED DESCRIPTION

[0034] The present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0035] Aiming at the direct demands of stakeholders such as airspace operations, pilots, airlines, and main manufacturers for flight management systems, this paper proposes a method for capturing flight management system requirements based on capability characteristics. Starting from the perspective of capability characteristics, this method effectively organizes flight management system system requirement capture activities, guides the thinking mode of flight management system system requirement capture, and analyzes and captures requirements from the aspects of human-computer interaction, interface, behavior, architecture, and performance. Specifically, it includes the following steps:

[0036] (1) Determine the principles and forms of defining the capability characteristics of the flight management system, identify the capability characteristics, and define the capability characteristics. The specific methods of step (1) include:

[0037] (a) Clarify the principles for defining the capability characteristics of the flight management system, including consideration of product lines and business, consideration of operations, consideration of functions, and consideration of safety.

[0038] (b) The form of defining the capability characteristics of the flight management system shall be clarified and defined in a table. The attribute columns shall include technical attributes and management attributes. The technical attributes shall include the capability characteristic number, capability characteristic name, capability characteristic description, standard traceability, functional hazard description, etc. The management attributes shall include the complexity, workload, technical maturity, and whether it is optional, etc. of the capability characteristic.

[0039] (c) Define the competency characteristics applicable to this project, based on the principles defined in (a) and the forms defined in (b).

[0040] (2) Select a capability feature, conduct demand analysis, describe the connotation of the capability feature, analyze the basis for capturing the capability feature requirements, and sort out the basis for capturing the capability feature requirements by analyzing the relevant standards, upper-level inputs, aircraft system constraints, messages, some assumptions and configurations. The specific methods of step (2) include:

[0041] (a) Describe the capability characteristics. Through descriptions at the operational and functional levels, describe in detail the connotation of the capability characteristics and define the scope and boundaries of the capability characteristics.

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

[0043] (c) Analyze upper-level inputs, including product specifications, human-computer interaction requirements, etc.;

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

[0045] (f) Analyze the advisories and cautions triggered by relevant conditions;

[0046] (g) make some assumptions, including those that require further confirmation from the client;

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

[0048] (3) Based on the results of the requirements analysis, system requirements are captured from five perspectives: human-computer interaction, interface, behavior, architecture, and performance, and requirements are defined according to the requirements definition standards.

[0049] (a) Consider the human-computer interaction between the pilot and the cockpit components, capture the human-computer interaction requirements related to the flight management system, such as flight management system pages, flight management system messages, primary flight display PFD, navigation display ND, vertical status display VSD, etc.;

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

[0051] (c) Consider stimulus / 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) Capture the flight management system performance requirements by taking into account requirements such as accuracy, real-time performance, integrity, and data throughput.

[0054] It is understandable that those skilled in the art can make equivalent substitutions or changes based on the technical solution and inventive concept of the present invention, and all these changes or substitutions should fall within the protection scope of the claims attached to the present invention.

Claims

1. A method for capturing system requirements of a flight management system based on capability characteristics, characterized in that The following steps are involved: (1) Determine the principles and forms for defining the capability characteristics of the flight management system, identify the capability characteristics, and define the capability characteristics; (2) Select a capability feature, conduct a demand analysis, describe the connotation of the capability feature, and analyze the basis for capturing the capability feature requirements. By analyzing the relevant standards, upper-level inputs, aircraft system constraints, messages, some assumptions, and configurations, the basis for capturing the capability feature requirements can be clarified. (3) Based on the results of the requirements analysis, system requirements are captured from five perspectives: human-computer interaction, interface, behavior, architecture, and performance, and requirements are defined according to the requirements definition standards.

2. The method for capturing system requirements of a flight management system based on capability characteristics as claimed in claim 1, characterized in that: The specific method of defining capability characteristics in step (1) includes: (a) Clarify the principles for defining the capability characteristics of the flight management system, including: considering product lines and business, considering operations, considering functions, and considering safety; (b) The form of defining the capability characteristics of the flight management system shall be clarified in the form of a table. The attribute columns shall include technical attributes and management attributes. The technical attributes shall include the capability characteristic number, capability characteristic name, capability characteristic description, standard traceability, and functional hazard description. The management attributes shall include the complexity, workload, technical maturity, and whether the capability characteristic is optional. (c) Define the competency characteristics applicable to this project, based on the principles defined in (a) and the forms defined in (b).

3. The method for capturing system requirements of a flight management system based on capability characteristics as claimed in claim 1, characterized in that: The specific method of demand analysis in step (2) includes: (a) Describe the capability characteristics, describe the connotation of the capability characteristics in detail through the description of the operation level and the functional level, and define the scope and boundaries of the capability characteristics; (b) Analyze the standards, including the airworthiness certification basis and design basis; (c) Analyze upper-level inputs, including product specifications and human-computer interaction requirements; (d) Analyze aircraft system constraints, including interfaces and architecture; (f) Analyze the advisories and cautions triggered by relevant conditions; (g) make some assumptions, including those that require further confirmation from the client; (h) Consider the product platform and analyze the configuration of airlines and aircraft manufacturers.

4. The method for capturing system requirements of a flight management system based on capability characteristics as claimed in claim 1, characterized in that: The specific method of demand capture in step (3) includes: (a) Consider the human-computer interaction between the pilot and the cockpit components, and capture the human-computer interaction requirements related to the flight management system, including the flight management system page, flight management system message, primary flight display PFD, navigation display ND, and vertical status display VSD; (b) Consider the data interaction between the flight management system and related external systems, and capture the flight management system interface requirements; (c) Consider stimulus / event response and system fault tolerance, and capture the flight management system behavior requirements; (d) Consider the actual physical architecture of the flight management system and capture the flight management system architecture requirements; (e) Capture flight management system performance requirements in terms of accuracy, real-time performance, integrity, and data throughput.

Images