JP2004310244A - Document update history management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To construct an update history management system which provides the reason of update, an updater, the content of the update, or the like to a user. <P>SOLUTION: In this update history management system, a history management screen is displayed on a display screen (step S6-1). Each line of the history management screen shows generation or update of a report, and each line includes "registration number", "former", "date", "remarks" and the like as items. A line with black circle shows generation of the report, and a line connected through a double line shows the update of an original report connected thereto. On this screen, since old editions other than the latest one can be seen from a user, the user can update the editions other than the latest one, and a plurality of kinds of the "latest editions" can be made to exist. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a document update history management system that can manage the update history of document data.
[0002]
[Prior art]
The contents of document data and programs are frequently updated. Managing this update history is important for document management.
[0003]
Therefore, various methods for managing the update history of a document or a program have been conventionally proposed.
[0004]
For example, Japanese Patent Application Laid-Open Publication No. H11-163873 discloses a method of calculating a ratio between the number of lines before correction and the number of lines after correction in a program list, obtaining a temporal change in this ratio, and predicting the number of lines in a program. Is disclosed.
[0005]
Patent Document 2 below discloses an apparatus capable of displaying a difference between a document before update and a document after update in the document.
[0006]
Patent Document 3 below discloses a method of managing update histories of database files updated from a plurality of hosts.
[0007]
Patent Document 4 below discloses a file correction history management system that stores a correction position and content as management information when the file content is corrected.
[0008]
Further, Patent Document 5 below discloses a technique for deleting, in a data sharing system shared by a plurality of terminals, an update history of data possessed by each terminal as soon as possible and reducing the amount of update history to be held by each terminal. It has been disclosed.
[0009]
Patent Document 6 below discloses a system in which when a source code of a program is erroneously corrected, when the correct correction is made and the erroneous correction is canceled, the cancellation operation is not reflected in the version number of the program. .
[0010]
[Patent Document 1]
Japanese Patent Application Laid-Open No. 4-09728 (Japanese Patent No. 3243791)
[Patent Document 2]
JP-A-5-298313 (Japanese Patent No. 2997518)
[Patent Document 3]
JP-A-7-129451 (Japanese Patent No. 2872019)
[Patent Document 4]
JP-A-10-3417 (Patent No. 3022326)
[Patent Document 5]
Japanese Patent Application Laid-Open No. 2000-122907 (Japanese Patent No. 300008)
[Patent Document 6]
Japanese Patent Application Laid-Open No. 2000-242474 (Japanese Patent No. 3005777)
[Problems to be solved by the invention]
However, according to the update history management methods disclosed in Patent Documents 1 to 6, what kind of correction has been performed so far, by whom, for what purpose, and how has it been performed? It is difficult to know.
[0011]
Patent Literature 1 discloses a technology that reads a change in the number of lines each time a program is updated and predicts the frequency of correction in the future, but cannot determine who made the correction, the reason for the correction, and the like. .
[0012]
Further, Patent Literature 2 discloses a technique in which a part updated by a first update can be known even after a second update is performed. This technique is useful for knowing where to update. However, there is no description about judging the reason for updating or the like.
[0013]
Patent Literature 3 discloses a system in which a plurality of hosts share one database. In Patent Document 3, each host updates the database sequentially according to the given serial number. It is said that this enables quick recovery from a file failure. However, even in Patent Document 3, since the reason for the update is not managed, there is no particular means for solving the question "What is the reason for the update?"
[0014]
Further, Patent Literature 4 discloses a technique for removing duplicate corrections in a system for correcting the contents of a file from a plurality of editors. That is, a warning is generated when another editor has already corrected a portion to be corrected by one editor.
[0015]
According to Patent Document 4, it is possible to prevent the superimposed correction, but no special means for managing the reason of the correction or the like is disclosed.
[0016]
Patent Literature 5 discloses a system in which a plurality of devices connected to a network each have the same document data. In this system, when document data is updated, the update information is transmitted to other devices. As a result, the contents of the document data held by a plurality of devices become the same. At this time, it is described that if the amount of update information is larger than the original data, the amount of transmission can be reduced by transmitting the document data itself.
[0017]
Points to keep in mind when managing security policy update history
In recent years, systems that support the construction of security policies have been developed.
[0018]
This security policy is a collection of various rules regarding information security of a predetermined group (for example, a company). In recent years, with the development of information technology, attention has been paid to the importance of formulating this security policy.
[0019]
This security policy is usually updated every predetermined period. The reason for this is that the number of employees in the company changes over time, and so does the work content. As a result, the composition of corporate information systems also changes.
[0020]
In order to respond to these changes, the content of the security policy needs to be constantly revised and updated. In particular, when performing security policy maintenance, it may happen that it is necessary to know what update has been performed and by whom for what reason.
[0021]
However, in the above-described conventional update history management method, although a technology for reflecting the result of the update in the document data file and a technology for efficiently sharing the update between a plurality of terminals have been proposed, the reason for the update and the There is no known method for managing updaters collectively. Further, there is a technology for adding a memo of update and information about update to a document data file to be updated, but a method of managing only update information separately from a document data file is not known.
[0022]
Therefore, for document data that is frequently updated, such as a security policy, a standard method of collectively managing the update reason, updater, and update content has not yet been established.
[0023]
As a result, in the maintenance of the conventional security policy (document data), the operator often manages the update history by making a personal note or memo separately. In the case where the update history is managed by such personal work, there is a possibility that it is difficult to take over the work when the worker in charge transfers or retires.
[0024]
Configure security policy
Also, this security policy is generally divided into a plurality of “parts” in many cases. For example,
Access control policy
・ Authentication / identification policy
In many cases, the configuration is divided into technical fields. Here, the access control policy is a set of rules for controlling access to resources in the information system. The authentication / identification policy is a policy related to authentication and identification, and is a collection of rules on technologies for authentication. In this patent, such a “portion” is called a “report”.
[0025]
As described above, the security policy is often managed by being divided into a plurality of reports. In this case, conventionally, in order for the operator to know the update history, it was necessary to open the data file of each report each time and inspect the contents in order. As a result, the work tends to be complicated.
[0026]
Object of the present invention
The present invention has been made in view of such a problem, and an object of the present invention is to construct a system that manages only update history information. In particular, it is an object of the present invention to construct a system capable of providing the user with the reason for the update, the updater, the content of the update, and the like.
[0027]
[Means for Solving the Problems]
In order to solve the above-described problems, the present invention uses a storage unit that stores a history management list, which is a list indicating an update history of a document and includes one or more lines indicating generation or update of the document. In the document update history management system that manages the update history of the document, each line in the history management list, the type, the registration number, the person who generated or updated, and the content of the generation or update, at least, A document update history management system, characterized in that a row representing the update in the history management list stores the registration number of a row representing a version to be updated represented by the row.
[0028]
With such a configuration, the document update history can be managed using a list that represents one update with one line.
[0029]
Further, the present invention is the document update history management system, characterized in that data indicating the newness is stored in a row indicating the generation in the history management list.
[0030]
With such a configuration, both generation and update can be managed similarly.
[0031]
Further, the present invention is the document update history management system, wherein the content of the generation or update is a link to a file representing the generation or update.
[0032]
It is often difficult to store the content of the generation or update itself in the list. By storing the link to the actual data using the link, the size of the update history list can be suppressed to an appropriate size.
[0033]
Further, the present invention provides a system for managing the update history of a document, wherein the display means for displaying the contents of the history management list, wherein a line in which data indicating that the type is new is stored is displayed. Indicates that the line is new, and displays the line in which the registration number is stored in the type, if the line indicates the original version to be updated. A document update history management system, comprising: display means for displaying a symbol connecting a line.
[0034]
With such a configuration, the user can know which line indicates the version (first version) at the time of generation. Similarly, it is possible to know which row represents the update.
[0035]
The present invention also provides a system for managing the update history of a document, wherein a history management list representing the update history of the document is displayed, the history management list including one or more lines representing generation or update of the document. And editing means for executing an editing operation when the user instructs editing on a predetermined line, wherein the editing means includes the following editing means. .
[0036]
That is, when the predetermined line designated by the user indicates an update, the editing unit configures the updated document represented by the predetermined line, and proceeds to an editing operation of the configured document. When the predetermined line indicated by the user indicates generation, the process shifts to the editing operation of the document at the time of generation indicated by the predetermined line.
[0037]
With such a configuration, the updated version of the document represented by each row can be edited.
[0038]
The present invention also provides a system for managing the update history of a document, wherein a history management list representing the update history of the document is displayed, the history management list including one or more lines representing generation or update of the document. And a control means for controlling the display operation of the details when the user instructs the display of the details on a predetermined line, wherein the following control means is included.
[0039]
That is, when the predetermined line specified by the user indicates an update, the control unit displays data of the specification of the document after the update indicated by the predetermined line, and displays the specified data specified by the user. In the case where the row of the document represents the generation, the data of the specification of the document at the time of the generation represented by the predetermined row is displayed.
[0040]
With such a configuration, the user can view the updated version of the document represented by each row.
[0041]
The present invention also provides a system for managing the update history of a document, wherein a history management list representing the update history of the document is displayed, the history management list including one or more lines representing generation or update of the document. And a control unit for controlling the display operation of the memo when the user instructs the display of the memo on a predetermined line, wherein the control unit includes the following control unit.
[0042]
That is, when the predetermined line designated by the user indicates an update, the control means displays memo data attached to the updated document represented by the predetermined line, and the user When the specified line indicates the generation, the memo data attached to the document at the time of generation indicated by the predetermined line is displayed.
[0043]
With such a configuration, the user can see the memo attached to the updated version of the document represented by each row.
[0044]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.
[0045]
1 Security policy management system
FIG. 1 shows a functional block diagram of a security policy management system 10 according to the present embodiment. As shown in this figure, the security policy management system 10
・ Security policy editing / generating means 12
-Security policy update history management means 14
.Control means 16
.Storage means 18
Each means is provided. Among these functions, the function of the security policy editing / generating means 12 itself includes a conventional document editing function called a conventional word processor or editor. The control unit 16 controls operations of the security policy editing / generating unit 12 and the security policy update history managing unit 14. Further, the storage unit 18 stores each report of the security policy to be managed, their update history, and other data.
[0046]
In the present embodiment, an example of managing the editing of the security policy and the like is shown. However, the same technology as that of the present embodiment can be used for managing the editing of other document data. That is, a security policy is described in the present embodiment as an example of a “document” of the present invention, but it is of course preferable to apply the present invention to another “document”.
[0047]
The security policy management system 10 includes a computer system and a program operating on the computer system. For example, the security policy editing / generating means 12 specifically adopts a configuration including software called a word processor or an editor. Software such as a word processor is well known. Since the security policy is also "document data", it can be generated and edited by software called a conventional word processor or editor.
[0048]
One of the characteristic configurations in the present embodiment is the security policy update history management unit 14. This means comprises a computer and a program operable on the computer, and this program executes the operation of the security policy update history management means 14.
[0049]
Hereinafter, the operation of the security policy management system 10 according to the present embodiment will be described.
[0050]
2 Operation of security policy management system
FIG. 2 is a flowchart showing the operation of the security policy management system 10 according to the present embodiment.
[0051]
First, in step S2-1, each "part" of the security policy managed by the security policy management system 10, that is, a list of reports is displayed on the display screen. This display operation is executed by the control unit 16. More precisely, a program constituting the control means 16 is executed. At the time of this display, the control unit 16 reads out the report list from the storage unit 18 and displays the report list to execute the operation of step S2-1.
[0052]
This display screen is called a “report menu”. FIG. 3 shows a display example of the report menu. A conceptual diagram of the report list is shown in FIG. As shown in this figure, the display screen of the report menu displays the report list almost as it is. The report list is tabular data and includes items of “report number”, “report name”, and “update date” as shown in FIG. The report number is a unique number assigned when the report is generated. The report name is the name of the report. The update date is the last update date of the report. In the report list, reports managed by the security policy management system 10 of the present embodiment are registered.
[0053]
2.1 Report Menu
As shown in FIG. 3, the display screen (report menu) according to the present embodiment displays not only a list of reports but also a batch replace button 20, a history management button 22, a print button 24, a close button 26, and the like. ing. These displays are also executed by the control means 16.
[0054]
When the user clicks the batch replacement button 20 (step S2-2), the selected report can be batch-replaced (step S2-3).
[0055]
The click means that the user presses a button of a pointing device such as a mouse while moving a cursor indicating a predetermined position on the display screen on a desired button. In particular, when a mouse is used as a pointing device, this cursor is often called a mouse cursor. A pointing device is a device used to indicate a desired position on a display screen. In addition to a mouse, various devices conventionally used in the world, such as a trackball and a sliding pad, may be used as the pointing device. Can be.
[0056]
When the user clicks the history management button 22 (step S2-4), the control unit 16 detects this and activates the history management function. Specifically, the security policy update history management means 14 of FIG. 1 is activated. When activated, the security policy update history management means 14 displays a history management screen on the display screen.
[0057]
FIG. 5 shows a display example of the history management screen. The detailed operation of the history management function realized by the security policy update history management unit 14 will be described later in detail.
[0058]
When the user clicks the print button 24 (step S2-6), the contents of the display screen, that is, the printing of the report list, is executed (step S2-7).
[0059]
When the user clicks the close button 26 (step S2-8), the history management function ends (step S2-9). This generally means that the security policy update history management means 14 ends, but an operation in which control is transferred to the control means 16 without ending the program of the security policy update history management means 14 may also be used.
[0060]
After this, it is preferable to return to a state where the main screen of the security policy management system 10 is displayed, for example. Such an end processing is preferably executed by the control unit 16. It is also preferable that after the security policy update history management means 14 ends, the report menu returns to the display state (FIG. 3).
[0061]
2.2 Operation of history management function
One of the characteristic items in the present embodiment is a report history management function (step S2-5).
[0062]
FIG. 6 is a flowchart showing details of the operation of this function. Activation of this function is performed by activation of the security policy update history management means 14 described above. Specifically, when a program constituting the security policy update history management unit 14 starts, a history management function starts.
[0063]
Hereinafter, the operation of the history management function will be described with reference to the flowchart of FIG. The operation described below is executed by a program constituting the security policy update history management unit 14.
[0064]
First, when this function is activated, a history management screen is displayed on the display screen as described in step S2-5 (step S6-1). This display is executed by the security policy update history management means 14 in FIG.
[0065]
The history management screen is shown in FIG. 5 as described above. As shown in FIG. 5, the history management screen is a table including a plurality of rows. Each row in this table represents a report generation or report update. One row corresponds to one “generate report” or “update report”.
[0066]
This table includes “generation number”, “report number”, “information asset”, “registration number”, “creator”, “date”, and “remarks” as items. The “generation number” is a serial number assigned when the report is generated. In FIG. 5, the generation number 12 means that the report is the twelfth generated report. “Report number” is a serial number assigned to each generated report. For example, 213 in FIG. 5 is a report number assigned to the generated report.
[0067]
“Information asset” indicates the number of the information asset in which the report is involved. “Registration number” is a serial number assigned in the order in which the reports were registered. The “creator” represents, in principle, the person who created the report, but the row indicating the update means the person who updated the report. "Date" indicates the date of creation in a row indicating creation of the report, and indicates the date of update in a row indicating update of the report.
[0068]
In "Notes", remarks concerning the creation or update of the report are entered. For example, “Generator original” in FIG. 5 means an initial version at the time of creating the report. In FIG. 5, “Replace” means that a part of the report has been updated and replaced.
[0069]
In FIG. 5, the line with a circle represents the generation of a report. Lines connected by double lines, that is, lines without circles, represent updates to the previous report connected by double lines.
[0070]
Here, the circle ● corresponds to an example of the “sign indicating new” in the claims. Further, the double line corresponds to an example of the “symbol connecting the line to the line of the original version to be updated” in the claims.
[0071]
For example, the row with the registration number 23 (the top row in FIG. 5) means that a report with the number 213 is newly generated (see the item “report number”). The row with the registration number 24 (the second row from the top in FIG. 5) indicates an update performed on the report 213.
[0072]
Similarly, the row with the registration number 42 indicates an update to the report 213 to which the update of the registration number 24 has been applied.
[0073]
Similarly, the row with the registration number 89 indicates an update to the report 213 to which the update of the registration number 42 has been applied.
[0074]
As described above, the registration numbers 24, 42, 89, 113, and 137 mean updates that are serially applied to the report 213 (applied in order). Therefore, the report 213 to which the update of the registration number 137 is applied is one of the latest editions.
[0075]
On the other hand, updates applied to one report may exist in parallel. In particular, in the case of a security policy, two types of update plans, Mr. A's update plan and Mr. B's update plan, may exist at the same time. In consideration of such a case, in the present embodiment, two or more types of update plans can be managed for one report. In other words, a plurality of updates applied in parallel to one report can be managed. Such an example is also shown in FIG.
[0076]
For example, a row with a registration number of 25 means generation of a report with a number of 101. On the other hand, the row with the registration number 26 indicates an update applied to the report 101 at the time of generation. The row with the registration number 37 also means an update applied to the report 101 at the time of generation. Hereinafter, the rows with registration numbers 75, 99, and 123 also mean updates that are applied directly to the report 101 at the time of generation. These are not updates that are applied in order as in the rows of the registration numbers 42 and 89 described above.
[0077]
As a result, regarding the report 101, there are five latest update proposals. As for the report 213, the version in which the update of the rows of the registration numbers 24, 42, 89, 113, and 137 described above are sequentially applied, and the rows of the registration numbers 258, 283, 310, 335, 377, and 564 as shown in FIG. At this time, the two types of updated versions are the latest versions.
[0078]
As described above, the update history management function according to the present embodiment can simultaneously handle a plurality of types of update versions for one security policy.
[0079]
The security policy update history management unit 14 displays this history management screen based on the history management list in the storage unit 18. An outline of the history management list is shown in FIG. As shown in this figure, the history management list is tabular data including information shown on the history management screen shown in FIG. 5, and based on this history management list, the security policy update history management means 14 The management screen can be displayed.
[0080]
Here, the security policy update history management unit 14 corresponds to an example of “a unit for displaying a history management list” in the claims.
[0081]
As shown in FIG. 7, the history management list includes items that are not directly shown on the history management screen in FIG. For example, the “type” is an item indicating whether the data in the row is the creation of a new report or the update of an existing report. If the content of the “type” is “new”, it means that a new report has been created, and based on this “new”, the security policy update history management unit 14 displays a black circle in FIG. is there.
[0082]
Here, “new” corresponds to an example of the “new data” in the claims.
[0083]
In the case of updating a report, the “type” describes the registration number of the parent to be updated. For example, the row of the registration number 24 has a type of “23”, which indicates that the row indicates an update to the report created with the registration number 23. Further, the line of the registration number 42 has the content of the type “24”, which indicates that the line indicates the update to the report created with the registration number 24. The security policy update history management means 14 can display the parent-child relationship by the double line in FIG. 5 based on the registration number of the parent of the update source.
[0084]
Further, as shown in FIG. 7, the history management list includes specific “contents”. In the present embodiment, when a new report is created, this “content” is a link to the report file. Of course, this "content" may be the content of the report itself. In many cases, it is convenient to describe the report itself in a file format of a word processor. Therefore, in the present embodiment, the above “content” describes a link to the file of the report.
[0085]
In the case of updating, the “content” is a link to a file including the update position and the updated content. Of course, also in this case, the update position or the update content itself may be stored in the “content”. In the present embodiment, an example will be described in which an update position and an update content are described in a word processor file format, similarly to a report.
[0086]
Note that the update position and the update content here are data generally used in a technique used for managing the version number of document data. In general, for managing the version number of document data, a technique of managing data of a first edition (first edition) and difference data between subsequent editions is conventionally known. That is, the difference between the first edition data and the second edition data, the difference between the second edition and the third edition data, the difference between the third edition data and the fourth edition data, and so on. Based on these data, for example, if a third edition is desired, the first edition data includes a difference between the first edition and the second edition data, a difference between the second edition and the third edition data, Is applied to obtain the third version of document data. In many cases, the difference data includes an update position and its update content (added text, etc.).
[0087]
The technology of version control (revision control) in the present embodiment employs the conventional technology described above as it is. Therefore, as described above, the “contents” of each line of the history management list in FIG. 7 correspond to the data of the first edition report itself in the case of generating a new report, and correspond to the data of the first edition in the case of updating the report. It corresponds to the difference data (update position and update content) between the previous version and that version.
[0088]
Here, “corresponding” means that a link to each data is described, but the data itself may be directly described in “contents”.
[0089]
As described above, in the present embodiment, the update history of a report is managed by using a table including a row indicating the generation or update of the report. In particular, in the present embodiment, a plurality of updates that are applied in parallel to a report of a certain version (either the version at the time of generation (that is, the first version) or a version to which updates are added thereafter) are managed. It is possible to manage the update history of a report that has more than one "latest version".
[0090]
In the present embodiment, a plurality of "latest versions" can be managed because, as is clear from the history management list (FIG. 7) and the history management screen (FIG. 5), the user can also use older versions other than the latest version. Because you can see. By adopting such a configuration, a user can update a version other than the latest version. As a result, according to the present embodiment, there can be a plurality of types of “latest versions”.
[0091]
2.2.1 Report update operation
Next, on the history management screen of FIG. 5, when the user selects a desired line (step S6-2) and clicks the edit button 30 (step S6-3), the update represented by that line is applied. Is displayed in another window (step S6-4).
[0092]
FIG. 8 shows an example in which another window is displayed. This figure shows a state where a report named “Executive Information Security Policy” is displayed. This display is performed by a program called a conventional word processor or editor. That is, from the state shown in FIG. 8, the user can not only browse but also edit the executive information security policy. As described above, the operation of performing not only browsing but also editing at the same time is an operation generally performed in a conventional word processor or the like, and thus can be sufficiently performed by the conventional technology.
[0093]
Here, the operation of “selection” is executed by the user moving the cursor over a desired line using a mouse and then pressing (clicking) the mouse button once. By this "selection" operation, the selected line is highlighted and the selected fact is explicitly shown to the user. Such an inverted display is shown in FIG. In FIG. 9, the row indicating the update with the registration number 682 is in an inverted display state, indicating that the row has been selected.
[0094]
2.2.2 Display and update operation of report of desired version
Details of the operation in step S6-4 will be described based on the flowcharts in FIGS.
[0095]
First, in step S10-1, the security policy update history management unit 14 sends the registration number of the version indicated by the line specified by the user to the security policy editing / generation unit 12. Here, the security policy editing / generating unit 12 corresponds to an example of an editing unit in the claims.
[0096]
Next, the word processor program included in the security policy editing / generating means 12 reconstructs the transmitted report of the registration number.
[0097]
For this purpose, first, in step S10-2, the word processor in the security policy editing / generating means 12 extracts the data of the row of the transmitted registration number from the history management list. The history management list is tabular data shown in FIG. 7 and is stored in the storage unit 18. Further, in particular, "contents" in the data taken out of the line of interest are stored in a predetermined memory.
[0098]
Next, in step S10-3, it is checked whether the "type" in the data of the line of interest is "new". If the result of the inspection is “new”, the flow proceeds to step S10-5, and if not, the flow proceeds to step S10-4.
[0099]
In step S10-4, a line whose registration number is the number described in the "type" of the line of interest is selected, and the data of the selected line is extracted from the history management list in the storage unit 18. At this time, similarly to step S10-2, the "contents" in the extracted data of the newly selected line is stored in the predetermined memory. Then, the process returns to step S10-3.
[0100]
In step S10-5, the report of the edition to be viewed / edited is reconstructed based on the "contents" previously stored on the predetermined memory. This reconstruction is performed by a word processor.
[0101]
Here, as described above, the “contents” are (the link to) the data of the first version of the report, and (the link to) the difference data representing the subsequently updated version. Constructing a predetermined version of document data (report) based on these data can be sufficiently executed by using a conventional version number management technique. Also in this embodiment, the word processor reconstructs a report of a predetermined version by using the conventional version number management technology.
[0102]
By the processing described above, the version report of the line designated by the user is reconstructed by the word processor, and the word processor displays the report on the display screen. In step S10-6, the user can further edit and update the report on the display screen.
[0103]
In step S10-7, the word processor records the operation of the user editing and updating the report, and after the editing is completed, outputs the difference data based on the operation. Since a technique for creating such difference data is well known in the related art, the present embodiment also uses the conventional technique as it is.
[0104]
Next, in step S11-1 in FIG. 11, after the editing is completed, the user instructs to save data and terminates the word processor.
[0105]
In step S11-2, the word processor instructed to save the data stores the difference data obtained as a result of the word processor editing action in the storage unit 18. Further, the word processor adds the line data including the link to the stored difference data as “content” to the history management list (see FIG. 7).
[0106]
“Type” in the added line data is the line number specified by the user in step S10-1. Thus, it can be shown that this line data represents an update to the version indicated by the line number specified by the user in step S10-1.
[0107]
The "generation number" in the added line data is the same number as the generation number in the line data indicated by the line number specified by the user in step S10-1. The “report number” in the added line data is the same as the report number in the line data indicated by the line number specified by the user in step S10-1. The "information asset" in the added line data has the same content as the information asset in the line data indicated by the line number specified by the user in step S10-1. The “registration number” in the added line data is a number obtained by adding 1 to the recently used registration number. The “creator” in the added line data is the user who has updated. “Date” in the added line data is the date on which the update was performed.
[0108]
“Remarks” in the added line data is simple memo data input by the user at the time of updating. In this embodiment, as described above, the user can input a simple memo regarding the update at the time of updating, and the simple memo is managed as a part of the update history. As a result, by describing the purpose and content of the update in this simple memo, it becomes possible to know the meaning and content of the update through the simple memo at a later date.
[0109]
As described above, according to the present embodiment, when the user updates each report of the security policy, each update is managed. In particular, management can be performed so that a plurality of revisions can exist for one edition, and (history) management of security policy updates with high flexibility can be performed.
[0110]
2.2.3 Other operations on the history management screen
From the history management screen, not only the operation of editing the report by clicking the edit button 30 (step S6-4), but also various operations can be performed based on the user's instruction. Returning to the flowchart of FIG. 6, these other operations will be described.
[0111]
2.2.3.1 Details of history
First, in the history management screen of FIG. 5, when the user presses the left button of the mouse (sometimes called left click) while placing the cursor on the selected line (step S6-5), the details of the history are displayed. Is displayed (step S6-6). FIG. 12 shows an example of this display.
[0112]
This display operation is executed by the security policy update history management unit 14. In this case, the security policy update history management unit 14 corresponds to an example of the “control unit that controls a display operation of a statement” in the claims.
[0113]
In the present embodiment, when the user wants to know the details of the desired update, he or she simply puts the cursor on the line indicating the update and left-clicks the user to easily obtain detailed information on the update. It is possible. This detailed information is referred to as “specification” in the present embodiment. Further, particularly in the present embodiment, since the details of the update and the reason for performing the update are included in the specification, the user can easily grasp the reason for the update performed in the past. It is possible.
[0114]
2.2.3.2 Presence or absence of memo
When the user presses the right button of the mouse (sometimes called right-click) while placing the cursor on the selected line on the history management screen in FIG. 5 (step S6-7), the report for the report is displayed. A display indicating the presence or absence of the memo is displayed (step S6-8). This display operation is executed by the security policy update history management unit 14. In this case, the security policy update history management means 14 corresponds to an example of “control means for controlling a memo display operation” in the claims, and the operation described below is basically performed by the security policy update history management means 14. Operation.
[0115]
The detailed operation of step S6-8 is shown in the flowchart of FIG.
[0116]
First, in step S13-1, the security policy update history management unit 14 checks whether a memo is added to the report. This check is performed based on the contents of the report list described with reference to FIG. This report list is stored in the storage unit 18 as described above.
[0117]
As shown in FIG. 4, information on the presence or absence of a memo is recorded in the item of “memo” in the report list. If the content of the "memo" is "NO", it means that the report has no memo attached. On the other hand, when a memo is attached, the “memo” describes a link to a file in which the memo is described. In the example shown in FIG. 4, the number of links is described for the report numbers 105 and 110, which indicates that a memo is added. On the other hand, the column of “memo” of other reports is “NO”, which indicates that no memo is attached.
[0118]
The security policy update history management means 14 checks whether or not a memo is attached to the report based on the contents of the "memo" column.
[0119]
As a result of the inspection, when a memo is attached, the process proceeds to step S13-2, and when no memo is attached, the process proceeds to step S13-6.
[0120]
In step S13-2, a message box 40 indicating that a memo is attached is displayed. This is shown in FIG. As shown in FIG. 14, in this message box 40, a message "Memo is registered in this report" is displayed, and an OK button 42 is also displayed. This display operation is executed by the security policy update history management unit 14. In this state, when the user clicks the OK button 42, the process proceeds to step S13-3.
[0121]
In step S13-3, the actual contents of the memo are displayed. The substance of the memo is described in a very common text data format, and the contents of the memo are displayed by displaying the text data. This display is executed by the security policy update history management unit 14. Of course, it is also preferable that the security policy update history management means 14 calls and activates an editor program or a word processor program capable of displaying text data.
[0122]
FIG. 15 shows an example of a screen displaying the contents of the memo. In the present embodiment, the report is composed of a plurality of blocks, and a memo can be added to each block.
[0123]
As shown in FIG. 15, in the present embodiment, the contents of a memo are displayed by displaying a message box containing a table showing the contents of one memo in one line. Inside the message box, a table including an item of “Block” and an item of “Memo” is shown. The number of the block to which the memo is attached and the content of the memo attached to the block are respectively shown. It is shown.
[0124]
In the example shown in FIG. 15, two memos are attached. First, the first block in the report is marked with a memo “Corrected on December 24, 2002”. In addition, a memo “101BLK35“ Compliant with ISMS certification standards ”is added” is added to the 35th block. As described above, in the present embodiment, a memo can be added for each block, so that the purpose and reason for updating the report, the content of the update of the report, and the like can be left in the memo.
[0125]
In step S13-4, the user waits for the user to select and click on any memo line. If it is clicked, the flow shifts to step S13-5.
[0126]
In step S13-5, when the user clicks, the block of the selected row is displayed. This display is preferably performed as in step S6-4 described above (as in the flowchart of FIG. 10). This display is preferably executed by the word processor program in the security policy editing / generating means 12, as in step S6-4.
[0127]
On the other hand, in step S13-6, a message box indicating that no memo is attached is displayed. Contrary to the example shown in FIG. 14, in this message box, a message "No memo is registered in this report" is displayed, and an OK button is also displayed. This display operation is executed by the security policy update history management unit 14. When the user clicks the OK button in this state, the operation of the flowchart in FIG. 13 ends, and the process returns to the processing in FIG.
[0128]
In this embodiment, it is possible to easily confirm whether or not there is a memo regarding a desired update. In other words, by simply placing the cursor on the line indicating the update and right-clicking by the user, it is possible to easily know whether or not a memo is attached to the update.
[0129]
According to such a memo, it is possible to grasp the reason for updating the report, the content of the update, and the like.
[0130]
2.2.4 End of history management and others
As shown in FIG. 5, in addition to the edit button 30, an end button 32 and a delete button 34 are displayed on the history management screen.
[0131]
Then, by clicking the end button 32, the history management function ends. Specifically, the history management screen is closed, and the report menu screen is displayed. When the delete button 34 is clicked, the report selected at that time can be deleted.
[0132]
3 Summary
As described above, a characteristic of the present embodiment is that the update history of the report is managed using the table including the rows corresponding to the generation and the update of the report. Since such a table is used, the user can easily grasp the update history of the predetermined report.
[0133]
In addition, since the contents of a report that has undergone a certain update, that is, a report of a certain “version”, can be easily checked, it is easy to see what changes have been made in the report so far. . In particular, according to the present embodiment, a memo can be added, so that the contents of each version can be checked more easily.
[0134]
【The invention's effect】
As described above in detail, according to the present invention, since the update history of a document is managed using a list including lines indicating generation and update, management can be performed for each update.
[0135]
Further, according to the present invention, a memo or a statement can be displayed by giving a predetermined instruction to a line indicating generation or update, so that the reason for the update or the like can be easily known.
[Brief description of the drawings]
FIG. 1 is a functional block diagram of a security policy management system according to an embodiment.
FIG. 2 is a flowchart illustrating an operation of the security policy management system according to the present embodiment.
FIG. 3 is an explanatory diagram illustrating a display state of a report menu.
FIG. 4 is a conceptual diagram of a report list.
FIG. 5 is an explanatory diagram illustrating a display state of a history management screen.
FIG. 6 is a flowchart illustrating the operation of a report history management function.
FIG. 7 is a conceptual diagram of a history management list.
FIG. 8 is an explanatory view showing a state in which an edit button is clicked from the history management screen and the contents of a predetermined version of the report are displayed in another window.
FIG. 9 is an explanatory diagram showing a state of selection.
FIG. 10 is a flowchart showing details of the operation in step S6-4.
FIG. 11 is a flowchart showing details of the operation in step S6-4.
FIG. 12 is an explanatory diagram showing a state in which another window showing details of a history is displayed.
FIG. 13 is a flowchart illustrating a detailed operation of step S6-8.
FIG. 14 is an explanatory diagram illustrating a state in which a message box indicating that a memo is attached is displayed.
FIG. 15 is an explanatory diagram illustrating a state in which a message box indicating the contents of a memo is displayed.
[Explanation of symbols]
10 Security Policy Management System
12 Security policy editing / generating means
14 Security policy update history management means
16 control means
18 storage means
20 Batch Replace button
22 History management button
24 Print button
26 Close button
30 Edit button
32 Exit button
34 Delete button

Claims (7)

Storage means for storing a history management list including a list indicating the update history of the document and including at least one row indicating the generation or update of the document, the document update history management system managing the update history of the document At
Each line in the history management list, the type, the registration number, the person who generated or updated, and at least the content of the generation or update,
A document update history management system, wherein a row representing the update in the history management list stores the registration number of a row representing a version to be updated represented by the row. The document update history management system according to claim 1,
A document update history management system, wherein data indicating that the document is new is stored in a row indicating the generation in the history management list. The document update history management system according to claim 1 or 2,
The document update history management system, wherein the content of the generation or update is a link to a file indicating the generation or update. The document update history management system according to any one of claims 1 to 3, further comprising:
Display means for displaying the contents of the history management list, and when displaying a line in which data indicating that the type is new is stored, adding a symbol indicating that the line is new Display means for displaying, when displaying a line in which the registration number is stored in the type, a symbol connecting the line to the line of the original version to be updated,
A document update history management system, comprising: In a system that manages the update history of documents,
Means for displaying a history management list representing an update history of the document, the history management list including one or more lines representing generation or update of the document;
Editing means for executing an editing operation when a user instructs editing on a predetermined line;
And the editing means comprises:
When the predetermined line specified by the user indicates an update, the updated document represented by the predetermined line is configured, the process proceeds to an editing operation of the configured document, and the predetermined instruction specified by the user is performed. A document update history management system, wherein, when a row of the document represents generation, the operation shifts to an editing operation of the document at the time of generation represented by the predetermined row. In a system that manages the update history of documents,
Means for displaying a history management list representing an update history of the document, the history management list including one or more lines representing generation or update of the document;
Control means for controlling the display operation of the statement when the user instructs the display of the statement for a predetermined line;
Including, the control means,
When the predetermined line designated by the user indicates an update, the data of the updated specification of the document represented by the predetermined line is displayed, and the predetermined line designated by the user indicates the generation. A document update history management system for displaying data of details of the document at the time of generation represented by the predetermined line. In a system that manages the update history of documents,
Means for displaying a history management list representing an update history of the document, the history management list including one or more lines representing generation or update of the document;
Control means for controlling the display operation of the memo when the user instructs the display of the memo for a predetermined line;
Including, the control means,
When the predetermined line specified by the user indicates an update, the data of the memo attached to the updated document indicated by the predetermined line is displayed, and the predetermined line specified by the user is displayed. A document update history management system, wherein when the generation is indicated, data of a memo attached to the document at the time of generation indicated by the predetermined line is displayed.

Images