JPH08292884A - Repository device - Google Patents

Abstract

PURPOSE: To maintain no contradiction of a logical model at a high level and improve the reliability and stability of the device by effectively checking a document halfway in operation by linking the logical submodel corresponding to the individual document with the document and managing it. CONSTITUTION: A logical model management part 24 generates a common work area 28 in a work area management part 21, and holds and manages the logical model 22 here, and a logical submodel management part 25 generates an individual work area 29 in the work area management part 21, and holds and manages the logical submodel 23 here. The logical submodel management part 25 can use extracted part of the logical model 22 (meaningful structure of plural documents) in the common work area 28 as the logical submodel 23. This logical submodel 23 is made to correspond to the document halfway in operation.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a repository device for managing documents used in software development.

In each scene of a software development cycle such as analysis and design, a software developer describes one required problem and a system for solving the problem in a plurality of types of documents. Also, a large problem or system may be described by dividing it into multiple documents of the same type. The information that these documents have in common can be expressed by one logical model. A repository device that supports software development stores and manages this logical model.

Recent CASE (Computer Ai)
ded Software Engineering)
With the spread of tools, there is an increasing demand for repository devices that can efficiently manage documents created with the CASE tool. Information common between the documents created by the CASE tool needs to be accurately reflected in the logical model stored in the repository device. Furthermore, when working on multiple documents in parallel, it is necessary to detect the effect of changes in one document on other documents and maintain consistency between the documents.

[0004]

2. Description of the Related Art CASE tools provide different types of editors suitable for each developer according to the software development cycle. Then, the data input to each editor is saved as a file as it is.
The data stored in the file includes semantic information and graphic information. Semantic information includes information that can be commonly used in each phase of the software development cycle, and if this information is extracted and used well, it will increase the productivity of software that is developed and constructed by division of labor. You can

In the conventional repository apparatus, semantic information is extracted from the data input to the editor, and common information is associated between a plurality of documents.
A plurality of related semantic information are stored as one model. Semantic information can be grasped as a set of individual objects, and the model of associated objects can be grasped as one logical model.

[0006] FIG. 6 is a diagram for explaining the prior art, and exemplifies the process of developing a deposit management system. Figure 6
In (a), the developer M uses the box representing the object from the editor P to describe the object called the customer and the object called the deposit account, and the connection representing the ownership is used to describe the object called the customer as the deposit account. Describes owning an object. The information extracted from this document x is stored in the repository device.

In FIG. 6B, another developer N uses the table to define the details of the deposit account from the editor Q, and describes that the number and the amount belong to the deposit account. The information extracted from this document y is also stored in the repository device. FIG. 6C shows a model of a semantic data structure in which the document x by the editor P and the document y by the editor Q are associated with each other. The repository device uses this semantic data structure, that is, a logical model. Was born to preserve.

The logical model managed by the repository device is changed or added at any time. For example, it is assumed that the developer M saves the document z shown in FIG. The repository device extracts an object called a customer, an object called a checking account, and the fact that there is an ownership relationship between them as semantic information, and updates the logical model.

[0009]

When updating the logical model, the repository device should create a new class called checking account, or the existing deposit account class name should be changed to the checking account class name. I do not know whether to change to. What is passed from the CASE tool is the data of the document z shown in FIG. 6D. However, on the repository device side, how to change the logical model only from the semantic information extracted from the document z is determined. I do not understand.

In the repository device, the semantic information extracted from the document z is fetched in some form based on its design and specifications. At that time, at least the function of maintaining the consistency of the logical model is maintained. Is desired. For example, a method of logically checking a document in the middle of work to maintain the consistency of the logical model can be considered. Although some CASE tools have such a function, it is necessary to individually modify the CASE tools, and the work load thereof is enormous.

According to the present invention, a link is provided between a document being processed and a repository device, and the document being processed is efficiently checked, thereby maintaining a high consistency of the logical model and improving reliability and reliability. The purpose is to provide a repository device with excellent stability.

[0012]

According to the invention, the above-mentioned object is achieved by the means described in the claims.

That is, according to the invention of claim 1, as shown in the schematic explanatory view of FIG. 1, in the repository device for storing and managing the logical model 12 in which the semantic information across a plurality of documents is associated and managed, A logical submodel 13, which is a partial logical model corresponding to the document,
The repository device 10 is provided with a management unit 11 that links and manages the document.

Further, the invention of claim 2 is a repository apparatus provided with a management unit having means for checking the consistency of a logical submodel related to a document when the document is updated. The invention provides a management unit having an impact detection unit that detects, when a document is updated, whether a change in the logical submodel related to the document affects the logical submodel related to another document. It is a repository device.

Further, the invention according to claim 4 is provided with a management unit having means for checking the consistency of the logical model based on the updated contents of the logical submodel related to the document when the document is stored. The invention is a repository device, and the invention of claim 5 includes a management unit having an impact detection unit that detects an influence on a logical model when the document is saved, based on the update content of the logical submodel related to the document. It is a repository device provided.

According to the invention of claim 6, when providing the logical model, the remaining part of the logical model excluding the logical submodel relating to the document being updated, and the logical submodel relating to the document being updated. It is a repository device provided with a management unit having means for providing a combination of the above.

[0017]

According to the first aspect of the invention, the repository device for accumulating and managing the logical model manages the logical sub-model which is a part of the logical model and corresponds to an individual document. With this repository device, a logical sub-model related to the document is associated with each individual document.

In the conventional repository apparatus, the information on the way of working of each document is held as a file outside the repository apparatus, so that the document on the way of working cannot be directly managed by the repository apparatus. However, in the second aspect of the invention, the logical check of the document in the middle of work is performed as a function of the repository device.

Further, in the conventional repository device, since the information of the document held in the file and the logical model are separated, it is possible to detect which part of which other document is affected by the change of one document. I couldn't. According to the third aspect of the present invention, the influence of the change in the document in the middle of the work is instantly detected from the relationship between the logical sub-models.

When the document is saved after the work is completed, the updated contents of the document reflected in the logical sub-model are reflected in the logical model. At this time, claims 4 and 5
In the invention, the consistency of the logical model is checked or the influence on the logical model is detected. In the invention of claim 6,
A logical model is presented separately for a part that can be referred to and a part that can be updated as well as referenced.

[0021]

FIG. 2 is a diagram showing an embodiment of the present invention. In the figure, the repository device 20 includes a plurality of CASE tools 5
0, 51, 52 are connected. The work area management unit 21 configuring the repository device 20 has a shared work area 2 accessible from a plurality of CASE tools in response to a request.
8 or an individual work area 29 accessible from an individual CASE tool is generated and managed. Logical model management unit 24
Causes the work area management unit 21 to generate a shared work area 28, and holds and manages the logical model 22 therein.

The logical sub-model management unit 25 causes the work area management unit 21 to generate an individual work area 29 and holds and manages the logical sub model 23 therein. The logical sub model management unit 25 uses the logical model 2 in the shared work area 28.
A part of 2 (semantic structure of a plurality of documents) can be taken out as a logical submodel 23.
This logical sub-model 23 is associated with the document in the process of work. The repository device 20 uses the logical submodel 2 in the individual work area 29 after the completion of the document creation.
3 is written back to the logical model 22 in the shared work area 28.

When the second document is opened on the CASE tool side, the logical submodel management unit 25 generates a second individual work area, and the logical submodel having a logical structure corresponding to this is created. Can be held. At this time, the original logical model 22 (including the logical submodel) in the shared work area 28 can be referenced from any of the individual work areas. In the individual work area, the logical submodel can be updated without being aware of other individual work areas.
The logical model 22 in the shared work area 28 remains in its original state until the document work is completed and the logical submodel corresponding to the document is written back.

The influence detection unit 27 detects which part of which other logical submodel is affected by changing the logical submodel 23 in the individual work area 29. Furthermore, when the document is saved, the logical submodel 23 of the individual work area 29 is shared by the shared work area 2
8 is written back to the logical model 22, and the influence of this writing back on the logical model 22 is also detected.

Logical submodel 2 in individual work area 29
3, it is possible to detect which part of which other logical submodel is affected by the change of the logical submodel 23. When the documents related to each other are edited in parallel, the repository device 20 can notify the people who are working on the affected documents of the result by looking at the result of the influence detection.

The check unit 26 logically checks the document. Then, this check can be performed using the logical submodel 23 in the individual work area 29. Therefore, it is possible to check the consistency while working on the document. Of course, it is possible to detect a contradiction even when the logical sub-model 23 is written back to the logical model 22, and it is possible to prevent the logical model 22 from being inadvertently changed.

FIG. 3 is a detailed explanatory view of the function realizing means.
Here, the repository device is designed with object-oriented software. The notation of the illustrated object model diagram is based on Rumbaugh's OMT method. In the figure, the repository class 30 owns a logical model class 32, and the logical model class 32 owns a logical submodel class 33. Logical model class 32
Alternatively, the logical submodel class 33 performs a checkin operation for writing back the logical submodel of the individual work area to the logical model to the work area management class 31, and a check for extracting the logical submodel from the logical model of the shared work area.
Instruct an out operation.

In FIG. 3, the logical model class 32
Performs logical model consistency check and impact detection operations at the logical model level. The logical submodel class 33 performs logical submodel consistency checking and impact detection operations at the logical submodel level.

FIG. 4 is an event trace diagram when a logical model and a logical sub model are newly created. In FIG.
First, when the creation of a new document with the CASE tool starts, "create a new logical model" in the repository device.
Request is issued. The logical model management unit creates the shared work area and the logical model, and returns the shared work area name and the logical model name.

Next, the CASE tool requests the repository device to "create a new logical submodel" using the shared work area name as a parameter. The logical submodel management unit creates an individual work area and a logical submodel, and returns the individual work area name and the logical submodel name.

Here, the CASE tool is presented with a logical model created by combining the logical work model of the shared work area, excluding the logical submodel of the individual work area, and the logical submodel of the individual work area. be able to. The logical model of the shared work area, excluding the logical submodel of the individual work area, can be referenced only, and the logical submodel of the individual work area can be updated as well as referenced.

FIG. 5 is an event trace diagram when updating the logical submodel. In FIG. 5, first, when the update operation of the existing document is started by the CASE tool, a request for "update logical submodel" is issued to the repository device.
The logical sub model management unit creates an individual work area and checks out the logical sub model, checks the logical sub model, and returns the logical sub model name.

While the CASE tool continues to update the document, the logical submodel management section
Continue self-checking for updated logical submodels.
Between the logical model management unit and the logical submodel management unit,
Correlation check is also performed. If the correlation check is successful, the logical model management unit NGs the logical sub-model management unit.
Is notified, and this NG is further notified to the CASE tool.

The CASE tool causes the repository device to analyze which part of another document the object in the updated document will affect, and corrects the logical submodel based on the result. Finally the document is saved,
Chec of logical submodel with correlation check OK
When the "hin" operation is executed, the logical submodel of the individual work area is written back to the logical model of the shared work area.

[0035]

As described above, according to the repository apparatus of the present invention, the document and the logical submodel are linked by managing the logical submodel which is the logical structure of the document in the middle of work. You can do document work in it. At this time, the original logical model in the shared work area can be referenced from the other individual work areas.

Further, by using the logical submodel in the individual work area, it is possible to perform a logical check of a document in the middle of work and a consistency check with other documents at any time. Furthermore, by using the logical submodel in the individual work area, it is possible to instantly detect which part of which logical submodel is affected by the change of the logical submodel.

As described above, when working a plurality of documents in parallel using the CASE tool, it becomes extremely easy to maintain the consistency between the documents, so that the work efficiency of the documents is improved and the software productivity is improved. It can be greatly increased.

[Brief description of drawings]

FIG. 1 is a schematic explanatory diagram of the present invention.

FIG. 2 is a diagram showing an embodiment of the present invention.

FIG. 3 is a detailed explanatory diagram of a function realizing means.

FIG. 4 is a diagram showing a process of creating a logical sub model.

FIG. 5 is a diagram showing a process of updating a logical sub model.

FIG. 6 is a diagram for explaining a conventional technique.

[Explanation of symbols]

 10, 20 Repository device 11 Management unit 12, 22 Logical model 13, 23 Logical sub model 21 Work area management unit 24 Logical model management unit 25 Logical sub model management unit 26 Check unit 27 Impact detection unit 28 Shared work area 29 Individual work area 30 repository class 31 workspace management class 32 logical model class 33 logical submodel class 50, 51, 52 CASE tool

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Ryusei Kondo 1015 Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Within Fujitsu Limited (72) Inventor Hiroyuki Yoshida 1015, Kamiodanaka, Nakahara-ku, Kawasaki, Kanagawa Within Fujitsu Limited

Claims (6)

[Claims] 1. A repository device for storing and managing a logical model in which semantic information of a plurality of documents is associated with each other, wherein a logical submodel, which is a partial logical model corresponding to an individual document, is linked to the document. A repository device characterized by comprising a management unit for performing management. 2. The repository device according to claim 1, wherein the management unit has means for checking the consistency of the logical submodel associated with the document when the document is updated. 3. The influence detecting means for detecting, when a document is updated, whether the change of the logical submodel related to the document affects the logical submodel related to another document when the document is updated. The repository apparatus according to claim 1, further comprising: 4. The repository device according to claim 1, wherein the management unit has means for checking the consistency of the logical model based on the updated contents of the logical submodel related to the document when the document is saved. . 5. The management unit according to claim 1, further comprising an impact detection unit configured to detect an influence exerted on a logical model when the document is saved, based on an updated content of a logical submodel related to the document. Repository device. 6. The management unit, when providing a logical model, combines the remaining part of the logical model excluding the logical submodel related to the document being updated and the logical submodel related to the document being updated. 2. The repository device according to claim 1, further comprising means for providing a copy.