Application scene-oriented service thread design method and device

Abstract

The invention provides an application scene-oriented service thread design method and device aiming at the problem of lack of service thread design processes and methods. Task scene analysis oriented to system capability requirements, system architecture analysis based on a typical application scene static model, a business mode analysis process based on a capability node irrelevant concept and a business thread analysis process based on a mapping analysis model are given, and method reference is provided for standardizing business thread design and conformity verification. And the business thread design and verification efficiency and the standardization degree can be improved.

Description

Technical Field

[0001] The present invention belongs to the field of aviation system engineering technology, and in particular relates to a business thread design method and device oriented to application scenarios. Background Art

[0002] The application scenario is realized through the organic combination of multiple business threads.

[0003] Currently, there is a lack of standardized definition of business thread design methods in China. Business thread analysis needs to be repeated for different application scenarios, resulting in low design efficiency.

[0004] The business thread design method for application scenarios can standardize and abstract general business operation processes, form a reusable business model knowledge base, and improve the efficiency of business thread design in typical application scenarios. Summary of the invention

[0005] The present invention mainly solves the problem of standard definition of business thread design process and method, provides a business thread design method and device oriented to application scenarios, and guides the standardized definition of activities and input / output of each process of task thread design.

[0006] A first aspect of the present invention provides a business thread design method oriented to an application scenario, comprising the following steps:

[0007] Obtain the application scenario environment, capability node model, and scenario operation model of the application scenario;

[0008] Determine the business model corresponding to the application scenario in the application scenario model library;

[0009] Instantiate the business model corresponding to the application scenario based on the application scenario environment and capability node model;

[0010] Run the model according to the instantiated business mode and scenario to obtain the business thread.

[0011] Optionally, the application scenario environment includes: application background, mission area, mission objectives, number of capability nodes and their geographical distribution.

[0012] Optionally, the capability node model includes: the composition, charge-and-control relationship, and attributes of each capability node in an application scenario environment.

[0013] Optionally, the scenario operation model is analyzed using a general task process operation flow method to indicate the operation process of each capability node based on time-space relationships in an application scenario environment.

[0014] Optionally, the method further includes:

[0015] Obtain the task activities of each capability node in the capability node model;

[0016] Obtain various interactive messages generated by each capability node performing various task activities, as well as the flow process of various interactive messages in the application scenario;

[0017] Obtain the capability requirements of each capability node that supports task activities and interactive message flows;

[0018] Build business models based on task activities, interaction information, and capability requirements.

[0019] Optionally, constructing a business model according to task activities, interaction information and capability requirements includes:

[0020] Obtain the scope and boundaries of the business model based on task activities, interactive information, and capability requirements;

[0021] Optionally, the business model architecture includes: business name, capability node elements, business model role organizational relationships, business operation process and its information interaction.

[0022] A second aspect of the present invention provides a service thread design device oriented to an application scenario, which is used to execute the method as described in any one of the first aspects.

[0023] In response to the problem of lack of business thread design process and method, the present invention proposes a business thread design method oriented to application scenarios, provides task scenario analysis oriented to system capability requirements, system architecture analysis based on typical application scenario static model, business model analysis process based on capability node-independent concept and business thread analysis process based on mapping analysis model, which provides a methodological reference for standardizing business thread design and compliance verification, and helps to improve the efficiency and standardization of business thread design and verification. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 It is a business thread design flow chart for application scenarios;

[0025] Figure 2 It is a task scenario analysis flow chart oriented to system capability requirements;

[0026] Figure 3 It is a flowchart of system architecture analysis based on the static model of typical application scenarios;

[0027] Figure 4 It is a business model analysis flow chart based on the concept of capability node independence;

[0028] Figure 5 It is a business thread analysis flowchart based on business model combination. DETAILED DESCRIPTION

[0029] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0030] The features and illustrative embodiments of various aspects of the present invention will be described in detail below. In the detailed description below, many specific details are proposed to provide a comprehensive understanding of the present invention. However, it is obvious to those skilled in the art that the present invention can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present invention by illustrating examples of the present invention. The present invention is by no means limited to any specific settings and methods proposed below, but covers any improvements, replacements and modifications of structures, methods, devices without departing from the spirit of the present invention. In the accompanying drawings and the following description, known structures and technologies are not shown to avoid unnecessary ambiguity in the present invention.

[0031] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other, and the embodiments can refer to and quote each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0032] The present invention is further described in detail below in conjunction with embodiments and drawings, but the embodiments of the present invention are not limited thereto.

[0033] The present invention proposes a business thread design method oriented to an application scenario, comprising the following steps:

[0034] 1. Application scenario analysis process definition for system capability requirements

[0035] It is mainly used to define the application scenario analysis process based on system capability requirements and clarify the process design methods of task scenario analysis, including defining the application scenario environment, capability node model, and scenario operation model, to provide scenario input for system architecture analysis.

[0036] (1) Define the application scenario environment

[0037] The definition of the application scenario environment mainly includes the application background, task area, task objectives, the number of capability nodes and their geographical distribution. By defining the application scenario environment, the application boundaries, time and space constraints and related task conditions of the task are clarified.

[0038] (2) Define capability node model

[0039] Based on the definition of the application scenario environment, a model of the composition, charge-and-control relationship, and attributes of each capability node in the application scenario environment is constructed to provide capability node input for the application scenario operation.

[0040] (3) Design scenario operation model

[0041] The general task process operation flow method (such as F2E2TA, OODA, etc.) is used to carry out task phase process analysis, define the operation process of each capability node based on time and space relationship in the application scenario environment, and form a static model of the application scenario.

[0042] 2. Architecture analysis process definition based on static model of typical application scenarios

[0043] The architecture analysis process based on the static model of typical application scenarios mainly defines architecture models such as system task activities, information interaction and capability requirements, and provides design input for conducting capability node-independent business model analysis.

[0044] (1) Define system task activities

[0045] Based on the task scenario process definition, analyze the task activities of each capability node to provide input for defining system capability requirements.

[0046] (2) Define system information interaction

[0047] Based on the task scenario process definition, analyze the various messages generated by each capability node when performing various task activities, as well as the flow of each message in the system.

[0048] (3) Define system capability requirements

[0049] Aiming at each system task activity and interactive message of each capability node, analyze the capability requirements that each capability node needs to have to support task activities and message interactions.

[0050] 3. Business model analysis process definition based on the concept of capability node independence

[0051] The business model analysis process based on the concept of capability node independence is oriented to the system architecture model, defines the business model boundary, and abstracts the business model architecture to form a reusable business model model library to support business thread design.

[0052] (1) Define business model boundaries

[0053] Analyze the scope and boundaries of business models based on the activities, interactive information, and capability requirements formed by the architecture analysis process. Usually, the scope and boundaries of each business model are divided in the form of activity clustering or task segmentation to ensure that each business model is independent or decoupled.

[0054] (2) Define the business model architecture

[0055] The business model architecture usually abstracts the general business model architecture model based on a task closed-loop model or process, including the business name, capability node elements, business model role organizational relationship, business operation process and information interaction description, etc.

[0056] 4. Business thread analysis process definition based on business model combination

[0057] The business thread analysis process is oriented to the needs of typical application scenarios, instantiates general business mode models, and combines general business modes according to the needs of task processes to form business threads to support the operation of application scenarios. At the same time, in the process of business thread design, if there are uncovered processes involved, new business mode models can be abstracted to improve the existing business mode knowledge base.

[0058] (1) Instantiate business model

[0059] The business model is instantiated and defined based on the specific capability node attributes, command-and-control relationships, and geographical deployment of the application scenario.

[0060] (2) Define business threads

[0061] According to the typical application scenario process, the instantiated business models are logically combined to form a business thread flow that meets the requirements of the task process.

[0062] (3) Analyze business thread coverage

[0063] Carry out business model mapping based on task requirements and analyze the coverage of business models on business threads. If there are processes in the business threads that are not covered by the current business model, the uncovered processes can be abstracted according to the business model analysis method of the capability node-independent concept to form a new business model and update the original business model knowledge base.

[0064] like Figure 1 , the business thread design process for application scenarios is as follows:

[0065] Process (1) is mainly used to define the application scenario environment, capability node model, scenario operation model, etc., as input for subsequent system architecture analysis;

[0066] Process (2) is based on the application scenario environment, system capability indicators and task scenario process defined in process (1), and carries out the process of defining system task activities, information interaction and capability requirement analysis, providing a standardized system architecture model input for business model analysis;

[0067] Process (3) defines the business model boundary based on the standardized system architecture model formed by process (2), and abstracts the business model architecture to form a business model architecture model that is independent of capability nodes and can be reused.

[0068] Process (4) instantiates the business model architecture model defined in process (3) for typical application scenario requirements, and combines common business models to form business threads according to task process requirements to support the operation of application scenarios. At the same time, in the process of business thread design, if there are uncovered processes involved, new business model models can be abstracted to improve the existing business model knowledge base.

[0069] like Figure 2 ,The application scenario analysis process for system capability requirements is as follows:

[0070] Process (1) Define the application scenario environment, including the task background, task area, task objectives, number of capability nodes and their geographical distribution, etc. By defining the application scenario environment, confirm the application boundary, spatiotemporal constraints and related task conditions of the task;

[0071] Process (2) is based on the application scenario environment defined in process (1), and defines the composition of each capability node, the charge relationship between nodes, and the node attributes, and supports the task scenario process definition to provide capability node input;

[0072] Process (3) is based on the capability node model constructed in process (2), oriented towards the general task process operation process, conducts task stage process analysis, and defines the operation process of each capability node based on the time-space relationship in the application scenario environment.

[0073] like Figure 3 ,The design process of the key system integration element association model for business needs is as follows:

[0074] Process (1) Analyze the task activity model of each capability node supporting each task stage based on the static model of the application scenario;

[0075] Process (2) is oriented to the application scenario model. Based on the task activity model of each capability node in process (1), it analyzes the information of the task interaction model of each capability node and its interaction logic model.

[0076] Process (3) is oriented towards the task activity model and information interaction model formed by processes (1) and (2), and analyzes the capability requirements to support the operation of the task activity and interactive message model.

[0077] like Figure 4 ,The business model analysis process based on the concept of capability node independence is as follows:

[0078] Process (1) uses a decoupling approach based on the architecture model to analyze the boundaries of business models, define common interfaces for each business model, and ensure that each business model has an independent capability scope.

[0079] Process (2) is based on the business model boundaries and common interfaces formed in process (1), and uses a task closed-loop model or process to abstract the business model architecture model, including business name, participating capability node elements, organizational relationships of each capability node role, business operation process and information interaction description, etc. By abstracting various business models, a business model library is formed.

[0080] like Figure 5 ,The business thread analysis process based on the mapping analysis model is as follows:

[0081] Process (1) Instantiates the business model that supports the operation of the scenario based on the specific capability node attributes, command and control relationships, geographical deployment and other information involved in the typical scenario.

[0082] Process (2) combines the business models instantiated in process (1) according to the typical application scenario process to form a business thread flow that meets the requirements of the task process.

[0083] Process (3) maps the business model based on task requirements and analyzes the coverage of the business model on the business thread. If there are processes in the business thread that are not covered by the current business model, the uncovered processes can be abstracted according to the business model analysis method of the capability node-independent concept to form a new business model and update the original capability node-independent business model library.

[0084] The above description is only a further embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent replacements or changes according to the technical solutions and concepts of the present invention within the scope disclosed by the present invention, which belong to the protection scope of the present invention.

Claims

1. A business thread design method for application scenarios, characterized in that: The following steps are involved: Obtain the application scenario environment, capability node model, and scenario operation model of the application scenario; Determine the business model corresponding to the application scenario in the application scenario model library; Instantiate the business model corresponding to the application scenario based on the application scenario environment and capability node model; Run the model according to the instantiated business mode and scenario to obtain the business thread.

2. The application scenario-oriented service thread design method according to claim 1, characterized in that: The application scenario environment includes: application background, mission area, mission objectives, number of capability nodes and their geographical distribution.

3. The application scenario-oriented service thread design method according to claim 1, characterized in that: The capability node model includes: the composition, charge-and-control relationship, and attributes of each capability node in the application scenario environment.

4. The application scenario-oriented service thread design method according to claim 3 is characterized in that: The scenario operation model is analyzed using the general task process operation flow method, and is used to indicate the operation process of each capability node based on the time-space relationship in the application scenario environment.

5. The application scenario-oriented service thread design method according to claim 1, characterized in that: The method further comprises: Obtain the task activities of each capability node in the capability node model; Obtain various interactive messages generated by each capability node performing various task activities, as well as the flow process of various interactive messages in the application scenario; Obtain the capability requirements of each capability node that supports task activities and interactive message flows; Build business models based on task activities, interaction information, and capability requirements.

6. The application scenario-oriented service thread design method according to claim 5, characterized in that: The business model is constructed according to the task activities, interaction information and capability requirements, including: Capture the scope and boundaries of the business model based on task activities, interaction information, and capability requirements.

7. The application scenario-oriented service thread design method according to claim 5, characterized in that: The business model architecture includes: business name, capability node elements, business model role organizational relationship, business operation process and its information interaction.

8. A business thread design device for application scenarios, characterized in that: Used to perform the method according to any one of claims 1 to 7.

Images