JP6087474B2 - Development information generator - Google Patents

Description

The present invention relates to the development information generating equipment.

  Regarding the development and change of hardware, for example, Patent Document 1 discloses a technique for grasping the range and degree of influence of hardware change on software and performing development while coordinating software and hardware. .

JP 2006-146842 A

  If the technique disclosed in Patent Document 1 is used, the software affected by the hardware change becomes clear, and the overall development including the software can be grasped. However, depending on the hardware selected for the change, the development difficulty of software, that is, the development man-hours will change greatly, and even if hardware changes that increase the software development man-hours, it is not possible to grasp that Can not. In addition, the price of hardware is important in development, but that is not possible.

  SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to provide information relating to a development plan that satisfies requirements for newly developed or changed hardware and lowers the software development man-hour and the hardware price.

  A representative development information generation apparatus according to the present invention is a development information generation apparatus that outputs information related to a hardware development plan, and selects hardware that satisfies the specifications of existing hardware and the requirements of new hardware, A recommended hardware configuration creation unit that outputs information of a recommended hardware configuration, a software development difficulty level calculation unit that outputs information on the difficulty level of software development according to the information of the recommended hardware configuration, and the recommended hardware configuration And a development plan generator for outputting information related to the development plan based on the information on the difficulty level of software development.

  Further, in the development information generation device according to the present invention, the development plan generation unit has a low hardware price based on the recommended hardware configuration information, and a low software development difficulty level based on the software development difficulty level information. Select development and output information about development plan.

  The present invention is also grasped as a method for generating development information.

  ADVANTAGE OF THE INVENTION According to this invention, while satisfy | filling the request | requirement of new hardware, the information regarding the development plan which lowers the software development man-hour and the price of hardware can be provided.

It is a figure which shows the example of a structure of a product development plan production | generation assistance system. It is a figure which shows the example of the data flow of a product development plan production | generation assistance system. It is a figure which shows the example of the processing flow of a recommended hardware configuration creation program. It is a figure which shows the example of the processing flow of a software development difficulty level calculation program. It is a figure which shows the example of the processing flow of a development plan production | generation program. It is a figure which shows the example of the existing hardware specification. It is a figure which shows the example of a new hardware request | requirement. It is a figure which shows the example of a structure of the product development plan production | generation assistance system of Example 2. FIG. It is a figure which shows the example of the data flow of the product development plan production | generation assistance system of Example 2. FIG. It is a figure which shows the example of the processing flow of a product plan calculation program. It is a figure which shows the example of a maintenance plan. It is a figure which shows the example of a production plan. It is a figure which shows the example of product development performance value data. FIG. 10 is a diagram illustrating an example of a processing flow of a recommended hardware configuration creation program according to the second embodiment. It is a figure which shows the example of the processing flow of the development plan production | generation program of Example 2. FIG. FIG. 10 is a diagram illustrating an example of a processing flow of a recommended hardware configuration creation program according to a third embodiment. FIG. 10 is a diagram illustrating an example of a new hardware request according to the third embodiment. FIG. 10 is a diagram illustrating an example of a processing flow of a recommended hardware configuration creation program according to a fourth embodiment. FIG. 20 is a diagram illustrating an example of a processing flow of a development plan generation program according to a fifth embodiment. FIG. 20 is a diagram illustrating an example of a data flow of feedback of development results of Example 7. It is a figure which shows the structural example of an input screen. It is a figure which shows the structural example of an output screen. FIG. 20 is a diagram illustrating an example of a processing flow of a recommended hardware configuration creation program according to an eighth embodiment. It is a figure which shows the example of software development difficulty. It is a figure which shows the example of software development difficulty level data. It is a figure which shows the example of base WBS. It is a figure which shows the example of a hardware specification data file. FIG. 20 is a diagram illustrating an example of a processing flow of a recommended hardware configuration creation program according to a sixth embodiment. It is a figure which shows the example of a new software request | requirement. It is a figure which shows the example of the software data file of the past PJ. FIG. 25 is a diagram illustrating an example of a processing flow of a recommended hardware configuration creation program according to the ninth embodiment. It is a figure which shows the example of the processing flow of the software development difficulty level calculation program of Example 9. FIG.

  Hereinafter, a preferred embodiment of a product development plan generation support system will be described with reference to the drawings.

  An example of development using a product development plan generation support system and a change of a microcomputer with respect to an existing system using the microcomputer will be described. FIG. 1 is a diagram showing an example of the configuration of a product development plan generation system. The product development plan generation support system 100 includes a server device 101 and a client device 102 and is connected via a network 130. The server device 101 includes an external storage device 103, a central processing unit 104, a main memory 105, and a communication I / F 106, and is connected via a bus. In FIG. 1, the external storage device 103 is connected to the central processing unit 104 via a bus. However, the present invention is not limited to this, and the external storage device 103 and the server device 101 may be network-connected.

  The external storage device 103 includes a past PJ (project) software data file 117, hardware specification data file 118, recommended hardware configuration data file 119, software development difficulty data file 120, development plan data file 121, and existing hardware specifications. Data file 122, new hardware request data file 123, existing software file 124, new software request data file 125, recommended hardware configuration creation program 126, software analysis program 127, software development difficulty calculation program 128, development plan generation program 129 , A base WBS (Work Breakdown Structure) 131 is stored.

  The client device 102 includes a communication I / F 107, a central processing unit 108, an input device 109, an output device 113, and a main memory 116. The input device 109 connects a keyboard 110, a mouse 111, and a touch panel 112, and the output device 113 connects a display 114 and a printer 115.

  The client device 102 starts a program stored in the main memory 116 and displays an input screen 2100 shown in FIG. 21 on the display 114 connected to the output device 108. Data is input to the input units 2101, 2102, 2103, 2104, 2105, and 2106 by the input device 109 from the keyboard 109, mouse 111, touch panel 112, and the like. When data is input, the central processing unit 108 receives a command and transmits a processing request and the input data to the server device 101.

  The server apparatus 101 receives a processing request and input data from the client apparatus 102 via the communication I / F 106. The input data is stored in the data files 117, 118, 119, 120, 121, 131 that are targets of the main memory 105 and the external storage device 103. The central processing unit 104 acquires the programs 126, 127, 128, and 129 from the external storage device 103 based on the processing request from the client device 102, writes them in the main memory 105, and executes the processing. The central processing unit 104 acquires necessary data files 117, 118, 119, 120, 121, 131 from the external storage device 103 during program execution, and stores the processing results in the external storage device 103. When all the processes are completed, the central processing unit 104 sends the data files 117, 118, 119, 120, 121, 131 storing the processing results to the client apparatus 102.

  The client apparatus 102 obtains a data file from the processing result via the communication I / F 107, sends it to the output apparatus 113 by the central processing apparatus 108, and outputs an output screen 2200 shown in FIG.

  FIG. 2 is a diagram showing an example of the data flow described above. The hardware specifications are input from the keyboard 110 or the like to the existing hardware specification input unit 2103 and the new hardware request input unit 2104 of the input screen 2100 shown in FIG. 21 via the input device 109, and the input data is the existing hardware specifications. The data file 122 and the new hardware request data file 123 are stored. The recommended hardware configuration creation program 126 extracts hardware that can satisfy the hardware specifications included in the new hardware specification data file 123 from the hardware specification data file 118, and outputs a recommended hardware configuration data file 119. . The recommended hardware configuration data file 119 is output to the recommended hardware configuration extraction result output unit 2202 of the output screen 2200 shown in FIG.

  Furthermore, the existing software and new software request are input to the existing software input unit 2105 and the new software request input unit 2106 of the input screen 2100 shown in FIG. It is stored in the request data file 125. The software analysis program 127 extracts a portion where the software needs to be changed when the hardware configuration selected from the recommended hardware configuration data file 119 is used for the existing software file 124.

  In the software development difficulty level calculation program 128, one hardware configuration is selected from the recommended hardware configuration data file 119, and a software development performance value using the selected hardware from the software data file 117 of the past PJ is extracted. The development result value is compared with the analysis result of the software analysis program 127 and the new software requirement, the development difficulty level is determined, and the result is stored in the software development difficulty level data file 120. The software development difficulty level data file 120 is output to the software development difficulty level calculation result output unit 2203 of the output screen 2200 shown in FIG.

  Finally, the development plan generation program 129 predicts the development man-hour when using each hardware configuration included in the recommended hardware configuration data file 119 based on the software development difficulty data file 120, and minimizes the development man-hour. Select the hardware configuration to be Based on the selected hardware configuration and the calculated development man-hours, it is determined whether each process included in the base WBS 131 is necessary, a development man-hour is input to generate a development plan, and the result is stored in the development plan data file 121. The result is output to the development plan calculation result output unit 2204 of the output screen 2200 shown in FIG. That is, the selected hardware configuration is output to the selected hardware configuration output unit 2205, and the development plan is output to the development result output unit 2206.

  FIG. 3 is a flowchart for explaining an example of processing of the recommended hardware configuration creation program 126. First, an existing hardware specification is acquired from the existing hardware specification data file 122 (S301). An example of existing hardware specifications is shown in FIG. The existing hardware specification 600 is data including, for example, a model number 601, a core 602, a frequency 603, a price 604, a delivery date 605, a minimum delivery number 606, a support status 607, a capacity 608, a voltage 609, a port number 610, and a peripheral device 611. . For example, the existing hardware specification 600 may be a hardware specification that has already been purchased or a hardware specification that has already been determined to be purchased.

  Next, a new hardware request is acquired from the new hardware request data file 123 (S302). FIG. 7 shows an example of a new hardware request. The new hardware request 700 includes the same items as the existing hardware specification 600, and is filled with the hardware specifications that the new hardware needs to have when changing the existing hardware. If there is no designation for the new hardware request 700, “-” is entered.

  The first line of the hardware specification data file 118 is set as a specific line, and the hardware specification is extracted from the specific line of the hardware specification data file 118 (S303). The hardware specification data file 118 is a file in which the existing hardware specifications 600 are listed as shown in FIG. For example, all hardware that can be used for development, including those that have not been purchased, may be listed, or all hardware for which information such as a catalog can be obtained may be listed. Hardware that simultaneously satisfies the existing hardware specification 600 and the new hardware request 700 is extracted from the hardware specification data file 118 and output to the recommended hardware configuration data file 119 (S304). The recommended hardware configuration data file 119 has a configuration similar to that of the hardware specification data file 118, and only hardware that satisfies the existing hardware specification 600 and the new hardware request 700 at the same time in the hardware specification data file 118 is included. including.

  It is determined whether all the lines of the hardware specification data file 118 have been processed (S305). If all the lines have not been processed, the specific line is moved to the next line (S306), and the process returns to S303. After all the rows of the hardware specification data file 118 are processed, they are sorted in ascending order by the price 604 included in the recommended hardware configuration data file 119, and the top 10 items are finally output to the recommended hardware configuration data file 119. (S307). Although the number of output cases is 10 here, the present invention is not limited to this, and an arbitrary number may be output. Further, not only the price 604 but also any items of hardware specifications such as the capacity 608 and the delivery date 605 are sorted and output to the recommended hardware configuration data file 119.

  FIG. 4 is a flowchart for explaining an example of processing of the software development difficulty level calculation program 128. First, the existing software file 124 is acquired (S401). Next, one hardware configuration is selected from the recommended hardware configuration data file 119 (S402). One peripheral device having the selected hardware configuration is extracted from the recommended hardware configuration data file 119 (S403). It acquires how the extracted peripheral device is implemented by existing software (S404), and calculates the software change difficulty (S405).

  As an example, a software implementation related to a timer that is a peripheral device of a microcomputer will be described. The specifications of the timers installed in each microcomputer may differ. For example, an H microcomputer board sold by company A is equipped with an H core made by company R. It is assumed that the H core incorporates a plurality of channels of 16-bit general purpose integrated timer units (ITU). By using the ITU, it is possible to count the clock signal and measure the passage of time based on the period of the clock signal of the H microcomputer. In the case of ITU, the start of the timer count is realized by describing “ITU.TSTR.BIT.STR0 = 1;” in programming in C language. This description is to start timer counting by directly specifying a value in the register that manages the timer count operation of the H core.

  On the other hand, the S microcomputer board sold by the S company has an M core made by the A company. It is assumed that this M core is equipped with a plurality of channels of TIM, which is a 16-bit general purpose timer. In the case of TIM, the timer count is started by setting “TIM_Cmd (TIM2, ENABLE);”. This function is a library function provided by Company S. By using this function, it is possible to control the timer count without directly manipulating the register value.

  That is, in the H microcomputer board, the timer count is controlled by directly rewriting the register value, whereas in the S microcomputer board, the timer count is controlled via the library provided by the S company. As described above, the peripheral device may depend on hardware and the software implementation may be different. Then, it is possible to reduce the influence by implementing the software by abstracting the hardware dependent part. For example, in the example shown in FIG. 24, when the abstraction level is high, even if the hardware is changed, the software above the library does not need to be changed due to the abstraction of the library or the like. For this reason, the change difficulty level can be regarded as zero. In addition, when it is necessary to change the bit position designation or bit value designation of the software due to the hardware change, the difficulty level of the change becomes high. If there is no abstraction at all, it is necessary to change the software corresponding to the hardware by changing the hardware.

  Here, as shown in FIG. 24, the degree of abstraction is determined, the location where the specification and the software implementation differ between the existing hardware and the recommended hardware is specified, and the change difficulty level is calculated by summing the change difficulty level of each location. (S405). For example, as the change difficulty level of each part, the software pattern shown in FIG. 24 in the target software may be detected by pattern matching, and the change difficulty level of the detected pattern may be assigned. An example of the software change difficulty level is shown in FIG. The degree of difficulty of software change is calculated for the timer, serial communication, RTOS, vendor-supplied library, and development environment, and the software to be calculated is stored. Aggregate the difficulty and calculate the average value. Although the timer and serial communication are used here, the present invention is not limited to this, and other peripheral devices may be used. Software change difficulty levels are calculated for all peripheral devices (S406, S413).

  The software change difficulty level may include software changes that are not related to hardware changes. The software change difficulty level due to the software change may be calculated based on the number of steps to be changed, or a known software change man-hour calculation may be used. In addition, since it is difficult to calculate the change difficulty level depending on the content of the change, the user inputs the change difficulty level shown in FIG. 25 in advance using the keyboard 110 or the like, including the software change difficulty level due to hardware changes. It may be set.

  Next, a new software request is acquired (S407). An example of a new software request is shown in FIG. Here, the new software request 2900 includes a function request and a non-function request. A development performance value such as a development amount and a development period using the selected hardware configuration is extracted from the software data file 117 of the past PJ (S408). An example of the software data file 117 of the past PJ is shown in FIG. This includes the file name, development amount, and period of the source code that has been modified and added to realize the software request, and includes metric information such as the number of steps of the source code included in the system. The software data file 117 of the past PJ in FIG. 30 describes the number of steps, but is not limited thereto, and may include metric information such as complexity. Further, in order to easily calculate the similarity by comparing the requests, one request is composed of a plurality of items, and each item is selected from a plurality of fixed contents so that the number of matching items becomes the similarity. It may be a request of various forms.

  The request of the software data file 117 of the past PJ and the request of the new software request data file 125 are compared, it is determined whether they are similar so that the maximum value becomes 1 from the minimum value 0, and the average value is obtained to calculate the similarity (S409). All software data files are processed (S410, S415). The same processing is performed for all hardware configurations (S411, S414). The most similar past PJ software data file 117 and software change difficulty are output as software development difficulty data file 120 (S412). Note that the software change difficulty level may be set in advance by the user using the keyboard 110 or the like in response to a request that does not correspond to the request for the software data file 117 of the past PJ.

  FIG. 5 is a flowchart for explaining an example of processing of the development plan generation program 129. A hardware specification is acquired from the recommended hardware configuration data file 119 (S501). The software development difficulty level of the target hardware configuration is acquired from the software development difficulty level data file 120 (S502). Then, a harmonic average of the software development difficulty level and the hardware price is calculated based on the formula (1), and a hardware configuration that minimizes the harmonic average is selected as a development target (S503, S504, S505). In the formula (1), the harmonic average is used. However, the average is not limited to this, and other average values may be used.

  Based on the software development difficulty level corresponding to the selected hardware configuration, the man-hour is predicted by the equation (2) (S506). Equation (2) is calculated by dividing the total number of software changes by the reference work value and multiplying by the software development difficulty level. Based on the calculated development man-hours, recommended hardware specifications, and software development difficulty level, the base WBS 131 is updated, and a development plan is generated and output (S507).

  An example of the base WBS is shown in FIG. A work package is defined for each process. For example, regarding specification development, impact analysis of existing specifications due to hardware changes includes impact analysis of hardware specification changes, impact analysis of RTOS (Real Time OS) changes, impact analysis of vendor-provided libraries, and impact analysis of development environment changes. . For example, in accordance with the recommended hardware specifications, there is a case where the RTOS change is not required or the hardware providing vendor does not change. At this time, the influence analysis of the RTOS change and the influence analysis of the vendor-provided library are not required. Unnecessary processes and work packages are deleted according to the recommended hardware specifications, and man-hours are input based on the calculated predicted values for the necessary processes and work packages to generate a development plan.

  As explained above, among the hardware candidates that meet the existing hardware specifications and new hardware requirements, the hardware development that has the minimum development man-hours and the selected hardware configuration can be selected by considering the software development difficulty level. The development plan used can be generated.

  In the second embodiment, in addition to the configuration described in the first embodiment, product plan information such as a production plan and a maintenance plan is also used to generate a product development plan. By using the product plan information, a highly accurate product development plan can be generated. FIG. 8 is a diagram for explaining an example of the apparatus configuration of the second embodiment. The product development plan generation support system 800 includes a server device 801 and a client device 102 and is connected via a network 130. The server device 101 includes an external storage device 103, a central processing unit 104, a main memory 105, and a communication I / F 106, and is connected via a bus. In FIG. 8, the external storage device 103 is connected to the central processing unit 104 via a bus. However, the present invention is not limited to this, and the external storage device 103 and the server device 101 can be connected to a network.

  The external storage device 802 includes a past PJ software data file 117, a hardware specification data file 118, a recommended hardware configuration data file 119, a software development difficulty data file 120, a development plan data file 810, and an existing hardware specification data file 122. New hardware request data file 123, existing software file 124, new software request data file 125, product development record value data file 808, maintenance plan data file 805, production plan data file 806, product plan calculation program 807, recommended hardware Configuration creation program 807, software analysis program 127, software development difficulty level calculation program 128, base WBS 131, development plan generation program 04, has a product plan data file 809.

  The client device 102 includes a communication I / F 107, a central processing unit 108, an input device 109, an output device 113, and a main memory 116. The input device 109 includes a keyboard 110, a mouse 111, and a touch panel 112, and the output device 113 includes a display 114 and a printer 115.

  The product development plan support system 800 shown in FIG. 8 is obtained by changing the external storage device 103 to the external storage device 802 with respect to the product development plan generation support system 100 shown in FIG. The other configurations have the same functions as those already described with reference to the same reference numerals in FIG.

  An example of the data flow of the system shown in FIG. 8 is shown in FIG. Data is input from the input device 109 such as the keyboard 110 to the product plan input unit 2101 and the maintenance plan input unit 2102 of the input screen 2100 shown in FIG. 21, and the input data is the product plan data file 806 and the maintenance plan data file 805. Stored in The product plan calculation program 807 compares the product development result value data file 808, the maintenance plan data file 805, and the production plan data file 806, extracts similar data, and calculates a predicted value. The calculated predicted value is stored in the product plan data file 809.

  Next, the recommended hardware configuration creation program 803 extracts hardware that can meet the delivery date described in the product plan data file 809 from the hardware specification data file 118 and can satisfy the new hardware requirements, and recommends the recommended hardware configuration. The data file 119 is output. Finally, the development plan generation program 804 predicts the development man-hour from the hardware configuration candidates included in the recommended hardware configuration data file 119 based on the software development difficulty level included in the software development difficulty level data file 120, and the product Among the hardware configurations that can satisfy the delivery date included in the plan data file 809, the hardware with the lowest price is selected. Based on the selected hardware configuration and the calculated development man-hours, it is determined whether each process included in the base WBS 131 is necessary, a development man-hour is input to generate a development plan, and the result is stored in the development plan data file 121. The development plan data file 810 is output.

  FIG. 10 is a flowchart for explaining an example of processing of the product plan calculation program 807. First, a maintenance plan is acquired from the maintenance plan data file 805 (S1001). An example of a maintenance plan is shown in FIG. Maintenance period 1101, maintenance object 1102, maintenance / maintenance 1103 indicating whether or not maintenance is performed, business trip repair 1104 regarding whether or not business trip repair is performed, custody repair 1105 regarding whether or not custody repair is performed, whether or not maintenance is performed Maintenance 1106, maintenance response time 1107, maintenance cost 1108, maintenance personnel 1109, and scheduled number 1110. Next, a production plan is acquired from the production plan data file 806 (S1002).

  An example of the production plan is shown in FIG. Expected demand 1201, transportation cost 1202, parts procurement cost 1203, parts procurement time 1204, inventory quantity 1205, production quantity 1206, delivery time 1207, software development period 1208, software development personnel 1209, hardware development period 1210, hardware development personnel 1211 are included. It is data. A maintenance plan and a production plan are acquired from the product development result value data file 808 (S1003), and a similarity with the acquired data is obtained (S1004).

  An example of the product development record value data file 808 is shown in FIG. This is a data structure in which actual values are added to the production plan data file 806 and the maintenance plan data file 805. The similarity is calculated by equation (3).

The maintenance plan and the production plan are compared with the data at the time of planning stored in the product development result value data file 808, normalization is performed so that the minimum value is 0 and the maximum value is 1, and the average value is calculated. Here, for comparison, a numerical value item is calculated as a difference, and a non-numeric item is 0 if it matches, and 1 if it does not match. The similarity indicates that the smaller the value, the more similar.

  All rows of the product development record value data file 808 are processed (S1005, S1006), and product development record value data that minimizes the similarity is selected (S1007). The ratio of the difference value between the planned value and the actual value of the selected product development actual value data is calculated, corrected by multiplying the ratio calculated for the production plan and the maintenance plan, and output as a product plan data file 809 (S1008). .

  FIG. 14 is a flowchart illustrating an example of processing of the recommended hardware configuration creation program 803. An existing hardware specification and a new hardware request are acquired (S301, S302). The delivery date is acquired from the product plan data file 809 (S1401). Next, the hardware specification is acquired from the hardware specification data file 118 (S303).

  Hardware capable of complying with the delivery date and satisfying the existing hardware specifications and new hardware requirements is registered in the recommended hardware configuration data file 119 (S1402). For example, when all the hardware specifications in the hardware specification data file 118 are processed, they are sorted in ascending order by hardware price, and the top 10 items are output as the recommended hardware configuration data file 119. Although the number of output cases is 10 here, the present invention is not limited to this, and an arbitrary number can be output. Further, not only the hardware price but also any item in the hardware specification such as the capacity may be sorted and output as the recommended hardware configuration data file 119.

  FIG. 15 is a diagram illustrating a flowchart for explaining an example of processing of the development plan generation program 804. The delivery date is acquired from the product plan data file 809 (S1501). When the delivery date included in the acquired product plan is one year or more, the hardware with the lowest price is selected from the recommended hardware configuration data file 119 (S1502, S1503). If the delivery date included in the acquired product plan is less than one year, the hardware that minimizes the software development difficulty is selected from the recommended hardware configuration data file 119 (S1502, S1505). The man-hour is predicted based on the software development difficulty corresponding to the selected hardware configuration (S506). Based on the calculated development man-hours, recommended hardware specifications, and software development difficulty level, the base WBS 131 is updated, and a development plan is generated and output (S507). Here, the process is switched over with a delivery date of one year or more and less than one year, but the present invention is not limited to this, and any delivery date can be set.

  As described above, according to the second embodiment, by using the product plan information, it is possible to select hardware that can finish development within the scheduled delivery date, and to develop a highly accurate development plan that can be developed without delay. Can be generated.

  In the third embodiment, an example of another embodiment of the recommended hardware configuration creation programs 126 and 803 shown in the description of the first and second embodiments will be described. In the first and second embodiments, for example, as shown in FIG. 6, the frequency is set to a fixed value of 16 MHz. On the other hand, in the recommended hardware configuration creation programs 126 and 803, hardware satisfying all new hardware requirements and existing hardware specifications is extracted from the hardware specification data file 118. For this reason, if there is no hardware satisfying the new hardware requirement and the existing hardware specification in the hardware specification data file 118, the recommended hardware candidate cannot be extracted. In the third embodiment, a recommended hardware candidate can be extracted by making it possible to specify a range of a new hardware request.

  FIG. 16 shows an example of a flowchart of recommended hardware configuration creation programs 126 and 803 in the third embodiment. An existing hardware specification and a new hardware request are acquired (S301, S302). An example of the new hardware request acquired here is shown in FIG. New hardware request 1700 is data including model number 1701, core 1702, frequency 1703, price 1704, delivery date 1705, minimum delivery number 1706, support status 1707, capacity 1708, voltage 1709, number of ports 1710, peripheral device 1711, Each data can be specified as a range. For example, the frequency 1703 is 100 MHz to 200 MHz.

  In the recommended hardware configuration program 803, the delivery date can be observed, and in the recommended hardware configuration creation programs 126 and 803, hardware that satisfies the existing hardware specifications and is within the specified range of the new hardware request is recommended hardware configuration data file. It registers in 119 (S1601).

  All the rows of the hardware specification data file 118 are processed (S305, S306), the recommended hardware configuration data file 119 is sorted in ascending order by price, and the top 10 items are output as the recommended hardware configuration data file 119 (S307). ). Although the number of output cases is 10 here, the present invention is not limited to this, and an arbitrary number can be output. In addition to the hardware amount, any item of the recommended hardware configuration data file 119 such as the capacity and the number of delivery days is sorted and output as the recommended hardware configuration data file 119.

  As described above, by making it possible to specify the range of new hardware requirements, hardware that satisfies the range of new hardware requirements can be extracted from the hardware configuration list as candidates, and completely matches the new hardware requirements. Even if not, a recommended hardware candidate can be extracted.

  In Example 4, an example of another embodiment of the recommended hardware configuration creation programs 126 and 803 will be described. In the first and second embodiments, for example, as shown in FIG. 6, the frequency is set to a fixed value of 16 MHz. In contrast, in the recommended hardware configuration creation programs 126 and 803 described in the first and second embodiments, hardware that satisfies all new hardware requirements and existing hardware specifications is extracted from the hardware specification data file 118. For this reason, if there is no hardware satisfying the new hardware requirement and the existing hardware specification in the hardware specification data file 118, the recommended hardware candidate cannot be extracted.

  Further, even if the recommended hardware configuration creation programs 126 and 803 described in the third embodiment do not exist in the hardware specification data file 118 within the range specified by the new hardware request, Cannot extract recommended hardware candidates.

  In the fourth embodiment, the similarity between the new hardware request and the specification of each hardware in the hardware specification data file 118 is calculated, and recommended hardware candidates are extracted based on the similarity. FIG. 18 shows an example of a flowchart of a recommended hardware configuration program in the fourth embodiment. Existing hardware specifications, new hardware requirements, and product plans are acquired (S301, S302). A hardware specification is extracted from the hardware specification data file 118 (S303).

  Next, if there is a new hardware request and a delivery date, the extracted hardware requirement similarity with the delivery date is obtained by equation (4) (S1801).

The hardware specification similarity is normalized so as to be a value from 0 to 1. Here, as the subtraction in the equation (4), the numerical item is calculated as a difference, and the non-numeric item is set to 0, and the non-matching item is set to 1. Note that the closer the degree of similarity is to 0, the more similar. Similarities are calculated for all hardware specifications, the calculation results are sorted in ascending order, and the top 10 items are output as the recommended hardware configuration data file 119 (S1802). Although the number of output cases is 10 here, the present invention is not limited to this, and an arbitrary number can be output.

  As described above, by calculating the similarity between the new hardware request and the specifications of each hardware in the hardware specification data file 118, even if the new hardware request does not match, the recommended hardware candidate Can be extracted.

  In Example 5, an example of another embodiment of the development plan creation program 129 will be described. When developing using hardware, a technical inquiry may be made to a vendor that provides the hardware. For example, in software development for embedded products using a microcomputer, the instruction set and library differ depending on the microcomputer used and the vendor providing the microcomputer.

  If the technical information provided by the vendor is insufficient, interview the Internet and other developers to obtain technical information. In some cases, you may contact technical vendors for technical support. If the acquisition of technical information does not proceed smoothly, development may be delayed and process delays may occur. That is, the difficulty level of obtaining technical information is related to the difficulty level of software development.

  Therefore, a process of calculating a software development difficulty level taking into account the difficulty level of obtaining technical information related to the target hardware and generating a development plan will be described. FIG. 19 shows an example of a flowchart of the development plan creation program 129 in the fifth embodiment. Data is acquired from the recommended hardware configuration data file 119 (S501). The software development difficulty level of the target hardware configuration is acquired from the software development difficulty level data file 120 (S502). The technology acquisition difficulty level is extracted from the support status included in the recommended hardware configuration data file (S1901). The technology acquisition difficulty level is normalized to 0 to 1 for Japanese language specifications, hardware specification disclosure on the Internet, technical support contact response, etc., and an average value is calculated as the technology difficulty level. The smaller the value, the lower the difficulty level.

  A harmonic average of the hardware price, the software development difficulty level, and the technology acquisition difficulty level is calculated (S1902). A hardware configuration that minimizes the harmonic average is selected as a development target (S505). Although the harmonic average is used here, the present invention is not limited to this, and other average values may be used. Then, the man-hour is predicted based on the software development difficulty corresponding to the selected hardware configuration (S506). The calculated predicted value is input to the base WBS 131, and a development plan is generated and output (S507).

  As explained above, it is possible to calculate the development difficulty with high accuracy by taking into account the difficulty of obtaining technical information necessary for software development using hardware configuration, and development that matches the actual situation of development A plan can be generated.

  In Example 6, an example of another embodiment in the development plan generation program 129 will be described. When developing a product using hardware, the target hardware may not be delivered on time, and development may be delayed. Here, hardware is selected in consideration of the delivery date violation rate in the past product development results, and a development plan is generated. As a result, the probability of development delay due to non-payment of the target hardware is reduced, so that a highly accurate development plan can be generated.

  FIG. 28 shows an example of a flowchart of the product plan calculation program 129 in the sixth embodiment. Data is acquired from the recommended hardware configuration data file 119, and the software development difficulty level corresponding to the hardware configuration is acquired from the software development difficulty level data file 120 (S501, S502). Next, the delivery date violation rate of this hardware configuration is extracted from the product development performance value data file 808 (S2801). The harmonic average of the hardware configuration price, software development difficulty level, and delivery date violation rate is calculated (S2802). After processing all data, the hardware configuration that minimizes the harmonic average including the delivery date violation rate is set as the development target (S2803), the development man-hour is predicted (S506), and the man-hour is input to the base WBS. A development plan data file 810 is generated (S507).

  As described above, by selecting hardware based on the hardware price, development difficulty, and delivery date violation rate, it is possible to reduce the probability of development delay due to non-payment of hardware.

  In the seventh embodiment, an example will be described in which the result of development based on the product development plan generated by the product development plan generation support systems 100 and 800 is fed back to the product development plan generation support systems 100 and 800 as development results. FIG. 20 shows an example of the data flow in the seventh embodiment. A product is developed based on the development plan data files 121 and 810 generated by the product development plan generation support systems 100 and 800 (S2001). The result of product development is stored in the development result data file 2000. The obtained development result is stored in the product development result value data file 808 and the past PJ software data file 117.

  As described above, the actual development results based on the generated development plan are stored in the product development result value data file 808 and the past PJ software data file 117, for example, the development plan of the product development generation program 804. The prediction accuracy is increased, and the difference between the development plan data file 809 and the development result data file 2000 can be reduced.

  In Example 8, an example of another embodiment of the recommended hardware configuration creation program 803 will be described. The processing result of the recommended hardware configuration generation program 803 described with reference to FIG. 14 outputs the top 10 items as recommended hardware configuration data, focusing on the price of the hardware, for example. In the eighth embodiment, the recommended hardware is extracted from a plurality of points of view, such as the result of extraction focusing on not only the hardware amount but also the delivery date, the result of focusing on performance, and the like, and the result is output as the recommended hardware configuration data file 119 To do.

  FIG. 23 is a flowchart illustrating an example of the recommended hardware configuration creation program 803 according to the eighth embodiment. As described with reference to FIG. 14, the existing hardware requirement, new hardware request, and delivery date of the product plan are acquired (S301, S302, S1401), and compared with the hardware specification of the hardware specification data file 118. (S303, S1402, S305, and S306) are extracted. In the example of the flowchart shown in FIG. 23, the top 10 items sorted by the price, the delivery date, and the number of peripheral circuits are output as recommended hardware files (S2300).

  As described above, it is possible to increase hardware selection candidates by outputting recommended hardware configurations selected from a plurality of viewpoints, not limited to the price of hardware.

  In Example 9, an example of another embodiment of the recommended hardware configuration creation program 803 and the software development difficulty level calculation program 128 will be described. The recommended hardware configuration creation program 803 and the software development difficulty level calculation program 128 described with reference to FIGS. 14 and 4 do not consider the characteristics of product development. For example, there may be a difference between a hardware change including new development and a hardware change including new development. If only the hardware is changed, the recommended hardware configuration creation program 803 does not need to acquire a new hardware request, and the software development difficulty level calculation program 128 does not need to acquire a new software request.

  Therefore, in the ninth embodiment, as shown in FIGS. 31 and 32, in addition to the processing described with reference to FIGS. 14 and 4, it is determined whether or not new development is included, and the processing is switched (S3100, S3200). In addition, in the registration to the recommended hardware configuration data file 119, hardware that can satisfy a new hardware request is registered only when there is a new development (S3101). If there is a request for new software, a software development result value most similar to the new development corresponding to the request for new software is also output (S3201). This makes it possible to reduce the processing of the recommended hardware configuration creation program 803 and the software development difficulty level calculation program 128 according to the type of product development.

  As described above, the processing amount can be reduced by switching the processing flow depending on the type of product development.

  The product development plan generation support systems 100 and 800 are not limited to the embodiments described above, and various modifications are possible. For example, the invention is not necessarily limited to those having all the configurations described. In addition, a part of the configuration described in one embodiment can be replaced with the configuration described in another embodiment, and the configuration described in another embodiment can be added to the configuration described in one embodiment. It is. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them, for example, by an integrated circuit. Further, each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a source code for realizing each function by the processor. Information such as source codes, tables, and files for realizing each function can be stored in a recording device such as a memory, a hard disk, or an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD. it can.

  In addition, the control lines and information lines are those that are considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

100 Product Development Plan Generation Support System 101 Server Device 102 Client Device 103 External Storage Device 117 Past PJ Software Data File 118 Hardware Specification Data File 119 Recommended Hardware Configuration Data File 120 Software Development Difficulty Data File 121 Development Plan Data File 122 Existing hardware specification data file 123 New hardware request data file 124 Existing software file 125 New software request data file 126 Recommended hardware configuration creation program 127 Software analysis program 128 Software development difficulty calculation program 129 Development plan generation program 131 Base WBS

Claims (11)

A development information generation device that outputs information related to a hardware development plan,
A storage device for storing a plurality of programs and a plurality of data;
A central processing unit that executes the plurality of programs and processes the plurality of data;
With
The central processing unit is
By executing the recommended hardware configuration creation program in the plurality of programs, the hardware that satisfies the specifications of the existing hardware and the requirements of the new hardware is selected, and the recommended hardware configuration information is stored in the plurality of data. Output to the storage device as one ,
By executing a software development difficulty level calculation program in the plurality of programs, software development difficulty level information corresponding to the recommended hardware configuration information is output to the storage device as one of the plurality of data items. And
By executing a development plan generation program in the plurality of programs, information on the development plan is stored as one of the plurality of data based on the information on the recommended hardware configuration and the information on the difficulty level of the software development. be output to the device
Development information generating apparatus according to claim. The central processing unit is
By executing the development plan generation program, the hardware price is low from the recommended hardware configuration information, and the development with the low software development difficulty is selected from the software development difficulty information. The development information generation apparatus according to claim 1, wherein information is output to the storage device as one of the plurality of data . The central processing unit is
By executing the software development difficulty calculator program, the recommended hardware corresponding to the configuration information, the information of the difficulty of software development that is calculated by the similarity of the type and historical software development software implementation form The development information generation apparatus according to claim 1, wherein the development information generation apparatus outputs the data to the storage device as one of a plurality of data . The central processing unit is
By executing a product plan calculation program in the plurality of programs, a product plan including a delivery date based on production plan information is output to the storage device as one of the plurality of data ,
2. The hardware according to claim 1, wherein the recommended hardware configuration creation program is executed to comply with the delivery date and select hardware satisfying the specifications of the existing hardware and the requirements of the new hardware. Development information generator. The central processing unit is
By executing the product plan calculation program, the delivery date included in the production plan is corrected according to the ratio between the planned value and the actual value in the past product development, and the product plan including the corrected delivery date is converted into the plurality of data. The development information generation apparatus according to claim 4, wherein the development information generation apparatus outputs to the storage apparatus as one of the following . The central processing unit is
By executing the development plan generation program, based on the recommended hardware configuration information and the software development difficulty information, the hardware configuration selection criteria are changed according to the delivery date, and the information on the development plan The development information generation apparatus according to claim 4, wherein the development information generation apparatus outputs the data as one of the plurality of data to the storage device. The new hardware requirement includes a requirement range;
The central processing unit is
By executing the recommended hardware configuration creation program, the hardware that satisfies the specifications of the existing hardware and falls within the required range of the new hardware is selected, and information on the recommended hardware configuration is stored in the plurality of data. The development information generation apparatus according to claim 1, wherein the development information generation apparatus outputs the information to the storage device as one . The central processing unit is
By executing the development plan generation program , information on the development plan is obtained from the plurality of data based on the technology acquisition difficulty level from the hardware provider, the recommended hardware configuration information, and the software development difficulty level information. The development information generation apparatus according to claim 1, wherein the development information generation apparatus outputs to the storage device as one of the following . The central processing unit is
By executing the development plan generation program , information related to the development plan is obtained based on one of the plurality of data based on the delivery date violation rate of the hardware providing vendor, the recommended hardware configuration information, and the software development difficulty level information. The development information generation apparatus according to claim 1, wherein the development information generation apparatus outputs to the storage device. The central processing unit is
By executing the recommended hardware configuration creation program, a plurality of hardware satisfying the specifications of the existing hardware and the requirements of the new hardware are selected, and the selected plurality of hardware is selected in the order based on the first condition. The development information generation apparatus according to claim 2, wherein the development information generation apparatus according to claim 2 is arranged in order based on the condition 2 and outputs information of a recommended hardware configuration to the storage device as one of the plurality of data . The central processing unit is
By executing the recommended hardware configuration creation program , a predetermined number of hardware is selected in ascending order of hardware price as the first condition, and the hardware is delivered in the order of early delivery as the second condition. The development information generation apparatus according to claim 10 , wherein a predetermined number of hardware is selected and information on a recommended hardware configuration is output to the storage device as one of the plurality of data .

Images