KR20220099380A - The system and method of making the flow chart database - Google Patents

Abstract

The present invention relates to a method and a system for constructing a flowchart database. In a system in which a server (MS) of a service provider (P: provider) to which a user accesses through a communication network (I) includes an input processing unit (IP) and an output processing unit (OP), and a database in which data is input and output by a control device controlling the input processing unit (IP) and the output processing unit (OP) in the server (MS), in order to database a flowchart composed of a boxes and a sign that are entities as an entity-relationship model (ERD), the database further comprises: a box database (box data DB: BDB) for recording data of a relative position value (coordinate position) of the box with respect to an xy-coordinate reference point (0,0) and a shape (shape) of the box; a main database (F-DB) having a sign database (sign DB: SDB) for recording top, bottom, left, and right direction information of the sign and feedback information to specific top and bottom boxes; a plurality of type databases (TDB1, TDB2, .TBN) for recording events (tasks) defined in the box by cooperating between columns as indexes defined to be linked to the main database (F-DB) through a code comparison; and an ancestor database (ADB) for performing code management and control functions of each piece of associated data between the plurality of type databases (TDB1, TDB2, .TBN) and the box database (BDB).

Description

Flowchart database construction method and system

The present invention relates to a method and system for constructing a database of flowcharts, and more particularly, the present invention relates to a method, transaction method, and method capable of converting and managing a flowchart as a database based on the concept of an object-relationship diagram (ERD) It relates to the provision of a system in which this is implemented.

In most of the domain areas of various tasks, a series of processes to obtain results by setting goals, establishing a plan and putting them into practice are performed in the work and research areas. It was done efficiently, increasing work efficiency, and it is developing in the direction of categorizing the management space. Of course, the history of this series of processes depends on the category and time.

In database-related work, a process that is a part of a flow chart is written by a person handling a domain domain, and is called an Entity Relationship Diagram (ERD: Entity Relationship Diagram, hereinafter referred to as 'ERD'). .) is written by a person who handles data. Of course, there is a concept of order in the flowchart itself, but there is no concept of order in ERD. You will only understand the content, and the understanding between the work of the collaborative team will be narrow.

ERD is a series of expressions for structured data as an entity-relationship model in the field of data modeling, and schematizes the relationships between data, and the expressions including before and after in these relationships are limited.

A flowchart is a diagram showing a workflow or process. It is a logical structure expressed by connecting arrows between boxes to help intuitive understanding and to convey the entire content concisely. It is difficult to reflect additional information in the output, and of course, there is a difficulty in reproducing or transforming the flowchart into an image shape conversely.

ERD is to draw a mutual relationship by schematizing the requirements analysis described in words with a picture, and in the field of data modeling, "Entity Relationship Model" is used as a concrete expression for structured data.

In addition, a database is generally used to store structured data, and the 'structure' of this data and its accompanying constraints can be designed by various techniques. In particular, one of the widely known techniques is object-relational modeling It is called (ERM: Entity-Relationship Modeling), and the concrete and feasible output of the object-relationship modeling (ERM) process becomes ERD.

The data modeling process requires a display method to express the data model as a picture. ERD is often used in strategic planning, schematically a top-level data diagram, or top-down planning of data, identifies the entities involved in running an enterprise and determines the relationships between them.

In some cases, data about data is needed, and data about data is often called 'metadata', and most of the data models include such metadata.

Data analysts need a lot of help from end users and executives to understand an organization's data and create the data that will be most beneficial to managing the organization. To facilitate communication with them, they need a clear way to graph data, and diagrams such as ERD are essential and useful tools for overall planning of an organization's information resources.

In the definition of ERD, 'entity' includes everything we give meaning to the data we store. The shape of the entity may be, for example, a product, a work, a business trip, a meeting, and the like. The shape of the entity has the same attribute type, for example, if there is an entity called 'work', an entity 'instance' called 'normal work' belonging to the entity may exist.

In ERD, an entity usually displays an event or thing to be systemized in a box shape, and the relationship between the boxes is also called a 'Sign' and describes the relationship between entities and attributes, where ' 'Attribute' means an indivisible unit of information representing the nature of entity relationships.

Prior patents related to database processing include 'method and system for providing an intelligent join strategy between heterogeneous NoSQL databases' of Korean Patent No. 10-1772333, and 'DML sentences of relational database into NoSQL databases' of Korean Patent No. 10-2174957 Although there is a 'transaction control method for synchronization with

Korean Patent No. 10-1772333 Korean Patent No. 10-2174957

In addition to the above sources, the database management system related to flowcharts as a technology known in the industry was able to express the relationship between two entities of data by applying the 'code comparison method' and 'self-circulation structure',

In the case of Oracle, for hierarchical data processing, SQL (Structured Query Language) called CONNECT BY is adopted as a special-purpose programming language designed to manage data in a relational database management system (RDBMS).

In relational database management systems, it is widely used for data search and management, database schema creation and modification, and database object access adjustment management. aimed at

In addition, since the existing method only considers the expression of upper and lower level concepts, it is limited to showing the flowchart of all structures. .

In order to solve the limited problem of the prior art, in the database construction method and the system of the flowchart of the present invention, the flowchart of all structures is made into a database through the code comparison unit (entity), the database indicating the entity relationship, and additional information, and , Flowchart This is to present a method and system for constructing a database of flowcharts that record and manage each entity (box) and relation (sign) in the storage space.

More specifically, the present invention uses a model that mixes the concepts of ERD and flow chart, which is one of the data modeling techniques, to database the flow chart implemented in various areas and types, and the method specifically. It is about the system that implements it.

In more detail, the focus is on the composition of the databaseization method, which is composed of a box as an entity, which is a component of the flowchart, and a sign as a relation, expressed as a data relationship between them, and combined with additional information. put

That is, the present invention is to take advantage of each of the advantages of the conventional ERD and flowchart described above and to supplement the insufficient technical area. It relates to a method of adding a database of concepts and a technology to manage the system in which the method is implemented and to service the method.

More fundamentally, a database is created in which the relationship between each entity is defined by defining and expressing data, which is a box, which is an entity as a component of a flowchart, and a symbol, which is a relation.

Then, an entity using the 'code comparison method' is created to combine additional information. Based on the created entity, a database is established and a system to perform it is established, and a service using it is presented.

Accordingly, the database construction method and the system of the flowchart of the present invention have been devised to solve the problems of the prior art as described above,

As the configuration of the system; In a system in which a server of a service provider that a user accesses through a communication network has an input processing unit and an output processing unit, and a database in which data is input and output by a control device that controls the input processing unit and the output processing unit in the server, the object-relationship model In order to database the flowchart consisting of a box, which is an entity as an (ERD), and a sign;

The database includes a box database that records data of the box's relative position value (coordinate position) and the box's shape (shape) with respect to the xy-coordinate reference point; A main database having a sign database that records feedback information to upper and lower boxes, and

A plurality of type databases that record events (tasks) defined in the box by collaborating between columns as indexes defined to be linked against the main database and code;

By further having an ancestor database that performs code management and control functions of the plurality of type databases and each associated data between the box database,

It characterized in that the control device of the system manages the flow chart as a database by comparing the data of the flow chart with the code in each database and managing the link,

As a description of the method, a server of a service provider connected by a user through a communication network has an input processing unit and an output processing unit, and has a database into which data is input/output by a control device that controls the input processing unit and the output processing unit in the server; - A method for databaseizing a flowchart consisting of a box, which is an entity, and a sign, as an entity as a relational model (ERD);

In the database, the relative position value (coordinate position) of the box with respect to the xy-coordinate reference point and the data of the shape (shape) of the box are recorded in the box database of the main database;

recording the vertical, horizontal, left, and right direction information of the sign and feedback information to a specific upper and lower box in the sign database of the main database;

Cooperating between columns as an index defined to be linked in the box database (BDB) and recording the event (task) defined in the box in the main database or type database;

By including at least the step of performing the link control of each associated data between the type database and the box database in comparison with the code of the Ancestor database;

It is characterized in that the control device of the system manages the flowchart as a database by managing the data of the flowchart in comparison with the code of the column data that is an index between the box database, the sign database, the type database, and the ancestor database. .

The method and system for constructing a database of a flowchart of the present invention provide a useful method and system capable of managing, reproducing, selling, and modifying the analysis data of a flowchart based on ERD into a database.

Furthermore, it is an object of the present invention to provide a service by mixing and processing the concepts of ERD and flowchart in the flow chart database construction method and system.

The database construction method and the system of the flowchart of the present invention provide qualitative data that can be sold to consumers on the Internet, and the user pays a certain price and applies and processes it to obtain the desired domain with the shortest time and effort. make it possible to do the job

1 is a block diagram showing an overall system in which a method of constructing a database of a flowchart according to the present invention is implemented.
2 is an explanatory diagram for converting box data of a flowchart into a main database in a method for constructing a database of a flowchart according to the present invention;
Figure 3 is an explanatory diagram for converting the signature data of the flow chart into the main database in the method of constructing the database of the flow chart according to the present invention.
4 is an explanatory diagram showing a main database (F-DB) constructed with box data and sign data in a database construction method of a flowchart according to the present invention.
Fig. 5 is an explanatory diagram showing a relationship between a main database (F-DB) and an auxiliary database in a method for constructing a database of a flowchart according to the present invention;
Fig. 6 is an explanatory diagram showing the configuration of an auxiliary database in the method for constructing a database of a flowchart according to the present invention;
7 is a table diagram constructed using a clustering factor in a method for constructing a database of a flowchart according to the present invention.
8 is a display diagram showing an example of the design of the user interface due to the introduction of the UI to the main database (F-DB) applied to the database construction method and system of the flowchart according to the present invention.
9 is a flowchart illustrating an embodiment of a method for constructing a database of a flowchart according to the present invention and a process diagram of a transaction service implemented and operated in the system.

Hereinafter, the configuration and operation of the database construction method and the system of the flowchart of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram showing an overall system in which a method of constructing a database of a flowchart according to the present invention is implemented, FIG. 2 is an explanatory diagram for converting the box data of the flowchart into a main database, and FIG. 3 is a main database of sign data of the flowchart explanations to do so. Fig. 4 is an explanatory diagram showing a main database (F-DB) constructed with box data and sign data of a flowchart, Fig. 5 is an explanatory diagram showing a relationship between the main database (F-DB) and an auxiliary database, Fig. 6 is an explanatory diagram showing the configuration of an auxiliary database, FIG. 7 is a table constructed using a clustering factor, and FIG. 8 is an example of a design of a user interface due to the introduction of UI to the main database (F-DB). A display diagram, FIG. 9 is a flowchart illustrating an embodiment of a process diagram of a database construction method of a flowchart according to the present invention and a process diagram of a transaction service implemented and operated in the system, which will be described sequentially or together.

In the following description, detailed descriptions of parts that can be easily implemented by those skilled in the art may be omitted.

The basis of the technical idea of the flowchart database construction method and the system of the present invention is to analyze the flowchart quantitatively and qualitatively to store it in two databases, and to combine it with other auxiliary additional information including these two databases. It is about a method of managing a system by adding a database of upper and lower level concepts and providing a service.

In more detail, a database is created that defines specific data of 'Box' and 'Sign' as entities, which are components of a flowchart, and defines a relationship between them.

And in order to combine the additional information necessary for these databases, another auxiliary database is constructed using the code contrast method. Furthermore, by using the generated databases, a database in which the flowchart is converted into data is constructed and a service to the user is initiated.

Therefore, the main, first technical viewpoint is characterized in that the flowchart is implemented as a database, and the second technical viewpoint is 'code comparison of the code upper and lower level concept in order to combine additional information in the database implementing the flowchart above. It is characterized in that it includes entities using 'law', and a third technical aspect is that the result can be provided as a service that enables transactions between users.

A method of constructing a database of a flowchart of the present invention and a system thereof will be described below with drawings.

As shown in FIG. 1 , the service user SU may access the service provider through the communication network I, log in, and use the service provided by the service provider P: operator.

The work performed by the operator P and the service user SU is performed by the input processing unit IP and the output processing unit OP in the server MS. The input processing unit (IP) is stored by the management system of the flowchart-based database (herein referred to as 'main database (F-DB)') designed for the service used by the service user SU.

The main server (MS) of the web (WEB) / WAP (WAP) is a database that stores the operation behavior of various types of users (user: service user (SU), sales user (PU), purchase user (BU)). It includes an input processing unit (IP) and an output processing unit (OP) for outputting input results of the user and the operator (P).

The main type of user, the service user (SU), will be an unspecified number of subjects (individuals, corporations) who use the service based on the main database (F-DB) based on the flowchart implemented according to the present invention.

A sales user (PU) is another form of a service user (SU), which accesses the information stored in the flowchart-based main database (F-DB) to the system of the operator (P) and downloads it to other unspecified number of service users ( You will be able to sell it to SU-1).

The purchasing user (BU) is another form of the service user (SU), and can purchase, modify, and use information up-downloaded by the business operator (P) or the sales user (PU).

The basic configuration of the main database (F-DB) includes a box database (BDB) and a signature database (DB) for collection and management of data related to the flowchart.

As shown in Fig. 2, the configuration of the main database (F-DB) is a box database that records the relative position value (coordinate position) of the box with respect to the xy-coordinate reference point (0 point) and the shape (shape) of the box. Separated from (BDB) and box database (BDB), the sign that establishes the relationship between each box above determines whether the sign is up, down, left, right, and whether the sign is feedback to a specific upper and lower box. A sign database (Sign DB: SDB) should be basically provided.

That is, as shown in Figure 2, the box database (BDB) of the main database (F-DB) is a relative distance value (X, Y) between specific boxes, the size of each box (W, H), the shape or shape of the box (S: Is it a rectangle or a rhombus?) In addition, there is a feature that the number of data is generated as a row as much as the number of boxes.

In the drawing, 5 boxes A, B, C, D, E have position values of X and Y with respect to the relative coordinate 0 (0, 0), the width and height of the boxes are W and H, and P value as the address of the box. This is entered

As shown in Fig. 3, in the sign database (SDB) of the main database (F-DB), the start box (B_Seq) and the destination box (AD_B_Seq) of one arrow, and the start box (B_Seq) start from the destination box (AD_B_Seq) It is composed of an arrow direction (ATD) ending in . Of course, the number of data is generated as much as the number of signs.

The main database (F-DB) including the above can express the flowchart as a data-based database, and based on the recorded data of the main database (F-DB), the control device performs a process of reversing the flowchart in reverse. Of course it can be done.

That is, the relative distance (X, Y) between boxes of the box database (BDB) of the main database (F-DB), the size of each box (W, H), information on the shape or shape of the box (S), and the sign database By combining the data in the direction of the arrow (ATD) starting from the starting box (B_Seq), the ending box (AD_B_Seq), and the starting box (B_Seq) of the arrow in the (DB) part, it becomes possible to re-order the flowchart.

Each entity in the flowchart, the Box, and each data of the sign (the relative position value of the box and the size and shape (shape) of the box), the up, down, left and right directions of the arrow that is the sign, or a specific upper and lower box feedback) is stored in the main database (F-DB), the box database (BDB) and the sign database (SDB), respectively.

An example of a table constructed using the sign data of the box data is shown in FIG. 4 .

Further, as in FIG. 5, in converting the flowchart into a database,

In addition to the main database (F-DB), the box database (BDB) and the signature database (SDB), as an auxiliary database, the specific activity contents, work contents (hereinafter referred to as 'jobs') or main database of each entity box. Only the contents of (F-DB) itself (if the type of work is formal and the number is limited, it can be included in the main database (F-DB) itself), each separate multiple type database that records work time (Type database:TDB1,TDB2,TDB3..TDBN: hereinafter 'TDB1,TDB2,.TDBN') and Ancestor database that performs code management function of each related data between box database (BDB) and sign database (SDB) You should have more (Ancestor DB:ADB).

In this regard, the box database (BDB) is data-coupled to the Ancestor database (ADB) as shown in FIG. 5, and each type database (TDB1, TDB2, .TDBN) is an anse to be combined with the box database (BDB). Data combination is managed via a master database (ADB).

In other words, in order to combine the box database (BDB) of the main database (F-DB) and additional information, the Ancestor database (ADB) is required in a code-to-code relation, and the Ancestor database (ADB) is the box database (BDB). It has a function of selecting a box for which additional information is to be combined among the boxes, and acting as a code management unit that manages the index information of the selected box and the index information of the additional information as a single database.

As clearly shown in FIG. 6, as an index required for data binding of the above-described Ancestor database (ADB) and box database (BDB), for example, a flowchart number (F_Seq), a box number (B_Seq), a type database The division key (T_Seq) of (TDB1, TDB2, ..TBN) is required as a database column. However, it goes without saying that the database column (T_Seq) is not required when only the main database (F-DB) is used as additional information.

In this case, it can be assumed that the definition of the column of the Ancestor database (ADB) is as follows.

Relative distance values (X, Y) between boxes in the box database (BDB) of the main database (F-DB), the size of each box (W, H), information on the shape or shape of the box (S), and the sign database ( DB) by combining the data in the direction of the arrow (ATD) starting from the starting box (B_Seq), the ending box (AD_B_Seq), and the starting box (B_Seq)) of the arrow in the DB) section, it becomes possible to reorder the flowchart.

The information and symbol information in the box above relate to the information of the figure representation, and even if additional information processing is applied, the index does not change. It is possible to build

The auxiliary databases cooperating with the main database (F-DB) will be described in more detail in FIGS. 1 and 5 .

These auxiliary databases are the upper and lower concepts of the box database (BDB) of the main database (F-DB), and a one-to-many relationship is established between two entities. .

The main database (F-DB) cooperates with the Ancestor database (ADB) to combine and control data of multiple type databases (TDB1, TDB2, .TDBN) in which specific management details (work) are recorded.

Among the type databases (TDB1, TDB2, .TDBN), in the case of the table of the type database (TDB1), the boxes of A and B in flowchart 1 are recorded as the work and time of climbing, eating, moving, and work, and the type database ( In the case of the table of TDB2), for example, it is a case where job information is recorded in the box (B) of the tenth flowchart.

In these two cases, for the combination of the main database (F-DB), the ancestor database (ADB) further has database information (TDB_F) and index information (F_Seq, B_Seq, T_Seq) for additional information as columns.

An execution database (Execution DB:EDB) may be further provided as an engine for executing specific contents of the actions of the type databases (TDB1, TDB2, .TBN).

By matching between the combined indexes (date: date, column (F_Seq), column (B_Seq)) to use commonly used columns and date information between databases, the efficiency of the entire database system can be extremely improved, as shown in FIG. By establishing the same relationship, the clustering factor of the system can be used up to the limit.

As shown in Figure 7, it matches between the indexes (date: date, column (F_Seq), column (B_Seq)) that are combined to use columns and date information commonly used between databases, and the main database (F-DB) Box database (BDB), Ancestor database (ADB), and type database (TDB1, TDB2, .TBN) are linked by contrasting codes by primary key (Seq), flowchart number (F-Seq), and box number (B_Seq) has been

In the box database (BDB), arrow direction box number (AD_B_Seq), arrow trail direction (ATD), box relative position X-axis value (X), box relative position Y-axis value (Y), box width value (W), box height value (H), the data of the shape of the box (S) are connected,

T_Seq as a type key and TDB_F as a type key for type databases (TDB1, TDB2, .TBN) link Ancestor database (ADB) and type databases (TDB1, TDB2, ..TBN).

The execution database (EDB), which is linked with the type database (TDB1, TDB2, .TBN) and executes the data of the type database (TDB1, TDB2, .TBN), is the type database (TDB1, TDB2, .TBN). It is linked with the classification key (T_Seq), other additional information (Contents), type databases (TDB1, TDB2, .TBN) and the execution database (EDB) of the Ancestor database (ADB).

Of course, if the type of work is formal and the number is limited, an additional column may be added to the main database (F-DB) itself and included in the main database (F-DB).

In the method and system for constructing a database of the flowchart of the present invention described above, as in FIG. 8 showing an embodiment for servicing the database related to the flowchart,

If you draw boxes A, B, C, D, E in the flowchart, and enter 'planning' in box (A) and 'task assignment' in box (B), the contents of 'planning' and 'task assignment', respectively It is called from this type database (TDB1, TDB2, ..TBN) by the Ancestor database (ADB) and, if necessary, is displayed as a user UI/UX screen of appropriate and various designs, and UI/UX by the execution database (EDB) A specific action can be generated on the screen (boxes C, D, E omitted).

As shown by way of example, if the plan establishment (A) is selected on the UI/UX screen, the task-specific schedule timetable and task modification (CL) and removal (DT), task addition button (AD) are displayed on the plan management screen. It is provided on the GUI screen, and these data changes are made through data processing and restoration of the type databases (TDB1, TDB2, ..TBN) of the management database (MDB) and the Ancestor database (ADB).

As the next box (B), the task assignment selection, the work management screen is created on the UI/UX screen, and the tasks of design, task assignment, research 1, and analysis 1 are developed, so that modification, removal, and addition of each database described above are also performed. Implementation and management are possible as collaboration.

As such, the database construction method of the flowchart of the present invention has the advantage of controlling the entire main database (F-DB) by utilizing the independent operation and index of each main database (F-DB).

A case in which the database construction method of the flowchart of the present invention is applied as a suitable business model that can be operated based on the implemented system is illustrated in FIG. 9 .

A number of users, such as service users (SU), sales users (PU), purchase users (BU), and business operators (P), can create a flowchart and use it jointly with other users.

The user is input/used/invited (10) to the main database (F-DB) and stored (11) in the main database (F-DB) of the present invention, and when a transaction transaction occurs, this related information is transferred to and stored (12) in a separate transaction database separate from the main database (F-DB).

On the other hand, a user searches (20) a flowchart that he or she needs in the main database (F-DB) of the present invention (20), purchases (21) a flowchart that meets his or her needs, and modifies/uses/invites it again While (22), it is updated and stored (23) in the main database (F-DB).

If the user discloses the flow chart he owns or decides to sell (30), this information will be sent back to the transaction database and registered (23) for sale.

That is, the user's work is stored in the main database (F-DB), and when it is decided to open or sell in the future, the data is transferred to a transaction database separate from the main database (F-DB).

The transferred data is open to all users, enabling free search of commercialized flowcharts. Another user who needs similar information in the public flowchart can purchase it, and can use it jointly with other users by modifying the purchase contents to the user's own style.

SU: service user
I: Internet communication network
P: operator
PU: sales user
BU: Buyer

Claims (6)

The server (MS) of the service provider (P: operator) to which the user connects through the communication network (I) has an input processing unit (IP) and an output processing unit (OP), and the input processing unit (IP) in the server (MS) and In a system having a database in which data is input and output by a control device that controls the output processing unit (OP), a flowchart consisting of a box and a sign, which is an entity as an object-relational model (ERD) to database;
The database includes a box data DB (BDB) that records data of the relative position value (coordinate position) of the box with respect to the xy-coordinate reference point (0, 0) and the shape (shape) of the box; A main database (F-DB) having a sign database (Sign DB: SDB) that records up, down, left and right direction information of a sign and feedback information to a specific upper and lower box;
A plurality of type databases (TDB1, TDB2, .TBN) that record events (tasks) defined in the box by collaborating between columns as an index defined to be linked in comparison with the main database (F-DB),
By having the plurality of type databases (TDB1, TDB2, .TBN) and an ancestor database (Ancestor DB: ADB) performing code management and control functions of each related data between the box database (BDB) further,
A system for constructing a database of a flowchart, characterized in that the control device of the system manages the flowchart as a database by comparing the data of the flowchart to the respective databases and managing the link. The method of claim 1,
The database construction system of the flowchart, characterized in that it can further have an execution database (EDB) as an engine for executing the specific contents of the action to be executed of the type database (TDB1, TDB2, .TBN). The method of claim 1,
The box database (BDB), the sign database (DB), the ancestor database (ADB), and the type database (TDB1, TDB2, .TBN) can be deployed on the user's UI/UX screen, and on the UI/UX screen, the A database construction system of a flowchart, characterized in that the control device controls the ancestor database (ADB) and the type database (TDB1, TDB2, ..TBN) so that the action contents of the box can be modified, removed, and added. The method of claim 1,
The step of the user entering/using/inviting (10) the flowchart or searching for a flowchart, the step of the user entering/using/inviting (10) into the main database (F-DB), the input/use/invitation Storing (11) the data in the main database (F-DB), when a transaction by the user occurs, the information is stored (12) in the transaction database;
In the step of the user searching for and discovering (20) his/her own necessary flowchart in the main database (F-DB), input/use/invite a flowchart or,
The user purchases (21) a flowchart that meets the needs, a step of modifying/using/inviting (22) the purchased flowchart (22), and modifying/using/inviting (22) data of the purchased flowchart In the step of being updated and stored (23) in the main database (F-DB), the control device implements a transaction method to update the data in the main database (F-DB) by making a purchase decision after searching the flowchart. A database building system of a flowchart, characterized in that it performs. The method of claim 1,
If the type of work is formal and the number is limited, it can be substituted for the type database (TDB1, TDB2, .TBN) by adding an additional column to the main database (F-DB) and including it in the main database (F-DB). Database building system of the flowchart, characterized in that there is. The server (MS) of the service provider (P: operator) to which the user connects through the communication network (I) has an input processing unit (IP) and an output processing unit (OP), and the input processing unit (IP) in the server (MS) and Having a database in which data is input and output by a control device that controls the output processing unit (OP), a flow chart composed of a box and a sign, which is an entity as an object-relational model (ERD), is databased. a method for doing;
The database stores the relative position value (coordinate position) of the box with respect to the xy-coordinate reference point (0, 0) and the data of the shape (shape) of the box in the box database (Box data DB) of the main database (F-DB). : writing to BDB);
Recording the vertical and horizontal direction information of the sign and feedback information to a specific upper and lower box in the sign database (Sign DB: SDB) of the main database (F-DB);
Cooperating between columns as an index defined to be linked to the box database (BDB), the event (job) defined in the box is recorded in the main database (F-DB) or type database (TDB1, TDB2, .TBN) ,
By including at least the step of performing link control of each associated data between the type database (TDB1, TDB2, .TBN) and the box database (BDB) by the Ancestor DB (ADB) by code comparison;
The control device of the system converts the data of the flowchart into the data of a column that is an index between the box database (BDB), the sign database (DB), the type database (TDB1, TDB2, ..TBN), and the Ancestor database (ADB). A method of constructing a database of a flowchart, characterized in that the flowchart is managed as a database by managing the link in preparation for the code.

Images