JP2023169803A - Computing system, method for executing program, and program - Google Patents

Abstract

To provide a computing system in which package software is operated regardless of the presence of customization.SOLUTION: The computing system includes: an operation device for executing predetermined operation processing; and a storage device storing the program, the storage device being connected to the operation device. The operation device performs the steps of: determining whether there is an add-on program in the program; executing the add-on program in the program when the presence of the add-on program is determined; and executing the program when the absence of the add-on program is determined.SELECTED DRAWING: Figure 1

Description

The present invention relates to a computer system, and particularly to a method for controlling execution of an add-on program.

ERP packages are standardly equipped with a wide variety of functions, and it is most efficient to utilize them. There are computer systems that are built on-premises using packaged software. Customization of the package software is necessary to meet customer requirements that are difficult to meet with the standard functions and master parameters of the package software.

As background technology in this technical field, there is the following prior art. Patent Document 1 (Japanese Unexamined Patent Application Publication No. 2014-59666) describes a business input screen customization system in a business core package that includes a component that is the base of the business input screen, which is a web source used in the business input screen, and an add-in/add-on used in the business input screen customization system. and a web application that generates a business input screen using the database contents and the business input screen web source. Providing an input screen to the customer, customizing the business input screen using a business input screen web source based on the content of the database and the input content by the SE, and storing the customized business input screen in the database. A business input screen customization system featuring the following is described.

JP2014-59666A

Customization makes it possible to flexibly respond to customer-specific requirements that cannot be achieved with uniform package functions, but it poses the problem of having to reimplement customized parts when updating the package software. Further, in a computer system constructed using a cloud service (for example, SaaS), it is difficult to customize it for each customer.

Therefore, there is a need for a system that minimizes the negative effects of customization and allows packaged software to operate regardless of the presence or absence of customization.

Therefore, an object of the present invention is to provide a computer system in which package software operates regardless of whether or not it is customized.

A typical example of the invention disclosed in this application is as follows. That is, the computer system includes an arithmetic device that executes predetermined arithmetic processing, and a storage device that stores the program and is connected to the arithmetic device, and the arithmetic device stores an add-on program in the program. a determination procedure for determining the presence or absence of the add-on program; a procedure for executing the add-on program in the program when it is determined that the add-on program exists; and a procedure for executing the program when it is determined that the add-on program does not exist. It is characterized by carrying out.

According to one aspect of the present invention, it is possible to provide a program that does not cause compilation errors regardless of the presence or absence of an add-on program. Problems, configurations, and effects other than those described above will be made clear by the description of the following examples.

1 is a diagram showing a logical configuration of a work management system according to an embodiment of the present invention. FIG. 1 is a diagram showing the physical configuration of the work management system of this embodiment. FIG. 2 is a diagram showing a detailed configuration of a work management business application according to the present embodiment. It is a figure which shows the example of the work daily table of a present Example. FIG. 7 is a diagram showing an example of a working daily time item table according to the present embodiment. It is a flowchart of the process performed by the automatic calculation processing part of a present Example. It is a flow chart of overtime time calculation processing of a present example. It is a flowchart of the error check process which the check processing part of a present Example performs. It is a flowchart of the error check process which the check processing part of a present Example performs.

FIG. 1 is a diagram showing the logical configuration of a work management system according to an embodiment of the present invention.

The work management system of this embodiment includes a work management server 101 and a work management database server 106. The work management server 101 and the work management database server 106 are connected through a communication line 105. The work management server 101 is connected to a user terminal 120 via a communication line 110, a network 113, and a communication line 111.

The work management server 101 executes the work management business application 300. The work management work application 300 includes a screen display processing section 301, a work details processing section 302, and a database access processing section 303. The detailed configuration of the work management business application 300 will be explained with reference to FIG. 3.

The work management database server 106 has a work management database 207. The work management database 207 is a database that stores work management data of employees, and the details of the stored data will be explained with reference to FIGS. 4 and 5. The work management database 207 includes an employee master managed by a master management processing unit 306, which will be described later.

FIG. 2 is a diagram showing the physical configuration of the work management system of this embodiment.

The work management server 101 includes a central processing unit 202, a program memory 203, a data memory 201, a network interface 204, and an auxiliary storage device (not shown). Program memory 203, data memory 201, and network interface 204 are connected via a bus.

Central processing unit 202 is an arithmetic unit that executes programs stored in program memory 203. As the central processing unit 202 executes various programs, the functions of each functional unit of the work management server 101 (for example, the screen display processing unit 301, the work details processing unit 302, the database access processing unit 303, etc.) are realized. Note that a part of the processing performed by the central processing unit 202 by executing the program may be performed by another arithmetic device (for example, hardware such as ASIC or FPGA).

The program memory 203 and the data memory 201 include a ROM which is a nonvolatile storage element and a RAM which is a volatile storage element. The ROM stores unchangeable programs (eg, BIOS) and the like. RAM is a high-speed and volatile storage element such as DRAM (Dynamic Random Access Memory), and program memory 203 temporarily stores programs executed by the central processing unit 202 and data used when executing the programs. However, the data memory 201 temporarily stores data used when executing a program.

The auxiliary storage device (not shown) is, for example, a large-capacity, nonvolatile storage device such as a magnetic storage device (HDD) or a flash memory (SSD). Further, the auxiliary storage device stores programs executed by the central processing unit 202. That is, the program is read from the auxiliary storage device, loaded into the program memory 203, and executed by the central processing unit 202, thereby realizing each function of the work management server 101.

The network interface 204 is a network interface device that controls communication with other devices (eg, work management database server 106, user terminal 120) according to a predetermined protocol.

The program executed by the central processing unit 202 is provided to the work management server 101 via a removable medium (CD-ROM, flash memory, etc.) or a network, and is stored in a nonvolatile auxiliary storage device that is a non-temporary storage medium. Ru. For this reason, the work management server 101 preferably has an interface for reading data from removable media.

The work management server 101 is a computer system that is physically configured on one computer or on multiple logically or physically configured computers, and is constructed on multiple physical computer resources. It may also run on a virtual machine. For example, the screen display processing unit 301, business details processing unit 302, and database access processing unit 303 may each operate on separate physical or logical computers, or may be combined into one physical or logical computer. It may be something that works on top of that.

The work management database server 106 has a network interface 206 and a work management database 207. The network interface 204 is a network interface device that controls communication with other devices (for example, the work management server 101) according to a predetermined protocol.

FIG. 3 is a diagram showing the detailed configuration of the work management business application 300 of this embodiment.

The work management work application 300 includes a screen display processing section 301, a work details processing section 302, and a database access processing section 303.

The screen display processing unit 301 creates data (for example, an html file) for displaying an input screen and an output screen on the user terminal 120.

The work details processing section 302 has a function of managing employee work based on data input from the user terminal 120, and includes a work details registration processing section 304, a monthly aggregation processing section 305, and a master management processing section 306. , a vacation remaining management processing section 307 and an other processing section 308.

The work content registration processing section 304 has a function of registering data input from the user terminal 120 into the work management database 207, and includes a check processing section 3041, an automatic calculation processing section 3042, and a data registration processing section 3043. The check processing unit 3041 checks the validity of data input from the user terminal 120. For example, a request for paid leave is compared with the number of remaining days of paid leave according to work rules, and it is determined whether paid leave can be granted. The automatic calculation processing unit 3042 calculates various attendance data such as actual working hours, overtime hours, late night overtime hours, late arrival times, and early leaving times at a predetermined timing (for example, at 5 a.m. every day) from attendance data and leaving data. The data registration processing unit 3043 inputs data values and fields to be registered in order to register the attendance data that has been checked by the check processing unit 3041 and/or calculated by the automatic calculation processing unit 3042 in the work management database 207. The data is sent to the database access processing unit 303.

The monthly aggregation processing unit 305 aggregates the attendance data (for example, working hours, overtime hours, late night overtime hours, etc.) for the month on a predetermined deadline according to work rules. The master management processing unit 306 provides an interface for updating work categories and vacation categories for each employee registered in the employee master. The leave remaining management processing unit 307 manages the granting status of various types of leave (for example, paid leave, personal injury and sick leave, etc.) granted to employees according to work rules. It also includes a processing section 308.

The database access processing unit 303 includes an updating unit 102 that issues a database control command (for example, an insert statement) to update the work management database 207 with data input from a user terminal, and an update unit 102 that issues a database control command (for example, an insert statement) to update the work management database 207 with data input from a user terminal, and It has a search unit 103 that issues a database control command (for example, a select statement) for searching the work management database 207.

The work management business application 300 has standard functions provided by the standard program 310 and add-on components 320 to 322 that replace or add to the standard functions. The standard program 310 and add-on components 320 to 322 may be composed of separate files or a single file. For example, the add-on component A320 executes add-on time calculation processing in step 610 of FIG. The add-on component B321 executes add-on overtime time calculation processing in step 703 of FIG. The add-on component C322 executes add-on error check processing (before database update) in step 808 of FIG. 8A. There are three types of add-on components: a type that adds processing to standard processing, a type that replaces part of the standard processing, and a type that is executed at a predetermined timing.

The add-on component is embedded in the program of the work management business application 300, and an add-on start flag consisting of a predetermined character string is added to the beginning, and an add-on end flag consisting of a predetermined character string is added to the end. Provided as information. The add-on head flag and the add-on end flag may be described, for example, in Java annotations (Java is a registered trademark). The add-on code is written between the add-on start flag and the add-on end flag. The add-on head flag and the add-on end flag include information on the type of the add-on. The add-on type information indicates which time calculation the add-on corresponds to, which check it corresponds to, and whether it is an addition or a replacement. That is, the execution location of the add-on component can be specified based on the information about the type of add-on.

For example, the check processing unit 3041 can replace the standard check condition with another check condition or add a new check condition using an add-on component (add-on error check). Further, the automatic calculation processing unit 3042 can use an add-on component (add-on calculation formula) to replace the calculation formula of the time item to be calculated with another calculation formula instead of the standard calculation formula, or to add a new calculation formula. Note that, as will be described later in the flowcharts of FIGS. 6, 7, 8A, and 8B, the work management business application 300 is established as a normal application without any compilation errors, regardless of the presence of add-on components. .

FIG. 4 is a diagram showing an example of a working daily table 401 that constitutes the work management database 207 of this embodiment, and FIG. 5 is a diagram showing an example of a working daily time item table 501 that constitutes the work management database 207 of this embodiment. FIG.

As shown in FIG. 4, the daily work table 401 is a table that stores the daily attendance and leaving data of each employee, including employee identification information (employee ID), year, month, date, work time, Contains data such as clock-out time, vacation classification, work style, etc.

As shown in FIG. 5, the working daily time item table 501 is a table that stores attendance data calculated by the automatic calculation processing unit 3042 from the daily attendance data and clocking out data of each employee, and includes employee identification information. Contains data such as (employee ID), year, month, date, time item name, and number of hours.

Although FIGS. 4 and 5 show tables that constitute the work management database 207, the tables may be configured in other data formats (list, queue, etc.).

FIG. 6 is a flowchart of automatic calculation processing executed by the automatic calculation processing unit 3042 of this embodiment. In the automatic calculation process shown in FIG. 6, add-ons are added as necessary (609 to 611).

First, the automatic calculation processing unit 3042 receives data from the check processing unit 3041 and acquires information necessary for automatic calculation (601). For example, according to the data received from the check processing unit 3041, the work category and calculation pattern of the employee are acquired from the work management database 207.

Then, the automatic calculation processing unit 3042 processes the data for automatic calculation (602). For example, various attendance data (actual working hours, overtime hours, late-night hours, etc.) are calculated from work arrival and departure times without considering work categories.

Then, the automatic calculation processing unit 3042 calculates overtime hours from the attendance data and leaving data (603), calculates flex working hours (604), calculates late arrival time (605), and calculates early leaving time (606). ), the actual working time is calculated (607). In the various time calculation processes in steps 603 to 607, as shown in FIG. 7, it is determined whether there is a replacement add-on, and if there is a replacement add-on for the calculation process, the replacement add-on is executed. do.

As shown in FIG. 7, in the overtime time calculation process (603), the automatic calculation processing unit 3042 collects add-on calculation formulas (for replacement) (701). Specifically, the automatic calculation processing unit 3042 searches the program memory 203 for an add-on start flag and an add-on end flag, and uses the type of information included in the add-on start flag to create an add-on calculation formula (replacement) for overtime calculation processing. ) and read the add-on code written between the add-on start flag and add-on end flag. In this way, since the add-on is detected by searching the program memory 203 for predetermined data (add-on head flag), it does not depend on the file format of the add-on (even if the add-on is embedded in the same file, it is configured in different files). even if the

Then, the automatic calculation processing unit 3042 determines whether there is an add-on calculation formula (for replacement) to be executed in the calculation process (702). If there is an add-on calculation formula (for replacement) that should be executed in the calculation process, the overtime hours are calculated by replacing the standard calculation formula and executing the add-on calculation formula (for replacement). 703), if there is no add-on calculation formula (replacement) to be executed in the calculation process, overtime hours are calculated using a standard calculation formula (704).

Although the overtime time calculation process (603) was explained in FIG. 7, other time calculation processes (flexible working time calculation, late arrival time calculation, early leaving time calculation, actual working time calculation) are also used to replace the calculation process. If there is an add-on, run the replacement add-on.

After that, the automatic calculation processing unit 3042 collects the add-on calculation formula (additional amount) (608). Specifically, the automatic calculation processing unit 3042 searches the program memory 203 for an add-on start flag and an add-on end flag, and creates an add-on calculation formula for time calculation that is additionally processed depending on the type of information included in the add-on start flag. (for addition) and reads the add-on code written between the add-on start flag and add-on end flag.

Then, the automatic calculation processing unit 3042 repeatedly executes the processing of steps 609 to 611 for the number of extracted add-ons. First, the automatic calculation processing unit 3042 determines whether there is an unprocessed add-on calculation formula (additional part) among the collected add-on calculation formulas (additional part) (609). Then, if there is no unprocessed add-on calculation formula (additional amount), the process exits from the repeat process and ends the automatic calculation process. On the other hand, if there is an unprocessed add-on calculation formula (additional part), the add-on calculation formula (additional part) is executed and calculated (610). Then, it is determined whether the next add-on calculation formula (additional part) exists (611). If the next add-on calculation formula (additional amount) does not exist, the process exits from the repetition process and ends the automatic calculation process. On the other hand, if the next add-on calculation formula (additional part) exists, the process returns to step 609, and the next add-on calculation formula (additional part) is executed and calculated (610).

Note that the add-on calculation formula does not need to exist in the program, but may, for example, provide parameters to the standard calculation formula, or may include information on a link to the calculation formula.

FIGS. 8A and 8B are flowcharts of error check processing executed by the check processing unit 3041 of this embodiment.

First, the check processing unit 3041 collects information necessary for error checking (801). For example, the work category and calculation pattern of the employee are acquired from the work management database 207 according to the input data.

Then, the check processing unit 3041 processes information necessary for error checking (802). For example, various attendance data (actual working hours, overtime hours, late-night hours, etc.) are calculated from work arrival and departure times without considering work categories.

Then, the check processing unit 3041 checks for errors in essential items provided as standard functions of the work management business application 300 (803), and checks for errors in other items.

After that, the automatic calculation processing unit 3042 executes automatic calculation processing (FIG. 6) (804).

Then, the check processing unit 3041 collects the add-on error check (before database update) (805). Specifically, the check processing unit 3041 searches the program memory 203 for an add-on start flag and an add-on end flag, extracts an error check for the add-on before updating the database based on the type of information included in the add-on start flag, and Reads the add-on code written between the start flag and the add-on end flag.

Then, the check processing unit 3041 repeatedly executes the processes of steps 806 to 811 for the number of extracted add-ons. First, the check processing unit 3041 determines whether there is an unprocessed add-on error check (before database update) (806). If there is no unprocessed add-on error check (before database update), the process exits from the repeat process and proceeds to step 812. On the other hand, if there is an unprocessed add-on error check (before database update), the add-on error check (before database update) is executed to determine whether there is an error or warning (807).

Then, the check processing unit 3041 determines whether the check result of the add-on error check (before database update) is an error or a warning (808, 809). If the check result of the add-on error check (before database update) is an error, the error check process is terminated, and if the check result of the add-on error check (before database update) is a warning, the warning is sent to the data memory 201. (810). Furthermore, if the check result of the add-on error check (before database update) is neither an error nor a warning, the check processing unit 3041 determines whether the next add-on error check (before database update) exists (811). If the next add-on error check (before database update) does not exist, the process exits from the repeating process, writes the checked data, and updates the work management database 207 (812). On the other hand, if the next add-on error check (before database update) exists, the process returns to step 806 and the next add-on error check (before database update) is executed (807).

Then, the check processing unit 3041 collects the add-on error check (after database update) (813). Specifically, the check processing unit 3041 searches the program memory 203 for the add-on head flag and the add-on tail flag, extracts the add-on error check after the database update based on the type of information included in the add-on head flag, and Reads the add-on code written between the start flag and the add-on end flag.

Then, the check processing unit 3041 repeatedly executes the processing of steps 814 to 820 for the number of extracted add-ons. First, the check processing unit 3041 determines whether there is an unprocessed add-on error check (after database update) (814). If there is no unprocessed add-on error check (after database update), the process exits the repeat process and proceeds to step 821. On the other hand, if there is an unprocessed add-on error check (after database update), the add-on error check (after database update) is executed to determine whether there is an error or warning (815).

Then, the check processing unit 3041 determines whether the check result of the add-on error check (after database update) is an error or a warning (816, 817). If the check result of the add-on error check (after database update) is an error, the work management database 207 updated in step 812 is rolled back to the data before the update (817), and the error check process is performed. finish. If the check result of the add-on error check (after database update) is a warning, the warning is retained in the data memory 201 (819). Furthermore, if the check result of the add-on error check (after database update) is neither an error nor a warning, the check processing unit 3041 determines whether the next add-on error check (after database update) exists (820). If the next add-on error check (after database update) does not exist, the process exits the repeating process, commits the work management database 207 updated in step 812, and finalizes the database update (821). On the other hand, if the next add-on error check (after database update) exists, the process returns to step 814 and executes the next add-on error check (after database update) (815).

In this way, the check using the add-on error check enables non-standard checks of the work management business application 300.

Furthermore, by combining the add-on error check (before database update) and the add-on error check (after database update), it is possible to perform various checks on input data. For example, when checking before updating the database, it is possible to check only the day on which data was input, and when checking after updating the database, it is possible to check other days (the entire month).

A computer system that includes an arithmetic unit (central processing unit 202) that executes predetermined arithmetic processing, and a storage device (program memory 203) in which a program is stored and connected to the arithmetic unit. a determination procedure for determining the presence or absence of an add-on program in a program; a procedure for executing the add-on program within the program if it is determined that the add-on program exists; Since the procedure for executing the program is executed, a program that does not cause a compile error can be provided regardless of the presence or absence of an add-on program. Additionally, add-ons that can be operated separately from the package software itself make version upgrades and updates relatively easy.

Note that the present invention is not limited to the embodiments described above, and includes various modifications and equivalent configurations within the scope of the appended claims. For example, the embodiments described above have been described in detail to explain the present invention in an easy-to-understand manner, and the present invention is not necessarily limited to having all the configurations described. Further, a part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Further, the configuration of one embodiment may be added to the configuration of another embodiment. Further, other configurations may be added, deleted, or replaced with a part of the configuration of each embodiment.

Further, each of the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example by designing an integrated circuit, and a processor realizes each function. It may also be realized by software by interpreting and executing a program.

Information such as programs, tables, files, etc. that realize each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

Furthermore, the control lines and information lines shown are those considered necessary for explanation, and do not necessarily show all the control lines and information lines necessary for implementation. In reality, almost all configurations can be considered interconnected.

101 Work management server 102 Update unit 103 Search unit 105, 110, 111 Communication line 106 Work management database server 113 Network 120 User terminal 201 Data memory 202 Central processing unit 203 Program memory 204 Network interface 206 Network interface 207 Work management database 300 Work management business application 301 Screen display processing section 302 Work details processing section 303 Database access processing section 304 Work content registration processing section 305 Monthly total processing section 306 Master management processing section 307 Leave remaining management processing section 308 Other processing section 310 Standard program 320, 321, 322 Add-on parts 401 Working daily table 501 Working daily time item table 3041 Check processing section 3042 Automatic calculation processing section 3043 Data registration processing section

Claims (9)

A computer system,
comprising an arithmetic device that executes predetermined arithmetic processing and a storage device connected to the arithmetic device,
The arithmetic device is
a determination procedure for determining the presence or absence of an add-on program in the program;
If it is determined that the add-on program exists, a step of executing the add-on program within the program;
If it is determined that the add-on program does not exist, the computer system executes a procedure for executing the program. The computer system according to claim 1,
In the computer system, in the determination step, the arithmetic unit searches the storage device for predetermined additional information, and if the additional information is retrieved, determines that the add-on program is present. The computer system according to claim 2,
The additional information includes data indicating the type of the add-on program,
In the computer system, in the determination step, the arithmetic unit identifies the type of the add-on program from the additional information, and acquires the add-on program at an execution location of the add-on program. The computer system according to claim 2,
The additional information includes head additional information indicating the beginning of the add-on program, and tail additional information indicating the end of the add-on program,
A computer system characterized in that the arithmetic unit acquires a code between the head additional information and the tail additional information as the add-on program. The computer system according to claim 3,
A computer system characterized in that the arithmetic unit specifies a function to be replaced by the add-on program from the additional information, and executes the add-on program in place of the specified function. The computer system according to claim 3,
A computer system characterized in that the arithmetic unit identifies an execution location of the add-on program from the additional information and executes the add-on program at the identified execution location. The computer system according to claim 1,
The add-on program determines the validity of data to be registered in the database,
A computer system characterized in that the arithmetic unit executes the add-on program in the program to perform validity determination that is not provided as a standard. A method of executing a program executed on a computer,
The computer includes an arithmetic device that executes predetermined arithmetic processing, and a storage device that stores the program and is connected to the arithmetic device,
The method of executing the program is as follows:
a determination procedure in which the arithmetic device determines the presence or absence of an add-on program in the program;
a step of executing the add-on program in the program when the computing device determines that the add-on program exists;
A method for executing a program, including a step of executing the add-on program when the arithmetic device determines that the add-on program does not exist. A program that is executed on a computer,
The computer includes an arithmetic device that executes predetermined arithmetic processing, and a storage device connected to the arithmetic device,
The program is
a determination procedure for determining the presence or absence of an add-on program in the program;
If it is determined that the add-on program exists, a step of executing the add-on program within the program;
and a program for causing the arithmetic device to execute a procedure for executing the program when it is determined that the add-on program does not exist.

Images