JP3702294B2 - Software development system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a software development system suitable for use when a plurality of software development companies develop different software in accordance with an order from an orderer.
[0002]
[Prior art]
Conventionally, a software development system has been known in which multiple software development companies develop different software according to the order from the ordering party, and deliver the developed software to the customer (ordering party) via a network such as the Internet. It has been.
[0003]
[Problems to be solved by the invention]
However, the conventional software development system has the following problems.
・ Software development companies generally perform operation check tests in conjunction with software developed by other companies, but the software (load modules) developed by other companies may not always be up-to-date. . Also, it took time and effort to determine whether it was the latest state.
[0004]
・ Because version management of the developed source file (text information) is done by the person in charge of development (manual work), the wrong version has been delivered due to mistakes in communication between developers, work mistakes, etc. There were many cases.
・ Because a network that connects software development companies and software delivery destinations was built on a dedicated line basis, the communication cost for one year was enormous.
[0005]
An object of the present invention is to provide a software delivery and version management method by a plurality of companies in a software development system using the Internet in order to solve the above problems.
[0006]
[Means for Solving the Problems]
In order to achieve the above object, in the software development system according to the present invention, a software development orderer orders different software developments from a plurality of software development devices, and each software development device loads the developed software. Delivered as a module to the orderer via the network, and the orderer delivers the load module delivered to each software development device via the network in the software development system delivered from each software development device Registration means for creating and registering information relating to a load module and distribution means for delivering a corresponding load module to each software development device when it is detected that the information registered in the registration means is updated are provided. Is.
[0007]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
In the embodiment of the present invention, a plurality of software development companies requested to develop different software from the ordering party deliver load modules to the ordering party (delivery destination) via the Internet, and the ordering party receives the load modules. Are provided to each software development company, a mechanism in which the software development company delivers source files (text information) via the Internet, and a source file version management method.
[0008]
First, the outline of each embodiment will be described.
First, a mechanism for delivering a load module will be described with reference to FIG.
In FIG. 1, a software development company A20 transmits a load module A14 developed by its own development server A to the load module storage area 11 of the software delivery destination (ordering party) 10 via the network 100. Further, the load module update information 13 in the WWW server 17 of the software delivery destination 10 is updated. Thereafter, the update status in the load module storage area 11 is collected by the automatic distribution program 12 activated at a fixed time, and the updated load module is distributed to each software development company A20, B30, C40.
[0009]
Next, a mechanism for delivering a source file will be described with reference to FIG.
Software development company A uses version management program 24 on its development server A to retrieve the latest version of source file A25. After correcting the source file A25, an operation check test is performed using the generated load module. If the normal operation can be confirmed, the source file A ′ 26 with the current modification is registered as the latest version using the version management program 24. At this time, the difference information 27 between the source file A25 and the source file A'26 is taken and left at hand. Then, the source file A ′ 26 is transmitted to the temporary source file storage area of the software delivery destination 10 via the network 100.
[0010]
The software delivery destination 10 takes the difference information 23 between the source file A′22 (source file A′26) delivered this time and the source file A21 corresponding to the old version, and this difference information 23 is obtained via the network 100. Send to software development company A20.
[0011]
The software development company A20 compares the received difference information 23 with the difference information 27 left at hand. If the two are the same, the software delivery destination 10 determines that the source file A'22 is the latest official delivery version and registers it as the source file A21.
[0012]
Next, a first embodiment of the load module delivery mechanism will be described in detail.
In FIG. 1, the present embodiment includes a management server 18 and a WWW server 17 of a software delivery destination (ordering party) 10, development servers A, development servers B, and development servers C of software development companies A20, B30, and C40. The communication network 100 is an internet connecting these components.
[0013]
The management server 18 and the WWW server 17 of the software delivery destination 10 are information processing devices provided with magnetic disk devices. The management server 18 stores and stores load modules delivered from the software development companies A20, B30, and C40, and executes an automatic distribution program by starting at a fixed time, thereby developing the development server of each software development company. 1 has a function of distributing a load module to be distributed via the network 100.
[0014]
Further, the WWW server 17 has a function of providing load module update information as screen information when an inquiry is received from each software development company. As the update information, information related to the load module such as the Japanese name, ID, and update date of the load module can be referred to as shown in FIG.
[0015]
Development servers A, B, and C of each software development company are information processing devices equipped with magnetic disk devices, and have areas for storing and storing load modules developed by the company and load modules developed by other companies. In addition, it has a function that can be connected to the management server 18 and the WWW server 17 of the software delivery destination 10 via the network 100 by the operation of the operator.
[0016]
Next, the operation of the present embodiment will be described in detail with reference to FIG. 1, FIG. 3, and FIG.
In FIG. 3, the software development company A20 generates a new load module A on its development server A using a newly created or modified source file (step A1). Next, this new load module A is transmitted to the load module storage area 11 in the management server 18 of the software delivery destination 10 using a file transfer protocol (FTP) (step A2).
[0017]
Also, for the purpose of notifying the development company other than the software development company A20 and the software delivery destination 10 that the load module A has been updated, the update information of the load module is created and registered in the WWW server 17, and the browser (Step A3). As the update information of the load module, information related to the load module such as a business name, a Japanese name, an ID name, and an update date is displayed in a format as shown in FIG.
[0018]
Next, at the software delivery destination 10, the automatic distribution program 12 that is activated at a fixed time is activated. This is because the OS of the management server 18 is set in advance so that the automatic distribution program 12 is executed every day at midnight (23:00 to 3:00 on the next day). It has become a mechanism. The automatic distribution program 12 first checks the update status of the load module storage area 11 of the management server 18 and extracts a property whose date has been updated by newly providing a load module. The extracted load module is transmitted to the development server of each software development company using a file transfer protocol (FTP) (step A4).
[0019]
From the next day, software development company B30 and software development company C40 that received distribution of load module A can know that load module A has been updated by browsing WWW server 17 of software delivery destination 10. (Step A5, A5 ′). In addition, the load module A15 is stored in the load module storage area in the management server of company B, and the load module A16 is stored in the load module storage area in the management server of company C. The function can be confirmed by executing the load module A (steps A6 and A6 ′).
[0020]
According to this embodiment, even if the load module is developed by another company, when the load module of the software delivery destination is updated, the distribution program automatically sends it. An environment for confirmation can be obtained.
In addition, update information of load modules developed by other companies can be easily obtained by referring to the WWW server (homepage).
[0021]
Next, an embodiment of a source file delivery and version management mechanism will be described in detail.
In FIG. 2, the present embodiment includes a management server 18 of a software delivery destination 10 and development servers A, B, and C of software development companies A20, B30, and C40 (here, software development company A will be described as an example). The communication network 100 is an internet connecting these components.
[0022]
The management server 18 of the software delivery destination 10 is an information processing device provided with a magnetic disk device. The management server 18 has an area for storing and storing a source file delivered from each software development company as an official version, and an area for temporarily storing a source file from each software development company immediately after delivery. .
[0023]
The development server of each software development company is an information processing device equipped with a magnetic disk device, which consists of an area for storing and storing source files developed by the company, and a program that has a version management function for those source files. It has a function capable of connecting to the management server 18 of the software delivery destination 10 via the network 100.
[0024]
Next, the operation of the present embodiment will be described in detail with reference to FIGS.
In FIG. 4, the software development company A20 pays out the latest version of the source file A25 using the version management program 24 on its development server A (step B1). Next, the paid out source file A25 is corrected (step B2). Then, an operation check test is performed using the load module generated from the corrected source file A′26 (step B3). Here, when an abnormality is recognized in the operation check test, the process returns to step B2, and the source file A'26 is corrected again (step B3, NG route).
[0025]
When normal operation is confirmed in the operation check test, the modified source file A′26 is registered as the latest version of the source file using the version management program 24 (step B4).
[0026]
Next, the difference information 27 between the uncorrected source file A25 and the latest version of the source file A'26 is acquired (step B5). The difference information 27 can be acquired by using the diff command when the OS of the development server A is UNIX.
[0027]
Then, the latest version of the source file A′26 is transmitted to the temporary storage area of the source file in the management server of the software delivery destination 10 using the file transfer protocol (FTP) (step B6). The software delivery destination 10 acquires difference information 23 between the latest version of the source file A′22 (source file A′26) delivered this time and the old version of the source file A21 registered in the management server 18. The difference information 23 can also be acquired by using the diff command when the OS of the management server is UNIX. Next, the difference information 23 is transmitted to the development server A of the software development company A using a file transfer protocol (FTP) (step B8).
[0028]
In response to this, the software development company A20 compares the difference information 27 acquired in advance and left at hand with the transmitted difference information 23 (step B9). If there is a mismatch between the two, the process returns to step B6 to transmit the source file A'26 again (step B9, NG route).
[0029]
If the difference information matches, the software development company A20 reports to the software delivery destination 10 that the source file has been transmitted correctly (step B10). Upon receiving this report, the software delivery destination 10 registers the source file A′22 delivered this time as an official version (step B11). As a means for communicating that the file has been transmitted between the software development company A20 and the software delivery destination 10, a telephone, a FAX, an electronic mail, or the like can be used.
[0030]
According to the present embodiment, it is possible to prevent a work mistake such as correcting an old version by performing an operation of paying out / registering a source file using a version management program.
In addition, the source file (text information) may be falsified by a malicious third party due to the use of a network based on the Internet, but both the development side (correction source) and the delivery destination Since the difference information taken is matched, tampering can be prevented.
[0031]
Next, a second embodiment of the load module delivery mechanism will be described with reference to FIG.
In FIG. 6, the present embodiment relates to the management server 18 and the WWW server 17 of the software delivery destination 10, the development servers A, B, and C of the software development companies A20, B30, and C40, and the connection of the communication network at each location. The firewall 19, 19 </ b> A, 19 </ b> B, 19 </ b> C having a VPN function (virtual private network function) at a point, and a communication network 100 by the Internet that connects these to each other. 1 is different from the first embodiment of FIG. 1 in that a firewall having a VPN function is installed at a connection point of the communication network 100. Except for this part, the operation is substantially the same as that of the first embodiment. On the other hand, there is no change.
[0032]
The firewalls 19, 19 A, 19 B, and 19 C having the VPN function automatically perform user authentication when performing communication while using the Internet as a communication network, encrypt communication information, and exchange data, thereby exchanging private lines. Confidentiality comparable to can be secured. In the first embodiment, since data transmitted via the Internet is not encrypted, there is a concern about leakage and tampering of communication information, but this embodiment prevents this and ensures confidentiality. This is a more realistic embodiment.
[0033]
【The invention's effect】
According to the present invention, even when load modules are developed by other companies, when the load module of the software delivery destination (order source) is updated, the latest load module is automatically distributed. Therefore, it is possible to obtain an environment in which function confirmation is always performed using the latest load module.
In addition, update information on load modules developed by other companies can be easily viewed on a WWW server (homepage).
[0034]
It also prevents mistakes such as modifying old version source files.
Furthermore, the source file (text information) may be falsified by a malicious third party by using a network based on the Internet, but delivered to the software development side (modification source). Since the difference information taken on both sides is matched, falsification can be prevented.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a first embodiment of a load module delivery mechanism in a software development system according to the present invention.
FIG. 2 is a block diagram showing an embodiment of a mechanism of source file delivery and version management in the software development system according to the present invention.
FIG. 3 is a flowchart showing an operation of a load module delivery mechanism.
FIG. 4 is a flowchart showing the operation of a source file delivery and version management mechanism.
FIG. 5 is a configuration diagram showing update information of a load module.
FIG. 6 is a block diagram showing a second embodiment of a load module delivery mechanism in the software development system according to the present invention.
[Explanation of symbols]
10 Software delivery destination 11 Load module A
12 Automatic distribution program 13 Load module update information 14 Load module A (A)
15 Load module B (A)
16 Load module C (A)
17 WWW server 18 Management server 19, 19A, 19B, 19C Firewall with VPN function 20 Software development company A
30 Software Development Company B
40 Software development company C
21 Source file A
22 Source file A '
23 Difference information (A'-A)
24 Version control program 25 Source file A
26 Source file A '
27 Difference information (AA ′)
100 network

Claims (6)

A software development orderer orders different software developments for multiple software development devices, and each software development device delivers the developed software as a load module to the orderer via the network. In a software development system that distributes delivered load modules to each software development device via the network,
Registration means for creating and registering information on the load module delivered from each software development device;
A distribution unit that distributes a corresponding load module to each software development device when it is detected that the information registered in the registration unit is updated ;
The software development device corrects the source file of the latest software developed, delivers the corrected source file to the ordering source, and also provides first difference information between the corrected source file and the source file before correction. Acquired,
The ordering party obtains second difference information between the new source file delivered and the source file delivered and registered before the modification,
A software development system, wherein the first difference information and the second difference information are compared and the ordering party officially registers the new source file when they match .   The software development system according to claim 1, wherein the software development apparatus performs an operation check test of the developed load module and the load module distributed from the orderer as necessary.   The software development system according to claim 1, wherein the software development apparatus is capable of browsing registration contents of the registration means.   The software development system according to claim 1, wherein the distribution is performed in a predetermined time zone. The software development device is characterized in that an operation check test is performed using the corrected source file, the corrected source file is delivered to the ordering party when there is no abnormality, and further corrected when there is an abnormality. The software development system according to claim 1 .   2. The software development system according to claim 1, wherein the ordering party and the software development apparatus communicate encrypted information via the network.

Images