Method and apparatus for designing computer programs for business

Abstract: Without using a host computer, a computer program for object business processing is efficiently developed in a work station. A data flowchart edit unit (111), a system flowchart generation unit (122), and a program specification generation unit (124) are provided in a distributed processor (10) such as a work station. First of all, edit of a data flowchart of business processing which becomes the object of software development is performed. Data items extracted at this time are entered into a data item dictionary (103) so that they may be handed over and used as input information of a data analysis unit (113). As for functions extracted in the edit process of the data flowchart, they are successively generated as a system flowchart (102) and program specifications (104). Finally, a source program (107) is generated.

Description: The present invention relates to a method and apparatus for designing a computer program for business processing without the intervention of a host computer under the support consistently given over the entire process by a distributed computer device such as a work station of a distributed processing system. Development of a computer program for business processing is typically executed in the following procedure. First of all, a program designer analyzes contents of object business processing, and investigates thoroughly unit functions forming the business and data flow between those functions. Analysis such as normalization of data items is then conducted by using an analysis tool. Data items are stored in a data item dictionary so that data may be consistently in all stages of the ensuing development processes. Further, detailed design is performed for processing, files, and data bases required for unit functions. Further, specifications of a program for implementing necessary processing are clarified, and a source program is produced on the basis of it. Conventionally, there has been a development support tool for supporting the development of such software, i.e., a program, representing the development object business in the form of drawing, and advancing processing in an interactive manner. There also has been a development support tool for representing processing, files, and data bases required for necessary functions in the form of drawing and for defining them in an interactive manner. They individually support respective processes of the above described software development. They accurately represent intention of the program designer by visually representing processing and specifications required for the object business, and support to exclude the redundancy of data items and maintain the consistency. Thus they contribute to improvement of software productivity. In U.S. Patent No. 5,185,867 issued to Kishio Ito on February 9, 1993, a method and an apparatus for automatically generating software specifications relating to the technical field of the present invention are disclosed. Conventional development support tools for business processing program will now be described. Software production techniques are disclosed in "HITACHI REVIEW", Vol. 68, May 1986, No. 5, Serial No. 772, pp. 29-42 and "HITACHI REVIEW", Vol. 70, February 1987, No. 2, Serial No. 793, pp. 7-14. The Automatic programming systems are disclosed in Japanese Patent Applications unexamined publication number JP-A-4-172529 published on June 19, 1992. Conventional development support tools had individual support functions. In case the entire program was to be designed in a distributed processing computer system, therefore, a development support tool on the host computer side was separated from a development support tool on the work station side. Consequently, the program was designed while data were being transferred between the host computer and the work station. In the conventional program design, data transfer processing frequently occurred between the host computer and the work station, and the load of the host computer became excessively large, resulting in a hindrance to other business. Or, on the contrary, processing had to be advanced according to the business plan of the host computer, and hence the development work could not be conducted efficiently. The conventional program design had these problems. Further, program development goes through respective processes so that a preceding process may be continued to its succeeding process. In the above described conventional development support tool, however, a troublesome procedure was needed to successively hand over definition information defined in a certain process to the next process. In addition, smooth transfer to the work of the next process was not considered. This resulted in a problem that development work could not be advanced efficiently. Further, data items extracted on the basis of analysis of the object business could not be used as the input of data analysis as they were. This resulted in a problem that efficient arrangement of data items in conformity with analysis of actual business could not be conducted. The present invention seeks to provide a program design method and apparatus which permits successively handing over of definition information between processes from a preceding process to its succeeding process and consistently conducting development of a program using a distributed computer independently of a host computer. An article entitled "A Specification Compiler for Business Application: SPACE" by M. Harada published in Proceedings From The 11th Annual International Computer Software & Applications Conference, 7 October 1987, Tokyo, at pages 171 to 180, discussed business program application developments. It proposed a method for designing a computer program for business processing in a distributed arrangement of computer workstations. The workstation displayed design windows containing design patterns from which the user could select appropriate ones to compose a design specification. According to a first aspect of the invention there is provided a method for designing a computer program for business processing with support from a distributed computer such as a workstation in a distributed processing system; wherein: said method comprises the steps of: producing definition of a plurality of unit functions forming said business and a data flowchart between said unit functions on the basis of data concerning business processing inputted to said computer by an operator; extracting a data item on the basis of said data flowchart by using a data analysis tool possessed by said computer and storing the data item in storage means; producing a system flowchart on the basis of said data flowchart by using a system flow generation tool possessed by said computer; producing program specifications on the basis of said system flowchart by using a program specification generation tool possessed by said computer; and producing a source program for said business processing, on the basis of the data item obtained from said storage means and said program specifications, by using a source program generation tool possessed by said computer. According to a second aspect of the invention there is provided a distributed computer device such as a workstation in a distributed processing system for supporting design of a computer program for business processing; wherein: said distributed computer device comprises: means for receiving data concerning business processing inputted by an operator and for producing definition of a plurality of unit functions forming said business and a data flowchart between said unit functions; system flow generation tool means for producing a system flowchart on the basis of said data flowchart; program specification generation tool means for producing program specifications on the basis of said system flowchart; data analysis tool means for extracting a data item on the basis of said data flowchart; storage means for storing said data item; and source program generation tool means for producing a source program for said business processing on the basis of the data item obtained from the storage means and said program specifications. The present invention may make it possible to adopt data items extracted by the analysis of the actual business as input of data analysis without modifying them and develop a program consistently on the basis of it. Thus, using the present invention, a processing program of object business may be developed in a distributed processor such as a workstation independently of a host computer. Definition information between processes can be successively and smoothly handed over from a preceding process to its succeeding process. Program development can be conducted consistently. Further, only data items extracted in conformity with object business can be analysed efficiently. There is no redundant work due to data analysis, so that program production in conformity with an object of the business becomes possible. As a result, there is generated an environment in which consistent program production can be efficiently conducted. System development capable of coping with an increase in backlog caused by an increase in system scale and a lack of personal becomes possible. An embodiment of the invention will now be described in detail, by way of example, with reference to the accompanying drawings, in which: Fig. 1 is a system configuration diagram of a work station for designing a business processing program according to the present invention; Fig. 2 is a diagram showing contents of an external storage device connected to the work station; Fig. 3 shows a flowchart and a data flowchart of design of a business processing program according to the present invention; Fig. 4 is a data flowchart; Fig. 5 is a system flowchart; Fig. 6 shows an example of definition information defined by program specifications; Fig. 7 shows an example of definition information defined by file specifications; Fig. 8 shows an example of definition information defined by form specifications; and Fig. 9 is a production process drawing of synthesis processing of a source program. The present invention will hereafter be described in detail on the basis of an illustrated embodiment. Fig. 1 is a block diagram showing an embodiment of system configuration of a work station for executing a program design method according to the present invention. The work station is formed by a processor 10, an external storage device 11 including a magnetic disk device, an input device 12, and an output device 13 such as a printer. Among them, the processor 10 includes a data flowchart edit unit 111, a system flowchart edit unit 112, a data analysis unit 113, a program specification edit unit 114, a file specification edit unit 115, a form specification edit unit 116, a source program edit unit 117, a system flowchart generation unit 122, a data transfer unit 123, a program specification generation unit 124, a file specification generation unit 125, a form specification generation unit 126, and a source program generation unit 127. Further, as shown in Fig. 2, the external storage device 11 includes a data flowchart file 101, a system flowchart file 102, a data item dictionary 103, a program specification file 104, a file specification file 105, a form specification file 106, and a source program file 107. In the present invention, data exchange with the host computer is unnecessary. A program for business can be designed in the work station alone which is a distributed computer. Fig. 3 shows the flow of processing and data of consistent program production in the work station shown in Figs. 1 and 2. The flow represented by the diagram of Fig. 3 starts from data flowchart edit for analyzing object business of software development and preparing a business design. Definition information is handed over and works of respective production processes are done. Thereafter, a source program is generated finally. The diagram of Fig. 3 represents the flow to this point. Production processes will hereafter be described one after another along the flow. Fig. 4 shows an example of the data flowchart 101D (where D means data) for defining necessary functions and data flow between functions with respect to object business processing of software development and for designing a business processing program. A symbol 201 in this data flowchart represents one of unit functions forming the business processing. The unit function 201 contains information such as unit business identification (ID) 211 and a function name 212. An illustrated arrow symbol 202 represents a data flow flowing between functions. The data flow 202 contains information such as at least one data item name 221 and attributes 222 associated with respective data item names. Further, an illustrated symbol 203 represents a medium for storing data. The medium 203 contains information such as at least one data item name and attributes associated with respective data item names. A person who edits the data flowchart 101D makes an analysis of contents of object business processing. On the basis of the result of the analysis, the person defines data 221 and 222 respectively of business ID and function name in an interactive manner by using the input device 12 and stores them in the data flowchart file 101. If in this case a completely new program is to be developed, for example, there are no data stored beforehand and hence the function name 212 and the data item name 221 are defined by inputting them cach time. Furthermore, if data already stored are present in the data item dictionary 103, the data in the dictionary can be displayed on the screen and taken into the data flowchart in an interactive manner. if at this time a data item name 221, for example, has been taken in, information such as an attribute 222 associated with that data item name 221 is also taken in automatically. As for each of defined data item names 221 contained in data flows included in the data flowchart 101D by at least one, it is inputted to the data analysis unit 113 by the data transfer unit 123 which transfers data to the next production process. The data analysis unit 113 takes over information and exercises functions such as normalization (unification of names and unification of the number of columns) of the data item name 221. The normalized data are used to produce the data item dictionary 103. When data are to be handed over to the next production process, its start is made by predetermined manipulation. That is to say, all of contained data items may be handed over in a lump by starting the data analysis unit 113 during edit of the data flowchart 101D. Alternatively, all data items contained in the data flowchart 101D may be handed over in a lump by terminating all edit of the data flowchart 101D and then starting the data analysis unit 113 with respect to the data flowchart. When data items are to be handed over to the next production process, processing is thus advanced to the data analysis unit 113 simultaneously. Thereby the worker can smoothly advance to interactive data analysis work. As for functions which are contained in the data flowchart 101D by at least one, internal processing for each of them must be further defined. By using the system flowchart generation unit 122 for generating the frame of specifications of the next production process which is one feature of the present invention, therefore, the business ID 211 and the function name 212 are taken over and the frame of the system flowchart 102D (a semifinished system flowchart), which is work contents of the next production process, is automatically generated and stored in the system flowchart file 102. In starting the system flowchart generation unit 122 in this case, the symbol 201 may be selected beforehand in the data flowchart 101D and the system flowchart generation unit 122 may be started. Alternatively, the system flowchart generation unit 122 may be started after edit of the data flowchart 101D has been terminated once and functions defined in the data flowchart may be processed in a lump. If the frame of the system flowchart 102D has been automatically generated, processing advances to edit of the system flowchart which is the next production process. The advance in this case may be made by predetermined manipulation. That is to say, the advance may be made by selecting a symbol 201 representing processing included in the data flowchart 101D and starting the system flowchart edit unit 112 with respect to the symbol. Alternatively, the frame of the system flowchart 102D automatically generated by the above described prodedure may be selected after the edit of the data flowchart 101D has been finished once and the system flowchart edit unit 112 may be started with respect to the frame. As for the method for automatically generating the frame of the system flowchart 102D, the method used in the conventional development tool can be applied thereto as it is. Therefore, its description will be omitted. Cooperation with the host computer becomes unnecessary by thus directly advancing to generation of the frame of the system flowchart 102D by predetermined manipulation after the edit of the data flowchart 101D. Fig. 5 shows an example of the system flowchart 102 for concretely defining processing contents with respect to one function defined in the data flowchart 101D, subdividing processing specifications of business while taking a program as the unit, and representing flow between individual programs. Strings of characters 211 and 212 included in this system flowchart 102D are respectively the business ID 211 and function name 212 handed over from the data flowchart 101D by automatic generation. Furthermore, illustrated symbols 301 and 303 are described to represent programs for implementing functions. Each of the symbols 301 and 303 contains a program name 311, a pattern name 312, a comment 313, a name 314 of a data base to be used, and a name 315 of a file to be used. A symbol 302 is described to represent a file used as the input and output of a program. The symbol 302 contains a file name 321, a file organization information 322, and a comment 323. Furthermore, a symbol 304 is described to represent a form outputted by the program. The symbol 304 contains a form name 331 and a medium classification 332. For each of programs, files and forms included in the system flowchart 102D, a further detailed definition must be formulated. In the same way as the above described case where the system flowchart is generated for each function included in the data flowchart 101D, therefore, contained information for each of the programs, files and forms is handed over and the frame of specifications of the next production process is generated. As for program specifications in this case, the program specification generation unit 124 for generating program specifications is used. As for file specifications, the file specification generation unit 125 for generating file specifications is used. As for form specifications, the form specification generation unit 126 for generating form specifications is used. In using each of the generation units 124, 125 and 126, a symbol included in the system flowchart 102D may be selected and a start may be made for the symbol. Alternatively, the generation units 124, 125 and 126 may be started in a lump for the program, file and form defined in the system flowchart 102D during edit of the system flowchart. Further alternatively, it is also possible to finish edit of the system flowchart 102D once and then make a start for the program, file and form, which have been defined in the system flowchart, in a lump. If the program specifications 104D, the file specifications 105D, and the form specifications 106D have been generated respectively, an advance is made to respective edit units 114, 115 and 116 forming the next production process. An advance in this case can be made in the same way as the above described advance from the edit of the data flowchart 101D to the edit of the system flowchart 102D. That is to say, the advance may be made by selecting each symbol included in the system flowchart 102D and starting an edit unit associated with the symbol. Alternatively, the frame of each set of specifications automatically generated may be selected after the edit of the system flowchart 102D has been finished once and the edit unit associated with the frame may be started. Fig. 6 shows an example of definition information, which is defined by the program specifications 104D, in the form of a table. These pieces of information are defined by the input device 12 in an interactive manner. However, some pieces of information are taken over from the system flowchart 102D which has been defined by the preceding production process. By making up for remaining information pieces, therefore, edit of the program specifications 104D is completed. As already described in the description of edit of the data flowchart 101D, information already stored in the data item dictionary 103 can be used. In the program specifications 104D, the name of specifications containing description of specifications of the file, form, and data base concerning the program is also described. Fig. 7 shows an example of definition information, which is defined by the file specifications 105D, in the form of a table. These pieces of information are defined by the input device 12 in an interactive manner. However, some pieces of information are taken over from the system flowchart 102D which has been defined by the preceding production process. By making up for remaining information pieces, therefore, edit of the file specifications 105D is completed. As already described in the description of edit of the data flowchart 101D, information already stored in the data item dictionary 103 can be used. Fig. 8 shows an example of definition information, which is defined by the form specifications 106D, in the form of a table. These pieces of information are defined by the input device 12 in an interactive manner. However, some pieces of information are taken over from the system flowchart 102D which has been defined by the preceding production process. By making up for remaining information pieces, therefore, edit of the form specifications 106D is completed. As already described in the description of edit of the data flowchart 101D, information already stored in the data item dictionary 103 can be used. If definition of specifications concerning one program has thus been completed thoroughly, names of specifications concerning the program are already described in the program specifications 104D. Therefore, a source program is automatically generated by starting the source program generation unit 127 from the edit screen of the program specifications 104D, or by finishing the edit of the program specifications, then selecting that program specifications 104D, and starting the generation unit 127. That is to say, the source program generation unit 127 refers to names of specifications described in the program specifications 104D and quotes the specifications. As for names of data items contained in the specifications, the unit 127 quotes the data item dictionary 103. By thus giving body and substance to prepared framework of the source program, the source program generation unit 127 automatically generates the required source program. Details of processing conducted in each production process of the flowchart of Fig. 3 will now be described. First of all, the production process for generating a system flowchart 102D from the data flow chart 101D will now be described. For each of unit functions 201 in the data flowchart 101D, one sytem flowchart associated therewith is produced. At this time, the business ID 211 and function name 212 defined in the data flowchart 101D are used as the title of the system flowchart 102D. In the production process for generating the system flowchart 102D, a picture for interactive processing between the operator and the processor 10 is displayed on the screen of the input device 12. For example, some names of processing patterns of a certain number of different standard programs prepared beforehand are displayed on the screen. By using the input device 12, the operator specifies suitable one out of those processing patterns. Furthermore, images urging the operator to input the input file name, output file name, reference file name, and form name are displayed. By using the input device 12, the operator specifies those information pieces. In the production process for generating file specifications 105D from the system flowchart 102D, corresponding file specifications 105D are generated for each of symbols 302 representing files included in the system flowchart 102D. A file name 321 defined in the system flowchart 102D is used as the title at the time of generation of file specifications. In the production process for generating form specifications 106D from the system flowchart 102D, a form name 331 is used in the same way as generation of file specifications. In the production process for generating program specifications 104D from the system flowchart 102D, the following information pieces are used as definition information of program specifications. Those information pieces include the processing pattern name selected at the time of generation of the system flowchart 102D, the input file name, output file name, reference file name, and form name inputted at the time of generation of the system flowchart 102D, and the input file name, output file name, reference file name, and form name defined at the time of edit of the system flowchart 102D. In the production process for generating a source program from the program specifications 104D, file specifications 105D, and form specifications 106D, the following processing procedure is executed. On the basis of the processing pattern name defined in the program specifications 104D, framework of a source program defined beforehand so as to be associated with the processing pattern is called from the file 104 and displayed on the screen. On the basis of the framework, the program is constructed in an interactive manner. A data item name defined in the file specifications 105D, a data item name defined in form specifications 106D, and their attributes (position of printing, the number of columns of printing, character size, and so on) are used to generate processing statements in the source program. On the basis of the program part name defined in the program specifications 104D, a source program defined beforehand so as to be associated with the part name is called from the file 107. Body and substance are given to the framework of the source program displayed on the screen. Fig. 9 is a production process diagram showing an example of program synthesis. Fig. 9 shows an example of a programming pattern expressed by COBOL language. A program specification defines pattern names, part names, definition specification and so on. The COBOL program is formed with some DIVISIONs. The combinations of the DIVISIONs are previously prepared as various patterns. In production of a source program, such patterns are used as the framework of the program. A source program is completed by giving body and substance to the framework. General processes are previously defined and registered to be used in program production. The process is expressed by COBOL language in PROCEDURE DIVISION. According to the information defined in the definition specification, definition statements are produced to be effectively used in actual programming. The definition statements are disposed in predetermined positions in the patterns. The file specification is expressed by COBOL language in ENVIRONMENT DIVISION. The record specification is expressed by COBOL language in DATA DIVISION. The table, screen and form specifications are expressed by COBOL language in WORKING-STORAGE SECTION in DATA DIVISION. The processing of data item dictionary is made in a same manner as the parts. The user (a programmer with COBOL language) can additionally express the other necessary processes with the additional coding. In accordance with the present invention as heretofore described, data flowchart generation means, system flowchart generation means, program specification generation means, and so on are provided in a distributed processor such as a work station. Functions and data items extracted through edit of the data flowchart which is analysis work of object business of software development are examined. As for functions needed for processing of business, there is generated such an environment that work can be advanced consistently while handing over definition data in production processes beginning from definition of the processing and ending at generation of a source program. As for data items, there is generated such an environment that the data item can be used at any time in consistent production process by handing over the data item to a data analysis unit and entering the data item in a data item dictionary. As a result, software development work can be done continuously and consistently in a distributed processor such as a work station. It thus becomes possible not only to improve the efficiency of software production, but also to consistently use data items extracted from the analysis of the object business as data items employed in respective production processes of that work. Therefore, it becomes possible to exclude the redundancy of work caused by doing separate work for extracting data items. As a result, efficient development of software fitting the purpose becomes possible.

Claims: A method for designing a computer program for business processing with support from a distributed computer such as a workstation in a distributed processing system; characterised in that: said method comprises the steps of: producing definition of a plurality of unit functions (201) forming said business and a data flowchart (101D) between said unit functions on the basis of data concerning business processing inputted to said computer (10) by an operator (12); extracting a data item on the basis of said data flowchart by using a data analysis tool (113) possessed by said computer (10) and storing the data item in storage means (103); producing (122) a system flowchart (102D) on the basis of said data flowchart by using a system flow generation tool possessed by said computer (10); producing (124) program specifications (104D) on the basis of said system flowchart by using a program specification generation tool possessed by said computer (10); and producing (127)a source program for said business processing, on the basis of the data item obtained from said storage means (103) and said program specifications, by using a source program generation tool possessed by said computer (10). A method according to claim 1, wherein in case an advance is to be made from a certain one of said steps to a next one of said steps, data generated in the preceding step are handed over to the next step and the next step is executed, in response to a predetermined order given to said computer. A method according to claim 1, wherein the data item defined in said data flowchart is inputted to said data analysis tool (113). A distributed computer device such as a workstation in a distributed processing system for supporting design of a computer program for business processing; characterised in that: said distributed computer device comprises: means (101) for receiving data concerning business processing inputted by an operator and for producing definition of a plurality of unit functions (201) forming said business and a data flowchart (101D) between said unit functions; system flow generation tool means (122) for producing a system flowchart (102D) on the basis of said data flowchart; program specification generation tool means (124) for producing program specifications (104D) on the basis of said system flowchart; data analysis tool means (113) for extracting a data item on the basis of said data flowchart; storage means (103) for storing said data item; and source program generation tool means (127) for producing a source program for said business processing on the basis of the data item obtained from the storage means (103) and said program specifications.

Inventors: TSUKAKOSHI TOSHIHARU, TSUKAKOSHI, TOSHIHARU
Applicants: HITACHI LTD, HITACHI, LTD.
Application year: 1993
Main classification: G06F9
IPC codes: G06F9