JP3527658B2 - System design support method and apparatus, and recording medium recording system design support program - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to design support for a system for business use, so-called CASE.
It belongs to the technology used for tools.

[0002]

2. Description of the Related Art Conventionally, in developing a system for business use, a so-called CASE (Computer Aided System Engineering) tool for supporting the system design has been used. As one of the CASE tools, "X (cross) up" developed by Ken System Development Co., Ltd.
per ”(registered trademark).

The key to successful system development in these rapidly changing times is to correctly grasp user needs in upstream processes. "Xupper" is a tool to support upstream analysis design, and is based on business flow diagrams and business rules that are easy for end users to understand.
Approach) is realized (Fig. 26).

There are already 62 users of "Xupper".
With 8 sites, "Xupper" strongly backs up the users' strategic system construction and brings a huge economic effect to each user.

[0005]

[Problems to be Solved by the Invention] The current "Xuppe
For "r", the following needs were obtained from the opinions of users.

1) We would like to make it possible to easily perform detailed analysis of data operations such as reference / update relationships between each process and entity attribute items.

2) It is desired to avoid duplicate description of the same operation between processes.

1) is particularly important in terms of maintainability of the system, and 2) is important in terms of productivity during development and productivity during maintenance.

FIG. 27 is a diagram conceptually showing the relationship between processes and entities in the conventional "Xupper". In the conventional “Xupper”, each update process is described on the process side, and in the example of FIG. 27, the “update process A1” that operates the data of the entity A is redundantly described in the process 1 and the process 2. , "Update process B1" that operates the data of entity B
Are redundantly described in Process 2 and Process 3.

The term "duplicated description" means that duplication creation during development and duplication maintenance during maintenance occur, which is not preferable in terms of system productivity.

Further, in order to eliminate the duplication of the data operation, a means of making a subroutine can be considered. In this case, although the duplicate description can be eliminated, the detailed analysis regarding the data operation remains difficult as in the conventional case. is there.

In view of the above problems, the present inventor has
"Xupper" is a major improvement by adding a new concept.

That is, it is an object of the present invention to eliminate redundant description of data operations in a system design support technique, and to easily enable various detailed analyzes of data operations.

[0014]

In order to solve the above-mentioned problems, the solution means taken by the invention of claim 1 is a computer system design for executing data processing of an entity.
As a method to support using computer,
Data, names and dependent entities and inputs and outputs
By inputting the definition of the data operation for the entity , including parameters and
The computer received the definition of the data operation.
Data manipulation according to the definition is intended to build a data component according to the entity that is independent from the process using this data manipulation, upon construction of data components, before
The computer registers the data indicating the name in the data operation table, the data indicating the dependent entity in the entity table, the data indicating the attribute item of the dependent entity in the attribute item table, and the input and output parameters The data shown is associated with the name data registered in the data operation table and the attribute item data registered in the attribute item table and registered in the parameter table.

The solution of the invention of claim 2 is a method of assisting the design of a system for executing data processing of an entity using a computer, which allows a designer to define a data operation for an entity.
The computer with the name and input and output parameters.
By entering the definition of the data operation for the entity , including the data and logic that uses other data components.
The computer receives the definition of the data operation,
The computer performs data operation according to the received definition ,
It is constructed as a data part related to the entity independent of the process using this data operation,
Upon construction of data components, the computer registers the data indicating the name in data manipulation table, data indicating the input and output parameters, registered in the name data and the attribute item table registered in the data operation table In association with the attribute item data, register in the parameter table, register the step data indicating the logic for each step in the logic table, and register the step data registered in the logic table and the input and output parameter data registered in the parameter table. The map data indicating the connection relationship is registered in the map table.

[0016] Further, the solution means taken by the invention of claim 3 is as a method for supporting the design of a system for executing data processing of an entity by using a computer.
Manipulates data on an entity on the computer
By entering the definition of
The computer receives the definition of the data operation.
The data operation related to the definition is constructed as a data part related to the entity independent from the process using the data operation, and the designer connects the screen or the form of the process and the built data part to the computer.
The computer to enter the result.
In response to the request, the computer receives the process related to the received combination and the correspondence relationship between the screen or the form and the data part,
Also, based on the correspondence between the entity and the data part, the correspondence between the process and the entity, the correspondence between the process and the attribute item of the entity, the correspondence between the screen or the form and the entity, and the screen or the form. A cross reference is generated that represents at least one of the correspondence with the attribute items of the entity.

Further, the solution means devised by the invention of claim 4 is a designer as an apparatus for supporting the design of a system which has a computer and executes data processing of an entity.
To the computer, the name and the subordinate entity
By entering the definition of the data operation for the entity , including input and output parameters, the
The computer receives the definition of the data operation,
The data manipulation in accordance with the definitions chromatography data is received, which is constructed as a data component according to the entity that is independent from the process using this data manipulation, upon construction of data components, the computer, data indicating the name In the data operation table, the data indicating the dependent entity in the entity table, the data indicating the attribute item of the dependent entity in the attribute item table, and the data indicating the input and output parameters in the data operation table. The registered name data and the attribute item data registered in the attribute item table are associated with each other and registered in the parameter table.

Further, the solution means taken by the invention of claim 5 is a designer as an apparatus which has a computer and supports the design of a system for executing data processing of an entity.
The computer with the name and input and output parameters.
By entering the definition of the data operation for the entity , including the data and logic that uses other data components.
The computer receives the definition of the data operation,
Data manipulation according to the definition in which the computer receives, is intended to build a data component according to the entity that is independent from the process using this data manipulation, upon construction of de <br/> over data components, said computer, The data indicating the name is registered in the data operation table, and the data indicating the input and output parameters is registered in the parameter table in association with the name data registered in the data operation table and the attribute item data registered in the attribute item table. Then, register the step data indicating the logic for each step in the logic table, and register the map data in the map table that indicates the connection relationship between the step data registered in the logic table and the input and output parameter data registered in the parameter table. To do.

The solution means taken by the invention of claim 6 is a designer as an apparatus for supporting the design of a system having a computer and executing data processing of an entity.
By entering a definition of a data operation for an entity into the computer,
The computer receives the definition of the data operation.
The data operation related to the definition is constructed as a data part related to the entity independent from the process using the data operation, and the designer connects the screen or the form of the process and the built data part to the computer.
The computer, the computer
The computer receives the definition of the data operation and
Based on the correspondence relationship between the process and screen or form related to the data and the data part, and the correspondence relationship between the entity and the data part, the correspondence relationship between the process and the entity, the correspondence relationship between the process and the attribute item of the entity,
Correspondence between screen or form and entity, and
A cross-reference representing at least one of the correspondence between the screen or the form and the attribute item of the entity is generated.

Further, a solution means taken by the invention of claim 7 is as a computer-readable recording medium in which a program for causing a computer to execute design support of a system for executing data processing of an entity is recorded.
Depends on the name entered by the designer on the computer
Receives and receives definitions of data manipulations for entities, including entities and input and output parameters
Data manipulation according to this data manipulation is realized a function to build as independent data component related to the entity from the process of using, and, upon the construction of the data part, to the computer, data indicating the name in data manipulation table Registering, data indicating the subordinate entity is registered in the entity table, data indicating the attribute item of the subordinate entity is registered in the attribute item table,
Data indicating input and output parameters is associated with the name data registered in the data operation table and the attribute item data registered in the attribute item table and registered in the parameter table, and a program for realizing the function is recorded. It is a thing.

Further, the solution means taken by the invention of claim 8 is as a computer-readable recording medium in which a program for causing a computer to execute design support of a system for executing data processing of an entity is recorded.
Enter the name and the input entered by the designer in the computer.
And logic that uses output parameters and other data components
Receiving a definition of a data manipulation for an entity including,
It realizes the function of constructing the data operation related to the received definition as a data component related to the entity independent of the process using this data operation , and, at the time of constructing the data component , stores the data indicating the name in the computer. Data that is registered in the operation table and indicates input and output parameters is associated with the name data registered in the data operation table and the attribute item data registered in the attribute item table, and registered in the parameter table, and the logic is set for each step. Registers the step data shown in Figure 1 in the logic table, and registers the map data in the map table, which indicates the connection relationship between the step data registered in the logic table and the input and output parameter data registered in the parameter table. Record the program for Those were.

Further, a solution means taken by the invention of claim 9 is as a computer-readable recording medium in which a program for causing a computer to execute design support of a system for executing data processing of an entity is recorded.
The computer receives the definition of the data operation for the entity input by the designer , and constructs the data operation related to the received definition as a data component related to the entity independent of the process using the data operation. Receives the combination of the screen or the form that composes the process input by the designer and the constructed data component, and the process related to the combination and the correspondence between the screen or the form and the data component, and the entity Based on the correspondence between data and data parts, the correspondence between processes and entities, the correspondence between process and entity attribute items, the correspondence between screens or forms and entities, and the attributes of screens or forms and entities. Generate a cross reference that represents at least one of the correspondence with the item,
It is a record of a program for realizing the function.

According to the present invention, the data operation defined by the designer is constructed as a data component for the entity, independent of the process using this data operation. Therefore, duplicated descriptions and inconsistent descriptions related to data operations can be eliminated, data parts can be reused, and productivity during system development is improved. Also, the ripple effect of changing the definition of an entity is
It will not reach the process side and the productivity of system maintenance will be improved.

[0024]

1 is a diagram conceptually showing a system designed by a system design support method according to the present invention, and is a diagram showing the position of a data operation unit in a system after design. The data operation unit is for performing data operations on a data definition unit, that is, each entity (database).

As shown in FIG. 1, in the present invention, the data operation unit is constructed as a data component related to an entity, which is independent of a process using this data operation. DLCP (Data Life Cyc
cle Procedure). In the example of FIG. 1, as the data component related to the order receiving entity, DLCP A
1, A2, A3 are built independently of the process.

By constructing the DLCP as shown in FIG. 1, the following effects can be obtained.

First, duplicate description and inconsistent description relating to data operation can be eliminated, and data parts can be reused, thereby improving productivity during system development.

Further, the ripple effect of changing the database definition does not reach the process side, and the productivity of system maintenance is also improved.

Further, a matrix showing the reference / update relationship between each process and the entity attribute item can be easily generated, the detailed analysis on the data operation is facilitated, and the maintainability of the system is improved.

A specific method of constructing the data component DLCP according to the present invention will be described below with reference to the drawings.

(Classification of Data Operations) The present inventor classifies operations related to data into the following four types in order to specifically realize the DLCP.

Basic Database Operation (Single DLC
P) Combined database operation (combined DLCP) Related database update (composite DLCP) Basic database operation of inspection or calculation (Functional DLCP) is a simple operation in units of table, and in SQL, In
Corresponds to sert, Update, Select, Delete statements.

The combined database operation of (3) is to operate by joining (JOIN) a plurality of tables, and is intended only for retrieval.

The related database update of (1) is related data update accompanying primary data update, that is, when a certain table is updated (or created), another related table is also updated.

The inspection or calculation in (3) is a completely different type from the above three data operations, and is a derivation process involving judgment (business logic). That is, the attribute item of the entity is not directly received, but only the result determined according to a certain business rule is received from the data content in the entity.

As a result of examining the above four types of data operations from the viewpoint of whether a control structure is required in DLCP, they are classified into the following two types.

(1) DAP (Data Access Procedure) A DLCP that simply accesses data. This corresponds to basic database operations (single DLCP) and combined database operations (combined DLCP).

(2) BP (Business Procedure) DLCP with business logic. Related database update (composite DLCP) and inspection or calculation (Functi
onal DLCP) corresponds to this.

(Construction of DLCP) The construction method of DLCP as a data component for performing data operation will be specifically described below by dividing it into DAP and BP.

<DAP> DAP is a database component for directly accessing (Insert, Update, Select, Delete) one or a plurality of joined tables. However, single DLCP and combined DL
Since the CPs are integrated, a plurality of tables to be combined can be defined only for the search-type DAP.

A summary of the properties of DAP is as follows. (1) A database component that directly accesses data (table). (2) It has one of the attributes Create, Retrieve, Update, Delete. (3) Always subordinate to one entity. (4) One entity has multiple DAPs. (5) It has attribute items of the entity to be accessed as input / output parameters. (6) SQL statement Where clause, Order by clause, Group by clause, H
It has a description equivalent to the aving clause. (7) It has no direct relationship with other DAPs or BPs.

FIG. 2 is a diagram showing an example of the DAP defined by the designer. The DAP definition in Figure 2 is a combined DLC
It is the "order search" as P, and the "customer" entity is used as a subordinate entity and the "customer" entity is used as a combined entity to search for order information of a specific order number. The subordinate entity is an entity that is a main target of the operation of this DAP. The binding entity refers to an entity that wants to obtain information by binding with a subordinate entity, and can be specified only when the CRUD attribute is “R”. A plurality of binding entities can be designated, and when a plurality of binding entities are designated, binding conditions between the binding entities can also be designated.

FIG. 3 is an image view of data parts for realizing the DAP definition "order search" of FIG. As shown in FIG. 3, in this "order reception search", the "order reception" entity is searched by using the "order reception number" input as an input parameter as a selection condition, and the retrieved "order reception date""customercode""ordernumber" Is output as an output parameter, the "customer code" is searched for the "customer" entity as a join condition, and the searched "customer name" and "customer address" are also output as output parameters.

The data component as shown in FIG. 3 can be viewed in the same manner as the electronic component, for example. That is, "order"
An entity such as or "customer" is a ROM, and the selection condition is implemented by wiring from an input terminal (input parameter). The coupling condition is wiring of signals for synchronizing ROMs, and the result of data manipulation is implemented by wiring from terminals of ROM to output terminals (output parameters).

FIG. 4 is a diagram showing a data storage form of data parts for realizing the DAP definition "order search" of FIG.

When the DAP definition of FIG. 2 is given, first, the name data 11 indicating the name and the outline of this DAP definition.
Is registered in the data operation table DLCPTBL (). Then, the CRUD attribute 12 of this DAP definition is registered in the attribute table DAPTBL ().

Data 13a, 13b indicating the subordinate entity and the combined entity of this DAP definition.
Is registered in the entity table DAPENTITYTBL (). The dependent entity data 13a indicates that the “order” entity is a dependent entity (primary: YES), and the combined entity data 13
b indicates that the "customer" entity is a combined entity (primary: NO). In addition, the data 14 indicating the join condition is stored in the join condition table DAPJOIN.
Register with ENTRYTBL ().

Then, the data 15a to 15e indicating the entity attribute items to be processed by this DAP definition.
Is registered in the attribute item table DAPENTRYTBL (). Attribute item data 15a to 15c is "order"
For the entity, "order date", "customer code", and "order number" are attribute items to be processed, and the attribute item data 15d and 15e are "customer name" and "customer" for the "customer" entity. It indicates that "address" is an attribute item to be processed.

Data 16a representing the input parameter "order number" and data 16b to 16f representing the output parameter "order date""customercode""ordernumber""customername""customeraddress", respectively, are set as parameters. Table D
Register with LCPPARAMTBL (). At this time,
In the output parameter data 16b to 16f, the association with the attribute item data 15a to 15e registered in the attribute item table DAPENTRYTBL is "DAPENT".
RY registration number ".

Further, the data 17 indicating the selection condition is registered in the selection condition table DAPWHERETBL ().

A single DL is used instead of the combined DLCP.
When the CP is defined, the joining entity and the joining condition are not given, so the joining entity data 13b
The attribute item data 15d and 15e and the connection condition data 14 related thereto are not registered. Other types of data are registered as in FIG.

5 to 10 are views showing examples of screens for the designer to define the DAP as shown in FIG.

FIG. 5 shows the names of DAPs, dependent entities,
It is a screen which sets a CRUD attribute and an outline. In FIG. 5, the name is “DAP name”, the subordinate entity is “Primary Entity”, and the CRUD attribute is “CRUD Type”.
Enter the outline in "Description". In addition, "Physical Name" is the function name at the time of source code generation, and "Full Name" is "DAP name" if necessary.
Enter an alias for the name entered in.

FIG. 6 is a screen for setting a binding entity and a binding condition. In FIG. 6, the join entity is “Join Entity” and the join condition is “Matching Column”.
in s ”. To add a combined entity, click the "Add" button to display the entity selection screen and select the entity to add. To add a join condition, click the "New" button and select the join source attribute item and join destination attribute item from the list of entity attribute items.

FIG. 7 is a screen for setting input parameters. In FIG. 7, when adding an input parameter,
Select an entity from the "Entity" pull-down menu, select the target item from the attribute items displayed in "Available Field", and then click the "<" button. As a result, the selected attribute item becomes "Available Field".
Removed from the list and added to "Input Parameter".

FIG. 8 is a screen for setting output parameters. In FIG. 8, when adding an output parameter,
Select an entity from the "Entity" pull-down menu, select the target item from the attribute items displayed in "Available Field", and then click the "<" button. As a result, the selected attribute item becomes "Available Field".
Removed from the list and added to "Output Parameter".

FIG. 9 is a screen for setting selection conditions. In FIG. 9, when adding a selection condition, "Keyword"
By assembling the conditional statement in "Where Text" by selecting the various operators of, the input parameter of "Input Parameters" and the attribute item of "Entity Field".

FIG. 10 is a screen for setting the arrangement order of the acquired data. In FIG. 10, when designating the arrangement order, the target item is selected from the attribute items displayed in “Field Name” and then the “<” button is clicked. As a result, the selected attribute item is additionally displayed in "Order By".

<BP> BP is a database component for realizing related database update and inspection or calculation.

The related database update may be realized by executing a plurality of the above-mentioned DAPs, but the unit of the process is one complete process by combining these.
BP realizes this processing as one composite component.

In the case of batch update processing, another data is created or updated each time one piece of primary data is read. To do this, one of the DAPs that retrieves the input data
It is sufficient to start another DAP for each case, but the above-mentioned DAP
However, they are independent of each other and do not have a structure that describes DAP in DAP. However, since the BP has a control description for activating another DAP in the control structure for activating the DAP, such processing can be realized as one component.

Further, since the DAP is a basic component for inputting / outputting data, only the data items in the database can be transferred. However, in BP, for example,
The process of returning whether or not the transaction amount of the ordering customer exceeds the credit limit amount and the calculation result of the discount rate based on the past order record can be realized as one component.

Relevant database updates are based on rules for maintaining data integrity and relevance. Also, the determination of credit limits and the calculation of discount rates are clearly business rules.

That is, the BP can be said to be a database component that executes all rules (business rules and rules on the data model).

The properties of BP are summarized as follows. (1) It is a composite part that accesses one or more data through DAP and performs processing and judgment. (2) It has a control structure with components that implement business rules and related data updates. (3) It has a parameter that returns a process and a determination result. (4) DAP or other BP can be incorporated within the control structure. (5) It can be associated with one business rule. (6) Not dependent on a specific entity.

FIG. 11 is a diagram showing an example of the BP defined by the designer. The BP definition of FIG. 11 is "new order registration", one order data is registered, the order number is automatically numbered, and this automatically numbered order number is returned as an output parameter. Because of this processing, B in FIG.
The P definition activates a BP that assigns a slip number and a DAP that newly creates order data. The "related business rule" is a business rule realized by this BP, and is created in a language description that the end user can recognize.

FIG. 12 is an image diagram of data parts for realizing the BP definition "new order registration" of FIG. 12
As shown in, in this "new order registration", the BP of "slip number numbering" is started with the "slip classification" input as an input parameter as a parameter, and the "slip number" obtained with this BP is output parameter. In addition to outputting as the "order number", the "slip number" and the "order date", "customer code", and "order number" input as input parameters are used as parameters to activate the "new order creation" DAP,
Generate order data.

That is, a BP can incorporate other BPs or DAPs in its logic. The built-in BP or DAP can connect the data by combining the respective input / output parameters.

FIG. 13 is a diagram showing a data storage form of a data part which realizes the BP definition "new order registration" of FIG. In the figure, the shaded portion indicates that the data has already been registered before registration of "new order registration".

When the BP definition of FIG. 11 is given, first, the name data 21 indicating the name and outline of this BP definition is registered in the data operation table DLCPTBL ().
The data operation table DLCPTBL already contains DL
Name data indicating CP "new order creation" and name data indicating BP "slip number numbering" are registered. Also,
The business rule 22 that is the basis of this BP definition is BPTB
Register to L ().

Then, input parameter data 23a to 23d representing the input parameters "slip classification""orderdate""customercode""ordernumber", respectively, and output parameter data 23e representing the output parameter "order number",
Register in the parameter table DLCPPARAMTBL (). Also, the BP logic (Action Diagram) is registered in the logic table ACTIONDIAGRAMTBL (). At this time, the logic is divided for each step and registered as individual step data 24a to 24f. For example, the step data 24a is the comment sentence “/ *
Data 24b corresponds to "Start BP for assigning slip number", and the data 24b is an EXEC statement "EXEC BP slip number assignment".
It corresponds to.

Further, the logic table ACTIOND
Step data 24a registered in IAGRAMTBL
24f and parameter table DLCPPARAMTB
Map data 25a to 25f representing the connection relationship with the parameter data registered in L are stored in the map table PARA.
Register with MMAPTBL (). For example, the map data 25a uses the input parameter “slip classification” (corresponding to the input parameter data 23a) of this BP definition as an input parameter when executing the BP “slip number numbering” (corresponding to the step data 24b). It means that.
Further, the map data 25b shows the execution result of the BP “slip number numbering” as the output parameter “order number” of this BP definition.
It is used as (corresponding to the output parameter data 23e).

14 to 17 are views showing examples of screens for the designer to define the BP as shown in FIG.

FIG. 14 is a screen for setting the BP name, related business rules and outline. In FIG. 14, the name is input in “BP Name” and the outline is input in “Description”. Related business rule is "Business Rules"
Specify in. In addition, enter the function name when generating the source code in "Physical Name", and enter a name different from the one entered in "DAP name" if necessary in "Full Name".

FIG. 15 is a screen for setting input parameters. In FIG. 15, when adding an input parameter, the “<Dictionary” button is clicked and the target item is selected from the displayed data items.

FIG. 16 is a screen for setting output parameters. In FIG. 16, when adding an input parameter, the “<Dictionary” button is clicked and the target item is selected from the displayed data items. Alternatively, the target item is selected from the output parameters of the DLCP incorporated in this BP.

FIG. 17 is a screen for setting the BP logic. In FIG. 17, for example, when the “Execute” button is clicked, a list of already constructed DLCPs is displayed on the screen, and when the target DLCP is selected, “Action Diagr
An EXEC statement that executes the target DLCP is inserted in the "am" list. Further, when the “If” button is clicked, a conditional expression input screen is displayed, and when a conditional expression is input here, an IF statement is inserted in the “Action Diagram” list.
Furthermore, when the EXEC statement in the “Action Diagram” list is selected and the “Param Mapping” button is clicked, a screen for performing parameter combination with the target DLCP is displayed.

(Combination of Process and Data Component) The designer can easily combine the data component constructed as described above with the screen or the form forming the process.

The processes include processes such as screens and forms, and processes such as batch update. Of these, regarding the screen and form applications, the BP described above is used.
The same can be said of the relationship between the and DAP. That is, when a screen or form is viewed as a product, DAP is an electronic component, B
P corresponds to a wiring board, and it suffices to incorporate these electronic parts and wiring board in the screen or form as a product.

Screens and forms also have input / output data.
By mapping these input / output items and the input / output parameters of BP or DAP, it is possible to finally update or refer to the entity via DAP.

FIG. 18 is a diagram showing the relationship between the application screen and the data parts. As an example, "order entry"
The relationship between the screen and the "order search" DAP is shown. Figure 1
8, when the user inputs the "order number" in the "order number" field and clicks the "search" button, the "order search" DAP incorporated in this click event is activated. In the "order search" DAP, the screen item "order number" is mapped to the input parameter "order number", and the screen parameter is displayed in the output parameter "order date""customercode""ordernumber""customername""customeraddress"."Orderdate","customercode","ordernumber","customername", and "customer address" are mapped. Therefore, the screen item "Order Date"
"Customer code""Ordernumber""Customername""Customeraddress"
The data obtained as a result of the execution of the "order search" DAP is displayed in.

FIG. 19 is a diagram showing an example of incorporation of data components into the application screen. In FIG.
In the "order entry" screen, the case where the "order entry search" DAP is incorporated in the event (entry point) "click" of the "search" button is shown. On the screen 33, the event "OnClick" of the "search" button is associated with the DLCP with the name "order search", and on the screen 34,
The input / output parameters of the “order search” DLCP and each item of the “order input” screen are mapped to combine the data. Here, the DLCP itself is a digital component, and the description of the screens 33 and 34 is also a digital specification. The screen 31 has specifications that the user can see and understand.
The screen 32 describes system specifications for realizing the specifications described on the screen 31, and is a so-called analog specification.

(Cross Reference Between Process and Data Component) By using the data component according to the present invention, a cross reference between the process and the data component can be easily generated, and the process, screen or form, entity, entity or The correlation with the attribute item can be easily known. This significantly improves the maintainability of the system.

FIG. 20 is a diagram showing a schematic configuration of an example of a system designed by the system design support method according to the present invention. As shown in FIG. 20, this system includes a plurality of processes, and each process has a plurality of screens (or forms). Further, this system is provided with a plurality of entities, and each entity has a data component DLCP independent of each process. Each screen constituting the process has a predetermined data part D
Associated with LCP.

In this case, the following cross reference can be easily created. (1) Screen or form vs entity (2) Screen or form vs entity attribute item (3) Process vs entity (4) Process vs entity attribute item FIG. 21 is a diagram summarizing the correlation in the system of FIG. The relationships shown in FIG. 21 are the DLCP table, the entity table, the attribute item table, and the CRU.
It can be easily obtained by referring to the D attribute table or the like.

From FIG. 21, a cross reference as shown in FIG. 22 is easily created.

FIG. 22A is a cross reference of the screen vs entity obtained by paying attention to the target entity in screen units in FIG. For example, the screen of the process A indicates that the entity X and the entity Y are created (C) and the entity Z is updated (U).

FIG. 22B is a cross-reference of screen vs entity attribute items obtained by focusing on the target attribute item in screen units in FIG. For example, the screen of process A is created for attribute items -1 to -4 of entity X and attribute items -5 and -6 of entity Y (C), and for attribute items -7 to -9 of entity Z. This means that update (U) is performed.

FIG. 22C is a cross reference of the process vs entity obtained by paying attention to the target entity for each process in FIG. For example, process A represents creating (C) for entity X and entity Y and updating (U) for entity Y and entity Z.

FIG. 22D is a cross-reference of the process vs entity attribute item obtained by paying attention to the target attribute item for each process in FIG. For example,
The process A is created for the attribute items -1 to -4 of the entity X and the attribute items -5 and -6 of the entity Y (C), the attribute item -6 of the entity Y and the attribute item -7 to -7 of the entity Z. 9 indicates that the update (U) is performed on 9.

FIGS. 23A to 23D are views showing a specific example of the display screen of each cross reference. Such a screen display makes maintenance of the system much easier.

FIG. 24 is a diagram showing an example of a hardware configuration of an actual development environment using the system design support method according to the present invention. The system design support method according to the present invention is realized in the form of software, for example, as an improved CASE tool “Xupper”. "Xuppe
The “r” is provided to each user in the form of being recorded on a recording medium such as a CD-ROM. That is, "Xup
The recording medium in which "per" is recorded is a recording medium in which a program for causing a computer to execute the system design support method according to the present invention is recorded. Of course, the information may be recorded on another type of recording medium and provided, or may be transferred via a network such as the Internet and provided to the user.

The system designer operates the client machine or the stand-alone machine in which "Xupper" is introduced to develop and design the system. That is, "Xup
A client machine or a stand-alone machine in which "per" is introduced is an apparatus that executes the system design support method according to the present invention. Designed systems or entities, DLCPs, processes, etc. are stored in a storage device such as a disk of a server machine or a stand-alone machine. When the development environment and the operating environment are different, the stored design information is moved to the operating environment and used for constructing an actual operating system. A user of the system operates a terminal or a printer connected via a network when the system operates on a server machine, and operates a stand-alone machine itself when the system operates on a stand-alone machine.

FIG. 25 is a diagram showing the actual file design of the portion for constructing the DLCP. The data shown in FIGS. 4 and 13 is generated according to the file design shown in FIG.

[0095]

As described above, according to the present invention, it is possible to eliminate duplicate description and inconsistent description related to data operation in system design, and to perform various detailed analyzes related to data operation.

[Brief description of drawings]

FIG. 1 is a diagram conceptually showing a system designed by a system design support method according to the present invention.

FIG. 2 is an example of a data component DAP defined by a designer.

FIG. 3 is an image diagram of a data component that realizes the DAP definition of FIG.

FIG. 4 is a diagram showing a data storage form of a data component that realizes the DAP definition of FIG.

FIG. 5 is an example of a screen for defining DAP.

FIG. 6 is an example of a screen for defining DAP.

FIG. 7 is an example of a screen for defining DAP.

FIG. 8 is an example of a screen for defining DAP.

FIG. 9 is an example of a screen for defining DAP.

FIG. 10 is an example of a screen for defining DAP.

FIG. 11 is a diagram showing an example of a BP defined by a designer.

12 is an image diagram of a data component that realizes the BP definition of FIG.

13 is a diagram showing a data storage form of a data component that realizes the BP definition of FIG.

FIG. 14 is an example of a screen for BP definition.

FIG. 15 is an example of a screen for BP definition.

FIG. 16 is an example of a screen for BP definition.

FIG. 17 is an example of a screen for BP definition.

FIG. 18 is a diagram showing a relationship between an application screen and data parts.

FIG. 19 is a diagram showing an example of incorporating a data component into an application screen.

FIG. 20 is a schematic configuration of a system designed by the system design support method according to the present invention.

21 is a diagram summarizing the correlation in the system of FIG.

22A to 22D are cross references created from FIG. 21.

23A to 23D are diagrams showing a specific example of a cross-reference display screen.

FIG. 24 is a diagram showing an example of a hardware configuration of an actual development environment using the system design support method according to the present invention.

FIG. 25 is a diagram showing an actual file design of a portion for constructing a DLCP.

FIG. 26 is a diagram conceptually showing the positioning of “Xupper”.

FIG. 27 is a diagram conceptually showing a relationship between a process and an entity in the conventional “Xupper”.

[Explanation of symbols]

11 Name data 13a dependent entity data 15a to 15e attribute item data 16a Input parameter data 16b to 16f output parameter data 21 Name data 23a-23d Input parameter data 23e Output parameter data 24a to 24f step data 25a-25f map data DLCPTBL data operation table DAPENTITYTBL entity table DAPENTRYTBL attribute item table DLCPPARAMTBL parameter table ACTIONDIAGRAMTBL logic table PARAMMAPTBL map table

Claims (9)

(57) [Claims] 1. A method for assisting the design of a system for executing data processing of an entity by using a computer, wherein a designer uses the computer as a name and a subordinate entity.
By entering the definition of the data manipulation for the entity , including the input and output parameters.
The computer receives the definition of the data operation.
Only the computer, data manipulation according to the received definition,
This is independent of the process using the data manipulation, as the data component related to the entity, which building, upon construction of data components, the computer, data indicating the name, registered in the data operation table, dependent The data indicating the entity is registered in the entity table, the data indicating the attribute item of the dependent entity is registered in the attribute item table, and the data indicating the input and output parameters is the name data registered in the data operation table, A system design support method characterized by registering in a parameter table in association with attribute item data registered in an attribute item table. 2. A method for assisting the design of a system for executing data processing of an entity by using a computer, wherein a designer gives the computer a name, an input and an output.
Contains parameters and logic that uses other data components.
Enter the data operation definition for the entity.
This enables the computer to execute the data operation.
Upon receipt of the definition, the computer executes the data operation relating to the received definition ,
This is independent of the process using the data manipulation, as the data component related to the entity, which building, upon construction of data components, the computer, data indicating the name, registered in the data operation table, input The data indicating the output parameter and the output parameter are associated with the name data registered in the data operation table and the attribute item data registered in the attribute item table, registered in the parameter table, and step data indicating the logic for each step is A system design support method characterized in that the map data is registered in the logic table, and the map data indicating the connection relationship between the step data registered in the logic table and the input and output parameter data registered in the parameter table is registered in the map table. . 3. A method for assisting the design of a system for performing data processing of an entity by using a computer, wherein the designer inputs the definition of data operation for the entity into the computer.
The computer receives the definition of the data operation, and the computer executes the data operation according to the received definition .
It is constructed as a data component related to the entity, which is independent from the process using this data operation, and the designer inputs to the computer the combination of the screen or form that constitutes the process and the constructed data component.
As a result, the computer receives the combination, and the computer executes the process based on the process and the screen or the form related to the received combination and the correspondence between the data component and the correspondence between the entity and the data component. At least one of the correspondence relationship between the entity and the entity, the correspondence relationship between the process and the attribute item of the entity, the correspondence relationship between the screen or the form and the entity, and the correspondence relationship between the screen or the form and the attribute item of the entity.
A method for supporting system design, which is characterized by generating a cross reference representing one of the two. 4. A device having a computer for supporting the design of a system for executing data processing of an entity, wherein a designer ...
By entering the definition of the data manipulation for the entity , including the input and output parameters.
The computer receives the definition of the data operation.
Only the computer, data manipulation according to the received definition,
This is independent of the process using the data manipulation, as the data component related to the entity, which building, upon construction of data components, the computer, data indicating the name, registered in the data operation table, dependent The data indicating the entity is registered in the entity table, the data indicating the attribute item of the dependent entity is registered in the attribute item table, and the data indicating the input and output parameters is the name data registered in the data operation table, A system design support device characterized by being registered in a parameter table in association with attribute item data registered in an attribute item table. 5. An apparatus for supporting the design of a system that has a computer and executes data processing of an entity, wherein a designer gives the computer a name, an input and an output.
Contains parameters and logic that uses other data components.
Enter the data operation definition for the entity.
This enables the computer to execute the data operation.
Upon receipt of the definition, the computer executes the data operation relating to the received definition ,
This is independent of the process using the data manipulation, as the data component related to the entity, which building, upon construction of data components, the computer, data indicating the name, registered in the data operation table, input The data indicating the output parameter and the output parameter are associated with the name data registered in the data operation table and the attribute item data registered in the attribute item table, registered in the parameter table, and step data indicating the logic for each step is A system design support apparatus characterized by being registered in a logic table, and registering map data indicating a connection relationship between step data registered in the logic table and input and output parameter data registered in the parameter table in the map table. . 6. An apparatus for supporting the design of a system having a computer, which executes data processing of an entity, wherein the designer inputs a definition of data operation for the entity to the computer,
The computer receives the definition of the data operation, and the computer executes the data operation according to the received definition .
It is constructed as a data component related to the entity, which is independent from the process using this data operation, and the designer inputs to the computer the combination of the screen or form that constitutes the process and the constructed data component.
This enables the computer to execute the data operation.
In response to the definition, the computer, based on the correspondence relation between the process and the screen or the form and the data component, and the correspondence relation between the entity and the data component, the correspondence relation between the process and the entity, and the process. At least one of the correspondence relationship between the entity and the attribute item of the entity, the correspondence relationship between the screen or the form and the entity, and the correspondence relationship between the screen or the form and the attribute item of the entity
A system design support device characterized by generating a cross-reference representing one of the two. 7. A computer-readable recording medium recording a program for causing a computer to execute design support for a system that executes data processing of an entity , the name being input by a designer to the computer , Dependent entities,
Input and an output parameter, the definition of the data manipulation for an entity, receives, manipulates data according to the received definition, independent from the process using this data manipulation, as the data component related to the entity, realizes a function of building And, at the time of constructing the data part , the data indicating the name is registered in the data operation table, the data indicating the dependent entity is registered in the entity table, and the data indicating the attribute item of the dependent entity is registered in the computer. , registered in the attribute item table, the data indicative of the input and output parameters, and the name data registered in the data operation table, in association with the attribute item data registered in the attribute item table, a function to be registered in the parameter table co-recording the program for causing actual revealed Computer-readable recording medium. 8. A computer-readable recording medium recording a program for causing a computer to execute design support for a system that executes data processing of an entity , the name input by a designer to the computer , Input and output parameters
And a logic that uses another data component , receive a definition of a data operation for an entity , and perform a data operation related to the received definition as a data component related to the entity, which is independent of a process that uses this data operation, Name data registered in the data operation table, data for indicating the name in the data operation table, and data for indicating input and output parameters in the computer when realizing the function to be constructed and for constructing the data component And the attribute item data registered in the attribute item table are registered in the parameter table, the step data indicating the logic for each step is registered in the logic table, and the step data registered in the logic table and the parameter table are registered. Input and output parameters registered in A computer-readable recording medium a program for the map data indicating a connection relationship between the data, the actual revealed the function of registering in the map table. 9. A computer-readable recording medium in which a program for causing a computer to execute design support for a system that executes data processing of an entity is recorded , the data for the entity being input by the designer to the computer. of operation
A screen or form that constitutes a process that receives a definition and constructs a data operation related to the received definition as a data component related to the entity that is independent of the process that uses this data operation, and that is input by the designer. Correspondence between the process and the entity based on the correspondence between the constructed data part and the process and screen or form related to the received combination and the data part, and the correspondence relationship between the entity and the data part. Relationships, correspondences between process and entity attribute items, correspondences between screens or forms and entities,
And, of the correspondence between the attribute item of the screen or form an entity, computer-readable recording medium storing a program for causing revealed actual function of generating a cross reference that represents at least one.