JP2002196930A - System and method for managing software parts and recording medium recorded with program for managing software parts - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system and a method for managing software parts and a recording medium recorded with a program for managing software parts allowing easily upgrading versions of software parts and easily recognizing information regarding the upgraded parts for a user. SOLUTION: When a new applicant or a revision applicant desires and applies to registration or revision of the software parts, an examiner examines it by evaluating documents and source codes of the applied software parts on the basis of examination minimum criteria recorded in a server 10. Then information of the software parts registered/applied in revision is transmitted to an approver who approves the examined results. If the approver approves the examined results, the software parts registered/applied in revision are stored in a database 27 of the server 10 which is notified to the new applicant or the revision applicant.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention stores a software component management system, a software component management method, and a software component management program for managing software components by numbers such as versions and revisions via a network communication field such as the Internet. Related to a storage medium.

[0002]

2. Description of the Related Art In recent years, the remarkable progress in the communication field has led to the widespread use of the Internet, which has made it possible for individual users to purchase, buy, sell, and participate in auctions on terminal devices. In such a software component purchasing system, when a user participates in the purchase of a software component on the Internet, the user can recognize the version of the software component to be purchased. Japanese Patent Application Laid-Open No. H11-219284 describes a version upgrade method for notifying each terminal of version upgrade information in a network environment. Also, Japanese Patent Application Laid-Open
Japanese Patent Application Laid-Open No. 0-320184 discloses a software version management system for upgrading a running software, and Japanese Patent Application Laid-Open No. H11-143694 discloses a software relating to a version management form of managing software by ID and version. It describes the version upgrade method.

[0003]

However, in a conventional software version upgrade method and software version upgrade system that manages software by version and revision numbers, software such as requirement specifications, design specifications, and user's manuals are assisted. It was not clear what changed the source code, object code, etc. of the documents and software parts for the change (hereinafter referred to as the change target). Also, for example, when the object to be changed is the source code, it is not clear which part of the source code has been changed, and the user may recognize the compatibility between the software part before the change and the software part after the change. Sometimes it was difficult. In general, large-scale software is developed by dividing software into components, which are components, and assigning a developer to each software component. In many cases, the version upgrade at the time of software component revision is managed by the individual development staff based on the change history. In this case, the method of updating the version and the contents of the change history depend on the development staff. It is often not considered to facilitate recognition.

FIG. 7 is a diagram showing factors of software component revision, revision range, and compatibility after revision. Revisions of software parts can be classified into two types from the viewpoint of compatibility: those that are incompatible or possibly not with the software parts before revision and those that are compatible with the software parts before revision. . As shown in FIG. 7, when a software component is revised, a plurality of factors (triggers) can be considered, and there are often a plurality of objects to be changed. Therefore, the work format at the time of revision depends on the management form depending on the individual developer. As a result, the user of the software component will have less understanding of the revised content.

Accordingly, a first object of the present invention is to easily upgrade a software component by defining a version or revision of the software component as a version element, and to provide information on the upgraded software component to a user. A software component management system, a software component management method, and a storage medium storing a software component management program that can be easily recognized by a user. A second object of the present invention is to provide a software component management system, a software component management method, and a storage medium storing a software component management program that can derive information on a change target from version information.

A third object of the present invention is to specify whether the software component of the revision is compatible with the mounting environment in which the software component of the revision was mounted.
An object of the present invention is to provide a software component management system, a software component management method, and a storage medium storing a software component management program that can guarantee that the software component operates even in the operating environment of the software component before revision. A fourth object of the present invention is to provide a software component management system, a software component management method, and a storage medium storing a software component management program that can derive information on compatibility / non-compatibility of a mounting application environment from version information. That is. A fifth object of the present invention is to provide a software component management system, a software component management method, and a storage device storing a software component management program capable of preventing duplicate maintenance of different versions of the same ID, that is, the same type of software component. Is to provide a medium.

[0007]

According to the first aspect of the present invention, in a software component management system for managing and registering software component versions via a computer network, a software component source code,
A software component information acquisition unit that acquires information and version information for each item such as a document and a specification manual, and stores it together with version information as software component information, and each item of software component information acquired by the software component information acquisition unit Revision request acquisition means for acquiring a revision request of the software component revision means for revising each item of the software component acquired by the software component information acquisition means based on the revision request acquired by the revision request acquisition means. Software component presentation means for presenting software component information revised by the software component revision means in response to a request from a software component purchase applicant or a software component use applicant, and wherein the revision request acquisition means comprises: Software The first object is achieved by acquiring a request to revise a change object, which is an item to be revised, such as a source code, a document, and a specification manual of a software component stored in the component information acquisition unit. .

According to a second aspect of the present invention, in the first aspect of the present invention, the software component revision unit acquires the software component information based on a revision request for a change object acquired by the revision request acquisition unit. The second object is achieved by upgrading the version information of the software component stored in the means. According to a third aspect of the present invention, in the first or second aspect of the present invention, the revision request acquiring unit includes a software component stored in the software component information acquiring unit revised by the software component revision unit. When acquiring compatibility information indicating whether or not there is compatibility with the mounting environment before the revision, the software component presentation unit converts the compatibility information into the software component purchase applicant or the software component use applicant. The third object is achieved by presenting the information in response to a request from the company. According to a fourth aspect of the present invention, in the third aspect of the present invention, the software component revision unit is stored in the software component information acquisition unit based on the compatibility information acquired by the revision request acquisition unit. The fourth object is achieved by upgrading the version information of the software component of the software component.

According to a fifth aspect of the present invention, in any one of the first, second, third, and fourth aspects of the invention, the software component presentation means is provided by the software component revision means. The fifth object is achieved by posting the latest revised software component. In the invention described in claim 6, in the invention described in any one of claims 1, 2, 3, 4, and 5, the software component revising means is configured to obtain the software component information. The fifth object is achieved by making the software component of the latest version information among the software components stored in the means a revision target.

According to a seventh aspect of the present invention, there is provided a software component management method for managing and registering software component versions via a computer network, wherein information on each item such as a source code, a document, and a specification manual of the software component is provided. Get version information,
A first step of storing the software component information together with the version information, a second step of obtaining a revision request for each item of the software component information obtained in the first step, and a second step of obtaining a request for revision of each item of the software component information obtained in the first step. A third step of revising each item of the software component obtained in the first step based on a revision request;
A fourth step of presenting the software component information revised in the third step in response to a request from a software component purchase applicant or a software component use applicant. 1
The first object is achieved by acquiring a revision request for a change object, which is an item to be revised, such as a source code, a document, a specification manual, or the like of a software component stored in the step.

According to an eighth aspect of the present invention, in a storage medium storing a software component management program for managing and registering software component versions via a computer network, a source code, a document, a specification manual, and the like of the software component are stored. A software component information acquisition function that acquires information and version information for each item and stores it together with version information as software component information, and a revision that acquires a revision request for each item of software component information acquired by the software component information acquisition function A request acquisition function, a software component revision function for revising each item of the software component acquired by the software component information acquisition function based on the revision request acquired by the revision request acquisition function, and the software unit A software component presentation function for presenting software component information revised by the revision function in response to a request from a software component purchase applicant or a software component use applicant, and a computer readable software management program for realizing the computer. A change object which is a storage medium in which the revision request acquisition function is an item to be revised such as a source code, a document, a specification manual of a software component stored by the software component information acquisition function; By acquiring a revision request for
Achieve the objectives.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will be described below in detail with reference to FIGS. (1) Overview of Embodiment In the software component management system according to the present embodiment, a user who wants to register a software component (hereinafter, referred to as a new applicant) or a user who wants to revise information on an already registered software component (hereinafter, a user). , A revision applicant) requests the PC terminal 1 to register or revise the applied software component, and the server 10 receives the registration / revision application. An examiner who examines a software component for which registration / revision has been applied evaluates a document or source code of the applied software component based on a minimum examination standard stored in the server 10. As a result of the examination by the examiner, if registration or revision of the software component for which registration / revision has been applied is determined to be permitted, information on the registered / revision-applied software component is sent to an approver who approves the examination result. When the approver approves the result of the examination by the examiner, the registered / revised application software component is
0 is stored in the database unit 27, and that effect is notified to the new applicant or the revision applicant.

A user who wants to purchase a software component (hereinafter referred to as a “purchase applicant”) can use the PC terminals 1, 2,
.., The information of each software unit stored in the database unit 27 of the server 10 can be viewed from the n side, and a purchase procedure for a desired software component can be performed.
That is, the purchase request can be transmitted to the server 10. Then, the user who has completed the purchase procedure is referred to the server 1
From 0, software components can be received. In the present embodiment, the server 10 receives a predetermined processing request from each of the PC terminals 1, 2,..., N in the user environment, and responds to the received request from the user.
The software components stored in the database unit 27 can be distributed to the terminals 1, 2,..., N. In the present embodiment, a software component refers to a software component that is made into components, that is, a module that is an independent process for each component.

(2) Details of Embodiment FIG. 1 is a diagram showing a configuration of a software component management system according to this embodiment. As shown in FIG. 1, a software component management system 100 is connected to a server 10 according to an embodiment of the present invention via networks 11 and 12, and a new registration applicant and a purchase applicant are connected to this server 10. , PCs (personal computer) terminals 1, 2,..., N functioning as request transmitting devices for transmitting predetermined processing requests by the revision applicant. .., N from the PC terminals 1, 2,..., N, a new registration application by the new registration applicant, a request for revision of registered software component information by a revision applicant, and a purchase applicant Functioning as a request receiving device for receiving a predetermined processing request such as a request for purchase of a software component by the user. When the server 10 receives a new registration application or a revision application, the examiner notifies the PC terminals 1, 2,.
, Also functions as a request processing result transmitting device for transmitting to n.

In this embodiment, the networks 11 and 12 will be described as the Internet as an example.
The present invention is not limited to this, but may be a captain system or any other WAN (Wide Area Network).
, N, a new registration applicant, a purchase applicant, a revision applicant, etc. can transmit a predetermined processing request to the server 10 and the server 10 ,..., N may be any network that can execute the required processing. In this embodiment, the networks 11, 1
2, the server 10 and the PC terminals 1, 2,..., N
The network may be connected by any of wired, wireless, or both, and may be any of a communication network using a line via a dedicated line, a wireless communication network using a portable terminal, and an information communication network using a communication satellite. In the present embodiment, PC terminals 1, 2,...
.., N are described as personal computers,
The present invention is not limited to this, and mobile phones, PDAs (Pe
rsonal Digital Assistant
s) and the server 10 and the networks 11 and 12
It is assumed that a terminal capable of transmitting and receiving information via the terminal is sufficient.

FIG. 2 is a block diagram showing the configuration of the server 10. The server 10 includes a control unit 21,
The display unit 22, the communication control unit 23, the input / output unit 24, the storage unit 25, and other devices (not shown) are connected via a bus line such as a data bus. The control unit 21 includes various devices according to a program, a CPU (central processing unit) for controlling and calculating each unit, a ROM (read only memory) for storing a program and data for the CPU to perform various controls and calculations, The CPU includes a RAM (random access memory) used as a working memory. The control unit 21 includes a plurality of PC terminals 1, 2,.
.., N can be individually and simultaneously processed simultaneously. The input / output unit 24 is connected to the network 11,
, N connected via the communication terminal 23, the applicant information such as the address, name, and telephone number of the new registration applicant or the revision applicant received by the communication control unit 23, and the new registration application Predetermined processing requests and data for software parts information that you wish to apply for or to apply for revision, purchaser information such as the address, name, and phone number of the purchaser, examination information that is the result of the examination by the examiner, and approval information by the approver. Is input to and output from the storage unit 25.

The display section 22 displays various information received from the PC terminals 1, 2,..., N received by the communication control section 23. The communication control unit 23 connects to the networks 11 and 12 via a general telephone line, an ISDN, and a wireless telephone line, and plays a role of a response function to a processing request together with the control unit 21 that controls the communication control unit 23. Storage unit 25
Mainly uses a hard disk which is a large-capacity storage device, stores programs and data for the CPU of the control unit 21 to perform various controls and calculations, and stores the programs and data in the software component management system according to the present embodiment. A functioning program unit 26, and PC terminals 1, 2, ...
A database unit 27 for storing predetermined data such as applicant information from n.

The program section 26 includes a database section 2
Applicant data, which is the information of the new registration applicant or the revision applicant stored in 7, the software component data of the software parts that the new registration applicant or the revision applicant wants to register / revise, the examination result data by the examiner, the examiner Examination criteria data, which is the basis for examination when the applicant examines the applicant data and software component data, approval data based on the examination result by the approver, and registration data of the applicant data and software component data registered by passing the examination , N via the networks 11, 12, a predetermined process (for example, transmission of the examination result of software component data desired to be assessed) , Data transmission processing of software parts data etc. desired by the purchaser) And a request receiving program for receiving processing requests from new registration applicants, revision applicants, and purchasers, and processing required for processing requests received by the request receiving processing program (data transmission processing such as examination results). And a variety of other programs.

In the database unit 27, the PC terminal 1,
The application data 27a received from 2,..., N, the examination criteria data 27c used as the basis for the examination when the assessor examines the application data 27a, Data 27b and other data are stored. The application data 27a includes the number of software component files requested to be examined by the examiner,
Scale, instructions, such as the number of classes, steps, bytes, etc.
Documents such as specifications and commentary, source code (source program), reviews of each phase documents and deliverables for errors, review results, test results, operation manuals, required for screening of usage or sales results etc. Software component data such as the attributes of various software components, and applicant data such as the address, name, occupation, and age of each applicant are stored.

The examination data 27c includes the application data 2
The examiner examines whether the software component data stored in 7a is usable or can be sold, and whether the version upgrade of the software component for which the revision application has been applied or the revision of the software component document, etc. is appropriate. In this case, document data on source software components, source code, characteristic data such as reviews, and examination data of past examination results are stored. The registration data 27b stores software component data and the like that the examiner passes the examination to be registered, used, revised, and sold based on the examination criteria data 27c.

In the case of a revision application by a revision applicant,
The registration data 27b includes a version element such as a version and a revision of a software component as a revision source, a version element after the revision, a requirement specification, a design specification, a user's manual, and other documents for assisting the software and software component. Information on what has been changed (object to be changed) out of source code, object code, etc. For example, if the object to be changed is source code, information such as which part of this source code has been changed, etc. Information is stored. Database unit 27
Are stored in the input / output unit 24 according to the programs stored in the program unit 26.
, And via the networks 11 and 12, the data is input from the PC terminals 1, 2,. In addition, application data 27
The IDs (identifiers) are individually added to the registered software components a and the registration / revision application in the registration data 27b, and the software component information on each software component is managed by the ID.

Next, management of software components that have been registered and revised in the software component management system according to the present embodiment will be described. FIG. 3 is a diagram showing a registration application / revision application for a new software component in the software component management system. In this embodiment, when the control unit 21 of the server 10 notifies that the registration, revision, and purchase request from each applicant have been received, the examiner uses the software displayed on the display unit 22 of the server 10. Inspection is performed by referring to the contents of the component data. When the examination result is notified by the control unit 21, the approver refers to the assessment result displayed on the display unit 22 of the server 10 to approve. It will be described, but not limited to this. For example, the server 10 and the networks 11, 1
2, a control unit 21 of the server 10 may transmit registration request, revision request, examination result, purchase request, and other data to this other terminal device. Another terminal device may be one of the PC terminals 1, 2,..., N. In this case, the examiner and the approver respond to the data such as the examination request, the revision request, the examination result, and the purchase request received from the control unit 21 of the server 10 by another terminal device (or PC terminal). , And each response can be transmitted to the server 10.

Hereinafter, a revision application in the software component management system according to the present embodiment will be described. In addition,
A revision application is a document or software part that has already been submitted for registration and has been registered and determined by the examiner, such as a version element such as the version and revision of the software part, a requirement specification, a design specification, and a user's manual. Means to apply for revision of the object to be changed, such as source code and object code. In addition, about the new registration application, PC terminal 1,
Each processing operation of the server 10 that performs registration / examination in response to a processing request from 2,..., N is the same as that at the time of the application for revision, and a description thereof will be omitted. The control unit 21 of the server 10 monitors whether or not there is access from the PC terminal 1 via the networks 11 and 12. When you access the parts management system,
The file (application slip) is transmitted from the server 10 to the PC terminal 1. The application form transmitted by the control unit 21 of the server 10 is
It is displayed on the display screen of the PC terminal 1.

According to the method of filling out the application form displayed on the display screen, the revision applicant submits the revision applicant data such as address, name and age, the actual software component, the number of software component files to be revised, Software that is the attribute of software components such as the number of classes, the number of steps, the number of bytes, documents such as manuals, specifications, and commentary, source code, review results, test results, operation manuals, and the number of uses or sales. Enter application data by entering part data, the relationship between the object to be changed and the version element, compatibility information on whether the revised software component is compatible with the environment in which the original software component was mounted, etc. Is created and the application procedure is performed by clicking the application button on the display screen (step 30).
1). The control unit 21 of the server 10 stores the application form received from the PC terminal 1 by the communication control unit 23 in the application data 27a of the database unit 27 and, at the same time, receives the application form from the examiner who is a system administrator. That is, it notifies that the revision request has been received.

The examiner who has received the notification from the control unit 21 creates a registration form as a result of the examination, such as whether the software component to be revised meets the minimum examination standard based on the application form, and performs the examination. (Step 302). The examination by the examiner is based on the examination criteria data 2 in the database section 27.
This is performed based on characteristic data such as documents, source codes, reviews, etc. regarding software components stored in 7c, and examination data of past examination results. Judgment includes, for example, the number of software component files, classes, steps, bytes, etc., documentation such as manuals, specifications, commentary, source code, review results, test results, operation manuals, use or sales A check sheet is created for each attribute such as the number of achievements, and if the criteria are cleared for each attribute, the number of checks is set to 1, and whether or not the examination passed, the assessment amount, etc. are determined according to this number of checks It has become.

When the examiner determines that the examination has been passed (step 302; examination passed), that is, when the examined software component can be revised, it is determined based on the version information of the original software component. The procedure of revising the version and attaching this examination result to the registration slip and sending it to the approver is performed. When the examiner executes transmission of the registration slip to the approver by clicking the registration button on the display unit 22, registration approval (revision approval) processing is performed by the approver who has received the registration slip (step 3).
03). When the approver selects the registration approval button on the display unit 22, the control unit 21 registers the registered registration form in the registration data 27 b of the database unit 27 (step 304), and at the same time, via the networks 11 and 12. A notice of registration approval is displayed on the display screen of the connected PC terminal 1. The revision applicant who has confirmed this registration approval
When the confirmation button on the display screen of the C terminal 1 is selected, the server 10 is notified of the confirmation. Upon receiving the confirmation, the control unit 21 of the server 10 displays on the PC terminal 2 of the purchaser when the purchaser accesses the software component management system on the PC terminal 2 and inputs the purchase and use of the software component. The corresponding software component data stored in the registration data 27b is posted on the screen.

On the other hand, if the examiner judges that the examination has failed (step 302; examination failed), that is, if the examiner judges that it is not possible to revise the examined software component, the examination that has failed is judged. Perform the procedure to attach the result to the registration slip and send it to the approver. When the examiner selects the non-registration button on the display unit 22 and transmits the registration form as non-registration to the approver, the approver who has received the non-registered registration form performs non-registration approval (non-revision approval). ) Processing is performed (step 305). Approver is the display unit 22
Is selected, the control unit 21 discards the non-registered registration slip without registering it in the registration data 27b of the database unit 27 (step 3).
06), the non-registration approval is displayed on the display screen of the PC terminal 1 connected via the networks 11 and 12.

Next, with respect to the software management system of the present embodiment, a user who wants to purchase a registered revised software component (hereinafter referred to as a purchase candidate) or a user who wants to use the software component (hereinafter referred to as a use). The processing operation of the server 10 when there is an access from a requester will be described. FIG. 4 is a diagram showing a relationship between IDs and version elements of each software component managed by the software component management system. In the registration data 27b of the database unit 27 of the server 10, version elements of each software component data are managed and registered as shown in FIG. In this embodiment as a version element,
Version identifying the revision of the same software component (V
) and a revision (Revision), which is the revision number of the same software component, is managed and registered in correspondence with the ID of each software component.

First, a purchase applicant or a use applicant (neither applicant is a user who is not using a software component) is displayed on the display screen of each of the PC terminals 1, 2,. To enter a request to purchase or use software components. Server 10 that has received this purchase or use request
The control unit 21 extracts software component information corresponding to a purchase request or a use request from the database unit 27 and, together with each version element of the revised software component as shown in FIG.・ ・
・ Display on the display screen of n. Here, the control unit 21
As shown in FIG. 5, the display screens of the PC terminals 1, 2,..., N display the latest number of each software component (the software component corresponding to the latest version information).

As described above, each applicant can refer not to the information of all the software components managed and registered as shown in FIG. 4 but to the software component of the latest version element. There is no need to refer to the extra information that has increased by the number. In addition,
The underlined portions in FIGS. 4 and 5, for example, “GUI parts” and “0002” indicate the scale of the number of files, classes, steps, bytes, etc. of software components revised by the revision applicant. , Manuals, specifications, commentary, and other documents, source code, review results, test results, operation manuals, and the like, and version elements of each revised software component.

In the present embodiment, it has been described that the version of the software component requested for revision by the revision requester is upgraded. However, the control unit 21 performs the process shown in FIG. As shown in FIG. 6, when a software component designated to be revised has been upgraded and revised up before, the latest version of the software component may be targeted for change. The underlined portion in FIG. 6 is the software component information portion to be revised, and the bold portion indicates revision of the latest version of the software component and further version up. For revised software parts,
Version elements can be attached objectively (rather than subjectively) and regularly. Further, the user of the software component can reduce the work time for specifying the changed object of the software component.

As described above, in the software component management system according to the present embodiment, the version element of the software component for which the revision has been applied is confirmed, and when the content of the change is understood, the object to be changed is specified. Then, it recognizes the presence / absence of risk (compatible / absent) in the case of adaptation to the mounting environment of the software component, and investigates the specified change object. If there is a risk due to the revision, the change object specified in consideration of this risk and the mounting environment are adapted. In other words, because the examiner does not pass the application for revision, the user of the software component has already identified the changed object of the revised software component. Can be reduced in the work time for specifying Also,
In the software component management system according to the present embodiment, a version element can be objectively and regularly attached to a software component to be revised, and a user of the software component can use the software component when the software component in use is revised. Recognize the presence / absence of risk in the work of applying a revised software component to a mounting environment without investigating each change object and improve the work efficiency of software component maintainers be able to.

As described above, in the software component management system according to the present embodiment, the version and revision of the software component are defined as version elements, thereby easily upgrading the version of the software component. Can be easily recognized by the user, and information on the object to be changed can be derived from the version information. Also, in the software component management system according to the present embodiment, by specifying whether the software component compatible with the mounting environment in which the original software component is mounted is compatible with the software component before the revision. It can be ensured that the component operates even in the operating environment, and the compatibility information of the mounting application environment can be derived from the version information. Furthermore, in the software component management system according to the present embodiment, it is possible to prevent duplicate maintenance of the same ID, that is, different versions of the same type of software component.

[0034]

According to the first aspect of the present invention, the revision request acquiring unit is an item to be revised, such as a source code, a document, or a specification manual of a software component stored in the software component information acquiring unit. Since the revision request of the change object is obtained, the version component can be objectively and regularly attached to the software component to be revised, and the user of the software component can change the change object of the revised software component. The work time for specifying the information can be shortened. In the invention according to claim 2, the software component revision means upgrades the version information of the software component stored in the software component information acquisition means based on the revision request of the change object acquired by the revision request acquisition means. Therefore, the user of the software component can shorten the work time for specifying the changed object of the revised software component.

According to the third aspect of the present invention, the revision request acquiring means is compatible with the mounting environment before the revision of the software component stored in the software component information acquiring means revised by the software component revision means. If the compatibility information indicating whether or not the software component has been acquired is obtained, the software component presentation means presents the compatibility information, and the user must objectively and regularly associate the version element with the revised software component. Can be. In the invention described in claim 4, the software component revision means upgrades the version information of the software component of the software component stored in the software component information acquisition means based on the compatibility information acquired by the revision request acquisition means. Therefore, when the software component being used is revised, the user of the software component determines whether or not there is a risk in the operation of applying the revised software component to the mounting environment, one by one for each of the objects to be changed. Can be recognized without investigating.

According to the fifth aspect of the present invention, since the software component presenting means posts the latest software component revised by the software component revision means, the work efficiency of the maintenance person of the software component can be improved. According to the invention described in claim 6, the software component revision means targets the revision of the software component of the latest version information among the software components stored in the software component information acquisition means. Can be improved.

In the invention according to claim 7, the second step is a change object which is each item to be revised, such as a source code, a document, and a specification manual of the software component stored in the first step. Of the revised software component, the version component can be objectively and regularly attached to the revised software component, and the user of the software component can identify the change target of the revised software component. Work time for performing the operation can be shortened. According to the invention described in claim 8, the revision request acquisition function is for revising a change object, which is an item to be revised, such as a source code, a document, or a specification manual of a software component stored by the software component information acquisition function. Since the request is obtained, the version component can be objectively and regularly attached to the software component to be revised, and the user of the software component can specify the change object of the revised software component. Work time can be reduced.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of a software component management system according to an embodiment.

FIG. 2 is a block diagram showing a configuration of a server.

FIG. 3 is a diagram showing a registration application / revision application for a new software component in the software component management system.

FIG. 4 is a diagram showing a relationship between IDs and version elements of each software component managed by the software component management system.

FIG. 5 is a diagram showing software components corresponding to the latest version information.

FIG. 6 is a diagram for explaining revision of a latest version of a software component.

FIG. 7 is a diagram showing factors of software component revision, a revision range, and compatibility after revision.

[Explanation of symbols]

1, 2, ..., n PC (personal computer)
Terminal 10 Server 11, 12 Network 21 Control unit 22 Display unit 23 Communication control unit 24 Input / output unit 25 Storage unit 26 Program unit 27 Database unit

Claims (8)

[Claims] In a software component management system for managing and registering software component versions via a computer network, information and version information of each item such as a source code, a document, and a specification manual of the software component are acquired. Software component information acquisition means for storing together with version information as software component information; revision request acquisition means for acquiring a revision request for each item of software component information acquired by the software component information acquisition means; acquisition by the revision request acquisition means Software component revision means for revising each item of the software component acquired by the software component information acquisition means based on the revised revision request; and software component information revised by the software component revision means. Software component presenting means for presenting a software component in response to a request from a software component purchase applicant or a software component use applicant. A software component management system characterized by acquiring a revision request for a change object, which is an item to be revised, such as a source code, a document, and a specification manual. 2. The software component revision means upgrades version information of a software component stored in the software component information acquisition means based on a revision request for a change object acquired by the revision request acquisition means. The software component management system according to claim 1, wherein 3. The method according to claim 1, wherein the revision request acquiring unit is configured to determine whether the software component stored in the software component information acquiring unit revised by the software component revision unit is compatible with a mounting environment before the revision. Wherein the software component presenting means presents the compatibility information in response to a request from the software component purchase applicant or the software component use applicant. 1 or Claim 2
Software component management system as described. 4. The software component revision means upgrades software component version information of software components stored in the software component information acquisition means based on the compatibility information acquired by the revision request acquisition means. The software component management system according to claim 3, wherein 5. The software component presenting means for posting the latest software component revised by the software component revision means.
The software component management system according to any one of claims 2, 3, and 4. 6. The software component revision unit according to claim 1, wherein the software component of the latest version information among the software components stored in the software component information acquisition unit is to be revised. 2, one of claim 3, claim 4, and claim 5
Software component management system described in 1. 7. A software component management method for managing and registering software component versions via a computer network, comprising: acquiring information and version information of each item such as a source code, a document, and a specification manual of the software component; A first step of storing the software component information together with the version information; a second step of obtaining a revision request for each item of the software component information obtained in the first step; A third step of revising each item of the software component obtained in the first step based on the revision request; and a software component purchaser or software component Provided in response to a request from the applicant The second step is a change object which is an item to be revised, such as a source code, a document, or a specification manual of the software component stored in the first step. A software component management method characterized by acquiring a product revision request. 8. A storage medium storing a software component management program for performing version management / registration of software components via a computer network, comprising: information for each item such as a source code, a document, and a specification manual of the software component; A software component information acquisition function for acquiring version information and storing it together with version information as software component information; a revision request acquisition function for acquiring a revision request for each item of software component information acquired by the software component information acquisition function; A software component revision function for revising each item of the software component acquired by the software component information acquisition function based on the revision request acquired by the revision request acquisition function; Storing a computer-readable software component management program for causing a computer to realize a software component presentation function for presenting the software component information in response to a request from a software component purchase applicant or a software component use applicant. Medium, wherein the revision request acquisition function is a source code of a software component stored in the software component information acquisition function, a document, a request for revision of an object to be modified, which is an item to be revised, such as a specification manual. A storage medium storing a computer-readable software component management program to be realized by a computer, which is to be acquired.