JP5997315B1 - Asset management apparatus, asset management method, and program - Google Patents

Abstract

An object of the present invention is to provide a technology that supports the creation of an estimate. A storage unit that stores information including an order record of software used for estimation, and an index calculation unit that calculates an index indicating the value of the software using the order record. A software extraction unit that extracts candidate software that is a candidate for use in the new estimate by referring to the storage unit using a search condition relating to the new estimate, the candidate software, and the candidate software calculated by the index calculation unit And a display information generation unit that generates display information indicating the index. [Selection] Figure 1

Description

  The present invention relates to an asset management device, an asset management method, and a program.

  Patent Document 1 states that “a collection unit that collects development assets, which is a set of development products obtained as a result of application development work, and a system of the development assets among the development assets collected by the collection unit. A classification key information creation unit that creates a function dictionary in which functions of the development asset are dictionaryd as key information for classifying each development product from the function definition file defined by the function, and a development asset collected by the collection unit A dictionary for storing a process dictionary in which development functions other than the function definition file are specified using the function dictionary and the process of development work is dictionaryd By identifying the process to which the development product is assigned using the storage unit, the function and process of the identified development product are associated with each other. A structure dictionary generation unit that generates a structure dictionary in which the structure of the development asset is converted into a dictionary; and when the designation of the function is received, each development product included in the development asset with reference to the structure dictionary If the development product grouped in the same function is grouped by function and the hierarchical structure of the development assets grouped by the process is displayed in a list, and the designation of the process is accepted, the structure dictionary is referred to. And an explorer for displaying a list of hierarchical structures of development assets obtained by grouping development products included in the development asset by process and grouping development products grouped in the same process by the function. A featured development asset management device "is disclosed.

JP, 2014-074963, A

  It is necessary to clarify the development scope and specifications when creating an estimate in contract software development. However, in reality, there are cases where the scope of development and specifications are not clear when estimating the size and amount of software. In this case, it takes time to reach an order after agreeing with the customer on the scope of development. On the other hand, even if information about software created in the past is held, it is difficult to say that such information is effectively used in creating a new estimate.

  Since the technique disclosed in Patent Document 1 does not assume the creation of an estimate, it does not contribute to the creation of an efficient estimate.

  The present invention has been made in view of the above points, and an object of the present invention is to provide a technique for supporting the creation of an estimate.

  The present application includes a plurality of means for solving the above-described problems, and examples thereof are as follows.

In order to solve the above-described problem, the asset management apparatus of the present invention uses the storage unit that stores the identification information for identifying the software used for the quotation and the order record of the software in association with each other , and uses the order record. An index calculation unit that calculates an index indicating the value of software, a software extraction unit that extracts candidate software that is a candidate for use in the new estimate by referring to the storage unit using a search condition related to the new estimate, and the candidate Software and the index of the candidate software calculated by the index calculation unit are displayed in association with each other, and display information on a search result screen for receiving selection of software to be used in the new estimate from the candidate software is generated. with a display information generation unit, a new identification number to a selected said software from among the candidate software Characterized in that it comprises a and a software registration section for registering in the storage unit as the software used in the estimate Te.

In order to solve the above problems, in the storage unit, the identification information and, wherein the identification information of the software referenced is software that was used to estimate of the software to identify the software used in the estimate is associated, the index calculation unit uses the received orders before Kiso software are higher in the reference relationship may be characterized by calculating the index of the candidate software.

In order to solve the above problem, the storage unit stores asset points calculated by the index calculation unit using information indicating an order amount or an order quantity as the order record, and the index calculation unit includes: using the asset points associated with the identification information before Kiso software may also be characterized by calculating the asset point of the candidate software as the index.

In order to solve the above problem, the storage unit stores order information indicating whether or not the software has been received as an order record, and the index calculation unit includes order information indicating that an order has been received. The order number of the candidate software may be calculated as the index using the number of the software that is higher in the reference relationship .

  In order to solve the above problem, the asset management apparatus of the present invention includes a search condition extraction unit that extracts a character string as the search condition from input information input to the new estimate registration screen for registering the new estimate. The display information generation unit may generate the display information indicating the number of the character strings included in the software extracted by the software extraction unit.

  In order to solve the above problem, the storage unit may store license information indicating whether or not the software has a license, and the software extraction unit may extract the software having the license. .

In order to solve the above-described problem, the asset management method of the present invention includes an index calculation procedure for calculating an index indicating the value of the software using an order record of the software used for the estimate, and a search condition for the new estimate. A software extraction procedure for extracting candidate software that is a candidate for use in the new estimate by referring to a storage unit that stores the identification information for identifying the software used for the estimate and the received order of the software in association with each other. A search result screen that displays the candidate software in association with the index of the candidate software calculated in the index calculation procedure and accepts selection of software to be used in the new estimate from the candidate software a display information generating step of generating information before selected from among the candidate software And executes and a software registration procedure for registering in the storage unit as the software used in the estimate are given the new identification number to the software.

In order to solve the above-described problem, the program of the present invention is a program that causes a computer to function as an asset management apparatus, and calculates an index indicating the value of the software using an order record of software used for estimation. Using the index calculation procedure and the search condition for the new quotation , the identification unit for identifying the software used for the quotation and the storage unit that stores the received orders of the software in association with each other are referred to and used for the new quotation. A software extraction procedure for extracting candidate software that is a candidate, the candidate software, and the index of the candidate software calculated in the index calculation procedure are displayed in association with each other, and selection of software to be used in the new estimate is selected. to generate a display information of the search result screen for accepting from among the candidate software Run the display information generating procedure, and a software registration procedure for registering in the storage unit as the software used in the estimate are given the new identification number to a selected said software from among the candidate software to the computer It is characterized by making it.

  According to the present invention, it is possible to provide a technology that supports the creation of an estimate.

  Problems, configurations, and effects other than those described above will be clarified by the following description of embodiments.

It is a business flow realized by using the asset management system according to the present embodiment. It is a block diagram which shows an example of a function structure of an asset management system. It is a figure which shows an example of customer information. It is a figure which shows an example of prototype information. It is a figure which shows an example of project information. It is a figure which shows the hardware structural example of a server apparatus. It is a flowchart which shows an example of a prototype information generation process. It is a flowchart which shows an example of a prototype search process. It is a flowchart which shows an example of an order information registration process. It is a flowchart which shows an example of the prototype search process in a modification. It is a figure which shows an example of a project registration screen. It is a figure which shows an example of a search result screen. It is a figure which shows an example of a search result detailed screen. It is a figure which shows an example of a prototype search screen.

  Hereinafter, examples of embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a business flow realized by using the asset management system 1 according to the present embodiment.

  In order software development, it takes time to create an estimate when the development scope and specifications are not clear. Therefore, in this workflow, a software prototype (prototype) is created at the time of estimation and stored as an asset. When creating a new software estimate, an effective estimate is supported by creating a new prototype by referring to a suitable prototype from the accumulated prototypes.

  First, when the user receives an estimate request from a customer ((1) in the figure), the business flow shifts to the estimate phase ((2) in the figure). In the estimation phase, first, the user inputs the contents of an estimate request to the asset management system 1 ((2-1) in the figure). The information to be input is not limited to the specification and the development range, and may be, for example, information on the preference of the customer staff.

  The asset management system 1 extracts candidate prototypes corresponding to the current estimate from prototypes created in the past based on the contents of the request for quotation and presents them to the user ((2-2) in the figure). At that time, the asset management system 1 calculates and presents an index to be referred to by the user when selecting a prototype from the candidate prototypes. When the user selects a prototype to be a base for the quotation from the presented candidate prototypes, the selected prototype is registered as a new prototype.

  The user determines the specifications of the product to be estimated based on the customer's request, and edits the registered prototype to create a prototype to be presented to the customer along with the estimate. The created prototype is changed as needed due to changes in specifications and ideas proposed to customers.

  The user creates an estimate based on the created prototype ((2-3) in the figure). When an order for software development related to an estimate is received ((3) in the figure) and the order results such as the order amount and order quantity are entered by the user, the order results are associated with the prototype, and the next estimate is created. To be able to refer to. In other words, the created prototype is stored as an available asset.

  Thereafter, the software development for which the order is received is carried out ((4) in the figure). If there is a change in the development content from the estimate, the registered prototype may be changed.

  As described above, the asset management system 1 enables presentation of candidate prototypes for selecting a prototype to be used as a reference when creating an estimate. In addition, a prototype selected from candidate prototypes is used to create a prototype to be presented to the customer along with the estimate. By creating an estimate using the created prototype, it is possible to efficiently create an estimate. In addition, since the prototype is presented to the customer, the customer can specifically grasp the image of the product related to the estimate, and the period until the order can be shortened. In addition, as the accumulation of prototypes as assets increases, prototypes that more closely match customer needs can be created and presented.

  FIG. 2 is a block diagram illustrating an example of a functional configuration of the asset management system. In the asset management system 1, the server device 10 and the terminal device 20 are connected via a network 30.

  The server device 10 is a server computer, for example, and realizes a function as an asset management device that manages prototypes as assets. The terminal device 20 is an information processing device such as a PC, a PDA (Personal Digital Assistant), or a smartphone, and is operated by a user such as an estimate creator. As shown in FIG. 2, one or a plurality of terminal devices 20 are connected to one server device 10. The server device 10 has a function as a web server, for example, and provides a service related to prototype management to the terminal device 20 through a browser. Note that part of the functions of the server device 10 may be realized by another information processing device.

  The server device 10 includes a control unit 110, a storage unit 120, and a communication unit 130. The control unit 110 controls processing related to prototype management in the present embodiment. The storage unit 120 stores data necessary for the processing of the control unit 110. The communication unit 130 controls communication between the server device 10 and the customer terminal device 20 via the network 30.

  The control unit 110 includes a search condition extraction unit 111, a prototype extraction unit 112, an index calculation unit 113, a display information generation unit 114, and a prototype registration unit 115.

  The search condition extraction unit 111 extracts a character string as a search condition from information input on the project registration screen for registering a project relating to a new estimate. Details will be described later.

  In the present embodiment, a project is created for each business unit proposed to a customer. One or more prototypes are associated with one project. For convenience, it is assumed that a new prototype is created every time an estimate is created, and that an order is received or lost for a project. In addition, since the prototype can be said to be information indicating an outline of the software scheduled to be developed, it can be said that the prototype itself is software.

  The prototype extraction unit 112 refers to the storage unit 120 using the search condition, and extracts candidate prototypes that are candidates for use in the new estimate.

  The index calculation unit 113 calculates an index indicating the value of the prototype based on the received order results such as the received order amount and the received order amount for the received project. The index calculation unit 113 calculates, for example, a prototype order rate, asset points, and the like as indexes, which will be described later in detail.

  The display information generation unit 114 generates display information of a search result screen in which candidate prototypes are associated with indexes calculated for the prototypes. Further, the display information generation unit 114 generates display information for displaying a search result detail screen showing details of the search results.

  The prototype registration unit 115 registers the prototype selected from the candidate prototypes displayed on the search result screen in the storage unit 120 as a new prototype. In addition, the prototype registration unit 115 accepts a change to the already registered prototype, and updates the information stored in the storage unit 120.

  The storage unit 120 stores customer information 121, prototype information 122, and project information 123. The customer information 121 is information related to a customer who is an ordering source of software, and includes company information 1211, group information 1212, and person-in-charge information 1213.

  The company information 1211 is information related to the ordering company. The group information 1212 is information related to a department in the ordering company. The person-in-charge information 1213 is information relating to the person in charge of the ordering company. The prototype information 122 is information related to a registered prototype. The project information 123 is information related to a software project to be developed.

  FIG. 3 is a diagram illustrating an example of the customer information 121. FIG. 3A shows an example of company information 1211. The company information 1211 includes a company identifier 1211a, a name 1211b, a color 1211c, a scale 1211d, a business type 1211e, a registration date 1211f, and a remark 1211g as columns. The company information 1211 has a record specified by the company identifier 1211a.

  The company identifier 1211a is identification information for specifying the ordering company. The name 1211b is an ordering company name. The color 1211c is a company image color. The scale 1211d is information indicating the scale of the company and is, for example, the number of employees or capital. The business type 1211e is information indicating the business type and characteristics of the company, and may be information indicating the focused business type, for example, if the company has a wide variety of business types. The registration date 1211f is information indicating the date and time when the company information 1211 is generated. The remark 1211g is remark information that is freely input to the company, but may be the latest trend of the company, for example.

  FIG. 3B shows an example of the group information 1212. The group information 1212 includes a group identifier 1212a, a name 1212b, a company identifier 1212c, a mission 1212d, a type 1212e, a color 1212f, a scale 1212g, a registration date 1212h, and a remark 1212i as columns. The group information 1212 has a record specified by the group identifier 1212a.

  The group identifier 1212a is an identifier for specifying a group. The name 1212b is information indicating a group name. The company identifier 1212c is an identifier for specifying the company to which the group belongs, and may correspond to the company identifier 1211a of the company information 1211. The mission 1212d is information indicating a role to be played as a group such as a department or section in the company. For example, the mission 1212d is a character string indicating “new business development”.

  Type 1212e is information indicating the characteristics of the group. For example, the type 1212e is a character string indicating “quality-oriented”, “delivery-oriented” or “customer-request-oriented”. The color 1212f is information indicating a color used as a basic tone in the role of the group. The scale 1212g is information indicating the scale of the group. The registration date 1212h is information indicating the registration date and time of the group information 1212. The remark 1212i is remark information that is freely input for the group.

  FIG. 3C shows an example of person-in-charge information 1213. The person-in-charge information 1213 includes a person-in-charge identifier 1213a, a name 1213b, a company identifier 1213c, a group identifier 1213d, a preference 1213e, a hobby 1213f, a type 1213g, a registration date 1213h, and a remark 1213i. . The person-in-charge information 1213 has a record specified by the person-in-charge identifier 1213a.

  The person-in-charge identifier 1213a is identification information that identifies the person in charge. The name 1213b is information indicating the person in charge name. The company identifier 1213c is identification information that identifies the company to which the person in charge belongs, and may correspond to the company identifier 1211a of the company information 1211. The group identifier 1213d is information for identifying the group to which the person in charge belongs, and may correspond to the group identifier 1212a of the group information 1212.

  The preference 1213e is information indicating the preference of the person in charge. For example, the preference 1213e is a character string such as “cool GUI (graphical user interface)”, “beautiful color”, or “futuristic”. The hobby 1213f is information indicating the hobby of the person in charge, and is a character string such as “reading” or “drive”, for example. The type 1213g is information indicating the personality and characteristics of the person in charge, and is a character string such as “like flashy” or “researcher type”, for example.

  The registration date 1213h is information indicating the registration date and time of the person-in-charge information 1213. Remarks 1213i are remark information that is freely input for the person in charge.

  Note that the customer information 121 may not include all of the information described above, or may include other information. Any information may be used as long as it registers information related to customers useful for search.

  FIG. 4 is a diagram illustrating an example of the prototype information 122. The prototype information 122 includes a prototype identifier 122a, a name 122b, a concept 122c, details 122d, a development environment 122e, an operating environment 122f, a scale 122g, an asset point 122h, a cumulative asset point i, a registered repository path. 122j, reference repository path 122k, reference revision 122l, registration date 122m, and remarks 122n are included as columns. The prototype information 122 has a record specified by the prototype identifier 122a.

  The prototype identifier 122a is identification information that identifies a prototype. The name 122b is information indicating the name of the prototype. The concept 122c is information indicating the concept of software to be developed, and is a character string such as “cool GUI”, for example. Details 122d are information indicating specifications and functions required for software. The development environment 122e is information indicating a development environment such as a development language or a compiler used for software development. The operating environment 122f is information indicating an environment in which the software operates, and is a character string such as “Windows (registered trademark) 8”.

  The scale 122g is information indicating the scale of software, and is, for example, the number of lines of source code, the number of screens presented by the software, and the like. The asset point 122h is an index indicating the value of the software, and is calculated based on the actual order received when the software is ordered. The calculation of asset points will be described later.

  The accumulated asset point 122i is a total asset point of the prototype positioned higher in the prototype reference relationship. Although details will be described later, another prototype may be referred to in the generation of the prototype. The referenced prototype is assumed to be located above the prototype to be generated. There may be further referenced prototypes in the referenced prototype, but these are all positioned above the generated prototype. The accumulated asset point is the total of the prototype asset points positioned higher in the prototype reference relationship.

  The registration repository path 122j is information for specifying a prototype storage location, and is uniquely determined for the prototype identifier 122a. The reference repository path 122k is information indicating a storage location of another prototype when there is another prototype referred to by the prototype related to the prototype identifier 122a.

  The reference revision 122l is information indicating a prototype version to be referred to. The registration repository path 122j, the reference repository path 122k, and the reference revision 122l are useful when, for example, version management software that manages the revision of software is used in parallel with the present system. The registration date 122m is information indicating the registration date and time of the prototype information 122. Remark 122n is remark information that is freely input for the prototype.

  Note that the prototype information 122 may not include all of the above-described information, as with the customer information 121, or may include other information.

  FIG. 5 is a diagram illustrating an example of the project information 123. The project information 123 includes a project identifier 123a, a name 123b, a mission 123c, a type 123d, details 123e, a scale 123f, an operating environment 123g, a related project identifier 123h, an order flag 123i, and a related prototype 123j. , Technology 123k, license form 123l, MVP 123m, customer identifier 123n, registration date 123o, and remarks 123p. The project information 123 has a record specified by the project identifier 123a.

  The project identifier 123a is identification information that identifies a project. The name 123b is information indicating the name of the project. The mission 123c is information indicating the role that the project should play. The type 123d is information indicating the characteristics of the project, and is a character string such as “product development”, “prototype”, “exhibition demo”, for example.

  The details 123e are information indicating specifications and functions required in the project. The scale 123f is information indicating the scale of the project. The operating environment 123g is information indicating the operating environment of software related to the project. The related project identifier 123h is identification information for specifying another related project when there is another project related to the project.

  The order receipt flag 123i is information for identifying whether or not an order has been received for the project. The related prototype 123j is identification information for specifying a prototype belonging to a project, and one or a plurality of prototypes are specified by the related prototype 123j.

  The technology 123k is information indicating descriptive information, and is a character string such as “wireless”, for example. The license form 123l is information for specifying a license holding form, and is a character string such as “shared with customer”, “owned only by own company”, or “owned by customer”. The MVP 123m is information indicating whether or not the prototype is presented at the time of estimation and the license is held. The MVP 123m is information indicating on or off, for example.

  The customer identifier 123n is information for identifying a project customer, and corresponds to, for example, the company identifier 1211a of the company information 1211, the group identifier 1212a of the group information 1212, and the person-in-charge identifier 1213a in the person-in-charge information 1213. The registration date 123o is information indicating the registration date and time of the project information 123. Remarks 123p is remark information that is freely input for the project.

  Note that the project information 123 may not include all of the above-described information, or may include other information, like the customer information 121 and the prototype information 122.

  Next, a hardware configuration example of the server device 10 will be described.

  FIG. 6 is a diagram illustrating a hardware configuration example of the server device 10. The server device 10 includes an arithmetic device 141, a memory 142, an external storage device 143, an input device 144, an output device 145, a communication device 146, and a storage medium drive device 147, and each component is connected by a bus.

  The arithmetic device 141 is a central arithmetic device such as a CPU (Central Processing Unit), and executes processing according to a program recorded in the memory 142 or the external storage device 143. Each processing unit constituting the control unit 110 realizes each function by the arithmetic device 141 executing a program.

  The memory 142 is a storage device such as a RAM (Random Access Memory) or a flash memory, and functions as a storage area from which programs and data are temporarily read. The external storage device 143 is a writable and readable storage medium such as an HDD (Hard Disk Drive).

  The input device 144 is a device that receives an input operation from a user, and is, for example, a touch panel, a keyboard, a mouse, a microphone, or the like. The output device 145 is a device that performs an output process of data stored in the controlled substance information estimation system, and is, for example, a display device such as an LCD (Liquid Crystal Display) or a printer.

  The communication device 146 is a device for connecting the server device 10 to the network 30 and is a communication device such as a LAN (Local Area Network) card. The communication unit 130 can use the communication device 146. The storage medium driving device 147 is a device that inputs and outputs information from a portable medium 148 such as a CD (Compact Disk) or a DVD (Digital Versatile Disk).

  The function of the storage unit 120 is realized by the memory 142 or the external storage device 143. The function of the storage unit 120 may be realized by a storage device on the network 30.

  As described above, the processing of each component of the server apparatus 10 may be executed by one hardware or a plurality of hardware. The processing of each component of the server device 10 may be realized by one program or a plurality of programs.

  The hardware of the terminal device 20 has the same hardware configuration as that of the server device 10. Therefore, the description of the hardware configuration of the terminal device 20 is omitted.

  FIG. 7 is a flowchart illustrating an example of the prototype information generation process. For example, when the server apparatus 10 receives an input of a display instruction for a project registration screen described later, this process is started. Prior to this processing, information related to the customer is registered in the customer information 121 in advance.

  First, the display information generation unit 114 displays a project registration screen (step S11). The display information generation unit 114 generates display information for displaying the project registration screen, and the communication unit 130 transmits the display information to the terminal device 20. In the terminal device 20, a project registration screen is displayed based on the generated display information.

  FIG. 11 is a diagram illustrating an example of the project registration screen 210. The project registration screen 210 includes areas for inputting a project name, mission, type, scale, license presence, information for identifying a customer, related projects, project identifiers, details, attached files, operating environment, and remarks. It is. Note that the input items described above are merely examples, and items other than information for specifying a customer may not necessarily be included, and other input items may be included.

  In the display of the customer information input area, the display information generation unit 114 refers to the customer information 121 and displays the name 1211b of the company information 1211, the name 1212b of the group information 1212, and the name 1213b of the person-in-charge information 1213 in a selectable manner. . In the display of the related project input area, the display information generation unit 114 refers to the project information 123 and displays the name 123b in a selectable manner. The control unit 110 receives input of information on the project registration screen 210. The customer information input area and the project information input area may be displayed so that a character string can be freely input.

  Returning to FIG. Next, the prototype registration unit 115 generates project information 123 (step S12). The prototype registration unit 115 newly assigns a project identifier 123a to the project information 123, and registers the project with the generated project identifier 123a. The information input on the screen 210 is associated and stored in the storage unit 120. Note that if the project identifier input on the project registration screen 210 already exists in the project identifier 123a of the project information 123, the prototype registration unit 115 does not generate the project identifier 123a and inputs it to the project registration screen 210. The associated information is associated with the corresponding project identifier 123a.

  Next, the prototype registration unit 115 searches for a prototype (step S13). This process will be described with reference to the flowchart shown in FIG.

  FIG. 8 is a flowchart illustrating an example of a prototype search process. This process explains the process performed in step S13 of the flowchart shown in FIG. 7 in more detail.

  First, the search condition extraction unit 111 extracts a character string serving as a search condition from input information (step S131). The search condition extraction unit 111 divides information input to the project registration screen 210 into words using a lexical analysis technique. The search condition extraction unit 111 extracts character strings constituting the divided words as search conditions. The search condition extracted here may be a character string indicating a customer's preference such as “blue screen” or a character string indicating the performance or operating environment of software such as “Windows 8”. Good.

  Next, the prototype extraction unit 112 extracts a candidate prototype including the extracted character string (step S134). The prototype extraction unit 112 specifies one of the search conditions that are one or more character strings extracted in step S131. The prototype extraction unit 112 refers to the customer information 121, the prototype information 122, and the project information 123 using the specified search condition, and extracts a record including the search condition. The prototype extraction unit 112 temporarily stores the identifier of the record including the search condition and the column.

  Here, based on the customer information 121 including the search condition, the prototype information 122, and the project information 123, the prototype information 122 related to the search condition is extracted as a candidate prototype. Therefore, when the record including the search condition is a record in the customer information 121, the prototype extracting unit 112 refers to the project information 123 using an identifier that identifies the customer information 121 including the search condition. The prototype extraction unit 112 specifies a record of the project information 123 including the identifier as the customer identifier 123n. The prototype extraction unit 112 extracts the related prototype 123j of the record of the identified project information 123 as a prototype related to the search condition.

  When the record including the search condition is the project information 123, the prototype extracting unit 112 extracts the related prototype identifier 123j of the record of the project information 123 including the search condition as a prototype related to the search condition. The prototype extraction unit 112 performs the above processing on all of the one or more character strings extracted in step S134.

  As a result, the prototype identifier 122a of one or a plurality of prototype information 122 including a character string as a search condition and the information identifying the identifier and column of the record including the character string are temporarily stored in an area (not shown) of the storage unit 120. Memorized.

  Next, the index calculation unit 113 selects one of the prototypes extracted in step S134 (step S135).

  Next, the index calculation unit 113 extracts another prototype that is higher in the reference relationship than the prototype selected in step S135 (step S136). Specifically, the index calculation unit 113 identifies the reference repository path 122k of the prototype information 122 related to the selected prototype, and the prototype identifier 122a of the other prototype information 122 having the reference repository path 122k as the registered repository path 122j. Are extracted as other prototypes that are higher in the reference relationship. If there is information indicating the path in the reference repository path 122k of the other prototype, the prototype identifier 122a of the other prototype information 122 having the reference repository path 122k as the registered repository path 122j is set in the higher order in the reference relationship. Extract as a prototype. The index calculation unit 113 repeats this process until there is no information indicating the path in the reference repository path 122k.

  Next, the index calculation unit 113 adds the total prototype asset points to calculate the cumulative asset points (step S137). The index calculation unit 113 sums the asset points 122h of the prototype information 122 selected in step S135 and the asset points 122h related to one or more other prototypes extracted in step S136, and calculates the cumulative asset points. .

  Next, the index calculation unit 113 specifies whether or not the total prototype has been successfully received (Step S138). The index calculation unit 113 identifies the project information 123 including the prototype identifier of the prototype as the related prototype 123j for the prototype selected in step S135 and one or more other prototypes extracted in step S136. The index calculation unit 113 uses the order receipt flag 123i of the identified project information 123 to identify whether or not the prototype associated with the identified project information 123 has been ordered. As a result, the prototype selected in step S135 and the other prototype extracted in step S136 are associated with information indicating whether the order has been accepted or not.

  Next, the index calculation unit 113 calculates an order receipt rate (step S139). The order rate is obtained, for example, by calculating (number of received prototypes / total number of prototypes × 100). In step S138, the index calculation unit 113 adds 1 which is the number of prototypes selected in step S135, to the number of prototypes associated with the information indicating that the order has been received, to the number of other prototypes extracted in step S136. Then, the order rate of the prototype selected in step S135 is calculated by dividing by the total number of prototypes and multiplying by 100.

  Next, the index calculation unit 113 determines whether all the prototypes extracted in step S134 have been selected in step S135 (step S140). When the index calculation unit 113 determines that all the extracted prototypes have not been selected (“NO” in step S140), the index calculation unit 113 selects one of the prototypes that have not yet been selected ( Step S141). After that, the index calculation unit 113 executes the processing after step S136.

  When the index calculation unit 113 determines that all of the prototypes extracted in step S134 have been selected (step S140), the control unit 110 advances the process to step S14.

  Returning to FIG. Next, the display information generation unit 114 determines whether there is a search result (step S14). The display information generation unit 114 determines that there is a search result when the prototype extraction unit 112 extracts a prototype in step S134. If the display information generation unit 114 does not determine that there is a search result (“NO” in step S14), the control unit 110 advances the process to step S17.

  When the display information generation unit 114 determines that there is a search result (“YES” in step S14), the display information generation unit 114 displays a search result screen described later (step S15). The display information generation unit 114 generates display information indicating a search result screen, which will be described later, and transmits the display information to the terminal device 20 via the communication unit 130. A search result screen is displayed on a display device (not shown) of the terminal device 20.

  FIG. 12 is a diagram illustrating an example of the search result screen 220. A search result display area 221, a registration button 222, a save button 223, and a close button 224 are included. The search result display area 221 is an area for displaying a search result for each candidate prototype, and includes a repository path 220a, details 220b, preferences 220c, trends 220d, asset points 220e, an order rate 220f, and a project identifier. 220g, prototype identifier 220h, and registration 220i.

  The search result screen 220 is an area for displaying a search result for each candidate prototype. The repository path 220a is the registered repository path 122j of the prototype information 122 selected in step S135 and step S141. The details 220b is the total number of search conditions included in the details 123e of the project information 123 having the prototype as the related prototype 123j and included in the customer information 121, prototype information 122, and project information 123 corresponding to the candidate prototype. is there.

  For example, when a character string indicating “video” is extracted as a search condition, a character string indicating “video” is included in the details 123e of the project information 123 corresponding to the candidate prototype in a predetermined candidate prototype. The number of the character strings included is counted in the details 220b. In addition, when the character string of “video” is included in the other columns of the project information 123, the customer information 121 corresponding to the candidate prototype, or the prototype information 122, the number of included character strings is counted in the details 220b. Is done. The number of search conditions shown in the details 123e is displayed in the search result display area 221 so as to be selectable.

  The display information generation unit 114 displays the number of search conditions included in the search result display area 221 based on the information temporarily stored in step S134 described above.

  The preference 220c indicates the number of search conditions included in the preference 1213e of the customer information 121 corresponding to the candidate prototype included in the customer information 121, prototype information 122, and project information 123 corresponding to the candidate prototype. The customer information 121 related to the candidate prototype is customer information 121 specified by the company identifier 1211a, the group identifier 1211b, or the person-in-charge identifier 1211c as the customer identifier 123n of the project information 123 having the candidate prototype as the related prototype 123j. is there. The number of search conditions indicated in the preference 1213e is displayed in a selectable manner.

  The trend 220d indicates the number of search conditions included in the technology 123k of the project information 123 having the prototype as the related prototype 123j and included in the customer information 121, prototype information 122, and project information 123 corresponding to the candidate prototype. Yes. The number of search conditions shown in the trend 220d is displayed in the search result display area 221 so as to be selectable.

  The asset P (point) 220e is a cumulative asset point of the prototype information 122 calculated in step S137. The order rate 220f is the order rate calculated in step S139 for the prototype. The project identifier 220g is the project identifier 123a of the project information 123 with the prototype as the related prototype 123j. The prototype identifier 220h is the prototype identifier 122a of the prototype information 122. The registration 220i is an input field for accepting selection.

  When one of the prototype information 122 displayed in the search result display area 221 is selected as the registration 220i of the prototype information 122 and the registration button 222 is selected, the selected prototype is registered in the prototype information 122 as a new prototype. Is done. Details will be described later. The save button 223 is a button for receiving a search result storage instruction displayed in the search result display area 221. The close button 224 is a button for accepting an instruction to end display of the search result screen 220.

  When the number of search conditions included in any of the details 220b, the preferences 220c, or the trends 220d is selected, a display screen is displayed on the search result detail screen 230, which is a screen showing details regarding the search conditions extracted by the selected number. Transition. FIG. 13 shows a search result detail screen 230 when “5” shown in the record preference 220c shown in the top row is selected in the search result display area 221 of the search display screen shown in FIG.

  FIG. 13 is a diagram illustrating an example of the search result detail screen 230. The search result detail screen 230 includes a detailed information display area 231. The detailed information display area 231 displays an attribute 231b, an information name 231c, and a hit count 231d in association with a keyword 231a that is a character string indicating a search condition.

  The keyword 231a is a character string indicating the search condition extracted by the number selected in the search result display area 221. The attribute 231b is information for specifying a column in which the extracted search condition is included. The information name 231c is information indicating an information name including a record having the extracted search condition. The hit number 231d is information indicating the number of search conditions included.

  In the search result detail screen 230 shown in FIG. 13, for the candidate prototype with the identifier “P0001”, the details of the record including “***” of the keyword 231a as the search condition is displayed. “***” of the keyword 231a is “2” with the number of hits 231c in the “preference” of the attribute 231b in the “customer information” of the information name 231c, which is related to the candidate prototype with the identifier “P0001”. It is included. Still, the same search condition includes “1” in each of the “detail” column of the project information 123 corresponding to the candidate prototype, the “mission” column of the project information 123, and the “detail” column of the project information 123. Means that

  In the search result detail screen 230 shown in FIG. 13, “***”, which is one keyword 231a, is displayed as a search result. However, when a plurality of search conditions are included as search results in the details 220b, preferences 220c, or trends 220d related to the number of search conditions selected in FIG. 12, a plurality of keywords 231a are displayed on the search result detail screen 230. The

  Returning to FIG. Next, the prototype registration unit 115 receives a prototype selection (step S16). It is assumed that when one of the registrations 220i in the search result display area 221 is selected and the registration button 222 is selected, the prototype registration unit 115 accepts selection of a prototype.

  Next, the prototype registration unit 115 registers as a new prototype (step S17). The prototype registration unit 115 copies the prototype information 122 selected in step S16, attaches a new prototype identifier 122a, and rewrites the registration repository path 122j to a new prototype storage location. Also, the prototype registration unit 115 rewrites the reference repository path 122k to the registration repository path 122j of the prototype information 122 before copying, and registers it as new prototype information 122. Then, the control part 110 complete | finishes the process of this flowchart.

  When using version management software that performs software version management, as described above, an identifier for specifying a prototype and a storage location may be linked to the present system. In this case, for example, when the prototype registration unit 115 generates a new prototype in step S17, the prototype registration unit 115 includes the prototype identifier 122a, the registration repository path 122j, the reference repository path 122k, and the reference revision 122l regarding the generated prototype. Commands related to registration, update, etc. are output to the version management software. In the version management software, information on the prototype is automatically updated when a command is received.

  In addition, after the prototype information generation process shown in FIG. 7, it is desirable to appropriately rewrite the contents of the prototype information 122 when the conditions relating to the estimate of the customer's request and software specifications are changed.

  In this process, by displaying the search result screen 220, it is possible to present an index indicating the value of software such as an order rate and asset points for each prototype retrieved based on the extracted search condition. In calculating the index, an index is calculated taking into account the orders received of other prototypes that were referenced when the prototype was created. Thereby, it is possible to recognize a prototype with a high order record. In addition, by registering a prototype suitable for the newly created estimate as a new prototype, information in the prototype created in the past can be reflected in the next estimate. Prototypes as accumulated assets can be used effectively.

  In the project registration screen 210, when the input of information indicating that the license is “present” is received, the prototype extraction unit 112 refers to the MVP 123m of the project information 123 and indicates that the license is “present”. A prototype associated with the project information 123 including information and the related prototype 123j is extracted. This makes it possible to extract candidate prototypes only for licensed prototypes.

  In addition to the above-described search conditions, a search condition may be added so that a prototype that has been presented to the customer is extracted as a candidate prototype. In this case, a presentation flag indicating whether or not it has been presented is provided in the prototype information 122. Thereby, prototype information extracted based on more detailed conditions can be used.

  FIG. 9 is a flowchart illustrating an example of the order information registration process. This process is performed in order to register the order information for the project when receiving an order for software creation from the customer based on the presented estimate. When a screen display instruction for registering order information is received, this processing is started.

  First, the control unit 110 receives an input of a project identifier of an ordered project and an order amount or an estimate month (step S21). On the screen (not shown) for registering the order information, information for specifying the project that has been ordered and the order amount or the estimate person month indicating the order record are input. The control unit 110 identifies the project identifier based on the input information, and temporarily stores the order amount or the estimated person month in the storage unit 120.

  The estimate month is information indicating the amount of work that one person predicts to perform in one month. However, the estimate month is not limited to the estimate month as long as the order quantity can be recognized.

  Next, the index calculation unit 113 calculates asset points using the received order results (step S22). For example, the index calculation unit 113 calculates (estimator month and order amount / 1,000,000, whichever is larger) as an asset point.

  Next, the prototype extraction unit 112 extracts a related prototype (step S23). The prototype extracting unit 112 refers to the project information 123 using the project identifier specified in step S21, and extracts one or a plurality of related prototypes 123j related to the project identifier 123a.

  Next, the control unit 110 updates the prototype information 122 and the project information 123 (step S24). Specifically, the control unit 110 changes the order reception flag 123j of the project information 123 corresponding to the project identifier specified in step S21 to information indicating that an order has been received. Further, the control unit 110 refers to the prototype information 122 using the prototype identifier that identifies each of the related prototypes extracted in step S23, and sets the asset point calculated in step S22 for each prototype identifier 122a to the asset point 122h. Associate as. The control unit 110 then ends the process of this flowchart.

  In the present embodiment, the order rate and cumulative asset points are calculated during the prototype search process. However, the calculation timing of these indices is not limited to this. For example, the order rate and cumulative asset points may be calculated together with the calculation of asset points during the order information registration process.

  In the present embodiment, asset points are calculated based on the order amount or information indicating the order amount and used as an index indicating the value of the software. Thus, when a prototype created in the past is presented as a search result, an index indicating the possibility of ordering can be presented together. Since an index is presented for each prototype, the user can select a prototype suitable for the estimate with reference to the index when selecting a prototype to be used for creating an estimate.

(Modification)
Next, a modification of the above embodiment will be described. In the above-described embodiment, the search condition is extracted based on the information input to the project registration screen 210 used at the time of project registration. However, in this modified example, a prototype search screen for receiving the input of the search condition (in detail, Search conditions are extracted based on the input to (to be described later). Hereinafter, differences from the above-described embodiment will be described, and description of overlapping points will be omitted.

  FIG. 10 is a flowchart illustrating an example of a prototype search process according to the modification. This process shows the details of the process performed in step S13 shown in FIG. In this modification, when a display instruction for a prototype search screen is received, the processing of this flowchart is started. Therefore, step S11 and step S12 shown in FIG. 7 are omitted.

  First, the display information generation unit 114 displays the prototype search screen 240 (step S132). Specifically, the display information generation unit 114 generates display information for displaying a prototype search screen 240 described later, and transmits the display information to the terminal device 20 via the communication unit 130. In the terminal device 20, a prototype search screen 240 is displayed based on the display information.

  FIG. 14 is a diagram illustrating an example of the prototype search screen 240. In the prototype search screen 240, an input area is associated with each item. The item is, for example, a keyword, type, scale, presence / absence of license, information for identifying a customer, registration date, etc., but is not limited thereto.

  Returning to FIG. Next, the search condition extraction unit 111 extracts a character string that serves as a search condition (step S133). The search condition extraction unit 111 divides information input to the prototype search screen 240 into words using a lexical analysis technique, and extracts a character string constituting the divided word as a search condition.

  Thereafter, the processing performed after step S134 is the same as the processing performed after step S134 in the flowchart shown in FIG.

  In this modification, not only the timing of project registration but also a prototype can be searched at any time.

  As mentioned above, although each embodiment and modification which concern on this invention have been demonstrated, this invention is not limited to an example of above-described embodiment, Various modifications are included. For example, the above-described exemplary embodiment has been described in detail for easy understanding of the present invention, and the present invention is not limited to the one having all the configurations described here. A part of the configuration of an example of an embodiment can be replaced with the configuration of another example. Moreover, it is also possible to add the structure of another example to the structure of an example of a certain embodiment. In addition, for a part of the configuration of an example of each embodiment, another configuration can be added, deleted, or replaced. Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. In addition, the control lines and information lines in the figure indicate what is considered necessary for the description, and do not necessarily indicate all of them. It can be considered that almost all configurations are connected to each other.

  In addition, the functional configuration of the server device 10 is classified according to main processing contents in order to facilitate understanding. The present invention is not limited by the way of classification and names of the constituent elements. The configuration of the server device 10 can be classified into more components depending on the processing content. Moreover, it can also classify | categorize so that one component may perform more processes.

  1: asset management system, 10: server device, 20: terminal device, 30: network, 110; control unit, 111: search condition extraction unit, 112: prototype extraction unit, 113: index calculation unit, 114: display information generation unit 115: Prototype registration unit, 120: Storage unit, 121: Customer information, 122: Prototype information, 123: Project information, 130: Communication unit, 141: Computing device, 142: Memory, 143: External storage device, 144: Input Device, 145: output device, 146: communication device, 147: storage medium drive device, 148: media, 210: project registration screen, 220: search result screen, 221: search result display area, 222: registration button, 223: save Button, 224: close button, 230: search result detail screen, 231: detailed information display area, 40: prototype search screen

Claims (8)

A storage unit that associates and stores identification information for identifying the software used for the estimate , and an order record of the software ;
An index calculation unit that calculates an index indicating the value of the software using the order record;
A software extraction unit that refers to the storage unit using a search condition relating to a new estimate and extracts candidate software that is a candidate for use in the new estimate;
Display information of a search result screen that displays the candidate software and the index of the candidate software calculated by the index calculation unit in association with each other, and receives selection of software used in the new estimate from the candidate software. A display information generation unit to generate,
A software registration unit that registers the software selected from the candidate software with a new identification number and registers it in the storage unit as software used for the estimation;
An asset management device comprising: The asset management device according to claim 1,
In the storage unit, the identification information for identifying the software used for the estimation is associated with the identification information of the software at the reference destination that is the software used for the estimation of the software ,
The index calculating unit uses the received orders before Symbol referenced software that are higher in the reference relationship, asset management device and calculates the index of the candidate software. The asset management device according to claim 2,
In the storage unit, asset points calculated by the index calculation unit using information indicating an order amount or an order amount are stored as the order results,
The index calculation unit, wherein associated with the identification information before Symbol referenced software using the asset point, asset management device and calculates the asset point of the candidate software as the index. The asset management device according to claim 2 or 3,
In the storage unit, order information indicating whether or not the software has been ordered is stored as the order record,
The index calculation unit calculates an order rate of the candidate software as the index using the number of the software of the reference destination that is higher in the reference relationship, related to the order information indicating that the order has been received. Asset management device. The asset management device according to any one of claims 1 to 4 ,
A search condition extraction unit that extracts a character string as the search condition from the input information input to the new estimate registration screen for registering the new estimate;
The asset management apparatus, wherein the display information generation unit generates the display information indicating the number of the character strings included in the software extracted by the software extraction unit. The asset management device according to any one of claims 1 to 5 ,
The storage unit stores license information indicating whether the software has a license,
The asset extraction apparatus, wherein the software extraction unit extracts the software having the license. An index calculation procedure for calculating an index indicating the value of the software using the actual order received of the software used for the estimate;
Candidate software that is a candidate for use in the new estimate by referring to a storage unit that stores the identification information for identifying the software used in the estimate and the received order of the software in association with the search condition for the new estimate. Software extraction procedure to extract,
Display information of a search result screen that displays the candidate software and the index of the candidate software calculated in the index calculation procedure in association with each other and accepts selection of software used in the new estimate from the candidate software Display information generation procedure for generating
A software registration procedure for registering in the storage unit as software used for the estimation by attaching a new identification number to the software selected from the candidate software;
The asset management method characterized by performing. A program for causing a computer to function as an asset management device,
An index calculation procedure for calculating an index indicating the value of the software using the actual order received of the software used for the estimate;
Candidate software that is a candidate for use in the new estimate by referring to a storage unit that stores the identification information for identifying the software used in the estimate and the received order of the software in association with the search condition for the new estimate. Software extraction procedure to extract,
Display information of a search result screen that displays the candidate software and the index of the candidate software calculated in the index calculation procedure in association with each other and accepts selection of software used in the new estimate from the candidate software Display information generation procedure for generating
A software registration procedure for registering in the storage unit as software used for the estimation by attaching a new identification number to the software selected from the candidate software;
That causes the computer to execute the program.

Images