JP2017182662A - Program creation system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a program creation system capable of easily utilizing data which is stored in a test database.SOLUTION: A program creation/execution system 100 includes: a first storage area 251 that stores an execution database 400; a second storage area 252 that stores a test database 300 which is accessed when an incomplete program is tested; and a first duplication processing unit 281. The first duplication processing unit 281 makes a creator select part of data which is input at the time of testing and is stored in the test database 300, copies the selected data, and stores the same in the execution database 400.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a program creation system, and more particularly to a system for creating a program that accesses a database.

  In recent years, informatization in companies has progressed, for example, various internal data can be stored in a database and used for various tasks such as personnel, accounting, product development management, quality management, customer management, facility management, document management, etc. Has been done. For example, Patent Document 1 (Japanese Patent Laid-Open No. 2012-216000) discloses an electronic document sharing system. In this electronic text sharing system, end users (employees) can search the information of electronic documents stored in the database, and the end users are limited to browsing and editing electronic document items. It is possible to limit the access of end users including search results.

  Programs related to the electronic document sharing system as described above and programs for utilizing other databases are usually executed by a CPU of a server which is a computer. A program that uses a database that stores various actual data in a company is often developed and created using a program creation system. The program being created undergoes various tests in a test environment.

  In this test environment, if a database storing various actual data (hereinafter referred to as an implementation database) is used, an unfinished program may execute an unexpected process and cause a problem. For example, when a program being created is tested using a database for implementation that includes actual employee and customer email addresses, unnecessary emails may be delivered by mistake and delivered to employees and customers. For this reason, a program creation system often prepares a test database separately from the implementation database. A person who creates a program such as application software using the test database performs a test for confirming the relationship between the operation on the operation screen and the input / output of each information in the test database, for example.

  Recently, in the process of testing a program being created, new data that is not included in the implementation database is often input and stored in the test database. Among the new data entered in the test environment and stored in the test database, there is data that is also required in the implementation database when the completed program is executed in the actual environment in the company. To do.

  However, in the conventional program creation system, the actual environment using the implementation database is distinguished from the test environment using the test database, and the data in the test database input in the test environment is diverted in the actual environment. In some cases, manual work is required.

  An object of the present invention is to provide a program creation system that can easily use data stored in a test database.

  A program creation system according to a first aspect of the present invention includes a first storage unit for storing an implementation database, a second storage unit for storing a test database different from the implementation database, 1 data replication processing unit. The implementation database is a database that is accessed by a program when the user of the program executes the completed program. The test database is a database accessed when testing an incomplete program. An incomplete program is a program that is being created by a creator who creates the program. The first data replication processing unit causes the creator to select some data from the data stored in the test database, and copies the selected data and stores it in the implementation database. The data stored in the test database is data input by the program creator when testing an incomplete program.

  In the program creation system according to the first aspect, during the creation of a program, an incomplete program is tested using the test database, and when the completed program is executed, the execution database is used. A part of the data input in the test and stored in the test database is copied and stored in the implementation database by the program creator selecting. The first data replication processing unit performs the process of causing the creator to select a part of the data and the process of storing the selected data in the implementation database.

  In this case, since the first data replication processing unit is provided and the above two processes are performed, the program creator simply selects a part of the data in the test database. Reflected in the database. Thus, in the program creation system according to the first aspect, the data stored in the test database can be easily utilized.

  A program creation system according to a second aspect of the present invention is the program creation system according to the first aspect, and further includes a second data replication processing unit. The second data replication processing unit causes the creator to select some data from the data stored in the implementation database, and copies the selected data and stores it in the test database.

  Since the program creation system according to the second aspect includes the second data replication processing unit in addition to the first data replication processing unit, the program creator selects a part of the data in the test database or the implementation database. Just do it and it will be reflected in the other database. That is, when the program creator selects a part of the data in the test database or the execution database, data copy processing is performed between the test database and the execution database. Therefore, utilization of data stored in the test database and utilization of data stored in the implementation database are facilitated.

  A program creation system according to a third aspect of the present invention is the program creation system according to the first aspect or the second aspect, and further includes a database generation unit. The database generation unit simultaneously generates an implementation database and a test database at the start of program creation.

  In the program creation system according to the third aspect, at the start of creation of a program using a database, an implementation database accessed by a completed program and a test database accessed by an incomplete program are generated. Therefore, the program creator manually creates an implementation database before using the function of the first data replication processing unit, or manually copies the implementation database at the start of creation to create a test database. There is no need to perform complicated work.

  A program creation system according to a fourth aspect of the present invention is the program creation system according to any one of the first aspect to the third aspect, and the test database has a test file of a data table. Then, the first data replication processing unit causes the creator to select a part of the data in the test file, and copies the selected data and stores it in the implementation database.

  In the program creation system according to the fourth aspect, a part of the data in the test file that is complicated to copy manually can be copied and stored in the implementation database by selection.

  A program creation system according to a fifth aspect of the present invention is the program creation system according to the second aspect, and the implementation database has an implementation file for a data table. Then, the second data replication processing unit causes the creator to select a part of the data in the implementation file, and copies the selected data and stores it in the test database.

  In the program creation system according to the fifth aspect, it is possible to copy and store a part of the data in the implementation file that is complicated to copy manually into the test database by selection.

  According to the program creation system according to the first aspect, the program creator simply selects a part of the data in the test database, and this is reflected in the implementation database. Thereby, in the program creation system which concerns on a 1st viewpoint, the data stored in the test database can be utilized easily.

  According to the program creation system according to the second aspect of the present invention, the program creator selects a part of the data in the test database or the implementation database, so that the test database and the implementation database are selected. Data copy processing is performed mutually. Therefore, it is easy to use the data stored in the test database and the data stored in the implementation database.

  According to the program creation system according to the third aspect of the present invention, the program creator manually creates the implementation database manually or manually copies the implementation database to create the test database. There is no need to do.

  According to the program creation system of the fourth aspect of the present invention, a part of the data in the test file that is complicated to copy manually can be copied and stored in the implementation database by selection.

  According to the program creation system of the fifth aspect of the present invention, a part of the data in the implementation file that is complicated to copy manually can be copied and stored in the test database by selection.

1 is a block diagram of a program creation / execution system according to an embodiment of the present invention. It is an example of the operation screen and history screen which the output part of a server displays on the display part of a client terminal. It is a figure which shows an example of a data table. It is a figure which shows the flow of the program creation by a program creation and implementation system.

  A program creation / execution system 100 according to an embodiment of the present invention will be described with reference to the drawings. The following description is only one example of the program creation system according to the present invention, and can be appropriately changed without changing the gist of the present invention.

(1) Overall Overview The program creation / execution system 100 of this embodiment is used to register information in a database and create a program (application software) that utilizes the registered information. The program creation / execution system 100 is also a system for executing the created program in the actual operating environment, not in the test environment being created, to put it into an implementation state.

  In the present embodiment, as a program created by the program creation / execution system 100, creation of a customer management program will be described as an example. However, as described above, the program generated by the program creation / execution system 100 is not limited to the customer management program, but may be used for other purposes such as employee management, document management, and product development project management. It may be a program used. The program creation / execution system 100 can create a wide variety of programs.

  The program creation / execution system 100 according to the present embodiment is a system that allows a program creator to create a program in a non-programming environment. In other words, the program creation / execution system 100 is a system that allows a program creator to create a program without coding. Coding refers to describing a program that can be processed by a computer using a programming language. The program creation / execution system 100 generates a program described in a program language such as SQL (Structured Query Language) by combining program parts (program patterns) prepared in advance by operating a GUI (Graphical User Interface). To do. For example, in the program creation / execution system 100, the program creator arranges program parts prepared in advance on the screen for program creation by arranging them by a mouse operation such as drag and drop, thereby performing a desired process. Generate a program to be executed.

  Note that the language of the program to be created is not limited to SQL. Further, the non-programming environment here is not limited to an environment in which the program creator does not code at all. When creating a program using the program creation / execution system 100, the program creator may create at least a part of the program by coding.

  FIG. 1 is a block diagram showing a physical configuration of the program creation / execution system 100. The program creation / execution system 100 mainly includes a server 200.

  The server 200 is a computer including a CPU 201, an output unit 210, a reception unit 220, an input unit 230, a display unit 240, a storage unit 250 including a volatile memory and a non-volatile memory, a communication unit (not shown), and the like. is there. When the program creation support software stored in the storage unit 250 is executed, the CPU 201 of the server 200 becomes a control unit for providing a program creation function. The CPU 201 serving as the control unit functions as functional units such as a program creation support unit 260 and a data replication unit 280.

  Note that the server 200 is not software for supporting program creation, but other programs stored in the storage unit 250 (including programs for customer management created by the program creation / implementation system 100 of the present embodiment). When executed, the CPU 201 functions as each functional unit for performing processing by other programs. Thereby, as described above, the created program can be executed in an actual operating environment and put into an implementation state. For example, if the customer management program is executed and put into an implementation state, the program creation / execution system 100 functions as a customer management system.

  The server 200 is connected to client terminals 10A, 10B, and 10C used by a person who develops and creates a program (hereinafter referred to as a program creator). The program creator uses the program creation / execution system 100 via the network 50 from the client terminals 10A, 10B, and 10C to create a program. In FIG. 1, the program creation / execution system 100 is connected to the three client terminals 10A, 10B, and 10C via the network 50, but the number of client terminals is merely an example and is limited to this. It is not a thing.

  If the server 200 executes the customer management program as described above and puts it into the implementation state, the client terminals 10A, 10B, and 10C are searched by the end user who uses the program creation / execution system 100 that functions as the customer management system. And will be used as a terminal for input / output.

  In the present embodiment, the network 50 is the Internet. However, the network 50 is not limited to the Internet. The network 50 may be a LAN (Local Area Network), an intranet, or the like.

(2) Detailed Description (2-1) Client Terminal At the time of program creation, the client terminals 10A, 10B, and 10C are computers that receive provision of a program creation support function from the server 200.

  The client terminals 10A, 10B, and 10C are, for example, general personal computers. The client terminals 10A, 10B, and 10C include, for example, a CPU (Central Processing Unit) (not shown), a storage unit such as a memory, a communication unit, and the like. The client terminals 10A, 10B, and 10C have input units 20A, 20B, and 20C such as a keyboard, a mouse, and a touch panel, respectively. Furthermore, the client terminals 10A, 10B, and 10C include display units 30A, 30B, and 30C such as displays. When the program in the storage unit is read and executed, the CPUs of the client terminals 10A, 10B, and 10C execute various processes.

  The client terminals 10A, 10B, and 10C are all configured similarly. For this reason, only the client terminal 10A (only the input unit 20A and the display unit 30A of the client terminal 10A) will be described below, and descriptions of the other client terminals 10B and 10C will be omitted.

(2-1-1) Input unit The input unit 20A is used for an operation screen displayed on the display unit 30A described later by a program creator or an end user (a user of the created application program for customer management). It is an input device used when operating.

  The operation performed from the input unit 20A on the operation screen displayed on the display unit 30A includes a predetermined operation for changing information in the data tables 310 to 350 of the test database 300 of the server 200 described later. Further, the operations performed from the input unit 20A include operations of answer input and selection input by the program creator in steps S11, S16, and S17 of FIG.

  An operation on the operation screen displayed on the display unit 30A using the input unit 20A is received by the receiving unit 220 of the server 200 described later via the network 50.

(2-1-2) Display Unit The display unit 30A displays various screens in order to present various information to the program creator and the end user.

  Here, the display content displayed on the display unit 30A when the program creator tests a program created using the program creation / execution system 100 will be described. In particular, here, when a predetermined operation is performed on the screen, the operation check test of the program when the predetermined operation is performed on the operation screen in which the information in the data tables 310 to 350 of the test database 300 of the server 200 is changed. The contents displayed on the display unit 30A when implemented will be described.

  During the operation check test, an operation screen 32A, a first history screen 34A, and a second history screen 36A are displayed on the display unit 30A (see FIG. 2). The operation screen 32A, the first history screen 34A, and the second history screen 36A are simultaneously displayed on the display unit 30A. The operation screen 32A, the first history screen 34A, and the second history screen 36A are screens that the output unit 210 of the server 200 described later displays on the display unit 30A. That is, the display unit 30A controls the display contents by the output unit 210 of the server 200 so that the operation screen 32A, the first history screen 34A, and the second history screen 36A are displayed simultaneously during the operation check test.

  Hereinafter, each of the screens 32A, 34A, and 36A will be described with reference to FIG.

(2-1-2-1) Operation Screen FIG. 2 shows an operation screen 32A for registering new information in a data table named customer master existing in the test database 300 of the server 200 described later. ing. The operation screen 32A is a screen that is actually used by the end user of the completed program when the program is completed.

  The operation screen 32A is an example of an operation screen related to data table information. In the operation screen 32A, a customer number, a customer name, a telephone number, and a person in charge are input from a keyboard that is an example of the input unit 20A in a text box that is displayed, and a “Save” button that is displayed is an example of the input unit 20A. An operation of clicking with a mouse can be performed. When such a predetermined operation is performed on the operation screen 32A, the operation screen 32A is created so that processing for newly registering information input in the text box of the operation screen 32A in the data table named customer master is performed. Has been. Specifically, for example, when the information registration operation is performed once on the operation screen 32A, the operation screen is displayed so that one line of information is newly registered in the data table of the customer master as shown in FIG. 32A has been created.

  The operation screen created using the program creation / execution system 100 is not limited to the operation screen 32A. The operation screen created by using the program creation / execution system 100 is not the operation screen 32A, or in addition to the operation screen 32A, the content change (update) of the information in the data table or the information from the data table. A screen used for deletion may be included.

  For example, the operation screen for changing (updating) the information contents of the data table includes a customer number used for specifying information to be updated, a text box used for inputting the updated contents, and information on the data table. An “update” button or the like for performing update processing is displayed. For example, the operation screen for deleting information in the data table is a text box used for inputting a customer number used for specifying information to be deleted, and a process for deleting information in the data table. Delete button etc. are displayed.

  However, the configuration of the operation screen for changing (updating) the content of information in the data table and deleting the information is not limited to the screen configuration illustrated here, and may be appropriately designed.

  When a predetermined operation is performed on the operation screen 32A using the input unit 20A during the operation check test, the content of the predetermined operation is received by the receiving unit 220 of the server 200 described later via the network 50. As will be described later, the command generation unit 264 of the server 200 generates a command corresponding to a predetermined operation received by the reception unit 220. Then, the changing unit 266 of the server 200 changes the information in the data table of the test database 300 in accordance with the command generated by the command generating unit 264. In addition, when a predetermined operation is performed on the operation screen 32A via the input unit 20A during the operation check test, the data table change history is displayed on the first history screen 34A and the second history screen 36A.

  It should be noted that an error that occurs when an operation is performed on the operation screen 32A during an operation check test and that is not related to a change in the information in the data tables 310 to 350 of the test database 300 is described by the program creator. This can be confirmed by looking at the area where the operation screen 32A is displayed on the display unit 30A. For example, if the program is designed so that a screen other than the operation screen 32A (for example, a confirmation screen) pops up when the “Save” button is pressed on the operation screen 32A, the program creator does not display this screen. This can be confirmed on the display unit 30A.

(2-1-2-2) First History Screen The first history screen 34A is an example of a history screen showing a data table change history corresponding to a predetermined operation on the operation screen 32A.

  On the first history screen 34A, a list of names of data tables (data tables 310 to 350) included in the test database 300 of the server 200 is displayed. For example, the first history screen 34A in FIG. 2 indicates that the test database 300 has data tables named “order received”, “order received details”, “customer master”, “employee master”, and “product master”. Show.

  Further, on the first history screen 34A, a message M1 is displayed as a change history of the data table in association with the name of each data table (adjacent to the right of the name in FIG. 2). In the first history screen 34A of FIG. 2, it is assumed that information has not been changed for the data tables named “employee master” and “product master” (the information in these data tables is , It is assumed that it will be referenced only). Therefore, the message M1 is not displayed next to the characters “employee master” and “product master”.

  Message M1 shows a summary of the information changes most recently executed in the data table to which message M1 is attached. The message M1 includes, in the data table, information indicating which information change was most recently executed among information registration, information content change (update), and information deletion. Further, the message M1 includes information on the number of information items that have been changed most recently. For example, when a data table as shown in FIG. 3 exists, the message M1 includes information on how many lines of information are registered, changed (updated), or deleted in the data table.

(2-1-2-3) Second History Screen The second history screen 36A is an example of a history screen that shows a data table change history according to a predetermined operation on the operation screen 32A.

  The second history screen 36A also shows the reference history of the data table in addition to the change history of the data table. The reference history of the data table displayed on the second history screen 36A indicates a history in which the information in the data table is referred to by the program creation support unit 260 of the server 200 for some processing. The reference to the data table information does not change the data table information.

  In the second history screen 36A, for example, the change history of the data table corresponding to the predetermined operation on the operation screen 32A and the reference history of the data table are displayed in time order so that the latest history is displayed at the top of the list. Displayed in list format. That is, on the second history screen 36A, the change history of the data table is displayed in order of time, not by data table. On the second history screen 36A, the change history of the data table and the reference history of the data table are not displayed separately, but the change history and the reference history are displayed side by side in time order. If the change history and the reference history increase too much and cannot be displayed on the display unit 30A at the same time, the second history screen 36A can be referred to by scrolling the screen so that all the change history and reference history can be referred to. It is configured.

  In the second history screen 36A, the data table change history is displayed using the message M2. In the message M2 indicating the change history, the information of which data table has been changed, what information has been changed (registration, content change (update), deletion), and how many pieces of information have been changed Is included in the message content. On the second history screen 36A, the reference history of the data table is also displayed using the message M2. The message M2 indicating the reference history includes in the content of the message which data table information has been referenced and how many pieces of information have been referenced.

  Each of the change history and the reference history of the data table displayed on the second history screen 36A (each row of the change history and the reference history displayed in the list format on the second history screen 36A) is, for example, by the mouse of the input unit 20A. It can be specified by clicking. A history specifying operation on the second history screen 36 </ b> A displayed on the display unit 30 </ b> A using the input unit 20 </ b> A is received by the receiving unit 220 of the server 200 described later via the network 50. When the accepting unit 220 accepts a history specifying operation, the display unit 30A displays details of data table information changes or data table for the history designated by the input unit 20A by the output unit 210 of the server 200 described later. The details of the reference content of the information are displayed on the display unit 30A. The details of the changed contents of the information in the data table indicate what kind of information is registered / changed / deleted in the data table information. The details of the reference contents of the information in the data table indicate what kind of information is specifically referred to in the data table information.

(2-2) Server The server 200 is a computer that provides a program creation support function to the client terminals 10A, 10B, and 10C used by the program creator.

  As described above, the server 200 includes the CPU 201, the output unit 210, the reception unit 220, the input unit 230 such as a keyboard and a mouse, the display unit 240 such as a display, the storage unit 250 including a memory and a hard disk, and the like. It is a computer.

(2-2-1) Output unit The output unit 210 is used when the program creator uses the program creation / execution system 100 in the client terminals 10A, 10B, and 10C connected to the server 200 via the network 50. In addition, various screens are displayed on the display units 30A, 30B, and 30C. That is, the output unit 210 is a display control unit that controls display contents of the display units 30A, 30B, and 30C of the client terminals 10A, 10B, and 10C connected to the server 200.

  When the above-described operation check test is performed in the client terminals 10A, 10B, and 10C, the output unit 210 displays an operation screen related to data table information on each of the display units 30A, 30B, and 30C of the client terminals 10A, 10B, and 10C. (For example, the operation screen 32A in FIG. 2) and a history screen showing a change history of the data table corresponding to a predetermined operation on the operation screen are displayed simultaneously. Further, the output unit 210 displays an inquiry screen and a data selection screen for the program creator in steps S11, S16, and S17 of FIG. 4 described later on the display units 30A, 30B, and 30C of the client terminals 10A, 10B, and 10C. Let

(2-2-2) Reception unit Data table of test database 300 displayed on display units 30A, 30B, and 30C, which is performed using input units 20A, 20B, and 20C in client terminals 10A, 10B, and 10C, respectively. The accepting unit 220 accepts an operation (including a predetermined operation) on the operation screen related to information 310-350 via the network 50. The predetermined operations on the operation screens displayed on the display units 30A, 30B, and 30C include operations for changing information in the data tables 310-350 (information registration, information content change (update), information deletion). Including. The operation on the operation screen displayed on the display units 30A, 30B, and 30C includes an operation for referring to information in the data tables 310-350. Note that which information in which data table 310 to 350 is to be changed / referenced by an operation on the operation screen is defined in the program being created.

  The receiving unit 220 receives a predetermined operation on the operation screen displayed on each of the display units 30A, 30B, and 30C of the plurality of client terminals 10A, 10B, and 10C for each of the display units 30A, 30B, and 30C.

  Upon receiving a predetermined operation on the operation screen related to information in the data tables 310 to 350, the reception unit 220 transmits information related to the predetermined operation to the command generation unit 264 of the program creation support unit 260 described later. The information regarding the predetermined operation includes information regarding the content of the predetermined operation (what information is to be changed with respect to any of the data tables 310 to 350 of the test database 300).

  In addition, when the accepting unit 220 accepts an answer operation or a selection operation by the program creator in steps S11, S16, and S17 of FIG.

(2-2-3) Storage Unit The storage unit 250 stores program creation support software for causing the CPU 201 to perform program creation support processing and data replication processing.

  The storage unit 250 stores various information necessary for causing the program creation / execution system 100 to function.

  The storage unit 250 further includes a first storage area 251 for storing the implementation database 400 and a second storage area for storing a test database 300 different from the implementation database 400, which will be described below. 252.

(2-2-3-1) Database The implementation database 400 and the test database 300 are generated by the database generation unit 261 described later and stored in the storage unit 250. The implementation database 400 is stored in the first storage area 251 of the storage unit 250, and the test database 300 is stored in the second storage area 252 of the storage unit 250.

  The test database 300 is a database accessed by an incomplete program when the incomplete program being created is tested. The test database 300 includes data tables 310, 320, 330, 340, and 350 that are defined when a program is created using the program creation / execution system 100. In FIG. 2, the test database 300 includes five data tables 310 to 350, but the number of data tables is not limited to the exemplified quantity.

  The implementation database 400 executes a completed program, and is accessed by the program when the end user receives a service provided by the program (for example, a customer management service including a search function in the case of a customer management program). Database. Like the test database 300, the implementation database 400 also includes data tables 410, 420.

(2-2-4) Program Creation Support Unit The program creation support unit 260 is one functional unit in the CPU 201 that functions as a control unit when the software for program creation support described above is executed. Perform various processes. In particular, among the processes executed by the program creation support unit 260, a process by the database generation unit 261 that creates a database at the start of program creation and each process related to the operation check test will be described. Regarding the operation confirmation test, the program creation support unit 260 functions as an operation screen generation unit 262, a command generation unit 264, a change unit 266, and a history screen generation unit 268.

(2-2-4-1) Database Generation Unit The database generation unit 261 selects that the program creator uses (utilizes) an existing implementation database used by another existing program at the start of program creation. In this case, a part or all of the existing implementation database is copied to generate a test database for a newly created program. In addition, when the program creator does not select to use the existing implementation database, the database generation unit 261 newly generates the test database 300 and the implementation database 400 at the same time, and stores the storage unit 250 of the server 200. (See FIG. 1). As described above, the implementation database 400 is stored in the first storage area 251, and the test database 300 is stored in the second storage area 252. At the same time, the test database 300 and the implementation database 400 have exactly the same contents.

  Since the data duplication unit 280 is provided as will be described later, the program creation / execution system 100 can partially copy data between the test database 300 and the implementation database 400. .

(2-2-4-2) Operation Screen Generation Unit The operation screen generation unit 262 causes the output unit 210 to display on the display units 30A, 30B, and 30C of the client terminals 10A, 10B, and 10C during the operation check test. Then, an operation screen related to data table information is generated.

  The operation screen generation unit 262 reads out the operation screen layout created in the program creation work from the storage unit 250 regarding the operation screen on which each of the client terminals 10A, 10B, and 10C performs the operation check test, and displays the operation screen. Generate. The operation screen generation unit 262 also performs various operations (such as inputting characters) on the operation screens displayed on the display units 30A, 30B, and 30C from the input units 20A, 20B, and 20C of the client terminals 10A, 10B, and 10C. If this is the case, an operation screen reflecting this is generated. The operation screen generated by the operation screen generation unit 262 for each of the client terminals 10A, 10B, and 10C is output by the output unit 210 to the display units 30A, 30B, and 30C of the client terminals 10A, 10B, and 10C.

  The operation screen generation unit 262 generates an inquiry screen for the program creator and a selection screen for data to be copied in steps S11, S16, and S17 of FIG. 4 to be described later.

(2-2-4-3) Command Generation Unit As described above, the reception unit 220 is one of the operation screens displayed on the display units 30A, 30B, and 30C of the plurality of client terminals 10A, 10B, and 10C. When a predetermined operation is accepted, information related to the predetermined operation is transmitted to the command generation unit 264. The information related to the predetermined operation includes information for specifying the client terminals 10A, 10B, and 10C where the predetermined operation has been performed, and details of the predetermined operation (for any of the data tables 310 to 350 of the test database 300). Information on what information changes will be made). For example, information transmitted from the reception unit 220 to the command generation unit 264 includes a customer number “0000003”, a customer name “CCC”, a telephone number “ZZ-ZZZZ-ZZZ” This is information that can specify that the operation of registering the information “FFF like” in one of the data tables (a data table named customer master, for example, the data table 310) has been performed.

  When the command generation unit 264 receives information related to the predetermined operation from the reception unit 220, the command generation unit 264 generates a command corresponding to the predetermined operation. For example, the command generation unit 264 newly registers information such as the customer number “0000003”, the customer name “CCC”, the telephone number “ZZ-ZZZZ-ZZZ”, and the person in charge “FFF” in the data table 310. When information related to a predetermined operation is received, a command for causing the changing unit 266 described later to execute such processing on the data table 310 is generated.

  The commands generated by the command generation unit 264 include registration of information in any of the data tables 310-350, change (update) of contents of any information in the data tables 310-350, and data tables 310-350. Including deletion of information.

  In addition, when receiving information related to the predetermined operation from the reception unit 220, the command generation unit 264 receives information for specifying the client terminals 10A, 10B, and 10C on which the predetermined operation has been performed, and the command created as described above. Are transmitted to the history screen generation unit 268.

(2-2-4-4) Changing Unit The changing unit 266 changes the information in the data table 310-350 instructed to change in accordance with the command transmitted from the command generating unit 264. As described above, the command is generated by the command generation unit 264 according to a predetermined operation on the operation screen displayed on the display units 30A, 30B, and 30C of any of the client terminals 10A, 10B, and 10C. That is, the changing unit 266 is information on the data tables 310 to 350 instructed to change in accordance with a predetermined operation on the operation screen displayed on the display units 30A, 30B, and 30C of any of the client terminals 10A, 10B, and 10C. To change.

(2-2-4-5) History Screen Generation Unit The history screen generation unit 268 causes the output unit 210 to display on the display units 30A, 30B, and 30C of the client terminals 10A, 10B, and 10C during the operation check test. Generate a history screen. The history screen is a screen showing a change history of the data table according to a predetermined operation on the operation screen displayed on the display units 30A, 30B, and 30C of the client terminals 10A, 10B, and 10C.

  Here, a case where the history screen generation unit 268 generates a history screen to be displayed on the display unit 30A of the client terminal 10A will be described as an example. Here, it is assumed that the history screen generation unit 268 generates the first history screen 34A and the second history screen 36A as shown in FIG.

  The history screen generation unit 268 generates a message M1 and a message M2 to be displayed on the first history screen 34A and the second history screen 36 as the change history of the data table 310-350. The message M1 and the message M2 are generated by a message generation unit 268a that is a functional unit of the history screen generation unit 268.

  When the operation check test is performed in the client terminal 10A, the output unit 210 operates the first history screen 34A and the second history screen 36A (including the message M1 and the message M2) generated by the history screen generation unit 268. Simultaneously with the operation screen generated by the screen generation unit 262, the screen is displayed on the display unit 30A of the client terminal 10A.

  In addition, the history screen generation unit 268 displays details of the information change contents or reference contents of the data table 310-350 to be displayed on the display unit 30A of the client terminal 10A when the reception unit 220 receives the above-described designation operation. Generate a screen to display. A screen for displaying details of the information change contents or reference contents of the data tables 310 to 350 is generated by the detail display generation unit 268b, which is a functional unit of the history screen generation unit 268.

  When the operation check test is performed in the client terminal 10A and the accepting unit 220 accepts the designation operation, the output unit 210 changes the information contents or reference contents of the data table 310-350 generated by the detail display generating unit 268b. A screen for displaying details is displayed on the display unit 30A of the client terminal 10A.

(2-2-5) Data Duplicating Unit Similarly to the program creation support unit 260, the data replication unit 280 is a function unit in the CPU 201 that functions as a control unit when the program creation support software is executed. is there. The data duplication unit 280 performs a process of causing partial data copying between the test database 300 and the implementation database 400. The data replication unit 280 includes a first replication processing unit 281 and a second replication processing unit 282. The first replication processing unit 281 causes the program creator to select some data from the data stored in the test database 300, and copies the selected data and stores it in the implementation database 400. The data stored in the test database 300 is data input by a program creator when testing an incomplete program being created (operation check test).

  For example, the customer number, the customer name, the telephone number, and the data of the person in charge input while looking at the operation screen 32A in the operation check test described above are registered in the data table 310 named customer master. The information (data) registered in the data table 310 of the customer master such as 3 is data input by the program creator.

  In addition, the first replication processing unit 281 may cause the program creator to select a part of the data in each data table of the test database 300 and copy the selected data to store in the implementation database 400. it can. For example, from the customer number, customer name, telephone number, and person-in-charge data registered in the customer master data table 310 of the test database 300 described above, the program creator inputs based on the actual operation information. It is assumed that the customer number and customer name data are selected, and the telephone number and the person in charge data are not selected. In this case, the first replication processing unit 281 extracts and copies only the customer number and customer name data from the data table 310 of the customer master of the test database 300 and copies these data to the customer of the implementation database 400. The data is stored in the master data table 410.

  Similarly, the second replication processing unit 282 causes the program creator to select some data in each data table of the implementation database 400, and copies the selected data and stores it in the test database 300. Can do.

(3) Flow of Program Creation Processing by Program Creation / Execution System Next, the flow of program creation using the program creation / execution system 100 will be described with reference to FIG. Here, the description will proceed on the assumption that the program creator is working using the client terminal 10A.

  When program creation is started, a screen asking whether or not to use (utilize) an existing implementation database accessed by another program appears on the display unit 30A of the client terminal 10A (step S11). If the program creator inputs YES here, the existing implementation database selected by the program creator is copied and becomes the test database (step S12). Here, the program creator can generate a test database by copying all data in the existing implementation database. In addition, the program creator creates a test database by selecting a predetermined data table in the existing implementation database in units of files or selecting only a part of the data in the predetermined data table. It can also be made.

  When the program creator inputs NO in step S11, a new implementation database 400 and test database 300 are generated (step S13). The implementation database 400 is stored in the first storage area 251 of the storage unit 250 illustrated in FIG. 1, and the test database 300 is stored in the second storage area 252. The implementation database 400 and the test database 300 are the same at the time of generation.

  After step S12 or step S13, the process proceeds to step S14, where the program creator creates a program using the function of the program creation support unit 260 of the server 200. As described above, the program creation / execution system 100 can generate a program described in a program language such as SQL by combining program parts prepared in advance by operating the GUI.

  In addition, the program creator tests the incomplete program being created in step S15. Specifically, the above-described operation check test is performed.

  The process proceeds to step S16, and when the program creator determines that the program being created is completed and inputs it from the input unit 20A of the client terminal 10A, the process proceeds to the next step S17.

  In step S17, the data duplication unit 280 of the server 200 confirms the intention of the program creator before releasing the completed program. Specifically, the data replication unit 280 determines whether or not to copy the data input in the program operation check test, that is, a part of the data stored in each data table of the test database 300 to the implementation database 400. Is displayed on the display unit 30A of the client terminal 10A. If the program creator inputs YES here, the process proceeds to step S18, where the first replication processing unit 281 of the data replication unit 280 copies a part of the data in the test database 300 to the implementation database 400 and stores it. To do. More specifically, as described above, the first replication processing unit 281 causes the program creator to select some data in each data table of the test database 300 or the data table of the test database 300 The selected data is copied and stored in the implementation database 400.

  As a result, when the completed program is executed, the execution database 400 accessed by the program already contains the data input during the operation check test. For this reason, the problem that the end user has to input the same data redundantly in the operation stage after the completion program is executed and put into the implementation state is solved.

(4) Features of the program creation / implementation system (4-1)
If the database that the program accesses when testing the program being created and the database that the program accesses when the program is actually executed and placed in the implementation state, an incomplete program will be Problems occur due to unexpected processing during testing. In view of this, a program test environment and an operation environment are conventionally distinguished, and for example, a server that provides a test environment and a server that provides an operation environment are often separated. The program creator conventionally copies data manually to match the data between the test database used in the test environment and the implementation database used in the operational environment. The burden of this work is great.

  Further, manual data copying is often performed by a method of backing up the entire implementation database used in the operation environment and restoring the backup data in the test environment.

  For this reason, conventionally, the data in the test database input and constructed in the test environment cannot be easily reflected in the operation environment.

  In view of such a conventional problem, the data creation unit 280 is provided in the program creation / execution system 100 according to the present embodiment. A part of the data input in the test (operation check test) and stored in the test database 300 is copied and stored in the execution database 400 by selection by the program creator. The first replication processing unit 281 of the data replication unit 280 performs processing for causing the creator to select a part of the data and processing for storing the selected data in the implementation database 400.

  Thus, in the program creation / execution system 100, the program creator simply selects a part of the data in the test database 300, and this is reflected in the implementation database 400. Therefore, according to the program creation / execution system 100, the data input at the time of testing the program being created and stored in the test database 300 can be easily reflected in the implementation database 400 and utilized.

(4-2)
In addition, since the program creation / implementation system 100 of this embodiment includes the second replication processing unit 282 in addition to the first replication processing unit 281, the program creator can store data in the test database 300 or the implementation database 400. Simply select a part of it and it will be reflected in the other database. That is, when the program creator selects a part of the data in the test database 300 or the execution database 400, the data copy processing is performed between the test database 300 and the execution database 400. . Therefore, the utilization of the data stored in the test database 300 and the utilization of the data stored in the implementation database 400 are facilitated.

(4-3)
In the program creation / execution system 100 according to the present embodiment, if the program creator desires, the implementation database 400 accessed by the completed program at the start of program creation, specifically in step S13 shown in FIG. A test database 300 accessed by the incomplete program is also generated at the same time. This eliminates the need for the program creator to manually create an implementation database, or to manually copy the implementation database to create a test database at the start of program creation.

(4-4)
In the program creation / execution system 100 of this embodiment, the first replication processing unit 281 of the data replication unit 280 causes the program creator to select a part of the data in each data table of the test database 300 and is selected. The data can be copied and stored in the implementation database 400. In addition, the second replication processing unit 282 may cause the program creator to select some data in each data table of the implementation database 400 and copy the selected data to store in the test database 300. it can.

  As described above, conventionally, there is a situation in which data is manually copied in order to match data between the test database and the implementation database. However, even though it was easy to copy the entire database, it was not easy to select a data table and copy it manually. Furthermore, it is very difficult and error-prone to manually extract only a part of the data in the data table and store it in the same data table in the other database.

  On the other hand, in the program creation / execution system 100 of this embodiment, for example, only the customer number and customer name data are selected from the information registered in the data table 310 of the customer master of the test database 300, and the telephone number, The data of the person in charge is not selected, and only the former can be easily reflected in the implementation database 400. As a result, it is possible to greatly reduce the work burden on the program creator.

(4-5)
The present invention can also be applied to a program creation / execution system in which a server that provides a test environment and a server that provides an operational environment are separated. An implementation database 400 and a test database 300 are placed in a storage unit 250 built in or externally attached to the server 200. Therefore, a series of operations such as program development / creation, testing, and release can be performed by one server 200.

(4-6)
In the program creation / execution system 100 of this embodiment, the data replication unit 280 of the server 200 confirms the intention of the program creator before the release of the completed program (see step S17 in FIG. 4). Specifically, the program creator is asked whether or not to copy the data input in the program operation check test, that is, a part of the data stored in each data table of the test database 300 to the implementation database 400. Ask.

  Because of this configuration, the program creation / execution system 100 according to the present embodiment, such as personal information of new employees who will join the company in the near future, should not be shown to the end user before releasing the program, It is also possible to store only in the test database 300 separated from the end user. Then, after the new employee joins the company, the data in the test database 300 can be copied to the implementation database 400.

  Of course, it is not impossible to consolidate the test database 300 and the implementation database 400 into one database. In that case, however, each data is not visible to the end user until April, and the end of the database after April. It is necessary to set a flag to make it visible to the user, which causes a disadvantage that the data capacity increases and the complexity of data input increases.

100 Program creation / execution system (program creation system)
250 storage unit 251 first storage area (first storage unit)
252 Second storage area (second storage unit)
261 Database generation unit 280 Data replication unit 281 First replication processing unit (first data replication processing unit)
282 Second replication processing unit (second data replication processing unit)
300 Test database 310, 320, ... Data table (test file)
400 Implementation database 410, 420, ... Data table (execution file)

JP 2012-216000 A

Claims (5)

A first storage unit (251) for storing an implementation database (400) accessed by the program when a user of the completed program executes the program;
A second storage unit (252) for storing a test database (300) different from the implementation database, which is accessed when a creator who creates the program tests an incomplete program being created. When,
From the data input by the creator and stored in the test database when testing the incomplete program, the creator is allowed to select a part of the data, and the selected data is copied and the execution is performed. A first data replication processing unit (281) stored in the database for use;
A program creation system (100). A second data replication processing unit (282) for causing the creator to select a part of the data stored in the implementation database, copying the selected data and storing the selected data in the test database;
The program creation system according to claim 1, further comprising: A database generation unit (261) for simultaneously generating the implementation database and the test database at the start of the creation of the program;
The program creation system according to claim 1, further comprising: The test database has test files (310, 320,...) That are data tables,
The first data replication processing unit causes the creator to select a part of the data in the test file, and copies the selected data and stores it in the implementation database.
The program creation system according to any one of claims 1 to 3. The implementation database has implementation files (410, 420,...) That are data tables,
The second data replication processing unit causes the creator to select a part of the data in the implementation file, and copies the selected data and stores it in the test database.
The program creation system according to claim 2.

Images