JP2021068021A - Extraction device, and extraction program - Google Patents

Abstract

To provide an extraction device which suitably extracts an inspection item of an application transplanted from other devices.SOLUTION: An extraction device extracts new inspection items of a target application in a new device in which the target application operates (S205), from among a plurality of old inspection items of the target application in an old device in which the target application operates (S200). Here, the item indicating information on hardware and/or software in the old device and the new device, and corresponding to each old inspection item is considered as a determination item. The extraction device acquires information indicated by the determination item in the old device and information indicated by the determination item in the new device (S215), and determines whether or not these pieces of information match (S225). Then, the old inspection item corresponding to the determination item in which it is determined that the information do not match, is extracted as the new inspection item (S230).SELECTED DRAWING: Figure 13

Description

The present disclosure relates to a technique for extracting inspection items of an application ported from another device.

In the development of an ECU mounted on a vehicle, the functions of a plurality of ECUs may be integrated into one ECU in order to reduce costs, optimize functions, and the like. Specifically, it is conceivable to port a plurality of applications (hereinafter referred to as applications) installed in each ECU before integration and operate these applications in parallel in one integrated ECU. ..

In such a case, it is necessary to inspect whether the application operating on the integrated ECU operates in the same manner as before the integration. However, in the inspection, it is not necessary to carry out all the inspection items of the application performed in the ECU before the integration, and it is necessary to extract the necessary inspection items from the inspection items before the integration.

Here, Patent Document 1 discloses a device that automatically generates an inspection program for a circuit block of an ECU based on the difference in the circuit diagram before and after the change of the ECU. Specifically, the apparatus deletes the part corresponding to the difference between the circuit diagrams before and after the change from the inspection program corresponding to the circuit diagram before the change, and reads the inspection program corresponding to the difference from the database. Then, by adding the read inspection program to the inspection program from which the difference has been deleted, an inspection program corresponding to the changed circuit diagram is generated.

Japanese Unexamined Patent Publication No. 2000-249736

However, when the application is ported from the ECU before the integration to the ECU after the integration, it is necessary to re-examine the operation of the application related to the difference between these ECUs. Therefore, even if the inspection program corresponding to the difference between the circuit diagrams before and after the change is replaced as in the technique disclosed in Patent Document 1, necessary items are suitably extracted from the inspection items of the ECU before integration. It is thought that it cannot be done.

An object of the present disclosure is to suitably extract inspection items.

The extraction device (40) of one aspect of the present disclosure is a target application from a plurality of old inspection items (60 to 69) which are inspection items of the target application in the old device (30) in which the target application (34) operates. Extracts new inspection items that are inspection items of the target application in the new device (10) in which is operated. The extraction device includes acquisition units (S100, S200), determination units (S105 to S130, S205), and extraction units (S150, S155, S225, S230). The acquisition unit is an item indicating information on hardware and / or software in the old device and the new device, and the item corresponding to each old inspection item is set as a judgment item, and the information indicated by the judgment item in the old device and the new one. Acquires the information indicated by the determination item in the device. Further, the determination unit determines whether or not the information indicated by the determination item in the old device matches the information indicated by the determination item in the new device. In addition, the extraction unit extracts the old inspection items corresponding to the determination items determined to be inconsistent by the determination unit as new inspection items.

According to the above configuration, a judgment item indicating information on hardware and / or software is provided, and if the information indicated by the judgment item in the old device and the new device is different, the old inspection corresponding to the judgment item is provided. Items are extracted as new inspection items. Therefore, the old inspection items related to the differences in hardware and software between the old device and the new device can be automatically extracted as new inspection items. Therefore, the inspection items can be suitably extracted.

An extraction program that operates the computer as the extraction device may be configured. The same effect can be obtained by operating the computer according to such an extraction program.

In addition, the reference numerals in parentheses described in this column and the claims indicate the correspondence with the specific means described in the embodiment described later as one embodiment, and limit the technical scope of the present disclosure. It's not something to do.

It is a block diagram of the integrated ECU. It is a block diagram of the ECU before integration. It is a block diagram of an extraction device. It is explanatory drawing about an inspection process and an inspection viewpoint. It is explanatory drawing of the environment type, the environment item, the environment information, and the related information shown in the environment information file of the pre-integration ECU. It is explanatory drawing of the environment type, the environment item, the environment information, and the related information shown in the environment information file of the integrated ECU. It is explanatory drawing of the inspection process file. It is a flowchart of an inspection process extraction process. It is a flowchart of an inspection process extraction process. It is explanatory drawing of the constraint item and the constraint information which the constraint information file of the pre-integration ECU shows. It is explanatory drawing of the constraint item and the constraint information which the constraint information file of the integrated ECU shows. It is explanatory drawing of the inspection viewpoint file. It is a flowchart of inspection viewpoint extraction processing.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.
[1. About ECU integration]
There is known a technique for integrating the functions of a plurality of ECUs mounted on a vehicle (hereinafter referred to as the pre-integration ECU) into one ECU shown in FIG. 1 (hereinafter referred to as the post-integration ECU 10). As an example, the post-integration ECU 10 of the present embodiment is configured to operate a plurality of applications operating in each of the plurality of pre-integration ECUs including the pre-integration ECU 30 shown in FIG. The application in the pre-integration ECU that operates in the post-integration ECU 10 is also called a VM (Virtual Machine).

As shown in FIG. 1, the hardware (hereinafter, HW) 11 of the microcontroller mounted on the ECU 10 after integration includes two CPUs 12 and a memory. Further, the HW 11 has a communication function with another ECU and a wireless or wired communication function with a device brought into the vehicle from the outside. Specifically, the HW 11 is configured to perform communication in accordance with CAN (registered trademark) or Ethernet (registered trademark) with an external device such as an ECU as an example.

Further, the integrated ECU 10 is equipped with a hypervisor 20, OS 21, apps 22, 23, Adaptive PF / OS 24, a container 25, and apps 26, 27. By executing these software loaded in the memory, the CPU 12 realizes the function of the ECU 10 after integration.

The post-integration ECU 10 integrates four pre-integration ECUs as an example, and the applications 22, 23, 26, and 27 are ported as VMs from each pre-integration ECU without changing their functions. is there.

Further, OS21 and Adaptive PF / OS24 are software platforms conforming to a predetermined standard, and have a function as an OS. The OS 21 operates the applications 22 and 23, and the Adaptive PF / OS 24 operates the applications 26 and 27. Note that OS21 and Adaptive PF / OS16 correspond to, for example, basic software (hereinafter, BSW) in an in-vehicle software platform compliant with AUTOSAR or the like.

Further, the hypervisor 20 and the container 25 allocate resources to the VMs and arbitrate the operation of each VM. In the present embodiment, as an example, the hypervisor 20 treats each of the OS 21 and the Adaptive PF / OS 24 as a VM and mediates them. Further, the container 25 treats the applications 26 and 27 as VMs and mediates them.

On the other hand, the application 27 is transplanted from the pre-integration ECU 30 shown in FIG. Hereinafter, the application will also be referred to as a target application 27. As shown in FIG. 2, the HW31 of the microcontroller mounted on the pre-integration ECU 30 includes one CPU 32 and a memory. Further, the HW 31 is configured to perform CAN or Ethernet compliant communication with an external device as an example.

Further, the microcontroller is equipped with an Adaptive PF / OS 33 corresponding to the BSW and a target application 34 to be transplanted to the ECU 10 after integration. The target application 34 is configured as an application that operates on the Adaptive PF / OS 33. The function of the pre-integration ECU 30 is exhibited by the CPU 32 operating these software loaded in the memory.

[2. Extractor]
The applications 22, 23, 26, and 27 of the post-integration ECU 10 are transplanted from the pre-integration ECU, and it has already been confirmed by the inspection performed in the pre-integration ECU that they operate normally. Therefore, in the inspection of the applications 22, 23, 26, and 27 of the post-integration ECU 10, among the plurality of inspection items performed on these applications in the pre-integration ECU, only the inspection items that may be affected by the integration are performed. Suitable. The inspection item means a set of one or a plurality of inspection procedures for inspecting the operation of the application. That is, the inspection procedure of the application performed in the pre-integration ECU belongs to any of the inspection items.

The extraction device 40 of the present embodiment has the applications 22, 23, which should be performed in the post-integration ECU 10 from among a plurality of old inspection items which are the inspection items of the apps 22, 23, 26, 27 performed in each pre-integration ECU. New inspection items, which are inspection items of 26 and 27, are extracted (see FIG. 3). The extraction device 40 is configured as a PC as an example, and includes a CPU 41, a memory 42, a storage unit 43, a user I / F 44, a display 45, and a communication unit 46.

The memory 42 is a semiconductor memory configured as a ROM, RAM, or the like, and the CPU 41 executes software stored in the ROM or software loaded in the RAM.

The storage unit 43 is composed of, for example, an HDD or the like, and stores software executed by the CPU 41 and various data.
The user I / F44 includes a keyboard, a mouse, and the like, and outputs a signal corresponding to the operation received from the user to the CPU 41.

The display 45 displays an image generated by the CPU 41.
The communication unit 46 accesses a network such as the Internet in response to an instruction from the CPU 41, and communicates with another device.

In this embodiment, an OS and an application (hereinafter, an extraction program) that operates the PC as an extraction device 40 are installed on the PC. That is, the extraction program is stored in the storage unit 43, and the CPU 41 operates the extraction program loaded from the storage unit 43 into the memory 42 on the OS, so that the PC operates as the extraction device 40. In this case, the memory 42 corresponds to an example of a non-transitional substantive recording medium. In addition, when the extraction program operates, the method corresponding to the extraction program is executed. The extraction device 40 may be configured not as a PC but as a dedicated device for extracting new inspection items. At this time, the function as the extraction device 40 may be realized by using hardware configured by a dedicated electronic circuit.

In the following, as an example, the extraction device 40 extracts a new inspection item to be performed in the inspection of the target application 27 in the post-integration ECU 10 from the old inspection items of the target application 34 performed on the pre-integration ECU 30. The processing of the case will be described. Of course, the extraction device 40 also extracts new inspection items for apps 22, 23, and 26 other than the target application 27 in the same manner as in the following description.

[3. About old inspection items]
The inspection of the target application 34 in the pre-integration ECU 30 is performed stepwise over a plurality of inspection processes (see FIG. 4). Each inspection process corresponds to the old inspection item. Specifically, the inspections of the target application 34 are software unit test 60, software integration test 61, software function confirmation test 62, system integration test (BSW) 63, system integration test (HW) 64, and system function test 65. Two inspection processes are performed in that order.

As the inspection process progresses, the scope of inspection will gradually increase. That is, the software unit test 60, the software integration test 61, and the software function confirmation test 62 are inspection processes for confirming the operation of the target application 34 alone. More specifically, in the software unit test 60, the operation of each of the plurality of units constituting the target application 34 is inspected. Further, in the software integration test 61, the coordinated operation of the plurality of units is inspected, and in the software function confirmation test 62, the overall operation of the target application 34 is inspected.

Further, in the system integration test (BSW) 63, the operation of the target application 34 on the BSW (in other words, Adaptive PF / OS33) is inspected, and in the system integration test (HW) 64, the target application 34 on the HW 32 is inspected. Operation is inspected. Further, in the system function test 65, the operation of the target application 34 on the BSW and the HW 32 is inspected.

Further, in each inspection process, the operation of the target application 34 is inspected by a plurality of old inspection items that are performed focusing on different inspection viewpoints. As an example, in the system integration test (BSW) 63, old inspection items from the inspection viewpoint such as memory 66, communication 67, CPU cycle 68, and security 69 are provided (see FIG. 4). In these old inspection items, the functions related to the inspection viewpoint related to the old inspection item are inspected.

[4. Extraction method of new inspection items]
First, the extraction device 40 extracts the inspection process to be performed in the ECU 10 after integration as a new inspection item from the above-mentioned six inspection processes. In other words, the extraction device 40 determines which stage of the inspection process should be performed. After that, the extraction device 40 extracts the old inspection items of the inspection viewpoint to be inspected by the integrated ECU 10 as new inspection items from the old inspection items of each inspection viewpoint in the extracted inspection process. That is, from the inspection viewpoints in the extracted inspection process, the inspection viewpoints to be inspected by the integrated ECU 10 are extracted.

Specifically, the extraction device 40 extracts the inspection process and the inspection viewpoint based on the determination items. The determination item indicates information about HW and / or software in the post-integration ECU 10 and the pre-integration ECU 30. In other words, the determination item indicates the operating environment of the target application in the post-integration ECU 10 and the pre-integration ECU 30. Further, the determination item corresponds to at least one old inspection item (that is, an inspection process or an inspection viewpoint) in which an inspection related to the information indicated by the determination item is performed. In addition, each old inspection item corresponds to any judgment item.

Then, the extraction device 40 acquires the information indicated by the determination item in the pre-integration ECU 30 and the information indicated by the same determination item in the post-integration ECU 10, and determines whether or not these information match. Then, the old inspection item corresponding to the determination item determined to be inconsistent is extracted as the new inspection item.

That is, if the information indicated by the determination items does not match, the part of the HW and / or software of the integrated ECU 10 related to the determination item has changed from the pre-integration ECU 30. Then, due to the change, the operation of the target application in the integrated ECU 10 may change with respect to the operation in the pre-integrated ECU 30. In order to inspect whether such a change has occurred in the target application of the integrated ECU 10 and whether the change interferes with the function of the target application in the integrated ECU 10, it corresponds to the determination items judged to be inconsistent. The old inspection item to be used is extracted as a new inspection item.

[5. Inspection process extraction method]
Extraction of the inspection process is performed using a determination item (hereinafter, environmental item) indicating BSW information or HW information. That is, the environment item and the information indicated by the environment item (hereinafter, environment information) are classified into any type of BSW information and HW information (hereinafter, environment type). The BSW information is information related to the BSW for operating the target application in the pre-integration ECU 30 and the post-integration ECU 10. On the other hand, the HW information is information about the HWs 31 and 11 for operating the software in the pre-integration ECU 30 and the post-integration ECU 10.

Here, a file showing the environmental information of each of the pre-integration ECU 30 and the post-integration ECU 10 is referred to as an environment information file (FIGS. 5 and 6). The environment information file has the environment information indicated by each environment item and the information indicating the environment type of each environment item. In addition, the environmental information file has related information corresponding to each environmental item (in other words, environmental information). The related information indicates whether or not the environmental information corresponding to the related information is related to the operation of the target application, in other words, whether or not it affects the operation of the target application. Hereinafter, the fact that the environmental information is related to the operation of the target application is described as "related", and the fact that the environmental information is not related to the operation of the target application is described as "unrelated". In addition, the environmental item indicating the environmental information that is "related" is also described as the target environmental item.

In this embodiment, as an example, at least "peripheral" and "number of cores" are used as environmental items classified into HW information. Further, at least "OS type", "version", and "presence / absence of ara" are used as environment items classified into BSW (see FIGS. 5 and 6). The peripheral refers to a communication standard for a communication function provided by HW. The number of cores indicates the number of CPU cores provided in the HW. The OS type indicates the type of OS corresponding to BSW. The version indicates the version of BSW. The presence or absence of ara indicates whether or not a function called ara is provided in the BSW.

The environment information file is provided corresponding to each of the pre-integration ECU 30 and the post-integration ECU 10. Further, each environmental information is extracted by the user from, for example, the specifications of the pre-integration ECU 30 and the post-integration ECU 10, and it is determined whether or not each environmental information is related to the operation of the target application. Then, based on these, each environment information file is generated when the user operates a PC or the like to set the environment information and the related information of each environment item.

On the other hand, each inspection process is defined as having or not being associated with at least one environment type (see FIG. 7). In the inspection process related to the BSW information, the operation of the target application on the BSW is inspected, and the inspection result in the inspection process is affected by the BSW. That is, if the BSW is changed, the inspection result of the target application in the inspection process may change. On the other hand, in the inspection process related to HW information, the operation of the target application on the HW is inspected, and the inspection result in the inspection process is affected by the HW. That is, if the HW is changed, the inspection result of the target application in the inspection process may change. On the other hand, the inspection results in the inspection process unrelated to the environment type are not affected by BSW and HW. That is, even if the BSW and HW are changed, the inspection result of the target application in the inspection process does not change.

More specifically, the inspection process corresponds to all environmental items classified into the environmental types associated with the inspection process. And the inspection process that is not related to the environment type does not correspond to any environment item.

In this embodiment, as an example, the software unit test 60, the software integration test 61, and the software function confirmation test 62 are not related to the environment type. Further, the system integration test (BSW) 63 is associated with BSW information, the system integration test (HW) 64 is associated with HW information, and the system function test 65 is associated with BSW information and HW information.

Hereinafter, a file containing information indicating whether or not each inspection process is related to the environment type will be referred to as an inspection process file. The extraction device 40 extracts the inspection process based on the environmental information files 50 and 51 of the pre-integration ECU 30 and the post-integration ECU 10 and the inspection process file 52 (see FIG. 1).

[6. Inspection process extraction process]
Next, the inspection process extraction process in which the extraction device 40 extracts the inspection process will be described (see FIGS. 8 and 9). This process is executed in response to an instruction from the user.

In S100, the CPU 41 of the extraction device 40 acquires the environmental information files 50 and 51 of the pre-integration ECU 30 and the post-integration ECU 10 and the inspection process file 52, respectively. The CPU 41 may acquire these files from another PC via the communication unit 46, or may acquire these files from a storage medium temporarily connected to the extraction device 40.

In S105, in the CPU 41, the environment information of the environment item (in other words, the target environment item) indicating that the environment type is HW information and the corresponding related information is "related" is the pre-integration ECU 30 and the post-integration ECU 10. It is determined whether or not all of them match. Then, when an affirmative determination is obtained (S105: Yes), the CPU 41 turns on the match flag corresponding to the HW information (S115), and shifts to S120. If a negative determination is obtained (S105: No), the CPU 41 turns off the match flag (S110) and shifts to S120.

In the examples shown in FIGS. 5 and 6, the environmental information indicated by the "peripheral" whose related information is "related" does not match between the pre-integration ECU 30 and the post-integration ECU 10. Therefore, the match flag corresponding to the HW information is turned on.

In S120, in the CPU 41, the environment information of the environment item (in other words, the target environment item) indicating that the environment type is BSW information and the corresponding related information is "related" is the pre-integration ECU 30 and the post-integration ECU 10. It is determined whether or not all of them match. Then, when an affirmative determination is obtained (S120: Yes), the CPU 41 turns on the match flag corresponding to the BSW information (S130), and shifts to S135. If a negative determination is obtained (S120: No), the CPU 41 turns off the match flag (S125) and shifts to S135.

In the examples shown in FIGS. 5 and 6, the information related to the "version" in the BSW information is "not related". Therefore, it is determined whether or not the "environmental information" matches with respect to the "environmental items" other than the "version".

In S135, the CPU 41 selects one of the inspection processes that has not been determined to be extracted / not extracted, and then reads out the environment type related to the selected inspection process from the inspection process file 52 (S140).

In the following S145, the CPU 41 determines whether or not there is an environment type related to the selected inspection process, and if there is no environment type (S145: Yes), the process proceeds to S160, and one of the environment types (S145: No), the process proceeds to S150.

In S150, the CPU 41 determines whether or not all the matching flags corresponding to the related environment types are ON, and if a positive determination is obtained (S150: Yes), the process proceeds to S160 and a negative determination is made. (S150: No), the process proceeds to S155.

In S155, the CPU 41 sets the selected inspection process to "re-inspection required" and extracts the inspection process as a new inspection item. That is, if the environmental information indicated by at least one of the target determination items classified into the environment type related to the inspection process does not match between the post-integration ECU 10 and the pre-integration ECU 30, the inspection process is regarded as a new inspection item. Be extracted. On the other hand, in S160, the CPU 41 sets the selected inspection process to "re-inspection unnecessary" and does not extract the inspection process as a new inspection item.

In S165, which is performed following S155 or S160, the CPU 41 determines whether or not the extraction / non-extraction determination has been made for all the inspection processes. Then, the CPU 41 ends this process when a positive determination is obtained (S165: Yes), and proceeds to S135 when a negative determination is obtained (S165: No).

[7. Extraction method of inspection viewpoint]
Extraction of the inspection viewpoint is performed using a determination item (hereinafter, restriction item) indicating constraint information that can restrict the operation of the target application. More specifically, the constraint information may be information about an event that can restrict the operation of the target application, which occurs when the target application operates together with another application. That is, the constraint information may be information about software and / or HW resources assigned to the target application.

Here, a file showing the constraint information of each of the pre-integration ECU 30 and the post-integration ECU 10 is referred to as a constraint information file (FIGS. 10 and 11). The constraint information file has constraint information indicated by each constraint item used for extracting the inspection viewpoint. In this embodiment, as an example, at least "memory isolation", "communication bandwidth", "core division", and "peripheral used" are used as constraint items.

“Memory isolation” indicates whether or not a dedicated memory area is allocated as the memory area used by the target application. As an example of the constraint information indicated by "memory isolation", "isolation for each application" is provided in which a dedicated memory area is allocated to each application. The "communication band" indicates the communication speed when the target application communicates with an external device. Further, the “core division” indicates how often the CPU execution cycle is allocated when the target application is executed. When the CPU execution cycle is always assigned to the target application, the "core division" indicates the constraint information of "no division". The "peripheral used" indicates a communication standard for communication between the target application and an external device.

The constraint information file is provided corresponding to each of the pre-integration ECU 30 and the post-integration ECU 10. Further, each constraint information is extracted by the user from the specifications of the pre-integration ECU 30 and the post-integration ECU 10. Then, based on this, each constraint information file is generated when the user operates a PC or the like to set the constraint information of each constraint item.

Then, each inspection viewpoint (more specifically, the inspection item of each inspection viewpoint) is determined whether or not it corresponds to at least one constraint item (see FIG. 12). In the inspection item from the inspection viewpoint corresponding to the constraint item, the inspection related to the constraint item is performed. On the other hand, in the inspection item from the inspection viewpoint that does not correspond to the constraint item, the inspection not related to any of the constraint items is performed.

Hereinafter, a file containing information indicating whether or not each inspection viewpoint corresponds to the constraint information will be referred to as an inspection viewpoint file. The extraction device 40 extracts the inspection viewpoint based on the constraint information files 53 and 54 of the pre-integration ECU 30 and the post-integration ECU 10 and the inspection viewpoint file 55 (see FIG. 1).

[8. Inspection viewpoint extraction process]
Next, the inspection viewpoint extraction process in which the extraction device 40 extracts the inspection viewpoint will be described (see FIG. 13). This process is executed in response to an instruction from the user.

In S200, the CPU 41 of the extraction device 40 acquires the constraint information files 53 and 54 of the pre-integration ECU 30 and the post-integration ECU 10, and the inspection viewpoint file 55. The CPU 41 may acquire these files from another PC via the communication unit 46, or may acquire these files from a storage medium temporarily connected to the extraction device 40.

In S205, the CPU 41 determines whether or not the constraint information indicated by each constraint item matches in the pre-integration ECU 30 and the post-integration ECU 10.
In S210, the CPU 41 selects one of the inspection viewpoints to be extracted / not determined, and then reads the constraint item corresponding to the selected inspection viewpoint from the inspection viewpoint file 55 (S215).

In the following S220, the CPU 41 determines whether or not there is a constraint item corresponding to the inspection viewpoint being selected, and if there is no constraint item (S220: Yes), the process proceeds to S235, and any of the constraint items (S220: No), the process proceeds to S225.

In S225, the CPU 41 refers to the determination result in S205, and whether or not the constraint information indicated by one or a plurality of constraint items corresponding to the inspection viewpoint being selected is all the same in the pre-integration ECU 30 and the post-integration ECU 10. To judge. Then, the CPU 41 shifts to S235 when an affirmative determination is obtained (S225: Yes), and shifts to S230 when a negative determination is obtained (S225: No).

In S230, the CPU 41 sets the selected inspection viewpoint to "re-inspection required" and extracts the old inspection item of the inspection viewpoint as a new inspection item. In the example of the constraint information files of the pre-integration ECU 30 and the post-integration ECU 10 shown in FIGS. 10 and 11, the constraint information indicated by the “communication band” and the “core division” is different. Therefore, "communication" and "CPU cycle", which are inspection viewpoints corresponding to "communication band" and "core division", are extracted as new inspection items.

On the other hand, in S235, the CPU 41 sets the selected inspection viewpoint to "re-inspection unnecessary" and does not extract the old inspection item of the inspection viewpoint as a new inspection item. In an example of the constraint information files of the pre-integration ECU 30 and the post-integration ECU 10 shown in FIGS. 10 and 11, the constraint information indicated by "memory isolation" matches. Therefore, "memory", which is an inspection viewpoint corresponding to "memory isolation", is not extracted as a new inspection item. Further, in the example of the inspection viewpoint file shown in FIG. 12, the constraint item corresponding to the inspection viewpoint of "security" is "none". Therefore, the inspection viewpoint of "security" is not extracted as a new inspection item.

In S240 performed following S230 or S235, the CPU 41 determines whether or not the extraction / non-extraction determination has been made for all the inspection viewpoints. Then, the CPU 41 ends this process when a positive determination is obtained (S240: Yes), and proceeds to S210 when a negative determination is obtained (S240: No).

[9. effect]
(1) According to the above embodiment, when the information indicated by the determination items in the pre-integration ECU 30 and the post-integration ECU 10 is different, the old inspection item corresponding to the determination item is extracted as a new inspection item. Therefore, the old inspection items related to the differences in HW and software between the pre-integration ECU 30 and the post-integration ECU 10 can be automatically extracted as new inspection items. Therefore, the inspection items can be suitably extracted.

(2) Further, as a determination item, a constraint item indicating constraint information that can restrict the operation of the target application 27 is provided, and the constraint item is used to inspect the target application 27 by the ECU 10 after integration. The viewpoint is extracted. Therefore, for example, in the integrated ECU 10, even if the operation of the target application 27 is restricted by the influence of another application, a new inspection item for inspecting the presence or absence of the influence due to the restriction can be suitably extracted. ..

(3) Further, as a judgment item, an environmental item indicating environmental information classified into BSW information or HW information is provided, and the inspection to be performed in the inspection of the target application 27 in the ECU 10 after integration is provided using the environmental item. The process is extracted. Therefore, even if there is a difference in HW or BSW between the pre-integration ECU 30 and the post-integration ECU 10, an inspection to be performed to inspect whether or not the difference affects the operation of the target application 27. The process can be suitably extracted.

(4) Further, corresponding to each environmental item, related information indicating whether or not the environmental information indicated by the environmental item is related to the operation of the target application is provided. Then, the inspection process is extracted without considering the environmental items whose related information indicates "not related". Therefore, by appropriately setting the related information corresponding to each environment item, the user can extract the inspection process to be performed in the inspection of the target application with higher accuracy.

[10. Other embodiments]
Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments, and can be implemented in various modifications.

(1) As an example, the extraction device 40 of the above embodiment extracts new inspection items of the application in the integrated ECU 10 mounted on the vehicle. However, even when the extraction device 40 transplants the applications of a plurality of old electronic devices that are not mounted on the vehicle to one new electronic device, the extraction device 40 performs a new inspection on the application of the new electronic device in the same manner as in the above embodiment. Items may be extracted. Even in such a case, the same effect can be obtained.

(2) When the application of a plurality of pre-integration ECUs 30 is transplanted to one post-integration ECU 10, the extraction device 40 of the above-described embodiment extracts new inspection items of the ported application in the post-integration ECU 10. However, when the application of one old ECU is transplanted to the new ECU, the extraction device 40 uses the new ECU from among the old inspection items performed on the application in the old ECU in the same manner as in the above embodiment. A new inspection item of the application may be extracted. Further, in such a case, the new ECU may be configured to operate only one application in the old ECU. Even in such a case, the same effect can be obtained.

(3) A plurality of functions possessed by one component in the above embodiment may be realized by a plurality of components, or one function possessed by one component may be realized by a plurality of components. .. Further, a plurality of functions possessed by the plurality of components may be realized by one component, or one function realized by the plurality of components may be realized by one component. Further, a part of the configuration of the above embodiment may be omitted. In addition, at least a part of the configuration of the above embodiment may be added or replaced with the configuration of the other above embodiment. It should be noted that all aspects included in the technical idea specified from the wording described in the claims are embodiments of the present disclosure.

[11. Correspondence of wording]
The pre-integration ECU 30 corresponds to the old device, and the post-integration ECU 10 corresponds to the new device. Further, S100 of the inspection process extraction process corresponds to the acquisition unit, S105 to S130 correspond to the determination unit, and S150 and S155 correspond to the extraction unit. Further, S200 of the inspection viewpoint extraction process corresponds to the acquisition unit, S205 corresponds to the determination unit, and S225 and S230 correspond to the extraction unit.

10 ... Post-integration ECU, 30 ... Pre-integration ECU, 11, 31 ... Hardware, 12, 32 ... CPU, 24, 33 ... BSW, 27, 34 ... Target application, 40 ... Extractor, 41 ... CPU, 60-65 … Inspection process, 66-69… Old inspection items based on inspection perspective.

Claims (5)

Among a plurality of old inspection items (60 to 69) that are inspection items of the target application in the old device (30) in which the target application (34) operates, the target in the new device (10) in which the target application operates. It is an extraction device (40) that extracts new inspection items that are inspection items of the application.
Items indicating information on hardware and / or software in the old device and the new device, the item corresponding to each of the old inspection items is set as a determination item, and the information indicated by the determination item in the old device and the information indicated by the determination item in the old device. The acquisition unit (S100, S200) for acquiring the information indicated by the determination item in the new device, and
A determination unit (S105 to S130, S205) for determining whether or not the information indicated by the determination item in the old device matches the information indicated by the determination item in the new device.
Extraction units (S150, S155, S225, S230) that extract the old inspection items corresponding to the determination items determined to be inconsistent by the determination unit as the new inspection items.
Extractor equipped with. In the extraction device according to claim 1,
The new device is configured to operate the target application together with other applications.
As the old inspection item, a plurality of inspection items (66 to 69) performed by focusing on different inspection viewpoints are provided.
The determination item indicates constraint information that can restrict the operation of the target application.
The old inspection item is an extraction device corresponding to the determination item indicating the constraint information related to the inspection viewpoint of interest in the old inspection item. In the extraction device according to claim 1,
The inspection of the target application in the old device is performed stepwise over a plurality of inspection processes (60 to 65), and the old inspection item is one of the inspection processes.
Information about BSW (24, 33), which is software for operating the target application on the old device and the new device, is defined as BSW information.
Information on the hardware (11, 31) for operating the software in the old device and the new device is defined as HW information.
The information indicated by the determination item is classified into any of the BSW information and the HW information.
Whether or not the old inspection item is related to at least one of the BSW information and the HW information is determined, and the result of the inspection by the old inspection item related to the BSW information is affected by the BSW. The result of the inspection by the old inspection item related to the HW information is affected by the hardware.
Among the old inspection items, the extraction unit (S150, S155) uses the old inspection item related to the type of information indicated by the determination item determined to be inconsistent by the determination unit as the new inspection item. Extractor to extract. In the extraction device according to claim 3,
The acquisition unit further acquires related information indicating whether or not the information indicated by the determination item is related to the operation of the target application.
The determination item for which it is understood that the related information indicates information related to the operation of the target application is defined as a target determination item.
When the extraction unit (S150, S155) determines that the information indicated by at least one of the target determination items indicating the information classified into the same type does not match by the determination unit, the extraction unit (S150, S155) determines that the information does not match. An extraction device that extracts the old inspection item corresponding to the type as the new inspection item. Among a plurality of old inspection items (60 to 69) that are inspection items of the target application in the old device (30) in which the target application (34) operates, the target in the new device (10) in which the target application operates. It is an extraction program that operates a computer as an extraction device (40) that extracts new inspection items that are inspection items of the application.
Items indicating information on hardware and / or software in the old device and the new device, the item corresponding to each of the old inspection items is set as a determination item, and the information indicated by the determination item in the old device and the information indicated by the determination item in the old device. The acquisition unit (S100, S200) for acquiring the information indicated by the determination item in the new device, and
A determination unit (S105 to S130, S205) for determining whether or not the information indicated by the determination item in the old device matches the information indicated by the determination item in the new device.
Extraction units (S150, S155, S225, S230) that extract the old inspection items corresponding to the determination items determined to be inconsistent by the determination unit as the new inspection items.
Extraction program with.

Images