Multi-user collaborative development method based on EasySAR configuration tool

Abstract

The invention discloses a multi-user collaborative development method based on an EasySAR configuration tool, and the method comprises the steps: S1, building a project group in the EasySAR configuration tool, enabling the information of the project group to comprise a project group invitation link, failure time and an invitation password, binding the user information with the project group, and limiting the authority of the related information of a project on the project group; s2, users in the project group create projects one by one, each user selectively shares data information of the own project, a web development interface corresponding to the project is obtained after the project is created, project configuration is carried out on the web development interface, constraint verification reminding is carried out in real time in the configuration process, and configuration items of different users are associated and synchronized; and S3, after all participating members in the project group receive a prompt that the verification configuration is successful, generating a code file, and completing the whole project configuration. The method for efficiently and conveniently developing the AutoSAR project through cooperation of multiple persons under the web architecture is achieved.

Description

Technical Field

[0001] The invention relates to a multi-user collaborative development method based on EasySAR configuration tool. Background Art

[0002] In the AUTOSAR architecture, basic configuration tools play a vital role. They are used to configure, verify and generate ECU basic software (BSW) and software components (SWC).

[0003] In today's AUTOSAR basic configuration tool market, local applications are the main ones, and the prominent features of such applications are: local applications usually run directly on the user's device, and the data is mainly stored locally. In a multi-device or multi-user environment, it is difficult to synchronize the locally stored data, which means that changes made on one device will not be automatically reflected on other devices. Without the concept of an account, users cannot synchronize data between different devices, and cannot interact with other users or share data.

[0004] Although online collaborative development tools on the market can use web communication technology to achieve data synchronization, in order to ensure the quality of development, they basically require manual review. In addition, conflicts may arise during the development process and need to be merged and resolved manually, which greatly affects development efficiency.

[0005] In the AUTOSAR system, each module has strict development specifications, and there are constraints on each container and parameter. Developers need to configure and develop according to the constraint specifications, and finally output usable code files for application in actual scenarios. Therefore, in the collaborative development process of the AUTOSAR project, it is necessary not only to ensure data synchronization but also the real-time constraint verification. When the configuration violates the constraint, the specific error information can be displayed in real time to reduce the repeated development and debugging process. Summary of the invention

[0006] The purpose of the present invention is to provide an efficient and convenient multi-user collaborative development method based on the EasySAR configuration tool.

[0007] To this end, the present invention provides a multi-user collaborative development method based on the EasySAR configuration tool, including: S1, creating a project group in the EasySAR configuration tool, the project group information including the project group invitation link, expiration time, invitation password, and binding user information and project group, and limiting the authority of project-related information to the project group; S2, users in the project group create projects one by one, and each user selectively shares the data information of his own project, and obtains the web development interface corresponding to the project after the project is created, performs project configuration on the web development interface, and performs constraint verification reminders in real time during the configuration process, wherein the configuration items between projects of different users are associated and synchronized; S3, when all participating members in the project group receive a prompt that the configuration is successfully verified, a code file is generated to complete the entire project configuration.

[0008] The present invention also provides a computer program product, including a computer program or an instruction, characterized in that when the computer program or the instruction is executed by a processor, the steps of a multi-user collaborative development method based on the EasySAR configuration tool are implemented.

[0009] The present invention also provides a computer device, comprising a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the multi-user collaborative development method based on the EasySAR configuration tool.

[0010] The EasySAR configuration tool of the present invention is an AUTOSAR configuration tool based on the web architecture. It introduces the concept of account. Users can invite other users to jointly form a project team. Members of the project team can share projects with each other and synchronize data in real time. At the same time, the module-related definition files are accessed, and real-time constraint verification of configuration data can be performed during the development and configuration process, and all generated and uploaded common files are recorded to ensure the interoperability of information.

[0011] In addition to the above-described purposes, features and advantages, the present invention has other purposes, features and advantages. The present invention will be further described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The drawings constituting a part of the present application are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings: Figure 1 is a flow chart of a multi-user collaborative development method based on the EasySAR configuration tool of the present invention; Figure 2 is a system architecture diagram of the EasySAR configuration tool of the present invention; Figure 3is a user configuration flow chart using the EasySAR configuration tool of the present invention; Figure 4 It is a schematic diagram of the EasySAR configuration tool of the present invention in a multi-user collaborative development scenario. DETAILED DESCRIPTION

[0013] The present invention will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0014] The present invention aims to provide an efficient and convenient method / system for multiple people to jointly develop AutoSAR projects. Based on the web page architecture, the user's account data information is logically isolated, and the user's account permissions are dynamically adjusted through project team management, so that members of the same project team can jointly develop a project.

[0015] like Figure 1 As shown, the multi-user collaborative development method based on the EasySAR configuration tool of the present invention includes the following steps S1-S3.

[0016] S1. Create a project group in the EasySAR configuration tool. The project group information includes the project group invitation link, expiration time, invitation password, and bind the user information and project group to limit the authority of project-related information to the project group.

[0017] S2. Users in the project group create projects one by one, and each user selectively shares the data information of his or her own project. After creating a project, the web development interface corresponding to the project is obtained. The project is configured on the web development interface and constraint verification reminders are performed in real time during the configuration process. The configuration items between projects of different users are associated and synchronized.

[0018] S3. When all participating members in the project team receive the prompt that the verification configuration is successful, the code file is generated to complete the entire project configuration.

[0019] The technical contents involved in each step of the method of the present invention are described in detail below.

[0020] 1. EasySAR System Composition The EasySAR system is an independently developed AutoSAR configuration tool. Figure 2 As shown, it is mainly composed of a web development interface front end built with a vue front-end architecture, a java back end built with a springboot architecture, and a module package.

[0021] The module package contains view models, constraint verification scripts, and generated code templates. The back-end architecture has built-in JAXBapi, which can map XML view models to Java objects, and return the JSON format agreed upon by the web interface for generating the interface. It also uses jep to call the py constraint verification script and return the verification results to the front-end page for display.

[0022] The data configured in the web interface will be stored after data processing in the backend. All data information based on the web development interface is stored in the same location.

[0023] The web page is different from the previous AutoSAR desktop version. It does not need to be installed and can be accessed by logging in to an account through a browser link. Under normal circumstances, a single account is developed independently, and the engineering data created is not interoperable. After the user logs in to the account, a unique token information will be generated on the front end and back end, which includes the currently logged in user information. For all configuration operations under the account, the token will follow the request header for communication and verification. After the token information is verified, all data information of the operation will be bound to the current user, thereby achieving data isolation.

[0024] 2. Project Configuration After the user creates a project, the first thing he sees is the visual configuration interface of the project. The user needs to complete the project configuration on this interface, which is implemented by parsing the Autosar xml view model.

[0025] As an extensible module plug-in, the module package belongs neither to the front end nor to the back end, and exists independently. The view model is an XML file that contains various tags and attributes included in the interface design.

[0026] The JAXB API built into the backend code can quickly convert the XML file content into a Java readable object, and then convert it into a standardized JSON format for the frontend. Based on the tags and attributes of the view model, configuration items of different styles of interfaces are generated. For example: <containers>This tag represents the container. <ecuc-param-conf-container-def>Represents a container instance, <ecuc-enumeration-param-def>Represents the parameter items of the enumeration class, <ecuc-string-param-def>Represents parameter items of string type, etc.

[0027] like Figure 3 As shown, after the standardized interface is generated, users can configure and develop the protocol stacks and modules they are responsible for in the graphical development interface.

[0028] 3. Collaborative Development 1. Project team management: members of the same project team can develop a project like Figure 4 As shown in the figure, when developing a complex protocol stack project, it often requires multiple development members to work together. At this time, we introduced the project team. Previously, data isolation was achieved based on accounts. In projects developed by multiple people, we use project teams as units for data isolation.

[0029] The person in charge of the actual development project team can create a project group_manage as an administrator, which can contain important information, such as the project group invitation link, expiration time, and invitation password, to ensure the security of the project group. Members who join the same project group have the right to share their own data information. By binding user information and project groups, the authority of project-related information is limited to the project group, and project sharing can be achieved, so that multiple users can develop the same project at the same time.

[0030] 2. Data synchronization: one user configuration information is synchronized to another user operation interface in real time, and they affect each other When multiple people collaborate on the same project, different members are responsible for configuring different modules, and the configuration items between modules are interrelated.

[0031] The configurator item of the Nm module in the network protocol stack will affect the CanNm module. In the Autosar specification, the value of CanNmBusSynchronizationEnabled under the CanNm module is affected by CanNmPassiveModeEnabled and NmBusSynchronizationEnabled under the Nm module. When user A configures the value of CanNmPassiveModeEnabled to false, and user B configures NmBusSynchronizationEnabled to true, user A will find that the value of CanNmBusSynchronizationEnabled is automatically assigned to true.

[0032] When developing a project, users can annotate parameter configuration items and take notes on the project. Other project members who are collaborating on the development can also see the notes in a timely manner, understand the development ideas, reduce communication barriers, and improve development efficiency.

[0033] 3. Information prompts: the relevant information configured by one user will be reminded to the operation interface of another user. During the user configuration process, if the user configuration is not accurate, the interface will remind you in real time. Currently, constraints can be divided into model constraints and custom constraints. The model constraint is the view model mentioned above. It can not only be used to generate the interface, but also plays an important role in verifying whether the configuration information meets the specifications.

[0034] When you open a container or operate a corresponding field in the web development interface, the backend performs verification through the validatePython interface. In the collaborative development process, the information data configured by all members participating in the development project are stored in the same location, and the data information that needs to be verified comes from everyone.

[0035] After specifying the module and parameter method, the backend generates a jep interpreter, runs the py constraint script, and obtains the prompt information and returns it to the web development interface for reminder. After the verification is completed, the error information is sorted and stored in noticeParams. The web development interface accurately locates the page field according to the error field name in noticeParams, displays the error prompt information below the configuration item, and displays it in red font on all user operation interfaces, so that users can detect and correct it in time.

[0036] The validation types are divided into three categories: automatic calculation, parameter disabling, and checkbox disabling. Each uses calcParams, forbidParams, and forbidCheckParams in the form of key-value pairs to implement data binding and constraint prompt functions. In the automatic calculation type, the relevant calculation rules, associated fields and other information are stored in calcParams as key-value pairs to ensure automatic and accurate calculation of the fields; when parameters are disabled, the disabled parameters and conditions are stored in forbidParams to avoid misoperation; when checkboxes are disabled, the relevant checkbox states and rules are stored in forbidCheckParams as key-value pairs to standardize checkbox operations and ensure data accuracy and reasonable page interaction.

[0037] 4. Entry reminder: real-time reminder for users entering the same module during collaborative development In the process of collaborative development, different users usually develop different modules. When they need to view or edit configuration items of other modules under special conditions, all users in the current module are reminded in real time which members are in the module to prevent unnecessary conflicts. When users find that the configuration items have changed, they can trace back which member made the change through historical operation records to reduce the review process.

[0038] 5. Collaborative development completed When all users complete their respective modules according to the information prompts, the project can pass all specification verifications. All participating users will receive a prompt that the verification configuration is successful, and the code file can be generated, and the entire project configuration is completed.

[0039] The present invention has the following technical features / advantages: 1. The AUTOSAR basic configuration tool brings many benefits to the collaborative development environment, which not only improves development efficiency, but also enhances the quality and reliability of the software system. The AUTOSAR configuration tool supports modular design, and each module has clearly defined interfaces and functions. This design allows modules to be developed and tested independently.

[0040] 2. Introduce the Web architecture and account concepts to achieve data interoperability between accounts. Module files are plug-in-based, and the module configuration visualization interface is realized by reading module files. The effect of real-time constraint reminders is achieved during the configuration process, improving development efficiency. At the same time, through the association relationship between the parameters set by the constraint file, the associated data is updated synchronously, thereby accelerating the development process of the entire project.

[0041] 3. Avoid development conflicts, module constraint file parsing and real-time synchronization In parallel development, module constraint file parsing technology is particularly important. By automatically reading and parsing the constraint file, the system can intelligently identify the configuration requirements and dependencies of different modules. Developers can work in parallel between different modules, and the system will effectively avoid and resolve potential configuration conflicts based on the rules of the constraint file.

[0042] For example, if two developers try to modify the parameters of the same module at the same time, the system will promptly detect and notify them of conflicts, thus ensuring that each configuration modification complies with the project's constraints. This intelligent parsing and verification mechanism greatly reduces human intervention in the development process and the workload of later conflict handling.

[0043] 4. In terms of configuration synchronization: When a developer modifies the parameters of a module, whether it is a parameter change or a module configuration change, all connected clients can obtain these changes with a millisecond delay, ensuring that every member of the team can synchronize project progress in real time.

[0044] Team members can then synchronize their work status with each other, avoiding errors and misoperations caused by information lags or configuration conflicts. This efficient synchronization mechanism not only improves development efficiency, but also ensures the consistency and stability of the entire project.

[0045] 5. AUTOSAR configuration tools are usually used in conjunction with a series of integrated tool chains that cover the entire process from design, configuration to verification. In a collaborative development environment, developers can add comments to parameters based on actual configuration conditions, which is more conducive to communication and understanding of the configuration among team members. The configuration page displays the current module configuration personnel in real time, which can effectively reduce the error rate caused by multiple configurations.

[0046] In one embodiment, the present invention provides a computer program product, including a computer program or instructions, characterized in that when the computer program or instructions are executed by a processor, the steps of a multi-user collaborative development method based on the EasySAR configuration tool are implemented.

[0047] In one embodiment, the present invention provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of a multi-user collaborative development method based on the EasySAR configuration tool.

[0048] The above description is only an embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention. < / containers>

Claims

1. A multi-user collaborative development method based on EasySAR configuration tool, characterized in that: include: S1. Create a project group in the EasySAR configuration tool. The project group information includes the project group invitation link, expiration time, invitation password, and bind the user information and project group to limit the authority of project-related information to the project group; S2. Users in the project group create projects one by one, and each user selectively shares the data information of their own project. After creating a project, they obtain the web development interface corresponding to the project, configure the project on the web development interface, and perform constraint verification reminders in real time during the configuration process. Configuration items between projects of different users are associated and synchronized; S3. When all participating members in the project team receive the prompt that the verification configuration is successful, the code file is generated to complete the entire project configuration.

2. The multi-user collaborative development method based on the EasySAR configuration tool according to claim 1, characterized in that: The EasySAR configuration tool consists of the following parts: a web development interface front end built by the vue front-end architecture, a java back end built by the springboot architecture, and a module package. The module package includes a view model, a constraint verification script, and a code generation template; the Java backend has a built-in JAXB file for mapping the XML view model to a Java object and returning a format file agreed upon by the web development interface to generate a development interface; the Java backend has a built-in jep interpreter for calling the constraint verification script and returning the verification result to the front-end page for display; the code generation module is used to generate a code file for the web development interface that has successfully verified the configuration; The Java backend also has a built-in data processing module for storing the data configured in the web development interface after processing, and all data information is stored in the same location.

3. The multi-user collaborative development method based on the EasySAR configuration tool according to claim 1, characterized in that: Step S2 also includes receiving another user configuration information on the user's web development interface.

4. The multi-user collaborative development method based on the EasySAR configuration tool according to claim 1, characterized in that: Receiving another user's configuration information on the user's web development interface includes: if the configuration of another user is inaccurate, prompting the web development interface with relevant information; and giving real-time reminders to users entering the same module.

5. The multi-user collaborative development method based on the EasySAR configuration tool according to claim 1, characterized in that: Step S2 also includes recording historical operations of changes in configuration items of the project to trace the changes in configuration items.

6. The multi-user collaborative development method based on the EasySAR configuration tool according to claim 1, characterized in that: When developing a project, users can also use it to annotate parameter configuration items and / or take notes on the project.

7. The multi-user collaborative development method based on the EasySAR configuration tool according to claim 1, characterized in that: The verification includes: When you open a container or operate a corresponding field in the web development interface, the backend performs validation through the validatePython interface; In the collaborative development process, the information data configured by all members of the project team are stored in the same location. The data information that needs to be verified comes from everyone. After specifying the module and parameter method, the backend generates a jep interpreter, runs the py constraint script, and obtains prompt information and returns it to the web development interface for reminders. After the verification is completed, the error information is sorted and stored in noticeParams; The web development interface accurately locates the page field based on the error field name in noticeParams and displays the error prompt information below the configuration item.

8. The multi-user collaborative development method based on the EasySAR configuration tool according to claim 1, characterized in that: When a developer enters the module interface where other developers are located, the system instantly broadcasts this information through the WebSocket channel to inform the user of the current page.

9. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the multi-user collaborative development method based on the EasySAR configuration tool according to any one of claims 1 to 9 are implemented.

10. A computer device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the steps of the multi-user collaborative development method based on the EasySAR configuration tool according to any one of claims 1 to 8.

Images