Multi-view coordination management method and system based on OTX intelligent coordination strategy

Abstract

The invention discloses a multi-view coordination management method and system based on an OTX intelligent coordination strategy, and the method comprises the steps: recognizing a current OTX diagnostic sequence development stage, obtaining the task complexity of the current OTX diagnostic sequence development stage, judging whether the current OTX diagnostic sequence development stage is a view demand stage or not, and if the current OTX diagnostic sequence development stage is the view demand stage, carrying out the multi-view coordination management. If yes, establishing task feature view demand association mapping, obtaining a view priority sequence of all views in the current OTX diagnostic sequence development stage, obtaining display priorities of all views based on the view priority sequence, extracting a cooperation mode, and recommending a cooperation strategy based on the cooperation mode and the display priorities of all views. According to the method, the development stage is automatically identified, the optimal view layout is recommended, the manual view switching time is shortened, the cooperation strategy is intelligently adjusted based on the current diagnosis task characteristics, and the task completion efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of OTX development technology, specifically to a multi-view coordination management method and system based on OTX intelligent collaboration strategy. Background Technology

[0002] In the OTX diagnostic sequence development environment, developers need to work using multiple views simultaneously, including a graphical sequence editor, code editor, flowchart view, and debug view. Existing technologies have the following limitations: Insufficient support for OTX-specific collaboration: Existing view coordination methods lack understanding and optimization of the workflow specific to OTX diagnostic sequence development.

[0003] Poor adaptability to diagnostic tasks: Unable to dynamically adjust view collaboration strategies according to different stages of OTX diagnostic tasks (such as sequence design, parameter configuration, debugging and testing).

[0004] Inefficient team collaboration: When multiple people are collaboratively developing OTX diagnostic sequences, there is a lack of intelligent view coordination mechanisms based on project roles and task assignments.

[0005] Lack of diagnostic context awareness: View coordination lacks a deep understanding of the professional context such as diagnostic protocols and vehicle communication characteristics.

[0006] Lack of intent understanding: The system cannot understand the user's intent when switching between multiple views, resulting in a lack of intelligence in view switching and coordination.

[0007] Rigid resource allocation: Resource allocation between views adopts a static strategy and cannot be dynamically optimized according to real-time workload.

[0008] Collaboration effectiveness is difficult to assess: There is a lack of quantitative evaluation and continuous optimization mechanisms for the effectiveness of multi-view collaboration. Summary of the Invention

[0009] To address the problems existing in the prior art, this invention provides a multi-view coordination management method and system based on OTX intelligent collaboration strategy. By automatically identifying the development stage and recommending the optimal view layout, it reduces the time spent manually switching views and intelligently adjusts the collaboration strategy based on the characteristics of the current diagnostic task, thereby improving task completion efficiency.

[0010] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0011] According to a first aspect of this application, a multi-view coordination management method based on an OTX intelligent collaboration strategy is provided, comprising: Identify the current stage of OTX diagnostic sequence development; Obtain the task complexity of the current OTX diagnostic sequence development stage; Based on the current OTX diagnostic sequence development stage and task complexity, determine whether the current OTX diagnostic sequence development stage is the view requirement stage. If it is the view requirement stage, then establish a task feature view requirement association mapping. Based on the task feature view requirement association mapping, obtain the view priority sequence of all views in the current OTX diagnostic sequence development stage, and obtain the display priority of all views based on the view priority sequence; Extract collaboration modes and recommend collaboration strategies based on collaboration modes and the display priority of all views.

[0012] In some embodiments of this application, based on the foregoing scheme, identifying the current OTX diagnostic sequence development stage includes: Insert event listeners into the OTX development environment to capture the current sequence of events in the OTX environment. Using a preset time threshold as a sliding window, the current operation features, temporal features, and contextual features corresponding to the current operation event sequence are obtained in real time. A stage classification model based on random forest is established. The current operation feature, the temporal feature and the context feature are input into the stage classification model, and the probability of each development stage is output. The development stage corresponding to the highest probability is taken as the current OTX diagnostic sequence development stage.

[0013] In some embodiments of this application, based on the foregoing scheme, the current operation event sequence includes several current operation events, wherein the current operation event is a graphical design operation event, a parameter configuration operation event, a debugging operation event, or an optimization operation event; Current operational characteristics include the frequency of graphical editing operations corresponding to graphical design operation events, the density of parameter configuration operations corresponding to parameter configuration operation events, the concentration of debugging operations corresponding to debugging operation events, and the proportion of optimization operations corresponding to optimization operation events.

[0014] In some embodiments of this application, based on the foregoing scheme, obtaining the task complexity of the current OTX diagnostic sequence development stage includes: An OTX syntax parser is built using ANTLR, which traverses the AST nodes to obtain the nesting depth of loops, branch complexity, concurrency complexity, variable dependency depth, data type conversion complexity, and data access density. The task complexity is obtained by weighted summation of control flow complexity and data flow complexity; The method to obtain the control flow complexity is as follows: The abstract syntax tree in the current OTX diagnostic sequence development stage is parsed. The abstract syntax tree includes loop nesting depth, branch complexity, and concurrency complexity. The loop nesting depth is the maximum number of loop nesting levels, the branch complexity is the product of the number of if-else nodes and the branch coefficient, and the concurrency complexity is the product of the number of parallel execution blocks and the concurrency weight. The control flow complexity is obtained by weighted summation of loop nesting depth, branch complexity, and concurrency complexity; The method to obtain the complexity of the data stream is as follows: The data dependencies in the current OTX diagnostic sequence development stage are analyzed. The data dependencies include variable dependency depth, data type conversion complexity, and data access density. Variable dependency depth is the length of the longest data dependency chain, data type conversion complexity is the product of the number of explicit type conversions and the conversion weight, and data access density is the number of read / write operations divided by the number of lines of code. The data flow complexity is obtained by weighted summation of variable dependency depth, data type conversion complexity, and data access density.

[0015] In some embodiments of this application, based on the foregoing scheme, the step of determining whether the current OTX diagnostic sequence development stage is a view requirement stage based on the current OTX diagnostic sequence development stage and task complexity, and establishing a task feature view requirement association mapping if it is a view requirement stage, includes: A task feature vector is established, which includes development stage features, complexity features, task type features, and urgency features. The development stage feature is the one-hot encoding corresponding to the current OTX diagnostic sequence's development stage, which may be the graphical design stage, parameter configuration stage, debugging stage, or optimization stage. The complexity feature is a numerical display of the task complexity. The task type feature is a classification encoding of the graphical design stage, parameter configuration stage, debugging stage, or optimization stage. The urgency feature is a quantitative representation of the urgency level. Based on development stage characteristics and complexity characteristics, determine whether the current OTX diagnostic sequence is in the view requirement stage: If the current OTX diagnostic sequence development stage is the graphical design stage and the task complexity is greater than or equal to the first complexity threshold, the current OTX diagnostic sequence development stage is the parameter configuration stage and the task complexity is less than the first complexity threshold but greater than the second complexity threshold, the current OTX diagnostic sequence development stage is the debugging stage, or if the current OTX diagnostic sequence development stage is the optimization stage and the task complexity is less than the second complexity threshold, then the current OTX diagnostic sequence development stage is the view requirement stage. Establish a task feature view requirement association mapping, which maps the current OTX diagnostic sequence development stage to the corresponding view requirements. If the current OTX diagnostic sequence development stage is the graphical design stage, the corresponding view requirements are the architecture view, dependency view, and review view; if the current OTX diagnostic sequence development stage is the parameter configuration stage, the corresponding view requirements are the parameter view, constraint view, and verification view; if the current OTX diagnostic sequence development stage is the debugging stage, the corresponding view requirements are the debugging view, log view, and monitoring view; if the current OTX diagnostic sequence development stage is the optimization stage, the corresponding view requirements are the performance view, resource view, and optimization suggestion view.

[0016] In some embodiments of this application, based on the foregoing scheme, obtaining the view priority sequence of all views in the current OTX diagnostic sequence development stage based on the task feature view requirement association mapping, and obtaining the display priority of all views based on the view priority sequence, includes: Establish a view feature matrix for all views, and represent each view using a view feature vector; Calculate the cosine similarity between the view feature vector and the task feature vector for each view; Sort the views by cosine similarity, and use the view with the highest cosine similarity as the main view, and the other views as auxiliary views.

[0017] In some embodiments of this application, based on the foregoing scheme, the extraction of collaboration modes and the recommendation of collaboration strategies based on the collaboration modes and the display priority of all views include: Collaboration patterns are extracted based on member activity, task dependence, and communication density. These collaboration patterns include centralized collaboration, division of labor collaboration, or review collaboration. If the collaboration mode is centralized collaboration mode, then the main view will be centered and enlarged, and the auxiliary views will be distributed around it; If the collaboration mode is a division of labor collaboration mode, the views are grouped and aggregated, and the independent workspaces of all views are isolated. If the collaboration mode is review collaboration mode, the main view will be highlighted and the other views will be arranged side by side.

[0018] According to a second aspect of this application, a multi-view coordination management system based on an OTX intelligent collaboration strategy is provided, the system comprising: The identification module is used to identify the current development stage of the OTX diagnostic sequence; The task complexity acquisition module is used to obtain the task complexity of the current OTX diagnostic sequence development stage; The Task Feature View Requirement Association Mapping Establishment Module is used to determine whether the current OTX diagnostic sequence development stage is a view requirement stage based on the current OTX diagnostic sequence development stage and task complexity. If it is a view requirement stage, a task feature view requirement association mapping is established. The display priority acquisition module is used to obtain the view priority sequence of all views in the current OTX diagnostic sequence development stage based on the task feature view requirement association mapping, and to obtain the display priority of all views based on the view priority sequence. The collaboration strategy recommendation module is used to extract collaboration modes and recommend collaboration strategies based on the collaboration mode and the display priority of all views.

[0019] According to a third aspect of this application, a computer-readable storage medium is provided that stores a computer program thereon, the computer program including executable instructions that, when executed by a processor, implement the method described above.

[0020] According to a fourth aspect of this application, an electronic device is provided, comprising: One or more processors; A memory for storing executable instructions of the processor, which, when executed by the one or more processors, cause the one or more processors to implement the method described above.

[0021] The beneficial effects of this application are as follows: (1) This application provides a multi-view coordination management method and system based on OTX intelligent collaboration strategy, which automatically identifies the development stage and recommends the optimal view layout, reduces the time for manual view switching, and intelligently adjusts the collaboration strategy based on the characteristics of the current diagnostic task, thereby improving the efficiency of task completion and realizing task-aware collaboration.

[0022] (2) This application provides a multi-view coordination management method and system based on OTX intelligent collaboration strategy. Based on the task feature view requirement association mapping, the view priority sequence of all views in the current OTX diagnostic sequence development stage is obtained, the display priority of all views is obtained based on the view priority sequence, and the view coordination is carried out based on the collaboration mode, which reduces the learning cost and improves the collaboration efficiency.

[0023] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and do not limit this application. Attached Figure Description

[0024] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and are intended to explain the invention, but do not constitute an undue limitation thereof. In the drawings: Figure 1 This is a flowchart of a multi-view coordination management method based on OTX intelligent collaboration strategy according to the present invention; Figure 2 This is a schematic diagram of a multi-view coordination management device based on an OTX intelligent collaboration strategy according to the present invention; Figure 3 This is a schematic diagram of an electronic device according to the present invention. Detailed Implementation

[0025] To make the objectives, features, and advantages of this invention more apparent and understandable, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described below are only some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0026] It should be understood that the terms "comprising" and other similar expressions in the specification, claims, and accompanying drawings of this invention are intended to cover a non-exclusive inclusion, such as a process, method, system, or apparatus that includes a series of steps or units and is not limited to the listed steps or units. Furthermore, "first" and "second" are used to distinguish different objects and are not intended to describe a specific order.

[0027] According to the first aspect of this application, please refer to Figure 1 The flowchart illustrates a multi-view coordination management method based on an OTX intelligent collaboration strategy. This embodiment provides a multi-view coordination management method based on an OTX intelligent collaboration strategy, including: Step S1: Identify the current OTX diagnostic sequence development stage.

[0028] In some embodiments of this example, identifying the current OTX diagnostic sequence development stage includes: Step S101: Implant an event listener in the OTX development environment to capture the current operation event sequence of the developer in the OTX environment; Step S102: Using a preset time threshold as a sliding window, obtain the current operation features, temporal features, and context features corresponding to the current operation event sequence in real time; Step S103: Establish a stage classification model based on random forest. Input the current operation feature, the temporal feature and the context feature into the stage classification model, output the probability of each development stage, and take the development stage corresponding to the highest probability as the current OTX diagnostic sequence development stage.

[0029] In some embodiments of this example, the current operation event sequence includes several current operation events, which are graphical design operation events, parameter configuration operation events, debugging operation events, or optimization operation events. Specifically, graphical design operation events include node dragging, connection line creation, and block diagram combination; parameter configuration operation events include numerical input, constraint setting, and data type change; debugging operation events include breakpoint setting, single-step execution, and variable monitoring; and optimization operation events include performance analysis, code refactoring, and resource monitoring.

[0030] In this embodiment, when extracting the current operation event, data cleaning is performed: invalid operations (such as accidental clicks) are removed, and consecutive similar operations are merged into a single event. The time window is divided: the current operation event sequence is divided into 30-second units.

[0031] In some embodiments of this example, the current operational characteristics include the frequency of graphical editing operations corresponding to graphical design operation events, the density of parameter configuration operations corresponding to parameter configuration operation events, the concentration of debugging operations corresponding to debugging operation events, and the proportion of optimization operations corresponding to optimization operation events. The preset time threshold is 5 minutes, the frequency of graphical editing operations is the number of graphical design operation events divided by the total number of operations, the density of parameter configuration operation events is the number of parameter configuration operation events divided by the time window length, the concentration of debugging operation events is the number of consecutive occurrences of debugging operation events, and the proportion of optimization operations is the number of optimization operation events divided by the total number of operations.

[0032] In some implementations of this embodiment, the current operation features (frequency of graphic editing operations, density of parameter configuration operations, concentration of debugging operations, and proportion of optimization operations) are input into a random forest-based stage classification model for stage identification, and the current OTX diagnostic sequence development stage (graphical design stage, parameter configuration stage, debugging stage, or optimization stage) is output. Probability calculation is performed, and the stage corresponding to the highest probability is taken as the current OTX diagnostic sequence development stage.

[0033] Specifically, a state transition probability matrix is ​​established to describe the transition rules between states, an observation probability matrix is ​​constructed, operational features are correlated with development stages, a forward-backward algorithm is used to calculate state probabilities, the Viterbi algorithm is used to solve for the most likely state, and the current OTX diagnostic sequence development stage and corresponding confidence score are output.

[0034] Step S2: Obtain the task complexity of the current OTX diagnostic sequence development stage.

[0035] In some implementations of this embodiment, the task complexity of the current OTX diagnostic sequence development stage is obtained, including: An OTX syntax parser is built using ANTLR, which traverses the AST nodes to obtain the nesting depth of loops, branch complexity, concurrency complexity, variable dependency depth, data type conversion complexity, and data access density. The task complexity is obtained by weighted summation of control flow complexity and data flow complexity.

[0036] In this embodiment, the method for obtaining the control flow complexity is as follows: The abstract syntax tree in the current OTX diagnostic sequence development stage is parsed. The abstract syntax tree includes loop nesting depth, branch complexity, and concurrency complexity. The loop nesting depth is the maximum number of loop nesting levels, the branch complexity is the product of the number of if-else nodes and the branch coefficient, and the concurrency complexity is the product of the number of parallel execution blocks and the concurrency weight. The control flow complexity is obtained by weighted summation of loop nesting depth, branch complexity, and concurrency complexity.

[0037] In this embodiment, the method for obtaining the data stream complexity is as follows: The data dependencies in the current OTX diagnostic sequence development stage are analyzed. The data dependencies include variable dependency depth, data type conversion complexity, and data access density. Variable dependency depth is the length of the longest data dependency chain, data type conversion complexity is the product of the number of explicit type conversions and the conversion weight, and data access density is the number of read / write operations divided by the number of lines of code. The data flow complexity is obtained by weighted summation of variable dependency depth, data type conversion complexity, and data access density.

[0038] Step S3: Based on the current OTX diagnostic sequence development stage and task complexity, determine whether the current OTX diagnostic sequence development stage is the view requirement stage. If it is the view requirement stage, establish a task feature view requirement association mapping.

[0039] In some implementations of this embodiment, based on the current OTX diagnostic sequence development stage and task complexity, it is determined whether the current OTX diagnostic sequence development stage is a view requirement stage. If it is a view requirement stage, a task feature view requirement association mapping is established, including: A task feature vector is established, which includes development stage features, complexity features, task type features, and urgency features. Among them, the development stage feature is the one-hot encoding corresponding to the current OTX diagnostic sequence development stage, which is the graphical design stage, parameter configuration stage, debugging stage, or optimization stage; the complexity feature is the numerical display of task complexity; the task type feature is the classification encoding of the graphical design stage, parameter configuration stage, debugging stage, or optimization stage; and the urgency feature is the quantitative representation of the urgency level (low, medium, high, urgent). Based on development stage characteristics and complexity characteristics, determine whether the current OTX diagnostic sequence is in the view requirement stage: If the current OTX diagnostic sequence development stage is the graphical design stage and the task complexity is greater than or equal to the first complexity threshold, the current OTX diagnostic sequence development stage is the parameter configuration stage and the task complexity is less than the first complexity threshold but greater than the second complexity threshold, the current OTX diagnostic sequence development stage is the debugging stage, or if the current OTX diagnostic sequence development stage is the optimization stage and the task complexity is less than the second complexity threshold, then the current OTX diagnostic sequence development stage is the view requirement stage. Establish a task feature view requirement association mapping, which is the current OTX diagnostic sequence development stage and the corresponding view requirements. If the current OTX diagnostic sequence development stage is the graphical design stage, then the corresponding view requirements are the architecture view, dependency view, and review view. If the current OTX diagnostic sequence development stage is the parameter configuration stage, then the corresponding view requirements are parameter view, constraint view, and verification view. If the current OTX diagnostic sequence development phase is the debugging phase, then the corresponding view requirements are a debug view, a log view, and a monitoring view. If the current OTX diagnostic sequence development phase is the optimization phase, then the corresponding view requirements are performance view, resource view, and optimization suggestion view.

[0040] Step S4: Based on the task feature view requirement association mapping, obtain the view priority sequence of all views in the current OTX diagnostic sequence development stage, and obtain the display priority of all views based on the view priority sequence.

[0041] In some implementations of this embodiment, based on the task feature view requirement association mapping, the view priority sequence of all views in the current OTX diagnostic sequence development stage is obtained, and the display priority of all views is obtained based on the view priority sequence, including: Establish a view feature matrix for all views, and represent each view using a view feature vector; Calculate the cosine similarity between the view feature vector and the task feature vector for each view; Sort the cosine similarity scores to obtain the display priority of all views.

[0042] In this embodiment, for the current OTX diagnostic sequence development stage, the view with the highest cosine similarity is used as the main view, and other views are used as auxiliary views. The main view occupies 60% of the screen space, and the auxiliary views are evenly distributed in the remaining space. Considering the data flow relationship between views, related views are arranged nearby.

[0043] Step S5: Extract the collaboration mode and recommend a collaboration strategy based on the collaboration mode and the display priority of all views.

[0044] In some implementations of this embodiment, a collaboration mode is extracted, and a collaboration strategy is recommended based on the collaboration mode and the display priority of all views, including: Collaboration patterns are extracted based on member activity, task dependence, and communication density. These collaboration patterns include centralized collaboration, division of labor collaboration, or review collaboration. If the collaboration mode is centralized collaboration mode, then the main view will be centered and enlarged, and the auxiliary views will be distributed around it; If the collaboration mode is a division of labor collaboration mode, the views are grouped and aggregated, and the independent workspaces of all views are isolated. If the collaboration mode is review collaboration mode, the main view will be highlighted and the other views will be arranged side by side.

[0045] In this embodiment, collaboration patterns are extracted based on member activity, task dependence, and communication density. These collaboration patterns include centralized collaboration, division of labor collaboration, or review collaboration, among others. The collaboration mode index is obtained by weighting and summing the member activity, task dependence and communication density. If the collaboration mode is greater than or equal to the first preset collaboration threshold, the collaboration mode is a centralized collaboration mode; if the collaboration mode is less than the first preset collaboration threshold but greater than the second preset collaboration threshold, the collaboration mode is a division of labor collaboration mode; if the collaboration mode is less than the second preset collaboration threshold, the collaboration mode is a review collaboration mode.

[0046] In this embodiment, the task contribution of each member in the team is obtained based on the number of code submissions, view edits, and task completions of each member within a preset time threshold. The Gini coefficient is obtained based on the task contribution of all members, and the member activity level is obtained based on the Gini coefficient.

[0047] In this embodiment, a task dependency network is constructed within a preset time threshold. In the task dependency network, nodes represent tasks, and edges represent the dependency relationship that "task B can only start after task A is completed." The network density is calculated, and the task dependency degree is obtained based on the network density. The formula for calculating the network density is the divisor of the actual number of edges and the maximum possible number of edges.

[0048] In this embodiment, within a preset time threshold, the communication density is obtained based on the average communication volume per person. The average communication volume per person is the divisor of the total number of communications and the team size. The higher the average communication volume per person, the greater the communication density.

[0049] According to the second aspect of this application, such as Figure 2 As shown, this embodiment provides a multi-view coordination management system based on the OTX intelligent collaboration strategy. The system includes: The identification module is used to identify the current development stage of the OTX diagnostic sequence; The task complexity acquisition module is used to obtain the task complexity of the current OTX diagnostic sequence development stage; The Task Feature View Requirement Association Mapping Establishment Module is used to determine whether the current OTX diagnostic sequence development stage is a view requirement stage based on the current OTX diagnostic sequence development stage and task complexity. If it is a view requirement stage, a task feature view requirement association mapping is established. The display priority acquisition module is used to obtain the view priority sequence of all views in the current OTX diagnostic sequence development stage based on the task feature view requirement association mapping, and to obtain the display priority of all views based on the view priority sequence. The collaboration strategy recommendation module is used to extract collaboration modes and recommend collaboration strategies based on the collaboration mode and the display priority of all views.

[0050] Specifically, this embodiment corresponds one-to-one with the above method embodiments. The functions of each module have been described in detail in the corresponding method embodiments, so they will not be repeated here.

[0051] According to a third aspect of this application, this embodiment provides a computer-readable storage medium having a computer program stored thereon, the computer program including executable instructions that, when executed by a processor, implement the method described above.

[0052] The present invention can implement all or part of the processes in the above methods, or it can be accomplished by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or system capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0053] According to the fourth aspect of this application, such as Figure 3 As shown, an electronic device is provided, comprising: One or more processors; Memory is used to store executable instructions for the processor, which, when executed by one or more processors, cause one or more processors to implement the methods described above.

[0054] Electronic devices are manifested in the form of general-purpose computing devices. Components of an electronic device may include, but are not limited to: at least one processor, at least one memory, and a bus connecting different system components (including memory and processor).

[0055] The processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor. The processor is the control center of a computer system, connecting all parts of the computer system through various interfaces and lines.

[0056] Memory can be used to store computer programs and / or modules. The processor implements various functions of the computer system by running or executing the computer programs and / or modules stored in the memory, and by accessing data stored in the memory. Memory can mainly include a program storage area and a data storage area. The program storage area can store the operating system and at least one application program required for a function (e.g., sound playback, image playback, etc.); the data storage area can store data created based on the use of the mobile phone (e.g., audio data, video data, etc.). Furthermore, memory can include high-speed random access memory, and can also include non-volatile memory, such as hard disks, RAM, plug-in hard disks, SmartMedia Cards (SMC), Secure Digital (SD) cards, Flash Cards, at least one disk storage device, flash memory device, or other volatile solid-state storage devices.

[0057] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, servers, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and memory) containing computer-usable program code.

[0058] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), servers, and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A system that specifies functions in one or more boxes.

[0059] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction set implemented in a process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0060] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0061] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0062] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0063] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A multi-view coordination management method based on OTX intelligent collaboration strategy, characterized in that, include: Identify the current stage of OTX diagnostic sequence development; Obtain the task complexity of the current OTX diagnostic sequence development stage; Based on the current OTX diagnostic sequence development stage and task complexity, determine whether the current OTX diagnostic sequence development stage is the view requirement stage. If it is the view requirement stage, then establish a task feature view requirement association mapping. Based on the task feature view requirement association mapping, obtain the view priority sequence of all views in the current OTX diagnostic sequence development stage, and obtain the display priority of all views based on the view priority sequence; Extract collaboration modes and recommend collaboration strategies based on collaboration modes and the display priority of all views.

2. The method according to claim 1, characterized in that, The identification of the current OTX diagnostic sequence development stage includes: Insert event listeners into the OTX development environment to capture the current sequence of events in the OTX environment. Using a preset time threshold as a sliding window, the current operation features, temporal features, and contextual features corresponding to the current operation event sequence are obtained in real time. A stage classification model based on random forest is established. The current operation feature, the temporal feature and the context feature are input into the stage classification model, and the probability of each development stage is output. The development stage corresponding to the highest probability is taken as the current OTX diagnostic sequence development stage.

3. The method according to claim 2, characterized in that: The current operation event sequence includes several current operation events, which are graphical design operation events, parameter configuration operation events, debugging operation events, or optimization operation events; Current operational characteristics include the frequency of graphical editing operations corresponding to graphical design operation events, the density of parameter configuration operations corresponding to parameter configuration operation events, the concentration of debugging operations corresponding to debugging operation events, and the proportion of optimization operations corresponding to optimization operation events.

4. The method according to claim 1, characterized in that, The task complexity of obtaining the current OTX diagnostic sequence development stage includes: An OTX syntax parser is built using ANTLR, which traverses the AST nodes to obtain the nesting depth of loops, branch complexity, concurrency complexity, variable dependency depth, data type conversion complexity, and data access density. The task complexity is obtained by weighted summation of control flow complexity and data flow complexity; The method to obtain the control flow complexity is as follows: The abstract syntax tree in the current OTX diagnostic sequence development stage is parsed. The abstract syntax tree includes loop nesting depth, branch complexity, and concurrency complexity. The loop nesting depth is the maximum number of loop nesting levels, the branch complexity is the product of the number of if-else nodes and the branch coefficient, and the concurrency complexity is the product of the number of parallel execution blocks and the concurrency weight. The control flow complexity is obtained by weighted summation of loop nesting depth, branch complexity, and concurrency complexity; The method to obtain the complexity of the data stream is as follows: The data dependencies in the current OTX diagnostic sequence development stage are analyzed. The data dependencies include variable dependency depth, data type conversion complexity, and data access density. Variable dependency depth is the length of the longest data dependency chain, data type conversion complexity is the product of the number of explicit type conversions and the conversion weight, and data access density is the number of read / write operations divided by the number of lines of code. The data flow complexity is obtained by weighted summation of variable dependency depth, data type conversion complexity, and data access density.

5. The method according to claim 1, characterized in that, The step of determining whether the current OTX diagnostic sequence development stage is a view requirement stage based on the current OTX diagnostic sequence development stage and task complexity, and if it is a view requirement stage, then establishing a task feature-view requirement association mapping, includes: A task feature vector is established, which includes development stage features, complexity features, task type features, and urgency features. The development stage feature is the one-hot encoding corresponding to the current OTX diagnostic sequence's development stage, which may be the graphical design stage, parameter configuration stage, debugging stage, or optimization stage. The complexity feature is a numerical display of the task complexity. The task type feature is a classification encoding of the graphical design stage, parameter configuration stage, debugging stage, or optimization stage. The urgency feature is a quantitative representation of the urgency level. Based on development stage characteristics and complexity characteristics, determine whether the current OTX diagnostic sequence is in the view requirement stage: If the current OTX diagnostic sequence development stage is the graphical design stage and the task complexity is greater than or equal to the first complexity threshold, the current OTX diagnostic sequence development stage is the parameter configuration stage and the task complexity is less than the first complexity threshold but greater than the second complexity threshold, the current OTX diagnostic sequence development stage is the debugging stage, or if the current OTX diagnostic sequence development stage is the optimization stage and the task complexity is less than the second complexity threshold, then the current OTX diagnostic sequence development stage is the view requirement stage. Establish a task feature view requirement association mapping, which maps the current OTX diagnostic sequence development stage to the corresponding view requirements. If the current OTX diagnostic sequence development stage is the graphical design stage, the corresponding view requirements are the architecture view, dependency view, and review view; if the current OTX diagnostic sequence development stage is the parameter configuration stage, the corresponding view requirements are the parameter view, constraint view, and verification view; if the current OTX diagnostic sequence development stage is the debugging stage, the corresponding view requirements are the debugging view, log view, and monitoring view; if the current OTX diagnostic sequence development stage is the optimization stage, the corresponding view requirements are the performance view, resource view, and optimization suggestion view.

6. The method according to claim 1, characterized in that, The task feature view requirement association mapping obtains the view priority sequence of all views in the current OTX diagnostic sequence development phase, and obtains the display priority of all views based on the view priority sequence, including: Establish a view feature matrix for all views, and represent each view using a view feature vector; Calculate the cosine similarity between the view feature vector and the task feature vector for each view; Sort the views by cosine similarity, and use the view with the highest cosine similarity as the main view, and the other views as auxiliary views.

7. The method according to claim 6, characterized in that, The extraction of collaboration modes, based on the collaboration mode and the display priority of all views, recommends collaboration strategies, including: Collaboration patterns are extracted based on member activity, task dependence, and communication density. These collaboration patterns include centralized collaboration, division of labor collaboration, or review collaboration. If the collaboration mode is centralized collaboration mode, then the main view will be centered and enlarged, and the auxiliary views will be distributed around it; If the collaboration mode is a division of labor collaboration mode, the views are grouped and aggregated, and the independent workspaces of all views are isolated. If the collaboration mode is review collaboration mode, the main view will be highlighted and the other views will be arranged side by side.

8. A multi-view coordination management system based on OTX intelligent collaboration strategy, characterized in that, include: The identification module is used to identify the current development stage of the OTX diagnostic sequence; The task complexity acquisition module is used to obtain the task complexity of the current OTX diagnostic sequence development stage; The Task Feature View Requirement Association Mapping Establishment Module is used to determine whether the current OTX diagnostic sequence development stage is a view requirement stage based on the current OTX diagnostic sequence development stage and task complexity. If it is a view requirement stage, a task feature view requirement association mapping is established. The display priority acquisition module is used to obtain the view priority sequence of all views in the current OTX diagnostic sequence development stage based on the task feature view requirement association mapping, and to obtain the display priority of all views based on the view priority sequence. The collaboration strategy recommendation module is used to extract collaboration modes and recommend collaboration strategies based on the collaboration mode and the display priority of all views.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer program includes executable instructions that, when executed by a processor, implement the method of any one of claims 1-7.

10. An electronic device, characterized in that, include: One or more processors; A memory for storing executable instructions of the processor, which, when executed by the one or more processors, cause the one or more processors to perform the method according to any one of claims 1-7.

Images