JP2012181650A - Operation system and server device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide technology for enabling a user himself or herself to execute alteration for function addition, and to perform file update in an uninterruptible manner.SOLUTION: A server device of an operation system includes: an engine unit; a picture generation unit; a DB unit; a management unit; and a base unit. A client device includes: a work flow editor; a DB edition editor; and a picture edition editor. The engine unit executes a workflow following the description of a scenario. The management unit manages a scenario, picture data, components of the scenario, components of a DB, and components of the picture data. The work flow editor fetches the components of the scenario, and creates and edits the scenario by combining the components of the scenario. The DB edition editor fetches the components of the DB, and creates and edits the DB by combining the components of the DB. The picture edition editor fetches the components of the picture data, and creates and edits the picture data by combining the components of the picture data.

Description

  The present invention relates to an operation system and a server device that can add, change, and delete functions in accordance with changes in services provided by the system and supported operations.

  With the diversification of user needs and intensifying changes in social conditions, the addition of system functions is required to be quick. System functions are added to establish necessary tasks, develop systems, test, and update files, and are being shortened in each phase.

(1) Establishing the necessary work The main contents of establishing the work are visualizing the specifications using a prototype model to support early grasping of potential needs through marketing in order to advance the start of development and examination of necessary work. It has become.
(2) Shortening the development period The development period is shortened by improving the development efficiency by establishing an integrated development environment and reducing the development scale by reusing programs and diversifying configuration files.
(3) Shortening of tests It is difficult to reduce test items because test digestion items and quality (number of bugs found) are often related to the Gombelz curve. The period is shortened.
(4) Reflection frequency of changed programs (file update)
Basically, the process needs to be restarted, so the service is interrupted and the file cannot be updated frequently. For this reason, when adding a current function, a process is restarted with a shortened service interruption time, such as a redundant configuration, and a function addition without interruption is performed by limiting the functions that can be changed.

  As an attempt to shorten the period until the system function is added, techniques such as Patent Document 1 and Patent Document 2 are provided. The technique of Patent Document 1 realizes function editing using a GUI by encapsulating functions with the concept of components. The technology of Patent Document 2 can be remodeled online by providing data input support.

  Large-scale systems ensure quality by developing and testing with a large number of people. However, originally, it is desirable that program development can be performed by a user who actually uses the program. Thus, with the development of an integrated development environment and the advent of business workflow editors, GUI programming has become mainstream and system development itself has been simplified. Further, a business workflow language called XML Process Definition Language (XPDL) is also provided, and an editor and an execution environment in which XPDL is implemented have been developed. A business workflow is a development method designed to allow users to add functions.

JP 2005-78650 A JP 2002-328941 A

  However, the technique of Patent Document 1 does not assume user programming, and cannot implement function update online. Further, the technique of Patent Document 2 can be modified only with a limited function of data input.

  In order to quickly add functions to the system, the user's required specifications must be designed quickly, the system operation according to the design can be efficiently guaranteed, and file updates can be performed at any time. Is required. The ideal for quickly adding system functionality is that the user can perform all such procedures. However, there are the following problems for the user to execute the program development.

(1) A user who is not familiar with the programming language cannot describe the function he / she wants to implement.
(2) Since the user does not know the internal operation of the system, the user cannot test the contents added by the user himself / herself.
(3) Since the material can be input into the system only by the system administrator or higher, the user cannot input the material into the system by his / her own hand.

  It is an object of the present invention to provide a technique that allows a user himself to perform modification for adding a function and can update a file without interruption.

  The operation system of the present invention includes a server device and a client device. The server device includes an engine unit, a screen generation unit, a DB unit, an ADP unit, a management unit, and a base unit. The client device includes a workflow editor, a DB editing editor, a screen editing editor, and a screen display unit. The engine unit activates the scenario and executes the workflow according to the description of the scenario. The screen generation unit generates a display screen to be displayed on the client device. The DB unit stores a DB (database) handled in the workflow. The ADP unit is a component for connecting to other systems. The management unit manages scenarios and screen data. The base unit executes various functions called from the engine unit. The workflow editor is used by the user to create and edit scenarios. The DB editing editor defines a DB schema and is used by a user to create a DB. The screen editing editor is used by the user to create screen data. The screen display unit displays a display screen and a screen for operating the workflow editor, DB editing editor, and screen editing editor. The management unit also manages scenario parts, DB parts, and screen data parts. The workflow editor can capture scenario parts, create and edit scenarios by combining scenario parts, and register them in the management unit. The DB editing editor can take in DB parts, create and edit DBs by combining DB parts, and register them in the DB unit. The screen editing editor can capture screen data components, create and edit screen data by combining screen data components, and register the screen data in the management unit.

  According to the operation system of the present invention, a user can customize a workflow, a database, and a screen (user interface) by providing an editor that can operate a component and a component in which processing logic and parameters are concealed.・ Distribute the edited material to the system. Therefore, the user can add functions to the system online without having to have a special programming language. As a result, it becomes possible to add a function at an arbitrary timing when the user needs it, and it is possible to quickly add a function.

The figure which shows the structural example of the operation system of this invention. The figure which shows the example of the processing flow in the case of registering a scenario. The figure which shows the example of the processing flow in the case of registering DB. The figure which shows the example of the processing flow in the case of registering screen data. The figure which shows the structure of the application example 1 of the operation system of this invention. The figure which shows the structure of the application example 2 of the operation system of this invention. The figure which shows the structure of the application example 3 of the operation system of this invention. The figure which shows the structure of the application example 4 of the operation system of this invention. The figure which shows the structure of the application example 5 of the operation system of this invention.

  Hereinafter, embodiments of the present invention will be described in detail. In addition, the same number is attached | subjected to the structure part which has the same function, and duplication description is abbreviate | omitted.

  FIG. 1 shows a configuration example of an operation system of the present invention. The operation system of the present invention includes a server device 100 and a client device 200. The server device 100 includes an engine unit 110, a screen generation unit 120, a DB unit 130, an ADP unit 140, a management unit 150, and a base unit 160. The client device 200 includes a workflow editor 210, a DB editing editor 220, a screen editing editor 230, and a screen display unit 240.

  The engine unit 110 records the scenarios 111-1 to 111-A in the scenario recording unit 115, selects and starts the scenario 111-a, and executes the workflow according to the description of the scenario 111-a (however, A Is an integer of 1 or more, a is an integer of 1 or more and A or less). More specifically, the scenario 111-a specified by the received information is triggered by information from another system (device) received by the ADP unit 140 or information indicating a user instruction from the client device 200 as a trigger. to start.

  The screen generation unit 120 records the screen data 121-1 to B (denoted as “screen D” in the drawing) in the screen data recording unit 125 (denoted as “screen D recording unit” in the drawing) and a dedicated screen. The data 129 is recorded and a display screen to be displayed on the client device 200 is generated using the screen data 121-b or the dedicated screen data 129 (where B is an integer of 1 or more, b is an integer of 1 or more and B or less). . The display screen may be a web browser or an original application.

  The DB unit 130 stores DBs 131-1 to C handled in the workflow. The DB may be a database, a file, or a process of storing in a memory. And the data of DB131-c is provided to the base | substrate part 160 as needed (however, C is an integer greater than or equal to 1, c is an integer greater than or equal to 1 and less than C). The ADP unit 140 includes ADPs 141-1 to 141 -D and connects to other systems using the ADP 141-d (where D is an integer of 1 or more and d is an integer of 1 to D).

  The management unit 150 manages scenarios 111-1 to A and screen data 121-1 to 121 -B. The management unit 150 also includes a component recording unit 155 and registration information 159. The part recording unit 155 includes scenario parts (scenario parts) 151-1 to E, DB parts (DB parts) 152-1 to F, screen data parts (screen data parts, but in the figure, "screen D parts" 153-1 to G are also managed (where E is an integer of 1 or more, F is an integer of 1 or more, and G is an integer of 1 or more). In the registration information 159, information on the activation conditions of the scenarios 111-1 to 111-A managed by the management unit 150 is recorded. The scenario parts 151-1 to E, the DB parts 152-1 to F, and the screen data parts 153-1 to G are a set in which necessary functions are input by combining the functions executed by the base unit 160 so that the user can understand them. Create in advance.

  The base unit 160 executes various functions called from the engine unit 110. More specifically, the base unit 160 includes an ADP-IF 161 that is an interface with the ADP unit 140, a DB-IF 162 that is an interface with the DB unit 130, and configuration units (the engine unit 110, the screen generation unit 120, and the DB unit 130). , ADP unit 140, management unit 150), a schedule function 164 for managing the order and timing of scenario execution, and PF functions 166-1 to 166-1 for realizing various other functions. As the PF function, for example, a function for notifying the engine unit 110 of information received by the ADP unit 140, an execution result of the scenario 111-a, contents of the DB 131-c, contents of the screen data 121-b, and the like are stored. There is a function of presenting via the screen generation unit 120 in response to a request from the device 200 (user request). Further, as one of the PF functions, a function of identifying a user based on information received from the client device 200 and specifying a scenario, DB, and screen data associated with the user may be provided.

  The workflow editor 210 is used by the user to create and edit the scenario 111-a. The workflow editor 210 can capture the scenario parts 151-1 to 151 -E, create and edit the scenario 111-a by combining the scenario parts, and register it in the management unit 150. The workflow editor 210 may be, for example, a GUI format or a CLI. Further, the scenario 111-a may be XPDL, XML, text, or a special binary format as long as it can be interpreted by the engine unit 110.

  The DB editing editor 220 defines the schema of the DB 131-c and is used by the user to create the DB 131-c. The DB editing editor 220 can take in the DB parts 152-1 to 152-1F, create and edit the DB 131-c by combining DB parts, and register it in the DB unit 130.

  The screen editing editor 230 is used by the user to create the screen data 121-b. The screen editing editor 230 can take in the screen data parts 153-1 to 153-1, create and edit the screen data 121-b by a combination of screen data parts, and register it in the management unit 150. The screen data 121-b may be Flash, Servlet, or html.

  The screen display unit 240 displays a display screen and a screen for operating the workflow editor 210, the DB editing editor 220, and the screen editing editor 230. The screen display unit 240 may be a web browser or a unique application.

  FIG. 2 shows an example of a processing flow when a scenario is registered. The scenario parts 151-1 to 151 -E are recorded in advance in the management unit 150 (S 1511). The user activates the workflow editor 210 on the client device 200 (S2101). The workflow editor 210 takes in the scenario parts 151-1 to 151-E from the management unit 150 (S2102). The user creates / edits the scenario 111-a using the workflow editor 210 (S2103). The workflow editor 210 stores the created / edited scenario 111-a in the management unit 150 (S2104).

  Thereafter, the user activates the display screen generated using the dedicated screen data 129 on the screen display unit 240 (S2401). The user sets an activation trigger for the scenario 111-a from the client device 200 (S2402). The management unit 150 registers the scenario 111-a, the start condition, and the execution mode in the registration information 159 (S1512). The execution mode is information for identifying the purpose of using the scenario 111-a such as the debug mode and the commercial mode. If it is a newly registered scenario, first check the operation in the debug mode and then switch to the commercial mode. The management unit 150 notifies the base unit 160 that the scenario has been changed (S1513). The base unit 160 notifies the engine unit 110 that the scenario has been changed (S1671). The engine unit 110 acquires a new scenario 111-a via the base unit 160 (S1111).

  Then, the base unit 160 receives information from another system (device) received by the ADP unit 140 or information indicating a user instruction from the client device 200 as one of the start conditions of the scenarios 111-1 to A. It is confirmed whether they match (S1672). When the activation conditions of the scenario 111-a are met, the scenario 111-a is activated (S1673). The engine unit 110 executes the scenario 111-a (S1112). In the execution of the scenario 111-a, the engine unit 110 sequentially calls the functions of the base unit 160 in accordance with the description of the scenario 111-a (S1113-1 to P), and the base unit 160 uses the PF functions 166-1 to H and the like. The function called using is executed (S1674-1 to P) (where P is an integer of 1 or more).

  FIG. 3 shows an example of a processing flow when registering a DB. DB parts 152-1 to 152-1F are recorded in the management unit 150 in advance (S1521). The user activates the DB editing editor 220 on the client device 200 (S2201). The DB editing editor 220 fetches the DB parts 152-1 to 152-1F from the management unit 150 (S2202). The user defines the schema of the DB 131-c with the DB editing editor 220, and creates and edits the DB 131-c (S2203). The DB editing editor 220 saves the created / edited DB 131-c in the DB unit 130 (S2204). The DB 131-c is used when a corresponding scenario is executed.

  FIG. 4 shows an example of a processing flow for registering screen data. Screen data components 153-1 to 153-1G are recorded in the management unit 150 in advance (S1531). The user activates the screen editing editor 230 on the client device 200 (S2301). The screen editing editor 230 takes in the screen data parts 153-1 to 153-1 to G from the management unit 150 (S2302). The user creates / edits the screen data 121-b using the screen editing editor 230 (S2303). The screen editing editor 230 stores the created / edited screen data 121-b in the management unit 150 (S2304). The management unit 150 stores the screen data 121-b in the screen generation unit 120 (S1532). The screen data 121-b is used when a corresponding scenario is executed.

  According to the operation system of the present invention, a user can customize a workflow, a database, and a screen (user interface) by providing an editor that can operate a component and a component in which processing logic and parameters are concealed.・ Distribute the edited material to the system. Therefore, the user can add functions to the system online without having to have a special programming language. As a result, it becomes possible to add a function at an arbitrary timing when the user needs it, and it is possible to quickly add a function.

<Application example 1>
FIG. 5 shows a configuration of an application example 1 of the operation system of the present invention. In this configuration, monitoring devices 400-1 to 400 -L are connected to the server device 100 (where L is an integer equal to or greater than 1). The monitoring devices 400-1 to 400-L are connected to and monitor the exchanges 420-1 to 420-J, the base stations 430-1 to K, etc. (where J is an integer of 1 or more and K is an integer of 1 or more). The user can maintain the exchanges 420-1 to J and the base stations 430-1 to 430 -K using the monitoring screens 410-1 to 410 -L of the monitoring devices 400-1 to L. By creating a scenario _{111-a 1} business what the user is maintaining utilizing monitoring screen 410-1～L, the server apparatus 100 can maintain as described in scenario _{111-a 1.} Further, when the types of exchanges and base stations increase, when the maintenance content is changed or a new business flow is added, a new scenario 111-a for maintenance online from the workflow editor 210 via the management unit 150. ₁ 'can be added.

<Application example 2>
FIG. 6 shows a configuration of an application example 2 of the operation system of the present invention. This configuration shows a case where a business support tool is added to Application Example 1. The failure management device 510 is a device for managing failure information and arranging necessary hardware. The construction management device 520 is a device for managing construction information of the exchanges 420-1 to J and the base stations 430-1 to K. The facility planning device 530 is a device for planning the number of facilities from the traffic amounts of the exchanges 420-1 to 420-J and the base stations 430-1 to 430-K. By creating a scenario 111-a ₂ of business content a user to input information to various apparatus, fault management apparatus 510, work management apparatus 520, information on the facility planning device 530 can be automatically input. Further, when the usage method of the business support tool is changed, it can be followed by changing to the scenario 111-a ₂ ′ for inputting the support tool.

<Application example 3>
FIG. 7 shows a configuration of an application example 3 of the operation system of the present invention. This configuration shows a case where Internet servers 600-1 to 600 -M are connected to the server apparatus 100 (where M is an integer of 1 or more). By creating a scenario _{111-a 3} for the service, you can use multiple Internet servers 600-1~M and cloud services. For example, when providing Web game Internet server 600-1, it is simplified AI by appending various rules in scenario 111-a ₃ for service. Further, by connecting the workflow editor 210 to the Internet, each user can freely create a scenario 111-a ₄ for the service, it can provide services that each Internet server in accordance with the scenario 111-a _4. Furthermore, an original tool can be created by using the API. In addition, by enabling the screen display unit 240 to be browsed via the Internet, the information stored in the DB unit 130 can be browsed.

<Application Example 4>
FIG. 8 shows a configuration of an application example 4 of the operation system of the present invention. In this configuration, the exchanges 420-1 to J and the Internet servers 600-1 to 600 -M are connected to the server device 100. By creating a scenario 111-a ₅ for the service, you can use the services of Internet server using a telephone. For example, it is possible to save the corresponding information in the DB unit 130 by browsing the map information during a phone call or by speaking a specific word (such as “save”) while browsing the Internet information. Become. In addition, by enabling the screen display unit 240 to be browsed via the Internet, the information stored in the DB unit 130 can be browsed. It is also possible to add a scenario 111-a ₆ for service at any time, can develop a new service real time and low cost.

<Application Example 5>
FIG. 9 shows a configuration of an application example 5 of the operation system of the present invention. In this configuration, the server device 100 includes an engine unit 810 in addition to the engine unit 110, and the other devices 830-1 to 830-1D are connected. By creating scenarios 811-1 to N of sequences adapted to other devices 830-1 to 830-D and recording them in the engine unit 810, a simple ADP can be created by performing sequence and data conversion in the engine unit (however, , N is an integer of 1 or more). Since the scenarios 811-1 to N can also be created using the workflow editor 210, the user can freely connect to the other apparatuses 830-1 to 830-N without programming.

[Program, recording medium]
The various processes described above are not only executed in time series according to the description, but may also be executed in parallel or individually as required by the processing capability of the apparatus that executes the processes. Needless to say, other modifications are possible without departing from the spirit of the present invention.

  Further, when the above-described configuration is realized by a computer, processing contents of functions that each device should have are described by a program. The processing functions are realized on the computer by executing the program on the computer.

  The program describing the processing contents can be recorded on a computer-readable recording medium. As the computer-readable recording medium, for example, any recording medium such as a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory may be used.

  The program is distributed by selling, transferring, or lending a portable recording medium such as a DVD or CD-ROM in which the program is recorded. Furthermore, the program may be distributed by storing the program in a storage device of the server computer and transferring the program from the server computer to another computer via a network.

  A computer that executes such a program first stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. When executing the process, the computer reads a program stored in its own recording medium and executes a process according to the read program. As another execution form of the program, the computer may directly read the program from a portable recording medium and execute processing according to the program, and the program is transferred from the server computer to the computer. Each time, the processing according to the received program may be executed sequentially. Also, the program is not transferred from the server computer to the computer, and the above-described processing is executed by a so-called ASP (Application Service Provider) type service that realizes the processing function only by the execution instruction and result acquisition. It is good. Note that the program in this embodiment includes information that is used for processing by an electronic computer and that conforms to the program (data that is not a direct command to the computer but has a property that defines the processing of the computer).

  In this embodiment, the present apparatus is configured by executing a predetermined program on a computer. However, at least a part of these processing contents may be realized by hardware.

DESCRIPTION OF SYMBOLS 100 Server apparatus 110 Engine part 115 Scenario recording part 120 Screen generation part 125 Screen data recording part 130 DB part 140 ADP part 150 Management part 155 Parts recording part 160 Base part 200 Client apparatus 210 Workflow editor 220 DB editing editor 230 Screen editing editor 240 Screen display

Claims (4)

An operation system composed of a server device and a client device,
The server device
An engine unit that starts a scenario and executes a workflow according to the scenario description;
A screen generator for generating a display screen to be displayed on the client device;
A DB unit for storing a DB handled in the workflow;
An ADP unit for connecting to other systems;
A management unit for managing scenarios and screen data;
A base unit that executes various functions called from the engine unit,
The client device is
A workflow editor for creating and editing the scenario;
A DB editing editor for defining a DB schema and creating the DB;
A screen editing editor for creating the screen data;
A screen display unit for displaying the display screen, the workflow editor, the DB editing editor, and a screen for operating the screen editing editor;
The management unit also manages parts of the scenario, parts of the DB, parts of the screen data,
The workflow editor captures parts of the scenario, creates and edits a scenario by combining the parts of the scenario, and can register to the management unit,
The DB editing editor can take in the DB parts, create and edit the DB by combining the DB parts, and register the DB part.
The screen editing editor can capture the screen data components, create and edit screen data by combining the screen data components, and register the screen data in the management unit. The operation system according to claim 1,
The various functions include a function for notifying the engine unit of information received by the ADP unit, a function for communicating with each component unit, a scenario execution result, a DB content, and a screen data content. An operation system, which is a function of presenting to the client device via the screen generation unit in response to a request from the client device. The operation system according to claim 1 or 2,
The operation system, wherein the scenario component, the DB component, and the screen data component are a set of parameters combined with functions executed by the base unit. A server device connected to the client device,
An engine unit that starts a scenario and executes a workflow according to the scenario description;
A screen generator for generating a display screen to be displayed on the client device;
A DB unit for storing a DB handled in the workflow;
An ADP unit for connecting to other systems;
A management unit for managing scenarios and screen data;
A base unit that executes various functions called from the engine unit,
The management unit
Also manages the scenario parts, the DB parts, and the screen data parts,
Provide parts of the scenario, parts of the DB, parts of the screen data in response to a request from the client device,
A server device that receives the scenario, the DB, and the screen data in response to a request from the client device.

Images