WO2016151865A1

WO2016151865A1 - Software selection system and method therefor

Info

Publication number: WO2016151865A1
Application number: PCT/JP2015/059513
Authority: WO
Inventors: 光一朗飯島; 大輔小牧; 啓生宮本; 湯本　一磨; 善弘水野; 恭福本
Original assignee: 株式会社日立製作所
Priority date: 2015-03-26
Filing date: 2015-03-26
Publication date: 2016-09-29

Abstract

A software selection system has: a database in which software component information that indicates a use record of a plurality of software components is recorded, the software component information including a functional requirement in which one or more functions of a software component are prescribed and a non-functional requirement in which a plurality of items as attributes of the function belonging to the functional requirement are prescribed; an estimation assistance terminal for inputting request information including the functional requirement and the non-functional requirement requested in a software component to be used for a new project; and an estimation assistance server for searching the database on the basis of the request information. The assistance server extracts, from the database, a combination of such software components that at least partial function in the functional requirement belonging to the software component information of the database conforms to the functional requirement belonging to the request information, and at least a part of the items in the non-functional requirement belonging to the software component information conforms to the non-functional requirement belonging to the request information, the software components having a record of being used at the same time in the past.

Description

Software selection system and method

The present invention relates to software design and estimation. For example, the present invention relates to a software selection system and method suitable for performing selection of software configuration relating to data collection and analysis, and rough estimation.

Conventionally, in the development of customer-specific or field-specific software systems, the customer requirements are ascertained from customer requests and interviews, and the system scale and development are roughly determined from past experience of sales and front system engineers. Calculate costs and implement proposals that include estimated prices for customers.

In the development of such software systems, software development costs can be reduced through development by selecting off-the-shelf Component type software combinations utilizing general-purpose software packages, or by diversion development based on past development. Is possible. Even in this case, as described above, from the past experience of sales and front system engineers, for example, select a software package with experience of use, or estimate the scale of modification from past experience of diversion development, the cost of development Estimate.

For example, in recent years, an M2M (Machine2Machine) system that measures and collects field information has advanced with the advancement and spread of sensor technology. In addition, technologies related to big data analysis that extract new knowledge and methods for improving work by collecting and statistically analyzing a large amount of sensor data collected and collected are also progressing.

In such systems related to M2M and big data, sensor device development, placement, and analysis methods after data collection must be customized according to customer requirements, while data collection and storage networks and DBMSs There are general-purpose software packages and software assets developed in the past for the statistical processing algorithm that is the base of the analysis method (Data Base Management System), and a software system can be constructed by combining them.

As a development of such a combination of existing software or software by diversion, for example, in Patent Document 1, a plurality of services prepared in advance are prepared particularly when software used for realizing a service of a leasing business is prepared in advance. In order to realize the service requested by the user based on the input information, means for detecting which service item of the service needs to be modified, and storing according to the detected information Means for obtaining software modification scale information by referring to the means and estimating the modification man-hour based on the information is disclosed.

Patent No. 4987357

However, Patent Document 1 is intended for modification of individual service functions in a series of software package products that have already been developed, and not for combinations of different software packages. For this reason, there is a problem that the number of man-hours for modification cannot be estimated in consideration of the development amount of the interface part such as the communication method between the plurality of software packages and the sharing of data.

Patent Document 1 holds information on which service executes a business function for business functions executed by a plurality of services prepared in advance, and is executed by the service requested by the user and the service. The function to be diverted is selected based on the correspondence relationship of the business functions, and there is a problem that the software cannot be selected due to non-functional requirements such as performance and reliability when there are multiple softwares that realize the same function.

Furthermore, in Patent Document 1, the scale of modification for each function is estimated and stored in advance, and there is a problem that the difference in scale of modification depending on the contents of modification cannot be considered. In addition, since the scale of modification for each function is recorded, there is a problem that it is impossible to take into consideration the development scale of the interface between the functions and the scale of newly added functions.

The present invention has been made in consideration of the above points, and selects a software component with a low development cost when constructing a software system.

In order to solve such a problem, the present invention provides a software including a functional requirement in which one or more functions of a software component are defined and a non-functional requirement in which a plurality of items that are attributes of functions belonging to the functional requirement are defined. Functions required for a software component used in a software system that is part information, in which software part information indicating the usage record of a plurality of software parts is recorded in association with each software part A function that belongs to the software component information by searching the software component information in the database based on the request information input to the estimate support terminal and the estimate support terminal that inputs request information including requirements and non-functional requirements At least some of the functions in the requirements conform to the functional requirements belonging to the requirement information, and An estimate for extracting a combination of software components that have been used in the past, and at least some of the non-functional requirements belonging to the software component information are software components that conform to the non-functional requirements belonging to the request information. And a support server.

According to the present invention, it is possible to select a software component with a low development cost.

It is a block diagram which shows the whole structure of the software selection system which concerns on this invention. It is a block diagram which shows the hardware constitutions and software constitution of each part which comprise a software selection system. It is a block diagram of the management table for managing software component information. It is a block diagram of the management table which manages the utilization performance information of a software component. It is a block diagram of an evaluation table. It is a block diagram of the input screen in an estimation assistance terminal. It is a block diagram of the output screen in an estimation assistance terminal. It is a flowchart for demonstrating the outline | summary of the selection method of a software component. It is a flowchart for demonstrating the production | generation / change process of the input item for requirement acquisition. It is a flowchart for demonstrating the process which extracts the optimal software component. It is a flowchart for demonstrating the production | generation method of a requirement pattern and a component pattern. It is a flowchart for demonstrating the process which patterns the combination of software components. It is a flowchart for demonstrating the method to extract a software component using a pattern. It is a flowchart for demonstrating the method to select a software component when there exists a defect in a non-functional requirement. It is a block diagram of the management table for managing the estimation result of the development amount of a software component.

(Outline of Examples)
In the present embodiment, it is assumed that the system is designed with a support tool of a front system engineer who creates a conceptual design of the system and a rough estimate through customer interviews at the initial stage of the software development process at the time of requirement acquisition and system proposal. The front system engineer may be, for example, a person in charge of negotiation with a customer in a system integration company, or a person in charge of system operation and development in a company.

The system engineer asks the customer about the need for new development (new project) of the software system, creates a conceptual design such as software configuration based on it, and estimates the development cost of the new development. At that time, the system engineer determines whether or not the software component including the existing software package and the past software asset (source code) that can be diverted can be used, and determines the software configuration suitable for the software system according to the determination result. . At this time, there are many general-purpose products, and for communication functions, data collection / conversion functions, and storage functions having high common functions, software components suitable for non-functional requirements such as real-time characteristics and development costs are selected.

In the support tool, software component groups that can be used in advance are registered in the database, and the results of hearing non-functional requirements from customers are input from the system engineer's operation terminal to support software components that match the hearing results. Extract on the server. Especially for the communication function, data collection / conversion function, and storage function, there are many general-purpose software components specialized for each function, and a software system is often built by combining multiple software components. . In this case, it is assumed that the presence / absence of the combination of the software parts has a great influence on the development cost because it relates to the development know-how of the interface between the software parts and the presence / absence of divertable source code.

Therefore, as a support tool, software that has been used at the same time in the past from among the software parts that meet the non-functional requirements as a result of interviews with customers is accumulated as a result of simultaneous use of software parts in the past. A function for extracting a combination of parts is required. In addition, for combinations of simple non-functional requirements that are frequently requested by customers, combinations of software components that are frequently used are extracted and stored in advance as software component patterns, and the accumulated software component patterns are given priority. By making proposals to customers, it is possible to promote the accumulation of development know-how and diversion codes. In addition, software that matches non-functional requirements by associating and storing a system architecture such as a system hardware configuration or network configuration (hereinafter sometimes referred to as a system configuration) and a software component pattern. It is possible to extract components that take into account differences due to hardware and network configurations.

(Example)
Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing the overall configuration of a software selection system according to the present invention. In FIG. 1, the software selection system includes an estimate support server 1001 that executes a software selection method, and information on software packages that can be selected by the estimate support server 1001 and source code (hereinafter referred to as software components) that can be used. A component information storage database (hereinafter sometimes referred to as DB) 1002 for storing software component information), a results management DB 1003 for recording the use results of software components in past development projects, and a component information storage DB 1002 A terminal that operates, manages, and maintains a component registration terminal 1004 that registers new software components, and a terminal that operates the estimate support server 1001. A front system engineer receives a request from a customer (user) Enter multiple information (request information) such as non-functional requirements by hearing It consists of an estimate support terminal 1005.

The estimation support server 1001 functions as a design / estimation support server that performs software design and estimation. Each estimate support terminal 1005 is connected to the estimate support server 1001 via the wide area network 1006. The estimation support server 1001, the component information storage DB 1002, the performance management DB 1003, and the component registration terminal 1004 are connected to each other via the local area network 1007 and function as a support tool. Note that a wide area network may be used instead of the local area network 1007.

FIG. 2 is a configuration diagram showing a hardware configuration and a software configuration of each unit constituting the software selection system. In FIG. 2, the estimation support server 1001 includes a CPU (Central Processing Unit) 2002, a memory 2003, a communication unit 2007, and an input / output device 2001 that are connected to each other via an internal bus. The CPU 2002 functions as a processor that executes various processes in accordance with a program (hereinafter also referred to as PG) stored in the memory 2003 and performs overall control of each part of the server. In the memory 2003, as a PG executed by the CPU 2002, a display PG2004 for generating a screen (input screen) for inputting requirements in each estimation support terminal 1005 and a screen (output screen) for displaying a component selection result, Stored are a component analysis PG2005 for analyzing the requirements for handling software components, and a component extraction PG2006 for selecting software components based on the requirements (request information) input from each estimation support terminal 1005. The communication unit 2007 functions as a communication interface that communicates with each estimation support terminal 1005 via the wide area network 1006, and via the local network 1007, the parts information accumulation DB 1002, the results management DB 1003, and the parts registration terminal 1004 Functions as a communication interface for communication. The input / output device 2001 includes an input device such as a mouse and a keyboard and an output device such as a printer and a liquid crystal display device.

The component information storage DB 1002 includes a CPU 2002, a memory 2003, a communication unit 2007, a component DB 2009, and an input / output device 2001 connected to each other via an internal bus. The CPU 2002 functions as a processor that executes various processes in accordance with the PG stored in the memory 2003 and controls the DB units. The memory 2003 stores an accumulation PG 2008 for accumulating software component information input from the component registration terminal 1002 in the component DB 2009 as a PG executed by the CPU 2002.

The performance management DB 1003 includes a CPU 2002, a memory 2003, a communication unit 2007, a requirement DB 2011, a combination performance DB 2012, and an input / output device 2001 connected to each other via an internal bus. The CPU 2002 functions as a processor that executes various processes in accordance with the PG stored in the memory 2003 and controls the DB units. In the memory 2003, as a PG executed by the CPU 2002, in response to an operation from each estimation support terminal 1005 and the estimation support server 1001, software component usage record information is stored in the requirement DB 2011 and the combination record DB 2012. The stored PG 2008 is stored.

The component registration terminal 1004 includes a CPU 2002, a memory 2003, a communication unit 2007, and an input / output device 2001 that are connected to each other via an internal bus. The CPU 2002 functions as a processor that executes various processes in accordance with the PG stored in the memory 2003, and controls each part of the terminal. The memory 2003 stores a component registration PG 2013 for registering component information in the component DB 2009 in cooperation with the storage PG 2008 as a PG executed by the CPU 2002.

Each estimation support terminal 1005 includes a CPU 2002, a memory 2003, a communication unit 2007, and an input / output device 2001 that are connected to each other via an internal bus. The CPU 2002 functions as a processor that executes various processes in accordance with the PG stored in the memory 2003, and controls each part of the terminal. The memory 2003 displays a requirement input screen (input screen) and a component selection result screen (output screen) on the input / output device 2001 in cooperation with the display PG2004 and the component extraction PG2006 as PG executed by the CPU 2002. The estimate acquisition PG2014 is stored.

FIG. 3 is a configuration diagram of a management table for managing software component information. In FIG. 3, a management table 300 is software component information including a functional requirement in which one or more functions of the software component are defined and a non-functional requirement in which a plurality of items that are attributes of functions belonging to the functional requirement are defined. It is a table for managing software component information that defines the specifications of software components. The management table 300 includes a key 301, a name 302, and a value 303, and is stored in the component DB 2009. In the key 301, identifier information (component ID) for uniquely identifying each software component is recorded. The component ID is an ID for identifying the software component, and a unique number is assigned to each unit of the software component selected in the software selection method of this embodiment when the software component is registered.

Name 302 is composed of name, function classification, function item, corresponding requirement / timeliness, corresponding requirement / reliability, ..., procurement price. The name is a name unique to each software component. In the value corresponding to the name, for example, “AAA ESB” is recorded as the value of the name of the component ID = 1. The function classification is a function that can be executed by the software component. In the value (Value) 303 corresponding to the function classification, “communication, collection” is recorded as the value of the function classification of the component ID = 1, for example, when the software component has the communication function and the data collection function. The The function item is an item of a function that can be executed by the software component. In the value 303 corresponding to this function item, for example, as the value of the function item of component ID = 1, for example, when the software component has various communication methods, “pub-sub, request-response” , "Naming service" is recorded.

Requirement requirement / timeliness means that software components have timeliness as non-functional requirements corresponding to functions. For example, “semi-real time” is recorded in the value 303 corresponding to the correspondence requirement / timeliness as the value of the correspondence requirement / timeliness of the component ID = 1. Corresponding requirement / reliability means that a software component has reliability as a non-functional requirement corresponding to a function. In the value 303 corresponding to the requirement / reliability, for example, “Non-stop, periodic maintenance” is recorded as the value of the requirement / reliability for the component ID = 1. The procurement price is a price that can be procured as each software component. In the value (Value) corresponding to the procurement price, for example, “10000000” is recorded as the value of the procurement price with the component ID = 1.

If the software component has a storage or communication function and a function item for managing a DB or file, “SQL, File-Storage” is recorded as the value of the function item. In addition, when a software component has timeliness as a non-functional requirement corresponding to a function and can be processed in “offline, online”, a value corresponding to the requirement / timeliness as “Value” "Offline, Online" is recorded.

As described above, each software component is registered with a name indicating each component, a function category and a function item indicating a functional requirement that can be supported, and a non-functional requirement item that can be supported as a specification of the software component. The applicable range is registered.

In this case, for example, in the software component with component ID = 1, the name is “AAA ESB”, and it has the functions of “communication” and “collection”. The function details of the software component with component ID = 1 include “pub-sub” “request-response” communication and “naming service” functions. As non-functional requirements, “semi-real-time” non-functional requirement items can be handled for non-functional requirement items, and for “non-functional requirement items of“ reliability ”,“ It is possible to cope with the reliability (presence or absence of stoppage) of either “non-stop” or “periodic maintenance”.

As the correspondence requirement of the non-functional requirement of the software component in this embodiment, the level of the non-functional requirement is indicated in a discrete category such as “semi-real time”, “offline”, “online”, but the communication speed etc. The method may be a continuous or quantitative expression, or any description method as long as it can compare the corresponding levels of non-functional requirements. By inputting these pieces of information from the component registration terminal 1004 and accumulating them in the component DB 2009, the software can be selected.

FIG. 4 is a configuration diagram of a management table for managing the usage history information of software components. In FIG. 4, a management table 400 is a table for managing the usage history information of software components, and is composed of a key 401, a name 402, and a value 403. Accumulated in DB1003 requirement DB2011 and combination DB2012.

As with the key 301, identifier information (component ID) for uniquely identifying each software component is recorded in the key 401. The name 402 is composed of a name, corresponding requirement / timeliness, corresponding requirement / reliability, and simultaneous use parts. Information similar to the value (Value) 303 is recorded in the value (Value) 403 corresponding to the name, the corresponding requirement / timeliness, and the corresponding requirement / reliability. The simultaneous use component is information for specifying another software component when each software component can be executed simultaneously with the other software component. In the value 403 corresponding to the simultaneous use component, for example, three software components (ID = 3, ID = 4, ID = 9) are executed as software components that can be executed simultaneously with the software component with ID = 1. If present, “ID = 3, ID = 4, ID = 9” is recorded as the value of the simultaneously used component with the component ID = 1.

In the usage history information of software parts, the contents of non-functional requirements that have actually been supported in the past are recorded as corresponding requirements, and information on parts that have been used at the same time is recorded.

From the usage information of software parts, for example, “AAA ESB” with part ID = 1 is used in projects where the timeliness (speed) is “semi-real-time” in the past, and the reliability is “non-stop”. It can be seen that it was used in the case of “periodic maintenance”. It can also be seen that “AAA ESB” with component ID = 1 was used at the same time as the software component with software component ID = 3,4,9. By creating and registering these pieces of information based on the results information input at the estimate support terminal 1005, it becomes possible to select requirements and combinations with results with priority when selecting software.

FIG. 5 is a configuration diagram of the evaluation table. In FIG. 5, an evaluation table 500 is a table for selecting requirement input items by the display PG 2004 of the estimation support server 1001, and includes items 501, values 502, and frequencies 503.

Item 501 is a non-functional requirement item, and information on “timeliness” and “reliability” is recorded in item 501. The value 502 is a non-functional requirement value, and information of “offline”, “online”, “semi-real time”, “real time”, “hard real time”, and “entropy” is recorded in the value 502. In the frequency 503, numerical information corresponding to the value 502 is recorded.

∙ For each non-functional requirement value of each non-functional requirement item, the number of corresponding products or the number of products that have been supported in past projects is counted, and the count value is accumulated in the evaluation table 500. At this time, for example, the entropy can be calculated from the count result, and the non-functional requirements that can deal with a wide range of values can be extracted.

For example, if the entropy of timeliness is “0.404” and the entropy of reliability is “0.278”, there is a software component that can support a wider range of requirement values for non-functional requirements for timeliness than reliability. You can see that it is registered. By making non-functional requirement items that can support a wide range of requirement values preferentially question items for customers, it is possible to narrow down to question items that are effective for selecting software components.

FIG. 6 is a configuration diagram of an input screen in the estimation support terminal. In FIG. 6, an input screen 600 is a display screen of the input / output device 2001 of the estimation support terminal 1005, and is a screen that accepts input from a front engineer.

The input screen 600 is used as a screen for a front engineer operating the estimate support terminal 1005 to input information (request information) of a new case or request extraction of software parts. In the display area of the input screen 600, a system configuration 601, a functional requirement 602, a non-functional requirement 603, a search condition 604, and the like are displayed.

In the system configuration 601 area, information for selecting and specifying the server configuration, communication path, and device is displayed. At this time, if the system configuration such as the server and communication path configuration is determined in advance, the front engineer inputs these pieces of information.

In the functional requirement 602 area, information for selecting and specifying the analysis function, the storage function, and the collection function is displayed. At this time, the front engineer inputs the functional requirements required in the case.

In the non-functional requirement 603 area, information for selecting and specifying timeliness and reliability is displayed. At this time, the front engineer inputs a non-functional requirement value (“offline”, “online”) to be dealt with in the case for each non-functional requirement item. Also, information indicating question items is displayed in the non-functional requirement 603 area.

In the area of the search condition 604, information for setting a priority condition when extracting software parts (“result priority”, “adaptation priority”, “procurement priority”) is displayed, and an OK button 605 is displayed. , NG button 606 is displayed.

FIG. 7 is a configuration diagram of an output screen in the estimation support terminal. In FIG. 7, an output screen 700 is a display screen of the input / output device 2001 of the estimation support terminal 1005, and recommends a combination of software components based on information (request information) of a new case input from the input screen 600. This is the output screen.

In the display area of the output screen 700, an extracted product list 701, an application record 702, and a new development item 703 required are displayed. In the area of the extracted product list 701, a list of software components extracted by the software component selection method executed in the component extraction PG2006 (for example, a combination of software components that have been used at the same time in the past) is displayed. . At this time, if there are a plurality of combination candidates, each candidate is also displayed. In this case, by operating any of the

selection buttons

704, 705, and 706, combinations of candidates 1 to 3 are displayed.

Supplementary information on the combination of the software parts is displayed in the area of the application record 702 and the new development item 703 required. For example, information indicating the usage record of the software combination is displayed in the application record 702 area, and information indicating functional items and non-functional requirements that are not supported in the new project is displayed in the area of the new development item 703 required. Is displayed.

FIG. 8 is a flowchart for explaining an outline of a method for selecting software components. This process is mainly executed by the component extraction PG2006 and the component analysis PG2005.

When the newly added software component information (software component information) is input to the component registration terminal 1004 from the input / output device 2001 of the component registration terminal 1004, the component registration PG2013 displays the input software component information, Transfer to the component information storage DB 1002 via the communication unit 2007. Thereafter, the storage PG 2008 of the component information storage DB 1002 registers the software component information transferred from the component registration terminal 1004 in the component DB 2009 (S11). At this time, in the component DB 2009, information on newly added software components is registered as information on software components to be extracted together with information on various software components used in the past. In other words, software component information of past and new software components that have been used in the past is registered and managed in the management table 300.

Next, one of the estimate support terminals 1005 activates the estimate acquisition PG2014, and through customer interviews, request information required for a new case (a software system to be newly constructed) (functional requirements indicating functions in the new case) And input of request information including non-functional requirements such as reliability (S12). At this time, the estimate support terminal 1005 displays the input screen of the requirement input generated by the display PG 2004 of the estimate support server 1001 on the display screen of the input / output device 2001, and uses the function requirements of the new matter as information by the operation of the system engineer. Or request information including non-functional requirements. The request information can also include information such as a contracted communication path, cloud, and virtualization as the system configuration of the new case. The processing of the display PG 2004 and the estimate acquisition PG 2014 in this step will be described in detail with reference to the flow of FIG.

Next, the estimate support server 1001 searches the software component information (software component information) registered in the component DB 2009 based on the request information input to the estimate support terminal 1005, and the software component registered in the component DB 2009. At least some of the functional requirements input to the estimate support terminal 1005 are compatible and at least some of the non-functional requirements are compatible from (software components registered in the management table 300) The extracted software parts are extracted and output (S13). At this time, the component extraction PG2006 is at least a part of the functional requirements input to the estimation support terminal 1005 from the software components (software components registered in the management table 400) registered in the combination DB2012 of the performance management DB1003. One or more software components that have been used at the same time in the past, and that have been used at the same time, and at least some of the non-functional requirements are compatible. (Software component information) can also be displayed on the screen by generating the display PG2004. In this step. The process of parts extraction PG2006 will be described in detail with reference to FIGS.

Finally, the estimate support server 1001 registers the information of the software parts actually used for selection and development as a usage history in the combination DB 2012 of the results management DB 1003 (S14). At this time, the estimate support server 1001 receives from the estimate support terminal 1005 the information of the software parts actually selected and used for development as the use history, and the combination information of the use of the software parts in the received use history, Registered in the combination DB 2012 of the performance management DB 1003, manages the registered information in the management table 400, and registers the requirement information corresponding to the new case in the requirements DB 2011 of the performance management DB 1003. In addition, the component analysis PG2005 of the estimate support server 1001 generates requirements and system configuration patterns corresponding to the new project. The processing in the component analysis PG2005 will be described in detail with reference to FIG.

FIG. 9 is a flowchart for explaining an input item generation / change process for acquiring requirements. This process is the specific content of step S12 of FIG. 8, and is mainly executed by the display PG 2004 and the estimate acquisition PG 2014.

First, the estimate acquisition PG 2014 of the estimate support terminal 1005 is information on non-functional requirements that can be handled by all software components, and is stored in the component DB 2009 of the component information storage DB 1002 and the requirement DB 2011 of the results management DB 1003. A list of non-functional requirements that can be handled by the software component (range of non-functional requirements) is acquired (S21). The non-functional requirement information acquired here is a set of items indicating the type of non-functional requirements such as “timeliness” and values indicating the level of non-functional requirements such as “real time” and “offline”. . A plurality of items may be registered for the value indicating the level of non-functional requirements. In addition, the level of non-functional requirements may be registered in the parts DB 2009 at the time of new registration as a part specification, or may be accumulated in the requirements DB 2011 as a requirement with a corresponding track record during past development. .

Next, estimate acquisition PG2014, for each non-functional requirement item (items such as “timeliness”), the size of the range that can be supported by all software components (value that can be supported by all software components (non-functional) The size of requirement level) is evaluated (S22). This evaluation method may be any method as long as it can compare the diversity of requirements that can be handled by all registered software components. For example, the appearance probability of a value indicating the level of the non-functional requirement is calculated for each item of the non-functional requirement, and the information entropy is calculated for each item of the non-functional requirement by the following equation (1).

Next, the estimate acquisition PG 2014 refers to the management table 500 indicating the analysis result, and extracts one or more items having a large applicable range (the level of non-functional requirements is large) (S23). At this time, for example, a non-functional requirement item (“timeliness”) having a high information entropy among each non-functional requirement item may be extracted in a predetermined number, or each non-functional requirement item may be extracted. Of these items, only non-functional requirement items whose information entropy is higher than a prescribed value may be extracted.

Finally, the estimate acquisition PG 2014 generates a question item for the customer based on the item of the non-functional requirement extracted in step S23, for example, “timeliness” of the non-functional requirement (S24). At this time, the display PG 2004 generates a screen for displaying the items of the non-functional requirements extracted by the estimate acquisition PG 2014 on the display screen of the input / output device 2001 and for hearing from the customer. This screen may be in any format as long as the customer can input an answer regarding the items of non-functional requirements extracted by the estimate acquisition PG 2014. For example, a non-functional requirement item extracted by the estimate acquisition PG 2014 may be displayed in a list and a non-functional requirement value corresponding to the non-functional requirement item may be selected.

At this time, the estimate acquisition PG 2014 refers to the software component information of the component DB 2009 and receives each software stored in the component DB 2009 when receiving request information including the functional requirement and non-functional requirement of the new matter as a question item from the user. For each non-functional requirement item included in the requirement information, evaluate the size of the range that can be handled, and extract and extract the non-functional requirement item with a large range that can be handled from this evaluation result. Part of the question items can be changed according to the non-functional requirement items. For this reason, it is possible to narrow down to question items effective for selecting software components.

FIG. 10 is a flowchart for explaining the process of extracting the optimum software component. This process is the specific content of step S13 in FIG. 8, and is mainly executed by the component extraction PG2006 of the estimation support server 1001.

First, the parts extraction PG2006 of the estimate support server 1001 acquires the requirements (request information) of the new case by the processing shown in step S12 and step S12 in FIG. 8 and step S21 in FIG. 9 (S31). At this time, in addition to the above-described non-functional requirements, if there are functional requirements to be dealt with, they are additionally acquired. In addition, when there is a restriction on the system configuration, such as when there is an existing system or when the basic hardware configuration has already been determined, it is additionally acquired.

Next, the component extraction PG2006 searches the compatible component list (management table 300) based on the functional requirements of the new project, and creates a new one from the software component information registered in the component DB2009 (management table 300). Only one or more software components that conform to the description of the functional requirements of the case are acquired (S32). For example, when the functional requirement of the new case is “communication”, the software component in which “communication” is recorded in the functional requirement of the software component information is acquired. This acquisition method may search for items whose function classifications and function items described as part specifications match the description of the functional requirements of the new project, or define missing values and similarity of terms, Either a fuzzy search for evaluating the degree of coincidence or either method may be used.

Next, the component extraction PG2006 narrows down only the extracted software components that can meet the non-functional requirements (S33). For example, if “Reliability” is recorded as a non-functional requirement item for a new project, only the software components for which “Reliability” is defined as a non-functional requirement among the extracted software components And

Thereafter, the component extraction PG 2006 determines whether the priority extraction condition is “result priority” or “function priority” for the combination of software components narrowed down in step S33 (S34). If it is determined in step S34 that "result priority", that is, if the preset component extraction condition is result priority, the component extraction PG 2006 searches the management table 400 and the software narrowed down in step S33. A combination of software parts that have been used in the past is extracted from the parts (S35). At this time, the component extraction PG2006 is a combination of software components that have been used in the past among the narrowed-down software components (the component whose value 403 is recorded as a simultaneously used component in the management table 400) (A combination of software parts specified by ID) is extracted.

After that, the component extraction PG2006 extracts (selects) a combination that matches the system configuration assumed by the new case from among the combinations of software components that have been used in the past (S36). Exit.

Here, the system configuration assumed for a new project includes the presence and type of IT processing hardware such as already installed or contracted communication paths, cloud, and virtualization. In the extracted combination of software parts, a combination of software parts having a record matching the system configuration is selected. When the system configuration includes software component information used by an existing system, a combination of software components that have been used with the existing software component is selected.

On the other hand, if it is determined in step S34 that “function priority”, the component extraction PG 2006 selects a software component with few duplicated or insufficient function items from among the functional requirements of the new item from the software components narrowed down in step S34. A combination is extracted (S37), and the processing in this routine is terminated.

In addition, after step S35, a step for determining whether or not the system configuration has been determined is added, and when a positive determination result is obtained in this step, that is, when the system configuration is determined in advance by the customer (When there is information related to the system configuration in the new case in the request information), the parts extraction PG 2006 selects the system configuration determined in advance, and then executes the process of step S36, and the system configuration is determined. If it is determined that the processing has not been completed, the processing in this routine can be terminated. Further, after step S32 or after step S35, a step of determining whether the procurement price of the software component is within the set price range is added, and the procurement price of the software component is within the set price range. On the condition, the part extraction PG2006 can also execute the process of step S33 or step S35.

FIG. 11 is a flowchart for explaining a generation method of a requirement pattern / part pattern. This process is the specific content of step S14 of FIG. 8, and is executed by the component analysis PG2005 of the estimation support server 1001.

First, the component analysis PG2005 of the estimation support server 1001 corresponds to a non-functionality corresponding to a case implemented in the system development using the software components (for example, software components with high information entropy) extracted in steps S11 to S13 in FIG. The requirement items (“reliability”, “timeliness”) and the values of the non-functional requirements (“offline”, “online”) are input from the estimation support terminal 1005 (S41).

Next, the parts analysis PG 2005 inputs the system configuration in the case from the estimate support terminal 1005 (S42). Here, the system configuration includes the presence and type of IT processing hardware such as already installed or contracted communication paths, cloud, and virtualization. Moreover, the identifier of the software component used in the existing system may be included.

Next, the component analysis PG 2005 inputs the identifier of the software component used in the case (S43).

Finally, the parts analysis PG2005 uses the information (software parts information and system configuration information) of the relevant matter (the matter implemented in the system development) entered in steps S41 to S43, and the past information that has already been entered. From the case information (software component information and system configuration information), a combination of software components is patterned, the pattern is analyzed (S44), and the processing in this routine is terminated. Details of step S44 will be described in detail with reference to FIG.

FIG. 12 is a flowchart for explaining processing for patterning combinations of software components. This process is the specific content of step S44 in FIG. 11, and is executed by the component analysis PG2005 of the estimation support server 1001.

First, the parts analysis PG2005 of the estimation support server 1001 classifies the system configuration in the past results into representative patterns, and calculates representative points from the classified patterns (S51). As this classification method, for example, the system configuration in each case, and information (items) of the system configuration applied to the software components used in each case, for example, “cloud”, “wireless LAN”, etc. The presence / absence of the correspondence (implementation) is expressed side by side and expressed as a vector. If each item matches, the value is set to “0”, otherwise, the value is set to “1”, and the Hamming distance is evaluated. A predetermined number of system configuration patterns are obtained by the hierarchical clustering method. In addition, as a representative point calculation method, for example, the mode value of the system configuration classified into the same pattern (the one with the highest performance among the patterned system configurations) may be used as the representative point. For all two combinations in the information, the distance may be calculated, and the system configuration of the case with the smallest total value of the calculated distances may be used as the representative point.

Next, the parts analysis PG 2005 classifies the non-functional requirements in each case with past results into representative patterns, and calculates representative points from the classified patterns (S52). In this classification method, for example, as in step S51, values of non-functional requirements (“real time”, “online”) are arranged and expressed as vectors, and a specified number of representative values are obtained by hierarchical clustering using the Hamming distance and the Ward method. Get a non-functional requirement pattern.

Finally, the parts analysis PG2005 calculates which system configuration pattern and non-functional requirement pattern match each past case, and for the calculated system configuration pattern / non-functional requirement pattern pair, The combination of software components used at the same time (the combination of software components with a track record that has been used in the past) is registered in the combination DB 2012 of the track record management DB 1003 (S53), and the processing in this routine is terminated. The calculation method to calculate which system configuration pattern and non-functional requirement pattern match each past case is that the case and the representative point of each pattern, if the pattern creation method is hierarchical clustering by the Ward method And the pattern with the closest calculated Hamming distance is set as the pattern to which the matter belongs.

In the above processing, the estimation support server 1001 classifies the system configuration applied to each software component recorded in the component DB 2009 for each item, patterns the classified system configuration items according to the presence or absence of correspondence, The representative points of the system configuration are extracted from the system configuration, and the non-functional requirements belonging to each software component recorded in the parts DB 2009 are classified according to the value of the item of the non-functional requirements. Each software component recorded in the component DB 2009 is created by patterning the value of the functional requirement item according to the presence or absence of correspondence, extracting the representative points of the non-functional requirement from the patterned non-functional requirement item values Of these, a combination of software components whose system configuration item matches the representative point of the system configuration and whose non-functional requirement item value matches the representative point of the non-functional requirement Will be recorded in the combination DB 2012 as a combination of software components.

FIG. 13 is a flowchart for explaining a method of extracting software parts using a pattern. This process is different from the process of FIG. 10 and is a software component extraction method using the pattern calculated in step S53 of FIG. 12, and is executed by the component extraction PG2006 of the estimation support server 1001.

First, the component extraction PG 2006 of the estimate support server 1001 acquires the requirement (request information) of the new case from the estimate support terminal 1005 as in step S31 of FIG. 10 (S61).

Next, as in step S32, the component extraction PG2006 searches the compatible component list (management table 300) based on the functional requirements of the new case, and newly selects the software component registered in the component DB 2009. Only software components that conform to the description of the functional requirements of the case are acquired (S62).

Next, the component extraction PG 2006 extracts a representative point of the non-functional requirement closest to the non-functional requirement of the new case as a non-functional requirement pattern based on the software component acquired in step S62 (S63).

Next, the part extraction PG2006 determines whether or not the system configuration has been determined (S64). When a positive determination result is obtained in step S64, that is, when the system configuration is determined in advance by the customer, the part extraction PG2006 selects a pattern closest to the representative point in the system configuration pattern determined in advance. Select (S65). If the pattern creation method is hierarchical clustering by the Ward method, the representative point is calculated by calculating the Hamming distance between the case and the representative point of each pattern, and the pattern with the closest Hamming distance The pattern to which the configuration belongs.

Finally, the component extraction PG2006 searches the combination DB2012 of the performance management DB1003 based on the pattern selected in step S65 and the non-functional requirement pattern extracted in step S63, and the system configuration pattern / non-functional requirement in the combination DB2012. A combination of software components registered in the pattern (a combination of software components that have been used in the past at the same time) is extracted (S66), and the processing in this routine is terminated. In step S66, the pattern not including the software component searched in step S62 is deleted.

On the other hand, if a negative determination result is obtained in step S64, that is, if the system configuration has not been determined in advance by the customer, the component extraction PG2006 uses the combination of software components registered in the non-functional requirement pattern as the system. A configuration example is extracted (S67), and the processing in this routine is terminated. At this time, if the extracted combination of software parts is information of a system configuration corresponding to the past, the information is output.

In step S63, it is assumed that the representative point of the extracted non-functional requirement does not completely correspond to the non-functional requirement desired by the customer. It is required to develop non-functional requirements that are not supported by developing UP based on the extracted software components.

In the above processing, when the estimate support server 1001 inputs the request information from the estimate support terminal 1005, the non-functional requirements belonging to the request information are classified according to the value of the non-functional requirement item, and the classified non-function Requirement item values are patterned according to whether they are supported, non-functional requirement representative points are extracted from the patterned non-functional requirement item values, and the system configuration of the new matter is included in the request information If there is information on the system configuration, the system configuration of the new project is classified for each item, the classified system configuration items are patterned according to whether they are supported, and the representative points of the system configuration from the patterned system configuration The combination DB2012 is searched based on the extracted representative points of the extracted non-functional requirements and the extracted representative points of the system configuration. Representative points of the system configuration and the extracted representative points requirement is to extract a combination of software components that match, respectively.

FIG. 14 is a flowchart for explaining a method of selecting a software component when there is a defect in non-functional requirements. In this process, the extracted software components have a gap between the corresponding non-functional requirements and the non-functional requirements required for the new project, and when a newly developed part due to UP occurs, This is a process for selection, and is executed by the component analysis PG2005 of the estimation support server 1001.

First, the parts analysis PG2005 of the estimate support server 1001 searches the performance management DB 1003 and acquires the development amount when there is a flawed requirement and has been handled by UP development in the past (S71). At this time, if there are similar cases multiple times in the past, the average value of the development amount is calculated.

Next, the parts analysis PG2005 acquires the development amount of the extracted software parts in the past UP development (S72).

Finally, the component analysis PG2005 estimates the development amount of the software component in the requirement as the predicted development man-hour from the past average development amount for each requirement and the past average development amount of the software component (S73). The process in is terminated. The estimated amount of development man-hours can be any method that reflects the amount of development for each requirement and the difficulty of UP development for each software component, and can be compared for multiple software components. For example, the development amount may be estimated based on the weighted average shown in Expression (2) and FIG.

C (software part i, requirement j) = average development amount of requirement j × (average development amount of software part i / total development amount of all software components) ... Formula (2)

FIG. 15 is a configuration diagram of a management table for managing the estimation results of the software component development amount. In FIG. 15, a management table 1500 is a table for managing the estimation results of the development amounts of a plurality of software components estimated in step S73 of FIG. 14, and includes a product name 1501, UP development step number 1502, non-function It consists of requirement 1503 and UP development step number 1504.

In the product name 1501, for example, information on part A, part B, and part C is recorded as names of a plurality of software parts. The non-functional requirement 1503 records information on timeliness, reliability, security, and capacity. Corresponding to each requirement of the non-functional requirement 1503, each part is recorded with a numerical value indicating the man-hour in development in the past. At this time, numerical information indicating the average man-hour of each part is recorded in the UP development step number 1502 corresponding to each requirement of the non-functional requirement 1503, and the UP development step number 1504 is recorded in the average man-hour of each part. Is recorded as numerical information.

For example, component A requires 1750 steps (average) in the past development. On the other hand, man-hours in the past development of the requirement “timeliness” require an average of 1000 steps. When development related to timeliness is required for part A, if the average development amount is estimated by equation (2), it is estimated that 1842.1 steps of modification are necessary.

According to this embodiment, when building a software system, it is possible to select a software component with a low development cost. That is, since a combination of proven software parts that have been used at the same time in the past is extracted from the combination DB 2012 of the result management DB 1003, it is possible to select a software part with a low development cost.

In addition, this invention is not limited to the above-mentioned Example, Various modifications are included. For example, the component information storage DB 1002 and the performance management DB 1003 can be configured as a single DB, or the component DB 2009, the combination DB 2012, and the requirement DB 2011 can be arranged in the estimation support server 1001, respectively. Further, the estimate support terminal 1005 can be arranged on the estimate support server 1001 and integrated. The above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.

Also, each of the above-described configurations, functions, etc. may be realized by hardware by designing a part or all of them, for example, by an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files that realize each function is stored in memory, a hard disk, a recording device such as an SSD (Solid State Drive), an IC (Integrated Circuit) card, an SD (Secure Digital) memory card, a DVD ( It can be recorded on a recording medium such as Digital Versatile Disc).

1001 Estimate support server, 1002 Parts information storage DB, 1003 Results management DB, 1004 Parts registration terminal, 1005 Estimate support terminal, 1006 Wide area network, 1007 Local area network, 2001 Input / output device, 2002 CPU, 2003 memory, 2004 Display PG, 2005 parts analysis PG, 2006 parts extraction PG, 2007 communication department, 2008 storage PG, 2009 parts DB, 2010 storage PG, 2011 requirements DB, 2012 combination DB, 2013 parts registration PG, 2014 estimate acquisition PG.

Claims

Software component information including a functional requirement in which one or more functions of the software component are defined and a non-functional requirement in which a plurality of items that are attributes of functions belonging to the functional requirement are defined, and the use of the plurality of software components A database in which software component information indicating the results is recorded in association with each software component;
An estimate support terminal for inputting request information including functional requirements and non-functional requirements required for software components used in a software system to be a new matter;
The software component information in the database is searched based on the request information input to the estimation support terminal, and at least a part of the functional requirements belonging to the software component information belongs to the request information. And a software component that has been used in the past, and is a software component that conforms to the non-functional requirement belonging to the requirement information, at least a part of the non-functional requirement belonging to the software component information. A software selection system comprising: an estimation support server that extracts a combination of
The software selection system according to claim 1,
The estimate support server includes:
A software selection system characterized by extracting a combination of software parts with a track record that has been used in the past when extracting a combination of software parts with a track record that has been used in the past.
The software selection system according to claim 1,
The estimate support server includes:
Extracting a combination of software parts with a track record used in the past on the condition that the track record has priority over the function, and when there is information about the system configuration of the new case in the request information, A software selection system that extracts a combination of software parts that matches the system configuration of the new item from the extracted combination of software parts.
The software selection system according to claim 1,
The estimate support server includes:
A software selection system characterized in that a condition for extracting a combination of software parts with a track record used in the past is set such that a procurement price of the software parts is within a set price range.
The software selection system according to claim 1,
The estimate support server includes:
The system configuration applied to each software component recorded in the database is classified for each item, the classified system configuration items are patterned according to the presence or absence of correspondence, and a system is selected from the patterned system configurations. The representative points of the configuration are extracted, the non-functional requirements belonging to each software component recorded in the database are classified for each non-functional requirement item value, and the classified non-functional requirement item values are supported. It is patterned according to the presence or absence of, the representative points of the non-functional requirements are extracted from the patterned non-functional requirement item values, and among the software components recorded in the database, the system configuration item is A combination of software components that matches the representative point of the system configuration and whose non-functional requirement item value matches the representative point of the non-functional requirement is executed. Software selection system, characterized in that recorded in the database as a combination of software components with.
The software selection system according to claim 5,
The estimate support server includes:
When the request information is input, the non-functional requirements belonging to the request information are classified according to the value of the non-functional requirement item, and the value of the classified non-functional requirement item is determined according to the presence or absence of correspondence. When a representative point of the non-functional requirement is extracted from the patterned non-functional requirement item value and information related to the system configuration of the new case exists in the request information, the new case The system configuration is classified for each item, the classified system configuration items are patterned according to the presence or absence of correspondence, a representative point of the system configuration is extracted from the patterned system configuration, and the extracted non-configuration The database is searched based on the representative points of the functional requirements and the representative points of the extracted system configuration, and the representative of the extracted non-functional requirements from among the combinations of the proven software parts. Software selection system, wherein the representative point of the extracted system configuration to extract a combination of software components that match respectively.
The software selection system according to claim 1,
The estimate support terminal is
When inputting the request information as a question item, the software component information in the database is referred to, and for each software component stored in the database, a response is made for each item of non-functional requirements included in the request information. It is characterized by evaluating the size of a possible range, extracting a non-functional requirement item having a large applicable range from the evaluation result, and changing a part of the question item according to the extracted non-functional requirement item. Software selection system to do.
The software selection system according to claim 1,
The estimate support terminal is
An input screen for inputting the request information and an output screen for displaying information from the estimate support server, and a system configuration, functional requirements and non-functional requirements for the new matter in the display area of the input screen A software selection system characterized by displaying information relating to and displaying a combination of software components extracted by the estimation support server in a display area of the output screen.
The software selection system according to claim 1,
The database is
A database for recording information from a component registration terminal, wherein a functional requirement in which one or more functions of the software component are defined and a non-functional requirement in which a plurality of items that are attributes of functions belonging to the functional requirement are defined; A component information accumulation database in which software component information including
Software component information indicating the usage results of the plurality of software components is configured from a performance management database recorded in association with each software component,
The parts information accumulation database and the results management database are:
Each is connected to the estimate support server,
The estimate support server includes:
A software selection system connected to the estimate support terminal via a network.
Software component information including a functional requirement in which one or more functions of the software component are defined and a non-functional requirement in which a plurality of items that are attributes of functions belonging to the functional requirement are defined, and the use of the plurality of software components A database in which software component information indicating the results is recorded in association with each software component;
An estimate support terminal for inputting request information including functional requirements and non-functional requirements required for software components used in a software system to be a new matter;
A software selection method in a system comprising: an estimate support server that searches software component information in the database based on request information input to the estimate support terminal,
The support server, as a result of the search, has at least a part of the functional requirements belonging to the software component information conform to the functional requirements belonging to the request information, and among the non-functional requirements belonging to the software component information. A software selection method comprising a step of extracting a combination of software parts that have been used in the past and that have at least some items that are software parts that conform to non-functional requirements belonging to the request information.
A software selection method according to claim 10, comprising:
The estimate support server includes:
In the step, when a combination of software parts with a track record that has been used in the past is extracted, a combination of software components with a track record that has been used at the same time in the past is extracted.
A software selection method according to claim 10, comprising:
The estimate support server includes:
In the step, on the condition that the performance is prioritized over the function, a combination of software components with a track record that has been used in the past is extracted, and information regarding the system configuration of the new matter exists in the request information In this case, a software selection method characterized by extracting a combination of software components that matches the system configuration of the new item from the extracted combination of software components.
A software selection method according to claim 10, comprising:
The estimate support server includes:
In the step, a condition for extracting a combination of proven software parts used in the past is set such that a procurement price of the software parts is within a set price range. .
A software selection method according to claim 10, comprising:
The estimate support server includes:
In the step, the system configuration applied to each software component recorded in the database is classified for each item, the classified system configuration items are patterned according to the presence or absence of correspondence, and the patterned system configuration The representative points of the system configuration are extracted from the above, the non-functional requirements belonging to each software component recorded in the database are classified for each value of the non-functional requirement item, and the classified non-functional requirement item The value of the function is patterned according to the presence or absence of correspondence, the representative point of the non-functional requirement is extracted from the patterned value of the non-functional requirement item, and among the software parts recorded in the database, the system The software part in which the configuration item matches the representative point of the system configuration and the value of the non-functional requirement item matches the representative point of the non-functional requirement Software selection method characterized by the combination, as a combination of software components that are proven record in the database.
The software selection method according to claim 14, comprising:
The estimate support server includes:
When the request information is input, the non-functional requirements belonging to the request information are classified according to the value of the non-functional requirement item, and the value of the classified non-functional requirement item is determined according to the presence or absence of correspondence. When a representative point of the non-functional requirement is extracted from the patterned non-functional requirement item value and information related to the system configuration of the new case exists in the request information, the new case The system configuration is classified for each item, the classified system configuration items are patterned according to the presence or absence of correspondence, a representative point of the system configuration is extracted from the patterned system configuration, and the extracted non-configuration The database is searched based on the representative points of the functional requirements and the representative points of the extracted system configuration, and the representative of the extracted non-functional requirements from among the combinations of the proven software parts. Software selection method characterized in that the representative point of the extracted system configured to extract a combination of software components that match, respectively.