JPH10269064A - Management system for distributed information linked with relating information among resources - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent the generation of the inconsistency of versions or the like among distributed resources in the environment of distribution destinations and to improve the convenience of the management and operation of the resources in a distributed system environment, by automatically specifying the resources for requiring re-distribution and the distribution destination in the case that change is generated in information managed by the environment of a distribution origin. SOLUTION: The distribution destinations of respective resources and the result of the past distribution are stored in a data base 103, and when the change is generated in a certain resource, relating information among the resources stored in the data base 103 is retrieved and resources to be affected by the change and the resources requiring the re-distribution are specified. The information relating to the distribution of the resources requiring the re-distribution is retrieved from the data base 103 and the result of the distribution is reflected on the information relating to the distributed result in the data base 103.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for managing information generated during development and information required for maintenance in the field of computer-assisted software engineering.

[0002]

2. Description of the Related Art Conventionally, there have been the following techniques for centrally managing information generated in software development in general.

[0003] Production information such as specifications and programs, management information such as quality and progress, environmental information such as development machines and tools, organization information such as individuals and projects, and information related to a combination of these information are integrated. to manage. As an example of this, there is JP-A-03-256120.

[0004]

In the above prior art, since the resource operation information is not managed, all the resources from development to operation are centrally managed in a centralized manner from development to operation. This is not a problem in a frame-based centralized system, but in a client / server system that distributes resources to machines on a network and distributes processing, it changes information managed by the distribution source environment. The problem is that it is difficult to communicate and reflect the effects of this to the recipients.

[0005] An object of the present invention is to automate the identification of resources that need to be redistributed and their distribution destinations when information managed by the distribution source environment changes, thereby enabling the distribution destination environment to have An object of the present invention is to prevent inconsistencies such as versions between distributed resources, and to enhance the convenience of resource management and operation in a distributed system environment.

[0006]

Means for Solving the Problems In order to achieve the above object, in a device for centrally managing information generated in software development in general, a distribution destination of each resource and a result of past distribution are stored, A mechanism is provided for searching in combination with related information between resources accumulated during development.

Further, in order to facilitate management of information related to distribution, it is possible to define a dependency relationship between resources between distributions.

[0008]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described with reference to the drawings.

FIG. 1 shows the configuration of an embodiment of the present invention and the relationship between them. The function of each component is as follows.

The resource management apparatus 101 includes a resource storage 102
Is a device that stores and manages attribute information of resources stored in the database 103, related information between resources, a distribution destination of each resource and a result of past distribution in the database 103.

[0011] When a change occurs in a certain resource, the affected range search mechanism 104 searches for related information between resources stored in the database 103, and finds resources affected by the change and resources that need to be redistributed. Is a mechanism for specifying

The distribution destination search mechanism 105 is a mechanism for searching the database 103 for information on distribution of the specified resource.

The distribution device 106 is a device for distributing the resources stored in the resource storage 102 to a designated machine and notifying the result of the distribution.

FIG. 2 shows a management structure of information stored in a database in the embodiment of FIG.

The resource attribute information is stored in an object defined for each resource type. Object 202,
203, 204, 205, and 206 are “documents”
Object. A “document” object is an object that stores attribute information of file resources such as specifications and programs. Also, object 2
01 is a “data item” object. A “data item” object is an object that stores attribute information of a data item.

The "document" object and the "data item" object manage version information, and the version number increases each time a change occurs in the resource.

The related information between resources is
The information is stored by associating with a direction and a type.

Association 212 is a "reference" association. The “reference” relation means that the resource of the relation destination refers to the content of the resource of the relation source. Related 213, 21
4, 215, 216 are "generation" related. "Generate"
Association means that the resource of the association destination has been generated based on the contents of the resource of the association source. Therefore, when the “reference” relation or the “generation” relation is established, when a change occurs in the resource of the relation source, the resource of the relation destination is also affected by the change.

Information relating to the distribution of resources is stored in combination of a “machine” object and a “replica” object, and a “distribution” relation and a “holding” relation.

A "machine" object is a machine name or I
An object that stores machine attribute information such as a P address. The “replica” object is an object that stores distribution attribute information such as a distributed version and an installation destination path.

From each resource, a “distribution” relationship is established toward the “replica” object by the number of distributions. In addition, the “replica” object is associated with “holding” toward a “machine” object that stores attribute information of a distribution destination machine.

In FIG. 2, "replica" objects 207, 208, 209 and "machine" object 21
0, 211, “distribution” related 217, 218, 219,
The “retention” relations 220, 221 and 222 are “file M
AIN. EXE must be distributed to machines PC1 and PC2, and versions 1.20 and 1.00 have been distributed, respectively, and file SUB. DLL is machine P
It needs to be distributed to C2, and version 1.10 has already been distributed. "

In the relationship 223 in FIG. 2, when defining a dependency relationship between resources according to the second embodiment of the present invention, the distribution 223 is performed from an object of a higher-order resource to an object of a lower-order resource. Remember by establishing a "subordinate" relationship.

FIG. 3 is a diagram showing an outline of processing when a change occurs in the embodiment of FIG.

When a change occurs in a certain resource, the resource management apparatus 101 instructs the influence range search mechanism 104 to search the influence range of the change (301) and specify a resource that needs redistribution (302). I do.

The influence range search mechanism 104 searches the resources affected by the change by following the "reference" relation and the "generation" relation in the direction of the relation from the resource in which the change has occurred. Further, from among the resources, resources that are related to “distribution” are searched, and resources that need to be redistributed are specified. If some of the resources that need to be redistributed
"Distribution-dependent" if any resources are the source of the association
The resource of the related destination becomes the resource of the redistribution candidate.

The influence range search mechanism 104 stores the resources that need to be redistributed and the resources of the redistribution candidates into the distribution destination search
And instructs to search for information related to distribution (303).

The distribution destination search mechanism 105 refers to the distributed version number stored in the "replica" object of the "distribution" related destination for the resource of the redistribution candidate, and matches with the current version number. If the resource does not need to be redistributed, it is determined that the resource does not need to be redistributed (304). For resources that need redistribution, "Distribute"
Search for related and “owned” related destination “machine” objects to identify the destination machine.

The resource management apparatus 101 notifies the distribution apparatus 106 of the resources that need to be redistributed and the destination machine.

The distribution device 106 performs distribution based on the notified distribution contents (305), and reports the distribution result to the resource management device 101.

The resource management device 101 updates the distribution version number of the “replica” object to the current version number for the resource whose distribution result is successful (306).

[0032]

According to the present invention, when resources managed by one development environment are distributed to another development environment or execution environment and operated, even if the resources of the distribution source are frequently upgraded, the distribution can be performed. It is possible to always keep the previous resources at the latest version, and the burden of managing and operating resources in a distributed system environment is reduced.

Even when distributing a plurality of resources collectively, it is not necessary to redistribute all resources each time, and only the minimum necessary files affected by the change due to the version upgrade can be distributed. Thus, the work load for distribution can be reduced.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of devices and a relationship between them in one embodiment of the present invention.

FIG. 2 is a diagram showing a management structure of information stored in a database in the embodiment of FIG.

FIG. 3 is a diagram showing an outline of processing when a change occurs in the embodiment of FIG. 1;

[Explanation of symbols]

101: Resource management device, 102: Resource hangar, 10
3 ... database, 104 ... influence range search mechanism, 105
... distribution destination search mechanism, 201 ... "data item" object, 202, 203, 204, 205, 206 ... "document" object, 207, 208, 209 ...
"Replica" object, 210, 211 ... "Machine" object, 212 ... "Reference" relation, 213, 2
14, 215, 216 ... "generation" related, 217, 21
8, 219 ... related to "distribution", 220, 221, 222 ...
"Retention" related, 223 ... "Distributed subordinate" related, 301 ...
Influence range search, 302: identification of resources requiring redistribution, 303: search of distribution destination information, 304: version comparison, 305: implementation of distribution, 306: reflection of distribution results.

Claims (2)

[Claims] An apparatus for centrally managing information generated in software development as a whole, accumulating the distribution destinations of resources such as specifications and programs, which are products of each process, and the results of past distribution during development. By managing the information in combination with the related information between the resources, if resources change, the resources that need to be redistributed due to the change and the distribution destinations are automatically identified. A method for managing information related to distribution, which enables efficient distribution. 2. A method according to claim 1, wherein a dependency relation between resources is defined for distribution, and when a higher-level resource is distributed, a lower-level resource can be distributed at the same time. .