JP2002163119A - Information processing system, object management method, operating system, and record medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique capable of minimizing various effects in an information processing system caused by the addition of a task and easily adding the task. SOLUTION: The tasks in the information processing system are divided into a first group of tasks depending on application software and a second group of tasks not depending on the application software of each software component, and group numbers for identifying individual groups are allocated to individual groups. ID numbers having identifiability only in their belonging groups are allocated to individual tasks. When a task is added to the prescribed group, the ID number of the task in the group may be merely reallocated, and the reallocation of the ID numbers of all tasks in the information processing system is not required.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a technique for constructing an environment for executing predetermined processing on an information processing system including a computer in the computer.

[0002]

BACKGROUND OF THE INVENTION An information processing system is provided for controlling hardware connected to the information processing system, executing processing of input data, and controlling output of processed data. Various software is installed. Software is generally configured by combining tasks and software components in order to perform various processes. A task is the minimum unit of processing. The software component includes a plurality of tasks for sharing processing, and the tasks are implemented in cooperation to realize processing as a software component. To execute a task, an event flag, a semaphore, and the like for synchronizing the tasks are required. Such event flags and semaphores are also provided in the software component. These tasks and operation elements of software components such as event flags and semaphores are referred to as “objects” in this specification. For example, TCP / IP (Transmission Control Protocol / In)
processing of various communication protocols such as
There are those that control screens and manage files.

When constructing an information processing system, an ID is assigned to each object to identify the object.
(Identification) numbers need to be assigned. The ID number is assigned for each type of object, such as an ID number for a task and an ID number for an event flag. Since only one ID number is set in the information processing system, by specifying the ID number, it is possible to specify a target object and execute the processing by the object. The ID number is managed by the operating system to control the processing by the object.

[0004] Registration of software components in the information processing system is performed as follows. As an example, a case where two software components are registered in the information processing system will be described with reference to FIG. The first software component registered first includes two tasks (task A and task B). As an example, assume that the ID number of task A is “10” and the ID number of task B is “11”. The second software component registered later includes three tasks (task X, task Y, and task Z). ID number of each task is "12", "13", "14"
And These are registered in the information processing system for each software component. The task and the ID number have a relationship as shown in FIG.

[0005] When a function is added to the first software component and a task C corresponding to the function is added,
The ID number of each task is changed. That is, as shown in FIG. 8B, the ID numbers of the task A, task B, and task C of the first software component are “10”, “11”, “1”.
2, the ID numbers of task X, task Y, and task Z of the second software component are changed to "13", "14", "15".

Task X that constitutes the second software component
When the request is made by specifying the task Y, the request is made by specifying the ID number “13” before the task C is added to the first software component. If task C is added to the first software component, ID number "14"
Make a request by specifying. In other words, the change of the object of the first software component affects the second software component. This is because the ID numbers are managed collectively. Therefore, if an incorrect ID number is specified after changing the ID number, the system may malfunction. In addition, since the ID number may be assigned by the system designer, if the ID numbers are managed collectively, it is necessary to reassign the ID numbers to all the objects when the number of objects increases or decreases.
Inefficient.

An object of the present invention is to provide a technique capable of minimizing various effects in an information processing system caused by the addition of an object as described above and easily adding an object.

[0008]

SUMMARY OF THE INVENTION The present invention for solving the above problems is an information processing system which realizes a predetermined function by specifying each of a plurality of objects and executing a process. This information processing system is divided into a plurality of groups to which different group information is allocated, and IDs for identifying each of the groups.
A plurality of IDs associated with the group information, wherein a table in which ID information and an object name of the plurality of objects to which information is assigned is recorded.
A management unit; and a specification unit that specifies a desired ID management unit from the plurality of ID management units based on the group information and specifies a desired object based on the ID information.

Further, the present invention is an information processing system for realizing predetermined application software by specifying each of a plurality of objects and executing a process. In this information processing system, ID information is associated with an object name of the plurality of objects which are divided into a plurality of groups to which different group information is assigned, and to which ID information for identifying each of the groups is assigned. A plurality of ID management means associated with the group information, wherein the recorded table is recorded;
According to the group information from the plurality of ID management means,
And D specifying means for specifying a management object and specifying a predetermined object based on the ID information.

According to the present invention, even when an object is added, reassignment of ID information only needs to be performed within a group to which the object is added.
Objects can be easily added to the information processing system. Further, since the ID information is managed for each group, it is possible to prevent an illegal request due to the designation of incorrect ID information. The object is an operation element such as a task, an event flag, and a semaphore.

The objects are classified, for example, as follows. (1) The plurality of objects include those included in one or more software components that are configured by two or more objects and perform predetermined processing, and those that are not included in the one or more software components. It is divided into a group of objects for each software component including itself and a group of objects not included in the software component. When a function is added to a software component, the I that is reallocated by the added object
The D information stops at the reallocation within the software component, and the addition of the function for each software component becomes free and easy.

(2) The plurality of objects are divided into a group of objects that depend on the application software and a group of objects that do not depend on the application software. In other words, objects that directly receive requests and return processing results with application software are separated from those that do not. By reducing the number of objects that depend on application software, object registration becomes easier.

(3) The plurality of objects are composed of two or more objects and perform predetermined processing.
There is an object included in any of the above software components and a first object not included in the software component and dependent on application software, and the object included in the software component includes a first object dependent on the application software. There is a third object that does not depend on two objects, and the plurality of objects are divided into a group of the first object and the second object, and a group of a third object for each software component. The method of dividing (3) has both the effects of the methods of dividing (1) and (2). In the case of (3), the table of the group of the first object and the group of the second object includes information indicating which software component includes the second object. When a request for a software component including the second object is issued to the third object, a group including the third component can be easily found, which leads to an increase in processing speed.
For example, when there is an instruction from the second object to execute a process by a third object included in a software component including the second object, the specifying unit may use a table of a group including the second object. The software component including the second object is confirmed, and the third object instructed by the ID management means associated with the group information of the confirmed software component group is specified.

The present invention can also be realized by the following method. That is, a method that is executed in an apparatus that realizes predetermined application software by specifying each of a plurality of objects and executing a process, and is divided into a plurality of groups to which different group information is assigned. A table in which the ID information of the plurality of objects and the object names associated with the ID information identifying each individual in each group are stored in association with the group information, and the table is associated with the group information. Specifying a predetermined object from the table based on the ID information;
It is an object management method.

The present invention can also be realized by the following operating system. That is, in an operating system that realizes predetermined application software by specifying each of a plurality of objects and executing a process, the objects are divided into a plurality of groups to which different group information is assigned, and each of the groups is individually assigned. A plurality of ID management means associated with the group information, wherein a table in which ID information and an object name of the plurality of objects to which ID information to be identified is allocated is recorded; ID by means of the group information from the means
An operating system including: a management unit; and a specification unit that specifies a predetermined object based on the ID information.

The present invention can also be realized by causing a computer to read and execute a recording medium on which the following program is recorded. That is, a computer that realizes predetermined application software by specifying each of a plurality of objects and executing a process is divided into a plurality of groups to which different group information is assigned, and the individual is identified within each group. A process of storing a table in which ID information and an object name of the plurality of objects to which ID information to be assigned is assigned in association with the group information; and storing the group information and the ID from the table.
An example is a computer-readable recording medium in which a program for executing a process of specifying a predetermined object based on information is recorded.

[0017]

Embodiments of the present invention will be described below in detail with reference to the drawings. In the present invention, objects such as tasks are managed based on the concept of software groups.

The software group will be described.
Objects are divided into a group of objects that perform various processes by themselves and a group of objects that perform one process in cooperation with a plurality of objects. Here, the latter is called a software component. The operating system manages the object ID number for each group in the following manner.

An object (first object) that performs processing alone receives various requests from application software and returns a processing result of the request to the application software (depends on the application software). The objects in the software component include an object (second object) that receives various requests from the application software and returns a processing result performed in the software component to the application software (depends on the application software). Application software and other software components include objects (third objects) that do not directly receive requests or return processing results. The third object is the core of the software component, and is an object used for performing a target process of the software component.

The first and second objects are regarded as one group, and a group number “0” is assigned. Also, the third
Objects are divided into groups for each software component, and a group number is assigned to each group. Objects are thus divided into groups. The first and second objects belonging to the group number “0” are assigned a group number “0” and an ID number.

Each group for each software component is assigned a group number after the group number "1".
The third object has a group number “−1” (16) indicating that the third object is unique to the software component to which the third object belongs.
FFH) is assigned when represented by a base number. That is, the third object belonging to the group number “1” is assigned a group number of “−1” even if the group number of the entire group is “1”. The third object is assigned an ID number having distinctiveness only within the group to which the third object belongs.

An object can be specified by combining a group number and an ID number. FIG. 1 shows an example in which objects are divided into groups, group numbers are assigned to the respective groups, and ID numbers are assigned to the objects.

In the example of FIG. 1, the group number and the ID number are represented by 16 bits. When the group number and the ID number are represented by 1234H (H represents a hexadecimal number, the same applies hereinafter), 12H is a group number,
34H is an ID number. The group number “00H”
This specifies the first and second objects, and is 0001H to 00FF in the same manner as the conventional ID number allocation.
H numbers are available. Group number "FFH"
Designates a third object, and FF01
Numbers from H to FFFFH can be used.

FIG. 1 shows tasks and software components of various processes executed by application software.
FIG. 3 is an exemplary diagram when registered in an information processing system. Two software components (first software component, second software component) each including three tasks, and two tasks (task 1, task 2) (first object)
And are registered. Of the three tasks (task A, task B, and task C) of the first software component, task A depends on the application software (second object), and task B and task C are inside the first software component. Unique (third object). Of the three tasks (task X, task Y, task Z) of the second software component, task X depends on the application software (second object), and task Y and task Z are stored inside the second software component. Unique (third object).

In FIG. 1, based on the concept of the software group described above, a group number and an ID number are assigned to each task as follows. Task 1 0001H (group number 0, ID number 0
1H) Task 2 0002H (group number 0, ID number 0)
2H) First software component task A 0010H (group number 0, ID number 1)
0H) Task B FF01H (unique within group, ID number 0)
1H) Task C FF02H (unique within group, ID number 0)
2H) Second software component task X 0011H (group number 0, ID number 1
1H) Task Y FF01H (unique within group, ID number 0)
1H) Task Z FF02H (unique within group, ID number 0)
2H)

The task 1, the task 2, the task A of the first software component, and the task X (group 0) of the second software component are assigned a group number "00H" because they depend on the application software. An ID number is assigned in the same manner as the number assignment. Task A and task X have a group number “00”.
"H" is assigned, but the task in each software component can be designated because it belongs to the first software component and the second software component, respectively.
Task B and task C (group 1) of the first software component are assigned a group number “FFH” because they are unique to the first software component. Since the task Y and task Z (group 2) of the second software component are unique to the second software component, the group number “F”
FH "is allocated.

When task B of group 1 specifies task C, FF02H is specified. Similarly, when task Y of group 2 specifies task Z, FF02H is also specified. Task B and task X have the group number “FF
H ", only tasks within the group to which it belongs can be specified. Therefore, task C and task Z
Are not confused even if the numbers "FF02H" are the same.

The tasks 1 and 2 of group 0 can issue various requests to the same group of tasks A and X, but are different groups and are not the same software component. , Cannot issue a request to task Z. But group 0
Even so, task A can issue requests to tasks B and C because it belongs to the first software component, and task X issues requests to task Y and task Z because it belongs to the second software component. Can be issued.

Although FIG. 1 describes the ID numbers for tasks, the concept of a software group can be similarly introduced to the assignment of ID numbers of other objects such as event flags and semaphores.

Here, when a task (task D) unique to the inside of the software component is newly added to the first software component, the task D is added to the group 1 with the number FF03H.
(Unique within the group, ID number 03H). At this time, although the ID numbers of the tasks in the group 1 fluctuate, the ID numbers of the tasks in the group 0 and the group 2 are not affected. In other words, even if a task is added, it is necessary to reassign ID numbers only within the group to which the task is added, and there is no effect on other groups.
There is no need to reassign ID numbers throughout the information processing system as in the prior art. Thus, by introducing the concept of a software group, it is possible to provide an operating environment in which objects are grouped and processing is performed in each group.

[0031]

FIG. 2 is a block diagram of an information processing system 10 for managing objects based on the concept of the software group as described above. This information processing system 1
0 includes an operating system (hereinafter, referred to as an OS) 20 and application software 30 that implements predetermined processing. The application software 30 realizes various processes by executing objects and software components such as a large number of tasks as shown in FIG.

The OS 20 includes a monitor unit 21 and ID management tables 23a to 23c, and manages and controls ID numbers assigned to each object. Each object is usually assigned a group number and ID by the system designer.
Although numbers are assigned, the OS 20 may automatically assign numbers.

The monitor section 21 corresponds to a specifying means of the present invention, and controls each object by identifying each object for each group number and ID number using the ID management tables 23a to 23c. It also has a pointer 22 for designating an ID management table for managing the ID number of the group to which the object to be controlled at that time belongs.

The ID management tables 23a to 23c correspond to, for example, each of the group numbers "0", "1", and "2", and hold the ID numbers of the objects belonging to the own group in association with the objects. I do. Also, information such as the execution state of the object and which software component it belongs to is held. Therefore, for example, even if the group number “0” is assigned, it can be recognized as another software component.

FIG. 3 is an example of a table stored in the ID management tables 23a to 23c. In the example of FIG.
The D management table 23a represents a table of group 0 corresponding to the group number “0”. A number consisting of a group number and an ID number, a task name, a task execution state,
Which software component belongs is indicated. Number "0
Task 1 of “001H” is on standby and does not belong to any software component. The task 2 with the number “0002H” is being executed and does not belong to any software component. The task A with the number “0010H” is being executed and belongs to the first software component. The number "00
The task X of “11H” is waiting and belongs to the second software component.

The ID management tables 23b and 23c in FIGS. 3B and 3C have the same configuration, and the numbers of the tasks belonging to the groups 1 and 2, the task names, the execution states, and the software components to which the tasks belong, respectively. Is shown.

In the present embodiment, three ID management tables are used. However, this is determined by the number of software components. For example, when there are five software components, the number of objects dependent on the application software 30 depends on the number of software components. When the number of groups is added, the number of ID management tables becomes six, and when the number of software components is one, the number of ID management tables becomes two by adding the group of objects dependent on the application software 30.

The processing performed by the monitor unit 21 will be described with reference to FIG. The monitor unit 21 specifies the ID management table 23a of the group 0 by default, and the ID management table 23b,
23c. That is, normally, the object that depends on the application software 30 is controlled by the main ID management table 23a, and when processing by the software component is performed, the ID management table of the subordinate software component (group) is controlled. specify. Since the monitor 21 controls the object, the monitor 21 can determine the group number of the group to which the object making a request to the monitor 21 belongs. When transferring (executing) control to a task unique to the software component, the ID management tables 23b and 23 of the group to which the object to which the control is transferred belongs by the pointer 22
Specify c. The ID management table of the designated destination can be confirmed from the ID management table 23a based on which software component the object belongs to.

For example, when the task A of the ID management table 23a as shown in FIG. 3A specifies "0001H", the ID management table 23a is set as an ID management table for managing ID numbers. When specifying “FF01H” indicating that task A is unique to any software component, the pointer 22 specifies the ID management table 23b of the first software component because task A is the first software component. I do.

With the information processing system 10 as described above, ID numbers are assigned to objects as follows. Here, it is assumed that only objects are tasks and event flags, and two software components including such objects are registered.

The assignment of an ID number will be described with reference to FIG. In the information processing system 10, four tasks (task 1 to task 4) dependent on application software, two event flags (event flag 1, event flag 2) dependent on application software, and two software components (first (A software component and a second software component). The first software component to be registered first has two tasks (task A and task B) that depend on the application software and two event flags (event flag A and event flag B) that depend on the application software. The first software component has three unique tasks (task C, task D, and task E) and three event flags (event flag C, event flag D, and event flag E). The second software component to be registered later has one task that depends on the application software (task X) and one event flag that depends on the application software (event flag X).
Prepare. Also, two tasks unique to the second software component (task Y and task Z) and an event flag
(Event flag Y, event flag Z).

The monitor unit 21 includes, as object information, a group number, an ID number of a usable task of the group “0” (hereinafter, referred to as a usable task ID number), and an available event flag of the group “0”. (Hereinafter, referred to as usable event flag ID numbers).

Registration with the information processing system 10 is performed as follows. 1. An object dependent on the application software 30 is registered. (1) The monitor unit 21 determines the object information as follows. Group number 0 Usable task ID number 0001H Usable event flag ID number 0001H

(2) Application software 30
Are registered and four event flags are registered. The task ID number and the event flag ID number are assigned as follows based on the object information. Task 1 0001H Task 2 0002H Task 3 0003H Task 4 0004H Event flag 1 0001H Event flag 2 0002H These ID numbers are stored in the ID management table 23a as objects of group “0”.

(3) Application software 30
The object information of the monitor unit 21 is updated as follows by registering an object that depends on. Group number 0 Usable task ID number 0005H Usable event flag ID number 0003H

2. Register the object of the first software component. (1) The monitor unit 21 specifies the group number “1”. The object information is as follows. Group number 1 Usable task ID number 0005H Usable event flag ID number 0003H

(2) Of the first software components, two tasks dependent on the application software 30 and two event flags dependent on the application software 30 are registered. These tasks and event flags belong to the first software component, but are registered with the group number “0” because they depend on the application software 30. The ID numbers of the task and event flags are assigned as follows based on the object information. Task A 0005H Task B 0006H Event flag A 0003H Event flag B 0004H The monitor unit 21 stores the above object in the ID management table 23a because the above-mentioned object is designated as the group number “0”. "1"
Is assigned to the first software component, it is interpreted as belonging to the first software component.

(3) Register three unique tasks and three event flags inside the first software component. The task and event flag ID numbers are allocated as follows. Task C FF01H Task D FF02H Task E FF03H Event flag C FF01H Event flag D FF02H Event flag E FF03H The system designer assigns a group unique number (FFH). Also, the object to be registered is interpreted as having the group number “1” based on the group number in the object information. That is, the object to be registered is interpreted as being group 1 and unique to the first software component. For example, the task D is the ID number “02H” of the group 1 and the event flag E is the group 1
Is interpreted as ID number “03H”. The above tasks C to E, event flags C to E
Is stored as an object of group 1 in the ID management table 23b.

(4) By registering the object of the first software component, the object information of the monitor unit 21 is updated as follows. Group number 1 Usable task ID number 0007H Usable event flag ID number 0005H

3. Register the object of the second software component. (1) The monitor unit 21 specifies the group number “2”. The object information is as follows. Group number 2 Usable task ID number 0007H Usable event flag ID number 0005H

(2) Among the second software components, one task and one event flag that depend on the application software 30 are registered. These tasks and event flags belong to the second software component, but are registered with the group number “0” because they depend on the application software 30. The task and event flag ID numbers are based on the object information.
It is allocated as follows. The task X 0007H event flag X 0005H The monitor unit 21 stores the above object in the ID management table 23a because the object is designated as the group number “0”.
Is assigned to the first software component, it is interpreted as belonging to the first software component.

(3) Register two unique tasks and two event flags inside the second software component. The task and event flag ID numbers are allocated as follows. Task Y FF01H Task Z FF02H Event flag Y FF01H Event flag Z FF02H The system designer assigns a group unique number. The object to be registered is interpreted as having a group number “2” based on the group number in the object information. In other words, the object to be registered is group 2,
It is interpreted as being unique inside the second software component. For example, the task Y is interpreted as the ID number “01H” of the group number 2 and the event flag Z is interpreted as the ID number “02H” of the group 2. The above task Y, task Z, event flag Y, event flag Z
Is stored as an object of group 2 in the ID management table 23c.

(4) By registering the object of the second software component, the object information of the monitor unit 21 is updated as follows. Group number 2 Usable task ID number 0008H Usable event flag ID number 0006H

As described above, the ID management table 23
Create ac. Although omitted in FIG. 5, in each table, in addition to the ID number, the task name, and the event flag name, other information about each object as shown in FIG. 3 is recorded.

When the task makes various requests to other tasks by specifying the ID number via the monitor unit 21, the group number "00H" or the group unique number "FFH"
Will be specified. When the group number “00H” is designated, the object to which the group number “00H” is assigned is designated. Group unique number "FF
When "H" is specified, the object of the software component to which the task that issued the request belongs is specified. That is, if task A specifies the task ID number “0004H”, it indicates that task 4 has been specified, and if task ID number “FF02H” has been specified, it indicates that task D has been specified. Also, task X is assigned a task ID number “0005”.
When "H" is designated, task A is designated, and when task ID number "FF02H" is designated, task Z is designated. When the task A is designated from the task C, the task ID number “0005H” is designated. An object unique to another software component cannot be specified because the group and the software component are different. That is, a request from task C to task Y cannot be made. As a result, an object is not erroneously specified.

When the group number “00H” is designated by managing the ID number by the monitor unit 21, the ID management table of the group number “00H” is referred to. When a unique ID number is designated inside the software component, the ID management table designated by the pointer 22 is referred to. Thus, access to objects other than the group to which the task belongs can be protected.

A more specific example will be described. Here, the image processing system will be described as an example of an information processing system. The software component is drawing software having a drawing function for a frame buffer. FIG. 6 shows the configuration of tasks of such an image processing system 70.

The image processing system 70 includes a management task 7
1. drawing software 72 for performing drawing processing on a frame buffer by processing by an internal task; data input task 7
6 is provided. The management task 71, according to the data obtained from the external input device by the data input task 76,
The calculation is performed on the image to be drawn on the frame buffer, and the calculation result is used as a drawing request as the drawing software 72.
Send to The data input task 76 is for acquiring data from the input device in accordance with an instruction from the management task 71 and sending the acquired data to the management task 71. A plurality of input devices may be provided. In this case, data is acquired from any one of the input devices and transmitted to the management task 71 according to an instruction from the management task 71.

The drawing software 72 includes a request receiving task 73
And a task 74 for drawing a point and a task 7 for drawing a line
5 is included. The request receiving task 73 receives a drawing request from the management task 71, and distributes the drawing request to a task 74 for drawing points or a task 75 for drawing lines according to the content of the request. The point drawing task 74 draws a point at coordinates specified by a drawing request. The line drawing task 75 draws a line at the coordinates specified by the drawing request. That is, this drawing software 72
In response to a drawing request from, a point or a line is drawn at the designated coordinates in the frame buffer.

The ID numbers of the respective tasks provided in the image processing system 70 are as follows using the drawing software 72 as one software component using the concept of a software group. Management task 71 0001H Request reception task 73 0002H Data reception task 76 0003H Task 74 for drawing a unique task point inside the drawing software 72 FF01H Task for drawing a line 75 FF02H

The management task 71, the request reception task 73, and the data reception task 76 belong to the group number “0” and depend on the image processing system 70. The request receiving task 73 is a task in the drawing software 72, but is a management task 71 that is a task outside the drawing software.
The group number is "0" to receive the request from. Task 74 for drawing points and task 7 for drawing lines
5 is related only to processing in the drawing processing software 72. Therefore, the task belongs to the group number “1” and is unique to the drawing software 72.

Here, a function is added to the drawing software 72. The functions to be added are, for example, a function of drawing a square at predetermined coordinates and a function of drawing a circle at predetermined coordinates. To implement these functions, draw a square task 7
7. A task 78 for drawing a circle is added to the drawing software 72. FIG. 7 shows a configuration of a task of the image processing system 70 when two tasks are added to the drawing software 72.

By adding a task, the image processing system 7
The ID numbers of the tasks included in 0 are as follows. Management task 71 0001H Request reception task 73 0002H Data reception task 76 0003H Task unique to draw inside the drawing software 72 Task 74 FF01H Line drawing task 75 FF02H Square drawing task 77 FF03H Circle drawing task 78 FF04H

As described above, even if the number of tasks is increased by adding a function to the drawing software 72, the drawing software 7
Add task in ID 2 (in software component) and ID
It is sufficient to assign a number, and it is possible to eliminate the influence on other tasks such as a change in the ID number of a task other than the drawing software 72.

By introducing the concept of a software group, it is not necessary to be aware of the internal structure of software components. This facilitates the management of the entire system when incorporating software components into the system. Since the structure of the software component does not need to be considered, even if the structure inside the software component changes in the future, the influence on the entire information processing system can be reduced.
Further, due to the concept of the software group, an object such as a task configuring a software component is invisible from other tasks configuring the system. Therefore, unauthorized access can be prevented, which is also useful from the viewpoint of protection.

In this example, the case where a task is added has been described. However, similar effects can be obtained by allocating ID numbers to other objects such as event flags and semaphores.

[0067]

According to the present invention as described above, it becomes easy to incorporate software components into an information processing system. Also, since there is no influence between software components,
Software component development becomes easier.

[Brief description of the drawings]

FIG. 1 is a diagram showing the concept of a software group.

FIG. 2 is a configuration diagram of a device that controls an object of the information processing system.

FIG. 3 is an exemplary diagram of an ID management table. FIG. 3A shows a group 0, FIG. 3B shows a group 1, and FIG. 3C shows a group 2.

FIG. 4 is an explanatory diagram of a process performed by a monitor unit.

FIG. 5 is an exemplary diagram of an ID management table. FIG. 5A shows a group 0, FIG. 5B shows a group 1, and FIG. 5C shows a group 2.

FIG. 6 is a diagram showing a configuration of a task of the image processing system.

FIG. 7 is a diagram showing a configuration of a task of the image processing system.

FIG. 8 is an explanatory diagram of a conventional case where a task is added to a software component. FIG.
Indicates the ID number after the task is added.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Information processing apparatus 20 Operating system 21 Monitor part 22 Pointer 23a-c ID management table 30 Application software 70 Image processing system 71 Management task 72 Drawing software 73 Request receiving task 74 Point drawing task 75 Line drawing task 76 Data input Task 77 Task to draw a square 78 Task to draw a circle

Claims (10)

[Claims] 1. An information processing system that realizes a predetermined function by specifying each of a plurality of objects and executing a process, wherein each of the plurality of objects is divided into a plurality of groups to which different group information is allocated. A plurality of ID management means associated with the group information, wherein a table in which ID information and an object name of the plurality of objects to which ID information identifying each is assigned is recorded; An information processing system, comprising: a desired ID management unit specified by the group information from the ID management unit, and a specified object specified by the ID information. 2. An information processing system for realizing predetermined application software by specifying each of a plurality of objects and executing a process, wherein each of the plurality of objects is divided into a plurality of groups to which different group information is allocated. A plurality of ID management means associated with the group information, wherein a table in which ID information and an object name of the plurality of objects to which ID information for identifying each of the plurality of objects is assigned is recorded; From the plurality of ID management means,
An information processing system, comprising: a management unit that specifies a D management unit and a specification unit that specifies a predetermined object based on the ID information. 3. The plurality of objects include those included in one or more software components that are configured by two or more objects and perform predetermined processing, and those not included in the one or more software components. The information processing system according to claim 2, wherein the information processing system is divided into a group of objects for each software component including a group of objects and a group of objects not included in the software component. 4. The information processing system according to claim 2, wherein the plurality of objects are divided into a group of objects dependent on the application software and a group of objects not dependent on the application software. 5. The plurality of objects include an object included in any one or more software components configured by two or more objects and performing a predetermined process, and an object not included in the software component and dependent on application software. A first object that depends on the application software, and a third object that does not depend on the application software. The plurality of objects include the first object and the first object. The information processing system according to claim 2, wherein the information processing system is divided into a second object group and a third object group for each software component. 6. The information processing system according to claim 5, wherein the table of the group of the first object and the group of the second object includes information indicating which software component includes the second object. 7. The method according to claim 7, wherein the specifying unit is configured to, when instructed to execute a process by the third object included in the software component including the second object, from the second object, the group including the second object The software component including the second object is confirmed from the table, and the third object instructed by the ID management means associated with the group information of the confirmed software component group is specified. 6. The information processing system according to item 6. 8. A method that is executed in an apparatus that realizes predetermined application software by specifying each of a plurality of objects and executing a process, wherein the plurality of objects are assigned to different groups. ID that is divided and identifies each individual within each group
A table in which ID information of the plurality of objects associated with information is associated with an object name is stored in association with the group information, and the ID is stored in the table associated with the group information.
An object management method in which a specified object is specified by information. 9. In an operating system for realizing predetermined application software by specifying each of a plurality of objects and executing a process, each of the plurality of objects is divided into a plurality of groups to which different group information is allocated. A plurality of ID management means associated with the group information, wherein a table in which ID information and an object name of the plurality of objects to which ID information identifying each is assigned is recorded; From the ID management means of the
An operating system, comprising: D specifying means for specifying the management means and specifying means for specifying a predetermined object based on the ID information. 10. A computer that realizes predetermined application software by specifying each of a plurality of objects and executing a process is divided into a plurality of groups to which different group information is allocated, and within each group. A process of storing a table in which ID information and an object name of the plurality of objects to which ID information identifying each is assigned is associated with the group information; and storing the group information and the ID information from the table. A computer-readable recording medium on which is recorded a program for executing a process of specifying a predetermined object.