JPS62271019A - Software development system - Google Patents

Abstract

PURPOSE:To attain a software development system that can always secure the coincidence of the editions and contents between a development load module and a work module, by adding a module plate monitor and a down-loader to a computer for development of software. CONSTITUTION:A module edition monitor 16 decides the coincidence of the editions between a load module 8 of a software developing computer 1 and a load module 31 of a work station 2. If no coincidence is obtained between both modules, the monitor 16 gives a warning to a station 2 and starts a down- loader 17. When coincidence is obtained, the monitor 16 reads the file capacities of both modules out of a capacity table. When no coincidence obtained, down- loader 17 is started. The station 2 proceeds to an integrated test process if no warning is produced since the module 31 is the latest edition. While the module 31 is replaced by the loader 17 if a warning is produced.

Description

[Detailed Description of the Invention] 3. Detailed Description of the Invention [Field of Industrial Application] This invention relates to a software development system that uses a large-sized computer as a software development computer to develop software for use in work stages. It is something.

[Conventional technology]

Conventional systems of this type include a software development system in which a software development computer and a workstation, which is a software development target machine, are offline, and a software development system in which the software development computer and workstation are connected online. There are two types of software development systems that do not provide a function to monitor and check the content of each software load module and the identity of software versions in real time.

The eleventh factor is the configuration diagram of the former offline software development system, where 1 is a software development computer consisting of one large child computer used as a software development machine, and 2 is a workpiece that is the target machine for software development. It is a station. Here (=Software development calculation ml and workstation 2 are not connected by a communication network.In addition, software development calculation aCt is also required for software development: operating system 3, compiler 4, linker 5, debugger 6) , a utility 7 software tool is installed, and a load module 31 for the workstation 2 is created using this software tool.

The load module 8 created by the software development computer 1 cannot be operated on the workstation 2 as it is, so it must be stored manually in the secondary storage device of the flexible disk 9, magnetic tape 10, or magnetic disk 11. Attach it to work stage Mushroom 2.

FIG. 12 is a configuration diagram of the latter online software development system. In the figure, software development calculations all are connected to a workstation 2, which is a software development target machine, via a communication line 12. . Software development calculation Ml includes operating system 3, compiler 4, linker 5, debugger 6, and utility 7, which are essential for software development.
The load module 31 for the work stage controller 2 is created using these software tools. Software development total J
! The load module 8 created on the machine 1 is temporarily stored in the secondary storage device of the flexible disk 9 or the magnetic tape 10 or the magnetic disk 11 of the software development computer 1, but it is stored on the online terminal installed on the workstation 2. Using the device emulator 13, this workstation 2 is converted into a software development computer 1.
The load module 8 created by the software development calculation m1 is transferred to the online terminal device 14 of the workstation 2 via the communication line network 12 to the file t6.The operation will now be described.

When developing software for the workstation 2 using the offline software development apparatus shown in FIG. 11, a developer sits in front of the online terminal device 14 connected to the software development computer 1, Use the editor, which is one of the elements in 7. As shown in FIG. 2, a software source module created using this utility 7 is converted into a target module and a load module 8 using a compiler 4 and a linker 5. Although this load module 8 cannot be comprehensively tested on the software development computer 1, it can be unit tested using the debugger 6. When a problem occurs during a unit test, the problem is repaired on the software development computer 1. On the other hand, when the unit test is completed, the development load module 8 is manually loaded into the work stage 2 using a secondary storage medium such as the flexible disk 9, magnetic tape 10, or magnetic disk 11. Ru. The development load module 31 loaded onto the workstation 2 performs a comprehensive test under the operating system 30 of the workstation 2.

When developing software for the workstation 2 using the online software development apparatus shown in FIG. Use the editor, which is one of the elements in 7. Second
As shown in the figure, a software source module created using this utility 7 is converted into a target module and a load module 8 using a compiler 4 and a linker 5. Although this a-domogère 8 cannot be comprehensively tested on the software development computer 1, it can be unit tested using the debugger 6. When a problem occurs in a unit test, the problem is repaired on the software development computer 1. On the other hand, after the unit test is completed, the development worker sits in front of the workstation 2 and emulates the workstation 2 into an online terminal device. Next, the development worker transfers the development load module 8 stored on the flexible disk 9, magnetic tape 10, or magnetic disk 11 of the software development computer 1 to the flexible disk 32 or the workstation 2 via the communication line 12. The file is transferred to the magnetic tape 33 or magnetic disk 34. After that, the development worker uses the software development computer 1
After completing the unit test on the work station 1, a comprehensive test can be immediately performed on the work station 2.

[Problem that the invention seeks to solve]

Since the conventional offline software development system is configured as described above, the load module 8 created by the software development computer 1 must be manually installed into the workstation run 2, which is the development target machine.

Therefore, there was a problem that software development efficiency was not improved. Furthermore, the load module 8 of the software development calculation a1 and the load module 3 of the workstation 2
There were problems such as the consistency of the content and version of 1 was not guaranteed.

On the other hand, since the conventional online software development device has two configurations as described above, the load module 8 created by the software development computer 1 has to be converted into an online terminal device by the workstation 2 using the emulator 13. , since this load module 8 is not transferred from the software development computer 1, it is shown in Figure @11 (:
Similar to the offline software development system shown above, there is a problem in that the contents and versions of the load module 8 of the software development machine #1 and the load module 31 of the workstation 2 are not guaranteed to be identical.

Furthermore, when there are multiple workstations 2, there is a problem in that the contents and versions of the load modules 31 cannot be guaranteed to be identical between the individual workstations 2.

In addition, in both offline and online software development systems, development workers must be aware of the differences in content and versions of the load module 8 of the software development computer 1 and the load module 1-31 of the workstation 2. There were problems that could not be discovered without further investigation. That is, there was a problem in that the task of ensuring the sameness of the contents and versions of the load modules 8 and 31 was not automated.

This invention was made in order to solve such problems (2), and includes the development load module 8 of the software development computer 1 and the word module 3 of the workstation run 2.
The purpose of this invention is to obtain a software development system that can always guarantee the sameness of contents as version 1.

[Means for solving problems]

The software development system according to the present invention includes a module version monitor that monitors in real time the version and content identity of a software load module and a workstation load module, and as a result of monitoring by this module version monitor, The present invention is characterized by comprising a downloader that downloads the latest load module to the workstation when it is found that the version and contents do not match.

[Effect]

The module version monitor according to the present invention visually detects differences between the contents and versions of the load module 8 of the software development machine 1 and the load module 31 of the workstation 2, and detects the existence of the differences. When the download program #m load module 8 is automatically transferred from the software development computer 1 to the workstation run 2 (
= By downloading, the contents and versions of each load module 8 and 31 are guaranteed to be the same.

〔Example〕

An embodiment of the present invention will be described below with reference to the drawings. 1st
In the figure, 1 is a software development computer consisting of a large computer used as a software development machine, 2 is a workstation computer that is a target machine for software development, and 15 is an online terminal emulator 3.
6, a software development calculator 8!1, a workstation 2, and a gateway processor 15 are all connected to a communication network 12. Software development calculation a1 is a module version monitor that monitors the version and contents of the developed load module 8 in addition to the operating system 3, compiler 4, linker 5, debugger 6, and utility 7 that are essential for software development. 16. Development load module 8
The software development computer 1 is equipped with a downloader 17 that downloads the software from the software development computer 1 to the workstation 2 via the communication line 12. The load module 8 created by the software development computer 1 is first stored in the secondary storage device of the flexible disk 9 or magnetic tape 10 or magnetic disk 11 of the software development computer 1, and then transferred to the workstation 2 by the downloader 17.
flexible disk device 32 or magnetic tape 33
Alternatively, the data is transferred to the magnetic disk 34.

Next: The second operation will be explained.

When developing software for work stage 2 under the software development system shown in FIG. The user sits in front of the workstation 2 running the emulator 36 and uses the editor, which is one of the elements in the utility 7. As shown in FIG. 2 or 3, a software source module created using this utility 7 is converted into a target module and a load module 8 using a compiler 4 and a linker 5. Although this load module 8 cannot be comprehensively tested on the software development computer 1, it can be unit tested using the debugger 6.

Figure 2 shows the processing flow up to the unit test when the development worker uses the online terminal device 14.
The figure shows a processing flow up to a unit test when a development worker uses the workstation 2 running the emulator 36 on the gateway processor 15.

If a problem occurs during a unit test, fix the problem on the software development calculation al.

Next, the operation of the modular monitor 16 will be explained.

As shown in FIG. 4, the module version monitor 16 is first activated at the same time as the software development computer 1 is activated, and is constantly in operation until the software development calculation a1 completes its operation. The module version monitor 16 then selects the work stage number 2 to be monitored. next,
The operating systems 3 and 30 generate and manage file information tables 18 and 29 shown in FIG. In FIG. 5, 19 is the file name, 20 is the creation date, 21 is the update date, 22 is the version name, 23 is the file capacity, and 24 is the file organization method. Next, the version of the development load module 8 created on the development machine 1, that is, the creation date 20, update date 21, and version name 22 are read. Next, calculations for software development! The versions of development load modules 8 and 31 created in s1 are on software development computer 1.
and workstation 2 are matched. If the versions do not match, a warning message 25 similar to the one shown in Figure 6 will be displayed on the workstation 2.
and starts the downloader 17. On the other hand, if the versions match, the file capacities 23 of the load modules 8 and 31 are read from the file information table. Next, it is determined whether the file capacities 23 of the load modules 8 and 31 match between the software development computer 1 and the workstation run 2. File capacity 23
If they do not match, a warning message 25 is sent to the workstation 2 and the downloader 17 is activated.

If the file capacities 23 match, then the load module 8 on the software development computer 1 side and the load module 31 on the workstation 2 side are read respectively, and it is determined whether their contents are the same. If the contents are different, a warning message 2 is sent to the relevant workstation 2.
5 and start the downloader. On the other hand, if the contents are the same, the next workstation 2 to be version monitored is selected and the same process as above is repeated. Further, after the downloader 17 has been started, the next workstation 2 to be viewed is selected and the same process as described above is repeated.

Next, the operation when the workstation 2 is started will be explained. As shown in Figure @7, workstation 2
When activated, it is first determined whether or not a warning message 25 has been sent from the module monitor 16. If there is no warning, the development load module 31 is the latest version, and the process proceeds to a comprehensive test of the load module 31. On the other hand, if a warning exists, a window with a warning message 25 is displayed on the workstation 2.

Subsequently, the load module 31 of the workstation 2 is updated by the downloader 17 started on the software development computer 1. Next, the process proceeds to a comprehensive test of the Lord Mosinir 31. Determine whether or not a problem has occurred in the comprehensive test results. When a problem occurs, the emulator 36 of the gateway processor 15 is activated, and the software development computer 1 repairs the problem in the load module '8. After this, the flow will be as shown in Figure @3.

Next, the operation of the downloader 17 will be explained. 8th
As shown in the figure, when the downloader 17 starts, it then reads the development load module 8 from the development manno 1. Next, the destination workstation 2 is specified and the a-Domojir 8 is sent.

Next, the interaction between the operating system 3, the mosier version monitor 16, and the downloader 17 will be explained.

In the software development calculation m1, the operating system 3, compiler 4, linker 5, Tehugger 6, utility 7, module monitor 16, and downloader 17 each exist as a software unit that acquires a central processing unit, that is, a task, and operate. do. As shown in FIG. 9, the mosier version monitor 16 is a resident task that always operates as a child task of the operating system 3 task. When the module version monitor 16 detects a difference between the versions and contents of the development load modules 8 and 31 (2.
It is dynamically generated as a child task of 6.

On the workstation 2, a substitute task is generated in response to task generation as described above. The operating system 30 of the workstation 2 exists as a single task, but it has a proxy task 26 for communicating with the task of the module monitor 16 on the software development computer 1 and a proxy task 26 for communicating with the task of the downloader 17. Task 27 exists. The module monitor substitute task 26 is a resident task that always exists as a child task of the operating 30 task of the workstation 2. The downloader proxy task 27 is dynamically generated as a child task of the operating 30 task of the workstation 2.

On the gateway processor 15, an operating system 35 and an emulator 36 exist and operate as tasks. As shown in FIG. 9, the emulator 36 task is a resident task that always operates as a child task of the operating system 35 task.

On the workstation 2, in addition to the above-mentioned proxy tasks 26 and 27, there is a proxy task 28 for communicating with the task of the emulator 36 of the gateway processor 15. The operator's substitute task 28 is dynamically generated as a child task of the task of the operating system 30 of the workstation 2.

Next, communication operations between each task on the software development computer 1 and each substitute task on the workstation 2 will be explained. Figure 10 (a), (b),
(C) (-The flow of communication is shown below. First, the task of the module monitor 16 is to set one workstation 2 to be monitored and send a 1nquiry request via the communication line 12. If workstation 2 is present, delegate task 26 returns its 1nquir)l result. In other words, the task of the mosier version monitor 16 is to read the file t'ft information table 18 of the software development computer 1, and read the file information table 29 of the workstation 2! It is transmitted via the communication line network 12. When the proxy task 26 receives this Yasugi, the workstation 2's file information table'l
9 Read and return the result to software development computer 1. Next, when the task of the module version monitor 16 receives the read completion notification of the file information table 29, it compares the contents of the respective file information tables 18 and 29. If the contents do not match, the task of the module version monitor 16 opens the file of the load module 8 of the software r'A issuing computer 1.

Next (2) The task of the Mosier version monitor 16 sends a pen request to the file of the Load Mosier version 31 of the workstation 2 via the communication line 12. When the agent task 26 receives this request, the workstation 2 opens the file of the load module 31 and returns the result to the software development computer 1. Next (=, the task of the software version monitor 16 receives the file open completion notification of this load module 31, and returns the result to the software development computer 1. Development calculation a1 load module 8
read L, then read 'I' record of load module 31 of workstation 2.
The J request is sent via the communication line network 12. Acting task 26
When receiving this request, it reads the file record of the load module 31 of the workstation 2 and returns the result to the software development computer 1. Next, upon receiving the record read completion notification of this load module 31, the task of the module version monitor 16 compares the record contents of each load module 8 and 31. Next, the module monitor 16 task sends a close request to the file in the load module 31 of the workstation 2 via the communication line 1f412. When the substitute task 26 receives this request, the file of the load module 31 of the workstation 2 is
ione l, and returns the result to the development machine 1.

Next, when the record contents of the a-to modules 8 and 31 do not match each other, the task of the module monitor 16 creates a notice message 25 and subsequently sends a create request for the window of the workstation 2. It is transmitted via the line network 12.

When the proxy task 26 receives this request, it creates a window on the workstation 2 and returns the result to the development machine 1. Next(:, When the task of the module version monitor 16 receives this window create completion notification, it subsequently sends a request to the communication line network 1 to display the warning message 25 on the window of the workstation 2.
Send via 2. When the proxy task 26 receives this request, it displays a warning message 25 on the window of the workstation 2, and returns the result to the software development manager JHII. At this time, a task for the downloader 17 and its substitute task 27 are generated. Next, upon receiving this display completion notification, the downloader 17 task sends a file delete request to the load module 31 of the workstation 2 via the communication network 12. When the proxy task 27 receives this request, it deletes the file in the load module 31 of the workstation 2.
Return the results of step 7 to software development calculation 8!1. Next, the task of the downloader 17 is to delete this
Upon receiving the e-completion notification, it sends a request to create the file of the load module 31 to the workstation 2 via the communication network 12. The substitute task 27 receives this request, creates the file of the load module 31 on the workstation 2, and returns the result to the development machine 1. Next, the downloader 17 task receives this create completion notification. Then, it reads a record from the file in the load module 8 of the development machine 1 and sends a write request for that record to the workstation 2 via the communication line 12. Writes a record to the file of module 31 and returns the result to development machine 1. Next, downloader 1
When task 7 receives this write completion notification, it loads the file clog in load module 8 on development machine 1.
se L, then sends a close request for the file of the a-to module 31 of the workstation 2 to the communication line network 12.
Send via. The substitute task 27 executes C165e on the file of the load module 31 of the workstation 2, and uses the result for software development! Return to aml.

Next, upon receiving this close completion notification, the downloader 17 task transmits a window delete request for the warning message 25 on the workstation 2 via the communication line network 12 . The substitute task 27 deletes the window of the warning message 25 on the workstation 2.
ete and return the delete result to the software development computer 1. Next, upon receiving this delete completion notification, the task of the downloader 17 disappears. At the same time, the substitute task 27 on the workstation 2 also disappears. Next (;, When the task of the module version monitor 16 detects the disappearance of the task of the downloader 17, its operation is initialized and the same process as described above is repeated.

Incidentally, in the above embodiment, a large-sized computer is used as the software development computer 1, but a small-sized computer, a medium-sized computer, or a very large-sized computer may also be used as the software development computer 1. Further, in the above embodiment, the workstation 2 is set as the development target machine, but a terminal device or a personal computer may be used as the workstation.

Further, in the above embodiment, the case where the software development calculation ml and the workstation 2 are connected via the communication line network 12 has been explained, but the case where the connection is made via a public line network or a local area network is also possible. It has a similar effect.

〔Effect of the invention〕

As described above, the present invention includes a remocher version monitor that monitors in real time the identity of the version and content of a software load module and a workstation load module, and a remocher version monitor that monitors the version and content of a software load module and a workstation load module as a result of monitoring by this module version monitor. Since it is equipped with a downloader that downloads the latest load module to the workstation when a mismatch is found, the version and contents of each load module 8 and 31 are guaranteed to be the same, and productivity and reliability are improved. This has the effect of providing a high quality software development environment.

[Brief explanation of drawings]

Figure 1 is a configuration diagram showing a software development system that is an embodiment of the present invention, and Figure 2 is a diagram showing load module creation and unit test development using a conventional software development computer 1 and online terminal device 14. Work flow chart,
FIG. 3 is a flowchart of the development work of load module creation and unit test when using the software development needle W:ml, gateway processor 15, and workstation 2, showing one embodiment of this invention.The fourth factor is this invention. A flowchart showing the operation of the modular monitor 16, which is an embodiment of
FIG. 5 is a configuration diagram of the file information table 18 which is an embodiment of the present invention, FIG. 6 is a configuration diagram of the window of the warning message 25 on the workstation 2 which is an embodiment of the invention, and FIG. A flowchart showing the operation of the workstation 2 after startup, which is an embodiment of the present invention, Figure @8 is a flowchart showing the operation of the downloader 17, which is an embodiment of the invention, and Figure 9 is an embodiment of the invention. A task configuration diagram on the software development computer 1, workstation 2, and gateway processor 15, FIG. 10(a)
, (b) and (C) are flowcharts showing communication exchanges between the tasks of the module monitor 16 and downloader 17 and their proxy tasks 26 and 27, which are one embodiment of the present invention, and FIG. FIG. 12 is a block diagram of a conventional online software development apparatus. In the figure, 1 is a software development computer, 2 is a workstation, 8 is a development load module, 12 is a communication line network, 13 is an emulator, 14 is an online terminal device, 15 is a gateway processor, 16 is a module version monitor, 17 3 is a town loader, and 31 is a workstation load module. Note that the same reference numerals in each figure indicate the same or corresponding parts.

Claims (1)

[Claims] A software development computer, a workstation that uses software created with the software development computer, and an emulator that operates the workstation as a terminal device and creates software with the software development computer. A software development system in which a gateway processor equipped with The modular version monitor and the results of monitoring by this modular version monitor,
A software development system comprising: a downloader that downloads the latest load module to a workstation when it is found that the version and contents do not match.