JP2006209793A - Software management method and software management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a software management system which improves productivity and advantage of budgetary management for consumers in outsourcing software management and maintenance. <P>SOLUTION: A software management method is employed to estimate more than one tasks concerning software requested by customers using computers. The method includes a step S502, S503 and S505. The method includes steps of: S502 receiving task schedule information and expected task amount information per task; S503 calculating total expected task amount per pre-determined term according to the received task schedule information and expected task amount information; and S505 indicating the total expected task amount per pre-determined term. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a software management system, and more particularly to a software management system for executing software maintenance, operation, development, and the like.

  There is an outsourcing business that receives requests from customers for maintenance, operation, development, etc. of application software, etc., and requests work from an external software house. The person who does this business is called an outsourcer.

  Generally, customers who are end users in this outsourcing business are considered to have the following needs. The first need is to flexibly deal with correction of small-sized application software, specification changes, and troubleshooting. The second need is to keep the cost within the range determined by the budget. The third need is to sequentially know the response status of small-availability deals.

  On the other hand, it is generally considered that an outsourcer outsourcing outsourcing has the following needs. The first need is to avoid sticking workers for each customer in order to improve productivity by reusing worker knowledge for other projects. The second need is to clarify the relationship between the response status and the budget between the customer and the response regarding the small number of cases. The third need is to increase the number of customers and to concentrate the work implementation system and implementation know-how for small projects. The fourth need, especially in the case of application software, is that there is a limited number of people who can be entrusted with maintenance and development because the business know-how is gathered. It is the point that we want to organize and deal with the company that maintained and developed the application software of the customer who was, and also the employees who were absent from the company.

  And as an outsource destination, it is thought that it has the following needs. The first need is that in the case of small-lot development, it is desirable to proceed with work while concurrently carrying out other work at the company or at home. The second need is to secure stable income by doing business related to software maintenance.

  The present invention has been proposed in view of the needs in the software outsourcing business as described above. Next, the problems directly caused in proposing the present invention will be further described.

  As described above, one of the needs of those who request outsourcing is the need to keep costs within the range determined by the budget. Conventionally, such needs have been estimated individually for each case. For example, it is considered that the customer budget cannot be fixed every month and budget management is difficult. A conventional estimation method is shown in FIG. Conventionally, the work period and the total work amount are estimated for each case (step S901). Therefore, the implementation system has fluctuated due to the estimation (step S902). Furthermore, the acceptance was performed only with the deliverable after the work was performed (step S903).

  On the other hand, when performing maintenance / management of software such as application software, it has been common for an operator to work by sticking to a customer. However, this method has a limitation in improving productivity by reusing the worker's knowledge for other projects because the worker is dedicated to one customer. In particular, software houses in remote locations must be excluded from the contractors, assuming that the work of the customer is a premise, not only because the software house cannot accept work and suffer losses, but also to customers and outsourcers. The opportunity to receive a very good service was lost.

  As described above, in the past, in outsourcing work such as software maintenance and operation in particular, there is a problem in budget management for customers, there is a limit in improving productivity, and further, remote software houses There was a problem that the utilization of was insufficient.

  Accordingly, an object of the present invention is to provide a software management method and system for improving the convenience of budget management for customers and improving productivity, particularly in outsourcing operations such as software maintenance and operation. It is.

  The software management method according to the first aspect of the present invention relates to software-related work, and is a software management method for estimating work by a computer in response to a request for a plurality of cases from a customer. And a step of receiving work schedule information (for example, step S502 in FIG. 5) and a step of calculating a total predicted work amount for each predetermined period based on the received predicted work volume information and work schedule information (for example, FIG. 5 (step S503) and a step (for example, step S505 in FIG. 5) for displaying the total expected work amount for each predetermined period. With such a configuration, it is possible to grasp the total expected work amount for each predetermined period. For example, when performing work at a fixed fee for each predetermined period, the work amount can be easily adjusted. Can be executed.

  Furthermore, in the above-described software management method, a step of adjusting the work schedule so that the calculated total predicted work amount for each predetermined period falls within the predetermined work amount range (for example, step S504 in FIG. 5). And S505) may be provided. Thereby, for example, a fixed fee is set for each predetermined period, and the work schedule can be automatically adjusted when it is necessary to keep the work amount in the predetermined period within a predetermined range. .

  Another software management method according to the present invention relates to software-related work, and is a software management method by a computer that outsources work to an outsource destination in response to a matter request from a customer. The step of receiving the transmitted development asset lending request (for example, step S803 in FIG. 8), and the development asset in a state where only the outsource destination that has transmitted the request can access the development asset. For example (step S806 in FIG. 8). As a result, for example, the development asset can be used even when the outsourced software house or the like is in a remote location, and development efficiency can be improved.

  A software management system according to a second aspect of the present invention is a software management system that outsources work to an outsource destination in response to a request for a case from a customer regarding work related to software. Development asset storage means (for example, the library original 112 in FIG. 7) and access storage means (for example, the reception / issuance folder in FIG. 7) assigned to each outsource destination and accessible only to the outsource destination 111), and stores the development asset stored in the development asset storage means in the access storage means when the development asset lending request transmitted from the outsource destination is received. As a result, for example, the development asset can be used even when the outsourced software house or the like is in a remote location, and development efficiency can be improved.

  Further, when a software program reflecting work from an outsource destination is received, it is desirable to store the software program in the access storage means.

  According to the present invention, it is possible to provide a software management system that improves the convenience of budget management for a customer and improves productivity when outsourcing software maintenance and management.

  FIG. 1 is a configuration diagram showing an outline of a software management system according to the present embodiment. The software management system 1 includes an item management server 10, an asset management server 11, a test machine 12, and a database 13, and is connected to a software house terminal 2 and a customer terminal 3 via a communication network 4. In addition, the software management system 1 is operated by an outsourcer that receives a request for development, maintenance, operation, and the like related to software from a customer and requests work from a software house or the like. Here, the software house indicates an example of an entity that can execute development, maintenance, operation, etc. regarding software in response to a request from an outsourcer, that is, an outsource destination, and includes not only a corporation but also an individual.

  The case management server 10 includes a registrant information processing unit 101, a case management unit 102, and an estimation processing unit 103, and is connected to the asset management server 11, the test machine 12, and the database 13.

  In order to use this software management system 1, a predetermined registration procedure is required. The registrant information processing unit 101 has a function of executing processing related to registration of customers and software houses. A customer or a software house inputs information to be registered using the terminals 2 and 3. The input registration information is stored in the registrant information storage unit 131 by the registrant information processing unit 101 of the case management server 10. When a predetermined registration procedure is completed, a user ID and a password are allocated to each customer, software house, and the like. When a customer or software house uses this software management system, it is necessary to log in by inputting these user ID and password.

  The case management unit 102 has functions such as bidding for a case and processing information regarding the work status of the case. The function will be described in detail later. The estimation processing unit 103 has a function of executing an estimate for each case and for each month based on the request information, for example, based on a monthly work amount. The function will be described in detail later.

  The asset management server 11 includes storage means for storing various program libraries, and functions such as granting a right to use a specific library under certain requirements when the software house performs tasks such as development, maintenance, and operation. It has.

  The test machine 12 is a test machine that executes tests on software programs developed, maintained, and operated by the software house 2. The test machine 12 can be used by a software house that is an outsource destination, or can be used by the outsourcer itself.

  The database 13 includes a registrant information storage unit 131, a case information storage unit 132, and an estimate information storage unit 133. In the registrant information storage unit 131, the registrant information processing unit 101 stores information on the registrant of the software management system 1. The item information storage unit 132 stores information about each item such as the work contents of the item, bid information, and work status information for each item. The estimated information storage unit 133 stores information estimated by the estimated information processing unit 103.

  In the software management system 1 shown in FIG. 1, the terminal 201 of the software house A, the terminal 202 of the software house B, and the terminal 203 of the software house C are illustrated as the terminals 2 of the software house. The terminal 2 is, for example, a computer that can execute development, maintenance, operation, and the like of a software program, and has a communication function that can connect to the system 1 via at least the communication network 4 and perform communication. Yes.

  The customer terminal 3 is, for example, a personal computer (PC), and is provided with a communication function capable of connecting to the system 1 via at least the communication network 4 and performing communication.

  The communication network 4 refers to a communication network such as the Internet, a public network, a dedicated line, etc., and includes both wired communication and wireless communication, and serves as a transmission medium when exchanging information.

Next, the estimation process in the present invention will be described with reference to FIG.
The estimation process according to the present invention is particularly characterized in that the amount of work for a predetermined period is fixed and the fee for the work is also fixed. In the following example, a month is used as the predetermined period, but the present invention is not limited to this, and the length of the period is not limited, such as a unit of 10 days, a unit of 2 months, a unit of 3 months, a unit of 6 months, or a unit of 1 year.

  First, the outsourcer communicates with the customer via the communication network 4 or directly to determine the amount of work for each month, and also determines the fee as the price. Then, the outsourcer inputs a monthly work amount to the estimation processing unit 103 using a keyboard or the like (step S201). Next, the outsourcer estimates the amount of work for each case such as maintenance and operation of application software, and inputs the value to the estimation processing unit 103 using a keyboard or the like (step S202). The estimation processing unit 103 stores the fixed work amount and the fixed fee input in step S201 and the work amount for each case input in step S202 in the estimated information storage unit 133 of the database 13.

  Subsequently, the estimation processing unit 103 reads information on the work amount for each case from the estimate information storage unit 133, calculates the cumulative work amount of the total case for each month, and displays the total work amount on the display.

  A display example of the display is shown in FIG. In FIG. 3, the cumulative work amount of the total projects for each month is shown in a table format. This table includes information on the work amount (person / day), work schedule, work assignment, and monthly work amount for the three projects X, Y, and Z, respectively. Among these, the outsourcer inputs information on the case name, the work amount, and the work schedule, and based on the input information, the estimation processing unit 16 calculates and outputs information on the work assignment and the monthly work amount. Furthermore, it is possible to provide a person-in-charge column for each case. Further, the amount of work may be the number of steps to be corrected instead of the display in units of people and days.

In this example, the project X has a work amount of 12 (person / day), and the work is performed from July 10 to July 20. The case Y has a work amount of 10 (person / day), and the work is performed from July 22 to August 10. The project Z has a work amount of 20 (person / day), and the work is performed from August 2 to September 10. Regarding the work allocation, since the work X is performed only in July, the work amount 10 is displayed as it is as the work amount 10 (person / day) is generated in July. In the case Y, the work is performed over July and August, so the work amount is prorated according to the number of work days of each month, and the work amount of each month is calculated and displayed. In the case Y, the total work amount is 10 (person / day), the work days for July are 10 days, and the work days for August are 10 days.
Work volume for July = 10 (person / day) x 10 (day) / 20 (day) = 5 (person / day)
Work amount for August = 10 (person / day) × 10 (day) / 20 (day) = 5 (person / day)
These work volumes are shown in parentheses in the work assignment column.

Further, since the case Z is performed over August and September, the amount of work for each month is calculated and displayed in the same manner as the case Y. In the case Z, the total work amount is 16 (person / day), the work days for August are 30 days, and the work days for September are 10 days, so each work amount is as follows.
Work amount for August = 16 (person / day) × 30 (day) / 40 (day) = 12 (person / day)
Work amount for September = 16 (person / day) × 10 (day) / 40 (day) = 4 (person / day)
These work volumes are shown in parentheses in the work assignment column.

The monthly work amount based on these three cases is obtained as follows by calculating the sum of the monthly work amount of each case.
Monthly work volume in July = 12 (person / day) + 5 (person / day) = 17 (person / day)
Monthly work volume in August = 5 (person / day) + 12 (person / day) = 17 (person / day)
Monthly work volume for September = 4 (person / day)

  In this example, since the work amount determined between the customer and the outsourcer is 18 (person / day), the monthly work amount is within the range, so the work amount is not adjusted. On the other hand, in this example, when the work amount determined between the customer and the outsourcer is 15 (person / day), it is necessary to adjust the work amount.

  An example in which the amount of work is adjusted is shown in FIG. This is an example when the work amount determined between the customer and the outsourcer is 15 (person / day), and the work amounts of the case X, the case Y, and the case Z are the same as the example shown in FIG. Project X will be operated from July 10th to July 20th. With respect to the case Y, in the example shown in FIG. 3, since the work amount for July was 5 (person / day), the work amount for July in the total of case X and case Y was 17 (person / day). ) Therefore, the work amount for July in Project Y needs to be 3 (person / day) or less. Therefore, in this example, the work schedule for the project Y, which was from July 22 to August 10, is changed from July 29 to August 7. As a result, the total work amount for July is 15 (person / day), which is within the work amount range determined between the customer and the outsourcer. By setting the case Y in this way, the work amount of the case Y for August is 7 (person / day). Therefore, it is necessary to change the work schedule for Item Z. In other words, in order to keep the fixed work amount within the range of 15 (person / day), 15 (person / day) -7 (person / day) = 8 (person / day) or less is less than August for Project Z The amount of work may be used. In order to set 8 (person / day) as the work amount of the project Z, for example, for the project Z, the work schedule may be set from August 12 to September 20.

  The inspection work is performed based on the monthly work amount (step S205). The commissioned software house will submit a work report at the end of the month, and acceptance will be performed based on this work report.

  As described above, the example in which the estimation processing unit 12 of the server 1 is used in order to keep the monthly work amount within the range of the predetermined monthly work amount has been described. In this example, the estimation processing unit 12 has a function of calculating and displaying the monthly work amount in response to the input of the work amount and the work schedule. However, the work schedule is automatically set as follows. It is good also as having a schedule function which adjusts.

  FIG. 5 is a flowchart showing a schedule function for automatically adjusting the work schedule. First, the outsourcer that performs the estimation inputs the monthly work amount agreed upon after discussion with the customer (step S501). Next, the work amount and work schedule for each item are input (step S502). A monthly work amount is calculated based on the input work amount information and work schedule information (step S503). Then, it is determined whether the calculated monthly work amount is equal to or less than the monthly work amount input in step S501 (step S504). If it is determined that the amount is larger than the monthly work amount, the work schedule is corrected (step S505). In the modification of the work schedule, the work schedule is shifted later for a specific matter so that the amount of work for the month is reduced as in the above example. Then, the work amount for each month is calculated again (step S503), and it is determined whether it is equal to or less than the monthly work amount input in step S501 (step S504). Such steps are repeated until the monthly work amount becomes equal to or less than the monthly work amount input in step S501. If the monthly work amount is equal to or less than the monthly work amount input in step S501, the result is displayed on the display or printed (step S505).

  In the middle of the month, if the amount of work becomes the planned amount of work, even if it is in the middle of the work, the work corresponding to the fixed monthly fee is taken as one month worth of work. Work that exceeds the planned work volume is treated as a separate contract.

  In the example shown in FIG. 3 and FIG. 4 described above, the work amount and work schedule are set for each project. However, the work is further divided into processes such as design, development, test, etc. A work schedule may be set. In the above example, the monthly work amount is modified so that it falls within the predetermined work amount range. However, in consideration of information such as the work status of the person in charge of each work. You may make it add correction. For example, when work concentrates on one person in charge over a predetermined amount, the work schedule is corrected. Furthermore, a priority order may be assigned to each item, and the schedule may be adjusted in consideration of this priority order. For example, a modification is made such that a work schedule is preferentially set up for high priority matters.

  Next, the bidding method for the case will be described. FIG. 6 is a flowchart for explaining a bid method for a case. First, the contents and the bidding method are posted from the outsourcer to each software house (step S601). The posting is performed as follows. First, the outsourcer inputs the contents of the project and the bidding method using a keyboard or the like. The entered case contents and bid method information are stored in the case information storage unit 132 of the database 13 by the case management unit 102. When the outsource instructs the server 10 to notify each software house 2 of the matter content and the bid method, the matter management unit 102 stores information on the matter content and the bid method stored in the matter information storage unit 132. Is transmitted to each software house 2 via the communication network 4. Transmission can also be performed by e-mail, and can also be performed by posting the contents of the case and the bidding method on a web (WEB) page. This case content includes the work content of the case. In addition, the bidding method includes a bidding period, an announcement method of a successful bidder, and the like.

  The software house, which has received the e-mail or browsed the web page, has acquired information on the project contents, uses the terminal 2 to determine the period and price estimate, and communicates according to the bidding method. The data is transmitted to the outsourcer matter management server 10 via the network 4 (step S602). In the case management server 10, the case management unit 102 receives the transmitted period and price estimation information and stores it in the estimation information storage unit 133. Further, the period and price estimate information stored in the estimate information storage unit 133 can be displayed on a screen (not shown) of the server 2 in accordance with an instruction from the outsourcer together with the bidder name. The display may be appropriately sorted in ascending order of price or in order of shorter period until bidding. After the end of the bidding period, the outsourcer examines the estimation information transmitted from each software house and determines the winning bidder, that is, the outsource destination (step S603).

  Further, the outsourcer notifies the determined successful bidder of the result and provides a program and a test environment (step S604). Specifically, the outsourcer is selected from the list of estimated information displayed on the screen by clicking on specific estimated information using the mouse or keyboard or checking the check box, and clicking the notification button. To notify the successful bidder of the result. The notification is performed by e-mail or the like. At the same time, a notification that the bidder other than the winning bidder was not selected as the winning bidder for the current case is transmitted.

  Next, the provision of a program environment and a test environment will be described in more detail. FIG. 7 is a configuration diagram specifically showing the configuration of the asset management server 11, the test machine 12, and the software house terminal 2 in the software management system 1 shown in FIG. In the figure, the asset management server 11 shows a reception / issuance folder 111 and a library original 112 as a configuration related to the provision of the program environment. The reception / issuance folder 111 is a folder that can be accessed only by the delegated software house, and the folder that can be accessed by each software house is different. Basically, the access right for each folder is managed by the case management unit 102, and only the software house permitted by the case management unit 102 can access the folder.

  This point will be specifically described. When a software house uses this system, as described above, it is necessary to input a user ID and a password. By providing a table in which the system associates information such as user IDs with specific folders in advance, the software house enters a user ID and password to use the system, and when the software house is logged in, , Allowing access to pre-associated folders.

  As another method, a password for accessing each folder may be generated separately from a password for logging in to the system, and this password may be given to the software house given an access right. In this case, it is possible to directly access the library original instead of each folder.

  The library original 112 includes, for example, a design document and a source program. Design documents and source programs used for maintenance, operation, etc. in a software house, and are stored for a certain period in a project folder assigned to the software house in response to a request from the software house. The software house can read this design document and use it for maintenance and operation work.

  The test machine 12 shows a test library 121 such as a design document and a source program, and a test library 122 that is an execution module obtained by compiling the test library 121.

  The software house terminal 2 shows a case management client 21 and a development client 22. The development client 22 shows a development library 221 such as a design document and a source program, a development library 222 that is an execution module obtained by compiling the development library, and a reference library 223 such as a design document and a source program. ing.

  Next, a processing flow relating to provision of a program environment and a test environment will be described using the flowchart shown in FIG. First, the case management server 10 of the software management system 1 transmits the case escalation to the software house, that is, the customer's requirements regarding the case, etc., to the software house (step S801). Specifically, the case management server Information about the case is transmitted from the ten case management units 102 to the terminal 2 of the software house via the communication network 4 by e-mail or the like. The software house confirms the received item information and identifies the target asset (step S802).

  The software house transmits a request for lending the identified target case to the asset management server 11 via the communication network 4 (step S803). The asset management server 11 receives the request and requests the matter management server 10 to confirm the matter (step S804). The matter management server 10 performs matter confirmation in the matter management unit 102 based on the matter information stored in the matter information storage unit 132. When the matter management unit 102 determines that the request is an appropriate request as a result of the confirmation of the matter, the matter management unit 102 notifies the asset management server 11 to that effect. The asset management server 11 receives the notification and makes a request for lending the requested target asset. In accordance with the request, the asset management server 11 reads the target asset from the library actual book 112 (step S805). Then, the target asset is paid out to the reception / issue folder 111 that can be accessed by the software house (step S806). In addition, the reference asset is paid out together with the payout of the target asset. For example, when the work is a modification of only a part of the program of the entire system, the reference asset corresponds to the other program. This is because it is necessary to grasp the contents of other programs in order to perform the correction work. However, the reference asset can only be read and cannot be rewritten. Simultaneously with the payout, the asset management server 11 notifies the software house terminal 2 of the lending via the communication network 4 (step S807).

  The case management client 21 of the software house terminal 2 receives the lending notice. Then, in response to an instruction from the software house or automatically according to the notification, a file related to the target asset and a file related to the reference asset are acquired from a predetermined area of the reception / issuance folder of the asset management server 11. Specifically, a file acquisition request regarding the target asset or the like is transmitted from the software house terminal 2 to the asset management server 11 via the communication network 4. The asset management server 11 reads the file from the predetermined area and transmits it to the software house terminal 2 via the communication network 4.

  The software house terminal 2 receives the file (step S808), and executes program development, maintenance, operation, and the like based on the received file related to the target asset and file related to the reference asset. Hereinafter, a case where a program correction operation is executed will be described. First, an execution module is generated by compiling the received target asset development library 221. Then, the program is modified using this execution module (step S809). When modifying the program, files related to reference assets are also used as appropriate. When completing the program modification work, the software house transmits the modified program to the asset management server 11 via the communication network 4 using its own terminal 2 (step S810). The corrected program is written in the reception / issuance folder 111. After this writing is executed, the software house cannot access the acceptance / issuance folder 111 for this matter. In addition, the software house transmits a correction completion notification to the case management server 10 (step S811).

  In the case management server 10, the case management unit 102 receives the correction completion notification and stores information to that effect in the case information storage unit 132. Then, the case management unit 102 performs management approval regarding the modification of the program (step S812). If the approval is obtained, the asset management server 11 updates the library original stored in the library original 112 with the modified program (step S813).

  Next, a test relating to the modified program is executed using the test machine 12 (step S814). The test is executed by obtaining the test library 122 from the library original 112 and compiling it into an execution module. The test may be performed by the modified software house or by the outsourcer itself. Furthermore, a software house other than the software house that has made corrections may be executed. After the test work is completed, the software house is released from the access right to the test machine 12 and cannot be used. The assets for which the test has been completed are transmitted to the customer terminal 3 via the communication network 4 (step S815).

  Unlike the above-described example, a necessary library may be attached to an electronic mail and transmitted to a software house, and a modified program may be attached to an electronic mail and transmitted to the system side.

  Next, the report of the work status of the project to the customer will be described. In the software management system according to the present invention, the software house entrusted with the work related to the case summarizes and reports to the outsourcer at the end of the month how much the work related to the case is completed. Therefore, the case management unit 102 of the case management server 10 submits the end-of-month report via the communication network 4 by e-mail or the like to a software house entrusted with work at a predetermined time near the end of the month. Make the notification you want. The software house that has received this notification uses the terminal 2 to transmit the end-of-month report to the case management server 10 via the communication network 4. The case management unit 102 of the case management server 10 receives the end-of-month report, extracts necessary information, and stores it in the case information storage unit 132. Further, the case management unit 102 reads information related to the end-of-month report stored in the case information storage unit 132 at a predetermined time, and transmits it to the customer via the communication network 4 by e-mail. Alternatively, the end-of-month report may be posted on a web page accessible only to the customer using a password assigned at the time of registration with the customer. In this example, the report is submitted at the end of the month, but it may be at the beginning of the month and the time is not limited. However, if the work is fixed monthly, it is desirable to submit a report every month. Thereby, the fixed amount of work can be adjusted based on the report.

  In addition, when a customer desires to obtain information on a work situation at an arbitrary time, the information on the work situation may be obtained from a software house to which the work is entrusted. In this case, the customer uses his / her terminal 3 to send an e-mail or the like describing that he / she wants to obtain information on the work status. The case management server 1 accepts the e-mail and displays the contents on the display. The outsourcer confirms the contents, and requests the case management unit 102 of the case management server 10 to send an e-mail or the like instructing to report the work status to the consigned software house To do. The software house creates and transmits a work report to the case management server 10 by e-mail or the like in the same manner as the month-end report.

  Alternatively, the customer may obtain the work status by clicking the button for obtaining the work status on the web page provided by the case management server 1 using the terminal 3 of the customer. . When the button is clicked, the case management unit 102 of the case management server 10 sends an e-mail or the like instructing the commissioned software house to report the work status via the communication network 4. To do. The software house creates and transmits a work report to the case management server 10 by e-mail or the like in the same manner as the month-end report.

  It is also possible to prepare a program for causing a computer to execute a function for executing the software management system. In this case, the program can be stored in a storage medium and can be transmitted through a communication medium. Here, examples of the storage medium include a floppy (registered trademark) disk, a hard disk, a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD, a ROM cartridge, a RAM memory cartridge with a battery backup, a flash memory cartridge, and a nonvolatile RAM cartridge. Etc. The communication medium includes a wired communication medium such as a telephone line, a wireless communication medium such as a microwave line, and the Internet.

(Appendix 1)
A software management method for estimating work with a computer in response to a request for a plurality of cases from a customer,
Receiving the expected work amount information and work schedule information for each case;
Calculating a total expected work amount for each predetermined period based on the received expected work amount information and the work schedule information;
A computer-based software management method comprising: displaying the total expected work amount for each predetermined period.

(Appendix 2)
The software management method according to supplementary note 1, further comprising a step of adjusting a work schedule so that the calculated total expected work amount for each predetermined period falls within a predetermined work amount range.

(Appendix 3)
A software management method using a computer that outsources work to an outsource destination in response to a job request from a customer,
Receiving a development asset loan request sent from an outsource destination;
A software management method using a computer, the method comprising: placing a development asset in a state where only the outsource destination to which the request is transmitted can be accessed in response to the development asset lending request.

(Appendix 4)
4. The software management method according to appendix 1, 2, or 3, wherein the software-related work is software maintenance / operation.

(Appendix 5)
A software management system that outsources work to an outsource destination in response to a request for a case from a customer,
Development asset storage means for storing development assets;
An access storage means allocated for each outsource destination and accessible only to the outsource destination;
A software management system for storing a development asset stored in the development asset storage unit in the access storage unit when a request for lending the development asset transmitted from an outsource destination is transmitted.

(Appendix 6)
6. The software management system according to appendix 5, wherein the software program is stored in the access storage means when a software program reflecting work from the outsource destination is received.

(Appendix 7)
A storage medium storing a program for estimating a work by a computer in response to a request for a plurality of cases from a customer with respect to a work related to software,
Receiving the expected work amount information and work schedule information for each case;
Calculating a total expected work amount for each predetermined period based on the received expected work amount information and the work schedule information;
A step of displaying the total expected work amount for each predetermined period.

(Appendix 8)
The storage medium according to appendix 7, wherein the program further includes a step of adjusting a work schedule so that the calculated total estimated work amount for each predetermined period falls within a predetermined work amount range.

(Appendix 9)
A storage medium storing a program for outsourcing work to an outsource destination in response to a request for a matter from a customer regarding work related to software,
Receiving a development asset loan request sent from an outsource destination;
A storage medium that executes a step of placing the development asset in a state where only the outsource destination to which the request is transmitted can be accessed in response to the development asset lending request.

It is a block diagram which shows the outline | summary of the software management system concerning this invention. It is a figure which shows the flow of the estimation process concerning this invention. It is a figure which shows the example of a screen display regarding the estimation process concerning this invention. It is a figure which shows the example of a screen display regarding the estimation process concerning this invention. It is a flowchart which shows the flow of the estimation process concerning this invention. It is a flowchart for demonstrating the request of the case to the outsource destination concerning this invention. It is a figure which shows the structure of the software management system concerning this invention. It is a flowchart which shows the specific process in the software management system concerning this invention. It is a figure which shows the flow of the conventional estimation process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Software management system 2 Software house terminal 3 Customer terminal 4 Communication network 10 Case management server 11 Asset management server 12 Test machine 13 Database 101 Registrant information processing part 102 Case management part 103 Estimate processing part

Claims (4)

A software management method using a computer that outsources work to an outsource destination in response to a job request from a customer,
Receiving a development asset loan request sent from an outsource destination;
In response to the development asset lending request, placing the development asset in a state where it can be accessed only by the outsource destination that sent the request;
And a software management method executed by a computer. A software management system that outsources work to an outsource destination in response to a request for a case from a customer,
Development asset storage means for storing development assets;
An access storage means allocated for each outsource destination and accessible only to the outsource destination;
A software management system for storing a development asset stored in the development asset storage unit in the access storage unit when a request for lending the development asset transmitted from an outsource destination is transmitted.   3. The software management system according to claim 2, wherein when the software program reflecting work is received from the outsource destination, the software program is stored in the access storage means. A storage medium storing a program for outsourcing work to an outsource destination in response to a request for a matter from a customer regarding work related to software,
Receiving a development asset loan request sent from an outsource destination;
A computer-readable storage medium that executes a step of placing a development asset in a state in which only the outsource destination to which the request is transmitted can be accessed in response to the development asset lending request.

Images