JPH06332714A - Self-pr system for object - Google Patents

Abstract

PURPOSE:To handle even a method as one of objects, to facilitate a countermeasure to a processing request having a new purpose by skillfully combining each object based on a still model, dynamic model, and functional model, and to attain the self-PR of each object in order to efficiently reuse the existing object. CONSTITUTION:The objects in a functional model 431 are organized, and a class is generated by a class schema 312 in an inside schema 310 corresponding to the applied processing request. Then, an instance for facilitating a countermeasure to the processing request is generated by an instance schema 316 corresponding to the obtained class, and the instance is executed. At the time of registering each prepared object, information for self-PR is automatically and manually set in a file, the detail contents are outputted according to a request from a user, and the input of necessary data is instructed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an object self-PR system in an object-oriented data processing system.

The real world is regarded as an object model and grasped, and the real world is associated with an extensional external expression and a comprehension,
Place the comprehension in the area where information is hidden, configure the so-called iD information that identifies the comprehension so as to correspond to an extensive adjective, and use the extensional adjective to construct the real world into the object world The static world and the dynamic world are expressed in advance, the system mechanism is given to the static world by a class and / or a composite class, and the dynamic world is given by an instance of the above class and / or a composite class. The present invention relates to an object self-PR method for effectively reusing an existing object in an object-oriented data processing system adapted to give a motion of the dynamic model.

[0003]

2. Description of the Related Art FIG. 19 is a diagram for explaining the advantage of encapsulating an object as in the case of the present invention. For example, taking the execution processing data 214 as an example, as shown in FIG. 19A, the execution processing data is a series of instructions (or a group of instructions).
250 is given as serialized in processing order. Some of these commands (or a group of commands) 250 collectively form a processing unit 251 that executes a predetermined process, that is, performs a certain behavior.

Therefore, the execution processing data shown in FIG. 19A can be regarded as serialized processing units 251 that perform a certain behavior as shown in FIG. 19B. The execution processing data 214 serialized as shown in FIG. 19B is for performing a specific operation as a whole. Therefore, the execution process data 214 for performing another specific process is given as another execution process data in which the processing units 251 having different combinations are connected.

As a large number of existing processing units 251 exhibiting different behaviors are obtained, as shown in FIG. 19C, individual processing units 251 are integrated under a predetermined method M as necessary. By doing so, it is possible to obtain the same operation data 214 as that shown in FIG. 19B.

The relationship among objects, object commands and object parts will be described in advance. Less than,
More specifically, the relationship between the object, the object command, and the object part according to the present invention will be described.

FIG. 20 shows an example of modeling in the real world, for example, a company department. In FIG. 20,
In the frame representing “employee”, for example, there is a “secretary” belonging to “job type = 1”, a “leader” belonging to “job type = 2”, and a “job type = 3”. There are “workers”. The "employee" frame belongs to the "team" frame.

"Leader" is related to "team" under the relationship of "team leader", and "worker" is related to "worker / machine" within the framework of "work unit". Related to "machine".

Further, "team" and "machine" are related under the relation of "machine / workplace", and "worker" and "machine" are also related under the relation of "machine / worker". Related by. Furthermore, “employee” is related to “department” under the relationship of “department / employee”.

Further, "employee" is "employee / attribute".
Under the relationship of "affiliation", the "work unit" is related to "part" under the relationship of "work unit / part".

Furthermore, (1) "department" is related to the object "department name" and object "dollar", and (2) "team" is related to the object "name" by the team identification number. , Related to the object "employee number" by job type, related to the object "code name" or object "surname" by name, related to the object "dollar" by salary, and the object "dollar" by average salary "," The object "number" by the average number of departments
(3) “Secretary” is related to the object “number” by typing speed, (4) “Affiliation” is related to the object “name” by name, and the object “year” by age. Related,
(5) "Part" is related to the object "Part number" and object "Dollar", (6) "Work unit / part" is related to the object "Number" by quantity, (7) "Work unit" Is related to the object "time" by the required time, (8) "machine" is related to the object "machine number", the object "dollar" and the object "machine name", and (9) "machine / labor". Is associated with the object "time" by the time of use.

In general, the model shown in FIG. 20 has a circle mark as “behavior” (or a method), a square mark as “data”, and a diamond mark as “relationship”.
It can be represented as shown in 1. That is, (1) method a and data I are combined to serve as one larger data IV, and (2) methods b and c are related to data II by the relationship α, and one larger data IV Acts as V, and (3) methods c and d are related to data III by the relation β, and one larger data
Acts as VI, and (4) method e is related to data IV, V and VI by the relation γ, and one larger data
It acts like VII, and can be represented in the form of being grouped together, entangled, and forming a larger group.

The circles, corners and diamonds shown in FIG. 21 can be handled as objects one by one. Considering a collection such as method a and data I shown in FIG. 21, consider encapsulation as shown in FIG. In FIG. 22 (A), a hole formed above the capsule indicates that a message can be exchanged. If the upper hole of the capsule shown in FIG. 22 (A) is covered, it corresponds to data IV which is a collection such as method a and data I shown in FIG. The data is shown at the left end of FIG. FIG. 22
When the method M is added to the data D at the left end of (B) to obtain a compound object, the data becomes the data shown in the center of FIG. 22 (B), and the method is added to the data and compounded. When the object is obtained, it becomes what is shown at the right end of FIG. The composite thus formed corresponds to FIG.

The manner in which compounding is performed is not limited to the form shown in FIG. For example, when the data D in the leftmost object in FIG. 22C is replaced with an object composed of a method and data,
(C) It is the second one from the left end. In this case, message passing is required between the illustrated method M ₁ and data D _1, and 3 from the left end of FIG. 22C.
The method M ₁ becomes one object as shown in the second. As a result, the object C and the object B exist in the object C, and the message passing exists between the object A and the object B.

Furthermore, in the illustrated object B
Method M is object B₁And on object B
Data D in object B₂Then, as shown in FIG.
(C) In the object B, the object
Ject B₁And object B ₂And exist,
Bect B₁And object B₂Between the message
The structure is such that there is a thing.

As described above, the so-called atomic object, which will be described later, is compounded into, for example, a capsule object, the capsule object is compounded into, for example, an event object, and the event object is compounded. For example, the system
It becomes an object ... It is compounded one after another.

In the above, what is shown as the data D is generally a plurality of processing target units, and what is shown as the method M is how to use the plurality of processing target units. It may be considered as information or a group of information to be instructed. In FIG. 22, what is expressed as an object is an individual “processing target unit” or a “processing target unit” that can be treated as a single integrated processing target unit.

As shown in FIG. 21, the individual objects I, II, III are larger objects IV, V, respectively.
Form part of a VI. In addition, the object IV, V, VI
Also forms part of the larger Object VII.
In other words, objects IV, V and VI are objects respectively.
Seen from VII, “Is ...
Relationships represented by “is (a)” and “part of (part)
-Of) ".

When considering the illustrated objects I, II, and III as the minimum units, these objects I, II, and III are so-called atomic objects. When they are collected, what is called a capsule object is formed, when those capsule objects are collected, what is called an event object is formed, and a larger system object is formed.

Each of these objects is generically called a composite object. The atomic object is also included in the concept of the compound object.
However, the atomic object is an object of the minimum unit as described above, and when it is generally called a compound object or simply an object, it may be considered that an atomic object that exists as a non-decomposable simple substance like the atomic object is excluded.

The encapsulated object described above is generally an encapsulation of the composite object. The individual objects can be represented by the following model. That is, FIG. 23 is an explanatory diagram of modeling an object.

Some real-world things, such as photographs, can be identified by the name representing the photograph and the nature of what the photograph is, for example, who photographed what time. it can. And the picture is
(I) A command as a name to specify the photograph, and (i
i) The entity of the picture (entity data) consisting of so-called black and white dots, and (iii) the nature of the photograph, the place where the entity of the picture is stored, and the like It can be modeled and grasped with a link that describes the relationship between multiple people who are present.

The individual objects described above can also be modeled and represented by commands, links and entity data, as shown in FIG. Figure 2
4 is a diagram for explaining the function of the modeled object. As shown on the left side of FIG. 24, an object can be represented by a command, a link and entity data, and it can be considered that dot data as shown in the figure is given to the entity data. The above-mentioned capsule object, event object, and system object are generally other objects X, as entity data, as shown on the right side of FIG.
A description specifying Y and Z is given, and the object is associated with the other object X, Y, Z and the other object X,
The Y, Z entity data x, y, z are used.

In the real world, as illustrated in FIG.
Objects that correspond to individual “processing target units” or “processing target units” that can be handled as one integrated processing target unit by combining individual processing target units are intricately related to each other.

With this point in mind, attempts have been made to use individual pieces of information or a group of pieces of information in association with each other for each purpose of processing. On the other hand, in the conventional software utilization technology, effective use of programs (libraries) accumulated in the past is essential for improving software productivity.

FIG. 25 is an explanatory diagram when a conventional component (library) is used. (a) is a case where a library in a procedural program is used, and when the main program A is created, a main library B in which a large number of previously created main programs are stored and programs of various functions are stored. An attempt is made to create a program that is efficient in using the function library C. In this case, in order to use the libraries B and C, it is necessary to know all their contents (including variables) in advance.

(B) is a case of object-oriented programming, in which an existing class library E is used to design an object D. In this case, an object is created in the format of "instance creation + message" for the object compounded in the class library E, in which the class variable and behavior are specified.
For that purpose, it is necessary to know beforehand the class variables and the types of behaviors being manipulated by using a browser or the like.

[0028]

As described above, the method is treated as one of the objects in order to use the individual information or the group of information in association with the processing for each purpose and to use them in combination. Based on static model, dynamic model and functional model, we can propose a new object-oriented data processing system that can process individual objects skillfully in combination for processing requests with new purposes. . On the other hand, it is required that such an object can be effectively reused, and the conventional method shown in FIG. 25 has the following problems.

(1) Reuse of a function library in a procedural program and a class library of an object-oriented program cannot be performed unless all contents are known. Therefore, you must check the variables beforehand in a procedural program with a browser or the like, and in the case of an object-oriented program, check the variables and the types of behaviors they have and use them.

(2) Conventionally, there is no idea that information representing details of contents is provided in a program, and since it is prepared only in the form of a document, the program itself can automatically publicize (promote) its own contents. Can not.

(3) Since there is no idea to specifically draw out comments in the program, it was not possible to see even if only comments were needed. (4) Due to the above (1) to (3), it was not possible to reuse already made parts, especially those made by others.

The present invention relates to a new object-oriented data processing system which can process individual objects in combination in response to a processing request having a new purpose based on the above static model, dynamic model and functional model. It is an object of the present invention to provide a self-PR system in which each part (object) can automatically inform the user of various information such as a part attribute based on its own variables, purpose and comments.

[0033]

FIG. 1 shows the principle configuration of an object-oriented data processing system according to the present invention. Reference numeral 310 in the figure is an internal schema that generates a class or a composite class corresponding to a processing request given a new purpose, and also generates the generated class or composite class (hereinafter, for simplicity, both Instance may be represented) is generated.

Reference numeral 410 represents a static world, 420 a dynamic world, and 431 a functional model. The real world is regarded as an object model and is grasped, and the real world is associated with an extensional adjective and a comprehension. (I) In the region where the comprehension is information hidden, the existing method 313 is used as a functional model 431. And class 302 are stored in the system (newly created methods and classes are also stored), and (ii) extensional adjectives are stored in the system as static world 410 and dynamic world 420. Has been incorporated into.

The static world 410 has a plurality of methods 313.
And the class 302 are grouped as a class corresponding to a new processing request, and the classes are combined to provide a system mechanism for executing the new processing request. In the dynamic world 420, the instances corresponding to each class are combined in the processing order for executing the new processing request,
It provides a dynamic model for running the system as sessions are created.

In the figure, reference numeral 312 is a class schema, which is a functional part for generating a class, and 313 to 315 are methods, which are taken in by the class schema 312 as constituent elements of the class corresponding to the new processing request. Method.

Reference numeral 316 is an instance schema, which represents a functional portion for generating an instance associated with each of the classes corresponding to the new processing request.

Reference numeral 303 is an instance, 414 is a state table, 415 is a causal relation constraint group, and 416 is a class variable / constant. The state table 414 describes the hierarchical relationship of a plurality of classes taken in as constituent elements, and links the used class variables / constants to the system assembled to correspond to the new processing request. You can think of it as being present. A causal relation constraint group 415 is also written in the state table 414 and describes causal relations that are constraints in executing a session in the illustrated dynamic world 420. For example, when executing the instance b, the causal relation that the instance a must be executed, etc. is described.
In executing the session, the causal relationship is checked.

Reference numeral 600 denotes a self-PR function unit according to the present invention, which facilitates the use of each as a reusable component (object) when a class to be processed, a composite class, a session, etc. are created and registered. Therefore, it is equipped with a function to automatically or partially set data representing the contents of parts from each side, and to provide information about parts requested by the user and request data input to the user. There is.

[0040]

When it is instructed to build a system corresponding to a new processing request, each class that is a constituent element of the system is generated. In generating each class, for the class schema 312,
The name of the method or class required to configure the class and a pointer pointing to the method or class are given. Then, the necessary methods and classes are fetched from the functional model 431 to the internal schema 310 side. In response to the generation of the class, the instance schema 316 generates the instance required to execute the class. Then, each generated instance is associated with a class that uses itself.

Each of the generated classes has a static world 41
Within 0, it is connected to the state table 414 and is a component in the system assembled to meet the above new processing request. The illustrated class 302 'represents the class that is the component. On the other hand, the dynamic world 42
In 0, each instance 303 is combined in time series and a session is assembled in order to execute the system. Then, the system is executed by executing the session. Alternatively, by assembling the session, the system is ready for execution.

As described above, the class and the composite class corresponding to the new processing request are generated, but these are held as the functional model 431 and are used for assembling the system corresponding to the further new processing request thereafter. Will be done.

Generated in each of the generation of each class or composite class that is a constituent element of the above system, the generation of an instance required to execute the class, and the generation of a session in which each instance is combined in time series. Each part (object) is registered, but at that time, the self PR function unit 600 operates. The self-PR function unit 600 automatically generates an object in which input data is collected by automatically using the data that configures the generated parts such as variables, purpose, type, comments of the registered parts, and specifications of the program. To do. This object has a self PR function and is provided corresponding to each registered part. Self PR
When the user makes a usage request for a part group, the function unit 600 extracts the object having the PR function corresponding to the requested part and executes the object to explain the contents of the requested part (object). Information to be provided, input requests for variables, etc. are presented to the user to publicize the contents, and at the same time, the user is requested to make necessary inputs, and the requested parts are made executable.

[0044]

EXAMPLE FIG. 2 is an explanatory view for explaining a static world and a dynamic world. The real world (for example, a user's request) is, as modeled in FIG. 46, an inclusive 402 that gives concrete information expressing the real world, and an extensional adjective that simply expresses the real world 400. 401 and 401 can be associated and modeled. In exchanging information, for example, in exchanging information about a certain real world 400, if the inclusive 402 of the real world 400 is understood by each other, an extension of the real world 400 It is enough to give the external letter 401. That is, it is not necessary to notify the other party of specific information, but it is sufficient to notify the other party of the name of the real world 400.

FIG. 2A is an explanatory diagram for explaining the static world and the dynamic world. In FIG. 2 (A), the inclusion 402 is
For the above reason, as shown in FIG. 2 (A), information is generally hidden, which corresponds to the “world of information hiding” 430. On the other hand, the real world represents a “static world” 410 that gives a mechanism of the real world 400 and a causal relationship in the mechanism, and represents a temporal movement of the real world or a plurality of sessions. Can be modeled with a "dynamic world" 420 that indicates whether or not to allow parallel processing of. Then, the "static world" or the "dynamic world" and the above-mentioned "information hiding world" are associated with each other by an extensional suffix 401, as shown in FIG. 2 (A).

Furthermore, the inclusion 402 is a world of information hiding and contains data that defines the meaning of an extensional affix. The real world is simulated using this extensional adjective, that is, an extensional adjective containing a certain meaning. that is,
It is a static model corresponding to the "static world" and a dynamic model corresponding to the "dynamic world".

FIG. 2B is an explanatory diagram for explaining the relationship among the static model, the dynamic model, and the functional model. Figure 2
The static model 411 shown in (B) is a model corresponding to the static world 410 shown in FIG. 2 (A), and the dynamic model 421 is also a model corresponding to the dynamic world 420. Further, the information hiding world 430 shown in FIG. 2A is associated with the functional model 431.

A static model is formed by specifying the mechanism of the system and designing the relations (templates) such as "is-a" and "part-of" described above. Then, a functional design is obtained, and a class 302 (or a class obtained by further compounding a plurality of classes-combined class) shown in FIG. 1 is designed in a corresponding form.

In the dynamic model, a specific processing target unit (instance) is formed by allocating the instance data in the above-mentioned class 302, and the temporal order relationship between the processing target units is designed. Formed by. Then, a constraint due to a causal relationship is given between the static model and the dynamic model.

Existing method 313 and class 302
Alternatively, the newly created class is retained as a functional model 431 and is used to build up a system corresponding to newer processing requests thereafter. These methods and classes are dynamically built up as a system and used. Finally, the dynamic object processing will be described.

FIG. 3 is a diagram for explaining a part of the operation in the dynamic object processing section. The above methods and classes are held in the component attribute file 205 as object components 206 as shown in FIG. 10 described later. The dynamic object processing unit shown in FIG.
Processing is performed using the object component. Needless to say, in the case of the present invention, as described above, it is possible to appropriately combine the object parts 206 or the object parts 206 in a composite form.

Reference numeral 212 shown in FIG. 3 denotes a dynamic object processing unit, which is a temporary operation mode 216 for performing simulations, an instant operation mode 217 for performing tests, and data processing or communication processing with other terminals. It has a production operation mode 218 for performing.

Reference numeral 205 is a parts attribute file, and reference numeral 205 'is a compilation of all or part of the contents of the parts attribute file 205 so that the actual operation can be executed at high speed. It holds the execution process data 214. In the case of an object program for processing execution, the execution processing data 214 is generally a series of processing units consisting of several tens to several hundreds of steps, which are so-called serially combined.

Reference numeral 213 is the above-mentioned object, which is generally the same as the above-mentioned atomic object, the above-mentioned capsule object state, the above-mentioned event object state, or the above-mentioned event object state. Corresponding to each of the system object states. The object 213 is stored in the form of the object part 206 as specified by the object command.

Reference numeral 215 represents a direct object processing expansion processing, and the individual objects 2
13 is expanded, or a plurality of objects are expanded together to obtain the execution processing data 214.

As described above with reference to FIG. 19, the object is generally grouped in the form of a composite object into units to be processed, and becomes a unit that exhibits a behavior for executing a process having a certain purpose. Then, they are in the form of an object component 206 specified by the object command 201 as shown in FIG.
It is stored in.

In the case where a system (corresponding to a new processing function) is created corresponding to a new processing request, a new object is created or a new object is created so that the processing corresponding to the new processing request can be executed. The existing object is purposely combined and the object exhibiting the new processing function is the object part 2 described above.
It is prepared as one of 06.

Regarding the generated object,
A process is performed such as performing a simulation as to whether or not the device actually functions correctly, or performing a tentative operation when the simulation is completed. This processing is the temporary operation mode 216 shown in FIG. 3, and the dynamic object processing unit 212 uses the content of the component attribute file 205 to simulate the corresponding processing operation.

Regarding the object 213 or the group of objects which have been normally operated in the temporary operation mode 216, the processing speed is slow as it is because it requires a lot of communication with the object management unit (see FIG. 4) in actual operation. To the execution processing data (EXE data) 214 (compiled into one EX
E data). The expansion processing is performed in the illustrated direct object processing expansion processing 215 and stored in the component attribute file 205 ′.

Dynamic Object Processing Unit 212
In the case of using the contents of the component attribute file 205, when it becomes necessary to temporarily perform a proxy process or a test process for a predetermined process, the above direct object process expansion is performed. Process 2
15 may be activated to generate execution processing data 214, and the processing may be performed. Such a processing mode is shown in FIG.
Is shown as instant operating mode 217.

Further, the production operation mode 218 shown in FIG.
This is a mode in which the actual processing operation is performed using the illustrated execution processing data 214. It should be noted that the meta data in the component attribute file 205 describes the semantic data regarding the property of the object, and the upper object (the object indicated by “is-a”) as viewed from its own object. Relations and lower-level objects (“part-
It may be considered that there is a description that indicates the connection relation for the object group indicated by “of”.

FIG. 4 shows the structure of the terminal station. Code 10
Reference numeral 1 denotes a terminal station which performs processing execution using the execution processing data 214 or communicates with another terminal station via a line. Further, reference numeral 103 represents a line such as a LAN or a switched line.

In the terminal station 101, there are further a communication / reception processing unit indicated by reference numeral 219, an object management unit indicated by reference numeral 220, a display indicated by reference numeral 221 and a hyper language processing unit indicated by reference numeral 222.

The illustrated directory processing unit 204 is a command / link processing unit, and is also called a directory processing unit. When one new object is created, a command (object command) corresponding to the designated name of the object is set, a storage location of the actual data 203 and the meta data 202 is allocated, and a command link table is created. At this time, the type of the object is determined and the size is determined. Then, using the command link table, the meta data 202 and the actual data 203
Allows input and output of the combination with.

The (temporary operation support) shown in FIG. 4 is a support function corresponding to the operation up to the temporary operation mode 216 shown in FIG. The illustrated hyper-language processing unit 222
Has a "part display / selection" function, which searches the display object 221 for available object parts and outputs them. If there is no suitable object, a new object part is designated by using the "part designation" function.
Class object parts can be created by the "Attribute setting" function, and instance object parts can be created by the "Schema" setting function.

The "component display" function using the display 221 includes (i) a table of contents that outputs the name and comment of the metadata of the object component, and (ii) a schema and attributes indicating the contents of the object component. Display of,
(Iii) There are indications of class attributes and instance constants.

In addition, the "component combination" function by the hyper language processing unit 222, that is, in order to combine object components to obtain a larger composite object component, an attribute addition / modification / deletion function for class creation is prepared. The function to add / change / delete the schema is provided for creating instance constants.

In the "user screen creation" function by the hyper language processing unit 222, when creating and displaying a screen,
Put screen data in the buffer of "Creation and display" class and create an instance. Therefore, the "user screen creation" function is equivalent to instantiating the screen class.

In the "provisional operation" function of the hyper language processing unit 222, when an instance receives a message, the message is linked with the method indicated by the class to temporarily realize a capsule (see FIG. 45) on the primary memory, and Try to execute the behavior that it has.

Further, the function of "part change" in the hyper language processing unit 222 has an internal schema 310 shown in FIG.
It corresponds to the function of.
This is a function to change object parts by adding or deleting. In addition, the "part registration" function is used for the part attribute file 2
05, a function of registering the object component in association with an object command (which is the name of the object component).

The "expansion (compilation)" shown in FIG. 4 is the direct object processing expansion processing 215 shown in FIG.
Is represented. In the expansion processing, the execution processing data 214 is expanded as large as possible according to the size of the primary memory of the data processing device.

The object management unit 220 controls the hyper language processing unit 222 shown in FIG. 4 to hold the object component 206 in the component attribute file 205 as described above, and controls the dynamic object processing unit 212 to temporarily store it. Operation mode 216 or instant operation mode 21
7 and the actual operation mode 218 are performed. Also,
In response to the message reception via the line 103, the instance is activated in the temporary operation mode, the data processor is operated by temporarily encapsulating on the primary memory, and the result of the processing is transmitted as a message. . Of course,
If there is already expanded data in the execution processing data 214,
Execute it and send a message to the partner terminal.

In the processing in the own terminal station 101, if the desired object component does not exist in the own terminal station 101, has no attribute, or has no schema, the other end station receives a message via the line 103. After being transferred,
Learning is carried out at the place where it is taken into the own terminal station 101.

FIG. 5 is a diagram showing an example of generation processing of classes and instances in the internal schema. Reference numeral 20 in the figure
Reference numeral 3 is actual data (entity data), and 204 is a command link processing unit.

Reference numeral 300 shown in FIG. 5 is a conceptual schema, which is a conceptual representation of the information hierarchical relationship considered in the present invention. Reference numeral 301 is a metaclass, which is prepared in the present invention so as to be able to generate a class into which a method can be appropriately changed.

Reference numeral 302 is a class, and if the class concerned is for a passenger car, it is considered that various methods concerning a passenger car are variably taken in and treated as one class. Reference numeral 303 is an instance, for example, class 3 for passenger cars
This is a drawing showing a processing program created for a specific passenger car by giving individual specific data to the generic name data used by each method loaded in 02.

Reference numeral 310 is an internal schema, which is configured inside the data processing apparatus as a schema corresponding to the above-mentioned conceptual schema 300. Reference numeral 311 is a metaclass method, which is a method for generating a desired individual class. Reference numeral 31
Reference numeral 2 denotes a class schema, which corresponds to one generated class and describes method IDs of various methods that are changeably incorporated into the class, and the various methods are used. Describes the sequence schema that indicates the order relationship.

Reference numerals 313, 314, 315 ... Represent methods, and each method 313, 314, 315
Are linked with the method ID on the class schema 312 to form a class method group used in the class.

Reference numeral 316 is an instance schema. In the instance schema 316, the class name of the class (for example, 312) related to the own instance schema 316 is described, and the instance data required by the method used in the class (the above-mentioned entity (May be considered as data 203) is described by linking with each method ID. Reference numeral 320 is pop-up data,
The pop-up data is extracted and written as instance data in the instance schema 316.

For example, when an attempt is made to generate a class 302 relating to a passenger car and an instance 303 related to the class, the following process is performed. Consider the various methods (think of these methods that already exist) that the person (operator) who tries to generate the class think of at that time as the methods necessary to generate the class. . The considered thing may be considered as the illustrated metaclass 301.

The operator inputs to the metaclass method 311 that a class related to a passenger car is to be generated, and also inputs the various method names that have been thought of to the metaclass method 311.

Correspondingly, metaclass method 3
Reference numeral 11 describes on the class schema 312 that it is a class related to passenger cars, and also describes method IDs corresponding to the above-mentioned various method names. At the same time, the metaclass method 311 is a sequence schema for instructing the usage order of various methods used in the class, and a message transmission method that the class may need when communicating with others. The respective IDs of are automatically described in the class schema 312.

Corresponding to the generation of the class schema 312, each method ID has its own method 313, 314.
... is pointed, and a class is generated. In addition, regarding the generated class, it is possible to freely delete, replace, or add the method to be used. Further, the metaclass method 311 may be considered to be activated from the side of the class to be generated.

Furthermore, the class schema is invoked from the above-mentioned class name (name of the class with which the self is related) described in the instance schema 316, and the instance class used in various methods used by the class. Data is sequentially input and described in the instance schema 316. It should be noted that this operation may be considered to be performed by the operator by prompting the operator to input each instance data from the class side. Of these instance data, the data that has not been registered as the pop-up data 320 up to that point is automatically registered on the pop-up data 320, and is available for subsequent use. Be prepared.

The data on the instance schema 316 is linked with the method ID on the class schema 312. Needless to say, the instance data on the instance schema 316 is deleted, exchanged, or added as needed. Also, if the method used by the class changes, it will change accordingly.

With the above configuration, it is possible to appropriately use the methods while generating a desired class, changing the method used in the class, and changing the instance data.

A method for performing each desired data processing is formed, a plurality of methods are combined to form a class, and further, a plurality of classes are combined to form a composite class as necessary. Or has been. As described above, these are placed in the world of information hiding shown in FIG.

In forming a class, as described with reference to FIG. 5, a class name is specified in the class schema 312 and used in the class corresponding to the method setting (changeable). The method ID of the method to be imported is described. In addition,
The method ID and each method 313, 314, ... Can be linked. Also, the sequence in which each method is executed is set.

An instance schema 316 is formed corresponding to a specific process. That is, the class name of the class that uses the instance is described in the instance schema, and individual instance data is described.

In response to the formation of the above class and the formation of the instance schema, the static world has a certain state table 4
Classes and methods chained under 14 and variables and constants 416 associated with each method exist. Also, if necessary,
It is related to other classes under the above-mentioned "is-a" relationship and "part-of" relationship. Furthermore, a constraint group that gives a causal relationship will be set.

In the dynamic world, when a session is created, the processing order is specified, and when parallel operations are performed, the timing for that is specified. FIG. 6 is an explanatory diagram illustrating a state in which a class is generated from a metaclass. Reference numerals 300, 310, 3 shown in FIG.
11, 312, 313, 314, 315 and 316 are shown in FIG.
It corresponds to the one shown in. Reference numeral 317 is a message transmission method, 318 is a gasoline cost calculation method shown as an example, and 319 is an object management unit 220.
3 shows a sequence table provided in the table. Reference numeral 220 represents an object management unit.

As described with reference to FIG. 5, the class name of the class to be created is set and the method used in the class is specified using the metaclass method 311. At the same time, message transmission method 3 for the class to communicate with others
17 and the like are automatically set, and the order relation of each method used in the class is set.

Correspondingly, the class schema 312
Method ID for each imported method above
The message transmission method ID and the sequence schema are described. Then, each ID and each method are linked.

A specific processing program is formed by specifying an instance using the created class. In the case shown in the figure, an instance that captures a specific instance corresponding to the class "car"
A schema 316 is prepared.

When a message using a predetermined instance schema is given to the object management unit 220, the object management unit 220 activates the instance (takes in the instance schema) and is described in the instance schema. The illustrated class schema 312 is linked from the illustrated class name, and the sequence schema in the class schema 312 is taken into the sequence table 319.
After this processing, the object management unit 220 examines the contents of the sequence table 319, sequentially uses the required method, and uses the contents of the instance schema 316 to process the instance corresponding to the message. .

FIG. 7 is an explanatory diagram for explaining a state of creating an instance from a class. The reference numerals shown in FIG. 7 correspond to those in FIG. Class 3 as described with reference to FIG.
When the method to be incorporated into the class is specified corresponding to 02, the class schema 312 is created in the internal schema 310, and the methods 313, 314, ...
・ Is linked.

In short, the class created in this way, for example, the class related to "car", is a data storage area that is still empty and in which rewritable instance data can be set, and various processes related to cars. It can be thought of as consisting of a group of methods for performing. And
By setting specific instance data in the data storage area of the class created in this way, the instance (specific processing program in which the instance data is used) is created. The specific processing program is the illustrated instance.

When creating an instance, the instance data used in each method is set on the instance schema 316. Then, the content of the set instance schema is linked with the method ID on the class schema 312. This causes the method in the associated class to be executed using the contents of the instance schema 316. A specific processing program (instance) can be executed. The execution is performed by the object management unit 22.
0 is the instance schema 316 and each method 31
, 314 ... Are activated.

In the case of the present invention, as described above, the metaclass
Using the method 311, the class name of the class to be created is input, various methods to be loaded into the class are mutably loaded, and the class is created in a desired form as appropriate. That is, a desired class is created by appropriately combining the methods. In the example of the processing program, the class can be considered to be a processing program in which the instance data is still described in the form of a variable.

In the processing program in the state where the class, that is, the instance data is still described in the form of a variable, the one completed by designating the specific instance data corresponding to the variable is specified. It is a processing program for performing the processing of. The processing program in which the variable is set to a constant is the above instance. By setting the instance data in the above-mentioned instance schema 316 to be rewritable, a desired instance is appropriately created.

FIG. 8 is an explanatory view for explaining the clothes (rolls) of the method. As described with reference to FIG. 5, the procedure world corresponding to the inclusion is associated with the object world through the extension. Further, as described with reference to FIG. 22, the method itself constitutes one object. The method is also present in the procedural world.

However, when a method is handled alone,
If it exists only in the method itself, when is the method born or disappeared (live / dead), whether it should be made resident (open / closed), and other information It is often unclear where to receive the input data (Input) or where to output the output data (Output).

For this reason, a verb (V in the drawing) or a complement (C in the drawing) that indicates the operation of the method is described together with the method itself (M in the drawing) to form one object. The verb V and the complement C are referred to as method clothing in the present invention.

FIG. 8A shows that the method is located in the procedure world as an object. Further, FIG. 8B shows that, in the method incorporated in a certain class, the clothing of the above method is described and the function of independently performing data output and data input is given. ing.

The clothing of an object provides a life cycle function for a method to act as an object independently. Having the life cycle function makes the object autonomous. That is, the garment allows the method selected by the operator through the extension to acquire the condition for allowing the operator to operate. In short, it is for preparing the data acquisition means for the selected method itself to instruct the operator to acquire the necessary data.

The clothing of the object includes "Life", "Open / Closed", "Input", and
In addition to "Onput", other methods include (i) "Send message" to notify the end of an object when it operates, and (ii) the request function including the clothing of the object. It has "sequence control" etc. that gives the processing order of.

As described above, by the action of the class schema and the instance schema, it is possible to freely combine a plurality of existing and / or newly generated methods to build a system corresponding to a desired processing purpose. Will be done. However, each method or class stored as a functional model in the information hiding world 430 (these are all objects)
It is necessary to consider so that any operator who intends to use it at a later date can easily understand what functions each of them can perform.

Conventionally, there is known a method of storing individual user data on a user data database and managing the individual user data by a database management system (DBMS). There is.

In addition, conventionally, with respect to individual user data under the management of the above-mentioned DBMS, a meta data describing a property (meta data) of the individual user data.
Data database, data dictionary and directory system (DD / DS)
A method of managing the above meta data is known.

In each of these methods, the user data managed by the DBMS and the meta data managed by the DD / DS have been conventionally specified by, for example, a sequence number indicating the data order. . For example,
An object iD is attached to the user data managed by the DBMS, and the object iD is added.
D was usually given by the above sequence number.

Furthermore, with respect to the iD attached to the meta data and the user data, the meta data and the user data are replaced with a system using a simple sequence number (or a symbol having no special meaning). It has also been attempted to express the meaning of the data that the data has by the above-mentioned iD.

FIG. 9 shows the structure of a conventionally known database. Reference numeral 207 in the drawing is a database, 20
8 is a database management system, 209
Is a user data database, 210 is a data dictionary and directory system, 21
Reference numeral 1 represents a meta data database.

As shown in FIG. 9, conventionally, a user data database 2 for collectively storing user data is provided.
09, the database management system (DBMS) 208 performs centralized management,
It performs processing such as generation, deletion, modification, and input / output of user data.

On the other hand, as the number of individual user data increases and the volume of each individual user data increases, in order to explain what role each individual user data has, Meta data is created. Then, a meta data database 211 for collectively storing the meta data is used, and as a unit for centrally managing the meta data database 211, a data dictionary and directory system (DD / DS) is used. ) Is provided.

In the present invention, the above meta-data shown in FIG.
The data and the user data are collectively grasped as the object part 206. FIG. 10 shows a processing mode for handling an object.

The object component 206 in the component attribute file 205 shown in FIG. 10 is the user component shown in FIG.
The user data in the data database 209 and the meta data in the meta data database 211 shown in FIG.
It can be considered that the data and the data are integrated into one so that they can be integrated.
Of course, in the case of the conventional configuration shown in FIG. 9, the database management system 208 and the data dictionary and directory system 210 operate independently of each other. Further, the contents of the user data database 209 and the contents of the meta data database shown in FIG. 9 were individually accessed and used. In the case shown in FIG. 10, the actual data 203 and the meta data 202 shown in FIG. 10 are combined and specified by an object command so that they can be handled as one object part 206.

Individual user data (entity data) on the user data database managed by the DBMS, and individual user data on the meta data database managed by the DD / DS. The idea of combining with the meta data of the above and handling it as an object part is being proposed.

Objects to be handled as the object parts include a so-called atomic object, which is a minimum scale object, and a sequentially complexed capsule object, event object, system object, and the like. For this reason, the object to be handled becomes extremely complicated and complex, and when a certain object is given, what kind of property the object has,
In other words, the situation may be such that only the person in charge of generation can judge.

From such a situation, regarding the meta data and the entity data which compose the above-mentioned object parts, the meta data has a descriptive text of the entity data, that is, a name, a comment, or meaning to a third party. The semantic data model, outline flow, detail flow, source program, etc. to be understood will be described.

Therefore, the object parts generally have a sufficiently large amount of information, and it is desired to give the object parts a name for briefly explaining the contents of the object parts.

In the present invention, a name for explaining the contents of the object part regarding the object which can be compounded is given, and the object part can be accessed by the name.

FIG. 11 shows a block diagram for object management. Reference numeral 101 in the drawing denotes a terminal station which constitutes a data processing device, and 103 denotes a LAN or a switching line for communicating with another terminal station.

Reference numeral 202 is meta data, 203 is actual data (entity data), 205 is a component attribute file, 206 is an object component, and 219 is communication /
A receiver 220 represents an object manager. Reference numeral 214 is execution processing data, which is obtained by compiling one of the object parts or a combination thereof and expanding the data so as to be suitable for the actual execution processing.
Reference numeral 05 'represents the same as the component attribute file 205 and includes the above-mentioned execution processing data 214.

Reference numeral 201 shown in the figure is an object command given in the present invention, which is given as a name for specifying the above-mentioned object component 206.

The object command 201 is roughly classified into a signature (surrogate) and an object iD, and the surrogate is composed of the following parts. That is, (i) header: Designates the number of bytes from the first byte to the number of bytes of a description area, an “is-a” layer, a “part-of” layer, a sequence, and the like described later. (ii) Explanatory text area: A summary of the explanatory text of the object, in which the original meta data of the object is compressed and described. For example, "Who made it?"
This is a compressed view of the portion corresponding to the explanatory text such as "what version?". (iii) “is-a” hierarchy: For example, when “dog is an animal”, the relative position of the dog is expressed by hierarchizing the relationship between the lower “dog” and the upper “animal”. is
-In the "a" layer, the lower "dog" is compared to the upper "animal"
Etc. to indicate the situation that exists. (iv) "part-of" hierarchy: For example, "Honshu", "Kyushu", and "Shikoku" form a part of "Mainland Japan". main land"
The fact that there is a structural relationship that a part of the above is configured is expressed by being positioned by the "part-of" hierarchy. (v) Sequence: A complex combination of objects (compound object) consists of many smaller objects. Such a portion that indicates the execution order (including branch) for a finer group of objects is compressed and expressed. (vi) Object iD: The same iD given to the data stored in the conventional user data database is given.

The object management unit 220 creates a new object part 206 in the part attribute file 205, modifies or deletes an existing object part, and integrates a plurality of object parts into a single object part. In addition to having the functions of grouping into objects and dividing a single object part into multiple object parts, it also has the following functions.

That is, it has a function of communicating with a plurality of objects, ordering the processing order of each object, and performing processing that matches the desired processing purpose. In performing such various processing, the object management unit 220
Specifies each object part by using the above object command 201.

The group of object parts ordered as described above or individual object parts are compiled as necessary to generate execution processing data 214, and data processing in the terminal station 101 is performed. Alternatively, the execution processing data 214 is used during the communication processing with the other end station via the LAN or the switching line 103 (because it is compiled, the file access etc. is small and the processing speed is high). .

The self-PR function of the object according to the present invention will be described. The self-PR function is provided for effectively using not only the parts created by the user but also the parts of others.

FIG. 12 is a schematic explanatory diagram of the self-PR function according to the present invention. When the operator issues a use request to the parts group from the display, each part will self-promote itself by the self-PR function. The contents are divided into the following three items.

Function for inquiring about variables held in each part and requesting input Function for publicizing the purpose, type, comments, etc. of parts according to the operator's request Function for teaching program specifications in response to questions ，
The contents to be taught include detailed explanation, outline explanation, meaning data, management data, usage, and the like.

Although the above is partially explained with reference to FIG. 8A, the information used also for the self PR is drawn out by the clothing (roll) function of the object. In addition, the largest number of information items is given by the component attribute file.

FIG. 13 is an explanatory diagram of the clothing function of the object. As shown in FIG. 13, the clothing function of an object is a function of turning it into an object by passing a program (a normally created program may be used). When made into an object, a list of buffers used by the programs used therein (a in FIG. 13) and a comment list (b in FIG. 13) are created. This is registered in the component attribute file by taking the metadata 0-iD (identification number 0). This makes it possible to check the buffer used by the component (buffer used by the program) and comments at any time.

The objectification by the clothing function includes the atomic objectization process (c in FIG. 13). Atomic objects are hyper-parts, and have independence, orthogonality, abstraction, simplicity, and normality. In other words, this atomic object processing is to make the buffer of the program NULL (flags and real numbers
L) and control parts (eg if t
(Hen, While for, etc.) is removed, it is replaced with the control in the super component, and the separated program is divided into each one.

There are three types of information used for the self-PR function of the component, which are the above-mentioned three types, and all of these three types represent the property of the component (object) as metadata. As shown in FIGS. 10 and 11, the object part, the metadata, and the user data form a part (object) 206 by combining the metadata 202 and the actual data (user data) 203. Although this metadata 202 is created almost automatically, the above data is given by the clothing function of the object as described above (FIG. 13), and the data is a component attribute file (this is automatically generated by the SPEC oriented). It is made by.

The metadata information of the parts will be explained here. As described above, the metadata information is basically automatically created by the clothing function of the object, and the introduction of the use buffer and the purpose of the part (name and simple (Introduction or comment in the program) and the genes contained in the component attribute file. This gene has a name,
Keyword (including abbreviation), description, old metadata data (data for management), semantic data, spatial connection, temporal connection, and component (atom object). Note that the name, keyword, and description may be included in the old metadata (metadata will be described later with reference to FIG. 15).

Semantic data is manually input because it is difficult to automate because parts are grasped by an abstract concept. The spatial connection represents the link data of the composite class, and the temporal connection represents the link data of the composite instance. The component as the entity of the component is represented by an aggregate of atomic components and composite components. However, if you search for deep signature links, they will eventually be represented by atomic components.

FIG. 14 is a diagram showing the construction of a component attribute file for self-PR and PR processing. There are roughly two methods considered for the component creation processing. One of them is user data processing, that is, hyper language processing, and the other is SPEC-oriented component creation processing. FIG. 14 shows an example of the hyper language processing, the contents of which will be described below.

In the hyper language processing 601, the operator operates the display (input / output terminal) 607 to use the atomic object 602 and the compound object 603 to generate a class (or compound class) 604, an instance 605, and a compound instance (or Session) 606. The information at that time is automatically assigned by the automatic sorting function 608 as the metadata 202 of the component of the component attribute file 205. There are seven types of information to be assigned, which are roughly represented by symbols A to G,
Each will be described below.

A: Part name This may be set by the program or may be input by the operator.

B: Component iD Since this is a common word that moves internally, it is automatically given by the user data processing.

C: Metadata This data means management data in the old metadata (metadata of the original part used when creating this time). It relates to DD / DS (210 in FIG. 9) such as who, when, what kind of change, what purpose, etc., and is divided into those that can be automatically created and those that are manually input.

D: Semantic data This is data expressing the contents of the program, and in most cases it is manually input. However, the attributes when creating a class are automatically entered.

E: Data of keyword (KW), description, flow, source, etc. In KW, the attribute name and part name are automatically input, or if the name is desired by the user, it is manually input. It
The explanation and flow are SPEC oriented, and the source is automatically input.

F: Structural data This is a combination of atomic parts and sequence data, and is input from the hyper language processing.

G: Entity data iD As described above, the metadata of the component of the component attribute file is
Hyper-language processing and SPEC-oriented processing (not shown)
About 90% is automatically created and input to the file. The operator re-inputs the remaining data and the data that is difficult to automatically create from the display 607 by the data input processing 609. Among them are the names of the above-mentioned parts, some old metadata, meaning data, KW, explanations, and flows.

The self-PR process 610 outputs the data of the parts attribute file and the contents of the parts (including the source of the program) corresponding to the requested contents when the request is made in the conversation form by the operator, and inputs the necessary data. , Assists in the creation and operation of new programs that require existing parts.

FIG. 15 is a flow chart at the time of program registration by the self PR function, which is executed at the time of registration of the program created by the configuration shown in FIG. When the program registration is executed, only the program or the buffer is taken out, and it is put together in a structure, at the same time, only the comment is taken out in the structure, and further the metadata and the like are input (S1 in FIG. 15). Next, if there is a usage request,
The structure of the buffer is displayed and the data value is input (at step S2). An instance schema is created from these results (at step S3).

FIG. 16 is a block diagram of functional blocks for self PR. Functions b, c and d in FIG. 16 correspond to the process S1 of the flow shown in FIG. In FIG. 16, for the program a to be registered, the function b that takes out the used buffer and makes it into a file, the function c that takes out the comment and makes it into a file, and the input function d of metadata, semantic data and flow, and the source work Registration f is performed. In this case, the display function e on the display controls the display of the contents of each file and the screen for inputting, and the operator can input the contents interactively while watching the display on the display. In addition, by making a request to the registered program by self-PR, processing such as displaying and inputting the content of the corresponding program is performed, the program is registered using the existing program, and the program is registered. Compile g
The execution program (EX
E program) h is created.

In the present invention, the output of each data of the part attribute file becomes the self PR function of the part. The self-PR function is dynamically and interactively output (advised) when the hyper language processing shown in FIG. 14 is operated. For example, when creating a class from a metaclass, you must advise checking the orthogonality of atomic object combinations. When creating an instance from a class, you must request the parameters needed for the configuration. At the end of the session, causal advice is needed. At this time, if the meaning, purpose, movement flow, source, structural data, etc. of the part are requested, advice (help) can be provided using the data of the part attribute file.

FIG. 17 is an operation flow chart for creating a program using the self PR function. In FIG. 17, reference numeral 510 denotes a self-PR function unit, which interactively outputs data in response to a request using the metadata of the component attribute file with the operator.

Explaining the processing, when the operator makes a usage request for a part (object) (S in FIG. 17).
1), the self-PR function unit 510 outputs the name of the registered component (S2). In response to this, the contents of the parts are displayed on the display (at step S3). When the operator selects one component from the table of contents and issues a component use request (at step S4), the self-PR function component 510 checks the variable to be set for that component and requests data entry. (S5). In response to this, the variable name of this component is displayed on the display (at step S6). On the other hand, it is determined whether or not a question has been input by the operator (at step S7), and if there is a question, the content of the question is queried (at step S7).
8). The self PR function unit 510 extracts and outputs the corresponding content in response to this (step S9). That is, contents of variables in the program, comments in the program, contents of metadata, contents of specifications, flows, contents of sources, etc.

The output contents are displayed, and it is judged whether the contents are parts (objects) (at step S10). If they are parts, data such as variables corresponding to the parts are input (at step S11). If it is not a part, the process can return to S8 to ask further questions. When data is input, it is checked that the data meets the predetermined type and definition (S12), and if not, an input request is displayed to the operator (S13). ). If the check is good (OK), the part (program) can be operated.

In this way, a new component is created by selecting a component suitable for the program newly created by the operator from the existing registered components (objects) and setting new data in it. Can be created.

FIG. 26 is a view for explaining an object-oriented design mode existing in the undercurrent of the present invention. Reference numerals 410, 420 and 431 in the figure respectively represent the static world 4 shown in FIG.
10, the dynamic world 420, and the functional model 431 are supported.

: When a request for system design is generated from the user :: A problem corresponding to the request is described, and a scenario for summarizing specifications is created.

[0157] Next, the analysis is performed, and what kind of data is required, what kind of method is necessary and available, etc. are summarized. : Based on the analysis result, in the static world 410, the work of extracting the required class will be performed, and the entity-relation (ER) diagram of the required data and the required method will be obtained. Entity-relationship (ER) diagram is created. The ER diagram is as shown in FIG. Then, the method for the schema is selected based on the ER diagram of the data, and the data and the method are correctly associated with each other based on the ER diagram of the method.

When the ER diagram of the method is obtained, the class is created and registered based on this, as shown in FIG. 1, FIG. 5, FIG. 6 and FIG. In addition, a compound class is created.

Further, in the dynamic world 420, a flow chart for related events is created, and events that can be processed in parallel are determined. And Fig. 1
The instance is generated and the sequence is designed as shown in FIG. 5, FIG. 6, and FIG. Further, a causal relationship is extracted in connection with the determination of an event that can be processed in parallel, and the causal relationship is set in the state table 414 as shown in FIG. 1 and FIG. 21, and reflected in the static world.

The user's request is dealt with based on the instance obtained as described above, but the classes, composite classes, and instances obtained during this period are functional models 43.
It is retained as 1 for future reuse. Also,
When creating the above class, for the methods that are in short supply for the time being, they are registered in order to create and use the insufficient methods and to prepare for future reuse. The creation of the lacking method is performed by the processing as shown in FIG. 1, FIG. 3 and FIG. 4 (processing of the hyper language processing 222 shown in FIG. 4), and the temporary operation is performed to improve the parts while combining the parts. In addition.

FIG. 18 is a diagram for explaining a mode of object reuse. The right half of FIG. 18 is shown in FIGS.
It corresponds to the static world 410, the dynamic world 420, and the functional model 431 shown in FIG. The left half of FIG. 18 shows a technique for combining object parts.

The free combination technique 480 of object parts in the left half of FIG.
6 corresponds to the processing shown in FIG. 6 and FIG. Also meta
The data creation 481 corresponds to the creation of the meta data shown in FIGS. 9, 10, and 11. Further, the object command 201 shown in FIG. 18 is the object command shown in FIG. 11, and is generated corresponding to each object part 206 which is a set of meta data and actual data as shown in FIGS. It

Generated object command 201
Are automatically organized and made freely available.
It is used in the question tool using the self-PR function in the right half object part reuse technology shown in FIG. That is, the required object parts 206 are called in and reused based on the object command.

[0164]

According to the present invention, the following effects can be obtained. When you register a program that you want to use as a component, the program will automatically perform PR afterwards, so you can reuse programs created by others.

Since the purpose, specifications, etc. of the program can be understood without knowing the contents of the program, and the purpose (meaning) and the size of the type are taught to the data to be input, the method of creating the program and the contents It is easy to reuse without knowing.

If you find that the explanation is insufficient,
Since it is possible to add the metadata, it is possible to manage who modified the modification, when, and why.

A program already created can be reused by passing the self PR function of the present invention.

[Brief description of drawings]

FIG. 1 shows a principle configuration diagram of the present invention.

FIG. 2 is an explanatory diagram illustrating a static world and a dynamic world.

FIG. 3 is a diagram illustrating a part of the operation in a dynamic object processing unit.

FIG. 4 shows a configuration of a terminal station.

FIG. 5 is a diagram showing an example of generation processing of classes and instances in an internal schema.

FIG. 6 is an explanatory diagram illustrating a state in which a class is generated from a metaclass.

FIG. 7 is an explanatory diagram illustrating a state of generating an instance from a class.

FIG. 8 is an explanatory diagram illustrating clothing (rolls) of a method.

FIG. 9 shows a configuration of a conventionally known database.

FIG. 10 shows a processing mode for handling an object.

FIG. 11 shows a block diagram of object management.

FIG. 12 is a schematic explanatory diagram of a self-PR function according to the present invention.

FIG. 13 is an explanatory diagram of a clothing function of an object.

FIG. 14: Part attribute file creation and P for self PR
It is a figure which shows the structure of R processing.

FIG. 15 is a flowchart at the time of program registration by the self-PR function.

FIG. 16 is a configuration diagram of functional blocks for self-PR.

FIG. 17 is an operation flow diagram of creating a program using the self-PR function.

FIG. 18 is a diagram illustrating a manner of reusing an object.

FIG. 19 is a diagram illustrating an advantage of encapsulating an object as in the case of the present invention.

FIG. 20 is a diagram illustrating a modeled state of a company department.

FIG. 21 is a diagram illustrating model abstraction.

FIG. 22 is a diagram illustrating a capsule.

FIG. 23 is an explanatory diagram of modeling an object.

FIG. 24 is a diagram illustrating the function of a modeled object.

FIG. 25 is an explanatory diagram of a method of using a conventional component (library).

FIG. 26 is a diagram for explaining an object-oriented design mode that exists in the undercurrent of the present invention.

[Explanation of symbols]

 302 class 303 instance 310 internal schema 312 class schema 313 method 314 method 315 method 316 instance schema 410 static world 414 state table 415 causal constraint group 600 self PR function unit

Front Page Continuation (72) Inventor Masahiko Murakawa 100-1 Sakado, Takatsu-ku, Kawasaki-shi, Kanagawa Fujitsu Network Engineering Limited (72) Masanobu Toyota 100-1 Sakado, Takatsu-ku, Kawasaki-shi, Kanagawa Fujitsu Network Engineering Ltd. In-house (72) Inventor Takeshi Adachi 100-1 Sakado, Takatsu-ku, Kawasaki-shi, Kanagawa Fujitsu Network Engineering Co., Ltd. (72) Inventor Naomi Ichikawa 1015, Uedanaka, Nakahara-ku, Kawasaki, Kanagawa

Claims (3)

[Claims] 1. A single processing unit and / or a composite processing unit obtained by combining a single processing unit is named an object, the objects are combined, and desired processing is executed by an object-oriented program or a procedural program. In the data processing system, the real world is regarded as an object model and grasped, the real world is associated with the extensional exposition and the comprehension, the comprehension is placed in the information hidden area, and the comprehension is specified. Is associated with an extensional adjective, is associated with the extensional affix, and the real world is represented by a static world and a dynamic world that make up the world of the object. For the dynamic world, the system mechanism is given by using a class and / or a composite class as a static model. As a model, the above class and /
Alternatively, a session corresponding to the movement of the dynamic model is given by using an instance of the composite class, and the above class and / or composite class is configured by combining a plurality of existing and / or newly generated methods, Self PR for configuring the above instance by associating with each and / or composite class and reusing the object of the existing program as a component
A functional unit, each class and / or composite class,
When it is desired to register an instance and a session as a component, an object is created corresponding to each component, which is a set of user data and metadata including self-PR input information, and the self-PR function unit requests the use of the component. On the other hand, the contents of the requested parts are output using the created metadata, and the necessary parts are created by inputting the data necessary for creating the parts to the output contents. A self-PR method for the featured object. 2. The object self-PR system according to claim 1, wherein the self-PR function unit outputs a list of registered parts when a usage request for the part is generated, and one part is selected for the list output. Then, the variable to be set and the input request are output in the relevant component, the purpose, type, and comment of the relevant component are output in response to the request for the relevant component, and the comment, the explanation, and the flow for the question about the specifications of the program , A source, management data, usage, etc. are output, and a self-PR method of an object is characterized in that it is possible to input after checking whether or not it meets a predetermined specification for data input. 3. The program according to claim 1, when registering a program to be a part, only the buffer in the program is taken out, and its file name, type, size, etc. are extracted as one structure, Only the comments of the above are taken out as one structure, and data such as the personal identification number of the creator and the creation date are automatically set, and external names, keywords for search, comment text for explanation, specifications, flow, meaning A self-PR method for an object, characterized in that data and data such as a screen configuration to be displayed are manually input, and the structure and the input information are stored in a component attribute file as metadata corresponding to the component.