JP2015170100A - Software article proposal system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a software article proposal system for proposing an appropriate software article in response to the actual situations of a utilization entity.SOLUTION: A software article proposal system 1 includes: a database 11 for recording software article information data and operation log data; and an arithmetic part 12 which selects a software article that the utilization entity should utilize, on the basis of the software article information data and the operation log data acquired from the database 11 and generates proposal software article data indicating a result of the selection. Article information indicated by the software article information data includes an operation that is executable when utilizing a software article. The arithmetic part 12 selects a software article that becomes article information matched to operation of the utilization entity indicated by the operation log data from among software articles indicated by the software article information data and generates the proposal software article data.

Description

  The present invention relates to a software product proposal system for proposing software products to be adopted.

  In recent years, software development has become active, and paid or free products (hereinafter referred to as “software products”) targeting various software have appeared in the world. In particular, the use of document creation and spreadsheets is common, but various types of software products with different executable operations (functions) have appeared in the world, so the choice of software products has expanded. Yes.

  Typically, such software products are renewed every few years or months (for example, re-agreement due to expiration of the license validity period) or replacement of old software products with new software products (for example, Replacement due to expiration of support period for old software products). Therefore, an opportunity to review software products to be used comes every few years or every few months.

  However, in spite of the regular arrival of such opportunities, the user (a computer that uses a software product and is at least one of a computer and a user for which a license is to be set; the same applies hereinafter). This is a problem because it is possible to ignore the actual situation and continue to use high-performance and expensive software products.

  Specifically, for example, when an administrator who decides whether or not to adopt a software product in a company wants to review the software product used by each employee, the work content and the presence / absence of skills related to the software product for each employee, etc. You must grasp the specific circumstances of each. However, when there are many employees in a large company or the like, it is practically impossible to grasp individual specific circumstances for each employee. For this reason, the administrator can select a low-function, low-priced, or free software product by mistake, and at the same time, all the employees are uniformly and highly functional so as not to interfere with their work. In addition, expensive software products will be selected.

  Patent Document 1 proposes a system that predicts the appropriate number of floating license purchases for a specific software product. However, this system does not select an appropriate software product from a plurality of software products.

JP 2012-185536 A

  An object of the present invention is to provide a software product proposal system for proposing an appropriate software product according to the actual situation of a user.

  In order to achieve the above object, a software product proposal system according to the present invention includes software product information data indicating product information of each of a plurality of software products having a common use, and a user who is at least one of a computer and a user A database for recording operation log data indicating a history of operations executed when using the product, and the software to be used by the user based on the software product information data and the operation log data acquired from the database An operation unit that selects a product and generates proposed software product data indicating the selection result, and the product information indicated by the software product information data includes an operation that can be performed when the software product is used. The calculation unit is the software. The proposed software product data is generated by selecting the software product that is the product information suitable for the operation of the user indicated by the operation log data from the software product indicated by the product information data. And

  According to this software product proposal system, it is possible to select and propose a software product suitable for the actual usage status of the software product by the user.

  Furthermore, in the software product proposal system having the above-described feature, the calculation unit performs the use executed at a predetermined frequency or more in a predetermined period indicated by the operation log data from the software products indicated by the software product information data. It is preferable to generate the proposed software product data by selecting the software product that can execute the operation of the subject most frequently.

  According to this software product proposal system, it is possible to select and propose a software product that can execute an operation that is highly likely to be executed by the user.

  Furthermore, in the software product proposal system having the above characteristics, the calculation unit performs all operations of the user who have been executed during a predetermined period indicated by the operation log data from the software products indicated by the software product information data. It is preferable to generate the proposed software product data by selecting the software product that can execute the above.

  According to this software product proposal system, it is possible to select and propose a software product that can execute all operations that the user may perform.

  Furthermore, in the software product proposal system having the above characteristics, the product information indicated by the software product information data includes a price of the software product, and the calculation unit includes the software product information indicated by the software product information data. If there are a plurality of the software products that are the product information suitable for the operation of the user indicated by the operation log data, the software product with the lowest price is selected from the software products, and the proposed software It is preferable to generate product data.

  According to this software product proposal system, it is possible to select and propose software products that are most economical and easy to introduce among software products that match the actual usage status of software products by the user. Become.

  Furthermore, in the software product proposal system having the above characteristics, preferably, the proposed software product data includes data associating the use subject with the software product selected by the calculation unit for the use subject. .

  According to this software product proposal system, it is possible for an administrator who decides whether or not to accept a software product to specifically grasp the software product to be adopted for each user.

  Furthermore, in the software product proposal system having the above characteristics, the calculation unit selects the software product one by one for each of the plurality of users, and the software product and the software product are selected from the software product. It is preferable that data relating the total number selected by the calculation unit is included in the proposed software product data.

  According to this software product proposal system, it is possible for an administrator who decides whether or not to accept a software product to grasp the total number of software products to be adopted in the entire organization to which the user belongs. .

  According to the software product proposal system having the above characteristics, it is possible to select and propose a software product suitable for the actual usage status of the software product by the user. Therefore, it is possible to propose an appropriate software product according to the actual situation of the user.

The block diagram shown about an example of the structure of the software goods proposal system which concerns on embodiment of this invention. The figure shown about an example of software merchandise information data. The figure shown about an example of operation log data. The figure shown about an example of proposal software merchandise data. The figure shown about another example of proposal software merchandise data. The figure shown about the further another example of proposal software merchandise data. The figure shown about another example of software merchandise information data and proposal software merchandise data. The figure shown about the further another example of software product information data and proposal software product data.

  In the following description of the software product proposal system according to the embodiment of the present invention, “software product” includes products targeted for one piece of software for specific uses such as document creation and spreadsheets. . In this case, for example, realization of some functions in software such as creation of new file, editing, printing, use of function, image editing, and the like corresponds to “operation” of the software product.

  In addition, the “software product” includes a product (so-called software suite or the like) for a plurality of software bundled in an abstract application such as office work or design. In this case, for example, in addition to (or instead of) realizing some functions in the software as described above, execution of some software in the software suite itself corresponds to “operation” of the software product. That is, the software itself included in the software suite itself corresponds to the “operation” of the software product.

  The “software” that is the target of the software product includes software executed on a computer that is directly used by a user. In this case, executing software on the computer corresponds to “use” of the software product.

  The “software” that is the target of the software product includes software (so-called web application software, server application software, etc.) executed on the server computer in accordance with a request from the client computer used directly by the user. . In this case, executing software on the server computer corresponds to “use” of the software product.

  However, in the following, for the sake of concrete explanation, the software product is intended for one software executed on a computer used directly by the user, and the license of the software product is granted to the computer. First, a case where the software product proposal system according to the embodiment of the present invention is used when the administrator considers updating of the license of the software product will be described first. And about various cases different from this example, after explaining this example, it demonstrates centering on the difference with this example.

  First, an example of the configuration of a software product proposal system according to an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an example of the configuration of a software product proposal system according to an embodiment of the present invention.

  As shown in FIG. 1, the software product proposal system 1 according to the embodiment of the present invention includes a database 11, a calculation unit 12, and an output unit 13.

  The database 11 records software product information data and operation log data. The software product information data indicates product information of each of a plurality of software products having a common use. The operation log data is input to the database 11 from each computer 20 via the bus 30 and is data indicating a history of operations executed by the computer 20 when using the software product. Further, for example, the database 11 is configured to include a recording device such as a hard disk or a semiconductor memory.

  Based on the software product information data and operation log data acquired from the database 11, the calculation unit 12 selects a software product to be used by the user, and generates proposed software product data indicating the selection result. For example, the calculation unit 12 includes a calculation device such as a CPU (Central Processing Unit) and a memory that temporarily stores data during calculation.

  The output unit 13 acquires the proposed software product data from the calculation unit 12, and notifies the administrator who determines whether or not to accept the software product, the selection result of the software product indicated by the proposed software product data. Further, for example, the output unit 13 includes a display device that displays the selection result of the software product indicated by the proposed software product data as an image such as a character or a table.

  Next, an example of the operation of the software product proposal system 1 will be described with reference to the drawings. FIG. 2 is a diagram illustrating an example of software product information data. FIG. 3 is a diagram illustrating an example of operation log data. FIG. 4 is a diagram illustrating an example of the proposed software product data.

  The software product information data illustrated in FIG. 2 includes “product name” that is software product identification information, “price” that is software product price information, and specific operations A to G when the software product is used. “Operation A” to “Operation G”, which are information indicating whether or not execution is possible, are included. Here, with regard to “operation A” to “operation G”, a circle (○) indicates an operation that can be executed when using the software product, and a cross (×) indicates an operation that cannot be executed when using the software product. Is shown.

  The software product identification information is, for example, information indicating a product name, a model number, and the like (the same applies hereinafter). Further, the price information of software products is information indicating, for example, a fixed price, an average market price, a sales price at a specific seller, and the like (hereinafter the same). Note that the price information of software products may be information indicating these prices as they are, but prices that take into consideration that the validity period and support period of the license for each software product are different (specifically, for example, future use) It may be information indicating a price during a certain period (for example, a price per year).

  The software product information data illustrated in FIG. 2 indicates that the software product X1 is a software product whose price is V1 and all operations A to G are executable. Further, the software product information data illustrated in FIG. 2 indicates that the software product X2 is a software product whose price is V2 and operations A to C can be executed. The software product information data illustrated in FIG. 2 indicates that the software product X3 is a software product whose price is V3 and operations A and B can be executed. In general, the prices V1 to V3 of software products increase as the number of operations that can be performed increases, and thus V1> V2> V3.

  The software product information data is generated by, for example, an administrator and recorded in the database 11. The software product information data may be data automatically generated by extracting information from a predetermined website (for example, the website of a manufacturer or seller of software products), or externally (for example, Data distributed from a software product manufacturer or seller) and recorded in the database 11 may be used.

  The operation log data illustrated in FIG. 3 includes “computer” that is identification information of the computer 20, “user” that is identification information of the user who uses the computer 20, and identification information of the software product used by the computer 20. Information that indicates a certain “product name”, “execution operation” that is information indicating the executed operation, “file” that is information indicating a file that is the target of the executed operation, and a recording location of the file “Location” and “Date and time” which is information indicating the date and time when the operation was executed (in this example, year / month / day / hour / minute / second) are included.

  The identification information of the computer 20 is, for example, information indicating a computer name set for the computer 20 by a user, an administrator, or the like, a serial number of the computer 20, and the like (hereinafter the same). The user identification information is, for example, information indicating the login name of the user when using the computer 20 (the same applies hereinafter).

  The operation log data illustrated in FIG. 3 indicates that the software product X1 is used in the computer Y1 whose user is U1, and at least the operation A, the operation B, the operation C, and the operation F are executed. . Further, the operation log data illustrated in FIG. 3 indicates that the software product X1 is used and at least the operation A, the operation B, and the operation C are executed in the computer Y2 whose user is U2.

  The operation log data is generated, for example, by sequentially recording operations performed in each computer 20. The operation log data created by each computer 20 is transmitted from the outside at a predetermined timing (for example, every time a predetermined time elapses or every time a predetermined number of operations are recorded in the computer 20). Each time an instruction to do so is input, etc.), it is transmitted from the computer 20 and recorded in the database 11.

  Then, the calculation unit 12 selects a software product to be used by the computer 20 based on the software product information data and operation log data acquired from the database 11, and generates proposed software product data indicating the selection result. At this time, the calculation unit 12 selects a software product that is product information suitable for the operation of the computer 20 indicated by the operation log data from the software products indicated by the software product information data.

  For example, the calculation unit 12 performs an operation of the computer 20 that is executed at a predetermined frequency or more during a predetermined period indicated by the operation log data (for example, a predetermined number of times in the most recent years) from the software products indicated by the software product information data. The software product that can execute the most executed operation) is selected. Thereby, the calculating part 12 can select the software goods which can perform operation with high possibility that the computer 20 will perform.

  In addition, for example, the calculation unit 12 selects a software product that can execute all the operations of the computer 20 (for example, operations performed at least once in the most recent years) performed during a predetermined period. Thereby, the calculating part 12 can select the software goods which can perform all the operations which the computer 20 may perform.

  In addition, when there are a plurality of software products that are candidates for selection, the calculation unit 12 selects the software product with the lowest price (that is, the software product with the least economic burden and easy to introduce).

  Here, a method of selecting software products by the calculation unit 12 will be described with a specific example.

  First, it is assumed that the operations executed at a predetermined frequency or higher in the computer Y1 are the operation A, the operation B, the operation C, and the operation F. In this case, operations A and B can be executed using any of software X1 to X3, operation C can be executed using software products X2 and X3, and operation F uses software product X1. Only possible if. Therefore, the calculation unit 12 selects the software product X1 that can execute all of the operation A, the operation B, the operation C, and the operation F for the computer Y1.

  In addition, it is assumed that the operations executed at a predetermined frequency or more in the predetermined period in the computer Y2 are the operation A, the operation B, and the operation C. In this case, the operations A and B can be executed using any of the software X1 to X3, and the operation C can be executed using the software products X2 and X3. However, at this time, there are two software products X1 and X2 that can execute all of the operations A, B, and C. Therefore, the calculation unit 12 selects the software X2 having a low price among the software products X1 and X2.

  And the calculating part 12 produces | generates the proposal software merchandise data which shows the selection result by said selection method which is illustrated in FIG. The proposed software product data illustrated in FIG. 4 includes data that associates the computer 20 with the software product selected by the calculation unit 12 for the computer 20.

  The proposed software product data illustrated in FIG. 4 includes “computer” that is identification information of the computer 20, “in-use product name” that is identification information of the software product currently used by the computer 20, and the calculation unit 12. “Proposal product name” which is identification information of the software product selected by “”, “Proposal price” which is price information of the software product selected by the calculation unit 12, and “Proposal price” And “reduction cost”, which is information indicating a value obtained by subtracting the price indicated by “price” (that is, the price of the software product selected by the calculation unit 12).

  The proposed software product data illustrated in FIG. 4 indicates that the software product X1 is selected for the computer Y1. Further, the proposed software product data illustrated in FIG. 4 indicates that the software product X2 is selected for the computer Y2.

  Then, the content of the proposed software product data generated by the calculation unit 12 (for example, the table illustrated in FIG. 4) is notified to the administrator by the output unit 13. As a result, the manager can determine whether to accept the software product after referring to the software product proposed by the software product proposal system 1.

  As described above, according to the software product proposal system 1 according to the embodiment of the present invention, it is possible to select and propose a software product suitable for the actual use status of the software product by the computer 20. Therefore, it is possible to propose an appropriate software product according to the actual situation of the computer 20.

  Further, the calculation unit 12 generates the proposed software product data indicating the software product selected for each computer 20 as illustrated in FIG. The software product to be adopted for the computer 20 can be specifically grasped.

  In the above example, “user”, “file”, and “location” in the operation log data illustrated in FIG. 3 are essential for the calculation unit 12 to generate the proposed software product data illustrated in FIG. Is not. Therefore, “user”, “file”, and “location” may not be included in the operation log data. However, as will be described later, when the user can be included in the user, “user” needs to be included in the operation log data. Further, in this case, if the computer is not included in the use subject, the “computer” may not be included in the operation log data.

  In the above example, one computer 20 is assigned to one user, and the computer 20 and the user correspond one-to-one. In this case, since it is possible to identify the computer 20 and the user, it is possible to treat the user as a user in addition to (or instead of) the computer 20.

  Here, an example of the proposed software product data generated by the calculation unit 12 when the user is treated as a user will be described with reference to the drawings. FIG. 5 is a diagram showing another example of the proposed software product data.

  The proposed software product data illustrated in FIG. 5 includes “user”, which is user identification information, instead of the “computer” of the proposed software product data illustrated in FIG. The proposed software product data illustrated in FIG. 5 may include both “computer” and “user”.

  The proposed software product data illustrated in FIGS. 4 and 5 may include information indicating the total amount of “reduction costs”. The total amount of the “reduction costs” may be simply the sum of the “reduction costs” or may reflect a discount according to the number of purchased software products. However, in the latter case, it is assumed that information regarding this discount is included in the software product information data illustrated in FIG.

  With this configuration, it becomes possible to appeal to the manager who decides whether to adopt the data software product, the necessity of reselecting the software product expressed by the total amount of “reduction cost”.

  Further, in addition to (or instead of) the proposed software product data, in which the user and the software product are associated with each other as illustrated in FIGS. 4 and 5, the calculation unit 12 converts the software product and the software product. Data including the selected total number may be included.

  Here, an example of the proposed software product data indicating the total number of selected software products will be described with reference to the drawings. FIG. 6 is a diagram showing still another example of the proposed software product data.

  The proposed software product data illustrated in FIG. 6 includes “product name” that is software product identification information, “price” that is software product price information, and the total number of software products currently used by the computer 20. And “total number of products in use”, which is information indicating the total number of software products selected by the calculation unit 12, and “total number of proposed products”.

  The proposed software product data illustrated in FIG. 6 indicates that the software product X1 is currently used in all of the N0 computers 20. Further, in the proposed software product data illustrated in FIG. 6, the calculation unit 12 selects the software product X1 for the N1 computers 20, selects the software product X2 for the N2 computers 20, and sets N3 This indicates that the software product X3 has been selected for the computer 20. In this example, N0 = N1 + N2 + N3.

  As described above, the calculation unit 12 generates the proposed software product data indicating the total number of the selected software products as illustrated in FIG. It is possible to grasp the total number of software products to be adopted by the entire organization to which the software belongs.

  Similarly to the proposed software product data illustrated in FIGS. 4 and 5, the proposed software product data illustrated in FIG. 6 includes information indicating “reduced cost” and the total amount of “reduced cost”. May be.

<Deformation, etc.>
[1] The software product proposal system 1 according to the embodiment of the present invention is not limited to the case of considering the update of the license of the software product as in the above example, but the case of considering the replacement of the old software product with the new software product. Can also be used.

  Here, the operation of the software product proposal system 1 when considering replacement of an old software product with a new software product will be described with reference to the drawings. FIG. 7 is a diagram illustrating another example of the software product information data and the proposed software product data. FIG. 7A is a diagram showing software product information data, and FIG. 7B is a diagram showing proposed software product data.

  The software product information data illustrated in FIG. 7A includes not only information about old software products X1 to X3 but also information about new software products X11 to X13 that are being considered for replacement. Except for this point, the software product information data illustrated in FIG. 7A is the same as the software product information data illustrated in FIG. It is preferable that the old software products X1 to X3 and the new software products X11 to X13 are distinguished in the software product information data by, for example, the presence or absence of a flag.

  Further, the proposed software product data illustrated in FIG. 7B is generated when the calculation unit 12 selects a software product to be proposed to the computer 20 from the software products X11 to X13 to be replaced. The Except for this point, the proposed software product data illustrated in FIG. 7B is the same as the proposed software product data illustrated in FIG.

  As described above, by including the information on the software products X11 to X13 to be replaced in the software product information data, the calculation unit 12 selects the software product that is actually considering replacement by the computer 20. It becomes possible. Therefore, for example, even when there is a difference in an executable operation between the old software and the new software, the arithmetic unit 12 considers such a difference and then selects an appropriate software product for the computer 20. It becomes possible to select.

  Note that the proposed software product data illustrated in FIG. 7B may include information indicating the total amount of “reduction cost” or may not include information of “reduction cost”. Good.

  Further, when the calculation unit 12 selects a software product that can execute all the operations of the computer 20 executed during a predetermined period indicated by the operation log data, the software product X11 to X13 to be replaced is included. When there is no item that can execute all of the operations, the calculation unit 12 may generate proposed software product data indicating that selection is impossible, or all software products X11 to be replaced. The proposed software product data may be generated by excluding operations that cannot be executed in X13 and then performing selection again.

[2] The software product proposal system 1 according to the embodiment of the present invention is not limited to the case where the user is limited to the computer 20 as in the above-described example, but can be used when the user is limited to the user. It can also be used when the user is not limited to one of the computer 20 and the user (that is, when the user can be a computer or a user).

  When the user is limited to the user, the calculation unit 12 performs an operation in which “computer” in the above example is simply changed to “user”. Specifically, the computing unit 12 selects a software product that is product information suitable for the user operation indicated by the operation log data from the software products indicated by the software product information data, and the proposed software indicating the selection result Generate product data.

  On the other hand, when the user is not limited to one of the computer 20 and the user, the calculation unit 12 selects a software product that is product information suitable for each operation of the computer 20 and the user. The operation of the software product proposal system 1 in this case will be described with reference to the drawings. FIG. 8 is a diagram showing still another example of the software product information data and the proposed software product data. FIG. 8A is a diagram showing software product information data, and FIG. 8B is a diagram showing proposed software product data.

  The software product information data illustrated in FIG. 8A includes “target” which is information indicating a license setting target, and includes not only information regarding software products X1 to X3 whose license setting target is a computer. Also included is information regarding the software product X21 whose license is to be set by the user. Except for these points, the software product information data illustrated in FIG. 8A is the same as the software product information data illustrated in FIG.

  In addition, the proposed software product data illustrated in FIG. 8B is generated by the calculation unit 12 selecting a software product that is product information suitable for each operation of the computer 20 and the user. . Except for this point, the proposed software product data illustrated in FIG. 8B is the same as the proposed software product data illustrated in FIG.

  Here, a specific example of the operation of the calculation unit 12 when generating the proposed software product data illustrated in FIG. 8B will be described.

  First, when the computer Y21 is the only user U21, or when the computer Y22 is the only user U22 and the computer and the user can be identified, the calculation unit 12 is similar to the above example. In addition, the software product suitable for the computer and the user operation indicated by the operation log data is simply selected from the software products X1 to X3, X21, and X22 indicated by the software product information data.

  The proposed software product data illustrated in FIG. 8B indicates that the software product X1 is selected for the computer Y21 (user U21). Further, the proposed software product data illustrated in FIG. 8B indicates that the software product X22 is selected for the user U22 (computer Y22).

  In addition, when one computer Y23 is used by two users U231 and U232, and when three computers Y241 to Y243 are used by two users U241 and U242, the computer and the user are identified. If the computer 20 and the user do not have a one-to-one correspondence, the computing unit 12 selects a software product for the computer, and selects a software product for the user. , The software product is selected.

  Specifically, for example, the calculation unit 12 is adapted to match the total amount when selecting the software products X1 to X3 for each computer so as to suit the operation of each computer, and the operation of each user. The total price when selecting software products X21 and X22 for each user is compared, and the one with the lower price is selected.

  The proposed software product data illustrated in FIG. 8B indicates that the software product X2 is selected for the computer Y23 in the combination of the computer Y23 and the users U231 and U232. In addition, the proposed software product data illustrated in FIG. 8B includes software products X21 selected for the user U241 and software products for the user U242 in the combination of the computers Y241 to Y243 and the users U241 and U242. X21 is selected.

  As described above, the software product proposal system 1 according to the embodiment of the present invention selects and proposes a software product suitable for the operation of the user, regardless of how the user uses the computer. be able to.

  Note that the proposed software product data illustrated in FIG. 8B may include information indicating the total amount of “reduction cost” or may not include information of “reduction cost”. Good.

[3] In the above example, the calculation unit 12 selects one software product for one user, but the calculation unit 12 may select two or more software products. For example, the calculation unit 12 may select all software products that are suitable for the operation of the user, or software products that are compatible with the operation of the user and are below a predetermined price (or from the lowest price). All of the predetermined number of software products) may be selected.

  In this case, the administrator notified of the contents of the proposed software product data by the output unit 13 determines the software product to be finally adopted with reference to the plurality of proposed software products. However, also in this case, since an appropriate software product according to the actual condition of the user is proposed to the administrator, it is possible to easily select the software product to be adopted by the administrator.

[4] In the above example, the calculation unit 12 preferentially selects a software product that is suitable for the operation of the user and has a low price. However, in addition to (or instead of) the price, the calculation unit 12 may select a software product according to a priority order based on another index.

  Other indexes include, for example, a manufacturer of software products, a user who uses the software products, and the type of software. Specifically, for example, selecting a software product according to a priority order based on the manufacturer of the software product means preferentially selecting a software product manufactured by a manufacturer with a large share and high reliability. In addition, for example, selecting a software product according to a priority order based on a user who uses the software product means preferentially selecting a software product for a computer (or a user). In addition, for example, selecting a software product according to a priority order based on the type of software targets software executed on a computer used directly by a user (or software executed on a server computer). A software product is selected preferentially.

  However, when the calculation unit 12 selects the software product according to the priority order based on the other index, the other index for each software product is similar to the “price” in the software product information data illustrated in FIG. It is assumed that the information on the software product information data is included.

  The present invention can be used in a software product proposal system that proposes software products to be adopted.

1: Software product proposal system 11: Database 12: Operation unit 13: Output unit 20: Computer 30: Bus

Claims (6)

Software product information data indicating product information of each of a plurality of software products having a common use, operation log data indicating a history of operations performed by a user who is at least one of a computer and a user when using the software products, A database that records
Based on the software product information data acquired from the database and the operation log data, the software product to be used by the user is selected, and a calculation unit that generates proposed software product data indicating the selection result; Prepared,
The product information indicated by the software product information data includes operations that can be executed when using the software product,
The calculation unit selects the software product to be the product information suitable for the operation of the user indicated by the operation log data from the software products indicated by the software product information data, and the proposed software product A software product proposal system characterized by generating data.   The arithmetic unit can execute the operation of the user subject executed most frequently at a predetermined frequency or more during a predetermined period indicated by the operation log data from the software products indicated by the software product information data. 2. The software product proposal system according to claim 1, wherein the software product data is generated by selecting the software product.   The calculation unit selects the software product that can execute all the operations of the user executed during a predetermined period indicated by the operation log data, from the software products indicated by the software product information data. The software product proposal system according to claim 1, wherein the software product product data is generated. The product information indicated by the software product information data includes a price of the software product,
When the software product indicated by the software product information data includes a plurality of software products that are the product information suitable for the operation of the user indicated by the operation log data, The software product proposal system according to any one of claims 1 to 3, wherein the software product data having the lowest price is selected and the proposed software product data is generated.   5. The proposed software product data includes data associating the use subject with the software product selected by the calculation unit with respect to the use subject. Software product proposal system according to item. The calculation unit selects one software product for each of the plurality of users.
The data associating the software product with the total number of the software products selected by the calculation unit is included in the proposed software product data. Software product proposal system.

Images