JP2019168881A - Software development apparatus - Google Patents

Abstract

An object of the present invention is to facilitate software unit version management in software development. The software unit includes software units (102, 103, 104, 105) included in a software file (101). The software units (102, 103, 104, 105) have identifiers for identifying the software units (102, 103, 104, 105). The software units 102, 103, 104, and 105 are extracted from the software file 101 by the identifier. [Selection diagram] Fig. 1

Description

  The present invention relates to a software development apparatus.

  Background arts in this technical field include Patent Document 1 (Japanese Patent Laid-Open No. 2015-162218), Patent Document 2 (Japanese Patent Laid-Open No. 09-258964), and Patent Document 3 (Japanese Patent Laid-Open No. 05-274121).

  In the summary column of Patent Document 1, “Create a control logic described in a graphic language. Generate a comment corresponding to each version of the control logic. A model file describing the control logic in binary format is stored in the version management system. According to the registration operation for registering in the repository, a comment is stored in the repository in association with each version of the model file. "

  In the summary column of Patent Document 2, “When the form DB and the version DB are interfaced and the system has a function of referring to each other in synchronization with each other, each time the software is changed or the form is registered / updated, both DBs Are updated at the same time, guaranteeing consistency between DBs, and enabling version management based on reports. "

  In the summary column of Patent Document 3, “when the program is updated, the component modules of all versions of the update target program are searched using the program identifier as a key in S2, and then the latest version of the module constituting the update target program is searched in S3. Thus, an update file is created in S4 and the program is updated. "

JP, 2015-162218, A JP 09-258964 A JP 05-274121 A

  In the software of the vehicle control device, the developed model is converted from the model into software of a format that can be incorporated into the microcomputer in order to be incorporated into the in-vehicle microcomputer (hereinafter, microcomputer). Even if there is a difference in the model, there may be no difference in the converted software. If there is no difference in the converted software, changing the version of the model managed by the form or file name complicates ensuring the consistency between the microcomputer and the software incorporated in the microcomputer.

  In the vehicle control device, set control constants such as a control constant for satisfying the vehicle performance and a control constant for OBD (On-Board Diagnostics) regulation are important. In the version management of these control constants, the simulation accuracy is improved by setting the control constants according to the actual operation in the simulation using the model. For this reason, control constants corresponding to software files and software units need to be managed as a unit.

  However, Patent Documents 1 to 3 do not consider these.

  Therefore, an object of the present invention is to facilitate software version management in software development.

  In order to solve the above-described problem, the present invention provides a software development device including a software unit included in a software file, wherein the software unit has an identifier for identifying the software unit, and the software is identified by the identifier. The software unit is extracted from the file.

  According to the present invention, version management of software units in software development can be facilitated.

Configuration diagram of configuration management system in an embodiment of the present invention Block diagram program (model) showing the relationship between software and software units File database configuration example Management procedure flow of configuration management method Version control table Version update conditions Control constant and configuration management system configuration diagram in vehicle control device Configuration management system configuration diagram when control constants in the vehicle control device are associated with each software unit Version registration procedure for control constants and software files in vehicle control equipment Combination of software file version and control constant version

  In vehicle embedded software, programming (hereinafter referred to as modeling) by drawing a block diagram is a common development method. In modeling, the required functions are simulated with the created block diagram program (hereinafter referred to as model), thereby reducing rework due to failure detection in downstream processes, reducing development man-hours, and improving quality. In the simulation, vehicle operations and control requests are confirmed by connecting software units, which are the minimum management units constituting the software file.

  In software development, when software is developed by multiple people, it is necessary to manage the software configuration (version management) in order to avoid conflicts, ease software management, and support traceability of functional safety standards. . Therefore, it is common to use a configuration management tool in order to prevent human errors in configuration management and to improve efficiency.

  File management developed by modeling includes folder management on a shared server and a method of managing file names by assigning version information. Numbering methods include manual acquisition using a form. As a management granularity, a method of managing versions of each model divided into control units using a configuration management tool is often used.

In the program development by modeling, it is possible to confirm the required specifications in the upstream process of software development by simulation using the model. Large models are realized by combining multiple software units. When diverting software, both model file units and software unit units are used, and it is necessary to manage version of software units as well as model file units. When file management is performed using a configuration management tool or a folder, and version information is assigned to a file name, management is performed in units of files, so the level of detail of management granularity is insufficient.
Based on this, embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a configuration diagram of a configuration management system in an embodiment of the present invention. In FIG. 1, the software file 101 is stored in the file database 106, and version update determination is performed in order to perform version management of the software file 101 and the software units 102, 103, 104, and 105 that are the minimum management units constituting the software file 101. The unit 107 is activated. The version update determination unit 107 acquires version information from the version management table 108 that manages the versions of the software file 101 and the software units 102 to 105, and the software file 101 and the software units 102 to 102 are acquired based on the version update condition 109. It is determined whether the version 105 is updated.

  FIG. 2 is an example of a block diagram program (model) showing the relationship between software and software units. In the present embodiment, the description will be given below using a model, but the present invention can also be applied to software described in other formats. In FIG. 2, a model 201 that is a software file is composed of four software units 202, 203, 204, and 205, and the software units 202, 203, 204, and 205 include four arithmetic operators and logical operators. (An example is block 206). The software units 202, 203, 204, and 205 are identified by a naming rule (an identifier that identifies a software unit) 207. In FIG. 2, “_unit” (part of the identifier) is appended to the end of the software unit name as an example. In this embodiment, the unit extracted by the naming rule is the software unit that is the minimum management unit of the software file, but it can also be applied to other management units.

  FIG. 3 is a configuration example of a file database. In FIG. 3, the file database 106 includes a plurality of repositories, a repository A 301 and a repository B 302. The repository A301 includes a plurality of directories such as a directory A303 and a directory B304, and a model A305 and a model B306 are stored in the directory A303. The latest version of the model A305 is “Ver.012”, and the old version (“Ver.011” and the like) is also stored in the directory A303 like the latest version.

  FIG. 4 is a management flow of the configuration management method.

  In step 401, the software developer modifies the software file.

  In step 402, the configuration management tool is requested to register in the file database in order to acquire the version of the changed software file and store it in the file database.

  In step 403, software units are extracted from the software file requested to be registered based on a preset naming rule.

  In step 404, a tool for performing version update determination is automatically activated.

  In step 405, a version update condition registered in advance is acquired. In the following steps, an example of updating the version when the version update condition is met will be described.

  In step 406, the software version is obtained from the version update table.

  In step 407, based on the information in the version update table, the software file to which the version is assigned is acquired from the file database.

  In step 408, it is determined whether the difference between the software requested for registration in step 402 and the software acquired in step 407 corresponds to the version update determination acquired in step 405. If it is determined that there is a version update, the process proceeds to step 409. If it is determined that there is no version update, the process proceeds to step 410.

  In step 409, the software version determined to be updated in step 408 is numbered from the information in the version management table, and the software version is reflected in the version management table.

  In step 410, the software file requested to be registered in step 402 is stored in a file database.

  FIG. 5 shows an example of the version management table. 5, the version management table includes a software file 501 (model A in FIG. 5) and a software unit 502 belonging to the software file 501. The version 503 of the software file 501 is changed from the base version 504 (the parent version in FIG. 5) of the version 503. The version 505 of the software unit 502 belonging to the software file 501 is described for each version 503 of the corresponding software file 501. For example, when the version 503 of the software file 501 is “10B”, the version 505 of the software unit “DDD_unit” is “Ver.040”.

  FIG. 6 shows an example of version update conditions. At the time of software version update determination, if the only difference from the base software is the version update exclusion condition group 601, the software version is not updated. The version update exclusion condition group 601 includes a plurality of version exclusion conditions including a version update exclusion condition 1 602, a version update exclusion condition 2 603, and a version update exclusion condition 604. Further, when the software version is updated, if the difference from the base software corresponds to the version update condition group 605, the software version is updated. Similarly to the version exclusion condition group 601, the version update condition group 605 includes a plurality of conditions of version update conditions 606, 607, and 608.

  Next, Example 2 will be described with reference to FIGS. 7, 8, 9, and 10.

  FIG. 7 is a control constant and configuration management system configuration diagram in the vehicle control device. In FIG. 7, a control constant 701 is a file corresponding to the software file 101 and is stored in the file database 106. The version of the control constant 701 is managed by the version management table 108. Further, the version corresponding to the combination 702 of the software file 101 and the control constant 701 is also managed by the version management table 108.

  FIG. 8 is a configuration management system configuration diagram in the case where control constants in the vehicle control device are associated with each software unit. In FIG. 8, a control constant 801 is a file corresponding to the software unit 102 belonging to the software file 101 and is stored in the file database 106. The version of the control constant 801 is managed by the version management table 108. Further, the version corresponding to the combination 802 of the software unit 102 and the control constant 801 is also managed by the version management table 108.

  FIG. 9 shows a control constant and software file version registration procedure in the vehicle control apparatus. Here, the case where the control constant is associated with the software file will be described, but the same applies when the control constant is associated with the software unit. In FIG. 9, the procedure from step 401 to step 410 is the same as that in the first embodiment, and a description thereof will be omitted.

  In step 901, the version information of the control constant is acquired from the version management table.

  In step 902, it is confirmed whether the combination of the software file version reflected in the version management table in step 409 and the control constant version acquired in step 901 is already registered in the version management table. If the combination version has already been registered in the version management table, the version update process ends. If the combination version is not registered in the version management table, the process proceeds to step 903.

  In step 903, the combination version of the software file version reflected in the version management table in step 409 and the control constant version acquired in step 901 is reflected in the version management table.

  FIG. 10 is a version management table for a combination of software file version and control constant version. There are as many combination versions 1001 as there are combinations of software version 1002 and control constant version 1003. For example, when the software version is 10B and the control constant version is 040, the combination version is 10B040. The combination version is set to be unique.

According to each of the above embodiments, a software development device including a software unit included in a software file, the software unit having an identifier for identifying the software unit, and the software file is identified from the software file by the identifier. Units are extracted.
That is, in software configuration management, a software unit is discriminated in a file having a plurality of software units by assigning a name (identifier) based on a naming rule to a minimum management unit (software unit) constituting the software. be able to.

  A version update condition that is a condition for updating the version of the software file and the version information of the software unit, and if the difference between the software file and the software unit corresponds to the version update condition, Update the version of the software unit.

  A version update condition that is a condition for updating the version of the software file and the version information of the software unit, and if the difference between the software file and the software unit corresponds to the version update condition, Do not update the version of the software unit.

  In addition, a version management table defining a version of the software file and version information of the software unit is provided, and the version of the software file is managed by updating the software version management table.

  In addition, it has a database for storing the software file, and updates the software version management table to register the corresponding version of the software file in the database.

  A management version for managing a combination of the software file version and the control constant version corresponding to the software file, and the software file version or the control constant version corresponding to the software file is updated; The management version is updated.

  The software unit version and the control constant version corresponding to the software unit are managed in a version management table, and the combination of the software unit version and the control constant version corresponding to the software unit is managed. When the version of the software unit or the version of the control constant corresponding to the software unit is updated, the management version is updated.

  As described above, by analyzing the structure of the software unit based on the upgrade conditions, version management for each software unit can be performed.

DESCRIPTION OF SYMBOLS 101 Software file, 102 Software unit A, 103 Software unit B, 104 Software unit C, 105 Software unit D, 106 File database, 107 Version update determination part, 108 Version management table, 109 Version update condition, 201 Software file, 202- 205 software unit, 206 control block, 207 software unit naming convention, 301 repository A, 302 repository B, 303 directory A, 304 directory B, 305 model A, 306 model B, 501 software file name, 502 software unit name list, 503 Software file version, 504 Base software version, 5 05 Software Unit Version List, 601 Version Update Exclusion Condition Group Example, 602 Version Update Exclusion Condition 1, 603 Version Update Exclusion Condition 2, 604 Version Update Exclusion Condition, 605 Version Update Condition Group Example, 606 Version Update Condition 1, 607 Version update condition 2, 608 Version update condition, control constant corresponding to 701 software file, combination of 702 software file and control constant, control constant corresponding to 801 software unit, combination of 802 software unit and control constant, 1001 software file Control constant combination version, 1002 Software file version, 1003 Control constant version

Claims (7)

A software development device having a software unit included in a software file,
The software unit has an identifier for identifying the software unit, and the software unit is extracted from the software file by the identifier. A version update condition that is a condition for updating the version of the software file and the version information of the software unit;
The software development apparatus according to claim 1, wherein when the difference between the software file and the software unit corresponds to the version update condition, the version of the software file and the software unit is updated. A version update condition that is a condition for updating the version of the software file and the version information of the software unit;
2. The software development apparatus according to claim 1, wherein when the difference between the software file and the software unit corresponds to the version update condition, the version of the software file and the software unit is not updated. A version management table that defines a version of the software file and version information of the software unit;
The software development apparatus according to claim 2 or 3, wherein the software version management table manages the version of the software file by updating the software version management table. Having a database for storing the software files;
The software development apparatus according to claim 4, wherein the software file of the corresponding version is registered in the database by updating the version management table. A management version for managing a combination of the version of the software file and the version of the control constant corresponding to the software file;
6. The software development apparatus according to claim 5, wherein the management version is updated when a version of the software file or a version of a control constant corresponding to the software file is updated. Managing the version of the software unit and the version of the control constant corresponding to the software unit in a version management table;
A management version that manages a combination of the version of the software unit and the version of the control constant corresponding to the software unit;
The software development apparatus according to claim 5, wherein the management version is updated when the version of the software unit or the version of a control constant corresponding to the software unit is updated.

Images