CN-122018857-A - Design method for generating standard system from avionics task system architecture model

CN122018857ACN 122018857 ACN122018857 ACN 122018857ACN-122018857-A

Abstract

The invention provides a design method for generating a standard system from an avionics task system architecture model, which comprises the steps of 1, designing a task style frame comprising a task environment, a task scene, a flight profile, a task plan, a node deployment scheme, a command relationship and a task rule, 2, designing a logic architecture frame comprising a capability architecture, a task architecture and a function architecture, and 3, capturing standard requirements to generate the standard system. The device platform can ensure clearer functional positioning of the device platform, has more accurate performance indexes, and avoids resource waste and repeated construction.

Inventors

She Mingren
XUE BING
WANG JINYAN
ZHOU HAIBING
YAN JIN

Assignees

中国航空无线电电子研究所

Dates

Publication Date: 20260512
Application Date: 20251227

Claims (8)

1. A design method for generating a standard system from an avionics task architecture model, comprising: Step 1, designing a task style framework, wherein the task style framework comprises a task environment, a task scene, a flight profile, a task plan, a node deployment scheme, a command relationship and a task rule; step 2, designing a logic architecture framework comprising a capability architecture and capability architecture model, a task architecture and task architecture model, and a function architecture and function architecture model; And step 3, capturing standard requirements, namely, capturing the standard requirements and constructing a standard system according to a capability framework, a task framework and a functional framework model which are designed for typical task scenes based on a standard recognition principle, a standard modification requirement and a standard selection principle.
2. The method of claim 1, wherein the task style framework is designed by performing standardized description on the form of the space domain scene for the task style to form a scene document capable of guiding modeling analysis and architecture design, wherein task scene design is normalized from the aspects of space environment and time plan, and performance, consumption and cost of the task scene design is evaluated, so that a task scene design model or document is formed and used as input of logic domain design.
3. The method of claim 2, wherein the step of determining the position of the substrate comprises, When the task environment is designed, the typical characteristics and development trends of the landscape environment, the natural environment, the social environment and the information environment are described through texts and pictures; when a task scene is designed, basic actions in the scene are determined, including fixed-point delivery actions and monitoring actions; When the flight profile is designed, the position state and the action change of the whole scene of the designated node are designed in the form of a table or an image; When a task plan is designed, determining a cooperative scheme of the participating nodes, describing a process from planning organization, implementation scheme, space preparation, on-site training to deployment arrangement through text, wherein the process comprises analysis and judgment of tasks, game targets and expectations, task commands and action schemes; when a node deployment scheme is designed, the types, the number and the deployment positions of the participating nodes of one party are arranged according to the strength comparison of the two parties in the game, and the names and the types of the space of the nodes are described through texts; when the command relationship is designed, describing the command relationship and mode of each level command mechanism or node through a command relationship diagram; when the task rule is designed, the task process is described through text or a flow chart, and the task process is performed in the order of initiating the task, leading and pushing the task, suspending or ending the task and stabilizing the action.
4. The method of claim 1, wherein designing the logic architecture framework is: Designing a capability architecture, namely designing a capability architecture model based on a task scene, namely designing a capability architecture, wherein the capability architecture comprises system capability analysis, system capability-sub-capability decomposition, capability dependency relationship analysis and capability-activity relationship analysis, constructing a capability architecture model of capability conception, classification, definition and relationship, and providing input for capturing related standard requirements of capability class; designing a task architecture, namely designing a task architecture model based on a task scene to design a document, wherein the task architecture model comprises task scene analysis, task activity decomposition and node interaction analysis, constructing a task architecture model of action concepts, node connection, organization relations, task activities, interface relations and task time sequences, analyzing task scene to design platform-level task requirements, and providing input for capturing unit capability type and flow type related standard requirements; Designing a functional architecture, generating a functional architecture model, namely designing a system functional architecture of a participating platform according to the result of task architecture design, wherein the system functional architecture comprises functional domain division, functional decomposition, functional interaction analysis, constructing a functional architecture model of system composition, system functions, message transmission and state conversion, analyzing the system functional requirements of the participating platform, and providing input for capturing the technical class related standard requirements.
5. The method according to claim 1, wherein the capturing standard requirements are specifically: aiming at the system capacity in the capacity architecture, the participation unit capacity, action flow and system operation flow in the task architecture, and the equipment/information system function in the function architecture, judging whether each capacity, flow and function need standard specification or not from the following dimensions: capability/flow/function input; constraints and control conditions of capabilities/flows/functions; capability/flow/functional tool usage method or flow; capability/flow/function output; According to a preset evaluation criterion, evaluating whether the input, constraint and control conditions, methods or processes and output should be included in the standard as standard requirements, wherein the preset evaluation criterion is as follows: Whether the standard is needed to ensure that the equipment meets the index or the requirement of task use; whether standard solidification and inheritance definition and description are needed or not; Thirdly, whether a standard control activity flow is needed; Whether the standard is needed to improve the development efficiency or reduce the development cost; Determining the content as a standard requirement entry when at least one criterion is satisfied; when all the evaluation criteria are not met, the standard requirement of the element is marked as no; The method comprises the steps of carrying out normalization and numbering on standard requirement items, carrying out association matching on a current standard set and standard requirements, judging whether the current standard can cover each standard requirement, associating the standard requirement into a standard configuration file model if the current standard is required, associating the standard requirement into a standard prediction description model if the standard is required to be added, and describing the content requirement of the added standard according to the corresponding capacity/flow/function meeting criteria by combining a logic architecture model.
6. The method according to claim 5, wherein the standard system is constructed specifically as follows: The method comprises the steps of generating a standard configuration file model, classifying and combining all standard adoption requirement entries, describing types, numbers, names and release time of the adopted standards to obtain the standard configuration file model, wherein the standards in the standard configuration file comprise capability type standard adoption requirements, flow type standard adoption requirements and standard file entries corresponding to technical type standard adoption requirements, and establishing a traceability relationship between the standard file entries and the standard requirements; and generating a standard prediction description model, namely classifying and merging all new standard requirement entries, describing new revised standard types, names and content requirements, and establishing a traceable relation between the new standard and the standard requirement to obtain the standard prediction description model.
7. The method of claim 6, wherein the step of providing the first layer comprises, The capability class standard traces back a corresponding capability/task architecture model aiming at capability class standard requirements, and determines the content requirements of the standard, wherein the content requirements comprise definition of a series of task sub-capabilities involved in solidification, dependent activities, dependent nodes, realization flows and capability indexes; The process type standard traces back a task event tracking model of a corresponding task architecture according to the process type standard requirement, and determines the content requirement of the standard, wherein the content requirement comprises a series of related actions, the activity flow of the task and a command cooperative relationship; the technical standard aims at a functional architecture function description model and a system event tracking model corresponding to technical standard requirement trace, and determines the content requirements of the standard, wherein the content requirements comprise the design requirements of a series of related system functions and communication interaction functions.
8. The method of claim 7, wherein the step of determining the position of the probe is performed, One newly added standard can correspond to a plurality of standard requirements, and one standard requirement can correspond to a plurality of newly added standards.

Description

Design method for generating standard system from avionics task system architecture model Technical Field The invention belongs to the technical field of standard specifications, and relates to a design method for generating a standard system from an avionics task system architecture model. Background The traditional standardized system design method generally adopts six-dimensional models, work decomposition structures, parallel decomposition methods, seed division methods/process division methods, classification methods and other system engineering methods of standardized system engineering, but has remarkable limitations on a bottom-up project collection mode, namely, on one hand, the method is provided with a top-level design, but is only presented in an isolated standard system block diagram and a detail table, and lacks explicit and modeling association with key elements such as top-level equipment capacity planning, task use scenes, technical development expectations and the like, on the other hand, the linear propulsion mode leads standard requirement generation to have one-sided (limited to a local view angle), repeatability (difficult to cooperate with multiple department requirements), postmortem (lagged to task evolution) and other stubborn diseases. Disclosure of Invention In order to solve systematic defects of lag in demand generation, weak system association and the like in a traditional standardized mode, the invention provides a design method for generating a standard system from an avionics task system architecture model, which comprises the following steps: A design method for generating a standard architecture from an avionics task architecture model, comprising: Step 1, designing a task style framework, wherein the task style framework comprises a task environment, a task scene, a flight profile, a task plan, a node deployment scheme, a command relationship and a task rule; step 2, designing a logic architecture framework comprising a capability architecture and capability architecture model, a task architecture and task architecture model, and a function architecture and function architecture model; And step 3, capturing standard requirements, namely, capturing the standard requirements and constructing a standard system according to a capability framework, a task framework and a functional framework model which are designed for typical task scenes based on a standard recognition principle, a standard modification requirement and a standard selection principle. Optionally, when designing the task style framework, the task style is subjected to standardized description in the form of an airspace scene for use in forming a scene document capable of guiding modeling analysis and architectural design, namely, the task scene is normalized from the aspects of space environment and time plan, and the task scene is evaluated in the aspects of performance, consumption and cost, so that a task scene prediction model or document is formed and used as the input of logic domain design. Alternatively, the typical characteristics of social environments, information environments, and trends; when a task scene is designed, basic actions in the scene are determined, including fixed-point delivery actions and monitoring actions; When the flight profile is designed, the position state and the action change of the whole scene of the designated node are designed in the form of a table or an image; When a task plan is designed, determining a cooperative scheme of the participating nodes, describing a process from planning organization, implementation scheme, space preparation, on-site training to deployment arrangement through text, wherein the process comprises analysis and judgment of tasks, game targets and expectations, task commands and action schemes; when a node deployment scheme is designed, the types, the number and the deployment positions of the participating nodes of one party are arranged according to the strength comparison of the two parties in the game, and the names and the types of the space of the nodes are described through texts; when the command relationship is designed, describing the command relationship and mode of each level command mechanism or node through a command relationship diagram; when the task rule is designed, the task process is described through text or a flow chart, and the task process is performed in the order of initiating the task, leading and pushing the task, suspending or ending the task and stabilizing the action. Optionally, the design logic architecture framework specifically includes: Designing a capability architecture, namely designing a capability architecture model based on a task scene, namely designing a capability architecture, wherein the capability architecture comprises system capability analysis, system capability-sub-capability decomposition, capability dependency relationship analysis and capability-activity relationship analysis, constructing