JP5364564B2 - Information processing method and information processing program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processing method and an information processing program that increase the efficiency of system development without correcting nor recompiling existing software components but reusing the software components. <P>SOLUTION: The information processing method includes steps of: a definition information obtaining means in a component as a program for executing predetermined information processing obtaining definition information prescribing specifications of data subject to the predetermined information processing; a data obtaining means in the component obtaining data subject to the predetermined information processing from a predetermined storage area by reference to the definition information obtained by the definition information obtaining means; a processing execution means in the component applying the predetermined information processing to the data obtained by the data obtaining means; and a data storage means in the component storing the data subjected to the predetermined information processing by the processing execution means in the predetermined storage area. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present invention relates to a technique for improving the versatility of software components created in an object-oriented language.

  In general, it is said that software components developed in an object-oriented language are easy to reuse (Patent Document 1, etc.).

  On the other hand, in business related to optical communication services, in which new services are often provided, corrections frequently occur for data items transferred by software components. Accordingly, when editing a software component that has been created in accordance with the correction of the data item, the content encapsulated in the software component is corrected. Therefore, it is necessary to correct and recompile the program, and it becomes difficult to reuse the software component as it is.

JP 2004-287650 A

  In view of the above problems, the present invention provides an information processing method and an information processing program for improving the efficiency of system development by reusing a software component without correcting and recompiling the existing software component. The purpose is to provide.

  In one form of the disclosed information processing method, a definition information acquisition unit included in a component that is a program that executes predetermined information processing acquires definition information that defines a specification of data to be subjected to the predetermined information processing And a step in which a data acquisition unit included in the component refers to the definition information acquired by the definition information acquisition unit and acquires data to be subjected to the predetermined information processing from a predetermined storage area; A processing execution unit included in the information processing unit that performs the predetermined information processing on the data acquired by the data acquisition unit; and a data storage unit included in the component performs the predetermined information processing by the processing execution unit. Storing the data in the predetermined storage area.

  In other words, in one form of the disclosed information processing method, the software configuration is categorized into the framework (hereinafter referred to as FW), the FW component, and the data area, and the interface of the FW component is determined as one. By doing so, a business system can be efficiently constructed by combining FW components. Also, with regard to the mounting of the FW component, the external parameter file is read and the definition information related to the data specification is automatically acquired, so that correction and recompilation of the program becomes unnecessary.

  The disclosed information processing method can improve the efficiency of system development by reusing software components without modifying and recompiling existing software components.

It is a figure which shows the basic structure of the framework employ | adopted with the information processing method by the information processing apparatus which concerns on this Embodiment. It is a figure which shows an example of the framework structure implement | achieved by the servlet which concerns on this Embodiment. It is a figure explaining the characteristic of the information processing method performed in the information processing apparatus which concerns on this Embodiment. It is a figure which shows the outline | summary of the flow of the information processing using the framework which concerns on this Embodiment. It is a source image figure of an action component. It is a figure which shows the work flow at the time of applying the information processing method performed in the information processing apparatus which concerns on this Embodiment to a library system, and a screen layout. It is a sequence diagram regarding the processing flow of a request (control processing) according to the present embodiment. It is a sequence diagram regarding a processing flow of a request (business process) according to the present embodiment. It is a sequence diagram regarding the processing flow of the business processing (control processing) according to the present embodiment. It is a sequence diagram regarding a processing flow of business processing (business processing) according to the present embodiment. It is a sequence diagram regarding the processing flow of the response (control processing) concerning this embodiment. It is a sequence diagram regarding the processing flow of a response (business process) according to the present embodiment. It is a sequence diagram regarding the processing flow (part 2) of the response (business process) according to the present embodiment. It is a figure which shows an example of the hardware constitutions of the information processing apparatus which concerns on this Embodiment.

  The best mode for carrying out the present invention will be described with reference to the drawings. First, an outline of an information processing method executed in the information processing apparatus 100 according to the present embodiment will be described with reference to FIGS. 1 and 2. FIG. 1 is a diagram illustrating a basic structure of a framework 1 employed in an information processing method by the information processing apparatus 100, and FIG. 2 is a diagram illustrating an example of a framework structure realized by a servlet.

  As shown in FIGS. 1 and 2, the framework 1 includes a common component 10, a framework (hereinafter referred to as FW) 20, a FW component 30, and a data area 40. The common component 10 is a common component that has been conventionally used. The processing control FW 21 included in the FW 20 has registration information related to the action controller 31 described later, and calls the registered action controller 31. The processing control FW holds information on the action controller 31 to be called, information on the action controller calling order, and the like.

  The FW component 30 includes an action controller 31, an action component 32, a component 33, and the like. The action controller 31 determines the requested screen and action, and calls the corresponding action component 32. Further, the action controller 31 holds information regarding the action component 32 to be called for each screen-action and information regarding the calling order of the action component 32.

  The action component 32 is a component that collectively manages processes for each requested screen and action. The action component 32 is a unit of function and is composed of a combination of a plurality of components 33, and manages processing performed for each screen and action. The action component 32 holds information about the component 33 to be called and information about the calling order of the components 33.

  The component 33 is a component that performs individual information processing. Moreover, the component 33 is good also as a form which notifies that to the action controller 31 or the action component 32, when each information processing is complete | finished. Thus, the action controller 31 or the action component 32 can connect the components 33 in a predetermined order. Here, the FW component 30 may be a simple interface of one class and one method.

  The data area 40 includes an application scope 41, a session scope 42, a thread scope 43, and the like, and is an area that can be referenced and updated from the common component 10, the FW 20, and the FW component 30. Here, since the data area 40 is a data area that can be referred to and updated from all components, the force of object-oriented data encapsulation is weakened. However, a scope for each application is prepared, and by using a character string class, an unintended area destruction due to a buffer overflow or the like possessed by the C language or the COBOL language does not occur.

  The application scope 41 holds static information such as contents read from the external parameter file. The session scope 42 holds information for each user to be used, such as information held even when the screen is changed, and corresponds to the session scope of the servlet. The thread scope 43 is information that changes at each screen transition, and is an area that is used for each screen request. The thread scope 43 corresponds to a servlet request scope.

  In the framework 1, the FW component 30 to be called by the FW 20 is acquired from the external parameter, and the control part is separated and externally defined. The framework 1 develops a plurality of FW components 30 and constructs a business by combining them. In the framework 1, the FW component 30 does not hold the data, and the data area 40 manages the data in a unified manner. Furthermore, in the framework 1, the versatility of the FW component 30 is improved by preparing the FW 20 for each architecture.

  Here, the characteristics of the information processing method executed in the information processing apparatus 100 according to the present embodiment will be described with reference to FIG. FIG. 3 is a diagram for explaining the characteristics of the information processing method executed in the information processing apparatus 100.

  As shown in FIG. 3, in the information processing method executed in the information processing apparatus 100, definitions, data, and programs are considered separately and assigned at the time of execution to execute processing. By doing so, when the requirement of the system is changed, the definition (definition information) and the data are changed together, so that the change of the program (component 33) becomes unnecessary and the change requirement becomes strong. In other words, when the requirements are changed, the definition and data can be exchanged, and the program can be exchanged without causing the system to be stopped. For example, when the data specification changes, the definition and data are changed, so that the component 33 can be dealt with without changing. When new data is added, the definition and data are newly prepared. Thus, the component 33 can be reused without modification.

  Note that the common component 10 is a common component that has been conventionally used as described above, and is a software component that always performs a certain process. Is not to be done. Therefore, when the system requirements are changed, the definition and data are not affected at all.

  Next, the outline of the flow of information processing using the framework 1 will be described with reference to FIG. FIG. 4 is a diagram showing an outline of the flow of processing when the framework is formed. In S1, the update button of “screen 01” is pressed, and the servlet container is called. In S2, the servlet container calls the process control FW21. In S3, the process control FW 21 calls the request action controller. In S4, based on the information of “screen 01” and “update”, the request action controller calls the corresponding request action component (screen 01. update. Request action component).

  In S5, components registered in the request action component (screen 01. update. Request action component) are sequentially called. Here, the request processor and the request validator are called and terminated. In S6, the process control FW 21 calls the business process action controller. If an error has occurred during the request action, the call is stopped and the process is transferred to the response action controller error.

  In S7, based on the information of “screen 01” and “update” and status information (“normal” or “validation error”), the business process action controller applies the corresponding business process action component (screen 01. update. Business process action component). Call. In S8, components registered in the business process action component (screen 01. update. Business process action component) are sequentially called. Here, the update process is called and ends.

  In S9, the process control FW 21 calls the response action controller. In S10, the response action controller calls the corresponding response action component (screen 01. display. Response action component) based on the information of “screen 1” and “update” and the status information (“normal” or “validation error”). In S11, the components registered in the response action component (screen 01. display. Response action component) are sequentially called. Here, the basic editing, normal processing, and response processor are called, and the process ends. In S12, the result of the screen display when the update of the screen 01 is normal is displayed on the screen by the function of the response processor.

  FIG. 5 is a source image diagram of the action component. In accordance with the source of the action component shown in the figure, the action component first reads all the action component information from the first line. In the example of FIG. 5, the names of the component 1 and the component 2 are read and acquired. Then, the action component generates an object of component 1, performs an instantiation process, and calls the go method of component 1, whereby the process 1 of component 1 operates. Next, the action component generates and instantiates the object of component 2, and the component 2 process 2 operates by calling the go method of component 2. As a result of the above processing, the operation is performed in the order of processing 1 of component 1 and then processing 2 of component 2.

  Here, if it is desired to change the processing order, the action component information can be defined in the order of component 2 and component 1, for example. In this case, since the action component reads and acquires the names in the order of component 2 and component 1, the action components perform their operations in the order of processing 2 of component 2 and then processing 1 of component 1.

  Therefore, for example, in the case of S5 in FIG. 4 described above, components registered in the request action component (screen 01. update. Request action component) are sequentially called. Here, in the action component information, the request processor, The component names are read and obtained in the order of request validator.

  Next, an example in which the information processing method executed in the information processing apparatus 100 is applied to the business flow of the library system will be described with reference to FIGS. FIG. 6 shows the business flow and screen layout of the library system used for the description here.

  First, a processing flow of a request (control process) will be described with reference to FIG. When the user presses the “search button” on the lending search screen in S101, the servlet container is called. In S102, the Java (registered trademark) servlet calls the processing control FW21. In S103, the process control FW 21 calls the request action controller. In S104, the request action controller acquires action controller information from the parameter file. In S <b> 105, the action controller refers to the action controller information from the “search screen press” information of the “lending search screen”, allocates and calls the “search request action component”. In S106, the search request action component acquires action component information from the action component information in the parameter file. Then, the components registered in the action component information are sequentially called by the search request action component. In S108, the search request action component calls the request processor.

  Next, a processing flow of a request (business process) will be described with reference to FIG. In S109, the search request action component calls “request processor”. In S110, the request processor component acquires editing information from the request processor information on the “search screen”. In S111, the request processor component acquires a screen item. In S112, the request processor component edits the acquired screen item by character string editing. In S113, the request processor component stores the character string edited information in the screen entity item. Through the above series of processing, the screen item of the lending search screen is transferred to the screen entity.

  Next, a processing flow of business processing (control processing) will be described with reference to FIG. In S114, the process control FW 21 calls the business action controller. In S115, the business action controller acquires action controller information from the parameter file. In S116, the business action controller refers to the action controller information based on the “search button pressed” information on the “lending screen” and the status information (normal), and assigns and calls the “search processing action component”. In S117, the search processing action component acquires action component information from the parameter file. Then, the search processing action component sequentially calls the components registered in the action component information. In S118, the search processing action component calls basic editing (search screen-screen entity → business entity). In S119, the search processing action component calls “rental information search”.

  Next, a processing flow of business processing (business processing) will be described with reference to FIG. In S120, the search processing action component calls basic editing (search screen—screen entity → business entity). In S121, the basic editing component acquires editing information from the basic editing information on the “search screen”. In S122, the basic editing component acquires information from the screen entity item. In S123, the basic editing component edits the acquired information by simple transfer. In S124, the basic editing component stores the edited data in the business entity item. In S125, the search processing action component calls “rental information search”. In S126, the lending information search component acquires information from the business entity. In S127, the lending information search component acquires the book name from the DB using the book ID of the acquired information as a key. In S128, the lending information search component acquires book lending information from the DB using the book ID of the acquired information as a key. In S129, the lending information search component stores the acquired book name and book lending information in the business entity. Through the above series of processing, data is transferred from the screen entity to the business entity, and the DB search result is written to the business entity.

  Next, a response (control process) process flow will be described with reference to FIG. In S130, the process control FW 21 calls the response action controller. In S131, the response action controller acquires action controller information from the parameter file. In S132, the response action controller refers to the action controller information based on the “search button pressed” information on the “lending search screen” and the status information (normal), and allocates and calls the “lending registration screen display action component”. In S133, the lending registration screen display action component acquires action component information from the parameter file. Then, the lending registration screen display action component sequentially calls the components registered in the action component information. In S134, the lending registration screen display action component calls basic editing (lending screen-business entity → screen entity). In S135, the lending registration screen display action component calls the response processor. In S136 and 137, the Java (registered trademark) servlet ends the processing.

  Next, a response (business process) process flow will be described with reference to FIG. In S138, the lending registration screen display action component calls basic editing (lending screen-business entity → screen entity). In S139, the basic editing component acquires editing information from the basic editing information on the “lending screen”. In S140, the basic editing component acquires information from the business entity item. In S141, the basic editing component edits the acquired information by simple transfer. In S142, the basic editing component stores the edited data in the screen entity item. By the series of processes described above, data transfer from the business entity to the screen entity is realized.

  Next, the continuation of the response (business process) process flow will be described with reference to FIG. In S143, the lending registration screen display action component calls the response processor. In S144, the response processor component acquires the editing information from the response processor information on the “lending registration screen”. In S145, the response processor component reads the screen template. In S146, the response processor component acquires information from the screen entity item. In S147, the response processor component edits the acquired information by character string editing. In S148, the response processor component edits the character string edited data by fixed character string editing. In S149, the response processor component stores the fixed character string processing edited data in the screen item. In S150, the response processor component displays a screen, and in S151, the Java (registered trademark) servlet ends the process. Through the series of processes described above, a screen template can be prepared as a base for a lending registration screen, and a screen entity can be transferred to a screen item.

(Example of hardware configuration of information processing apparatus according to this embodiment)
An example of a hardware configuration of information processing apparatus 100 according to the present embodiment will be described with reference to FIG. FIG. 14 is a diagram illustrating an example of a hardware configuration of the information processing apparatus 100. The information processing apparatus 100 includes a CPU (Central Processing Unit) 210, a ROM (Read-Only Memory) 220, a RAM (Random Access Memory) 230, an HDD (Hard Disc Drive) 240, a display device 250, a recording medium I / F 260, and the like. Have.

  The CPU 210 is a device that executes a program stored in the ROM 220, performs arithmetic processing on data expanded (loaded) in the RAM 230 in accordance with a program instruction, and controls the entire information processing apparatus 100. The ROM 220 stores programs executed by the CPU 210 and data. When the CPU 210 executes a program stored in the ROM 220 by the CPU 210, the program or data to be executed is expanded (loaded), and temporarily holds the operation data during the operation.

  The HDD 240 is a device that stores an OS (Operating System) that is basic software, an application program according to the present embodiment, a plug-in for function expansion, and the like together with related data.

  The display device 250 includes a key switch using hard keys, an LCD (Liquid Crystal Display), and the like, and functions as a user interface for performing various settings when the user uses the functions of the information processing apparatus 100. is there. A recording medium I / F (InterFace) 260 is an interface for reading data recorded on a recording medium 290 such as a CD (Compact Disc), a DVD (Digital Versatile Disc), and an SD memory card.

  Each unit of the information processing apparatus 100 may be realized by the CPU 210 executing a program corresponding to each unit stored in the ROM 220 or the HDD 240, and the processing related to each unit is realized by hardware. It is good also as a form. Further, the program recorded in the recording medium 270 may be read via the recording medium I / F 260, and each unit of the information processing apparatus 100 may be realized by the read program.

  Although the embodiment of the present invention has been described in detail above, the present invention is not limited to the specific embodiment, and various modifications are possible within the scope of the gist of the present invention described in the claims.・ Change is possible.

DESCRIPTION OF SYMBOLS 10 Common component 20 Framework 21 Processing control framework 30 Framework component 31 Action controller 32 Action component 33 Component 40 Data area 41 Application scope 42 Session scope 43 Thread scope 100 Information processing apparatus 210 CPU
220 ROM
230 RAM
240 HDD
250 Display device 260 Recording medium I / F
270 recording medium

Claims (4)

In an information processing apparatus having software parts of an action controller that manages execution of business processing, an action component provided for each business processing, and a component provided for each information processing constituting the business processing An information processing method,
Action controller
Receiving an action from a predetermined screen;
Obtaining action controller information in which an action component for executing a business process identified from the screen and the action is registered;
Calling an action component registered in the acquired action controller information;
The action component called by the action controller
Obtaining action component information in which a plurality of components for executing a business process specified from the screen and the action and an order of calling components for executing the business process are registered;
Sequentially calling components registered in the acquired action component information according to the order;
The component called by the action component
Obtaining data to be processed by the business process from a predetermined storage area;
To said data obtained were collected, and executing processing relating to the business process,
And storing the data in executing the processing, the predetermined storage area,
Including
further,
When the specification of data in the predetermined storage area is changed, at least the action component information in which the component that executes the information processing on the data and the order of calling the component are registered;
When new data is added to the predetermined storage area, at least adding action component information in which the component that executes the information processing on the new data and the order of calling the component are registered; ,
An information processing method including: The components, when stored prior Symbol data is completed, and notifies to the effect that storing of the data is completed with respect to the action component,
The action component, before SL when there is notification, information processing method according to claim 1, characterized in that invoking the following components of order of the component performing the notification. In the information processing device ,
Accept actions from a given screen,
Acquire action controller information in which an action component for executing a business process specified from the screen and the action is registered;
Function as an action controller that calls the action component registered in the acquired action controller information,
Obtaining action component information in which a plurality of components for executing a business process specified from the screen and the action and an order of calling the components for executing the business process are registered;
The components registered in the acquired action component information are caused to function as action components called by the action controller that sequentially calls according to the order,
Acquiring data to be processed by the business process from a predetermined storage area;
For the acquired data, execute information processing related to the business process,
Causing the data that has been subjected to the information processing to function as a component called by an action component that is stored in the predetermined storage area;
further,
When the specification of data in the predetermined storage area is changed, at least the component that executes the information processing on the data and the action component information in which the order of calling the component is registered are changed,
When new data is added to the predetermined storage area, at least a component for executing the information processing on the new data and an action component information in which the order of calling the components is registered is added . Information processing program. The components, when stored prior Symbol data is completed, and notifies to the effect that storing of the data is completed with respect to the action component,
The action component, if there is pre-Symbol notification, call the next component in the order of the component performing the notification, the information processing program according to claim 3.

Images