JP2010113392A - It asset configuration management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To preliminarily recognize not only already known dependency relation relative to existing software in the management of IT assets but also any influence received by the other software due to the change, new development or new introduction of software, and to easily recognize correct specifications by managing history of the change of software. <P>SOLUTION: A computer system, its specifications, software operating in the computer system, data to be input or output by the software and the dependency relation of the software and the data are stored in a database system, and the dependency relation is clarified by retrieving the database. Also, history of the documents of the software is managed, and an inter-version difference is retrieved. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an IT resource configuration management system that manages specifications, dependencies, and configurations of IT resources including application software.

  IT resources are difficult to manage because there are many IT resources and there is a dependency on the combination of hardware, software, and software. For software, the dependencies were complex and management was particularly difficult.

  As technologies for facilitating the management of IT resources, Patent Literature 1, Patent Literature 2 and Patent Literature 3 describe a technology in which the system manages software dependency relationships and changes the software to satisfy the dependency relationships. Various disclosures have been made. According to these technologies, it is possible to leave a part of dependency management to the system when software is changed, and prevent changes that do not satisfy the dependency in the range managed by the system. Is possible. However, all of these prior arts are management of existing software, and it is assumed that the dependency relationship is already known. When attempting to change, newly develop or introduce software, it is not possible to manage the dependency brought about by the software to be changed, newly developed or newly installed. I couldn't understand the impact on other software.

Furthermore, depending on the technology for managing the dependency relationship, it has been difficult to grasp the correct specification by managing the change history of software that has been changed during the development process. This is because, in principle, there is no dependency between the version of the software that has been changed and the version after the change.
JP 2004-158812 A Japanese Patent Laid-Open No. 2006-177881 JP 2008-186147 A

In the present invention, in the management of IT resources, when existing software is to be changed, newly developed or newly introduced, it is not easy to grasp in advance how other software is affected by the change, new development or new introduction. It tries to solve the problem. At the same time, it is intended to solve the problem that it is difficult to grasp the correct specification by managing the change history of software that has been changed in the development process.
According to the present invention, it is possible to strictly set the requirements, scope, etc. of software changes, new development or new introduction, but the present invention further provides the approval to approve new development performed by a company through setting the scope. It is also intended to solve the problem that the right of settlement is not always clear.

  With the configuration described below, the present invention grasps in advance the influence of other software on software changes, new developments or new introductions, and manages the history of software changes to grasp correct specifications. Make it easier.

  The IT resource configuration management system of the present invention includes information on two or more computer systems, specifications of the computer system, software operating in the computer system, and data input or output by the software. IT resource configuration information included as items is held in a database system, and the database system can search the IT resource configuration information using software as a key.

  The IT resource configuration information includes documents created when software is developed, and the documents are history-managed.

  The IT resource configuration information includes version information of the software, the history of the documents is associated with the version information, and the database system includes a version of software operating in one computer system among the documents. It is possible to search for a part describing a difference from the version of the software operating in another computer system.

  The IT resource management information includes a dependency relationship between software and data as an item, and the database system searches for another software having a dependency relationship with data having a dependency relationship with the software using one software as a key. It can be characterized by obtaining.

  The present invention clarifies the settlement right holder in a proposal or the like for approving a new development performed by a company with the configuration described below.

  In the IT resource configuration management system of the present invention, an access person and a person in charge are set in an access management item that is all or a part of items included in the IT resource structure information, and the access that has been approved by the person in charge The access management item can be added, deleted, or modified only by a possible person.

The IT resource configuration management system of the present invention can search IT resource configuration information using one software as a key, and the effect of facilitating the grasp of the influence range of software change by the result of this search. is there.
In addition, it is possible to search for documents that are history-managed and associated with software versions, and it is possible to easily obtain information necessary for grasping the scope of influence of software changes.
Furthermore, the IT resource configuration management system of the present invention can include a dependency relationship between software and data as an item of IT resource management information. Using this, it is possible to search for other software that may have a dependency relationship with one piece of software and data, narrowing down the other software to be examined, and facilitating understanding of the impact range of software changes There is an effect of doing.

  The IT resource configuration management system of the present invention approves a new development performed by a company because an accessible person and a responsible person are set in access management items that are all or part of the items included in the IT resource configuration information. This has the effect of clarifying by setting the right of settlement as the person in charge of the debate.

(Definition of terms)
Prior to the description of the embodiments, terms commonly used will be clarified.

  “Computer system” refers to a device capable of operating a program. For example, one personal computer corresponds to the computer system. When computer systems are connected via a network, there are a computer system that operates as a server and a computer system that operates as a client. A computer system that operates as a server and a computer system that operates as a client are also computer systems.

  “Software” refers to one or more programs used to perform predetermined processing. The entire program necessary for performing a predetermined process is a piece of software. One software runs on one computer system, one or more programs running on one computer system, the same program running on two or more computer systems, or runs on two or more computer systems It can take any form of different (two or more) programs.

The “database” is a program and data that can store items in association with each other and search for the items.
The “database” is not limited to so-called database software as long as items can be stored in association with each other and items can be searched.

  “Documents” are explanatory materials about software that can be stored in a database. For example, a machine-readable manual and a software help file correspond to the documents.

  “History management” means that every time a correction (addition, deletion, or change of contents) is made to a document, either the document before correction, the document after correction, or the difference between before and after correction This means that documents are held in a form that can be output. For example, the history management corresponds to having a program that holds documents before correction and documents after correction and obtains a difference between the two documents.

The “dependency relationship” refers to a relationship between software and data or a relationship between two pieces of software, and a relationship in which one change can affect the other. Here, “influence” means “need to change”. For example, in the relationship between software and data, the relationship in which software inputs / outputs data, and in the relationship between two softwares, when one uses the function of the other as a subroutine, and the processing that should not be used as a subroutine but should be the same A case where it is implemented in two pieces of software corresponds to the dependency relationship.
Note that this is an “influenceable relationship” and not an “influenced relationship”. This is because whether or not it actually affects depends on the specific contents of the change and cannot be determined in advance in all cases.

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

(Basic settings)
Company X is a company that conducts sales activities worldwide. Company X has bases in Tokyo, New York and Paris, and the computer system shown in FIG. 1 is installed in each base.

In the Tokyo office 2, software A2, B1, and C1 are operating in a computer system CS01 that operates as a server. Computer systems CS02, CS03, and CS04 that operate as clients are connected to CS01, and software A2 operates on these clients. The software A2 is software composed of the entire program that operates on the server and the client, and the software B and C are composed of programs that operate only on the server.

At the New York site 3, software A2E is operating in a computer system CS04 that operates as a server. Computer systems CS05 and CS06 that operate as clients are connected to CS04, and software A2E operates on these clients. The software A2E is software composed of the entire program that operates on the server and the client, and is obtained by adding English localization to the software A2 that operates on the Tokyo base.

At the Paris site 4, the software A2F is operating in the computer system CS07 that operates as a server. Computer systems CS08 and CS09 that operate as clients are connected to CS07, and software A2F operates on these clients. The software A2F is software composed of the entire program that operates on the server and the client, and is obtained by adding French localization to the software A2 that operates on the Tokyo base.

Here, the name of the software is represented by one letter of alphabet, the function version is represented by one letter, and if there is localization within the function version, it is represented by one letter of alphabet, and these are combined. For example, “A2” indicates the function version “2” of the software “A”, and “A2E” indicates the function version “2” of the software “A” plus the localization “E” (English). The “version” refers to a function version without localization and a combination of the function version and localization, for example, “2” and “2E”.

  Company X operates an IT resource configuration management system on a server CS01 in the Tokyo office, which is the head office. The IT resource configuration management system can be accessed from each base through the inter-base network 1. The IT resource configuration management system holds the following data as IT resource configuration information.

表１は、ＩＴ資産構成管理システムのデータベースに含まれるコンピュータシステムの情報をまとめたものである。コンピュータシステム毎に、その名称、配置されている拠点、そのシステムがサーバであるかクライアントであるかの区別、そのコンピュータシステムがクライアントである場合には接続するサーバ、そのコンピュータシステムがサーバである場合には接続するクライアント、そのコンピュータシステムの仕様としてのＣＰＵ、メモリ並びにＯＳ、及び、そのコンピュータシステムにおいて動作するソフトウェアに関する情報が、データベースに保持される。

Table 1 summarizes computer system information included in the IT asset configuration management system database. For each computer system, its name, the location where it is located, whether the system is a server or a client, if the computer system is a client, the server to connect to, and if the computer system is a server In the database, information relating to a client to be connected, a CPU as a specification of the computer system, a memory and an OS, and software operating in the computer system are held in a database.

表２は、ＩＴ資産構成管理システムのデータベースに含まれるソフトウェアの情報をまとめたものである。ソフトウェアのバージョン毎に、依存関係にあるソフトウェア、依存関係にあるデータ、及び、そのアプリケーションソフトウェアの動作のためにコンピュータシステムに要求される仕様としてのＣＰＵ、メモリ並びにＯＳに関する情報が、データベースに保持される。
ソフトウェアＣ１は、ソフトウェアＡ２の機能の一部をサブルーチンとして利用している。
ソフトウェアＡ２はデータＪを出力し、ソフトウェアＢ１はデータＪを入力する。

Table 2 summarizes software information included in the database of the IT resource configuration management system. For each version of software, information on the CPU, memory, and OS as specifications required for the computer system for the operation of the application software is maintained in the database. The
The software C1 uses a part of the function of the software A2 as a subroutine.
Software A2 outputs data J, and software B1 inputs data J.

表３は、ＩＴ資産構成管理システムのデータベースに含まれるドキュメント類の情報をまとめたものである。ソフトウェアのバージョン毎に、そのコンテンツが保持されている。

Table 3 summarizes information on documents included in the database of the IT resource configuration management system. Each software version holds its contents.

表４は、ＩＴ資産構成管理システムのデータベースに含まれるアクセス管理の情報をまとめたものである。対象項目毎に、責任者とアクセス可能者に関する情報が、データベースに保持され得る。
ＩＴシステムに関するＸ社の規則では、２以上の拠点をまたがるソフトウェアの変更または新規導入については東京拠点のＣＩＯの承認を必要とし、１拠点のみに関するシステムの変更または新規導入は各拠点のＩＴ責任者の承認で行うことができるとされている。この規則に従い、ソフトウェアごとに責任者が指定されている。なお、ソフトウェアＡ２について、Ａ２は東京拠点のみに導入されているが、Ａ２の変更はＡ２Ｅ及びＡ２Ｆをも変更することとなり３拠点にまたがるので、ＣＩＯが責任者となっている。

また、アクセス可能者は、変更、新規開発または新規導入の必要の都度設定するものであり、通常は設定されていない。

Table 4 summarizes access management information included in the database of the IT resource configuration management system. For each target item, information about the responsible person and accessible person can be held in the database.
Company X's rules for IT systems require the approval of the CIO at the Tokyo office for software changes or new installations across two or more offices, and IT managers at each office are responsible for system changes or new installations for only one office. It can be done with approval. In accordance with this rule, a responsible person is designated for each software. As for the software A2, A2 is installed only in the Tokyo base, but since the change of A2 also changes A2E and A2F and spans three bases, the CIO is responsible.

The accessible person is set whenever a change, new development or new introduction is necessary, and is not normally set.

(Document history management)
Company X was using software A1 at its Tokyo office. After that, version A2 with an extended function added to A1 was developed, and A2 was also used at the New York and Paris bases. Developed A2E and A2F with A2 localized in English and French for use in New York and Paris. In addition, Company X uses software B1 and C1 only in the Tokyo office. The above is the software shown in Table 2.

表５は、ＩＴ資産構成管理システムのデータベースに含まれるドキュメント類の差分情報をまとめたものである。バージョンのみの違いであるソフトウェアの組み合わせについての一部について、ドキュメント類の差分（旧バージョンから新バージョンへの変更事項）に係る情報が保存されている。
Ｘ社は、ソフトウェアＡ１のドキュメント類をＩＴ資産構成管理システムのデータベースに保持していた。Ａ２の開発後、Ａ２のドキュメント類をデータベースに追加した。その際、ＩＴ資産構成管理システムは、Ａ２のドキュメント類について、データベース内に同じ名称のアプリケーションソフトウェア（Ａ）の別のバージョン（Ａ１）のドキュメント類が保持されていることを検出し、これら２つのバージョンのドキュメント類の差分を求めて、表５に示すようにデータベースに保存した。具体的には、Ａ１からＡ２への差分として、拡張機能のマニュアルが追加されたこと及びヘルプファイルが変更されたことが差分データとして保存された。

Table 5 summarizes the difference information of documents included in the database of the IT resource configuration management system. Information about differences in documents (changes from an old version to a new version) is stored for a part of a combination of software that is only a difference in version.
Company X kept the documents of software A1 in the database of the IT resource configuration management system. After the development of A2, the documents of A2 were added to the database. At that time, the IT resource configuration management system detects that documents of another version (A1) of the application software (A) having the same name are held in the database for the documents of A2, and these two Differences between versions of documents were obtained and stored in a database as shown in Table 5. Specifically, as the difference from A1 to A2, the fact that the extended function manual was added and the help file was changed were saved as difference data.

  In addition, Company X has added A2E and A2F documents to the database. At that time, the IT resource configuration management system detects that documents of another version (A2) of the application software (A) having the same name are held in the database for the documents of A2E. Differences between versions of documents were obtained and stored in a database as shown in Table 5. Specifically, as the difference from A2 to A2E, the fact that the help file (Japanese) was deleted and the help file (English) was added was stored as difference data. Similarly, as the difference from A2 to A2F, the fact that the help file (Japanese) was deleted and the help file (French) was added was saved as difference data.

(Change proposal and approval)
An employee of company X's Tokyo office planned a function change for software A2 and proposed it to the IT manager at the Tokyo office. The IT manager in the Tokyo office accessed the database of the IT asset configuration management system and confirmed that the A2 manager was the CIO, not the IT manager in Tokyo. The IT manager at the Tokyo office told the employee about this, and the employee made a new proposal to the CIO. This proposal included the estimated amount for changes only in A2.

The CIO who received the proposal from the employee accessed the database of the IT resource configuration management system in order to grasp the influence of the change of the software A2. The procedure for the IT resource configuration management system to determine the possible range of influence is as shown in FIG. In the following, the procedure for obtaining the range of possibility of influence will be described with reference to FIG.

The CIO designates the software A2 in the software designation step 11. By this designation, “specification of the range of possibility of influence when software A2 is changed” is instructed to the IT resource configuration management system.
In step 12, the IT resource configuration management system detects that A2E, A2F, and C1 are dependent on A2 based on the data shown in Table 2, and adds these software to the potential impact range.
As shown in Table 2, since the data A having the dependency relationship exists in the software A2, the IT resource configuration management system starts the loop process of Step 13. In step 14, the IT resource configuration management system searches for “software other than A2 having a dependency relationship with data J”. This search is executed based on the data shown in Table 2, and the software B1 is searched. In step 15, A1, A2E, A2F, and B1 as a result of the search are added to the potential influence range.
Since there is no data other than the data J in the software A2, there is no dependency data, and the loop is exited in step 16. In step 17, the IT resource configuration management system outputs software A 1, A 2 E, A 2 F, B 1, and C 1 as an influence possibility range.

  The CIO pointed out the possibility of changes in A2E, A2F, B1, and C1 because the proposal from the employee included the estimated amount for only the software A2 change, and instructed the employee to review it. did.

Upon review by employees, it was found that the proposed changes to A2 had no changes to the processing of data J and the functions used by C1, and no changes were required for B1 and C1.
The employee described the difference between the version of software A running on the computer system CS01 and the version of the software A running on another computer system in order to review the scope of change required for A2E and A2F. The part was searched with the IT asset configuration management system. As a result, only the difference in the above-mentioned help file was searched as the difference in documents.
Since the above search results do not include manual differences related to functions, A2E and A2F are the addition of localization to A2 and there is no functional difference. It turns out that it is only localization for the file.
The employee re-proposed to the CIO in addition to the above-mentioned development work contents and the estimated amount of money.

ＣＩＯは、社員からの再提案を承認し、社員をＩＴ資産構成管理システム上のＡ２、Ａ２Ｅ及びＡ２Ｆに係る項目のアクセス可能者として設定した。設定後のアクセス管理は表６のとおりである。なお、Ａ２Ｅについてはニューヨーク拠点のＩＴ責任者が管理責任者であるが、その上位者であるＣＩＯもアクセス可能者を設定できる。

The CIO approved the re-suggestion from the employee, and set the employee as an accessible person for the items related to A2, A2E, and A2F on the IT asset configuration management system. Table 6 shows the access management after the setting. As for A2E, the IT manager in New York is the manager, but the higher-level CIO can also set accessible persons.

（変更の実行）
ＣＩＯの承認を得た社員は、ソフトウェアＡ２を変更したソフトウェアＡ３及びＡ３をローカライズしたＡ３Ｅ並びにＡ３Ｆの開発を完了し、アクセス可能者としてＩＴ資産構成管理システムのデータベースにＡ３、Ａ３Ｅ及びＡ３Ｆの情報を追加した。追加後の情報は、表７、表８、表９及び表１０のとおりである。
なお、社員はＡ３でなくＡ２に係るアクセス可能者であるが、ＩＴ資産構成システムのアクセス管理はソフトウェアの変更を想定しているので、社員はＡ２を変更した上位バージョンＡ３についての情報の追加も可能である。
また、社員は、ソフトウェアＡ３、Ａ３Ｅ及びＡ３Ｆを表１Ａの通りにインストールした。

(Perform changes)
Employees who have received approval from CIO have completed the development of A3E and A3F, which are localized versions of software A3 and A3, which have changed software A2, and have access to A3, A3E and A3F information in the IT asset configuration management system database Added. The information after the addition is as shown in Table 7, Table 8, Table 9, and Table 10.
The employee is an accessible person related to A2 instead of A3. However, since the access management of the IT resource configuration system assumes a software change, the employee can also add information about the higher version A3 that changed A2. Is possible.
The employees also installed software A3, A3E and A3F as shown in Table 1A.

(effect)
According to this embodiment, the following effects can be obtained.
In this embodiment, since the documents of the software A are managed in history and the difference between versions is searched, it can be easily grasped that A2E and A2F are localized versions of A2 and the functions are not expanded. . As an effect of the IT resource configuration management system, more generally, it is possible to easily grasp the exact specification of the version operating for the application and the difference from other versions.
In the present embodiment, it is possible to easily grasp the range of possible impact of changing the software A2 using the IT resource management system, and it is easy to grasp the software that actually affects. As a result, it is possible to correctly change the affected range, and it is easy to estimate the cost.
In this embodiment, the employee in Tokyo, who is the proposer, is set as an accessible person, and other persons are not permitted to change the information related to the A2, A2E, and A2F of the IT asset configuration management system database. For this reason, the information in the database is kept in a correct state, and IT resources can be correctly operated.

  This embodiment is the same as the first embodiment with respect to basic settings and document history management.

(Consideration of change)
After the change according to the first embodiment, an employee in the accounting department of company X notices that software D having a function similar to that of software A3 is commercially available, and that operating expenses can be reduced by replacing A3 with D. It was.
In order to examine the function of A3 in detail, the employee searches the history of documents of software A, and outputs the difference between A1 and A3 and the difference between A2 and A3.
As a result, it was found that the extended function was added and the change related to the change function was performed.

When the specifications of the commercially available software D were investigated, it was found that the change function was supported but the extended function was not provided. The extended function is frequently used in X, and its effect is high.
The employee considered that replacing A3 with commercial software D was a loss overall, and decided not to replace it with D.

(effect)
According to this embodiment, the following effects can be obtained.
In this embodiment, since the documents of the software A are managed in history and the difference between versions is searched, it is possible to easily grasp the expansion and change of functions performed from A1 to A3. As described above, there is an effect that the absolutely necessary function can be accurately grasped when replacing software.

  In this embodiment, the basic setting and the history management of documents are the same as those in the first embodiment.

(Consideration of change)
The Paris base has a branch office in Berlin. A Paris-based IT manager considered the need for localization of software A2 in German.
The IT manager in Paris decides to localize to German as an extension of A2F, accesses the IT asset configuration management system database, and confirms that the A2F manager is the IT manager in Paris. did.

(Perform changes)
The IT manager in Paris developed a version of A2G that was localized to German at his own responsibility and added A2G information to the IT asset configuration management system database.

(effect)
According to this embodiment, the following effects can be obtained.
In this example, it was easily understood that the person responsible for the software A2F was the person responsible for IT in Paris. As a result, the development that can be processed in the department such as the base can be settled in the department, and an effect is obtained that rapid processing is possible.

  This embodiment is basically the same as the first embodiment in basic setting, document history management, and proposal and approval of changes. Information on access management of the database of the IT resource configuration management system is added to enhance safety when executing the change. Hereinafter, differences from the first embodiment will be described.

（変更の検討における実施例１との相違点）

ＣＩＯは、社員をＩＴ資産構成管理システム上のＡ２、Ａ２Ｅ及びＡ２Ｆに係る項目のアクセス可能者として設定するに当たり、合わせてシステムキーを設定する。設定後のアクセス管理は表１１のとおりである。

(Differences from Example 1 in studying changes)

When the CIO sets an employee as a person who can access items related to A2, A2E, and A2F on the IT resource configuration management system, the CIO also sets a system key. Table 11 shows the access management after the setting.

(Difference from the first embodiment in execution of change)

In developing the software A3, A3E, and A3F, an installer is also developed. The installer stores the system key value that is requested at the time of installation as a system key value (not a predetermined fixed value) in the database of the IT asset configuration management system. Created to use the value obtained by accessing.
When installing A3, A3E and A3F, the employee accesses the database of the IT resource configuration management system to know the value of the system key and input it.

(effect)

According to the present embodiment, a person other than the employee who can be accessed cannot know the value of the system key and cannot perform the installation. It is possible to prevent an accident in system operation caused by a person other than the accessible person accidentally installing A3.

In addition, since the CIO can change the value of the system key even after the development of A3 is completed, it is possible to prohibit the installation by an employee who can be accessed if necessary.

(Extended example)

The embodiments of the present invention are not limited to the above-described embodiments, and other embodiments that extend the above-described embodiments are possible. An example of such extension is shown below.

In the first embodiment, the software A2 is changed, but instead of this, a new software (referred to as “D1”) may be developed or introduced. In this case, the information related to D1 is added to the software information shown in Table 2, and the software having the dependency and the data having the dependency are set based on the design of D1. As a result, the possible range of development or introduction of D1 can be specified, and the same effect as in the first embodiment can be obtained.

In approving the change, the drafting and settlement are performed using the approval system, and the approval system refers to the database of the IT resource configuration management system, and only the proposal by the accessible person is processed. It is also possible to respond to a request for approval and prevent an incorrect request from being made.

As information related to the software shown in Table 2, the cost required for the development and operation of the software may be retained and used for measuring the cost effectiveness of the software.

In the first embodiment, the possible range of influence of software is specified, but in addition to this, the possible range of influence of hardware may be specified. Specifically, the possible range of hardware can be specified by detecting the case where the specification of each computer system on which the software A3 operates does not satisfy the required specification of A3.

The IT resource configuration management system of the present invention has the advantages of facilitating management of IT resources and contributing to IT governance, and is therefore expected to be used in a wide range of industries having IT resources.

It is a system configuration diagram of the entire IT resource. (Example 1) It is the figure which showed the process which specifies the influence possibility range of software. (Example 1)

Explanation of symbols

1 Network between bases 11 Step for specifying software 12 Step for searching for software having dependency relationship and adding it to possible range 14 Step for searching for software having dependency relationship with data having dependency relationship 15 Impacting searched software Step 17 of adding to the possibility range Step of outputting the possibility range of influence

Claims (5)

A database system including IT resource configuration information including items relating to two or more computer systems, specifications of the computer system, software operating in the computer system, and data input or output by the software And the database system can search for the IT resource configuration information using software as a key. 2. The IT resource configuration management system according to claim 1, wherein the IT resource configuration information includes documents created when software is developed, and the documents are history-managed. The IT resource configuration information includes version information of the software, the history of the documents is associated with the version information, and the database system includes a version of software operating in one computer system among the documents. 3. The IT resource configuration management system according to claim 2, wherein a part in which a difference from a version of software having the same name operating in another computer system is described can be searched. The IT resource management information includes a dependency relationship between software and data as an item, and the database system searches for another software having a dependency relationship with data having a dependency relationship with the software using one software as a key. The IT resource configuration management system according to claim 1, wherein the IT resource configuration management system is obtained. An accessible person and a responsible person are set in an access management item that is all or a part of the items included in the IT resource configuration information, and the access management item is added only by the accessible person who is approved by the responsible person. The IT resource configuration management system according to any one of claims 1 to 4, wherein deletion or correction can be performed.

Images