Software development method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a software development method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining a software development demand; determining a demand list and a parameter configuration template according to software development demands; mapping the demand list into a parameter configuration template to obtain a target configuration file; and inputting the target configuration file into a preset generation component to generate a target code. The technical problem that in the vehicle-mounted software development process, due to the fact that the accuracy and efficiency of configuration of the AUTOSAR CP tool chain are low, the development efficiency and quality of the vehicle-mounted software are low is solved.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of software development, and in particular, to a software development method, apparatus, electronic device, and storage medium. Background Art

[0002] In the field of in-vehicle ECU (Electronic Control Unit) software development, the toolchain configuration under the AUTOSAR CP (Automotive Open System Architecture Classic Platform) architecture is the basis for the efficient and stable operation of in-vehicle systems. With the advancement of vehicle intelligence, the iterative update speed of in-vehicle software has accelerated, posing higher requirements for the efficiency and quality of software development.

[0003] However, the current AUTOSAR CP toolchain configuration process still highly relies on manual operations. It is necessary to manually analyze system requirements and perform configurations. This process is not only time-consuming but also likely to affect software quality due to deviations in requirement understanding or parameter configuration errors. Existing solutions include: writing automated configuration scripts using scripting languages (such as Python, Shell). These scripts can parse requirement documents and generate ARXML files according to predefined rules. However, this method requires engineers to have high scripting skills, and when requirements or the AUTOSAR CP architecture change, the maintenance and update costs of the scripts are relatively high; adopting specialized configuration management software or tools. These tools provide graphical user interfaces for easy parameter configuration. However, for large-scale or complex systems, such a configuration method is inefficient and it is difficult to avoid understanding deviations and configuration omissions during manual configuration; using artificial intelligence technologies, such as machine learning models, to automatically analyze requirement documents and match corresponding configuration parameters. This method can theoretically improve the degree of configuration automation. However, in practice, due to the certain deterministic relationship between AUTOSAR CP configuration parameters and requirement items, the training and maintenance costs of the AI model are high, and when requirement items are added or modified, the model needs to be adjusted accordingly, and the operation is complex. In summary, although existing methods have alleviated the pressure of manual configuration to a certain extent, there are still deficiencies in terms of requirement diversity, configuration complexity, and efficiency improvement, and it is difficult to meet the growing requirements for automated, efficient, and accurate configuration in in-vehicle ECU software development.

[0004] Therefore, in the process of in-vehicle software development, how to improve the degree of automation, accuracy, and efficiency of AUTOSAR CP toolchain configuration, and thus improve the development efficiency and quality of in-vehicle software is one of the important technical problems in the related technical fields. For the above problems, no effective solutions have been proposed yet. Summary of the Invention

[0005] An embodiment of the present application provides a software development method, apparatus, electronic device, and storage medium, aiming to improve the problem that in the process of in-vehicle software development, due to the low accuracy and efficiency of AUTOSAR CP toolchain configuration, the development efficiency and quality of in-vehicle software are low.

[0006] According to one aspect of the embodiments of the present application, a software development method is provided, including: obtaining software development requirements; determining a requirements list and a parameter configuration template according to the software development requirements; mapping the requirements list to the parameter configuration template to obtain a target configuration file; and inputting the target configuration file into a preset generation component to generate target code.

[0007] The software development method provided by the embodiments of the present application achieves the following technical effects: First, by obtaining software development requirements, it ensures that subsequent development work is oriented towards actual requirements, avoiding the disconnection between toolchain configuration and actual requirements; Second, converting requirements into a specific requirements list clarifies the specific goals and requirements of software development, helps to clearly understand software requirements, reduces uncertainty in the development process, and determining the parameter configuration template realizes the standardization of configuration parameters, ensuring the consistency and standardization of configuration parameters. By determining the requirements list and parameter configuration template based on requirements, the automation and standardization of the configuration process are realized, improving the efficiency and accuracy of configuration; In addition, mapping the requirements list to the parameter configuration template to obtain a target configuration file further converts requirements into configuration parameters through automated means, greatly improving the generation efficiency of the configuration file, reducing the complexity and time consumption of manual configuration, and providing key support for the efficient development of in-vehicle software; And inputting the target configuration file into a preset generation component to generate target code completes the automated conversion from requirements to software implementation, significantly simplifies the software development process, avoids the repetitive labor and possible errors of manual code writing, and ensures the standardization and high quality of code generation, thereby greatly improving the development efficiency and quality of in-vehicle software. Thus, the embodiments of the present application can achieve the technical effect of improving the development efficiency and quality of in-vehicle software by improving the accuracy and efficiency of AUTOSAR CP toolchain configuration in the process of in-vehicle software development, and solve the technical problem that in the process of in-vehicle software development, due to the low accuracy and efficiency of AUTOSAR CP toolchain configuration, the development efficiency and quality of in-vehicle software are low.

[0008] Optionally, determining the requirements list according to the software development requirements includes: determining a requirements description file according to the software development requirements, where the requirements description file is a standardized document for recording software development requirements; and determining the requirements list according to the requirements description file, where the requirements list is a requirements list for guiding parameter configuration.

[0009] The above optional embodiments of the present application can achieve the following technical effects: According to the software development requirements, a requirements description file is determined, realizing the standardized recording of requirements. As a standardized document for recording software development requirements, the requirements description file can ensure that all relevant parties have a common understanding and interpretation of the requirements, avoiding requirement understanding deviations, and providing a clear and accurate requirement basis for subsequent development work; According to the requirements description file, a requirements list is determined. This process further transforms the requirements into a specific and operable requirements list, and the requirements list can clearly list each requirement to be configured in software development, providing precise guidance for parameter configuration. In summary, through the standardized requirements description file and the specific requirements list, the clear, structured, and precise expression of software development requirements is achieved, significantly improving the accuracy and efficiency of requirement analysis and configuration parameter matching in in-vehicle software development.

[0010] Optionally, determining the requirements description file according to the software development requirements includes: parsing the software development requirements to generate multiple requirement items based on a target format; constructing a requirements table as the requirements description file according to the multiple requirement items.

[0011] The above optional embodiments of the present application can achieve the following technical effects: Parsing the software development requirements to generate multiple requirement items based on a target format transforms the vague and unstructured requirement information into a clear and structured format, ensuring that each requirement is accurately identified. The generated requirement items not only have a unified form for subsequent processing but also have clear content, helping to reduce understanding deviations; Constructing a requirements table as the requirements description file according to the generated multiple requirement items realizes the standardized and systematic recording of requirement information. The requirements table not only provides an intuitive display of the requirement items but also facilitates the comparison between requirement items and the tracking management of requirements. In the form of a table, specific requirements can be quickly located to ensure that each requirement is fully considered during the configuration process, avoiding configuration omissions. At the same time, it is convenient for developers and managers to effectively control requirement changes, reducing project delays and cost increases caused by unclear requirements or frequent changes. In summary, through generating structured requirement items and constructing a requirements table, the accurate parsing and standardized recording of in-vehicle software development requirements are achieved, helping to improve the efficiency and accuracy of requirement management, reducing requirement understanding deviations, and providing clear and systematic requirement guidance for the automated mapping of configuration parameters.

[0012] Optionally, determining the requirements description file according to the software development requirements includes: performing a correctness check on the software development requirements according to a preset check rule to obtain a correctness check result, where the correctness check includes information integrity check and information consistency check; in response to the correctness check result indicating that the software development requirements pass the check, determining the requirements description file.

[0013] The above optional embodiments of the present application can achieve the following technical effects: By performing correctness verification on software development requirements according to preset verification rules, the integrity and consistency of requirement information are ensured, the uncertainties in the configuration or development process caused by missing requirement information are avoided, and at the same time, the conflicts caused by inconsistent requirement descriptions of configuration parameters in different modules are avoided; In response to the result of the correctness verification indicating that the software development requirements pass the verification, a requirement description file is determined. This process ensures that only verified and error-free requirement information can be used for subsequent configuration and development work. Through this verification mechanism, errors in requirements can be discovered and corrected in advance, and the ineffective work based on incorrect requirements can be avoided, thereby improving the overall development efficiency. In summary, by introducing a requirement correctness verification mechanism, including the verification of information integrity and consistency, the accuracy of in-vehicle software development requirements is ensured.

[0014] Optionally, determining the requirement list according to the requirement description file includes: determining a preset generation component associated with the requirement item to obtain a component to be configured, where the requirement item is included in the requirement description file; constructing a requirement list according to the requirement item and the component to be configured.

[0015] The above optional embodiments of the present application can achieve the following technical effects: Determining a preset generation component associated with the requirement item to obtain a component to be configured, this process establishes a clear association between the requirement item and the specific generation component, ensuring that each requirement can directly point to the software component that needs to be configured or generated. Through this association, the deviation in the understanding of requirements during the configuration process can be avoided, ensuring that the configuration work closely corresponds to the requirement items in the requirement description file, reducing configuration errors and omissions, and improving the accuracy and pertinence of configuration; Constructing a requirement list according to the requirement item and the component to be configured, the requirement list not only lists all requirement items but also clearly defines the component to be configured corresponding to each requirement item, providing clear configuration guidance. The construction of the requirement list makes the configuration work no longer rely on the subjective understanding and memory of developers about requirements, but is based on documented and structured information, greatly improving the efficiency of the configuration work, and at the same time reducing human errors during the configuration process, ensuring the consistency between configuration and requirements. In summary, by establishing the association between requirement items and preset generation components and constructing a requirement list based on this association, the precise matching of requirements and component configuration in in-vehicle software development is achieved.

[0016] Optionally, determining the parameter configuration template according to the software development requirements includes: determining a parameter configuration template corresponding to the component to be configured from a preset template library according to the component to be configured.

[0017] The above optional embodiments of the present application can achieve the following technical effects: Selecting a parameter configuration template according to the component to be configured realizes the precise matching of the components listed in the requirement description file with the configuration templates in the preset template library, ensuring the pertinence and standardization of the configuration work. For each component to be configured, instead of analyzing and setting parameters from scratch, the preset template related to the component can be directly used, greatly reducing the time for parameter analysis and configuration and lowering the complexity of the configuration.

[0018] Optionally, mapping the requirement list to the parameter configuration template to obtain the target configuration file includes: constructing the mapping relationship between the items in the requirement list and the parameters in the parameter configuration template; according to the mapping relationship, mapping the items in the requirement list to the parameters in the parameter configuration template to obtain dynamic configuration items; determining the target configuration file according to the dynamic configuration items and the static configuration items, where the static configuration items are preset configuration items.

[0019] The above optional embodiments of the present application can achieve the following technical effects: Constructing the mapping relationship between the items in the requirement list and the parameters in the parameter configuration template transforms the requirement list into a direct guide for configuration parameters. Through the clear mapping relationship, it ensures that each requirement can be accurately corresponded to a specific parameter in the parameter configuration template, avoiding misalignment or omission between the configuration parameters and the requirements, and improving the accuracy and pertinence of the configuration; according to the mapping relationship, mapping the items in the requirement list to the parameters in the parameter configuration template to obtain dynamic configuration items, this process realizes requirement-driven parameter configuration. By automatically converting requirements into parameters, it reduces the burden of manual configuration, avoids human errors, enables the parameter configuration to quickly respond to requirement changes, and improves the flexibility and speed of the configuration; according to the dynamic configuration items and the static configuration items, a complete target configuration file can be constructed. This process realizes the automation of parameter configuration and also ensures the comprehensiveness and stability of the configuration file. In summary, by constructing the mapping relationship between the items and the parameters, transforming the items in the requirement list into dynamic configuration items in the parameter configuration template, and combining with the static configuration items to determine the target configuration file, the precision, automation, and efficiency of parameter configuration in in-vehicle software development are realized.

[0020] Optionally, determining the requirement list according to the requirement description file includes: determining the priorities corresponding to multiple requirement items in the requirement description file according to the requirement description file and the preset priority rules; sorting the multiple requirement items according to the priorities to obtain ordered requirement items; determining the requirement list according to the ordered requirement items.

[0021] The above optional embodiments of the present application can achieve the following technical effects: determining the priority of requirement items according to the requirement description file and the preset priority rules ensures that critical requirements can be processed first. Through the preset priority rules, it is possible to quickly identify which requirements are core and which are auxiliary, so that under limited development resources, functions that have the greatest impact on system performance or user experience can be preferentially configured and developed, avoiding waste of resources and blindness in development, and improving the rationality of resource allocation; sorting multiple requirement items according to their priorities to obtain ordered requirement items, and the ordered arrangement of requirement items provides a clear execution path for development and configuration work, improving the systematicness and efficiency of development work; determining a requirement list according to the ordered requirement items, and the establishment of the requirement list enables configuration and development to be carried out in the order of priorities, effectively controlling the project progress and avoiding delays caused by improper processing order of requirements. In summary, through the process of determining the priority of requirement items, sorting, and generating a requirement list based on the ordered requirement items, the priority management of requirements and the reasonable allocation of resources in in-vehicle software development are achieved.

[0022] According to another aspect of the embodiments of the present application, there is also provided a software development device, including: an acquisition module for acquiring software development requirements; a determination module for determining a requirement list and a parameter configuration template according to the software development requirements; a mapping module for mapping the requirement list into the parameter configuration template to obtain a target configuration file; a generation module for inputting the target configuration file into a preset generation component to generate target code.

[0023] The development device of the above software provided by the embodiments of the present application achieves the following technical effects: The acquisition module is used to acquire software development requirements, ensuring that the starting point of software development is based on accurate requirement information and avoiding subsequent development problems caused by deviation in requirement understanding or incomplete requirement collection; the determination module is used to determine a requirement list and a parameter configuration template according to the software development requirements. The determination of the requirement list clarifies the specific objectives and contents of software development, and the parameter configuration template is a standardized guide for configuration work, ensuring that developers can complete parameter configuration quickly and accurately, avoiding subjective errors in the configuration process, and improving the efficiency and accuracy of the configuration work; the mapping module maps the requirement list into the parameter configuration template to obtain a target configuration file, realizing requirement-driven parameter configuration, ensuring a high degree of consistency between the configuration parameters and business requirements, reducing redundancy and errors in the configuration process, and improving the generation efficiency and quality of the configuration file; the generation module is used to input the target configuration file into a preset generation component to generate target code. The existence of the generation module reduces the workload of manual coding and improves the efficiency and quality of code generation. In summary, the development device of the software disclosed in the present application, through the organic combination of the acquisition module, the determination module, the mapping module and the generation module, realizes the technical effect of improving the development efficiency and quality of in-vehicle software by improving the accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process, and solves the technical problem that the development efficiency and quality of in-vehicle software are low due to the low accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process.

[0024] According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a processor and a memory. Among them, the memory is used to store a computer program; the processor is used to execute the program stored on the memory to implement the software development method in any one of the above.

[0025] The above electronic device provided by the embodiments of the present application achieves the following technical effects: Storing the computer program corresponding to the software development method in any one of the above in the memory and using the processor to execute the computer program stored on the memory realizes the technical effect of improving the development efficiency and quality of in-vehicle software by improving the accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process, and solves the technical problem that the development efficiency and quality of in-vehicle software are low due to the low accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process.

[0026] According to another aspect of the embodiments of the present application, there is also provided a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the software development method in any one of the above is implemented.

[0027] The computer-readable storage medium provided by the embodiment of the present application achieves the following technical effects: storing the computer program corresponding to the software development method for implementing any one of the above in the computer-readable storage medium, and using the processor to execute the computer program stored in the computer-readable storage medium, achieving the technical effect of improving the development efficiency and quality of in-vehicle software by improving the accuracy and efficiency of the AUTOSAR CP toolchain configuration during the in-vehicle software development process, and solving the technical problem that the development efficiency and quality of in-vehicle software are low due to the low accuracy and efficiency of the AUTOSAR CP toolchain configuration during the in-vehicle software development process.

[0028] It should be noted that the general description and the detailed description hereinafter in the above content are only for exemplifying and explaining the present application, and do not constitute a limitation to the present application. Description of the Drawings

[0029] Figure 1 is a flowchart of the software development method provided by one embodiment of the present application;

[0030] Figure 2 is a schematic structural diagram of the in-vehicle software development method provided by one embodiment of the present application;

[0031] Figure 3 is a structural diagram of the software development device provided by one embodiment of the present application;

[0032] Figure 4 is a structural diagram of the electronic device provided by one embodiment of the present application. Detailed Embodiments

[0033] In order to make the technical problems, technical solutions and beneficial effects solved by the present application clearer and more understandable, the present application will be further described in detail below in conjunction with embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0034] It should be noted that the terms "first", "second", etc. in the specification, claims and drawings of the present application are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0035] According to an embodiment of the present invention, an embodiment of a software development method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0036] A software development method provided by an embodiment of the present application includes: obtaining software development requirements; determining a requirements list and a parameter configuration template according to the software development requirements; mapping the requirements list to the parameter configuration template to obtain a target configuration file; and inputting the target configuration file into a preset generation component to generate target code.

[0037] The software development method provided by the embodiment of the present application achieves the following technical effects: First, by obtaining software development requirements, it ensures that subsequent development work is guided by actual requirements, avoiding the disconnection between tool chain configuration and actual requirements; Second, converting requirements into a specific requirements list clarifies the specific goals and requirements of software development, helps to clearly understand software requirements, reduces uncertainty in the development process, and determining the parameter configuration template realizes the standardization of configuration parameters, ensuring the consistency and standardization of configuration parameters. By determining the requirements list and parameter configuration template based on requirements, the automation and standardization of the configuration process are realized, improving the efficiency and accuracy of configuration; In addition, mapping the requirements list to the parameter configuration template to obtain a target configuration file further converts requirements into configuration parameters through automated means, greatly improving the generation efficiency of the configuration file, reducing the complexity and time consumption of manual configuration, and providing key support for the efficient development of in-vehicle software; And inputting the target configuration file into a preset generation component to generate target code completes the automated conversion from requirements to software implementation, significantly simplifies the software development process, avoids the repetitive labor and possible errors of manual code writing, and ensures the standardization and high quality of code generation, thereby greatly improving the development efficiency and quality of in-vehicle software. Thus, the embodiment of the present application can achieve the technical effect of improving the development efficiency and quality of in-vehicle software by improving the accuracy and efficiency of AUTOSAR CP tool chain configuration during the in-vehicle software development process, and solves the technical problem that the development efficiency and quality of in-vehicle software are low due to the low accuracy and efficiency of AUTOSAR CP tool chain configuration during the in-vehicle software development process.

[0038] Embodiment 1

[0039] An embodiment of the present application provides a software development method. Please refer to Figure 1 , including the following steps:

[0040] S110: Obtain software development requirements;

[0041] Specifically, in the initial stage of software development, software development requirements are collected through various channels. These requirements can come from customers, market research, internal requirement change orders, etc., covering various aspects such as software functions, performance, security, and user experience.

[0042] A standardized requirement acquisition process can ensure that all requirements are recorded and used as the basis for development, avoiding requirement omissions, reducing rework in subsequent development stages, improving development efficiency, and making requirement management more systematic and transparent.

[0043] S120: Determine the requirement list and parameter configuration template according to the software development requirements;

[0044] Specifically, after collecting software requirements, analyze the software development requirements, break them down into a specific requirement list, and at the same time, select a suitable parameter configuration template according to the matching results between the requirement list and relevant modules in the AUTOSAR CP architecture. Each parameter configuration template contains all configuration parameters related to a specific function or requirement, as well as the dependency relationships and configuration rules between the parameters.

[0045] It should be noted that the AUTOSAR CP architecture is a standard software architecture designed for automotive electronic control units, aiming to improve the reusability, portability, and maintainability of automotive software. It consists of a series of basic software modules, runtime environments, and development toolchains, providing a unified interface and standardized design methods for in-vehicle software.

[0046] It can be understood that through the determination of the requirement list and parameter configuration template, the accurate matching of requirements and configuration parameters is achieved, improving the accuracy and efficiency of configuration. At the same time, the preset parameter configuration template reduces the subjectivity of manual analysis and configuration, reduces the risk of configuration errors, and improves the stability and reliability of the software.

[0047] S130: Map the requirement list into the parameter configuration template to obtain the target configuration file;

[0048] Specifically, map each requirement in the requirement list accurately to the corresponding configuration parameters in the parameter configuration template to form a complete target configuration file. This process involves the calculation of parameter values, the generation of parameter combinations, the verification of parameter dependency relationships, etc.

[0049] It can be understood that the mapping of the requirement list and the parameter configuration template realizes the direct conversion of requirements to configuration parameters, ensuring a high degree of consistency between the configuration parameters and business requirements. This automated process effectively improves the generation efficiency of the configuration file, reduces manual configuration errors, and provides accurate guidance for subsequent code generation.

[0050] S140: Input the target configuration file into a preset generation component to generate target code.

[0051] Specifically, input the target configuration file into a preset generation component, and through the preset generation component (such as the code generation tool in the AUTOSAR CP toolchain), it is automatically converted into executable software code. The code generation component needs to have specific parsing capabilities and generation logic, and can generate corresponding functional code according to the parameters in the configuration file.

[0052] It can be understood that automated code generation significantly improves development efficiency, reduces errors in manual coding, and ensures code consistency and quality. This process lowers the development threshold, enabling the development team to focus more on the implementation of business logic and innovative functions, and accelerating the listing and iteration speed of software products.

[0053] In summary, the software development method provided in this application includes: obtaining software development requirements; determining a requirements list and a parameter configuration template according to the software development requirements; mapping the requirements list to the parameter configuration template to obtain a target configuration file; inputting the target configuration file into a preset generation component to generate target code. By using the above method, it is possible to achieve the technical effect of improving the development efficiency and quality of in-vehicle software by improving the accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process, and solve the technical problem that the development efficiency and quality of in-vehicle software are low due to the low accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process.

[0054] Optionally, in the above step S120, determining the requirements list according to the software development requirements includes the following steps:

[0055] S121, determine a requirements description file according to the software development requirements, where the requirements description file is a standardized document for recording the software development requirements;

[0056] Specifically, convert unstructured software development requirement information into a structured and standardized requirements description file, which details key information such as the description, parameters, priorities, and dependencies of each requirement to ensure that all requirements are clearly and consistently recorded.

[0057] It can be understood that using a standardized requirements description file format not only facilitates the collation and storage of requirement information, but also enables subsequent automated configuration systems to read and parse it. The use of standardized documents reduces requirement understanding deviations, avoids repetitive labor and resource waste during requirement processing, ensures requirement integrity, and improves requirement management efficiency.

[0058] S122. Determine a requirements list according to the requirements description document, where the requirements list is a requirements list for guiding parameter configuration.

[0059] Specifically, read the requirements description document, parse the requirements information therein, and convert it into a specific requirements list. This list clarifies the various functions and performance indicators to be implemented, as well as which modules and configuration parameters in the AUTOSAR CP architecture these requirements correspond to. The requirements list is the direct basis for subsequent parameter configuration and is also a key input to the automated configuration system.

[0060] It can be understood that the generation of the requirements list ensures the direct correspondence between requirements and module configurations in the AUTOSAR CP architecture, avoiding the disconnection between requirements and configurations. By converting requirements into specific parameter configuration items, the accuracy of parameter configuration is improved. At the same time, it provides clear guidance for subsequent automated configuration, reduces configuration errors, and speeds up the parameter configuration process.

[0061] Optionally, according to software development requirements, determining the requirements description document includes the following steps:

[0062] S123. Parse the software development requirements to generate multiple requirement items based on the target format;

[0063] Specifically, in the requirements input stage, software development requirements exist in various unstructured forms, such as natural language descriptions, emails, meeting minutes, etc. To ensure the efficient operation of the subsequent automated configuration system, the software development requirements are converted into multiple requirement items that meet the target format.

[0064] Specifically, first parse the software development requirements to identify the key elements of the requirements, such as function descriptions, performance indicators, interface requirements, security considerations, etc., and then convert these key elements into a set of requirement items based on a specific target format. The target format is usually a predefined format that can be directly read and processed by the automated configuration system, such as XML, JSON, or a specific database table structure.

[0065] By parsing the requirements and generating requirement items based on the target format, the compatibility and consistency problems caused by the diverse requirement input formats in the prior art are overcome. The standardized requirement item format enables subsequent steps such as requirement management, requirement analysis, and parameter configuration to be automated, improving the efficiency and accuracy of requirement processing and reducing misunderstandings and errors caused by inconsistent requirement formats.

[0066] S124. Construct a requirements table as the requirements description document according to the multiple requirement items.

[0067] Specifically, after generating the requirement items based on the target format, these requirement items are organized into a requirement table to form a complete requirement description file.

[0068] Specifically, the requirement table is a structured data set. Each row represents a requirement item, and each column represents the characteristics of the requirement item, such as requirement ID, description, type, priority, associated module, parameter requirements, etc. In this way, the requirement description file not only contains the detailed information of the requirements, but also provides the relevance and priority information between the requirements, facilitating the subsequent analysis and processing of requirements by the automated configuration system.

[0069] It can be understood that constructing the requirement items into a requirement table not only realizes the structured storage of the requirements, but also provides a visual display of the requirements, enabling requirement analysts to understand and process the requirements more intuitively and quickly. The standardized format of the requirement description file also facilitates seamless docking with the automated configuration system of the AUTOSAR CP tool chain, reducing manual intervention and improving the efficiency of automated configuration.

[0070] Optionally, according to the software development requirements, determining that the requirement description file further includes the following steps:

[0071] S125, perform a correctness check on the software development requirements according to the preset verification rules to obtain a correctness check result, where the correctness check includes information integrity check and information consistency check;

[0072] Specifically, before the requirements are input and parsed into requirement items based on the target format, a thorough correctness check is performed on the software development requirements according to the preset verification rules. This verification process includes information integrity check and information consistency check.

[0073] Specifically, the information integrity check refers to checking whether the software development requirements contain all necessary information. For example, whether a requirement item clearly defines its function description, performance indicators, interface requirements, security considerations, etc. If any key information is missing from the requirements, the system will not be able to generate a complete and accurate requirement description file. Therefore, the purpose of this verification is to ensure that the requirement description is comprehensive enough to avoid understanding deviations or configuration errors caused by missing information in the subsequent development stage.

[0074] Specifically, the information consistency check refers to checking whether there are logical conflicts or inconsistencies between the requirement information. For example, two requirement items respectively require different performance standards for the same function, or the interface requirements proposed by a requirement item do not conform to the specifications of the AUTOSAR CP architecture. The purpose of the information consistency check is to ensure that all requirement items can work together without causing technical contradictions or obstacles during the implementation process.

[0075] It can be understood that through pre-verification before the requirements are transformed into requirement description files, incomplete and inconsistent problems in the requirements can be detected and processed early, avoiding a large amount of rework caused by requirement errors in the later development.

[0076] S126, in response to the correctness verification result indicating that the software development requirement verification passes, determine the requirement description file.

[0077] Specifically, when the correctness verification result indicates that the description of the software development requirement is complete and consistent, the system continues to generate the requirement description file. This process ensures that only high-quality development requirement information can be further processed, avoiding the impact of low-quality requirements on the subsequent development process.

[0078] It can be understood that by ensuring that only the development requirements that pass the verification can be determined as the requirement description file, this process raises the quality threshold of the development requirements, reducing various problems caused by insufficient requirement quality in the subsequent development, such as development deviation, function redundancy, or performance conflict, etc.

[0079] Optionally, determining the requirement list according to the requirement description file includes:

[0080] S127, determine the preset generation components associated with the requirement items to obtain the components to be configured, where the requirement items are included in the requirement description file;

[0081] Specifically, after the requirement description file is determined, identify the preset generation components associated with the requirement items, so as to determine the components to be configured, such as the components in the AUTOSAR CP architecture that need to be configured.

[0082] Optionally, the preset generation components are a set of component templates preset according to the AUTOSAR CP architecture specification, and each component template corresponds to one or more functional modules in AUTOSAR CP, such as security modules, communication modules, storage modules, etc. By analyzing the requirement items in the requirement description file, identify which functional modules are mentioned or implied by the requirement items, and then according to the preset mapping relationship between the components and the functional modules, find the preset generation components most directly related to the requirement items, and further determine the list of components to be configured.

[0083] It can be understood that through the association between the requirement items and the preset generation components, an accurate mapping from non-technical requirement descriptions to technical component configurations is achieved. This process avoids subjective judgments and understanding deviations between requirements and technical implementations in traditional software development, improving the accuracy and efficiency of the conversion from requirements to technical components. Determining the components to be configured ensures the pertinence of the subsequent parameter configuration work, avoiding ineffective configuration of irrelevant components, and saving development resources and time.

[0084] S128. Build a requirements list based on the requirement items and components to be configured.

[0085] Specifically, after determining the components to be configured, a requirements list is built. This list will detail the parameter items that need to be adjusted or set in each component to be configured, as well as information such as the value range, default value, and priority of the parameter items. Based on the requirement items in the requirement description file and combined with the parameter configuration rules of the components to be configured, a requirements list is generated. Each requirement item corresponds to a specific technical parameter in the list, such as a function switch, performance threshold, security level, etc. These parameters will be used to guide subsequent parameter configuration.

[0086] It can be understood that building the requirements list provides clear guidance for the parameter configuration work. The generation of the requirements list further reduces the manual configuration work in software development, improves the efficiency of automated configuration, and ensures the consistency and accuracy of the configuration parameters with the business requirements.

[0087] Optionally, according to the software development requirements, determining the parameter configuration template includes: determining the parameter configuration template corresponding to the component to be configured from the preset template library according to the component to be configured.

[0088] Specifically, after determining the requirements list, according to the components to be configured listed in the requirements list, select the parameter configuration templates corresponding to these components from the preset template library. The preset template library is one of the core components of the automated configuration system. It contains the parameter configuration templates of all components under the AUTOSAR CP architecture, and each template is pre-designed and customized according to the AUTOSAR CP architecture specification.

[0089] Optionally, the parameter configuration templates in the template library not only contain all the parameters of the component, but also preset the default value, value range, priority of the parameters, and the dependency relationships between the parameters. This makes the template not only able to guide parameter configuration, but also can be used as the basic framework for parameter configuration to ensure the correctness and consistency of the configuration.

[0090] It can be understood that by selecting the parameter configuration templates from the preset template library, it is possible to quickly and accurately provide guidance for parameter configuration of the components to be configured, avoiding the cumbersome and error-prone problems of manual parameter configuration in traditional software development. Especially for complex components with numerous parameters, manual configuration is not only time-consuming and laborious, but also prone to configuration deviations or omissions. The use of parameter configuration templates not only simplifies the configuration process, but also ensures the standardization and quality of the configuration results. In addition, the existence of the template library enables the automated configuration system to handle a wide range of AUTOSAR CP components, improving the versatility and adaptability of the system, and also simplifying the maintenance work when adding new components or changing component parameters.

[0091] Optionally, mapping the requirement list to the parameter configuration template to obtain the target configuration file includes the following steps:

[0092] S131, construct the mapping relationship between the item in the requirement list and the parameter item in the parameter configuration template;

[0093] Specifically, construct the mapping relationship between the item in the requirement list and the parameter item in the parameter configuration template, and establish the direct association between the requirement item in the requirement list and the specific parameter in the parameter configuration template.

[0094] It can be understood that by constructing the mapping relationship, the accurate conversion from the requirement item to the specific parameter item is realized, reducing the uncertainty and subjectivity of parameter configuration.

[0095] S132, according to the mapping relationship, map the item in the requirement list to the parameter item in the parameter configuration template to obtain the dynamic configuration item;

[0096] Specifically, on the basis of establishing the mapping relationship, according to the specific requirement item in the requirement list, dynamically adjust the parameter item in the parameter configuration template to obtain the dynamic configuration item.

[0097] Specifically, the dynamic configuration item refers to those parameter items whose values need to be adjusted according to the specific requirement item, and the values of these parameter items will be directly determined by the requirement item in the requirement list. For example, for the parameter item of "start time threshold", if the requirement list requires that "the vehicle remote start function needs to complete the start preparation within 30 seconds", then the dynamic configuration value of "start time threshold" will be set to 30 seconds.

[0098] It can be understood that by dynamically adjusting the parameter item in the parameter configuration template, the personalization and customization of parameter configuration are realized, meeting the specific configuration requirements of different business needs. The generation of dynamic configuration items not only improves the flexibility and adaptability of parameter configuration, but also ensures the tight coupling between the configuration parameters and business requirements, avoiding the disconnection between the configuration parameters and requirements.

[0099] S133, determine the target configuration file according to the dynamic configuration item and the static configuration item, where the static configuration item is a preset configuration item.

[0100] Specifically, the generation of the target configuration file is based on the integration of the dynamic configuration item and the static configuration item. The dynamic configuration item is the parameter item adjusted according to the requirement list, while the static configuration item refers to those parameter items that do not need to be adjusted according to the specific requirement but are preset according to the architecture specification. For example, some basic initialization settings, protocol versions and other parameter items are usually regarded as static configuration items. The use of static configuration items simplifies the structure of the target configuration file, reduces unnecessary configuration work, and improves the generation efficiency of the target configuration file.

[0101] It is understandable that by integrating dynamic configuration items and static configuration items, the comprehensiveness and standardization of the target configuration file are ensured, and the accuracy and readability of the configuration file are improved.

[0102] Optionally, according to the requirement description file, determining the requirement list includes the following steps:

[0103] S141. According to the requirement description file and the preset priority rules, determine the priorities corresponding to multiple requirement items in the requirement description file;

[0104] Specifically, according to the preset priority rules, evaluate each requirement item in the requirement description file to determine its priority.

[0105] Specifically, the preset priority rules can be based on multiple factors, such as the impact of the requirement item on system security and stability, the urgency of the requirement item, the dependency relationship of the requirement item, the complexity of implementing the requirement item, etc. By evaluating each requirement item in the requirement description file to determine its priority, it is possible to identify which requirement items are critical and need to be given priority consideration during the configuration process.

[0106] It is understandable that by determining the priorities of the requirement items, it provides guidance for subsequent requirement analysis and parameter configuration work, enabling the configuration work to prioritize the handling of critical requirements and avoiding wasting resources on non-critical requirements.

[0107] S142. According to the priorities, sort the multiple requirement items to obtain an ordered list of requirement items;

[0108] Specifically, after the priorities of the requirement items are determined, sort the requirement items according to these priority values to obtain an ordered list of requirement items arranged in descending order of priority.

[0109] It is understandable that the ordered list of requirement items not only reflects the priorities of the requirement items but also provides a processing order for subsequent configuration work, ensuring that high-priority requirement items can be processed first, while low-priority requirement items are configured when resources permit.

[0110] S143. According to the ordered list of requirement items, determine the requirement list.

[0111] Specifically, after the ordered list of requirement items is determined, based on this ordered list of requirement items, construct the requirement list. The requirement list not only contains the detailed descriptions of the requirement items but also contains the priority information and configuration order of each requirement item, providing accurate guidance for subsequent parameter configuration work. The system will process the requirement items in the ordered list of requirement items one by one, convert them into specific parameter configuration requirements, and thus construct a complete requirement list.

[0112] It is understandable that constructing a requirements list based on ordered requirement items ensures the systematicness and orderliness of requirement configuration, avoiding chaos and duplication in the configuration work. The priority information and configuration order included in the requirements list can help quickly identify which configuration work needs to be reordered or prioritized in the event of requirement changes or resource adjustments, improving the flexibility and response speed of the configuration process.

[0113] Optionally, for the development method of in-vehicle software provided in the embodiments of the present application, please refer to Figure 2 , and the following can also be implemented:

[0114] (1) Input software development requirements through the collection interface of the requirements specification management system. Among them, the requirements specification management system provides input interfaces for requirements such as diagnosis, communication, and storage, and gives alarm prompts for anomalies such as missing key information. This system completes the collection and summary of requirements and outputs a standardized requirements description file. The input software development requirement information needs to contain clear requirement information, such as: message name, signal name, period, default value, etc. of Can communication;

[0115] (2) Verify the input requirement information according to the inspection rules;

[0116] (3) Export the requirement information in the form of a table as the requirements description file. Among them, the requirements description file is the key link connecting the requirements specification management system and the automated configuration system, and the generated format and parsing method need to be consistent;

[0117] (4) The automated configuration system takes the requirements description file exported in (3) as input. First, it passes through the requirement parsing module to identify the requirements list and the corresponding AUTOSAR CP modules that need to be configured. Among them, the automated configuration system consists of three parts: a requirement parsing module, a parameter configuration module, and an ARXML generation module;

[0118] (5) The parameter configuration module calls the corresponding parameter configuration template according to the CP modules that need to be configured identified in (4), and maps the content of the requirements list to the corresponding parameter items in the configuration template. Among them, the parameter configuration template includes basic configuration items and dynamic configuration items. The parameters of the basic configuration items change less, and the dynamic configuration items will change according to the requirement input. Fixing the parameters of the basic configuration items forms the parameter configuration template for the corresponding CP module;

[0119] (6) The ARXML generation module outputs the ARXML file in the standard format for the parameter items configured in (5). The output standard format ARXML file needs to be adapted to the AUTOSAR CP configuration tool, and the tool needs to be able to identify and generate the corresponding code;

[0120] (7) Import the standard ARXML file into the AUTOSAR CP configuration tool to generate corresponding code and obtain the basic software engineering.

[0121] In the vehicle software development method provided by the embodiments of the present application, the software development requirements are collected and standardized through the requirements specification management system, ensuring the accuracy and consistency of the requirements and laying a solid foundation for the subsequent development process. Secondly, the systematic verification of the requirement information can detect and correct any inconsistencies or omissions in the requirements at an early stage, avoiding rework caused by requirement errors in the later development and significantly improving the efficiency and quality of requirement management. The requirement parsing module accurately identifies the requirement list and its related AUTOSAR CP modules. This step avoids subjective biases during manual parsing through automated processing, improving the accuracy and efficiency of the matching between requirements and configuration modules. The parameter configuration module uses a preset parameter configuration template to achieve a direct mapping from the requirement list to configuration parameters, ensuring a high degree of consistency between the configuration parameters and business requirements, reducing configuration redundancy and errors, and improving the speed and accuracy of the configuration work. The introduction of the ARXML generation module enables the parameter configuration results to be output as ARXML files in accordance with the AUTOSAR CP standard format, accelerating the code generation process and ensuring the correctness and compatibility of the generated code. Finally, the standard ARXML file is imported into the AUTOSAR CP configuration tool to generate code. This automated process not only significantly reduces the development time and cost but also ensures the quality and consistency of the code, providing strong support for the rapid iteration and high-quality delivery of vehicle software. In summary, by implementing the vehicle software development method provided by the embodiments of the present application, seamless connection from requirement input to code output can be achieved, not only significantly improving the efficiency of vehicle software development, reducing the development cost and error rate, shortening the development cycle, but also ensuring the accuracy and consistency of software development, providing a strong technical driving force for the rapid development of the vehicle software industry.

[0122] Embodiment 2

[0123] The embodiments of the present application also provide a software development device 30. Please refer to Figure 3 , including: an acquisition module 310 for acquiring software development requirements; a determination module 320 for determining a requirement list and a parameter configuration template according to the software development requirements; a mapping module 330 for mapping the requirement list into the parameter configuration template to obtain a target configuration file; and a generation module 340 for inputting the target configuration file into a preset generation component to generate target code.

[0124] The development device of the above software provided by the embodiments of the present application achieves the following technical effects: The acquisition module is used to acquire software development requirements, ensuring that the starting point of software development is based on accurate requirement information and avoiding subsequent development problems caused by deviation in requirement understanding or incomplete requirement collection; the determination module is used to determine a requirement list and a parameter configuration template according to the software development requirements. The determination of the requirement list clarifies the specific objectives and content of software development, and the parameter configuration template is a standardized guide for the configuration work, ensuring that developers can complete parameter configuration quickly and accurately, avoiding subjective errors in the configuration process, and improving the efficiency and accuracy of the configuration work; the mapping module maps the requirement list to the parameter configuration template to obtain a target configuration file, realizing requirement-driven parameter configuration, ensuring a high degree of consistency between the configuration parameters and business requirements, reducing redundancy and errors in the configuration process, and improving the generation efficiency and quality of the configuration file; the generation module is used to input the target configuration file into a preset generation component to generate target code. The existence of the generation module reduces the workload of manual coding and improves the efficiency and quality of code generation. In summary, the software development device disclosed in the present application, through the organic combination of the acquisition module, the determination module, the mapping module and the generation module, realizes the technical effect of improving the development efficiency and quality of in-vehicle software by improving the accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process, and solves the technical problem that the development efficiency and quality of in-vehicle software are low due to the low accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process.

[0125] It should be noted that the optional implementation manners of this embodiment can refer to the relevant descriptions in Embodiment 1, and will not be elaborated here.

[0126] Embodiment 3

[0127] The embodiments of the present application further provide an electronic device 40. Please refer to Figure 4 , which includes a memory 410 and a processor 420. Among them, the memory 410 is used to store a computer program; the processor 420 is used to execute the program stored on the memory to implement the software development method described in any embodiment of the present application.

[0128] The above electronic device provided by the embodiments of the present application achieves the following technical effects: storing the computer program corresponding to the software development method described in any of the above into the memory, and using the processor to execute the computer program stored on the memory, realizing the technical effect of improving the development efficiency and quality of in-vehicle software by improving the accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process, and solving the technical problem that the development efficiency and quality of in-vehicle software are low due to the low accuracy and efficiency of AUTOSAR CP toolchain configuration during the in-vehicle software development process.

[0129] Those of ordinary skill in the art can understand that Figure 4 the structure shown is only schematic, and the electronic device can also be a terminal device such as a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a personal digital assistant, and a Mobile Internet Device (MID). Figure 4 It does not limit the structure of the above-mentioned electronic device. For example, the electronic device 40 may further include more or fewer components (such as a network interface, a display device, etc.) than those shown in Figure 4 or have a different configuration from that shown in Figure 4 Example 4

[0130] The embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the software development method described in any embodiment of the present application is implemented.

[0131] Optionally, in this embodiment, the above storage medium may include, but is not limited to: various media that can store computer programs such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disc.

[0132] The computer-readable storage medium provided in the embodiment of the present application achieves the following technical effects: storing the computer program corresponding to the software development method in any of the above into the computer-readable storage medium, and using the processor to execute the computer program stored in the computer-readable storage medium, so as to achieve the technical effects of improving the accuracy and efficiency of the AUTOSAR CP toolchain configuration during the in-vehicle software development process, and further improving the development efficiency and quality of the in-vehicle software, and solving the technical problem that the development efficiency and quality of the in-vehicle software are low due to the low accuracy and efficiency of the AUTOSAR CP toolchain configuration during the in-vehicle software development process.

[0133] The serial numbers of the above embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0134] In the above embodiments of the present application, the descriptions of the respective embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

[0135] In the present application, "a plurality of" means two or more.

[0136]

[0137] ​In this application, unless otherwise clearly defined, the terms "install", "connect", and "link" shall be understood in a broad sense. For example, it may be a fixed connection, a detachable connection, or an integral connection; it may be a mechanical connection or an electrical connection; it may be a direct connection or an indirect connection through an intermediate medium, and it may be the communication inside two components. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0138] The terms "first", "second", "third", "fourth", etc. (if any) in this application are used to distinguish similar objects and do not necessarily describe a specific order or sequence.

[0139] The term "and / or" in this application is merely a relational description of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this application generally represents an "or" relationship between the associated objects before and after.

[0140] If there is no special indication, all steps of this application can be carried out in sequence or randomly. For example, the method includes steps A and B, which means that the method may include steps A and B carried out in sequence, or steps B and A carried out in sequence. For example, it is mentioned that the method may further include step C, which means that step C can be added to the method in any order. For example, the method may include steps A, B, and C, or steps A, C, and B, or steps C, A, and B, etc.

[0141] The above are only the preferred embodiments of this application and are not intended to limit this application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this application shall be included within the protection scope of this application.

Claims

1. A software development method, characterized in that, Including: Obtain software development requirements; According to the software development requirements, determine a requirements list and a parameter configuration template; Map the requirements list to the parameter configuration template to obtain a target configuration file; Input the target configuration file into a preset generation component to generate target code.

2. The method according to claim 1, wherein According to the software development requirements, determining the requirements list includes: According to the software development requirements, determine a requirements description file, where the requirements description file is a standardized document for recording the software development requirements; According to the requirements description file, determine the requirements list, where the requirements list is a requirements list for guiding parameter configuration.

3. The method according to claim 2, characterized in that, According to the software development requirements, determining the requirements description file includes: Parse the software development requirements to generate multiple requirement items in a target format; Construct a requirements table as the requirements description file according to the multiple requirement items.

4. The method according to claim 1, wherein The determining the requirements description file according to the software development requirements includes: Perform a correctness check on the software development requirements according to preset check rules to obtain a correctness check result, where the correctness check includes information integrity check and information consistency check; In response to the correctness check result indicating that the software development requirements pass the check, determine the requirements description file.

5. The method according to claim 2, characterized in that, According to the requirements description file, determining the requirements list includes: Determine a preset generation component associated with the requirement item to obtain a component to be configured, where the requirement item is included in the requirements description file; Construct a requirements list according to the requirement item and the component to be configured.

6. The method according to claim 5, wherein The determining the parameter configuration template according to the software development requirements includes: According to the component to be configured, determine a parameter configuration template corresponding to the component to be configured from a preset template library.

7. The method according to any one of claims 1 to 6, characterized in that, The mapping the requirements list to the parameter configuration template to obtain a target configuration file includes: Construct a mapping relationship between the item in the requirements list and the parameter item in the parameter configuration template; According to the mapping relationship, map the item in the requirements list to the parameter item in the parameter configuration template to obtain a dynamic configuration item; According to the dynamic configuration item and the static configuration item, determine the target configuration file, where the static configuration item is a preset configuration item.

8. The method according to claim 2, wherein According to the requirements description file, determining the requirements list includes: According to the requirements description file and preset priority rules, determine the priorities corresponding to multiple requirement items in the requirements description file; Sort the multiple requirement items according to the priorities to obtain ordered requirement items; According to the ordered requirement items, determine the requirements list.

9. A software development device, characterized in that, Including: An obtaining module, configured to obtain software development requirements; A determining module, configured to determine a requirements list and a parameter configuration template according to the software development requirements; A mapping module, configured to map the requirements list to the parameter configuration template to obtain a target configuration file; A generating module, configured to input the target configuration file into a preset generation component to generate target code.

10. An electronic device, characterized in that, Including a processor and a memory, where The memory is used to store a computer program; The processor is configured to execute the program stored on the memory to implement the method according to any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1-8 is implemented.

Images