Program presentation with reviewer feedback maintenance

An application with a function for inputting feedback incorporated into it is created and presented with the present embodiment. By this means, feedback about the problems in the running of the application may be obtained efficiently. In addition, an application with a function for inputting feedback about the components that define the operations of the application and a function that maintains a correspondence between the feedback descriptions and the components that are the target of the feedback incorporated into it is created by the present embodiment. By this means, the component in the application that the feedback concerns may easily be determined.

FIELD OF THE INVENTION

The present invention relates to a device, method, and program for developing application programs (hereinafter referred to as simply “applications”), and more specifically to a device, method, and program that makes reviewing of applications possible.

BACKGROUND OF THE INVENTION

Typically, the problems in the operation of applications are noticed by users when attempts are made to run the application. In such cases, the user notifies the developer of the application about the problem. Such operations are normally carried out with the following steps.1. The developer sends the application to the user.2. The user runs the application and describes the problem. At that time, screen captures may be taken to clarify the problem.3. The user sends these to the developer.4. The developer reads the description of the problem. At that time, the screen captures may be referred to for gaining an understanding of the problem.5. The developer opens an application development tool and solves the problem.

However, with the scenario in question, the developer must find the location of the problem in the application based on the description obtained from the user. If there are screen captures, it may help in that investigation. However, when there are no screen captures, there is the fear of the developer not being able to find the correct location where the problem is. Moreover, when a group of people are working on drawing objects, technology already exists such that any user can input comment data for the drawing object (for example, see Published Unexamined Patent Application JP8-16514). In this Patent Reference, comments concerning drawing, text and other objects that are displayed in a screen area that is shared with others through a communications network are stored together with the object, and the object and the comments are used jointly through the communications network.

DESCRIPTION OF THE PREFERRED EMBODIMENT

However, the above cited patent merely discloses the sharing of comment data related to a drawing object among a plurality of users working in collaboration with each other. Namely, no means is disclosed for efficiently communicating information concerning the operation of the application from a user to the developer when one user is the application developer and refers to the screen for defining the operations of the application (an application development tool or environment) and another user is a user of the application and refers to the screen to run the application.

The present invention is for solving technical problems such as those above, and it is an object thereof to be able to efficiently acquire information concerning the operation of an application. Furthermore, another object of the present invention is acquiring the information concerning the operation of an application in such a way that it can be determined which location within the application the acquired information is concerned with.

Based on these objects, an application was developed where, in the development of an application, it is possible to relate the data that is input concerning elements that define the operation of the application to those elements. Namely, the device of the present invention is provided with a display part that displays a plurality of elements that define the operations of an application and a creation part that creates an application program that carries out operations defined by a plurality of elements displayed on this display part and maintains the correspondence between the specific element and the data when data related to a specific element out of the plurality of elements is entered.

Here, the creation part may be such that an application program that outputs the correspondence information as a file is created. In addition, there may also be provided a reading part that reads the correspondence information that the application program maintains, and the display part may further display data that includes the correspondence information read by the reading part. Furthermore, the display part can be constituted so as to display the correspondence relationship between the specific element and the data in response to a predetermined operation. In addition, a user interface object for inputting and outputting information among users is given as an example for a specific element. Alternatively, it may be a transition between two user interface objects for inputting and outputting information among users.

In addition, the present invention may also be perceived as a method for developing application programs. In such cases, the method of the present invention includes a step that displays the plurality of elements defining the operations of the application program, a step that carries out the operations defined by the plurality of elements and creates the application program for maintaining the correspondence information for the specific element and the data when the data for a specific element out of the plurality of elements is entered, a step where the application program reads the correspondence information, and a step that displays the data included in the correspondence information.

On the other hand, the present invention may also be perceived as a program for implementing prescribed functions on a computer. In such cases, a first program of the present invention implements a function that reads design information obtained by designing using a plurality of elements that operate the application program and a function carries out the operations defined by the plurality of elements and creates the application program that maintains the correspondence information for the specific element and the data when data is input for a specific element out of the plurality of elements. In addition, a second program of the present invention is a computer program reviewed by a reviewer. Furthermore, the functions provided for the reviewer so as to input into the computer the data concerning the specific element out of the plurality of elements that define the operations of that computer program and the function for maintaining the correspondence information between the specific element and the data when data is input by the reviewer are implemented. Furthermore, a third program of the present invention implements the function for displaying the plurality of elements that define the operations of the application program, the function for reading the correspondence information for the specific element created by the data concerning the specific element out of the plurality of elements being input and the data, and the function for displaying the data included in the correspondence information.

According to the present invention, it becomes possible to efficiently acquire information concerning the operation of an application.

In the following, the preferred embodiment for carrying out the present invention (hereinafter, referred to as “embodiment”) will be described in detail referring to the appended drawings. First, the computer system used by the present embodiment will be described.FIG. 1is a drawing showing an example of the elements of the computer system in the present embodiment. As is shown in the drawing, the computer system comprises a computer10and a computer20connected via a communications line30.

Here, the computer10is a computer used by the application developer. Furthermore, an application development tool, which is software for developing applications, is installed. For example, a personal computer, a workstation or another computer may be used for this computer10. In addition, the computer20is a computer used by the application reviewer. Here, the reviewer is someone who is a user of the application, reviews the operation of the application, and verifies whether or not that operation satisfies the requirements. For example, a personal computer, a workstation or another computer may also be used for this computer20. Furthermore, the communications line30maybe anything as long as it carries out telecommunications between the computer10and the computer20, and for example, the Internet may be used.

Next, the functions of the computer10and the computer20are provided with in the present embodiment will be described. First, the functions on the computer10used by the developer will be described. This computer10is equipped with a design information storage part11, an application storage part12, and a feedback storage part13. In addition, a design information editing part14and an application creation part15are provided.

Here, the computer10is a computer used by the application developer. Furthermore, an application development tool, which is software for developing applications, is installed. For example, a personal computer, a workstation or another computer may be used for this computer10. In addition, the computer20is a computer used by the application reviewer. Here, the reviewer is someone who is a user of the application, reviews the operation of the application, and verifies whether or not that operation satisfies the requirements. For example, a personal computer, a workstation or another computer may also be used for this computer20. Furthermore, the communications line30may be anything as long as it carries out telecommunications between the computer10and the computer20, and for example, the Internet may be used.

Next, the functions of the computer10and the computer20as provided within the present embodiment will be described. First, the functions on the computer10used by the developer will be described. This computer10is equipped with a design information storage part11, an application storage part12, and a feedback storage part13. In addition, a design information editing part14and an application creation part15are provided.

The design information storage part11stores the design information created by the user's defining the operations of the application. Namely, the design information is information that includes a component for an example of the elements that define the operations of the application. Here there are, for example, user interface (UI) objects and UI transitions for the components that define the operation of the application. A UI object is an object that the user can confirm visually, and is a page or a button, text box, checkbox, table or other UI element displayed on a display. In addition, UI objects may have a hierarchical structure, and this is applicable to tables and cells, which are their subordinate objects. UI transitions are defined as moving and changing to another UI by an operation in a certain UI. However, although this example is of a component related to a UI, the concept is not limited to this. For example, making a component out of a process (for example, database search processing or the like) that is not directly related to the UI that is executed by the operation in a certain UI may also be considered to be using this concept.

Moreover, these functions are executed through cooperation between the software and hardware resources. Specifically, the design information editing part14and the application creation part15are achieved by the CPU of the computer10executing the application development tool by reading from, for example, a magnetic disk device into a main memory. In addition, the design information storage part11, application storage part12, and feedback storage part13may be achieved using, for example, a magnetic disk device. Furthermore, the programs and data stored on the magnetic disk device may also be loaded from a CD or other storage medium or may be downloaded through a network such as the Internet.

Next, the functions on the computer20used by the reviewer will be described. This computer20is equipped with an application storage part22and a feedback storage part23. In addition, it is equipped with a feedback editing part26. The application storage part22stores an application created in the computer10and received through the communications line30. The feedback storage part23stores feedback that has been output by the application. The feedback editing part26inputs the feedback for the application and indicates the saving of the feedback.

Moreover, these functions are executed through cooperation between the software and hardware resources. Specifically, the feedback editing part26is achieved by the CPU of the computer20reading the application that has been created in the computer10from the application storage part22to the main memory and executing it. In addition, the application storage part22and feedback storage part23may be achieved using, for example, a magnetic disk device. Furthermore, the programs and data stored on the magnetic disk device may also be loaded from a CD or other storage medium or may be downloaded through a network such as the Internet.

Next, we describe the flow of work when the developer creates an application, the reviewer reviews that application, and the developer confirms the results of the review on the computer system in question.FIG. 2is a flow chart showing this workflow. Moreover, something UI related such as a UI object or a UI transition is presumed here for the component that defines the operations of the application. In the figure, the workflow for the developer is shown on the left side, and the workflow for the reviewer is shown on the right side. In addition, the operations of the application development tool are shown on the boundary line in the middle of the figure.

First, the developer designs the application flow (Step101). Here, the application flow is the definition of the processing flow for the application. Next, the developer designs a UI object used in the application processing (Step102). In addition, a UI transition is associated with the UI object if necessary (Step103). At this time, the application development tool assigns a unique ID to the UI object and the UI transition (Step111).

Next, the developer creates an application using the application development tool and sends that application to the reviewer (Step104). At this time, the application development tool embeds the ID assigned in step111in the application (Step112). Furthermore, the developer waits for the reviewer to return feedback (Step105).

On the other hand, the reviewer, who has received the application, first runs the application (Step201). In addition, the reviewer may view the UI transition at this time. Furthermore, the reviewer adds feedback about the UI object, UI transition and the like according to the results of the running of the application (Step202). At this time, in addition to the feedback itself, the application also records the position information on the screen of the component that is the object of the feedback as well as its ID (Step211). Moreover, inFIG. 2, not only the component ID, but also the position information is recorded, but this is to communicate the strict position of the target of the feedback which cannot be communicated by the component ID alone. By this means for example, circumstances such as not understanding the meaning of the target location of a character string within a cell even when the cell ID is recorded for a data table may be dealt with. However, an embodiment that does not record the position information when the ID of the component alone is sufficient for identifying the target of the feedback may be used. Finally, the reviewer sends the feedback to the developer (Step203).

By this means, the developer receives the feedback, and the application development tool loads the feedback (Step106). At this time, the application development tool relates the feedback to the position where the reviewer has added the feedback based on the position information and the ID of the component that is the target of the feedback (Step113). Subsequently, the developer reads and analyzes the feedback in the application development tool (Step107). Furthermore, the developer determines whether or not there is a problem (Step108), and if there is a problem, returns to step101, and if not, ends the operation.

In the following, we show examples of the screens displayed following this workflow. First, a description of examples of screens displayed on the computer10when the developer is designing the application will be given referring toFIG. 3-FIG.7.FIG. 3shows an example of the screen when the application flow is designed. In this example, this is called “page flow,” because the application flow is shown by transitions between pages here. This page flow shows that the application is designed to include a login page40, a table display page50, an item addition page60, and an item display page70. In addition, a UI transition81which represents the transition to the table display page50when the login page40is operated and a UI transition82which represents the transition to the item addition page60when the table display page50is operated are shown in the page flow. Furthermore, UI transitions83and84which represent a return to the table display page50when the item edition page60is operated, a UI transition85which represents a transition to the item display page70when the table display page50is operated, and a UI transition86which represents a return to the table display page51and the item display page70is operated are also shown.

FIG. 4shows an example of the screen when the login page40is designed. A label43and a text box44for the system user password are placed along with a label41and a text box42for the system user ID being placed on the login page40. In addition, a link45that is pressed after the ID and password are input is also placed on the login page40.

In the following, we show examples of the screens displayed following this workflow. First, a description of examples of screens displayed on the computer10when the developer is designing the application will be given referring toFIG. 3-FIG.7.FIG. 3shows an example of the screen when the application flow is designed. In this example, this is called “page flow,” because the application flow is shown by transitions between pages here. This page flow shows that the application is designed to include a login page40, a table display page50, an item addition page60, and an item display page70. In addition, a UI transition81which represents the transition to the table display page50when the login page40is operated and a UI transition82which represents the transition to the item addition page60when the table display page50is operated are shown in the page flow. Furthermore, UI transitions83and81which represent a return to the table display page50when the item addition page60is operated, a UI transition85which represents a transition to the item display page70when the table display page50is operated, and a UI transition86which represents a return to the table display page51and the item display page70is operated are also shown.

FIG. 6shows an example of the screen when the item addition page60is designed. A label61and a list box62are placed on the item addition page60for the expense type section, and there are placed a label65and a text box66for the amount along with there being placed a label63and a combo box64for the details. In addition, there are placed an OK button67that is pressed when confirming these inputs and a Cancel button68that is pressed when canceling these inputs.

FIG. 7shows an example of the screen when the item display page70is designed. A display71for the expense type section, details and amount and a button72that is pressed after confirming this display71are placed on the item display page70.

FIG. 6shows an example of the screen when the item addition page60is designed. A label61and a list box62are placed on the item addition page60for the expense type section, and there are placed a label65and a text box66for the amount along with there being placed a label63and a combo box64for the details. In addition, there is placed an OK button67that is pressed when confirming these inputs and a Cancel button68that is pressed when canceling these inputs.

FIG. 8shows the situation when the mouse is clicked on the UI transition82in the page flow. In this case, a menu87, “Add feedback to this action,” is displayed. In this state, if, for example, the menu87is clicked, it goes to the state shown inFIG. 9. In other words, a dialog box88for inputting feedback is displayed. Furthermore, inFIG. 9, the feedback “While performing this action, does this application access our authentication server?” is input in this dialog box88by the reviewer.

FIG. 10shows the situation when the mouse is clicked on the link45on the login page40. In this case, a menu47with “Add feedback to this hyperlink” and “Add feedback to this page” is displayed. In this state, if, for example, the first line on the menu47is clicked, it goes to the state shown inFIG. 11. In other words, a dialog box48for inputting feedback is displayed. Furthermore, inFIG. 11, the feedback “I like a button for the login,” has been input in this dialog box48. Moreover, as has been described above, a state (run mode) where the “Interactive Storyboard” tab is selected and a state (feedback mode) where the “Feedback” tab is selected are provided, and feedback can only be input with the feedback mode. However, an implementation where these two modes are not provided may also be considered to be an embodiment of the present invention. In such a case, the choice “Login,” for example, is provided on the third line of the menu47. Furthermore, if the first line or the second line is selected, it is possible to input feedback, and if the third line is selected, the operation that is supposed to be carried out when the link45is pressed is carried out.

FIG. 12shows the situation when the mouse is clicked on the data table51on the table display page50. In this case, a menu57with “Add feedback to this data table” and “Add feedback to this page” is displayed.

In this state, if, for example, the first line on the menu57is clicked, it goes to the state shown inFIG. 13. In other words, a dialog box58for inputting feedback is displayed. Furthermore, inFIG. 13, the feedback “We need to show the exchange rate in this table as well,” has been input in this dialog box58.

Furthermore, a description of examples of screens displayed on the computer10when the developer is checking the feedback will be given referring toFIG. 14andFIG. 15.FIG. 14shows the state where the feedback consisting of a plurality of feedback descriptions is displayed in the page flow. In this case, two lines of feedback descriptions are displayed in the feedback view area89. Furthermore, by selecting the feedback description on the second line, the UI transition85corresponding to this is highlighted. FIG.15shows the state where feedback is displayed on the login page40. In this case, three lines of feedback descriptions are displayed in the feedback view area49. Furthermore, in contrast toFIG. 14, the third line feedback description corresponding to the link45is highlighted by selecting the link45.

Next, a detailed description will be given of the application development tool that executes these screen transitions and the operation of the application automatically created by this application development tool. Moreover, in the following also, components (UI components) related to UI objects and UI transitions in the UI are presumed as the objects for which feedback is added. In addition, the UI design information is that which indicates the page flow and page design information inFIG. 3-FIG.7.FIG. 16is a flowchart showing the operations of the design information editing part14, which is a subset of the functions in the application development tool used when the developer edits the design information. Moreover, the design information editing part14carries out processing for editing the design information and processing for reading the feedback and bringing it together with the design information. Therefore, the operations related to both will be described together here also.

First, the design information editing part14determines whether or not the reading of the UI design information has been indicated (Step401). Here, if the determination is made that reading of the UI design information is indicated, the UI design information is read and displayed on the screen (Step402). When reading of the UI design information is not indicated, the design information editing part14determines whether or not the reading of feedback has been indicated (Step403). Here, if the determination is made that reading of feedback is indicated, the feedback is read and displayed on the screen (Step404).

When reading of feedback is not indicated, the design information editing part14determines whether or not the reading of changes to the UI design information has been indicated (Step405). For example, there is a determination as to whether a new UI component has been added, the position where a UI component is placed has been changed, the color of a UI component has been changed, a UI component has been deleted or the like. Here, if a determination is made that the reading of changes in the UI design information is indicated, the UI design information is changed, and the screen is updated (Step406). Moreover, when a UI component is added, a unique ID is assigned to that UI component. Furthermore, the correspondence between that UI component and ID are embedded in the UI design information in an understandable format.

When the reading of changes in the UI design information is not indicated, the design information editing part14determines whether or not a UI component has been selected (Step407). Here, if it is determined that a UI component has been selected and if there is a description that has been given correspondence to the same ID as the ID for the selected UI component, that description is highlighted (Step408). Namely, since the correspondence between the UI component and the ID in Step406is embedded in the UI design information, the ID for the selected UI component is first extracted from the UI design information. Furthermore, feedback descriptions that correspond to this ID are identified within the feedback.

When no UI component has been selected, the design information editing part14determines whether or not a feedback description has been selected (Step409). Here, if it is determined that a feedback description has been selected and if there is a UI component having the same ID as the ID that has been given correspondence with the selected description, that UI component is highlighted (Step410). Namely, as will be discussed later, the feedback description is embedded in the feedback so that the correspondence with the ID of the UI component that is the target of the feedback is understood, so the ID that the selected description corresponds to is extracted from the feedback. Furthermore, the UI component given correspondence with this ID is identified within the UI design information.

When no feedback description has been selected, the design information editing part14determines whether or not the writing of the UI design information has been indicated (Step411). Here, if it is determined that the writing of the UI design information has been indicated, the UI design information that is being edited is written to the design information storage part11(Step412). Subsequently, the design information editing part14determines whether or not there has been an end indication (Step413). Here, when there has been no end indication, there is a return to Step410, but when there has been an end indication, the process terminates.

FIG. 17is a flowchart showing the application creation part15, which is a function for automatically creating the application based on the design information that has been edited in this manner, out of the application development tool functions. First, the application creation part15reads the first UI design information (Step501). Then it determines whether or not the UI design information has been read (Step502). Here, when it has been determined that the UI design information has been read, the first UI component included in that UI design information is read (Step503). Then it determines whether or not the UI component has been read (Step504). As a result, when it is determined that the UI component has been read, the UI component of the application corresponding to the UI component in the UI design information is created (Step505). Moreover, the ID assigned in Step406to the UI component in the UI design information is set for the UI component in the application at this time.

Subsequently, the application creation part15reads the next UI component in the UI design information (Step506) and returns to Step504. Then the Steps504-506are processed repeatedly until the UI components in the UI design information are exhausted. Furthermore, when the UI components are exhausted, the next UI design information is read (Step507), and there is a return to Step502. Then the Steps502-507are processed repeatedly until the UI design information is exhausted. Finally, when it is determined that there is no UI design information in Step502, functions related to the application as a whole, such as a page flow display function or a feedback editing function, are created (Step508), and processing is terminated.

FIG. 18is a flow chart showing the operations for a feedback editing process by the application created by the application creation part15. First, the application determines whether or not there has been an indication for a page transition (Step601). Here, when it is determined that there has been an indication for a page transition, the page transition is made (Step602). When there has been no indication for a page transition, the application determines whether or not there has been an indication for addition of feedback (Step603). Here, when there is a determination that there has been an indication for addition of feedback, the application carries out feedback addition processing, which will be discussed later (Step604).

When there has been no indication for the addition of feedback, the application determines whether or not there has been an indication of a change in feedback (Step605). Here, when there is a determination that there has been an indication of the change, the application carries out feedback change processing, which will be discussed later (Step606). When there has been no indication of a change in feedback, the application determines whether or not there has been an indication for saving the feedback (Step607). Here, when there is a determination that there has been an indication for saving the feedback, the application saves the feedback in a file (Step608). Subsequently, the application determines whether or not there has been an end indication (Step609). Here, when there has been no end indication, there is a return to Step601, but when there has been an end indication, the process terminates.

Here, the processing content in Step604and Step606described above will be described in further detail with reference toFIG. 19.FIG. 19(a) is a flowchart showing the detailed operations of the feedback addition process in Step604. When the feedback addition process starts, the application first displays a dialog box (Add Feedback dialog) for adding feedback (Step611). In addition, if the user inputs feedback in to this dialog box, that input is received. Furthermore, whether or not there has been an indication for temporarily saving the feedback that has been input is determined (Step612).

As a result, when it is determined that there has been such a save indication, the application stores the feedback that has been input in memory that it can reference itself (Step613). Moreover, the application determines which UI component the indication of the feedback addition was for in Step603based on the position information on the screen and obtains the ID for that UI component based on the correspondence between the UI component and the ID embedded in the application. Furthermore, in this Step613, the feedback that has been input is related to and maintained with the correspondence with the ID for that UI component. On the other hand, when there is no indication for that saving, the processing ends.

FIG. 19(b) is a flowchart showing the detailed operations of the feedback change process in Step606. When the feedback change process starts, the application first displays a dialog box (Change Feedback dialog) for changing the feedback (Step621). Moreover, the application determines which UI component the indication of the feedback change was for in Step605based on the position information on the screen and obtains the ID for that UI component based on the correspondence between the UI component and the ID embedded in the application. Furthermore, feedback that is related to that UI component and already saved in the memory that it can reference is read and displayed in the Change Feedback dialog. In addition, if the user adds changes to that feedback, those changes are received. Furthermore, whether or not there has been an indication for temporarily saving the feedback after the changes is determined (Step622).

As a result, when it is determined that there has been such a save indication, the application changes the feedback in the memory using the feedback that has been entered (Step623). In addition, when there has been no indication for that saving, the application determines whether or not there has been an indication for deleting the feedback (Step624). As a result, when it is determined that there has been such an indication for deletion the application deletes the feedback in the memory (Step625). On the other hand, when there is no indication for that deletion, the processing ends.

In the present embodiment, the ID for the UI component is embedded in all of the design information created by the design information editing part14, the application created by the application creation part15, and the feedback created by the feedback editing part26. Therefore, specific examples of the methods for embedding the ID for the UI component will be described with reference to examples of source code that correspond to the design information, the application and the feedback, respectively. FIG.20shows examples of source code used in the design and creation of an application. Of these,FIG. 20(a) shows the part corresponding to the link45placed on the login page in the source code forming the basis for the application design screen. The ID assigned to the link45is embedded in the place in this source code that is surrounded by the rectangle. Of these,FIG. 20(b) shows the part corresponding to the link45placed on the login page in the source code of the automatically created application. The ID assigned to the link45is embedded in the place in this source code that is surrounded by the rectangle.

Furthermore,FIG. 21shows the source code of a file where the feedback is output when feedback is added for the link45on this login page40. The ID assigned to the link45is also embedded in the place in this source code that is surrounded by the rectangle. In addition, the feedback description “This needs to be a button” is written two lines below that. In other words, this file may be considered as correspondence information in which the ID for the component that is the target of the feedback is associated with the feedback description.

Finally, the computer hardware configuration preferable for use as computer10and computer20in the present embodiment will be described.FIG. 22is a drawing showing an example of this computer hardware configuration. As is shown in the figure, the computer is equipped with a central processing unit (CPU)10a, which is a computation means, a main memory10cconnected to the CPU10avia a motherboard (M/B) chipset10b, and a display facility10dconnected to the CPU10aby the same M/B chipset10b. In addition, a network interface10f, a magnetic disk drive device (HDD)109, an audio facility10h, a keyboard/mouse10iand a flexible disk drive10jare connected to the M/B chipset via a bridge circuit10e.

Moreover, each of the constituent elements is connected via a bus inFIG. 22. For example, a connection is made between the CPU10aand M/B chipset10band between the M/B chipset10band the main memory10cvia a CPU bus. In addition, a connection may be made between the M/B chipset10band the display facility10dvia an accelerated graphics port (AGP), but when the display facility10dincludes a PCI express compatible video card, the connection between the M/B chipset10band this video card is made via a PCI express (PCIe) bus. In addition, when connected with the bridge circuit10e, the network interface10fmay, for example, use PCI express. In addition, the magnetic disk device10gmay use, for example, serial AT attachment (ATA), parallel ATA or peripheral component interconnect (PCI). Furthermore, the keyboard/mouse10iand the flexible disk drive10jmay use a universal serial bus (USB).

Here, the present invention may be implemented totally through hardware, or may be implemented totally through software. In addition, it may be implemented through both hardware and software. In addition, the present invention may be implemented as a computer, data processing system or computer program. This computer program may be stored on a computer-readable medium. Here, electronic, magnetic, optical, electromagnetic, infrared, semiconductor system (device or machine), or propagation media may be considered for the medium. In addition, semiconductor or solid-state recording devices, magnetic tape, removable computer diskettes, random access memory (RAM), read only memory (ROM), rigid magnetic disks, and optical discs may be cited as examples for the computer-readable medium. At present, the example of optical discs includes compact disc read only memory (CD-ROM), compact disc read/write (CD-R/N) and DVD.