JPH11296361A - Program information managing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily manage information related to a program to be developed by unitary management. SOLUTION: A program information managing means 9 applies each attribute information inputted from an attribute information inputted image 10 and the logic part of a program inputted from a program edition screen 11 to each pattern, and preserves it in a single integrated substance file 12 so that the unitary management of corresponding edition information can be attained. A document information generating part 3 automatically generates a software specification 13 based on information other than the program logic from the integrated substance file 12, and a program extracting part 4 generates a program file 14 by extracting the logic part of the program from the integrated substance file 12. An information update processing means 15 newly generates an integrated substance file 12 by adding revision information according to specification change.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a program information management apparatus, and more particularly, to management of document information such as programs generated in program development and program specifications.

[0002]

2. Description of the Related Art Generally, software development proceeds by designing software, creating a software specification describing software specifications, and creating a source program based on the software specification. If the software specifications are changed during development, the entire software or only the changed parts are redesigned, the software specifications are revised, and a source program is created or modified based on the revised software specifications. Alternatively, create a software prototype in advance and show it to elicit client requests for software,
In some cases, the prototype software specification is revised according to the request, and software is developed by creating or changing the software. In addition, even after the software development, there are many cases where specifications are changed due to addition or change of functions, and the software is developed as a new version.

As described above, when software is developed, document information such as software specifications and a source program are created. When the contents are changed, the changed contents are written each time. Must be reflected in software specifications and programs. Even if the specification changes, the contents of the software specification and the program after reflecting the change must always match.However, it is usually generated as a separate file. At the present time, it is difficult to say that it is not always easy to make the same because the same person does not always perform the revision work on the source program.

Therefore, conventionally, for example, Japanese Patent Application Laid-Open
No. 175,643 (hereinafter referred to as “prior art 1”)
There is disclosed a software development support device capable of reliably matching a software specification and a source program. In the prior art 1, this is realized by operating as follows. That is, when an editing operation is performed on a software specification, the history of the software specification is maintained, and editing operation information of the source program is generated based on the history information. I am trying to fix it. On the other hand, when an editing operation is performed on the source program, the history is maintained, and the editing operation information of the software specification is generated based on the history information. I am trying to fix it. As a result, consistency between the software specification and the source program can be achieved, and labor required for reflecting design and correction contents can be reduced.

[0005] For example, Japanese Unexamined Patent Publication No. Hei 5-324289 (hereinafter referred to as "prior art 2") discloses a detailed processing to a logic part of a program based on a unique comment description embedded in a source code. There is disclosed an apparatus capable of automatically generating a program design document for explaining the flow of the process. In Prior Art 2, this is realized by operating as follows. In other words, a comment describing the unique processing name for the detailed processing such as assignment, conditional branching, and output in each step of the program is translated into a language in accordance with the analysis of the program algorithm and the analysis result by the verbalization mechanism, and is formatted Output.

[0006]

However, conventionally, since the software specification and the source program are managed by different entities by generating them as different files, a mechanism for associating them has been required. . For this reason, a means for associative management has been required. In particular, when a revised edition or the like is generated, its management becomes more complicated.

Further, in the prior art 1, the history is held in accordance with the correction of either the software specification or the source program, the editing operation information is generated, and the other is corrected, so that the other is corrected. If the correction is made again before the contents are reflected, the matching may not be achieved. To cope with such inconveniences, the processing becomes complicated, and the cost of the apparatus may increase.

In the prior art 2, it is difficult to manage the history of software specifications and source programs.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and an object of the present invention is to manage information related to a program to be developed in a unified manner, thereby facilitating the management of the information. It is to provide a device.

[0010]

In order to achieve the above object, a program information management apparatus according to a first aspect of the present invention provides a program information management apparatus which stores a developed program and attribute information relating to the program in a predetermined location of a template. A program information management unit that fits and stores the model together with a model in a single integrated entity file; a document information generating unit that automatically generates document information based on the stored contents of the integrated entity file; and a program from the integrated entity file. And program extraction means for generating a program file by extracting the logic part of the above, and manages the corresponding version of the program and the attribute information in a single entity.

[0011] In a second aspect of the present invention, in the first aspect, the program information management means includes: an attribute information management unit that applies attribute information input from an attribute information input screen to the template; A program edit processing unit for applying a logic part of the program input from the edit screen to the template.

A program information management device according to a third aspect of the present invention is the program information management device according to the first aspect, wherein the information stored in the integrated entity file is taken out, the content is changed, and the changed attribute information is changed. And an information update processing means for newly generating an integrated entity file reflecting the above.

According to a fourth aspect of the present invention, in the program information management apparatus according to the third aspect, the information update processing means updates the document information by applying attribute information including revision information input from an attribute information input screen to the template. A processing unit, and a program update processing unit that applies the logic part of the program input and changed from the program editing screen to the template, and stores the attribute information of the corresponding version and the logic part of the program together with the template by storing the template. A new integrated entity file is generated.

According to a fifth aspect of the present invention, in the third aspect of the present invention, the program information management apparatus further includes a version information management unit that manages version information associated with updating of information related to the program.

According to a sixth aspect of the present invention, in the program information management device according to the first aspect, the document information and the program generated based on the stored contents of the integrated entity file are converted into a format that can be displayed by a world wide web browser. And information display control means.

[0016]

Preferred embodiments of the present invention will be described below with reference to the drawings.

Embodiment 1 FIG. 1 is a block diagram showing an embodiment of a program information management device according to the present invention. The program information management device according to the present embodiment includes an attribute information management unit 1, a program edit processing unit 2,
It has a document information generation unit 3, a program extraction unit 4, a document information update processing unit 5, a program update processing unit 6, a version information management unit 7, and an information display control unit 8. The program information management means 9 including the attribute information management unit 1 and the program editing processing unit 2 holds the template as shown in FIG. 2 internally or in a file format. Each attribute information input from the screen 10 is applied to a predetermined portion of the model. The program edit processing unit 2
The logic portion of the program input from the program editing screen 11 is applied to a predetermined portion of the model. The program information management means 9 saves the attribute information and the program assigned to the template together with the template in a single integrated entity file 12. The details regarding the template will be described later. The document information generation unit 3 includes the integrated entity file 1
Document information such as the software specification 13 is automatically generated based on the stored contents of 2. The program extracting unit 4 extracts a logic part of the program from the integrated entity file 12 and generates a program file 14. The document information update processing unit 5 updates the attribute information of the integrated entity file 12 based on the revision work performed via the attribute information input screen 10 or the like. The program update processing unit 6 updates the logic part of the program stored in the integrated entity file 12 based on the revision work performed via the program editing screen 11 or the like. The information update processing unit 15 including the document information update processing unit 5 and the program update processing unit 6 newly generates the integrated entity file 12 and stores the updated information. The version information management unit 7 uses the version information file 16 to manage the version information accompanying the update of the information on the program. The information display control unit 8 converts the software specification 13 and the program generated based on the stored contents of the integrated entity file 12 corresponding to the specified version into a format that can be displayed by a World Wide Web (WWW) browser, It can be displayed on a display not shown.

FIG. 2 is a diagram showing an example of the contents of the above-mentioned model. In the present embodiment, an SGML (Standard Generalized) is provided so as to support WWW.
Markup Language) document. The template includes revision information such as a revision date, and tags in which attribute information such as a program name, a version, and a function and a source code indicating a logic portion of the program are to be stored and registered in advance. Each predetermined location where various types of information are inserted is configured by a set of a tag (for example, <program name>) indicating the head and an end tag (</ program name>) expressed by adding a slash thereto. Such tags are all prepared for the information necessary for generating the program and the document information, and are held by the program information management means 9.

A feature of the present embodiment is that the corresponding version of the program and the software specification 13 are stored in a single integrated entity file 12 so as to be centrally managed. This makes it very easy to maintain the consistency between the program and the software specification, so that the load required for information management in software whose contents are revised can be significantly reduced. Further, with the reduction of the load, the productivity of software can be improved.

Next, the operation of this embodiment will be described. Here, generation of the integrated entity file 12 and input of the attribute information and the program, and generation of the software specification 13 and the program file will be sequentially described.

First, the process of generating the integrated entity file 12 in response to the input of the attribute information and the program will be described with reference to the flowchart shown in FIG.

First, the attribute information management unit 1 displays an attribute information input screen 10 as shown in FIG. 1 (step 10).
1) Accept the attribute information input by the user (step 102). Input items provided on the attribute information input screen 10 are set based on tags registered in the model. As a result, it is possible to input all the information necessary for creating the software specification. The attribute information management unit 1 applies each attribute information input from the attribute information input screen 10 to a predetermined portion of the read template (step 103). FIG. 4 shows an example in which the input attribute information is applied to a template. Basically, each attribute information is inserted at a place other than the source code and the revision information where the logic part of the program is inserted.

On the other hand, the program editing processing section 2 displays the program editing screen 11 shown in FIG.
04), accept the program and its function name (module name) input by the user (step 10)
5). The program editing function provided by the program editing processing unit 2 has the same function as general document creation software. The program edit processing unit 2 applies the logic part of the program input from the program edit screen 11 to a predetermined portion (source code) of the module corresponding to the template (step 106). FIG. 5 shows an example in which the input program is applied to a model. In this way, the integrated entity file 12 is generated by storing the input attribute information and the program together with the template (step 107).

With the above procedure, the integrated entity file 12 corresponding to each program can be generated. Actually, a version information file update process is further executed. The details of this process will be described in a later section regarding a process related to version management. This embodiment is characterized in that the input attribute information and the program are stored in a single file, and the input order of the attribute information and the program, the configuration of each screen, and the screen transition are appropriate. Should be designed. Further, the reason why the revision information not used in the template is included is that the information update processing unit 15 shares the template with the template used in the revision work.

Next, the generated integrated entity file 12
Will be described with reference to a flowchart shown in FIG.

The document information generation unit 3 reads information of a part other than the source code in the integrated entity file 12 (Step 201). Specifically, the information stored between the tag name (<tag name>) indicating the tag name and the start position and the end tag name (</ tag name>) is extracted as a set. At this time, if no information is set between the tags, the information is ignored. For the first edition, the revision information will be ignored. The tag name and each attribute information extracted as a set are temporarily stored as variables (step 20).
2). <Tag 1>, <Tag 2>, <Tag 3>, ..., <
In the case of a hierarchical tag structure such as / tag3>, </ tag2>, </ tag1>, this hierarchical information is temporarily stored as a multidimensional array variable, and is referred to when creating a software specification. Make sure you can do it. In the example shown in FIG. 2, the relationship between <module> and </ module> and the tag between them is equivalent to this. As described above, when the information for creating the software specification is collected based on the information of the parts other than the source code stored in the integrated entity file 12, the document information generation unit 3 executes the processing in the predetermined format. A software specification is prepared by adjusting the appearance so that the data can be output (step 203). For example, as shown in FIG. 7, when the information described in the software specification is output in the form of a table, first, for the information forming the cover, the program name and version variables are extracted and output. The information that makes up the module information is the module name,
Extract and output function variables. The information item names in each table are represented by tag names. In this embodiment, the software specification is described in HTML (HyperT).
In order to create an ext Markup Language (HTML) document, an HTML file in which only tags for creating a table or the like are described is prepared in advance as a model, and each information is applied. As described above, a software specification can be created from information of a part other than the source code in the integrated entity file 12.

Subsequently, the program extracting section 4 generates a program file. The basic operation is the same as that of the above-described document information generating section 3. That is, only necessary information from the integrated entity file 12, in this case, only the source code portion and the corresponding function name information in the integrated entity file 12 are read (step 204). Then, the source code portion, that is, the logic portion of the program is generated as one file (step 205). At this time, a file name to be stored is generated by adding a predetermined identifier of a programming language describing the logic to the function name. For example, if the program is described in the C language, it will be “function name.c”.
<Source code> and <// in the integrated entity file 12
By performing the above-described file generation processing on each logic part created by the source code>, a program file can be generated based on the integrated entity file 12. An executable image file is generated from this program file.

According to the above procedure, a software specification and a program file can be automatically generated from the same integrated entity file 12. In the above example, when creating the software specification, each attribute information is output in the form of a table. However, the contents of the template HTML file and the processing of the document information generation unit 3 corresponding thereto are changed. Thus, it is possible to flexibly cope with various types of software specifications. Further, in the present embodiment, the automatic generation of the software specification and the program file has been described as a series of processes, but only one of them can be generated.

According to the present embodiment, all the information required to generate the corresponding version of the software specification and the program file is stored in a single entity (file). A means for associating the program with document information relating to the program becomes unnecessary. For this reason, management of information on the program becomes extremely easy. Of course, since the document information generation unit 3 and the program extraction unit 4 are provided, the integrated entity file 12
, A software specification and a program file can be automatically generated.

Next, a process in the case where a software specification and a program are modified due to a change in specifications and a revised edition is generated will be described with reference to the flowchart shown in FIG.

When the specification is changed and a revised version needs to be created, the document information update processing unit 5 displays the attribute information input screen 10 shown in FIG. The information is taken out and displayed on the screen (step 301). The necessary information in this case is information other than the source code. The information that needs to be corrected among the displayed information is changed by the user, but in the case of a revision, information such as a revision date, a revision person, and a revision content should be input from the attribute information input screen 10, so that the The information update processing unit 5 receives the attribute information including the revision information (Step 302). Then, each attribute information is applied to a predetermined portion of the template (step 30).
3). FIG. 9 shows an example in which the input attribute information is applied to a template. Basically, each attribute information is inserted at a place other than the source code where the logic part of the program is inserted. At this time, the revision information is also inserted.

On the other hand, the program update processing section 6 displays the program edit screen 11 shown in FIG. 1, and when modifying an existing program, reads the program from the integrated entity file 12 and displays it (step 304). ).
Then, the newly generated or modified program and its function name are received (step 305), and a predetermined portion (source code) of the module corresponding to the template is received.
(Step 306). Then, the input attribute information and the program are stored in the new integrated entity file 12 together with the template (step 307). In this embodiment, the integrated entity files 12 having the same name are stored and managed in different folders. However, the integrated entity files 12 may be assigned different names and managed in the same folder.

As described above, when the integrated entity file 12 is newly generated, the version information management unit 7 generates version information for performing version management and adds it to the version information file 16 (step). 308). Although not described above, the version information file 16 is generated when the first version of the integrated entity file 12 is generated, and version information for the first version is registered. More specifically, when the integrated entity file 12 is newly generated, the version information management unit 7 extracts information created by <version> and </ version> from the integrated entity file 12 and Generate version information. In the present embodiment, the software specification is automatically generated and displayed by displaying the version number on the screen as shown in FIG. 10 by the information display control unit 8 and allowing the user to select it from the screen with a mouse or the like. Therefore, HTML such as <a href=v1.0/index.htm> 1.0 version </a> is generated as version information and registered in the version information file 16.

As described above, by generating the version information, the information display control unit 8 can display a software specification of a desired version. That is, the information display control unit 8 operates the integrated entity file 12 corresponding to the selected version.
Generates a software specification in the same manner as the document information generation unit 3, converts this into a format that can be displayed by a WWW browser, and displays it on a screen. FIG. 11 is a diagram showing an example of a screen transition of the software specification displayed from the screen shown in FIG. Finally, the logic of the program can be similarly displayed on the screen from the specification screen of each function. According to the present embodiment, version management can be performed in this way.

Although the configuration of the apparatus according to the present embodiment shown in FIG. 1 is illustrated in correspondence with the processing, some functions required in each processing are duplicated. Application can be generated in common. For example, the information update processing means 15 is almost the same in function as the program information management means 9 except that the contents of the integrated entity file 12 are displayed on each screen and handles revision information, so that the functions can be shared. The function of the information display control unit 8 extracting the software specification and the program from the integrated entity file 12 can be shared with the document information generation unit 3 and the program extraction unit 4.

In this embodiment, only the software specification has been described as the document information. However, other document information relating to the program to be managed, such as an operation manual, can be handled in the same manner. Further, the software specification does not necessarily indicate only a single document, and a case where the document includes a plurality of document information such as a system design specification, a database specification, and an internal specification is also within the scope of the present invention. . Even when such a plurality of documents are handled, it can be easily retained and managed in the integrated entity file 12 simply by adding tags corresponding to information necessary for the model to the model.

Also, in the present embodiment, the logic of the program is input from the edit screen because it is assumed to be used at the time of software development. However, the program edit processing unit is not in the screen but in a file format. 2 may be passed.

Further, in the present embodiment, the use of a WWW browser is premised, so that the template is generated by an SGML document. However, it is needless to say that the present invention can be applied to a system that does not use a WWW browser.

[0039]

According to the present invention, since the corresponding version of the program and the document information are stored in a single entity and centrally managed, the consistency between the program and the document information can be maintained. It can be very easy.

Further, since an integrated entity file is newly generated for each revision and the corresponding version program and document information are managed, version management can be performed easily.

Further, since the version information is managed, each version can be easily displayed.

Since the document information and the program can be converted into a format that can be displayed by a world wide web browser, the document and the program can be easily displayed in the HTML document format.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an embodiment of a program information management device according to the present invention.

FIG. 2 is a diagram showing an example of contents of a model prepared in advance in the present embodiment.

FIG. 3 is a flowchart showing a process of generating an integrated entity file according to the embodiment.

FIG. 4 is a diagram showing an example in which each piece of attribute information input in the present embodiment is applied to a template.

FIG. 5 is a diagram showing an example when a program input in the present embodiment is applied to a model;

FIG. 6 is a flowchart illustrating a process of generating a software specification and a program file according to the present embodiment.

FIG. 7 is a diagram showing a display example of a software specification document generated in the present embodiment.

FIG. 8 is a flowchart showing a process of generating a revised version in the present embodiment.

FIG. 9 is a diagram illustrating an example in which each piece of attribute information input in the present embodiment is applied to a template.

FIG. 10 is a diagram showing an example of a screen when a version number is displayed in the present embodiment.

FIG. 11 is a diagram showing an example of a screen transition of a software specification displayed from the screen shown in FIG. 10;

[Explanation of symbols]

1 attribute information management section, 2 program editing processing section, 3
Document information generator, 4 program extractor, 5 document information update processor, 6 program update processor, 7th edition information manager, 8 information display controller, 9 program information manager, 10 attribute information input screen, 11 program editing Screen, 12 integrated entity files, 13 software specifications, 14 program files, 15 information update processing means, 16 version information files.

Claims (6)

[Claims] 1. A program information management means for applying a developed program and attribute information relating to the program to a predetermined location of a prepared template, and storing the program and a model together with the template in a single integrated entity file. Document information generating means for automatically generating document information based on the stored contents, and program extracting means for extracting a logic part of the program from the integrated entity file and generating a program file, and a corresponding version of the program and attributes A program information management device, wherein information is managed by a single entity. 2. The program information management means according to claim 1, wherein: an attribute information management unit for applying attribute information input from an attribute information input screen to said template; and a program for applying a logic part of a program input from a program edit screen to said template. The program information management device according to claim 1, further comprising: an edit processing unit. 3. An information updating process for extracting information stored in the integrated entity file, changing the content thereof, and newly generating an integrated entity file reflecting the changed attribute information. 2. The program information management device according to claim 1, further comprising means. 4. A document information update processing unit for applying attribute information including revision information input from an attribute information input screen to the template, a logic of a program input and changed from a program edit screen. And a program update processing unit for applying a part to the template, wherein the integrated entity file is newly generated by storing attribute information of a corresponding version and a logic part of the program together with the template. Item 3. The program information management device according to Item 3. 5. The program information management apparatus according to claim 3, further comprising version information management means for managing version information accompanying update of information on the program. 6. An information display control means for converting document information and a program generated based on the stored contents of the integrated entity file into a format that can be displayed by a world wide web browser. Program information management device.