KR19990025291A - Computer-aided Software Engineering Model Information Management System and Its Operation Method - Google Patents

Abstract

The present invention relates to a CASE model information management system for a computer-assisted software engineering (CASE) tool information repository, and a method of operating the same. The present invention can store information about various types of models of a CASE tool in a standardized form. When there is a model search, the information about the model can be provided, and the information storage can be used to develop a CASE model information management system that allows the information repository to retrieve data from the physical storage location and provide it to the tool user. In order to effectively operate the CASE model information management system, the CASE model information is expressed in a formal form, and for this, the specification of the CASE model is utilized in memory when the development support tool system is driven. Management system develops specifications, data structures and approaches As a result, all models to be supported by the CASE tool can be specified.In order to store this specification, the information storage management system can identify the system of model information managed by the database management system, and the model information desired by the CASE tool. Since it can be found and provided, it can increase efficiency and productivity by preventing duplicate management of CASE model information and reducing change management cost due to change of model information.

Description

Computer-aided Software Engineering Model Information Management System and Its Operation Method

The present invention is a computer aided software engineering (CASE) tool model information management system for the operation of the information storage (RESORT / D), which is a sub-system of the object-oriented reengineering software development support tool (RESORT) And its operation method. In particular, it is characterized by specifying model information used in the CASE tool to provide consistency and extensibility of the model information system.

The data used in the CASE tool is a model, and the CASE tool supports the whole process of software development, analysis, design, and implementation.

The user can make software development more convenient by using the model used for analysis and the model used for design.

Information about a model is called metadata, which is data about data and describes and defines the data.

Information repositories have the ability to store and manage this metadata.

Therefore, the information store stores the information about the model in the physical information store and supports the CASE tool to retrieve the desired information while having the information about the model.

The existing research center (RESORT) analyzes the source code of the developed system (Legacy System) and displays it as design information, and reorganizes the design information into objects supporting the object-oriented paradigm to create a new system. It is an engineering software, and the information repository (RESORT / D) is a paradigm such as design information of existing system and reorganized object-oriented design information. do.

The CASE tools, however, use different models depending on the methodology and notation they support.

Therefore, the repository should have information about all the models, and when the model is added or changed, the repository should be rebuilt, which requires a lot of effort and time.

The CASE tools have different methodologies to support the software development process, and thus provide different models.

The conventional CASE information repository does not support an integrated model management method, and stores the necessary information for each tool, resulting in duplication of information and a lot of efforts to maintain integrity when changing information.

In order to solve the above problems, the present invention can store the information (Information) about the various types of model (Model) of the tool in a form, and when there is a model search of the user of the tool (model) in the corresponding model It can provide information about the data, and by using this inquiry result, information storage is to develop CASE model information management system to retrieve data from physical database and provide it to tool users.

1 is a system configuration to which the present invention is applied,

2 is a model information conversion flowchart conceptually illustrating a process in which CASE model information of the present invention is transformed and managed in a system;

3 is an exemplary diagram of a specification expressing a meta-meta model and a model in text for CASE model information to be managed by the CASE model information management system of the present invention;

4 is a data structure diagram for on-memory management of CASE model information according to the present invention;

5 is a process flow chart for registration of CASE model information according to the present invention;

Figure 6 is a flow chart for the extraction of CASE model information according to the present invention.

Explanation of symbols for main parts of the drawings

100: Information storage (RESORT / D)

110: tool interface

111: information storage interface

112: reverse engineering interface

113: Object Restructuring Interface

114: Area Modeling Tool Interface

120: CASE Model Information Management System

121: register

122: lookup

130: information storage management system

140: database management system

150: database

200: model

201: metamodel

202: physical data storage

202a: file or table

203: specification of tool models

300: tool

301: Model

302: purpose

303: relationship

304: list node

305: tree (root)

In order to achieve the above object, the present invention provides a tool interface for receiving data from a CASE tool and outputting required data, a CASE model information management system for managing information on the model itself, and a tool from a CASE model information management system. And a database interface for accessing the physical disk from the database through a query and processing the data.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

1 is a system configuration diagram to which the present invention is applied, a tool interface 111 for receiving data from a CASE tool, outputting required data, and a CASE model information management system 120 managing information on the model itself. ), The information storage management system 130 for obtaining information of the model required by the tool from the CASE model information management system, and the database interface 140 for processing data by accessing a physical disk from the database 150 through a query word. It is composed.

FIG. 2 is a model information conversion flowchart conceptually illustrating a process in which CASE model information of the present invention is transformed and managed in a system. The concept of model information managed by an information repository will be described as follows.

CASE tools differ in their methodologies to support the software development process, and thus provide different models 200.

The information repository derives an integrated meta model 201 from these models and stores it in the form of a table or file 202a on the physical disk 202.

The parts of data that are to be kept permanently from the metamodel 201 are converted to an efficient storage system on the physical disk 202, and information about the type of the CASE tool itself must be managed for retrieval of model information from the storage system. The CASE model information management system was invented for this purpose.

In order to operate CASE model information management system effectively, various factors must be provided.

First, CASE model information should be expressed in a standardized form. For this purpose, specification of CASE model information is required.

This specification is also used in memory when running the RESORT system.

Therefore, a data structure is needed to be managed in memory, and an access method is needed to utilize this data structure.

To satisfy this, CASE model information management system developed specification, data structure and approach.

Referring to FIG. 3, the specification is a formal specification of the target data to be managed, and the category expressed by the specification is defined and defined for meta-meta data, which is data constituting a metamodel. It refers to the specification of the relationship between the model and meta-meta data, etc. According to the above specification has a hierarchical structure.

Among the symbols used in the Meta-meta Model, which is a diagram of meta-meta data, the rectangle means MetaObject, the line means MetaRelationship, and the lozenge includes the relationship. Contain is a symbol that has meaning, and the relationship between the objects made up of this symbol is also called metaAggregation.

It is a notation based on the notation of Unified Modeling Language among object-oriented models.

That is, the Meta-meta Model of CASE model information consists of the MetaObject and MetaRelationship.

Types of MetaObject include Tool (300), Object (302), and Relation (303). MetaRelationship types include Container, Source, and Destination.

Among the MetaObjects, the relationship between the Tool 300 and the Object 302 may be only MetaAggregation, and the relations that the Relation MetaObject may have are Souce and Destination.

All MetaObjects, including Relation MetaObjects, have the same specification.

That is, it has a Type that says the type of MetaObject and a Name that says the name of the MetaObject.

If MetaObject is a Tool, an instance can be a name such as RESORT / R, RESORT / O, and so on.

If the MetaObject is a Model, names such as Structure Chart, Control Flow Graph, and Class Diagram can be instances.

And as relation information between MetaObject and MetaObject, it has Container that points to MetaObject that contains MetaObject.

Class Diagram of the UML For example, if the type of MetaObject is an object and its Name is calss, the value of Container is a class diagram.

Relation MetaObject is a MetaObject having relational information. Since a relation has relativity, it has a Source and Destination specification as a specification for representing a Source and a Destination among MetaRelationships.

Source is an instance name of MetaObject and must be defined in MetaObject.

Destination is an instance name of MetaObject and must be defined in MetaObject.

FIG. 4 is a data structure diagram for on-memory management of CASE model information according to the present invention. Referring to the data structure model, the data structure of the specification to be represented in the memory will be described. In addition, the memory structure for providing a service uses a tree structure and a list structure in parallel to quickly access data. The tree structure can be used to query and dynamically generate models.

Since each MetaObject can exist in plural, Container relationship, such as the relationship between Tool MetaObject and Model MetaObject, uses Tree structure using List structure.

Among the symbols used in the model representing the data structure, the rhombus indicates inclusion relations, the black rhombus indicates that there is more than one component, and the hollow rhombus indicates that there may be no components.

In addition, the triangle symbol represents the inheritance of the object-oriented concept. The tool 300, the Model 301, the Object 302, the Relation 303, and the MetaObjects are all List Nodes 304. Say.

That is, one or more identical MetaObjects have a List structure, and each Node consists of itself and a pointer to the next Node.

FIG. 5 is a flow chart for registering CASE model information according to the present invention, and receives MetaOnbject (S1) and determines whether it is a Relation MetaObject (S2) In the case of Relation MetaObject, it is determined whether it has a Source and a Destination MetaObject (S3). ).

If the source and destination after the determination, it is determined whether the source and Detination exists (S4), if present, it receives all the MetaObject to determine whether the container of the MetaObject exists (S5) and creates a MetaObject Node if present. (S6) It inserts in the trip (S7), and the position is inserted as a child node of the container metaObject pointed to by the input metaObject.

If the source and the destination do not exist or the source and the destination do not exist after the determination, and if the container of the MetaObject does not exist, an error message is generated (S8) and terminated.

Next, referring to FIG. 6, when the name of the model to be searched is input (S9), a position search is performed from the tree (S10), and an empty MetaObject List is generated (S11).

After creating an empty MetaObject List, extract the MetaObject having the object to be found as a container (S12), add the found MetaObject to the MetaObject List (S13), determine whether all the corresponding MetaObjects are found (S14), Transfer the found MetaObject list to the information repository management system (S15).

As described above, according to the present invention, all models to be supported by the CASE tool can be specified, and the information storage management system can identify the system of model information managed by the database management system. The tool can find and provide the desired model information.

Therefore, it is possible to increase efficiency and productivity by preventing duplicate management of CASE model information and reducing change management cost due to change of model information.

Claims (7)

In computer-assisted software engineering (CASE) tool model information management for the operation of information storage (RESORT / D), which is a sub-system of object-oriented reengineering software development support tool (RESORT), A tool interface for receiving data from a CASE tool and outputting required data; A CASE model information management system managing information about the model itself; An information repository management system for obtaining model information required by the tool from the CASE model information management system; CASE model information management system comprising a database interface for processing the data by accessing the physical disk from the database through a query. According to claim 1, wherein the CASE model information management system CASE model information management system, characterized by providing model information used in the CASE tool to provide consistency and extensibility of the model information system. According to claim 1, wherein the information storage management system CASE model information management system, characterized in that to derive an integrated meta-model from the models and to store in the form of a table or file on a physical disk. In the operation method of the CASE tool model information management system for the operation of the information repository, which is a sub-system of the object-oriented reengineering software development support tool, A first step of defining a specification to be utilized on a memory when the RESTORE system is driven to represent the CASE model information in a standardized form; Developing a data structure for managing the specification on memory; And a third step of developing an approach for utilizing the data structure. The method of claim 4, wherein the first step is The meta-meta data, which is the data that constitutes the meta-model with a formal description of the target data to be managed, A method of operating a CASE model information management system, characterized by defining a relationship between a metamodel and meta-meta data. 5. The data structure of claim 4, wherein the specification of the specification to be represented in the memory of the second stage A method of operating a CASE model information management system, which uses a tree structure and a list structure in parallel to quickly access data in order to provide a service while staying in memory while the RESORT system is running. The method of claim 4, wherein the third step In case of registered model by inputting the name of the model to find, find all MetaObjects that have as container, Insert the found MetaObject into the list of MetaObjects and repeat the process of finding the MetaObject with the found MetaObject as the Container. The method of operating a CASE model information management system, characterized in that if all MetaObjects are found, the list of metaobjects is returned to the information storage management system.