JPS6059436A - Production and control system for program and document - Google Patents

Abstract

PURPOSE:To facilitate the effective production, maintenance and update of both program and document by controlling the programs and documents integratedly and in the form of a computer file. CONSTITUTION:Both program information 106 and document information 107 are supplied to a CPU102 from a CRT103 arranging a keyboard. An integrated file 510 stores a program file 110 and a document file 210 in one body or with close contacts with each other. Then both information 106 and 107 are stored to a magnetic disk 101 in the form of the file 510. When a correction is needed to the file 510, the new information 106 or 107 is supplied through the CRT103 like in the case of input. Then an additional correction is given to a desired area of the file 510. The corrected contents are displayed to a CRT103. Furthermore a program list 105 and a document list 205 can be delivered by means of a printer 104.

Description

DETAILED DESCRIPTION OF THE INVENTION The present invention relates to a method for efficiently creating and maintaining a large number of computer programs and their documents.

(Prior Art) Conventionally, computer programs and documents such as manuals have been created and managed separately, resulting in the following problems.

■ Delay in document preparation.

Compared to the program itself, which needs to be developed quickly, document maintenance inevitably takes a backseat. This trend is especially noticeable when creating an individual-paced program.

■ Inadequate document search method.

The problem is that the program itself and the documents are managed separately. 4 Even if you want to quickly view the documents related to a certain program, it takes a lot of effort to search. This problem is related to the above item (2), and means that when a part of a program is modified, it is practically difficult to immediately modify the document.

■ Inconsistency in document content and set of documents.

The content and format of the document is left to the will of the program author or system creator and is not uniform. For example, each program manufacturer uses a different format. This is especially true for programs created on an individual basis. Therefore, in order to collect various programs and prepare documents in a certain format, a great deal of effort is required to re-edit the documents. The program name and information required for program creation are still available.
It is also necessary to separately create documents such as a program summary table that summarizes the author's name, functions, etc., and this also requires a considerable amount of effort.

Figures 1 and 2 are conceptual diagrams showing the conventional method of creating programs and documents. It also shows a method for creating documents in the form of electronic files.

First, in FIG. 1, a program is created using a CPU 102 connected to a magnetic disk 101, a CRT terminal 103 with a keyboard, and a printer 104. The program information 106 input from the CRT terminal 103 via the keyboard is stored as a program file 1.10 in the magnetic disk Ioi via the CPU 102, and is outputted to the printer 104 as needed.
It can be obtained as a program list 105. On the other hand, the document information 107 is first
-108, and then printed as necessary, resulting in a printed document 1o9.

Next, FIG. 2 will be explained. The creation of the program is the same as in the case of FIG. 1, as shown in FIG. 2(a).

On the other hand, document creation is performed using a magnetic disk 2o1, a keyboard, and a CRT terminal 20, as shown in Figure 2(b).
3 and a printer 204 are connected to the CPU 1202. Note that 205 is a document,
Here, 201, 202. ... 204 may be collectively regarded as a word processor.

Still, on the hardware, 201, 202. ....

204 may also be used as 101, 102, -, 104.

However, what is important here is that in any case, the program file 110 and the document file 21
0 are created and managed separately, which means that creating and managing them requires a great deal of effort.

Figure 3 shows the procedure for creating programs and documents using the conventional method, and Figure 4 shows the procedure for creating a program summary table that summarizes program names, author names, functions, etc. using the conventional method. .

In the conventional method, programs and documents are managed separately, so the program and document creation procedure shown in Figure 3 is cumbersome, resulting in delays in document preparation and ■ However, the procedure for creating the program summary table shown in Figure 4 is still very difficult, as mentioned in the explanation above. The disadvantage is that it requires manual labor.

(Object of the Invention) In order to eliminate these drawbacks, the present invention manages both programs and documents in a unified manner in the form of a computer file, and creates documents regarding all programs according to a predetermined format. This facilitates the efficient creation, maintenance, and updating of programs and documents.The following figure will be explained in detail.

(Structure and operation of the invention) FIG. 5 is a diagram showing an outline of the creation and maintenance of programs and documents according to the method of the present invention.

First, program information 106 and document information 107
CRT io 3.1 with key fod:'l
The program file 110 and document file 21.0 are stored in the magnetic disk 101 as a unified file 510 in which the program file 110 and the document file 21.0 are stored integrally or in a closely related manner.

To modify the unified file, enter the latest program information 1 from the CRT 103 with a keyboard in the same way as when inputting it.
06 or the document information 107 manually, and add 11 corrections to the necessary parts of the unified file 510.

By using the unified file 510, the present invention allows programs and documents to be modified simultaneously, greatly improving productivity. The contents of the modified unified file 510 can be stored on the CRT 1 with keys and keys when necessary.
You can view it by displaying it on 03, and then select printer 1 as appropriate.
It is also possible to output in the form of zologram list 105 and dokeymen l-205 using 04.

Figure 1 is still shown in Figure 2.The major difference from the conventional method is that in the method of the present invention, programs and documents are created and stored as one unit or in a closely correlated form, and
It is corrected and updated using the same method using the same keyboard CRT 103, and as a result, problems ①, ②, and ② of the conventional method described above are completely improved.

FIG. 6 is a diagram showing the flow of creating and managing program circles and single queues according to the method of the present invention.

First, after conducting a study 601, a process 602 of creating a program and document using an editor is performed to create a unified file 603 that stores information about both the program and the document.

Next, a test run 604 of the program is performed, and if the result is OK, the program is terminated. If not, the program is reviewed again 601, and the program and documentation are modified 602. A unified file 603 is created.

A program and document are created by repeating the above steps. Comparing this with the flow of program and document creation management according to the conventional method (FIG. 3), it can be seen that the processing flow according to the method of the present invention is extremely simplified.

If we focus on the creation and modification of the program itself, there is no difference between the two, and within the dashed line frame in Figure 3 (301 to 3 o 4
) corresponds to the whole of FIG. 6 (6()1 to 6o4).

On the other hand, when we focus on document creation and modification, there is a big difference between the two. In the conventional method shown in FIG. 3, in order to obtain the document file 307 or document 310 by executing document file creation/modification 306 or document creation/modification 309, first, document file search 30 is performed.
5 or the document itself needs to be searched 308. Hosoishi 1 When developing a program with thousands of applications, it usually takes a very long time to find the necessary document files or documents themselves. In fact, it can be difficult to locate the necessary documents within practical time limits. Unfortunately, in the conventional system, only the processing (program creation/modification) within the dashed line frame in FIG. 3 takes precedence, and document creation and modification are postponed.

As described above, according to the present invention, there is no need to go through the trouble of searching for documents, and the program can be corrected and the document corrected at the same time. Therefore, the problem described in L can be avoided, and the latest document can always be updated. It is possible to secure it.

FIG. 7 shows a program summary table (program name 1 author name 1 date of creation/update, file name, function or processing content of the program) according to the method of the present invention.

It shows the procedure for creating a program (list of how to use Stezzo numbers, explanations of arguments, restrictions, etc.). The only operation required to obtain a program summary table is to start a program summary table creation program.

Here, the details of the operation of the summary table creation program are shown in FIG. 4, and the program summary table creation procedure is performed by a computer. In this case, the steps of program summary table 407 and fair copying 408 in FIG. 4 are unnecessary, and the process of picking out the necessary parts in the document 406
[However, the words in parentheses are anxiety] will continue to program summary table 409.

Creating a program summary table using the method of the present invention is much easier and more accurate than the conventional method shown in FIG. 4, and enables efficient and detailed program management using a combiner.

As shown in FIG. 4, in the conventional method, it is safe to start up the file management program 401 and create a list 402 of existing program names without having to edit it. Next, based on this, a document file search 403 or a document search 404 is performed to find a set of documents 405 associated with the program name list 402. Next, enter the items necessary to create a program summary table (program name, author name, year and month of creation, and 1).

File name, program function or processing content.

An operation 406 is performed in which the number of program steps, etc.) are picked up one by one from each document by handwriting or cutting and pasting, and a handwritten or cutting and pasting zologram summary table 407 is obtained. Further, this is corrected 408 using an editor, word processor, printing, or other means to create a printed 70-segment summary table 409. lastly,
The contents are compared with the document set 405 or the 70-segment gram summary table 407, and if there are no errors, the process ends. If there is an error, return to the fair copy 408 and repeat the above.

As described above, in the conventional method shown in FIG. 4, since the document formats of each program are not uniform, it is necessary for a person to manually pick out the necessary parts of the document one by one.

On the other hand, in the method of the present invention, since the format of the document is unified, it takes 40 hours to pick up the necessary parts.
6 can be run at a convenience store in the evening.Furthermore, since the program and 18 documents are managed together, the task of searching for document files can be easily done.
Since all of 3 can be executed by the combiner, as shown in FIG. 7, the target 1] can be achieved simply by starting 701 a program for creating a program summary table created in advance. It is also possible to create a summary table of only programs that meet the 11-key criteria by using the keywords in the unified file in the same way as described above.

In the conventional Nof method (Figure 4), creating a program summary table just once is a huge effort, and it is inefficient to do this frequently. 7th
According to Figure), it is possible to create a program summary table for Shiko I-Bond New at any time very easily by searching based on various information (program name 1 author name, key +7) 4) in the unified file. This allows for detailed program management.

Figure 8 shows a flow diagram and 1.

This shows an example of the structure of a unified file 510 for a document, with the document file 210 at the beginning [1-, followed by the program file 110. Copy the document format file 810 prepared in advance at the beginning of program creation to the beginning of the unified file 510, make it a 1" keyment file, enter the contents of the program files 1 and 0, and sequentially file the document file. All you have to do is enter the contents of 210.

At this time, the document information may be stored as a comment in each program.
Based on the program names stored in , and the information created and saved in the document corresponding to each program,
1) Program summary table that summarizes author name, function summary, etc.
(II) Summary documents such as program manuals, lists of programs and their functions searched according to iiD keywords, etc. can also be automatically created by computer processing.

(Effects) As explained above, according to the method of the present invention, programs and documents can be managed in an integrated manner, and documents can always be kept in a well-organized and up-to-date state. Still 7 bladders.
Because a single set of documents is used, all materials such as program summary sheets can be automatically created using a computer, making it possible to create, maintain, and manage accurate, quick, and detailed programs and documents. It has the advantage of being

[Brief explanation of drawings]

Figures 1 and 2 are conceptual diagrams showing the method for creating programs and documents using the conventional method, Figure 3 is a diagram showing the procedure for creating programs and documents using the conventional method, and Figure 4 is a diagram showing the program summary table using the conventional method. FIG. 5 is a diagram showing the outline of the creation and maintenance of programs and doggements according to the method of the present invention; FIG. 6 is a diagram showing the flow of creating and managing programs and documents according to the method of the present invention; FIG. 7 is a diagram showing a procedure for creating a program summary table according to the method of the present invention, and FIG. 8 is a diagram showing an example of the structure of a unified file for programs and documents according to the method of the present invention. 101, 201... magnetic disk, 102, 202...
・・CPU, 103,203・・Keyboard-handed CRT
Terminal, 104, 204...Printer, 105-Program list F, 106...Program 1111 report, 107
Document information, 108... Chiwaki Dogiment, 1
09...Fll, Intermediate document, 110 ・
Zorogura l, file, 205... document, 2
10.1 document file, 510.Unified file, 810.Document format file. Figure 1 Figure 2 (a) 0j Figure 5 205 Figure 6 Figure 7 Figure 8 Procedural amendment (method) % formula% 2 Name of invention Program and togyme/1.
Creation management method 3 Relationship with the case of the person making the amendment Applicant address 1-1-6 Uchisaiwai-cho, Chiyoda-ku, Tokyo Name (4
22) Representative of Nippon Telegraph and Telephone Public Corporation Tsune Shinfuji 5, [1i1j of 1981]
January 11 (Delivery date: January 31, 1980) 6 Number of inventions increased by amendment Op.7 Target of amendment Drawing 8

Claims (3)

[Claims] (1) When creating a program for an electronic subtraction machine using an information input/output device, the main body of the program to be created is saved as a source program file, and the program name, author name, file name, creation/update date, usage method, etc. ,
A file containing document information necessary for using the program, such as argument explanations and restrictions, in a predetermined format can be associated with the source program file, or both files can be saved as one. A method for creating and managing programs and documents, characterized in that the files in which the information is stored are used to create, maintain, and update programs and documents. (2) Claim No. 1 (2) characterized in that document information is stored as a comment in each program.
1) Program and document creation and management method described in section 1). (3) Based on the program name stored in the directory file and the information created and saved in the document corresponding to each program, (1) a program summary table summarizing the author name, function summary, etc.; Claim (1) characterized in that a summary document such as an iD program manual, (iii) a list of programs searched according to keywords and their functions, etc. is automatically created by computer processing. Program and document creation management method.