Software development management and control method, device and system

Abstract

The invention discloses a software development control method, device and system, and relates to the technical field of software development, the method is applied to a software development management platform, and the method comprises the following steps: obtaining development reference information required by a current to-be-controlled target development stage of a software development project; sending a first publishing notification of the development reference information to a software development platform based on the modeling language; obtaining demand analysis information of the target development stage returned by the software development platform; sending a second release notification of the demand analysis information to the software development platform under the condition that the demand analysis information is confirmed to meet the demand review requirement in the automobile software evaluation specification; and obtaining an architecture design model of the target development stage returned by the software development platform. According to the method, the automobile software evaluation specification is combined with the development and management and control process of the automobile software, and the development of the automobile software is managed and controlled more reasonably.

Description

Technical Field

[0001] This application relates to the technical field of software development, and in particular, to a software development control method, device, and system. Background Art

[0002] With the increasing requirements of the automotive industry for vehicle safety and quality, higher requirements are also put forward for the software on vehicles.

[0003] In order to ensure the software quality of vehicle software, some automotive software evaluation specifications have been proposed in the current automotive industry. For example, the German Automobile Industry Association has released the Automotive Software Process Improvement and Capacity Determination (ASPICE) specification. The automotive software evaluation specification provides a reliable basis for judging software quality. However, currently, the automotive software evaluation specification is not effectively combined with the development and control process of automotive software, which is not conducive to developers developing high-quality automotive software more efficiently. Based on this, how to combine the development and control process of automotive software with the automotive software evaluation specification to achieve more reasonable control of software development in the automotive field is a technical problem that needs to be solved by those skilled in the art. Summary of the Invention

[0004] In view of the above problems, this application provides a software development control method, device, and system, which realizes the combination of the automotive software evaluation specification and the development and control process of automotive software, and realizes more reasonable control of the development of automotive software.

[0005] On the one hand, this application provides a software development control method, which is applied to a software development management platform and includes:

[0006] Obtain the development reference information required for the target development stage currently to be controlled in the software development project. The development reference information is the releasable information that has been confirmed to meet the review requirements in the automotive software evaluation specification before the target development stage. The target development stage belongs to multiple development stages required for software development in the automotive software evaluation specification;

[0007] Send a first release notice of the development reference information to the software development platform based on the modeling language. The first release notice is used to instruct developers to perform requirement analysis for the target development stage based on the development reference information;

[0008] Obtain the requirement analysis information of the target development stage returned by the software development platform;

[0009] When it is confirmed that the requirement analysis information meets the requirement review requirements in the automotive software assessment specification, a second release notice of the requirement analysis information is sent to the software development platform, and the second release notice is used to instruct developers to perform architecture design in the target development stage based on the requirement analysis information;

[0010] Obtain the architecture design model of the target development stage returned by the software development platform.

[0011] In a possible implementation manner, when obtaining the requirement analysis information of the target development stage returned by the software development platform, it further includes: obtaining the first traceability information returned by the software development platform, and the first traceability information is used to characterize that the requirement analysis information is obtained based on the development reference information;

[0012] When obtaining the architecture design model of the target development stage returned by the software development platform, it further includes: obtaining the second traceability information returned by the software development platform, and the second traceability information is used to characterize that the architecture design model is obtained based on the requirement analysis information.

[0013] In another possible implementation manner, after obtaining the architecture design model of the target development stage returned by the software development platform, it further includes:

[0014] When it is confirmed that the architecture design model meets the architecture design review requirements in the automotive software assessment specification, the architecture design model is used as the development reference information required for the next development stage after the target development stage.

[0015] In another possible implementation manner, it further includes:

[0016] When it is confirmed that the requirement analysis information meets the requirement review requirements in the automotive software assessment specification, based on the review process of the requirement analysis information on the software development management platform, a requirement specification that meets the requirements in the automotive software assessment specification is generated;

[0017] When it is confirmed that the architecture design model meets the corresponding architecture design review requirements in the automotive software assessment specification, based on the review process of the architecture design model by reviewers on the software development management platform, an architecture design specification that meets the requirements in the automotive software assessment specification is generated;

[0018] After obtaining the requirement analysis information of the target development stage returned by the software development platform, it further includes:

[0019] Generate a requirements review report for the requirements analysis information based on the review opinions of at least one reviewer entered on the software development management platform for the requirements analysis information;

[0020] After obtaining the architecture design model of the target development stage returned by the software development platform, it further includes:

[0021] Generate an architecture design review report for the architecture design model based on the review opinions of at least one reviewer entered on the software development management platform for the architecture design model.

[0022] In another possible implementation, before obtaining the development reference information, it further includes:

[0023] Obtain the project requirements information of the software development project, where the project requirements information is used to describe the product functions that are desired to be implemented;

[0024] The obtaining of the development reference information required for the target development stage currently to be controlled in the software development project includes:

[0025] In the case of confirming that the project requirements information meets the project requirements review requirements in the automotive software evaluation specification, determine the project requirements information as the development reference information required in the systems engineering development stage of the software development project;

[0026] The obtaining of the requirements analysis information of the target development stage returned by the software development platform includes:

[0027] If the target development stage is the systems engineering development stage, obtain the system requirements information returned by the software development platform;

[0028] The obtaining of the architecture design model of the target development stage returned by the software development platform includes:

[0029] If the target development stage is the systems engineering development stage, obtain the system architecture design model returned by the software development platform.

[0030] In another possible implementation, the obtaining of the development reference information required for the target development stage currently to be controlled in the software development project includes:

[0031] If the target development stage is the software engineering development stage, obtain the system architecture design model obtained in the systems engineering development stage;

[0032] The obtaining of the requirements analysis information of the target development stage returned by the software development platform includes:

[0033] If the target development stage is the software engineering development stage, obtain the software requirement information returned by the software development platform;

[0034] The obtaining of the architecture design model of the target development stage returned by the software development platform includes:

[0035] If the target development stage is the software engineering development stage, obtain the software architecture design model returned by the software development platform.

[0036] In another possible implementation, after obtaining the software architecture design model returned by the software development platform, it further includes:

[0037] When it is confirmed that the software architecture design model meets the software architecture design review requirements in the automotive software evaluation specification, send the software architecture design model to the terminal device of the target developer, and the software architecture design model is used to provide a basis for the target developer to develop software code;

[0038] Obtain the software code information returned by the terminal device of the target developer, and store the software code information and the association relationship between the software code information and the software development project.

[0039] In another possible implementation, after obtaining the software code information returned by the terminal device of the target developer, it further includes:

[0040] Set the software code information to the released state, where in the case that the software code information is in the released state, testers can test the software code information;

[0041] Obtain the test results obtained by the tester based on the software requirement analysis information, the software architecture design model, and the software code information, and the association relationship between the test results and the software development project.

[0042] On the other hand, the present application also provides a software development control device, which is applied to a software development management platform and includes:

[0043] The first obtaining unit is used to obtain the development reference information required for the target development stage currently to be controlled in the software development project. The development reference information is the releasable information that has been confirmed to meet the review requirements in the automotive software evaluation specification before the target development stage. The target development stage belongs to multiple development stages required for software development in the automotive software evaluation specification;

[0044] A first publishing unit, configured to send a first publishing notice of the development reference information to a software development platform based on a modeling language, where the first publishing notice is used to instruct developers to perform requirement analysis for the target development stage based on the development reference information;

[0045] A second obtaining unit, configured to obtain the requirement analysis information of the target development stage returned by the software development platform;

[0046] A second publishing unit, configured to, when confirming that the requirement analysis information meets the requirement review requirements in the automotive software evaluation specification, send a second publishing notice of the requirement analysis information to the software development platform, where the second publishing notice is used to instruct developers to perform architecture design for the target development stage based on the requirement analysis information;

[0047] A third obtaining unit, configured to obtain the architecture design model of the target development stage returned by the software development platform.

[0048] In another aspect, the present application further provides a software development control system, including:

[0049] A software development management platform and a software development platform;

[0050] Wherein, the software development management platform is configured to execute the software development control method described in any one of the above;

[0051] The software development platform is at least configured to feedback the requirement analysis information and the architecture design model of the target development stage currently to be controlled in the software development project to the software development management platform.

[0052] As can be seen from the above content, in each development stage of the software development project of the present application, the obtained development reference information is publishable information that has been confirmed to meet the review requirements of the automotive software evaluation specification. Therefore, after sending a publishing notice of the development reference information to a software development platform based on a modeling language, the reliability of developers performing requirement analysis on this software development platform based on the development reference information is higher. Moreover, after the requirement analysis information returned by the software development platform, only when confirming that the requirement analysis information meets the requirement review requirements in the automotive software evaluation specification, a publishing notice of the requirement analysis information will be sent to the software development platform, enabling developers to design the architecture design model of this development stage on the software development platform based on the requirement distribution information that meets the automotive software evaluation specification, improving the reliability and quality of the architecture design model, so that the requirement analysis information and the architecture design model in each development stage of the software development project can meet the automotive software evaluation specification, realizing more reasonable control of the software development process, and naturally improving the quality of the finally developed automotive software. Description of the Drawings

[0053] In conjunction with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the original components and elements are not necessarily drawn to scale.

[0054] Figure 1 It is a schematic flowchart of a software development control method provided for this application;

[0055] Figure 2 It is another schematic flowchart of a software development control method provided for this application;

[0056] Figure 3 It is an interaction relationship diagram of software development control by the ALM platform and the MBSE platform based on the ASPICE specification in this application;

[0057] Figure 4 It shows the functional modules involved in development control by the ALM platform based on the ASPICE specification and an example of information interaction between each functional module and the MBSE platform;

[0058] Figure 5 It shows an example of interaction between the ALM platform and the MBSE platform in the system engineering development stage;

[0059] Figure 6 It shows an example of interaction between the ALM platform and the MBSE platform in the software engineering development stage;

[0060] Figure 7 It shows a schematic diagram of the composition structure of a software development control device provided for this application. Specific Embodiments

[0061] The following describes the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. The terms used in the embodiments part of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application. Those of ordinary skill in the art will know that with the development of technology and the emergence of new scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0062] In the description and claims of this application, as well as in the above-mentioned drawings, terms such as "first" and "second" are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, which is merely a way of distinguishing objects with the same attributes when describing the embodiments of this application. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion, so that a process, method, system, product or device comprising a series of units does not have to be limited to those units, but may include other units not clearly listed or inherent to these processes, methods, products or devices.

[0063] On the one hand, this application provides a software development control system, including a software development management platform and a software development platform, and the software development management platform and the software development platform can establish a communication connection.

[0064] Among them, software development control is carried out on the software development management platform based on the automotive software evaluation specification.

[0065] The software development platform can feedback the requirement analysis information and architecture design model created by developers on the software development platform to the software development management platform.

[0066] Of course, developers can also generate traceability information in accordance with the requirements of the automotive software evaluation specification, and generate traceability information related to the requirement analysis information and architecture design information on the software development platform, so that the software development platform can feedback the relevant traceability information to the software development management platform.

[0067] In this application, the software development platform can be a software development platform based on a modeling language. For example, the software development platform can be a Model-Based Systems Engineering (MBSE) platform, and the MBSE platform is a server system or cloud platform configured with MBSE, etc., without limitation.

[0068] Among them, MBSE has gradually emerged with the development of computer technology and the application and popularization of object-oriented, graphical, and visual system modeling language technologies. The characteristics of MBSE are that on the basis of inheriting the idea of "defining user requirements in the early stage of the development phase and conducting design synthesis and system verification" in systems engineering, through the application of formal methods, a graphical and visual standard modeling language is used to construct a system architecture model. Through the application of MBSE, the problems of ambiguity, fuzziness, difficulty in searching and establishing traceability caused by using natural language to describe architecture design in traditional document-based systems engineering can be effectively solved.

[0069] First, the software development control method of this application will be introduced from the perspective of the software development management platform.

[0070] As Figure 1 , a flowchart diagram of a software development control method provided by this application is shown. The method of this embodiment is applied to a software development management platform, and the method of this embodiment may include:

[0071] S101, obtain the development reference information required for the target development stage that needs to be controlled for the current software development project.

[0072] Among them, the target development stage belongs to multiple development stages involved in software development required by the automotive software assessment specification. In this application, there can be multiple possibilities for the automotive software assessment specification. When the automotive software assessment regulations are different, the number and types of development stages involved in software development specified in the automotive software assessment specification will also vary, and this is not restricted.

[0073] In a possible implementation manner, the automotive software assessment specification can be the ASPICE specification. In the ASPICE specification, it is divided into different process groups according to the system layer and the software layer, and each process group can be regarded as a development stage. For example, the process groups specified in the ASPICE specification include: the system process group and the software process group. Correspondingly, in this application, the multiple development stages involved in software development required by the ASPICE specification can include: the system engineering development stage corresponding to the system process group, and the software engineering development stage corresponding to the software process group.

[0074] Among them, the development reference information is the publishable information that has been confirmed to meet the review requirements in the automotive software assessment specification before this target development stage. The development reference information is the reference information required to determine the requirements analysis information of the target development stage, and when the target development stage is different, the development reference information will also be different.

[0075] S102, send a first release notice of the development reference information to the software development platform based on the modeling language.

[0076] Among them, the software development platform based on the modeling language can be an MBSE platform, or other platforms that can implement requirements analysis and architecture design during software development based on the modeling language, and this is not restricted.

[0077] The first release notice is used to instruct developers to perform requirements analysis for this target development stage based on the development reference information.

[0078] Among them, developers can log in to the software development platform through the development client corresponding to the software development platform. Based on the first release notice received on the software development platform, developers can confirm that the development reference information complies with the automotive software evaluation specification and can perform requirement analysis based on the development reference information. On this basis, developers can perform requirement analysis for the target development stage on the software development platform based on the development reference information.

[0079] S103, obtain the requirement analysis information for the target development stage returned by the software development platform.

[0080] Among them, the requirement analysis information is the requirement analysis information constructed by developers on the software development platform based on the development reference information.

[0081] Requirement analysis information is the information required for reference in designing the architecture design model for the corresponding development stage during the software development process. Requirement analysis information is used to represent information such as the functional modules involved in software development and the relationships between functional modules.

[0082] When the target development stages are different, the requirement analysis information will also be different. For example, the requirement analysis information can be system requirement analysis information (also known as system requirement information) or software requirement analysis information (also known as software requirement information).

[0083] S104, when it is confirmed that the requirement analysis information meets the requirement review requirements in the automotive software evaluation specification, send a second release notice of the requirement analysis information to the software development platform.

[0084] Among them, the requirement review requirements in the automotive software evaluation specification can stipulate the various requirements that the requirement analysis information needs to meet.

[0085] In this application, there can be various possible specific implementations for the software development management platform to determine whether the requirement analysis information meets the requirement review requirements based on the automotive software evaluation specification, and no restrictions are imposed on this.

[0086] For example, in one possible implementation, the software development management platform can obtain the review opinions of at least one reviewer on the requirement analysis information, and the review opinions are used to indicate whether the requirement analysis information meets the requirement review requirements in the automotive software evaluation specification. For example, each reviewer can sequentially determine whether the requirement analysis information meets the corresponding regulations according to the various regulations of the requirement review requirements displayed by the software development management platform and input the review opinions. Correspondingly, if the proportion of reviewers who confirm that the requirement analysis information meets the requirement review requirements among the at least one reviewer's review opinions exceeds the set ratio, it is confirmed that the requirement analysis information meets the requirement review requirements.

[0087] It can be understood that if the requirements analysis information does not meet the requirements review requirements, an exception prompt for the requirements analysis information can be fed back to the software development platform. The exception prompt is used to prompt that the requirements analysis information does not meet the requirements review requirements of the automotive software evaluation specification, so that developers can regenerate the requirements analysis information on the software development platform.

[0088] Among them, the second release notice is used to instruct developers to perform the architecture design of the target development stage based on the requirements analysis information. Correspondingly, after receiving the second release notice on the software development client corresponding to the software development platform, developers can build a corresponding architecture design model on the software development platform based on the requirements analysis information.

[0089] S105, obtain the architecture design model of the target development stage returned by the software development platform.

[0090] Among them, the architecture design model can include information such as objects involved in implementing the development requirements corresponding to the target development stage, signal transmission relationships between objects, and control logic relationships between objects, etc., without limitation.

[0091] When the target development stages are different, the architecture design models will also be different. For example, the architecture design model can be a system architecture design model or a software architecture design model.

[0092] It can be understood that after obtaining the architecture design model, it can also be reviewed on the software development management platform to determine whether the architecture design model meets the architecture design review requirements in the automotive software evaluation specification. If so, it is confirmed that the architecture design model meets the release conditions, and naturally, the execution of the next development stage can be triggered. Based on this, when it is confirmed that the architecture design model meets the architecture design review requirements in the automotive software evaluation specification, this application can also use the architecture design model as the development reference information required for the next development stage after the target development stage.

[0093] As can be seen from the above, in each development stage of a software development project, the development reference information obtained is publishable information that has been confirmed to meet the review requirements of the automotive software assessment specification. Therefore, after sending a release notice of the development reference information to the software development platform based on the modeling language, the reliability of the requirements analysis carried out by developers on this software development platform based on the development reference information is higher. Moreover, after the requirements analysis information returned by the software development platform, a release notice of the requirements analysis information will only be sent to the software development platform when it is confirmed that the requirements analysis information meets the requirements review requirements in the automotive software assessment specification, enabling developers to design the architecture design model for this development stage on the software development platform based on the requirements distribution information that meets the automotive software assessment specification, improving the reliability and quality of the architecture design model. As a result, the requirements analysis information and architecture design models in each development stage of the software development project can all meet the automotive software assessment specification, achieving a more reasonable control of the software development process and naturally improving the quality of the finally developed automotive software.

[0094] It can be understood that the automotive software assessment specification can also stipulate the activities that must be carried out and the document outputs required in each target development stage to strictly standardize the software R & D process.

[0095] In a possible implementation, the automotive software assessment specification requires the ability to trace the information in the software development process. Therefore, developers are required to configure the traceability information of the corresponding development artifacts while constructing or creating relevant development artifacts. Based on this, while developers generate requirements analysis information based on the software development platform, they also generate the first traceability information of this requirements analysis information. Correspondingly, while the software development management platform obtains the requirements analysis information, it can also obtain the first traceability information returned by the software development platform. Among them, the first traceability information is used to indicate that the requirements analysis information is obtained based on the development reference information. Correspondingly, based on the first traceability information, the development reference information on which the requirements analysis information is generated can be traced.

[0096] Similarly, after developers construct the architecture design model based on the software development platform, they can also construct the second traceability information of this architecture design model. Correspondingly, while the software development management platform obtains the architecture design model, it can also obtain the second traceability information returned by the software development platform. Among them, the second traceability information is used to indicate that the architecture design model is obtained based on the requirements analysis information. Based on the second traceability information, the requirements analysis information on which the architecture design model is based can be determined.

[0097] It can be understood that the automotive software evaluation specification will also require generating corresponding review reports after reviewing each document or information in the target development stage, or recording the relevant information on the modification and update of the relevant information during the review process.

[0098] Based on this, in another possible implementation, after the software development management platform obtains the requirements analysis information of the target development stage from the software development platform, it can also generate a requirements review report for the requirements analysis information based on the review opinions of at least one reviewer entered on the software development management platform. Among them, the requirements review report can at least include the review opinions of each reviewer on the requirements analysis information. Of course, the requirements review report can also include information such as the review results of the requirements analysis information, the time when each reviewer gives the review opinions, etc., and there is no limit to this.

[0099] Similarly, after the software development management platform obtains the architecture design model, it can also generate an architecture design review report for the architecture design model based on the review opinions of at least one reviewer entered on the software development management platform. Among them, the architecture design review report can at least include the review opinions of each reviewer on the architecture design model. Of course, it can also include other review information related to the architecture design model, and there is no limit to this.

[0100] In another possible implementation, when it is confirmed that the requirements analysis information meets the requirements review requirements in the automotive software evaluation specification, a requirements specification that meets the requirements in the automotive software evaluation specification can also be generated based on the review process of the requirements analysis information on the software development management platform.

[0101] Among them, the review process for the requirements analysis information involves various review-related operation behaviors. For example, it can include: the review opinions of the reviewers on the requirements analysis information; in the case of non-passing the review, the adjustment instructions entered by the reviewers for the requirements analysis information; the further review of the updated requirements analysis information and other process information.

[0102] Among them, the requirements specification can record the information related to the review process of the requirements analysis information that the automotive software assessment specification requires to record, specifically subject to the content required to be recorded in the automotive software assessment specification for the requirements specification. For example, during the review process of the requirements analysis information, content updates and version updates may occur, which involves some information interactions between the reviewers and the developers through the software development management platform and the software development platform. The requirements specification can record these interaction information involved in the review process. For example, the review passing time of the requirements specification, the review situations of each time, the number of times and the modification time indicated to be modified during the review process, and the version information of the requirements specification, etc.

[0103] Similarly, in the case where it is confirmed that the architecture design model meets the architecture design review requirements corresponding to the automotive software assessment specification, based on the review process of the reviewers on the architecture design model on the software development management platform, an architecture design specification that meets the requirements in the automotive software assessment specification is generated.

[0104] The review process of the reviewers on the architecture design model involves various operation behaviors related to the review, such as the input review opinions, adjustment opinions, etc. Specifically, it is similar to the review process of the requirements analysis information and will not be elaborated here.

[0105] Among them, the architecture design specification can record the information related to the review process of the architecture design model that the automotive software assessment specification requires to record, specifically subject to the content required to be recorded in the automotive software assessment specification for the architecture design specification. For example, the architecture design specification can record the review passing time of the architecture design model, the number of times and the modification time modified during the review process, the current version information, etc., without any restrictions.

[0106] It can be understood that software development generally involves system-related development stages and software-related development stages. Based on this, in this application, the automotive software assessment specification requires that the multiple development stages involved in software development at least include: the system engineering development stage and the software engineering development stage.

[0107] The system engineering development stage is the first development stage of software development, and the system engineering development stage needs to construct the system requirements and system architecture design by combining the requirements of stakeholders such as customers. Based on this, in one possible implementation, before obtaining the development reference information, it further includes: obtaining the project requirements information of the software development project, where the project requirements information is used to describe the product functions that are expected to be achieved. The project requirements information describes the product functions that the user hopes to achieve in natural language. For example, the project requirements information can be "When the car door is developed, the interior lights of the vehicle will turn on for illumination." Correspondingly, when it is confirmed that the project requirements information meets the project requirements review requirements in the automotive software evaluation specification, the project requirements information is determined as the development reference information required in the system engineering development stage of the software development project.

[0108] It can be understood that in the system engineering development stage, it is necessary to determine the system requirements information and the system architecture design model. Based on this, if the target development stage is the system engineering development stage, the requirements analysis information returned by the software development platform is the system requirements information. Correspondingly, the architecture design model returned by the software development platform is the system architecture design model.

[0109] Similarly, in the software engineering development stage, it is necessary to determine the software requirements information and the software architecture design model. Based on this, if the target development stage is the software engineering development stage, the requirements analysis information returned by the software development platform is the software requirements information. Correspondingly, the architecture design model returned by the software development platform is the software architecture design model.

[0110] Furthermore, after the software engineering development stage, the developer also needs to perform detailed software design and finally complete software code writing, etc. Based on this, when it is confirmed that the software architecture design model meets the software architecture design review requirements in the automotive software evaluation specification, this application can also send the software architecture design model to the terminal device of the target developer, and the software architecture design model is used to provide a basis for the target developer to develop software code. Correspondingly, the software development management platform can obtain the software code information returned by the terminal device of the target developer and store the software code information and the association relationship between the software code information and the software development project.

[0111] To facilitate the understanding of the solution of this application, below, taking one implementation as an example, the software development control method of this application will be introduced from the perspective of the interaction between the software development management platform and the software development platform.

[0112] As Figure 2 , a schematic diagram of the process interaction of the software development control method provided by the embodiment of this application is shown. The method of this embodiment may include:

[0113] S201, The software development management platform obtains the project requirement information of the software development project.

[0114] Among them, the project requirement information is also called stakeholder requirement information, which is used to describe the product functions that are expected to be realized.

[0115] S202, When it is confirmed that the project requirement information meets the project requirement review requirements in the automotive software assessment specification based on the review operation of at least one reviewer on the project requirement information, the software development management platform generates a project requirement specification and sends a release notice of the project requirement information to the software development platform.

[0116] In this application, both the software development management platform and the software development platform perform relevant operations based on the automotive software assessment specification during the software development process and generate relevant documents required by the automotive software assessment specification.

[0117] For the sake of easy understanding, taking the automotive software assessment specification as the ASPICE specification, taking the software development platform as the MBSE platform, and taking the software development management platform as the Application Lifecycle Management (ALM) platform as an example, see Figure 3 , which is the interaction relationship diagram of the ALM platform ( Figure 3 the ALM system in) and the MBSE platform for software development control based on the ASPICE specification. In Figure 3 , the MBSE tool is the client of the MBSE platform. Users log in to the MBSE platform through the MBSE tool to implement relevant operations such as requirement analysis and architecture design through the MBSE platform. Therefore, the operations on the MBSE tool can be regarded as the operations performed by the MBSE platform.

[0118] It can be seen from Figure 3 that software development in the ASPICE specification can involve two process groups, namely the system engineering group and the software engineering group. Among them, each process group is a software development stage. Therefore, the system engineering group is the system engineering development stage, and the software engineering group corresponds to the software engineering development stage. In different software development stages, the development reference information obtained by the ALM platform and the MBSE platform is different, and the determined requirement analysis information and architecture design are also different.

[0119] In order to enable the ALM platform to store the information related to the software development project, project managers can also create a project space in the ALM platform, which is used to store the requirement information, architecture design models, various reports, specification documents, and other information related to the software development project.

[0120] Moreover, project managers can also set up the hierarchical structures and required traceability relationship information involved in each process group based on the ASPICE specification. For example, the products to be developed, the documents obtained, and the traceability relationships required for creating the system requirements hierarchy, system architecture design hierarchy, software requirements hierarchy, and software architecture design hierarchy.

[0121] Project managers can also set up the project plan information for this software development project on the ALM platform, such as the development start time, development completion time, and test completion time of the project plan.

[0122] In addition, project managers can also set up defect and other data management spaces on the ALM platform. This part of the space is used to store the problems generated in each development stage and the defect records during the testing process.

[0123] To implement the processing in different software development stages, multiple requirement modules are set up on the ALM platform. Different requirement modules are responsible for controlling different development stages. For example Figure 4 As shown, the stakeholder requirements module in the ALM platform is responsible for the analysis and processing of project requirement information, the system requirements module is responsible for the processing in the system engineering development stage, and the software requirements module is responsible for the related processing in the software engineering development stage.

[0124] Correspondingly, the interactions between different requirement modules in the ALM platform and the MBSE tool will also be different, which will be described in combination with the corresponding steps later.

[0125] Among them, after the software development management platform obtains the project requirement information, the software development platform has completed a requirement handshake for this project requirement information and can initiate the review of the project requirement information. Each reviewer can perform review operations on the project requirement information on the software development platform, and the software development management platform can record the review operations of each reviewer and determine the final review result. For example, the software development platform can freeze the project requirement information to enter the review stage of this project requirement information. In this review stage, each reviewer can log in to the software development platform through a terminal device and input review opinions on the project requirement information or select review opinion options, etc.

[0126] Among them, the project requirement information meeting the project requirement review requirements can be based on the review operations of each reviewer, and it is confirmed that the proportion of review opinions belonging to qualified reviews exceeds the set ratio. Of course, it can also be determined by other means, and there is no restriction on this.

[0127] When the project requirement information meets the requirements of the project requirement review, the software development management platform can set the status of the project requirement information to the released status and send a release notice of the project requirement information to the software development platform, so that developers with permissions can obtain the release notice of the project requirement information through the software development platform. Among them, the release notice of the project requirement information can include the project requirement information, and it can be confirmed that the project requirement information meets the requirements of the project requirement review through the release notice.

[0128] For example Figure 5 , it shows an example of the interaction process between the ALM platform and the MBSE platform in the system engineering development stage.

[0129] It can be seen from Figure 5 that the ALM platform will first obtain the project requirement information (stakeholder requirements in Figure 5 ) in the system engineering development stage and complete the requirement handshake. After freezing the project requirement information, it can obtain the review operations of the reviewers on the project requirement information and obtain information related to the entire review process of the project requirement information. After confirming that the project requirement information meets the requirements of the project requirement review, the project requirement information can be released, and thus the project requirement information is sent to the MBSE platform; at the same time, the ALM platform will also generate a project requirement specification.

[0130] The project requirement specification can record information related to the review process of the project requirement information, such as change requests for the project requirement information during the review process (such as version update situations, content change situations), and review opinions input by each reviewer at different times, etc.

[0131] Furthermore, after the project requirement information meets the requirements of the project requirement review, the ALM platform can also output a handshake record, which can record the time when the project requirement information is handshake (received), the number of handshakes, etc.

[0132] S203. Based on the project requirement information, the software development platform obtains the system requirement information constructed by the developer and the traceability information corresponding to the system requirement information, and sends the system requirement information and its corresponding traceability information to the software development management platform.

[0133] Among them, the traceability information corresponding to the system requirement information is used to indicate that the system requirement information is obtained based on the project requirement information. This traceability information actually constructs the association relationship between the system requirement information and the project requirement information, and based on this traceability information, the project requirement information on which the system requirement information is constructed can be traced back.

[0134] System requirements information describes the requirements of software from a system perspective, including the functions that the system needs to implement, the rules and constraints that need to be complied with, etc. Among them, the system may include software modules that execute the functions of the software product and the hardware that runs the software modules, etc.

[0135] It can be understood that the project requirements information can be project requirement entries including multiple requirements information. Correspondingly, the system requirements information can be system requirement entries including multiple system requirements.

[0136] Among them, developers can perform system requirements analysis based on the project requirements information obtained from the software development platform. Among them, the process in which developers perform system requirements analysis based on the software development platform and finally generate system requirements information and the first traceability information can be unrestricted.

[0137] Combined with Figure 3 and Figure 4 It shows that:

[0138] From Figure 3 and Figure 4 it can be seen that after obtaining the project requirements information on the MBSE platform, developers need to perform system requirements use case analysis and system function analysis on the MBSE platform through the MBSE client (i.e., the MBSE tool) before they can obtain the system requirements information.

[0139] Specifically, developers determine the functional requirements of the system based on the project requirements information, and build a system use case diagram that meets the functional requirements on the MBSE platform based on the Systems Modeling Language (SysML) or the Unified Modeling Language (UML). Add the association relationships between different system use cases and external actors in the system use case diagram.

[0140] Then, based on the system use case diagram, developers can use sequence diagrams, activity diagrams, state diagrams, or internal module diagrams in the SysML or UML language to express the behavior of the system, the external ports of the system, and the connection relationships between the system and external actors, and derive the dynamic and static characteristic requirement descriptions of the system to form system requirements information. As Figure 4 shown in, a use case diagram needs to be constructed in the system use case model, and through the system function analysis process, combined with activity diagrams, sequence diagrams, state diagrams, and internal module diagrams, the characteristic requirement descriptions of the system can be obtained, and finally the system requirements information is formed.

[0141] Of course, the project requirements information can be converted into one or more system requirements. Therefore, the system requirements information can include system requirement entries with at least one system requirement.

[0142] In addition, developers can also add the association relationship between the system requirement information and the project requirement information to the system requirement information to form the first traceability information.

[0143] S204. The software development management platform records the review operations of at least one reviewer on the system requirement information. When it is confirmed that the system requirement information meets the requirement review requirements in the automotive software evaluation specification, based on the review process of the system requirement information on the software development management platform, a requirement specification that meets the automotive software evaluation specification is generated, and a release notice of the system requirement information is sent to the software development platform.

[0144] After the software development management platform receives the system requirement information, the software development platform will set the system requirement information to the frozen state to initiate the review of the system requirement information. For example, the software development platform sends a review notice for the system requirement information to the terminal device of the reviewer to review the system requirement information through the reviewer.

[0145] During the process of the reviewer's review operation on the system requirement information, the software development management platform will record the review operation behaviors of each reviewer, so that when it is subsequently confirmed that the system requirement information meets the requirement review requirements, a requirement specification is generated based on the review operations of each reviewer.

[0146] Of course, when the system requirement information meets the requirement review requirements, the first traceability information corresponding to the system requirement information will also be stored for subsequent information traceability.

[0147] In this embodiment, the software development management platform can also generate a requirement review report for the requirement analysis information based on the review opinions of at least one reviewer on the requirement analysis information. Among them, every time the requirement analysis information changes, the changed requirement analysis information will be reviewed, and a corresponding requirement review report needs to be generated.

[0148] Such as Figure 5 As shown, after obtaining the system requirement information returned by the MBSE platform in the ALM platform, it will be frozen first, and then the review of the system requirement information will be initiated. During the review process of the system requirement, a system requirement review report will be generated; moreover, after the system requirement information passes the scoring, the ALM platform will release the system requirement information that has passed the review, generate a system requirement specification, and at the same time, store the traceability information corresponding to the system requirement information.

[0149] Among them, the release notice of the system requirement information is used to instruct developers to perform system architecture design based on the system requirement information.

[0150] S205, the software development platform obtains the system architecture design model constructed by the developer based on the system requirement information and the traceability information corresponding to the system architecture design model, and sends the system architecture design model and its corresponding traceability information to the software development management platform.

[0151] The system architecture design model may include the interactions between the various hardware parts and components in the system, and it can characterize the relationships among hardware, software, and data streams.

[0152] Among them, the traceability information corresponding to the system architecture design model is used to characterize that the system architecture design model is obtained based on the system requirement information, and through this traceability information, the system requirement information referred to by the system architecture design model can be traced back.

[0153] In this application, there is no limitation on the specific implementation of the developer combining the system requirement information to build a system architecture design model on the software development platform and generating corresponding traceability information.

[0154] The following combines Figure 4 Taking one implementation as an example for a brief introduction, the developer (such as an architecture development engineer) combining the system requirement information can use SysML or UML language on the MBSE client to conduct system architecture design:

[0155] First, the developer determines the subsystems involved in the system architecture design. For example, taking the design of a vehicle lamp control system as an example, the architecture design can be carried out through a module definition diagram, dividing the system into two subsystems, namely the body controller and the instrument panel, and these two subsystems are connected to the vehicle's main control system.

[0156] Secondly, the developer respectively establishes descriptions of the static architecture, dynamic behavior subsystem ports based on the internal module diagram, refined activity diagram, and sequence diagram of SysML or UML language to obtain the system architecture design model.

[0157] In addition, the developer can also add the corresponding traceability information to the system architecture design model.

[0158] It can be understood that during the system architecture design process, the subsystem requirements of the subsystems may also be determined, as well as the traceability information between the subsystem requirements and the system requirement information. This application will also send the subsystem requirements and the traceability information of the subsystem requirements to the software development platform.

[0159] S206. The software development management platform records the review operations of at least one reviewer on the system architecture design model. When it is confirmed that the system architecture design model meets the system architecture design review requirements in the automotive software evaluation specification, based on the review process of the system architecture design model on the software development management platform, a system architecture design specification that complies with the automotive software evaluation specification is generated, and a release notice of the system architecture design model is sent to the software development platform.

[0160] Among them, the process of generating the system architecture design specification is similar to the process of generating the system requirements specification before, and will not be elaborated here.

[0161] It can be understood that when the system architecture design model meets the system architecture design model review requirements, this application will also store the second traceability information corresponding to the system architecture design model.

[0162] It can be understood that after the review of the system architecture design model, the software development management platform will also generate a system architecture design review report for the system user architecture design model based on the review opinions of at least one reviewer on the system architecture design model. As Figure 5 shown, after the ALM platform obtains the system architecture design model, the system architecture design model will be frozen to start the review of the system architecture design model. After the review of the system architecture design model, a system architecture design review report will be generated. Moreover, after the system architecture design model passes the review (that is, meets the requirements for the system architecture design model in the ASPICE specification), a system architecture design specification will also be generated, and the traceability information corresponding to the system architecture design model will be stored.

[0163] Among them, the release notice of the system architecture design model is used to instruct developers to analyze software requirements based on the system architecture design model.

[0164] S207. The software development platform obtains the software requirement information generated by the developer based on the system requirement information and the system architecture design model, as well as the traceability information corresponding to the software requirement information, and sends the software requirement information and the traceability information corresponding to the software requirement information to the software development management platform.

[0165] Among them, the traceability information corresponding to the software requirement information is used to indicate that the software requirement information is obtained based on the system requirement information and the system architecture design model.

[0166] Among them, there is no restriction on the process of the developer generating software requirement information on the software development platform.

[0167] For example, in combination with Figure 4Explanation: Developers (such as software requirements engineers) establish a software use case diagram in the MBSE platform based on system requirements information (or subsystem requirements information) and the system architecture design model, and derive software requirements information from the software use case diagram.

[0168] In addition, developers can also establish traceability information that includes the association relationships between this software requirements information, system requirements information, and the system architecture design model.

[0169] Among them, software requirements information is used to represent the specific functions that the software needs to implement. For example, software requirements information can describe the specific signals to be received, the execution actions triggered by the signals, the software components called by the execution actions, etc.

[0170] S208, the software development management platform records the review operations of at least one reviewer on this software requirements information. When it is confirmed that this software requirements information meets the software requirements review requirements in the automotive software assessment specification, based on the review process of this software requirements information on the software development management platform, a software requirements specification that meets this automotive software assessment specification is generated, and a release notice of this software requirements information is sent to the software development platform.

[0171] Among them, relevant information related to the review process of this software requirements information can be recorded in this software requirements specification, including but not limited to the number of updates of this software requirements information, the current version information, and the review time, etc.

[0172] Among them, the process of generating the software requirements specification is similar to the process of generating the system requirements specification before, and will not be elaborated here.

[0173] It can be understood that after reviewing the software requirements information, a software requirements review report of the software requirements information can also be generated based on the review opinions of at least one reviewer entered on the software development management platform for this software requirements information. This software requirements review can record information such as the reviewers of this software requirements information, the review opinions, and the review time, etc.

[0174] Among them, software requirements information can include multiple software requirements. Therefore, software requirements information can also be called software requirement items, and this software requirement item can include at least one software requirement.

[0175] For example, combined with Figure 4 and Figure 6 Explanation:

[0176] From Figure 4It can be seen that after developers generate software requirement diagrams using SysML or UML languages on the MBSE platform and finally obtain software requirement items, the MBSE platform sends the software requirement items to the ALM platform, and the ALM platform will perform corresponding processing using the software requirement module. The processing performed by the software requirement module can be referred to Figure 6 as shown.

[0177] As Figure 6 It can be seen that after the ALM platform receives the software requirement information, it sets the software requirement information to the frozen state to initiate the review of the software requirement information. After the reviewers review the software requirement information, the ALM platform will generate a software requirement review report. Moreover, after confirming that the software requirement information passes the review (i.e., meets the requirements review requirements for software requirement information in the ASPICE specification), the software requirement information will be released so that developers can perform subsequent development based on the released software requirement information.

[0178] Of course, if the software requirement information does not meet the review requirements, the ALM platform will also send abnormal instructions such as a review failure indication to the software development platform, so that developers can reconstruct the software requirement information that meets the requirements and repeat the operations in steps S207 and S208 above until the review requirements are met.

[0179] Among them, the release notice of the software requirement information indicates that the software requirement information meets the software requirement review requirements in the automotive software assessment specification, enabling developers to confirm that they can perform the next development operation based on this release notice. Therefore, this release notice is used to instruct developers to build a software architecture design model based on this software requirement information.

[0180] S209, the software development platform obtains the software architecture design model constructed by developers based on the software requirement information and the traceability information corresponding to the software architecture design model, and sends the software architecture design model and the traceability information corresponding to the software architecture design model to the software development management platform.

[0181] The software architecture design model includes software-related components, the interactions between components, and the interactions between components and the external environment.

[0182] Among them, there is no restriction on the implementation process for developers to build a software architecture design model and corresponding traceability information on the software development platform based on the software requirement information.

[0183] For example, in combination with Figure 4Explanation: Developers set software components based on software requirement information, and use module definition diagrams, internal block diagrams, sequence diagrams, activity diagrams, and state machine diagrams in SysML or UML languages to represent the static and dynamic behavior characteristics of the software, establish a software architecture design model, and add a traceability relationship between the software architecture design model and the software requirement information in the software architecture design model to obtain corresponding traceability information.

[0184] S210, The software development management platform records the review operations of at least one reviewer on the software architecture design model. When it is confirmed that the software architecture design model meets the software architecture design review requirements in the automotive software evaluation specification, based on the review process of the software architecture design model on the software development management platform, a software architecture design specification that meets the automotive software evaluation specification is generated, and the software architecture design model is sent to the terminal device of the target developer.

[0185] Among them, the software architecture design model is used to provide a basis for the target developer to develop software code.

[0186] Among them, the process of the software development management platform generating the software architecture design specification is similar to the process of generating the system requirement specification, which will not be elaborated here.

[0187] For example, Figure 6 Taking it as an example to illustrate, after obtaining the software architecture design model on the ALM platform, the software architecture design model is set to the frozen state to initiate the review of the software architecture design model. Based on the review opinions of the reviewers on the software architecture design model, a software architecture design review report can be generated. Moreover, after it is confirmed that the software architecture design model meets the corresponding review requirements in the ASPICE specification, the ALM platform can generate a software architecture design specification based on the review process of the software architecture design model.

[0188] Among them, the software architecture design specification can record the process information related to the reviewers' review of the software architecture design model, such as the current version information and the number of modifications of the software architecture design model, etc.

[0189] Among them, the target developer is the person who needs to perform software detailed design and code writing based on the software architecture design model.

[0190] After receiving the software architecture design model through the terminal device, the target developer can perform software detailed design and software unit construction work based on the software architecture design model, and finally obtain the software code information required for the software development project. For example, the target developer can generate software code information based on the software architecture design model using tools such as MATLAB, and the specific method is not limited.

[0191] S211, the software development management platform obtains the software code information returned by the target developer's terminal device, and stores the software code information and the association relationship between the software code information and the software development project.

[0192] Among them, the software code information may include information related to software code design such as software detailed design and software code units.

[0193] Among them, the association relationship between the software code information and the software development project is also the association relationship between the software code information and the software requirement information in the software development project. Based on this association relationship, the software architecture design model on which the software code information is based can be traced.

[0194] In this embodiment, the software development management platform and the software development platform can carry out relevant product development and control based on the automotive software evaluation specification, so that the software development management platform can obtain the development products required for each development stage in line with the automotive software evaluation specification, and obtain the traceability information between different development products in the entire development stage, so as to more reasonably realize software development control.

[0195] Such as Figure 3 As shown, in the system engineering development stage and the software engineering development stage, each time the MBSE platform feeds back the corresponding requirement information or architecture design model to the ALM platform, the traceability information corresponding to the requirement information and the architecture design model will be synchronously stored in the ALM platform, realizing the traceability of various information products in each stage of the software development process.

[0196] At the same time, based on the solution of this application, in software development control, the software development management platform can also obtain various document outputs required by the automotive software evaluation specification, so as to be able to promptly verify the cause of problems in the case of vulnerabilities in the developed software code information.

[0197] For example, taking the automotive software evaluation specification as the ASPICE specification, the software development management platform as the ALM platform, and the software development platform as the MBSE platform as an example, combined with the relevant introduction above Figures 3 to 6 it can be known that the document outputs obtained by the ALM platform and belonging to the requirements of the ASPICE specification can be seen in the following table:

[0198]

[0199] Among them, the traceability matrix in the above table is the manifestation form of the traceability information, that is, the traceability information represented in matrix form.

[0200] It can be understood that after the software development management platform obtains the software code information returned by the target developer's terminal device, the software development management platform can also set the software code information to the released state. Among them, when the software code information is in the released state, testers can test the software code information.

[0201] Correspondingly, the software development management platform can also obtain the test results obtained by the tester based on the software requirement analysis information, the software architecture design model, and the software code information, as well as the association relationship between the test results and the software development project.

[0202] Among them, there is no limit to the specific implementation of the tester's software testing based on the software requirement analysis information, the software architecture model, and the software code information.

[0203] Of course, the tester will also perform corresponding tests based on the system requirement information and the system architecture design, and upload the corresponding test results to the software development management platform.

[0204] Such as Figure 3 , the tester can build corresponding test cases based on the system requirement information, the system architecture design model, the software requirement information, the software architecture design model, etc. in the ALM platform and perform tests to obtain corresponding test results.

[0205] Corresponding to a software development control method of the present application, the present application also provides a software development control device. As Figure 7 , it shows a schematic diagram of a composition structure of the software development control device provided by the present application. The device can be applied to a software development management platform and includes:

[0206] The first acquisition unit 701 is used to acquire the development reference information required for the target development stage currently to be controlled in the software development project. The development reference information is the releasable information that has been confirmed to meet the review requirements in the automotive software evaluation specification before the target development stage. The target development stage belongs to multiple development stages required for software development in the automotive software evaluation specification;

[0207] The first release unit 702 is used to send a first release notice of the development reference information to the software development platform based on the modeling language. The first release notice is used to instruct the developer to perform requirement analysis for the target development stage based on the development reference information;

[0208] The second acquisition unit 703 is used to acquire the requirement analysis information of the target development stage returned by the software development platform;

[0209] A second publishing unit 704, configured to send a second publishing notice of the requirements analysis information to the software development platform when it is confirmed that the requirements analysis information meets the requirements review requirements in the automotive software evaluation specification, where the second publishing notice is used to instruct developers to perform architecture design in the target development stage based on the requirements analysis information;

[0210] A third obtaining unit 705, configured to obtain the architecture design model of the target development stage returned by the software development platform.

[0211] In a possible implementation manner, the software development control device further includes:

[0212] A first traceability obtaining unit, configured to obtain first traceability information returned by the software development platform while the second obtaining unit obtains the requirements analysis information, where the first traceability information is used to represent that the requirements analysis information is obtained based on the development reference information;

[0213] A second traceability obtaining unit, configured to obtain second traceability information returned by the software development platform while the third obtaining unit obtains the architecture design model, where the second traceability information is used to represent that the architecture design model is obtained based on the requirements analysis information.

[0214] In another possible implementation manner, the software switch control device further includes: an information feedback unit, configured to, after the third obtaining unit obtains the architecture design model, when it is confirmed that the architecture design model meets the architecture design review requirements in the automotive software evaluation specification, use the architecture design model as the development reference information required for the next development stage after the target development stage.

[0215] In another possible implementation manner, the software development control device further includes:

[0216] A first specification generating unit, configured to generate a requirements specification meeting the requirements in the automotive software evaluation specification based on the review process of the requirements analysis information on the software development management platform when it is confirmed that the requirements analysis information meets the requirements review requirements in the automotive software evaluation specification;

[0217] A second specification generating unit, configured to generate an architecture design specification meeting the requirements in the automotive software evaluation specification based on the review process of the architecture design model by reviewers on the software development management platform when it is confirmed that the architecture design model meets the architecture design review requirements corresponding to the automotive software evaluation specification;

[0218] A first report generation unit, configured to generate a requirements review report for the requirements analysis information based on review opinions of at least one reviewer on the requirements analysis information input on the software development management platform after a second acquisition unit acquires the requirements analysis information;

[0219] A second report generation unit, configured to generate an architecture design review report for the architecture design model based on review opinions of at least one reviewer on the architecture design model input on the software development management platform after a third acquisition unit acquires the architecture design model.

[0220] In another possible implementation, the software development control unit further includes: a project requirements acquisition unit, configured to acquire project requirements information of a software development project before a first acquisition unit acquires development reference information, where the project requirements information is used to describe product functions to be implemented;

[0221] The first acquisition unit includes:

[0222] A first information acquisition subunit, configured to determine the project requirements information as development reference information required in the system engineering development stage of the software development project if it is confirmed that the project requirements information meets the project requirements review requirements in the automotive software evaluation specification;

[0223] The second acquisition unit includes:

[0224] A first requirements acquisition subunit, configured to acquire system requirements information returned by the software development platform if the target development stage is the system engineering development stage;

[0225] The third acquisition unit includes:

[0226] A first model acquisition subunit, configured to acquire a system architecture design model returned by the software development platform if the target development stage is the system engineering development stage.

[0227] In another possible implementation, the first acquisition unit includes:

[0228] A second information acquisition subunit, configured to acquire the system architecture design model obtained in the system engineering development stage if the target development stage is the software engineering development stage;

[0229] The second acquisition unit includes:

[0230] A second requirements acquisition subunit, configured to acquire software requirements information returned by the software development platform if the target development stage is the software engineering development stage;

[0231] The third acquisition unit includes:

[0232] A second model acquisition subunit, configured to, if the target development stage is a software engineering development stage, acquire a software architecture design model returned by the software development platform.

[0233] In another possible implementation, the software development control device further includes:

[0234] A model sending unit, configured to, after the second model acquisition subunit acquires the software architecture design model, and when it is confirmed that the software architecture design model meets the software architecture design review requirements in the automotive software evaluation specification, send the software architecture design model to the terminal device of the target developer, where the software architecture design model is used to provide a basis for the target developer to develop software code;

[0235] A code acquisition unit, configured to acquire software code information returned by the terminal device of the target developer, and store the software code information and the association relationship between the software code information and the software development project.

[0236] In another possible implementation, the device further includes:

[0237] A code status setting unit, configured to, after the code acquisition unit acquires the software code information returned by the terminal device of the target developer, set the software code information to a released state, where, when the software code information is in the released state, testers can test the software code information;

[0238] A test result acquisition unit, configured to acquire the test result obtained by the tester based on the software requirement analysis information, the software architecture design model, and the software code information, and the association relationship between the test result and the software development project.

[0239] In an embodiment of the present application, an electronic device is further provided. The electronic device may be a server or other computer device, without limitation. The electronic device at least includes a processor and a memory;

[0240] The processor is configured to execute the software development control method described in any one of the above embodiments;

[0241] The memory is configured to store the program required for the processor to perform operations

[0242] Of course, the electronic device may further include a display unit, an input unit, etc., without limitation.

[0243] In an embodiment of the present application, a computer program product is further provided, including computer-readable instructions, which, when running on an electronic device, cause the electronic device to implement any one of the software development control methods provided in the embodiments of the present application.

[0244] In an embodiment of the present application, a computer-readable storage medium is further provided. The storage medium carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any software development control method provided by the embodiments of the present application.

[0245] In addition, it should be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, in the attached drawings of the device embodiments provided in the present application, the connection relationship between the modules indicates that they have a communication connection, which can be specifically implemented as one or more communication buses or signal lines.

[0246] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware. Of course, it can also be implemented by dedicated hardware including application-specific integrated circuits, dedicated CPUs, dedicated memories, dedicated components, etc. Generally, functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structures for implementing the same function can also be various, such as analog circuits, digital circuits or dedicated circuits. However, for the present application, in more cases, software program implementation is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a readable storage medium, such as a floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disc of a computer, etc., and includes several instructions for causing a computer device (which can be a personal computer, training device, or network device, etc.) to execute the methods described in the various embodiments of the present application.

[0247] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product.

[0248] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that includes one or more integrated available media. The available medium may be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Claims

1. A software development management and control method, characterized in that: Applied to software development management platform, including: Obtaining development reference information required for a target development stage to be currently controlled in a software development project, wherein the development reference information is releasable information that has been confirmed to meet review requirements in an automotive software assessment specification before the target development stage, and the target development stage belongs to a plurality of development stages required to be involved in software development in the automotive software assessment specification; Sending a first release notification of the development reference information to a software development platform based on a modeling language, wherein the first release notification is used to instruct a developer to perform a requirements analysis of the target development phase based on the development reference information; Obtaining demand analysis information of the target development stage returned by the software development platform; When confirming that the requirement analysis information meets the requirement review requirements in the automotive software assessment specification, sending a second release notification of the requirement analysis information to the software development platform, wherein the second release notification is used to instruct the developer to perform the architecture design of the target development phase based on the requirement analysis information; Obtaining the architecture design model of the target development stage returned by the software development platform.

2. The software development management and control method according to claim 1, characterized in that: While obtaining the demand analysis information of the target development stage returned by the software development platform, the method further includes: obtaining first traceability information returned by the software development platform, wherein the first traceability information is used to indicate that the demand analysis information is obtained based on the development reference information; While obtaining the architecture design model of the target development stage returned by the software development platform, it also includes: obtaining second traceability information returned by the software development platform, wherein the second traceability information is used to characterize that the architecture design model is obtained based on the demand analysis information.

3. The software development management and control method according to claim 1, characterized in that: After obtaining the architecture design model of the target development stage returned by the software development platform, the method further includes: When it is confirmed that the architecture design model meets the architecture design review requirements in the automotive software assessment specification, the architecture design model is used as development reference information required for the next development stage after the target development stage.

4. The software development management and control method according to claim 1, characterized in that: Also includes: In the case of confirming that the requirement analysis information meets the requirement review requirements in the automotive software assessment specification, generating a requirement specification that meets the requirements in the automotive software assessment specification based on the review process of the requirement analysis information on the software development management platform; In the case of confirming that the architecture design model meets the architecture design review requirements corresponding to the automotive software assessment specification, generating an architecture design specification that meets the requirements of the automotive software assessment specification based on the review process of the architecture design model by the reviewer on the software development management platform; After obtaining the demand analysis information of the target development stage returned by the software development platform, the method further includes: generating a requirement review report for the requirement analysis information based on a review opinion of the requirement analysis information input by at least one reviewer on the software development management platform; After obtaining the architecture design model of the target development stage returned by the software development platform, the method further includes: Based on the review opinions of the architecture design model input by at least one reviewer on the software development management platform, an architecture design review report of the architecture design model is generated.

5. The software development management and control method according to claim 1, characterized in that: Before you get the development reference information, also include: Obtaining project requirement information of a software development project, wherein the project requirement information is used to describe product functions that are desired to be achieved; The development reference information required for the target development stage of the software development project to be currently controlled includes: In the case of confirming that the project requirement information meets the project requirement review requirements in the automotive software assessment specification, determining the project requirement information as development reference information required for the system engineering development stage in the software development project; The obtaining of the demand analysis information of the target development stage returned by the software development platform includes: If the target development stage is a system engineering development stage, obtaining system requirement information returned by the software development platform; The obtaining of the architecture design model of the target development stage returned by the software development platform includes: If the target development stage is a system engineering development stage, a system architecture design model returned by the software development platform is obtained.

6. The software development management and control method according to claim 1 or 5, characterized in that: The development reference information required for the target development stage of the software development project to be currently controlled includes: If the target development stage is a software engineering development stage, obtaining a system architecture design model obtained in a system engineering development stage; The obtaining of the demand analysis information of the target development stage returned by the software development platform includes: If the target development stage is a software engineering development stage, obtaining software requirement information returned by the software development platform; The obtaining of the architecture design model of the target development stage returned by the software development platform includes: If the target development stage is a software engineering development stage, a software architecture design model returned by the software development platform is obtained.

7. The software development management and control method according to claim 6, characterized in that: After obtaining the software architecture design model returned by the software development platform, the method further includes: When confirming that the software architecture design model meets the software architecture design review requirements in the automotive software assessment specification, sending the software architecture design model to a terminal device of a target developer, wherein the software architecture design model is used to provide a basis for the target developer to develop software code; The software code information returned by the terminal device of the target developer is obtained, and the software code information and the association relationship between the software code information and the software development project are stored.

8. The software development management and control method according to claim 7, characterized in that: After obtaining the software code information returned by the terminal device of the target developer, the method further includes: Setting the software code information to a release state, wherein when the software code information is in the release state, a tester can test the software code information; The test results obtained by the tester based on the software requirement analysis information, the software architecture design model and the software code information test, as well as the correlation between the test results and the software development project are obtained.

9. A software development control device, characterized in that: Applied to software development management platform, including: A first obtaining unit is used to obtain development reference information required for a target development stage to be currently controlled in a software development project, wherein the development reference information is releasable information that has been confirmed to meet the review requirements in the automotive software assessment specification before the target development stage, and the target development stage belongs to a plurality of development stages required to be involved in software development in the automotive software assessment specification; A first publishing unit, configured to send a first publishing notification of the development reference information to a software development platform based on a modeling language, wherein the first publishing notification is used to instruct a developer to perform a requirements analysis of the target development phase based on the development reference information; A second obtaining unit is used to obtain the demand analysis information of the target development stage returned by the software development platform; A second publishing unit is used to send a second publishing notification of the demand analysis information to the software development platform when confirming that the demand analysis information meets the demand review requirements in the automotive software assessment specification, wherein the second publishing notification is used to instruct the developer to perform the architecture design of the target development stage based on the demand analysis information; The third obtaining unit is used to obtain the architecture design model of the target development stage returned by the software development platform.

10. A software development management and control system, characterized in that: include: Software development management platform and software development platform; Wherein, the software development management platform is used to execute the software development management and control method as described in any one of claims 1 to 8 above; The software development platform is at least used to feed back to the software development management platform the demand analysis information and architecture design model of the target development stage of the software development project to be currently managed.

Images