Test specification creation equipment

Abstract

The present disclosure relates to a test specification generation device that generates a model of test specifications for a test target system on the basis of design data of an input new item and design data of accumulated existing items. The test specification generation device includes: a comparison unit that compares the design data of the new item with the design data of the existing items taken out of an existing item database; and a conversion unit that extracts input / output information of the existing items from the design data of the existing items, extracts input / output information of the new item from the design data of the new item, and converts test specifications of the existing items into test specifications of the new item on the basis of an input / output information conversion rule. The comparison unit compares the design data of the existing items and the design data of the new item to determine whether or not the design data of the existing items can be reused. If reuse is possible, the conversion unit extracts the input / output information of the new item and the input / output information of the test specifications and converts the test specifications of the existing items into the test specifications of the new item.

Description

[Technical field]

[0001] The present disclosure relates to a test specification creating device that creates a template for a test specification in a distributed cooperative system such as a train system. [Background technology]

[0002] In a distributed cooperative system such as a train system, conventionally, testing would be carried out by creating new test specifications for each system, creating test specifications in a format that can be used in a simulator based on the created test specifications, and running a simulation.

[0003] An example of a system for creating test specifications and executing a simulation is the system disclosed in Patent Document 1.

[0004] Patent Document 1 discloses a system for automatically ensuring consistency between a design model, an interface specification, and one or more tests created to test the design model. In this system, a controller called a broker incorporated in a modeling environment creates an interface specification, and the interface specification identifies an interface of the design model. In this system, a proposed change to any one of the interface of the design model, the interface specification, and the interface of the test can be captured by the broker and applied to the other two. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Special Publication No. 2016-506550 Summary of the Invention [Problem to be solved by the invention]

[0006] In addition, in simulations of distributed cooperative systems such as train systems, test specifications were sometimes reused for similar systems, but errors in data names, data values, prerequisites, etc. could cause problems in the test results, leading to rework to review the test specifications. In addition, when creating test specifications when changing the architecture, such as changing the equipment configuration or function layout, the comprehensiveness of the specifications created by humans is an issue. Also, creating test specifications that reflect the user's test viewpoint and maintaining them from the user's test viewpoint are also issues.

[0007] The present disclosure has been made to solve the above-mentioned problems, and aims to reduce the man-hours required for creating test specifications. [Means for solving the problem]

[0008] A test specification creation device according to the present disclosure is a test specification creation device that creates a template of test specifications for a system to be tested based on input design data of a new case and stored design data of an existing case, and includes a comparison unit that compares the design data of the new case with the design data of the existing case retrieved from the existing case database, a conversion unit that extracts input / output information of the existing case from the design data of the existing case and extracts input / output information of the new case from the design data of the new case, and converts the test specifications of the existing case into test specifications of the new case based on input / output information conversion rules, and a conversion unit that receives the design data of the existing case and the design data of the new case, and converts architecture information of the existing case defined in the design data of the existing case and architecture information of the new case defined in the design data of the new case. the comparison unit compares the design data of the existing case with the design data of the new case to determine whether the design data of the existing case can be reused, and if so, the conversion unit extracts input / output information of the new case and input / output information of the test specifications, and converts the test specifications of the existing case into the test specifications of the new case. Effect of the Invention

[0009] According to the test specification creation device of the present disclosure, when design data of an existing case can be reused, the conversion unit extracts input / output information of the new case and input / output information of the test specifications, and converts the test specifications of the existing case into test specifications for the new case, thereby eliminating the need to create new test specifications for each case, and reducing the labor required to create the test specifications. [Brief description of the drawings]

[0010] [Figure 1] 1 is a block diagram showing a configuration of a test specification creating device according to a first embodiment; [Diagram 2] 4 is a flowchart for explaining the operation of the test specification creating device according to the first embodiment. [Diagram 3] FIG. 2 is a diagram showing a function list in which a system under test is described in a hierarchical structure of function blocks, function specifications, and functional units. [Figure 4] FIG. 13 illustrates an example of creating test specifications for a new case. [Diagram 5] FIG. 2 is a table showing the device configuration of the system under test. [Figure 6] FIG. 13 is a diagram illustrating an example of a definition of a test specification change part presentation rule. [Figure 7] FIG. 13 is a diagram illustrating an example of a modification of the architecture. [Figure 8] FIG. 13 is a diagram illustrating an example of a modification of the architecture. [Figure 9] FIG. 11 is a block diagram showing a configuration of a test specification creating device according to a second embodiment. [Figure 10] 10 is a flowchart illustrating the operation of the test specification creating device according to the second embodiment. [Figure 11] FIG. 2 is a diagram showing a hardware configuration for realizing a test specification creating device according to the first and second embodiments. [Figure 12] FIG. 2 is a diagram showing a hardware configuration for realizing a test specification creating device according to the first and second embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] <Embodiment 1> <Device configuration> Fig. 1 is a block diagram showing the configuration of a test specification creation device 100 according to the first embodiment. As shown in Fig. 1, the test specification creation device 100 is a device that supports the creation of test specifications 12 based on input new case design data 1, and the created test specifications 12 are input to a simulator 13 for input / output data to a test target system (hereinafter, "test target"). The simulator 13 for input / output data to the test target is a device that simulates communication processing of each device in a distributed cooperative system, and inputs the test specifications 12 to the test target 14 by performing communication processing described in the test specifications 12.

[0012] As shown in FIG. 1, the test specification creation device 100 has an existing case database 3 that stores existing case design data and test specifications for existing cases, an input / output information conversion rule database 6 that stores input / output information conversion rules, and a test specification change part presentation rule database 8 that stores presentation rules for change parts of the test specifications.

[0013] As shown in FIG. 1, the test specification creating device 100 includes a function block comparing unit 2, a new pattern learning unit 4, an input / output data converting unit 5, an architecture change detecting unit 7, a test specification generating unit 9, and a test specification change portion presenting unit 10.

[0014] The function block comparison unit 2 extracts and compares function lists from the new case design data 1 and the design data of the existing case extracted from the existing case database 3. The comparison of the function lists can be performed by calculating the similarity between the function lists and comparing it with a threshold value.

[0015] Then, if the function list is compared by the function block comparison unit 2 and there is an existing case whose similarity is equal to or greater than the threshold and is the maximum, it is determined that the test specification 12 can be created by reusing the design data of the existing case, that is, the design data of the existing case can be reused, and the input / output data conversion unit 5 executes the following process.

[0016] That is, the input / output data conversion unit 5 extracts the input / output data name, preconditions for the input / output data, initial conditions, and value ranges for the input / output data from the design data of the existing case as input / output information for the existing case.Then, the input / output data name, preconditions for the input / output data, initial conditions, and value ranges for the input / output data to be described in the test specifications are extracted from the new case design data 1 as input / output information for the new case.By extracting such input / output information, it becomes possible to determine whether the existing case can be reused.

[0017] Furthermore, the input / output data conversion unit 5 converts the input / output information of the new case associated with the design data of the existing case whose similarity is equal to or greater than the threshold and is the maximum in the function block comparison unit 2, into the input information of the test specification 12 based on the input / output information conversion rules stored in the input / output information conversion rule database 6. By adopting such a configuration, it becomes possible to reuse the existing case.

[0018] On the other hand, if the function block comparison unit 2 compares the function lists and finds that there is no existing case whose similarity exceeds the threshold, it determines that the design data of the existing case cannot be reused, and the new pattern learning unit 4 learns the new case design data as a new design pattern and stores it in the existing case database 3 as the existing case design data.

[0019] The architecture change detection unit 7 receives the design data of the existing case and the new case design data 1, and detects a difference between the architecture information and related prerequisites of the existing case defined in the design data of the existing case, for which the functional block comparison unit 2 has determined that the similarity is equal to or greater than a threshold and is the maximum, and the architecture information and related prerequisites of the new case defined in the new case design data 1.

[0020] The test specification change part presentation unit 10 generates presentation information of test specification change parts due to architecture changes based on the architecture information detected by the architecture change detection unit 7, prerequisites related to the architecture information, and presentation rules for test specification change parts when parameters defined in the design data are changed, which are stored in the test specification change part presentation rule database 8.

[0021] The test specification generating unit 9 generates the test specification 12 based on the input / output information of the test specification 12 generated by the input / output data converting unit 5 and the test specification change part presentation information generated by the test specification change part presenting unit 10 .

[0022] <Operation> Next, the operation of the test specification creating device 100 will be described with reference to the flowchart shown in Fig. 2. First, design data of an existing case and test specifications 12 of the existing case are stored in the existing case database 3 (step S101).

[0023] The design data includes a function list of functions to be tested in the test target 14, information on input / output data for each function, device information (architecture information) related to each function, function information related to each function, and information on the entire system.

[0024] FIG. 3 shows an example of a function list in the form of a table when the system under test 14 is described in a hierarchical structure of function blocks, function specifications, and functional units.

[0025] The functional block shown in Figure 3 is the unit for creating functional specifications, and is a grouping of functional specifications in the same category, for example, air conditioning, brakes, etc. A functional specification is a specification that describes the flow of function execution. It is composed of a combination of the processing of multiple constituent devices of a distributed cooperative system, such as screen operations, processing of device A, and processing of device B. A functional unit is a single function for executing a functional specification.

[0026] FIG. 3 shows, as an example of a functional block, air conditioning settings, which indicate the temperature settings of the air conditioning in the train and the temperature settings of the seat heater, and transmission monitoring, which indicates the monitoring function of communication between the constituent devices of the distributed cooperative system. As an example of functional specifications, for air conditioning settings, air conditioning initialization, which indicates the initialization function of the air conditioning settings, and line delia setting, which indicates the setting function of the blower in the train, are shown. For transmission monitoring, CCU-O, which indicates the subsystem of the train integrated management system, and recording, which indicates the recording function of various information, are shown. As an example of a functional unit, for air conditioning settings, an air conditioning setting screen on a display device for setting the air conditioning in the train and an air conditioning setting initialization process for initializing the air conditioning settings are shown. For transmission monitoring, a transmission monitoring screen for displaying the transmission status in the system on a display device, a transmission monitoring process, and a recording process are shown.

[0027] The function list is not limited to the hierarchical structure shown in FIG. 3. It is also possible to use a function list that simply lists the individual functions, or a function list that describes each device that makes up the system.

[0028] Among the design data, information on input / output data for each function is expressed by, for example, the name of the input / output data, the data type of the input / output data, device information associated with the input / output data, and prerequisites.

[0029] The device information related to each function is represented by the name and index of the device in the system that processes the function, and the vehicle number in which the device is installed.

[0030] The function information related to each function is represented by the names and indexes of the sub-functions that constitute each function, and device information for performing the processing of the sub-functions.

[0031] The information of the entire system can be expressed, for example, by the system architecture, software architecture, functional layout, functional configuration, data transmission method between functions or between devices, prerequisites, and initial conditions. In a train system, the information of the entire system can also be expressed by the number of cars, the train configuration, the number of devices installed, and the transmission delay.

[0032] Returning to the explanation of the flowchart in Fig. 2, the function block comparison unit 2 extracts an existing case from the existing case database 3 (step S102). This means extracting input / output information of the function of the design data of the existing case as shown in Fig. 3.

[0033] Next, new case design data 1 is input to the test specification creating device 100 (step S103). This process means that the user of the test specification creating device 100 inputs the new case design data 1 via an input interface.

[0034] The new project design data 1, like the design data of the existing project, is composed of a function list of functions to be tested in the test target 14, information on input / output data for each function, equipment information related to each function, function information related to each function, and information on the entire system.

[0035] Next, the function block comparison unit 2 extracts a function block configuration from the new case design data 1 (step S104). This means extracting function list information from the new case design data 1.

[0036] Next, the function block comparison unit 2 compares the function list of the design data of the existing case extracted in step S102 with the function list of the new case design data 1 extracted in step S104 (step S105). This is a process of comparing the function lists as shown in Fig. 3 created for the design data of the existing case and the design data 1 of the new case, and means to judge whether the design data of the existing case can be reused.

[0037] An example of a comparison method is to calculate the similarity degree = (number of matching function blocks) / (number of function blocks) and check whether it is equal to or exceeds a threshold value determined by the user. In addition, the matching of function blocks can also be determined based on the rate at which the functional specifications associated with each function block match.

[0038] In the comparison in step S105, if the similarity is equal to or greater than the threshold, it is determined that the design data of the existing case can be reused (Yes), and the process proceeds to step S107. On the other hand, if the similarity is less than the threshold, it is determined that the design data of the existing case cannot be reused (No), and the process proceeds to step S114.

[0039] In step S114, if the comparison result in step S105 shows that there is no existing case in the existing case database 3 whose similarity is equal to or greater than the threshold value, the new pattern learning unit 4 learns the input design data of the new case and stores it in the existing case database 3 as an existing case.

[0040] In the new pattern learning unit 4, for example, machine learning including deep learning is used to make the design data of the new case and the table of architecture information into one new pattern, and the new pattern is stored in the existing case database 3. By providing such a new pattern learning unit 4, it is possible to accumulate new patterns for new cases. In the comparison in step S105, a pattern with a similarity below a threshold value is made into a new pattern.

[0041] Prior to the processing in step S107, input / output data conversion rules are created from the design data and test specifications of the existing case, and are stored in the input / output information conversion rule database 6 (step S106).

[0042] This process means that the user of the test specification creation device 100 inputs, via an input interface, conversion rules created based on the functional specifications corresponding to the test specifications of the existing cases and new cases, the input data names, the output data names, the formats of the input and output data, for example, data types, data transmission methods, communication sources, communication destinations, etc. An example of the conversion rules will be described later.

[0043] In step S107, the input / output data conversion unit 5 extracts input / output information for the existing case with the highest similarity among the existing cases in the existing case database 3 whose similarity is equal to or greater than a threshold value, and associates the extracted information with the corresponding part of the input / output data of the test specifications for the new case. As an association method, for example, data with matching or similar data names can be automatically associated, or data with similar names can be semi-automatically associated with manual intervention.

[0044] Then, for the input / output data in the design data of the existing case stored in the existing case database 3 and the input / output data in the input new case design data 1, the input / output data of the test specifications of the existing case is converted into input / output data of the test specifications of the new case based on the input / output data conversion rules stored in the input / output information conversion rule database 6 in step S106.

[0045] The input / output data conversion unit 5 generates input / output data for the test specifications of the new case from the input / output data for the test specifications of the new case generated in step S107 and the input / output data for the test specifications of the existing case (step S108).

[0046] Figure 4 shows an example of creating test specifications for a new case based on conversion rules from design data for an existing case, design data for a new case, and test specifications for an existing case. In the example of Figure 4, the conversion rules are defined as follows: if at least one of the following conditions (1) to (3) is satisfied, the data is judged to be corresponding even if the input and output data are different.

[0047] (1) Functional specifications are supported (2) At least one of the input data name and the output data name is similar (3) 90% of the input and output data, such as data type and source device, are identical The identity determination in the condition (3) is performed using a predetermined threshold value, which can be selected by the user of the test specification creating device 100 .

[0048] The following (Example 1) to (Example 3) are examples of data conversion when the above conversion rule is applied. Note that (Example 1) to (Example 3) correspond to No. 1 to No. 3 in FIG.

[0049] (Example 1) If the design data of the existing project describes function specifications: air conditioning settings, input data: I_TrainConfValid, output data: HVAC_F_LAN1_ErrCnt_HVAC, and the design data of the new project describes function specifications: air conditioning settings, input data: I_TrainSystemConfValid, output data: HVAC_F_LAN1_ErrCnt_HVAC, and the test specifications of the existing project associated with this design data describe "Air conditioning setting specifications: Set I_TrainConfValid to "true" and confirm that HVAC_F_LAN1_ErrCnt_HVAC is "false", then the test specifications of the new project will output "Air conditioning setting specifications: Set I_TrainSystemConfValid to "true" and confirm that HVAC_F_LAN1_ErrCnt_HVAC is "false".

[0050] In the above (Example 1), the air conditioning settings (functional specifications) of the existing case and the new case correspond, the input data names are similar, and the output data names match, so based on conversion rules (1) and (2), the input and output data of the test specifications of the existing case is converted into the input and output data of the test specifications of the new case.

[0051] (Example 2) If the design data of the existing project describes function specifications: Transmission monitoring, input data: CCU_O_F_LAN1_ErrCnt_CCUO_Status, output data: display, date and time display: yyyymmddhhmmss, and the design data of the new project describes function specifications: Transmission monitoring, input data: CCU_O_F_LAN1_ErrCnt_CCUO_Status, output data: display, date and time display: yyyymmddhhmm, and the test specifications of the existing project associated with this design data describe "Transmission monitoring specifications: Set CCU_O_F_LAN1_ErrCnt_CCUO_Status to "0" and confirm that the display is "yyyymmddhhmmss", then the test specifications of the new project describe "Transmission monitoring specifications: Set CCU_O_F_LAN1_ErrCnt_CCUO_Status to "0" and confirm that the display is "yyyymmddhhmm".

[0052] In the above (Example 2), the transmission monitoring functional specifications of the existing case and the new case correspond, the input data names are similar, and the output data names match, so based on conversion rules (1) and (2), the input / output data of the test specifications of the existing case is converted into the input / output data of the test specifications of the new case.

[0053] (Example 3) If the design data for the existing project describes function specifications: pantograph up / down, threshold (speed): 50km / h, input data: I_TrainSpeed, output data: I_PantoValid, and the design data for the new project describes function specifications: pantograph up / down, threshold (speed): 70km / h, input data: I_TrainSpeed, output data: I_PantoValid, and the test specifications for the existing project associated with this design data describe "Pantograph up / down specifications: Enter the initial value "0" into I_TrainSpeed, and verify that I_PantoValid becomes "true" when the threshold of 50km / h is exceeded," then the test specifications for the new project will be output as "Pantograph up / down specifications: Enter the initial value "0" into I_TrainSpeed, and verify that I_PantoValid becomes "true" when the threshold of 70km / h is exceeded."

[0054] In the above (Example 3), the functional specifications of the pantograph rising and lowering correspond between the existing case and the new case, the input data names are similar, and the output data names match, so based on conversion rules (1) and (2), the input and output data of the test specifications of the existing case are converted into the input and output data of the test specifications of the new case.

[0055] Here, when creating the conversion rule as described above in step S106, the correspondence between the conditions (1) to (3) and each piece of data is input via an input interface, and the correspondence with each piece of data is managed, for example, in a table. This table of the correspondence between the data and the conditions becomes the conversion rule.

[0056] By using the conversion rules described above, test specifications for a new case can be automatically created from the test specifications for an existing case, even if the input and output data are slightly different.

[0057] Furthermore, the above correspondence relationships can all be entered by the user, but if the data and correspondence relationships of existing cases can be reused, the range that can be reused can be specified through the input interface, and the test specification creation device 100 can automatically create a table of the correspondence relationships between data and conditions, i.e., conversion rules, for that range. In this case, since the conversion rules are created by the user and the test specification creation device 100, it can be said that the conversion rules are created semi-automatically.

[0058] Next, the architecture change detection unit 7 extracts a difference between the architecture information and related prerequisites described in the design data of the existing case extracted in step S102 and the architecture information and related prerequisites described in the new case design data 1 extracted in step S104 (step S109), and outputs the difference as changed part presentation information of the architecture.

[0059] Fig. 5 shows the equipment configuration of the test object 14 in a table. In Fig. 5, a BECU (Brake Control Unit), a CCU (Central Control Unit), and a display are shown as the equipment of the test object 14, and it is shown that, as data transmission methods, the BECU has Ethernet (registered trademark) and a dedicated transmission path, the CCU has Ethernet, and the display has Ethernet. It is also shown that, as on-board equipment, the BECU has a TCU (Train Control Unit), the CCU has a TCMS (Train Control Management System), and the display has information equipment.

[0060] The architecture change detection unit 7 manages tables that describe such architecture information and related prerequisites for existing projects and new projects, and by comparing the tables for existing projects and new projects, it extracts the different parts of the data transmission method and on-board equipment for each device as differences. Note that input / output units (I / O) and prerequisites are not shown in FIG. 5. In the prerequisites column, the prerequisites for the device configuration information in each row are described. For example, the first row of the table in FIG. 5 represents the configuration information when the BECU mounted on the TCU communicates via Ethernet, and the prerequisite states that "a redundant configuration with a dual system in each car of the train is used." Multiple prerequisites may be described, and if there are no prerequisites, they need not be described.

[0061] By adopting such a configuration, it becomes possible to extract the changes in the test specifications due to the change in architecture.

[0062] The description of the device configuration of the test target 14 is not limited to the description as shown in FIG. 5, and elements such as device groups, devices, data transmission methods, and prerequisites can also be described in a hierarchical structure.

[0063] After detecting the change in architecture in step S109, the test specification change portion presenting unit 10 detects the change portion of the test specification based on the architecture change corresponding portion presenting information (step S111).

[0064] Prior to the processing in step S111, a presentation rule for test specification change parts when a parameter defined in the design data is changed is created and stored in the test specification change part presentation rule database 8 (step S110). The parameters include the number of cars, the train configuration, the number of devices installed, the design data, the transmission delay, the test target, etc.

[0065] Fig. 6 shows an example of the definition of the test specification change part presentation rule. In Fig. 6, in addition to the above-mentioned parameters, the central system, which indicates the case where the test specification is transmitted to each device, the distributed system, which indicates the case where the test specification is transmitted between each device, and the function block are shown.

[0066] In Fig. 6, for example, when the parameter is the number of vehicles, the change conditions are increased and decreased. Also, when the parameter is the number of vehicles, the function block is air conditioning, the function use is initial air conditioning setting, the test specification is (11-1) checking the display of the air conditioning device layout diagram on the air conditioning setting screen, and the presentation content is correcting the number of air conditioning devices.

[0067] Here, an example of using the test specification change part presentation rule shown in Fig. 6 will be explained using the number of vehicles as an example parameter. When the number of vehicles in a new case increases (or decreases) compared to the number of vehicles in an existing case, test specification change part presentation information is created so that "Modify the number of air conditioning devices" is presented as the presentation content on the test specifications of the existing case for the test specification item number (11-1) corresponding to the function block "air conditioning" and the function specification "initial air conditioning setting".

[0068] This is the processing of step S111 in the flowchart of FIG. 2, which is the processing of the test specification change part presentation unit 10 that generates presentation information of test specification change parts in the test specifications using the result of the detection of the architecture change in step S109 and the presentation rules of the test specification change parts stored in step S110.

[0069] The test specification generation unit 9 generates test specifications describing the architecture change corresponding parts using the architecture change corresponding part presentation information (step S112). If an example of this test specification is "Check 'Turn off all air conditioners' on the air conditioner setting screen 1 of the display device and confirm that the ON / OFF display of air conditioners 1 to 5 is OFF," then the presentation information would be "Change the number of air conditioners."

[0070] By presenting the architectural changes, it is possible to present test specifications to be added, deleted, or modified, thereby improving the comprehensiveness and quality of the tests.

[0071] The test specifications describing the architecture change-compatible parts are presented to the user as a template for the test specifications for the new case, for example, via a display device (not shown) (step S113). The user creates the final test specifications 12 by modifying the template for the test specifications while referring to the presented contents, and inputs the final test specifications 12 to the simulation device 13 for input / output data to the test target.

[0072] <Example of architecture change> Finally, an example of an architecture change will be explained using Figures 7 and 8. Figures 7 and 8 show an example of a change when integrating on-board systems of trains, with Figure 7 showing the on-board system before integration and Figure 8 showing the on-board system after integration.

[0073] As shown in Fig. 7, the on-board system before integration includes information equipment 201, a TCMS 202, and a propulsion control device 203. The information equipment 201 includes PISs (Passenger Information Systems) 2011 and 2012, a camera 2013, and a display 2014, and information is exchanged between the devices via Ethernet EN.

[0074] The TCMS 202 has central units 2021 and 2022, and information is exchanged between the central units 2021 and 2022, between the information system equipment 201 and TCMS 202, and between the propulsion control device 203 and TCMS 202 via Ethernet EN.

[0075] The propulsion control device 203 includes a first control device 210 and a second control device 220. The first control device 210 includes a control calculation CPU board 211 and an input / output (IO) board 212, and a control calculation CPU board 213 and an input / output (IO) board 214. The control calculation CPU boards 211 and 212 exchange information with the TCMS 202 via Ethernet EN.

[0076] The second control device 220 has a control calculation CPU board 221 and an input / output (IO) board 222, and a control calculation CPU board 223 and an input / output (IO) board 224. The control calculation CPU boards 211 and 213 exchange information with the TCMS 202 via Ethernet EN, and information is exchanged between the control calculation CPU board 211 and the control calculation CPU board 213 via a brake control dedicated transmission line BTL.

[0077] 8, the integrated on-board system includes an integrated system 205 and a control device 206. The integrated system 205 includes a CCU, TCU arithmetic function integrated units 2051 and 2052, PISs 2053 and 2054, a camera 2055, a display 2056, and input / output (IO) boards 2057 and 2058, and information is exchanged between each device and the control device 206 via Ethernet EN.

[0078] The control device 206 has a control calculation CPU board 2061 and an input / output (IO) board 2062, and a control calculation CPU board 2063 and an input / output (IO) board 2064. The control calculation CPU boards 261 and 212 exchange information with the TCMS 202 via Ethernet EN, and information is exchanged between the control calculation CPU board 2061 and the control calculation CPU board 2063 via a brake control dedicated transmission line BTL.

[0079] As shown in Figures 7 and 8, when integrating systems, the architecture is significantly changed, and in the past, creating test specifications for new cases after the changes required a huge amount of work. However, according to the test specification creation device 100 of embodiment 1, the amount of work required can be reduced compared to creating new test specifications.

[0080] According to the test specification creation device 100 of the first embodiment described above, a template for test specifications can be created by inputting design data and test specifications for existing cases, and design data for new cases, thereby reducing the number of steps required for creation compared to creating new test specifications.

[0081] <Embodiment 2> <Device configuration> Fig. 9 is a block diagram showing a configuration of a test specification creation device 200 according to embodiment 2. The test specification creation device 200 shown in Fig. 9 has a configuration in which a user editing unit 15 is further provided in the test specification creation device 100 according to embodiment 1 shown in Fig. 1.

[0082] The user editing unit 15 receives the created test specifications 12 as feedback, and enables the user to check the test specifications 12 and modify the test specification conversion rules defined in the input / output information conversion rule database 6 and the test specification change part presentation rules defined in the test specification change part presentation rule database 8. In Fig. 9, the same components as those in the test specification creation device 100 described using Fig. 1 are denoted by the same reference numerals, and duplicated explanations will be omitted.

[0083] <Operation> Next, the operation of the test specification creating apparatus 200 will be described with reference to the flowchart shown in Fig. 10. In Fig. 10, the same components as those in the flowchart described with reference to Fig. 2 are denoted by the same reference numerals, and duplicated descriptions will be omitted.

[0084] After creating a template for test specifications for a new case in step S113, the user checks whether the presented content and converted content are appropriate (step S115). If they are appropriate, the process ends, and if they are not appropriate, the process proceeds to step S116.

[0085] In step S116, the test specification change part presentation rules defined in the test specification change part presentation rule database 8 are reset, and the process proceeds to step S117. In this process, when the specification change part presentation rules are defined in a table as described with reference to Fig. 6, the rules are reset by editing the data in the table.

[0086] In step S117, the conversion rules defined in the input / output information conversion rule database 6 are reset. In the case where the input / output information conversion rules are defined in a table as described with reference to Fig. 4, this process is a process of resetting the rules by rewriting the information in the table cell that contains the wording of the conversion rule.

[0087] In addition, if the test specification conversion rules are reset in step S117, in step S107, when the input / output data of the test specifications of the existing case is converted into the input / output data of the test specifications of the new case based on the input / output data conversion rules, the input / output data of the test specifications of the existing case is converted into the input / output data of the test specifications of the new case based on the reset input / output data conversion rules.

[0088] In addition, when the test specification conversion rules are reset in step S117, in step S108, rather than recreating new test specifications, it is also possible to detect only the range affected by the changes in the input information conversion rule database 6 and modify the test specifications previously created in step S108.

[0089] Furthermore, when the test specification change portion presentation rule is reset in step S116, instead of generating new architecture change corresponding portion presentation information in step S112, it is also possible to detect only the range affected by the change in the test specification change portion presentation rule database 8 and modify the architecture change corresponding portion presentation information created in the previous step S112.

[0090] According to the test specification creation device 200 of the second embodiment described above, a user can periodically adjust parameters in the test specification conversion rules and the architecture change corresponding part presentation information at the time of architecture change, so that the maintainability of the test specification creation device 200 can be expected to be improved.

[0091] <Hardware configuration> Each component of the test specification creating apparatus 100 and 200 according to the first and second embodiments described above can be configured using a computer, and is realized by the computer executing a program. That is, the test specification creating apparatus 100 and 200 are realized, for example, by a processing circuit 50 shown in Fig. 11. A processor such as a CPU (Central Processing Unit) or a DSP (Digital Signal Processor) is applied to the processing circuit 50, and the function of each part is realized by executing a program stored in a storage device.

[0092] Dedicated hardware may be applied to the processing circuit 50. When the processing circuit 50 is dedicated hardware, the processing circuit 50 corresponds to, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a combination of these.

[0093] In the test specification creating devices 100 and 200, the functions of the components may be realized by individual processing circuits, or the functions may be realized collectively by a single processing circuit.

[0094] 12 shows a hardware configuration in the case where the processing circuit 50 is configured using a processor. In this case, the functions of each part of the test specification creating devices 100 and 200 are realized by a combination of software, etc. (software, firmware, or software and firmware). The software, etc. is written as a program and stored in the memory 52. ​​The processor 51 functioning as the processing circuit 50 realizes the functions of each part by reading and executing the program stored in the memory 52 (storage device). In other words, it can be said that this program causes a computer to execute the procedure and method of operation of the components of the test specification creating devices 100 and 200.

[0095] Here, the memory 52 may be, for example, a non-volatile or volatile semiconductor memory such as RAM, ROM, flash memory, EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), HDD (Hard Disk Drive), magnetic disk, flexible disk, optical disk, compact disk, mini disk, DVD (Digital Versatile Disc) and its drive device, or any storage medium to be used in the future.

[0096] The above describes a configuration in which the functions of each component of the test specification creating devices 100 and 200 are realized by either hardware or software, etc. However, the present invention is not limited to this, and some of the components of the test specification creating devices 100 and 200 may be realized by dedicated hardware, and other components may be realized by software, etc. For example, it is possible to realize the functions of some components by the processing circuit 50 as dedicated hardware, and realize the functions of other components by the processing circuit 50 as the processor 51 reading and executing a program stored in the memory 52.

[0097] As described above, the test specification creating devices 100 and 200 can realize the above-mentioned functions by hardware, software, or a combination of these.

[0098] Although the present disclosure has been described in detail, the above description is illustrative in all respects and does not limit the present disclosure. It is understood that countless variations not illustrated can be assumed without departing from the scope of the present disclosure.

[0099] In addition, within the scope of the present disclosure, it is possible to freely combine the respective embodiments, and to appropriately modify or omit the respective embodiments.

Claims

1. A test specification creation device that creates a template of test specifications for a test target system based on input design data of a new case and stored design data of an existing case, a comparison unit that compares the design data of the new project with the design data of the existing project; a conversion unit that extracts input / output information of an existing case from the design data of the existing case, extracts input / output information of a new case from the design data of the new case, and converts a test specification of the existing case into a test specification of the new case based on an input / output information conversion rule; receiving the design data of the existing project and the design data of the new project; Architecture information of the existing project defined in the design data of the existing project; an architecture change detection unit that detects a difference between architecture information of a new project defined in the design data of the new project and architecture information of the new project, and detects an architecture change; a test specification change part presentation unit that presents a change part of the test specification due to the architecture change as test specification change part presentation information; a test specification generation unit that generates a template of the test specification by using the test specification of the new case converted by the conversion unit and the test specification change part presentation information; The comparison unit determines whether the design data of the existing case can be reused by comparing the design data of the existing case with the design data of the new case, and if the design data can be reused, the conversion unit extracts input / output information of the new case and input / output information of the test specifications, and converts the test specifications of the existing case into test specifications for the new case.

2. The comparison unit is 2. The test specification creation device according to claim 1, further comprising: a similarity between the design data of the existing case and the design data of the new case is calculated; and if there is design data of the existing case whose similarity is equal to or greater than a threshold and is the maximum, it is determined that the design data of the existing case can be reused.

3. The input / output information conversion rule is 2. A test specification creation device as described in claim 1, which determines that the input / output information of the existing case corresponds to the input / output information of the new case if the input / output information of the existing case and the input / output information of the new case satisfy at least one of the following conditions: functional specifications correspond, at least one of input data names and output data names are similar, and 90% of the input / output data is the same; and in which the conversion unit converts the test specification of the existing case into the test specification of the new case.

4. The input / output information conversion rule is 4. The test specification creating device according to claim 3, wherein the input / output information conversion rule is defined by a table in which the input / output information of the existing case, the input / output information of the new case, and the test specification of the existing case are associated with each other.

5. 2. A test specification creation device as described in claim 1, wherein the input / output information of the existing case and the input / output information of the new case extracted by the conversion unit include a name of the input / output data, a data type of the input / output data, a prerequisite for the input / output data, and a value range of the input / output data.

6. the architecture change detection unit manages architecture information of the existing project and architecture information of the new project; 2. The test specification creation device according to claim 1, wherein the architecture information of the existing project and the architecture information of the new project managed by the architecture change detection unit include names of devices constituting the test target system, a data transmission method, and names of on-board devices installed in the devices.

7. The test specification change part presentation unit presents the change part of the test specification based on a test specification change part presentation rule, The test specification change point presentation rule is as follows:

2. The test specification generating device according to claim 1, wherein a change in a parameter is defined by a table including presentation contents corresponding to at least a change condition, a function block, and a function specification.

8. 8. The test specification creating device according to claim 7, further comprising a user editing section that enables the input / output information conversion rule and the test specification change portion presentation rule to be modified after the template of the test specification has been created.

9. 2. The test specification creating apparatus according to claim 1, further comprising a new pattern learning section for learning the design data of the new case as a new design pattern when the design data of the existing case cannot be reused in the comparison section.

Images