JP2012173983A - Task application configuration device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform the addition, correction, deletion and display of data via a user operation picture by configuring a task application having a cross expansion type table or a time series expansion type table in which a line and a column respectively have an independent index on the basis of defined content without programming it.SOLUTION: Table definition information and table expansion information is stored as application definition information 201 in an application definition information storage part 101, and an application execution part 103 generates an expansion table in the application data storage part 102 on the basis of the content, and sets its relation with the data operation element of a user operation picture 104. Each record of the expansion table is made to have not only expansion data but also the identification ID of a record as the object of expansion and the identification ID of a record as the assistance of expansion.

Description

The present invention relates to a business application configuration apparatus for configuring and using business application software for processing business information according to the needs of individual business organizations in a business organization composed of a plurality of members.

The business application software used by the members of the management organization in the business is composed of execution modules programmed in a form that can be understood by computers and communication devices. In many cases, the programming required here requires a high level of expertise regarding the operation of computers and communication devices, and its development is costly and time consuming.

Technologies to reduce the development man-hours for business application software include modularizing functional elements as much as possible, configuring the software with a combination of these modules, selecting or setting predefined parameters, and end There are methods using a simple programming language represented by user computing.

Although these methods have the effect of reducing the man-hours for developing business application software compared to before, they are greatly restricted by the procedure for operating computers and communication devices and the language structure for operating computers. Therefore, specialized knowledge about software is required.

On the other hand, Patent Document 1 discloses a technique for enabling a user who does not have computer programming knowledge to configure a business application based on knowledge about the structure of business information. Here, by defining the configuration content of the business application, the business application configuration apparatus configures business application software according to the content.

Japanese Patent Application No. 2011-018952

Many information processing operations have their own indexes in the row and column directions, and information is often set and managed in cells as intersections of the indexes. For example, in the commodity price list, the amount of money is determined by a combination of the commodity name and the specification contents, and this is presented as a matrix type table. In addition, the product stock list is a list in which the number of stocks corresponding to the product name is expanded by date.

On the other hand, with the technique described in Patent Document 1, the user operation screen when handling business information has a simple record format having an index only in one direction of a row or column. Therefore, when it is desired to cross-expand each record according to the items of other records or when it is desired to expand in time series, unique programming is required.

Even when using simple programming technology or when creating and managing the above-mentioned cross-expansion and time-series expansion tables by parameter settings using development tools, etc. There is no technology that can be managed separately from the business application itself as application definition information that does not include programming knowledge.

In order to solve the above-described problem, the business application configuration apparatus according to the present invention expands a plurality of tables in combination, and associates the expanded table with the data operation elements arranged on the user operation screen, thereby combining the index. The information processing of the user corresponding to is enabled. In addition, by managing the contents as application definition information for different business applications in each company organization, the man-hours for system development and maintenance are reduced.

In order to achieve the above object, a business application configuration apparatus of the present invention comprises an application definition information storage unit, an application data storage unit, an application execution unit, and a user operation screen, and the application definition information storage unit The application definition information stored in the table includes table definition information and table expansion information. The table definition information includes one or more attribute definition information. The table expansion information includes the table definition information to be expanded. The application data stored in the application data storage unit includes expansion target table identification information to be identified, expansion auxiliary table identification information for identifying the table definition information serving as expansion assistance, and one or more expansion attribute definition information. Normal corresponding to the contents of the table definition information And the expansion table corresponding to the contents of the table definition information, the normal table includes a normal record corresponding to the contents of the table definition information, and the expansion table corresponds to the contents of the table definition information The normal record includes attribute data corresponding to the attribute definition information, and the expansion record includes a expansion target record identification ID that identifies a record that is a expansion target, and a expansion that identifies a record that is an expansion aid The user operation screen includes an attribute data operation element corresponding to the attribute data and an expansion data operation element corresponding to the expansion data; and the application data includes an auxiliary record identification ID and expansion data corresponding to the attribute definition information. The execution unit includes an expansion result table generation unit, an expansion table screen configuration unit, An expansion table input unit; and an expansion table output unit, wherein the expansion result table generation unit includes a table of the normal table to be expanded as the expansion target record identification ID in the expansion table corresponding to the table expansion information. The identification ID of one record selected from among them is made to correspond, and the identification ID of one record selected from the normal table which is the development assistance is made to correspond as the development auxiliary record identification ID, and the above-mentioned table development information belongs The expansion record having the expansion data corresponding to each of the expansion attribute definition information as a component is stored in the application data storage unit, and the expansion table screen configuration means uses the same attribute as the attribute data of the normal record The attribute data corresponding to the attribute data of the definition information Corresponding to the attribute data operation element whose operation element is the same row or the same column on the user operation screen, the expansion data of the expansion record in the expansion record having the same expansion target record identification ID The expanded data operation elements corresponding to the expanded data corresponding to the same attribute definition information correspond to the expanded data operation elements that are in the same row or the same column on the user operation screen, and the expanded table input means includes the When there is a user input to the expanded data operation element, the corresponding expanded data value in the application data storage unit is changed, and the expanded table output means changes the expanded data value in the application data storage unit In this case, the value displayed in the corresponding expanded data manipulation element is changed.

Preferably, the expansion table screen configuration means includes the expansion data manipulation element corresponding to the expansion data of another expansion record having the same expansion auxiliary record identification ID as the expansion data of the expansion record. The expanded data operation elements corresponding to the same column or the same row on the operation screen are associated with each other.

Preferably, the table definition information includes time series definition information, and the application execution unit includes time series table generation means for storing a time series table according to the time series definition information in the application data storage unit, The expansion result table generation means uses the time series table according to the time series definition information as expansion assistance when the table definition information indicated by the expansion auxiliary table identification information has the time series definition information.

Preferably, the table expansion information includes a concatenated key for identifying the attribute definition information of the table definition information indicated by the expansion target table identification information, and the attribute definition information of the table definition information indicated by the expansion auxiliary table identification information. And the expansion result attribute information including the concatenated key for identifying the expansion record attribute information, and the expansion result table generation means includes, for all the expansion link attribute information included in the table expansion information, When the value of the attribute data corresponding to the concatenated key and the value of the attribute data corresponding to the concatenated key of the normal record which is an expansion aid have a specified relationship, the expansion record is stored in the expansion table. Add

Preferably, the development attribute definition information includes calculation formula definition information, the application execution unit includes a development result table calculation unit, and the development result table calculation unit includes the attribute in the calculation formula of the calculation formula definition information. When the identification name of the definition information or the identification name of the expansion attribute definition information is included, before calculating the value of the expansion data corresponding to the expansion attribute definition information, the part of this identification name is replaced with the expansion record or Corresponds to the value of the attribute data corresponding to the attribute definition information or the expansion attribute definition information included in the record indicated by the expansion target record identification ID of the expansion record or the record indicated by the expansion auxiliary record identification ID of the expansion record Replace with the value of the expanded data.

Preferably, the expansion attribute definition information includes cumulative calculation definition information, and the expansion result table calculation means calculates a value of the expansion data corresponding to the expansion attribute definition information having the cumulative calculation definition information of the expansion record. When determining, the value of the attribute data corresponding to the same attribute definition information on the expanded record having the same expanded object record identification ID and the expanded auxiliary record identification ID one before or after refer.

According to the present invention, it becomes easy to modify a business application having a cross-deployment type or time-series development type screen in accordance with the needs of each management organization or the needs of a person in charge. As a result, when there is a problem in the flow of business information and the flow of work in the management organization, it is possible to change the information system step by step while improving the portion each time.

In addition, according to the present invention, another business application definition information for another similar management organization is configured based on one or a plurality of business application definition information having a cross-deployment type or time-series development type screen. This can greatly reduce the man-hours related to conventional business application development.

Further, according to the present invention, the business application definition information having a cross-deployment type or time-series development type screen can be used as a method for processing the information in the business in charge, even if the business person who is a user does not have specialized knowledge about programming. By registering as, you can bring the business application you use closer to the mechanism that suits your needs.

It is the figure which showed the outline | summary of the business application component apparatus. It is the figure which showed the structure of application definition information. It is the figure which showed the structure of the application data storage part. It is the figure which showed the outline | summary (the 1) of an application execution part. It is the figure which showed the outline | summary (the 2) of an application execution part. It is the figure which showed the relationship between a normal table and an expansion | deployment table. It is the figure which showed the development with a condition by a connection attribute. It is the figure which showed the user operation screen of an expansion | deployment table. It is the figure which showed the expansion | deployment using a time series table. It is the figure which showed the user operation screen of the expansion | deployment table expanded in time series. It is the figure which showed the operation screen of the expansion | deployment table connected with the connection attribute. It is the figure which showed the table definition information of the product price and the product specification. It is the figure which showed the content of the goods price table and the goods specification table. It is the figure which showed the table expansion | deployment information of goods price. It is the figure which showed the expansion | deployment table display screen of a goods price list. It is the figure which showed the definition information of goods inventory and a calendar. It is the figure which showed the contents of the goods inventory table and the calendar table. It is the figure which showed the table expansion information of goods inventory. It is the figure which showed the expansion | deployment table display screen of a goods stock list.

The operation of the business application configuration apparatus according to the present invention will be described below. As shown in FIG. 1, the business application configuration apparatus 100 includes an application definition information storage unit 101, an application data storage unit 102, an application execution unit 103, and a user operation screen 104.

The user 105 performs information processing such as inquiry of information necessary for business, addition, correction, and deletion via the user operation screen 104. On the user operation screen 104, application data 301 stored in the application data storage unit 102 is displayed by the application execution unit 103, and information input by the user 105 is displayed by the application execution unit 103 by the application data storage unit. This is reflected in the application data 301 stored in 102.

The application definition information 201 stored in the application definition information storage unit 101 is used to determine the data structure of the application data storage unit 102, the processing operation of the application execution unit 103, and the contents of the screen configuration of the user operation screen 104. Used by the execution unit 103.

FIG. 2 shows the structure of the application definition information 201. The application definition information 201 stored in the application definition information storage unit 101 has one or more table definition information 202 and one or more table development information 203. Each table definition information 202 has one or more attribute definition information 204. In the case of a time series table, the table definition information 202 includes time series definition information 209.

The table expansion information 203 has expansion target table identification information 206 and expansion auxiliary table identification information 207, and the identification name of the table defined as the table definition information 202 is set. The table development information 203 has one or more development attribute definition information 205, and has calculation formula definition information 210 and cumulative calculation definition information 211 as necessary. Further, the table expansion information 203 has expansion connection attribute information 208 as necessary.

The application definition information 201 can be defined or changed in accordance with the characteristics of the target business, and can be acquired from the outside by the business application configuration apparatus 100, or the business application configuration apparatus 100 can acquire the user 105. Edit according to your needs. See Patent Document 1 for this procedure.

FIG. 3 shows the structure of application data 301 stored in the application data storage unit 102. The tables constituting the application data 301 include a normal table 302 and a development table 303.

The application execution unit 103 configures the normal table 302 corresponding to the table definition information 202. The table identification name of the normal table 302 is the identification name of the corresponding table definition information 202. Further, the application execution unit 103 adds, modifies, or deletes the normal record 304 with respect to the normal table 302. The application execution unit 103 causes the normal record 304 to have an identification ID having a unique value in the same normal table 302 and attribute data 305 corresponding to the attribute definition information 205.

On the other hand, the application execution unit 103 configures the expansion table 303 corresponding to the table expansion information 203 by the expansion result table generation unit 110. The table identification name of the expansion table 303 is the identification name of the corresponding table expansion information 203. Further, the application execution unit 103 adds, corrects, or deletes the expansion record 306 from the expansion table 303 by the expansion result table generation unit 110. This development record 306 has a development target record identification ID 308 and a development auxiliary record identification ID 309 in addition to the development data 307 corresponding to the development attribute definition information 205.

As shown in FIG. 4, the application execution unit 103 stores the application data 301 used in each business application in the application data storage unit 102. At this time, the contents stored in the application data storage unit 102 are read from the database 106 by the table data synchronization unit 112 in accordance with an instruction from the user 105, and newly added, modified, or deleted contents are stored in the database 106. Include in the book.

Further, as shown in FIG. 4, the application execution unit 103 expands the expanded data operation element 108 when the expanded table input unit 113 changes the value of the expanded data operation element 108 on the user operation screen 104. Based on the target record identification ID 308 and the development auxiliary record identification ID 309, the development record 306 is inspected, and the value of the development data 307 of the record is replaced with the changed value changed by the user and stored.

Further, as shown in FIG. 4, when the expansion data 307 of the expansion record 306 is changed by the expansion table output unit 114, the application execution unit 103 displays the result displayed on the user operation screen 104. Therefore, the expanded data operation element 108 is specified from the row position, the column position, and the attribute name stored in the expanded record 306, and the value is changed.

The expansion result table generation unit 110 performed by the application execution unit 103 selects the expansion target record identification ID 308 and the expansion auxiliary record identification ID 309 included in the expansion record 306 from the normal table 302 indicated by the expansion target table identification information 206, respectively. The identification ID of the selected record and the identification ID of the record selected from the normal table 302 indicated by the expansion auxiliary table identification information 207 are set so that the combination of the two identification IDs is unique in the expansion table 303. To do.

When a development record 306 of the development table 303 is newly generated for the table development information 203, the following procedure is used.

Step 1: One normal record 304 included in the expansion target table indicated by the expansion target table identification information 206 is selected as record A.

Step 2: One normal record 304 included in the expansion auxiliary table indicated by the expansion auxiliary table identification information 207 is selected as record B.

Step 3: When the expanded connection attribute information 208 exists, for all the expanded connection attribute information 208, the value of the connection attribute of the record A indicated by the expansion connection attribute information 208 is compared with the value of the connection attribute of the record B. If the condition indicated by the expanded connection attribute information 208 is not satisfied, the process proceeds to step 5.

Step 4: The expansion record 306 is added to the expansion table 303, and the expansion target record identification ID 308 is set as the identification ID of the record A, and the expansion auxiliary record identification ID 309 is stored as the identification ID of the record B in the application data storage unit 102.

Step 5: Return to Step 2 until all normal records 304 included in the expansion auxiliary table indicated by the expansion auxiliary table identification information 207 are executed.

Step 6: Return to Step 1 until all normal records 304 included in the expansion target table indicated by the expansion target table identification information 206 are executed.

When the normal table example (A) 401 whose identification name is A and the normal table example (B) 402 whose identification name is B are given, the expansion result table generation unit 110 performs normal processing as shown in FIG. A development table example (A × B) 403 is generated with the table example (A) 401 as a development target table and the normal table example (B) 402 as a development auxiliary table. Here, the “target ID” column corresponds to the expansion target record identification ID 308, and the “auxiliary ID” column corresponds to the expansion auxiliary record identification ID 309. “Attribute 2” and “Attribute 3” are columns corresponding to the expansion attribute definition information 204.

Further, the expansion result table generation unit 110 limits the records to be expanded when the expansion link attribute information 208 is defined in the table expansion information 203. FIG. 7 shows a case where the expansion connection attribute information 208 is defined as “consolidation attribute”. The values of the connection attributes of the expansion target record and the expansion auxiliary record are compared and indicated in the “condition” column. The expansion record 306 is added only when both are equal to each other according to the existing conditions. As a result, as shown in FIG. 7, among the six record candidates, three records having the same connection attribute value are set in the application data storage unit 102 as the expanded record 306.

As shown in FIG. 8, the application execution unit 103 converts the application data 301 stored in the application data storage unit 102 into the attribute data operation element 107 and the expansion data operation element of the user operation screen 104 by the expansion table screen configuration unit 111. 108. The expansion table screen constituting unit 111 follows the following procedure.

Step 1: One table expansion information 203 is selected from the application definition information storage unit 101, and further, a corresponding expansion table 303 is selected in the application data storage unit 102 to be a expansion table X. If there is no corresponding table, add a new one.

Step 2: One normal record 304 is extracted in order from the first record of the normal table 302 corresponding to the development target table identification information 206, and is designated as record A. A line on the user operation screen 104 corresponding to the record A is a line A.

Step 3: The attribute data 305 included in the record A is made to correspond to the attribute data operation element 107 on the row A, and the identification ID of the record A and the identification name of the attribute definition information 204 are stored in the attribute data operation element 107 .

Step 4: One normal record 304 is extracted in order from the first record of the normal table 302 corresponding to the expansion auxiliary table identification information 207, and is designated as record B. Further, a column on the user operation screen 104 corresponding to the record B is a column B.

Step 5: In the table development information 203, if an attribute name as a column title is specified and the corresponding attribute data 305 exists in the record B, the value is used as the column title corresponding to the column B. It is displayed on the operation screen 104.

Step 6: Among the expansion records 306 included in the expansion table X, the expansion record 306 having the identification ID of the record A and the identification ID of the record B is set as the expansion record X. One expanded data 307 included in the expanded record X is selected and set as expanded data X.

Step 7: When a plurality of development attribute definition information 205 is defined in the table development information 203, the subdivision number corresponding to each is set as subdivision C. The expanded data X is made to correspond to the expanded data operation element 108 belonging to the row A, the column B, and the subdivision C. The expanded data operation element 108 has an identification ID of the record A, an identification ID of the record B, and an expanded attribute definition. The identification name of the information 205 is stored. Further, in the expansion record X, row A and column B are stored as the row position and column position on the user operation screen 104 of the expansion data operation element 108.

Step 8: Return to Step 6 until all the development data 307 included in the development record X is executed.

Step 9: Return to Step 4 until all the normal records 304 of the normal table 302 corresponding to the expansion auxiliary table identification information 207 are executed.

Step 10: Return to Step 2 until all normal records 304 of the normal table 302 corresponding to the development target table identification information 206 are executed.

When the table definition information 202 stored in the application definition information storage unit 101 defines the starting date and time, the section width, and the number of expansions as the time series definition information 209, the application execution unit 103 stores the application data storage unit 102 in the application data storage unit 102. As a normal table 302, a time series table is generated by the following procedure.

Step 1: The identification name of the table definition information 202 having the time series definition information 209 is stored in the application data storage unit 102 as the normal table 302.

Step 2: The starting date / time of the time series definition information 209 is set as the date / time S.

Step 3: One normal record 304 having “start date and time” and “end date and time” as attributes is added, attribute data 305 of “start date and time” is set as date and time S, and attribute data 305 of “end date and time” is set as date and time S + section Remember as width.

Step 4: The value of the attribute data 305 of “end date and time” is set as the date and time S, and the process returns to step 3 until the number of records reaches the number of expansions.

When the identification name of the time series table generated according to the above procedure is specified as the table expansion information 203 as the expansion auxiliary table identification information 207, the application execution unit 103 displays each record of the table to be expanded. Expanded in time series, expanded data 307 corresponding to the expanded attribute definition information 205 is expanded in the application data storage unit 102.

In FIG. 9, the time series table generation means 115 uses the time series table with the starting date and time of April 10th, the section width of 1 day, and the number of expansions of 3 as the expansion auxiliary table and the normal table A as the expansion target table. The result which produced | generated the series table is shown. The generated time series table example (T) 411 includes three records whose start date and time are “April 10”, “April 11”, and “April 12”.

FIG. 9 shows a result of generating the expansion table by the expansion result table generating unit 110 using the time series table as the expansion auxiliary table T as an expansion table example (A × T) 412. This development table example (A × T) 412 has a total of 6 records, each having “attribute 2” and “attribute 3”.

FIG. 10 shows an example of the expansion table (A × T) 412 associated with the user operation screen 104 by the expansion table screen configuration unit 111. Corresponding to “attribute 1” and “attribute 2” in the expansion table 303 of “A × T”, each row is further subdivided in the table (A × T), and subdivided rows of “attribute 1” and “attribute 2” Is set.

As a result of the application execution unit 103 associating the expansion data 307 of the expansion record 306 included in the expansion table 303 with the expansion data operation element 108 of the user operation screen 104 by the expansion table screen configuration unit 111, the expansion connection attribute information When 208 is defined, since the records to be expanded are limited, as shown in the example 415 of the user operation screen in FIG. 11, a part of the data is displayed on the user operation screen 104 in a missing form. The

If the screen configuration of the user operation screen 104 corresponding to the table expansion information 203 is “column shortening type”, the expansion table screen configuration unit 111 sets the column corresponding to the expansion data 307 to the expansion auxiliary record identification ID 309. Regardless of the method, the vacant columns in the same row are assigned in order. An example 416 of the user operation screen in FIG. 11 is an example of the “column shortening type” user operation screen 104.

If the calculation formula definition information 210 is defined in the expansion attribute definition information 205, the application execution unit 103 uses the expansion result table calculation unit 116 to change the value of the corresponding expansion data 307 according to the calculation expression. And When the identification name of the attribute definition information 204 is present in the calculation formula section of the calculation formula definition information 210, the value is recursively replaced by the following procedure.

Step 1: Select the identification name of the attribute definition information 204 included in the calculation formula of the calculation formula definition information 210 and set it as the attribute identification name X. In addition, a value to be assigned to the corresponding location in the calculation formula as the value of the attribute identification name X is defined as the attribute value X.

Step 2: When the attribute identification name X includes the expansion target table identification information 206 as a prefix or suffix for qualification, the process proceeds to Step 4. If the expansion auxiliary table identification information 207 is included, the process proceeds to step 5.

Step 3: If the table development information 203 includes the development attribute definition information 205 corresponding to the attribute identification name X, the value of the development data 307 corresponding to the attribute identification name X of the development record is set to the attribute value X, and the process goes to Step 6. move on.

Step 4: If the table definition information 202 corresponding to the expansion target table identification information 206 includes the attribute definition information 204 corresponding to the attribute identification name X, it corresponds to the attribute identification name X of the record indicated by the expansion target record identification ID 308. The value of the attribute data 305 is set as the attribute value X, and the process proceeds to step 6.

Step 5: If the table definition information 202 corresponding to the expansion auxiliary table identification information 207 includes the attribute definition information 204 corresponding to the attribute identification name X, it corresponds to the attribute identification name X of the record indicated by the expansion auxiliary record identification ID 309. The value of the attribute data 305 is set as the attribute value X, and the process proceeds to step 6.

Step 6: Return to Step 1 until it is executed for all the identification names of the attribute definition information 204 included in the calculation formula of the calculation formula definition information 210. Otherwise, calculate the value of the formula and end.

When the cumulative calculation definition information 211 is set in the expansion attribute definition information 205 in the expansion result table calculation unit 116, the application execution unit 103 sets the value of the expansion data 307 for the table expansion information 203 according to the following procedure. To decide.

Step 1: One record of the development target table indicated by the development target table identification information 206 is selected and designated as record A.

Step 2: One development attribute definition information 205 is selected and set as a development attribute X. When the cumulative calculation definition information 211 of the expansion attribute X has an initial value, the attribute value of the record A corresponding to the attribute name specified there is set as the cumulative data X.

Step 3: One record in the expansion auxiliary table indicated by the expansion auxiliary table identification information 207 is selected in the sorted order, and is designated as record B.

Step 4: In the expansion table 303, the expansion record 306 having the identification ID of the record A and the identification ID of the record B is searched. If not, go to 6.

Step 5: In the development record X, cumulative calculation is performed with the value of the development data 307 corresponding to the development attribute X and the cumulative data X, and the result is set as new cumulative data X. Unless otherwise specified as the method of cumulative calculation, simple cumulative calculation is (cumulative data X) = (cumulative data X) + (expanded data value of expanded attribute X).

Step 6: Return to Step 3 until all records in the expansion auxiliary table indicated by the expansion auxiliary table identification information 207 are executed.

Step 7: Return to Step 2 until all the development attribute definition information 205 is executed.

Step 8: Return to Step 1 until all the records of the expansion target table indicated by the expansion target table identification information 206 are executed.

The operation of the business application configuration apparatus 100 according to the present invention will be described below using a specific embodiment. First, the first case is a case of a business application configuration for managing product price information. In many cases, the product price differs depending on the specification additionally set for each product, but this business application is used to efficiently manage the different price depending on the product specification.

FIG. 12 shows the attribute names constituting the definition information of the product price table and the product specification table. Here, the product price table is a development target table, and the product specification table is a development auxiliary table. That is, consider a case where prices are displayed in table format for each specification for each item of merchandise.

Here, three records of product A, product B, and product C are set in the product price table, and the reference price and category of each product are input and stored. Also, two records of specification 1 and specification 2 are set in the product specification table, and the amount of addition for each specification and the category of applicable product are input and stored. FIG. 13 shows the contents of a specific product price table and product specification table in this case.

FIG. 14 shows table expansion information 203 of “product price list”. Here, the table to be expanded is “product price”, the table to be expanded is “product specification”, and the expansion connection attribute information 208 is specified. Here, when the “category” of each item in the product price table is included in the “category” list of each specification in the product specification table, the expansion record 306 is generated.

In a state where the above application definition information 201 is stored in the application definition information storage unit 101, the application execution unit 103 first generates the expansion table 303 by the expansion result table generation unit 110.

The number of records in the product price table is 3, the number of records in the product specification table is 2, and a total of 6 expansion record 306 candidates are examined for records corresponding to the conditions based on the expansion connection attribute information 208. Conditions other than the combination of 2 and the combination of product B and specification 2 were satisfied, and a total of 4 records were generated.

Subsequently, the expansion result 307 of the expansion record 306 is calculated by the expansion result table calculation unit 116 according to the calculation formula definition information 210 set in the expansion attribute definition information 205. The value of “standard price” is “standard price + standard addition”. For example, in the case of a combination of “product A” and “specification 1”, 400 + 50 = 450. Similarly, the values of all the development data 307 are calculated.

Thereafter, the application execution unit 103 relates the attribute data operation element 107 and the expansion data operation element 108 to the user operation screen 104 by the expansion table screen configuration unit 111, and sets the value of the expansion data 307 by the expansion table output unit 114. Is displayed on the screen. FIG. 15 shows a user operation screen 104 corresponding to this case.

In FIG. 15, columns of “product name” and “reference price” are attribute data operation elements 107, and columns of “specification 1” and “specification 2” are expanded data operation elements 108. The rows of “Product A”, “Product B”, and “Product C” correspond to the records of the product price table 503, respectively, and the columns of “Specification 1” and “Specification 2” correspond to the respective items of the product specification table 504. Supports records.

As a second embodiment, an example of a business application configuration for managing the transition of merchandise inventory will be described. FIG. 16 shows the table definition information 202 of the product inventory table to be expanded and the time series definition information 209 of the calendar table to be expanded. In the second embodiment, a business application for managing the quantity of merchandise inventory in a table developed in time series by a calendar table is configured.

The calendar table is set in the application data storage unit 102 by executing the time series table generation unit 115 using the time series definition information (calendar) 511 of FIG. In this example, two records are generated together with the start date and time of April 20, which is the starting point, and the start date and time of April 21.

Three records of product A, product B, and product C are set in the product stock table, and the current stock is input to each record. FIG. 17 shows the contents of a product inventory table to be expanded stored in the application data storage unit 102 and the contents of a calendar table for assisting expansion.

The application definition information storage unit 101 stores “product inventory list” as the table development information 203. In this table development information 203, “commodity stock” is defined in the development target table identification information 206, and “calendar” is defined and stored in the development auxiliary table identification information 207. Further, the table development information 203 stores two development attribute definition information 205 of “number of orders” and “stock quantity”. For “stock quantity”, the calculation formula is defined as (−number of orders) as calculation formula definition information 210, and cumulative calculation definition information 211 is also specified. The initial value in the cumulative calculation is “current stock”. FIG. 18 shows the contents of the development attribute definition information 205 of “product inventory list”.

Using the above-described application definition information 201 stored in the application definition information storage unit 101 and the contents of the expansion table and the normal table 302 serving as an expansion assistance stored in the application data storage unit 102, the application execution unit 103 Then, the expansion result table generation unit 110 is executed.

As the expansion record 306 of the “product inventory list” which is an expansion table, a total of 6 records are generated as a product of 3 records of the product inventory table and 2 records of the calendar table, and “order number” and “inventory number” for each combination. The value of the expanded data 307 “is set in the application data storage unit 102.

In the initial state, since no value is set as the “number of orders”, the application execution unit 103 sets 0 as the default value. On the other hand, since the calculation formula definition information 210 and the cumulative calculation definition information 211 are set for the “stock quantity”, a value is calculated according to the expansion result table calculation means 116.

In this case, the calculation formula is “−number of orders”, and since the number of orders received at this point is all zero, the value of the calculation formula is also zero. However, since the cumulative calculation definition information 211 is designated and “current stock” is set as an initial value, the actual calculation formula is “the number of stocks one day ago—the number of orders received”. The number of orders received. Therefore, on both April 20 and April 21, the stock quantity of product A is 50, the stock quantity of product B is 15, and the stock quantity of product C is 30.

Here, the user, through the user operation screen 104, as an actual “order received”, two products B on April 20, 20 products C, 23 products A on April 21, Consider the case where two products B are input. When the registration button is pressed, the expansion table input unit 113 stores these values as the expansion data of the product inventory list table. Subsequently, the expansion result table calculation unit 116 re-expands the “stock quantity” expansion data. A value of 307 is calculated.

In this case, since the “order quantity” is not 0, the “stock quantity” is sequentially reduced from the value set in the “current stock”, and the stock quantity for each day is calculated. The calculated “stock quantity” value is displayed on each expanded data operation element 108 of the user operation screen 104 by the expansion table output means 114, and has the contents shown in FIG.

100 Business application component device
101 Application definition information storage unit
102 Application data storage unit
103 Application execution unit
104 User operation screen
105 user 106 database 107 attribute data operation element
108 Expanded data manipulation element
110 Expansion result table generation means
111 Deployment table screen configuration means
112 Table data synchronization means
113 Development table input means
114 Expansion table output means
115 Time series table generation means
116 Expansion result table calculation means
201 Application definition information
202 Table definition information
203 Table expansion information
204 Attribute definition information
205 Deployment attribute definition information
206 Deployment target table identification information
207 Development auxiliary table identification information
208 Expanded link attribute information
209 Time series definition information
210 Formula definition information
211 Cumulative calculation definition information
301 Application data
302 Normal table
303 Expansion table
304 Normal record
305 attribute data
306 Expanded record
307 Expanded data
308 Expanded record identification ID
309 Development support record identification ID
401 Example of normal table (A)
402 Normal table example (B)
403 Example of expansion table (A x B)
407 Table expansion information example (with A x B connection)
408 Example of expansion table (with A x B connection)
410 Time Series Definition Information Example (T)
411 Time series table example (T)
412 Example of expansion table (A × T)
413 User operation screen example (A x B)
414 User operation screen example (A x T)
415 Example of user operation screen (A × B) with connection condition 416 Example of user operation screen (A × B) Column shortening type 501 with connection condition Table definition information (product price)
502 Table definition information (product specification)
503 Product price table 504 Product specification table 505 Deployment attribute definition information (product price list)
506 Table development information (product price list)
507 Product price list screen 510 Table definition information (product inventory)
511 Time series definition information (calendar)
512 Expansion attribute information (product inventory list)
513 Commodity inventory table 514 Calendar table 515 Commodity inventory list screen

Claims (6)

An application definition information storage unit;
An application data storage unit;
An application execution unit;
A user operation screen, comprising:
The application definition information stored in the application definition information storage unit is:
Table definition information,
Including table expansion information,
The table definition information is
Contains one or more attribute definition information,
The table expansion information is
Expansion target table identification information for identifying the table definition information to be expanded; and
Expansion assistance table identification information for identifying the table definition information serving as expansion assistance;
Contains one or more deployment attribute definition information,
The application data stored in the application data storage unit is
A normal table corresponding to the contents of the table definition information and an expansion table corresponding to the contents of the table expansion information;
The normal table is
Including a normal record corresponding to the contents of the table definition information,
The expansion table is
Including an expanded record corresponding to the contents of the table definition information,
The normal record is
Including attribute data corresponding to the attribute definition information,
The expansion record is
A deployment record identification ID for identifying a record to be expanded;
A development assistance record identification ID for identifying a record that is a development assistance;
Including expanded data corresponding to the attribute definition information,
The user operation screen is
An attribute data manipulation element corresponding to the attribute data and a development data manipulation element corresponding to the development data;
The application execution unit
Expansion result table generation means;
Expansion table screen configuration means;
Expansion table input means;
An expansion table output means,
The expansion result table generation means includes:
In the expansion table corresponding to the table expansion information,
Corresponding to the identification ID of one record selected from the normal table to be expanded as the expansion target record identification ID,
Corresponding to the identification ID of one record selected from the normal table that is expansion assistance as the expansion assistance record identification ID,
The expansion record having the expansion data corresponding to each of the expansion attribute definition information belonging to the table expansion information as a component,
Storing in the application data storage unit,
The expansion table screen configuration means includes:
The attribute data of the normal record is
The attribute data operation elements corresponding to the attribute data of the same attribute definition information correspond to the attribute data operation elements that are in the same row or the same column on the user operation screen,
The expansion data of the expansion record is
The expanded data operation element corresponding to the expanded data corresponding to the same attribute definition information in another expanded record having the same expanded object record identification ID is the same row or the same column on the user operation screen. Corresponding to the expansion data manipulation element,
The expansion table input means includes
When there is a user input to the expanded data operation element, the value of the expanded data corresponding to the application data storage unit is changed,
The expansion table output means includes
When the value of the expansion data in the application data storage unit is changed, the business application configuration apparatus changes a value displayed in the corresponding expansion data operation element. The expansion table screen configuration means includes:
The expansion data of the expansion record is
The expansion data operation element corresponding to the expansion data of another expansion record having the same expansion auxiliary record identification ID corresponds to the expansion data operation element in the same column or the same row on the user operation screen. The business application composition device according to claim 1. The table definition information is
Including time series definition information,
The application execution unit
A time series table generating means for storing a time series table according to the time series definition information in the application data storage unit;
The expansion result table generation means includes:
When the table definition information indicated by the expansion auxiliary table identification information has the time series definition information,
The business application configuration apparatus according to claim 1 or 2, wherein the time series table according to the time series definition information is used as an expansion aid. The table expansion information is
A concatenated key for identifying the attribute definition information of the table definition information indicated by the expansion target table identification information;
Expansion expansion attribute information including a connection key that identifies the attribute definition information of the table definition information indicated by the expansion auxiliary table identification information as a component,
The expansion result table generation means includes:
For all the expansion connection attribute information included in the table expansion information,
A value of the attribute data corresponding to the concatenated key of the normal record to be expanded;
The value of the attribute data corresponding to the concatenated key of the normal record that is an expansion aid is
If the relationship is specified,
4. The business application composition apparatus according to claim 1, wherein the expansion record is added to the expansion table. The expansion attribute definition information is
Including formula definition information,
The application execution unit
It has a deployment result table calculation means,
The expansion result table calculation means includes:
When the calculation formula of the calculation formula definition information includes the identification name of the attribute definition information or the identification name of the expanded attribute definition information,
Before calculating the value of the expanded data corresponding to the expanded attribute definition information,
The value of the attribute data corresponding to the attribute definition information or the expansion attribute included in the record indicated by the expansion target record identification ID of the expansion record or the expansion record or the expansion auxiliary record identification ID of the expansion record 5. The business application composition device according to claim 1, wherein the business application composition device is replaced with a value of the expanded data corresponding to the definition information. The expansion attribute definition information is
Including cumulative calculation definition information,
The expansion result table calculation means includes:
When determining the value of the expansion data corresponding to the expansion attribute definition information having the cumulative calculation definition information of the expansion record,
Referencing the value of the attribute data corresponding to the same attribute definition information on the expanded record having the same expanded object record identification ID and the expanded auxiliary record identification ID one before or after. 6. The business application composition apparatus according to claim 1, wherein

Images