JP2005258982A - Work management system, program, and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently manage a series of work carried out by a user on a distributed system. <P>SOLUTION: This work management system 2 is provided with a means 4 managing user information 10 associating a user ID with a work ID, a means 5 managing work context information 11 associating the work ID to a task ID, a means 6 managing task information 12 associating the task ID with a step ID, a means 7 managing step information 13 associating the step ID with step status information, and a means restarting a step showing interruption status by the step status information based on the the user information 10, the work context information 11, the task information 12, and the step information 113 when the restart instruction and the user ID are inputted. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a work management system, program, and method for managing user work in a ubiquitous environment.

  Examples of techniques for managing the history of work performed by a user using a computer include access log management, bookmarks, online bookmarks, workflow management, and database distributed transaction management.

  Access log management is a technique for holding a history when a user accesses the system. In the access log management, the user's interaction with the system and various events generated according to the interaction are recorded and can be referred to later. Access logs can be classified and recorded according to type.

  The bookmark is a function of the Web browser. When using a bookmark, a WWW (World Wide Web) URL (Uniform Resource Locators) designated by the user is held in the Web browser. The user can easily access using the held URL.

  The online bookmark is a technique for storing the URL held in the Web browser using the storage on the network in the bookmark technique (see, for example, Patent Document 1). If the URL on the storage can be referred to by using this online bookmark, the bookmark function can be basically used from a different Web browser.

  Workflow management is a technique for facilitating the execution, sharing, and cooperation of tasks when performing a task via a network.

  When workflow management is used, the relationship between each work becomes clear, and the flow of documents and data to be transferred is managed.

In the distributed transaction management of a database, the contents of a database at multiple points in time (checkpoints) are held as snapshots, and changes to the database are held as transaction logs. Thereafter, when any failure occurs in the database, the failure recovery of the database is performed by rollback or rollforward processing using the held snapshot and transaction log.
JP 2003-91457 A

  In the access log management, the user's work can be recorded. However, in the access management, recording of data related to user access is the main operation, and it is difficult to perform higher-level processing beyond that.

  In bookmarks, the Web browser basically holds the URL specified by the user, so when accessing from another Web browser, the saved URL needs to be set for the other Web browser. Further, in the bookmark, session management of the Web browser is basically not performed. Therefore, even if a bookmark is used, it is difficult to manage work that requires session management, such as interruption / resumption of work.

  Also, online bookmarks, like the bookmarks, basically do not perform session management, so it is difficult to manage work that requires session management.

  In workflow management, basically, a series of operations need to be statically analyzed and determined in advance. Therefore, it is not assumed that management is dynamically performed for work arbitrarily executed by the user on the distributed system. Therefore, in workflow management, it is difficult to manage, for example, Web surf.

  Distributed transaction management basically manages transactions specialized for the task of storing data in records, and is not expected to be used for other tasks. Therefore, even when distributed transaction management is used, it is difficult to dynamically manage the work arbitrarily executed by the user on the distributed system, for example, it is difficult to manage Web surf etc. .

  The present invention has been made in view of the above circumstances, and an object thereof is to provide a work management system, a program, and a method for efficiently managing a series of work performed by a user on a distributed system.

  Specific means taken for realizing the present invention will be described below.

  In the embodiment of the present invention, the first management means manages user information in which user identification data for identifying a user is associated with work identification data for identifying a work by the user. The second management means manages work context information that associates work identification data with task identification data for identifying a task that represents a flow of steps in the work. The third management unit manages task information in which task identification data is associated with step identification data indicating a step started by a user in the task. The fourth management means manages step information that associates step identification data with step state information that indicates whether or not the step indicated by the step identification data is in an interrupted state. When the restart instruction and the user identification data are input, the restarting unit restarts the step whose step state information indicates the suspended state based on the user information, the work context information, the task information, and the step information.

  According to the present invention, a series of operations performed by a user on a distributed system can be efficiently managed.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following embodiments, the same parts are denoted by the same reference numerals and the description thereof is omitted.

(First embodiment)
In this embodiment, a work management system that allows a series of work to be continued even when the user uses different terminals before and after the work is interrupted will be described.

  FIG. 1 is a block diagram showing an example of a work management system according to the present embodiment.

  The user 1 can freely access and work with the service providers SP1 to SPm using a plurality of different terminals TM1 to TMn.

  The work management system 2 relays between the terminals TM1 to TMn and the service providers SP1 to SPm, and manages a series of work by the user 1.

  The work management system 2 executes a program 3 a recorded on the recording medium 3. The work management system 2 operates in accordance with the program 3a, thereby realizing functions as the first management unit 4, the second management unit 5, the third management unit 6, the fourth management unit 7, and the resuming unit 8.

  In FIG. 1, the storage unit 9 is externally attached to the work management system 2. However, the storage unit 9 may be built in the work management system 2. A database may be used as the storage unit 9.

  User information 10, work context information 11, task information 12, and step information 13 stored in the storage unit 9 represent various attributes relating to the user, work, task, and step, respectively.

  The terminals TM1 to TMn, the work management system 2, the service providers SP1 to SPm, and the storage unit 9 may be connected via a network such as the Internet, for example.

  First, it is assumed that the user 1 uses the terminal TM1 to input user identification data (user ID) and access one of the service providers SP1 to SPm to perform work.

  Then, the first management unit 4 sends the user information 10 that associates the user identification data for identifying the user 1 and the work identification data for identifying the work performed by the user 1 to the storage unit 10. Remember.

  The second management unit 5 stores, in the storage unit 10, work context information 11 that associates work identification data with task identification data for identifying a task that represents a flow of steps of the same category in the work.

  The third management unit 6 stores, in the storage unit 10, task information 12 that associates task identification data with step identification data that indicates a step that has been started by the user 1 in this task.

  The fourth management unit 6 stores in the storage unit 10 step information 13 that associates step identification data with step state information that indicates whether or not the step indicated by the step identification data is in an interrupted state.

  Here, it is assumed that a task branch event such as clicking a hyperlink on the Web browser occurs in the work of the user 1.

  Then, the second management unit 11 stores the work identification data in association with the task identification data indicating the task after branching in the work context information 11.

  The 3rd management part 12 and the 4th management part 13 manage the task information and step information similar to the above also about the task after a branch.

  Next, it is assumed that the user 1 inputs a work resumption command and user identification data using the terminal TMn.

  Then, based on the user information 10, work context information 11, task information 12, and step information 13 in the storage unit 9, the resuming unit 8 resumes the step whose step state information indicates the suspended state, and displays the resuming result as a terminal. Output to TMn.

  Further, after the work is resumed, the resuming unit 8 can retroactively execute only the steps instructed by the user 1 and resume only a part of the work.

  The user 1 can then take over the work of the terminal TM1 using the terminal TMn and proceed with the work.

  The work management system 1 according to the present embodiment will be described below with a specific example.

  FIG. 2 is a diagram illustrating an example of the relationship between the user 1, work context (working state), task, and step.

  Each work context is a series (a group) of work units performed by the user 1.

  A task is a unit of work flow executed in a work context. Note that a plurality of tasks may be executed in parallel within the work context. The task may branch and a new task may be started.

  The step is a work execution unit of the user 1 at a certain point in time of the task. A task transition occurs when a new step is executed.

  FIG. 3 is a class diagram showing an example of the relationship between the user 1, work context, task, and step.

  In the logical configuration of FIG. 3, the user 1 has zero or more work contexts. A work context has zero or more tasks. A task has zero or more steps. The task has 0 or 1 parent task (task that is a branch source). The task has zero or more child tasks (tasks to be branched to). A step has zero or one previous step. A step has zero or one next step.

  FIG. 4 is a data structure diagram showing an example of user information 10, work context information 11, task information 12, and step information 13.

  User information 10, work context information 11, task information 12, and step information 13 are created for each user 1, work context, task, and step in FIG.

  In each user information 10, work context information 11, task information 12, and step information 13, item names and values are associated with each other.

  The user information 10 includes a user ID (user identification data), a login state, and a work context ID (work identification data).

  In the example of FIG. 4, the user information 10 is that the user ID of the user 1 is “taro”, the user 1 is in the logged-in state, and the user 1 is the work indicated by the work context IDs “C1” and “C2”. Indicates that the context has started.

  The work context information 11 includes a work context ID, a work context name, a state, a task ID (task identification data), and a user ID.

  In the example of FIG. 4, the work context information 11 is the work context with the work context ID “C1”, the work context name is “travel plan”, the state is “ACTIVE”, and the task IDs “T1” and “T2”. "T3" task has been started, indicating that the task is to be executed by the user "Taro".

  The work context information 11 is similarly created for the work context with the work context ID “C2”.

  The task information 12 includes a task ID, a task name, a state, a step ID (step identification data), a parent task ID, a child task ID, and a work context ID.

  In the example of FIG. 4, the task information 12 includes a task ID “T1”, a task name “transfer”, a state “ACTIVE”, and step IDs “S1”, “S2”, “S3”, “ This indicates that the step “S4” has started and belongs to the work with the work context ID “C1”.

  Further, the task information 12 has a parent task ID representing a task (parent task) as a branch source and a child task ID representing a task (child task) as a branch destination for the task with the task ID “T1”.

  Note that the task information 12 is similarly created for the tasks with the task IDs “T2” and “T3”.

  The step information 13 includes a step ID, a step name, a state, a previous step ID, a next step ID, and a task ID.

  In the example of FIG. 4, the step information 13 is a step belonging to the task ID “T1” with the step name “transfer guidance”, the state “ACTIVE”, and the step ID “S1”. Represents.

  The step information 13 has a previous step ID representing the previous step and a next step ID representing the next step for the step with the step ID “S1”.

  Note that step information 13 is similarly created for the steps with the step IDs “S2” to “S4”.

  The user information 10 and the work context information 11 represent the relationship between the user 1 and the work context. The work context information 11 and the task information 12 represent the relationship between the work context and the task. The step information 13 represents the relationship between tasks and steps.

  Various IDs are associated between the user 1 and the work context, between the work context and the task, and between the task and the step.

  In the present embodiment, the tree structure can be searched in the order of user information 10, work context information 11, task information 12, and step information 13, and the tree structure can also be searched in the reverse order. However, it may be possible to search only in the order of the user information 10, the work context information 11, and the task information 12.

  Hereinafter, the case where the user 1 performs the work shown in FIG. 5 will be described as an example of the work context, task, and step generation state associated with the work of the user 1.

  FIG. 6 is a diagram illustrating an example of a data structure immediately after the user 1 logs into the work management system 2 (at the time of Start in FIG. 5).

  In order to manage the work context, a user master table 14, a work context master table 15, a task master table 16, and a step master table 17 are prepared.

  User information 10, work context information 11, task information 12, and step information 13 are stored in the user master table 14, work context master table 15, task master table 16, and step master table 17, respectively.

  Immediately after login, the user ID and login status are stored in the user master table 14. Information on other users may be stored in the user master table 14, but is omitted here.

  Note that FIG. 6 exemplifies a state immediately after the user 1 logs in for the first time, so no data is stored in the work context master table 15, the task master table 16, and the step master table 17. At the time of login after the work is interrupted and logged out, the work context information 11, the task information 12, and the step information 13 before the logout are stored in the tables 15-17.

  As shown in FIG. 7, when the user 1 starts a new work (St1), an empty work context C1 is generated.

  FIG. 8 is a diagram illustrating an example of a data structure at the start of new work. Information related to the work context C1 is stored at the start of the work. In FIG. 8, the newly changed portion is indicated by a thick frame. The same applies to the following drawings.

  In the same row as the user ID “Taro” in the user master table 14, the work context ID “C1” of the started work C1 is stored.

  Further, a work context ID “C1”, a work context name “travel plan”, a status “ACTIVE”, and a user ID “Taro” are stored in a certain row of the work context master table 15.

  Next, as shown in FIG. 9, when the user 1 starts the task T1 (St2), the task T1 and the first step S1 of the task T1 are generated under the management of the work context C1. In this embodiment, a task is indicated by a broken line, and a step is indicated by a solid circle.

  FIG. 10 is a diagram illustrating an example of a data structure at the start of the task T1. By starting the task T1, information on the task T1 and step S1 is stored.

  The task ID “T1” is stored in the same row as the work context ID “C1” in the work context master table 15.

  In addition, a task ID “T1”, a task name “task 1”, a state “ACTIVE (start)”, a step ID “S1”, and a work context ID “C1” are stored in a certain row of the task master table 16.

  Further, in a row of the step master table 17, a step ID “S1”, a step name “step 1”, a state “ACTIVE”, a task ID “T1”, and information are stored. The information associated with the step ID in the step master table 17 includes, for example, data used to reproduce this step, URL, value input by the user 1, settings, and the like.

  Next, as shown in FIG. 11, when the user 1 proceeds with a step in a task T1 (St3), a step S2 subsequent to the step S1 is generated.

  FIG. 12 is a diagram illustrating an example of a data structure when the task T1 progresses. As the task T1 progresses, information about step S2 is stored, and the relationship of “previous step” and “next step” is made between step S1 and step S2.

  The step ID “S2” indicating the newly started step S2 is added to the same row as the task ID “T1” in the task master table 16.

  Further, the state of the same row as the step ID “S1” in the step master table 17 is changed to “CLOSED (end)”, and the next step ID “S2” is stored.

  Further, a step ID “S2”, a step name “step 2”, a state “ACTIVE”, a previous step ID “S1”, a task ID “T1”, and information are stored in a row of the step master table 17.

  In this embodiment, only the final step in the task is set to the state “ACTIVE”, and the other steps are set to the state “CLOSED” when the next step occurs. However, other state management may be performed.

  Next, as shown in FIG. 13, when the user 1 starts another task T2 in step S2 of a task T1 (St4), a task branch occurs, and a new task T2 and a new step of the new task T2 are generated. S3 is generated.

  FIG. 14 is a diagram illustrating an example of a data structure at the start of a new task T2. With the start of the new task T2, information regarding the task T2 and step S3 is stored, and the parent task and the child task are related between the task T1 and the task T2.

  The task ID “T2” of the newly started task T2 is added to the same row as the work context ID “C1” in the work context master table 15.

  Further, a child task ID “T2” indicating the child task T2 of the task T1 is added to the same row as the task ID “T1” in the task master table 16.

  Also, a task ID table “T2”, a task name “task 2”, a status “ACTIVE”, a step ID “S3”, a parent task ID “T1”, and a work context ID “C1” are stored in a row of the task master table 16. Is done.

  Further, in a row of the step master table 17, the step ID “S3”, the step name “step 3”, the state “ACTIVE”, the task ID “T2”, and information are stored.

  For example, the task branch may be detected according to an instruction from the user 1 or may be automatically determined by the program.

  Next, as shown in FIG. 15, when the user 1 advances the step of the new task T2 (St5), a step S4 subsequent to the step S3 is generated.

  FIG. 16 is a diagram illustrating an example of a data structure when the new task T2 progresses. As the new task T2 progresses, information about step S4 is stored, the state of step S3 is changed to “CLOSED”, and the relationship of “previous step” and “next step” is made between step S3 and step S4. The

  The step ID “S4” indicating the newly started step S3 is added to the same row as the task ID “T2” in the task master table 16.

  In the same row as the step ID “S3” in the step master table 17, the state is changed to “CLOSED” and the next step ID “S4” is stored.

  Further, a step ID “S4”, a step name “Step 4”, a state “ACTIVE”, a previous step ID “S3”, a task ID “T2”, and information are stored in a certain row of the step master table 17.

  Next, as shown in FIG. 17, when the user 1 advances the work of the original task T1 (St6), step S5 subsequent to step S2 is generated.

  FIG. 18 is a diagram illustrating an example of a data structure when the original task T1 progresses. As the task T1 progresses, information about step S5 is stored, and the relationship of “previous step” and “next step” is made between step S2 and step S5.

  The step ID “S5” indicating the newly started step S5 is added to the same row as the task ID “T1” in the task master table 16.

  In the same row as the step ID “S2” in the step master table 17, the state is changed to “CLOSED” and the next step ID “S5” is stored.

  Further, a step ID “S5”, a step name “Step 5”, a state “ACTIVE”, a previous step ID “S2”, a task ID “T1”, and information are stored in a row of the step master table 17.

  Then, as shown in FIG. 19, the user 1 finishes the new task T2 after the branch (St7).

  FIG. 20 is a diagram illustrating an example of a data structure at the end of the new task T2.

  The state of the same row as the task ID “T2” in the task master table 16 is changed to “CLOSED”.

  Further, the state of the same row as the step ID “S4” in the step master table 17 is changed to “CLOSED”.

  The end of the task may be in accordance with, for example, an instruction from the user 1 or may be automatically determined by the program.

  As described above, the work status is managed in a form like a tree structure in the work context C1. A tree-structured leaf in the work context C1 at a certain point in time, that is, a group of steps at the end of the task, represents the latest state of the group of tasks that have not been completed.

  Here, it is assumed that the user 1 interrupts the operation in the state of FIG. 17 and FIG. 18 (St6). Then, step S5 at the end of task T1 and step S4 at the end of task T2 are suspended.

  The tree structure of the work context C1 can be handled as a work history. Steps S1, S2, and S3 that are not leaves represent a previous state in the work by the user 1.

  FIG. 21 is a diagram showing an example of a data structure at the time when the user 1 interrupts the work in the state (St6) of FIGS. 17 and 18 described above.

  Due to the interruption of the work, the state of the work context C1 being executed is changed to “SUSPENDED”, and among the tasks belonging to the work context C1, the tasks T1 and T2 which are “ACTIVE” and the tasks T1 and T2 are “ACTIVE”. The states of steps S4 and S5 that are "SUSPENDED" are set.

  Specifically, the state “ACTIVE” in the same row as the work context ID “C1” in the work context master table 15 is changed to “SUSPENDED” indicating interruption.

  Further, the respective states “ACTIVE” in the same row as the task IDs “T1” and “T2” in the task master table 16 are changed to “SUSPENDED”.

  In addition, each state “ACTIVE” in the same row as the step IDs “S4” and “S5” in the step master table 17 is changed to “SUSPENDED”.

  In the present embodiment described above, even if the user 1 uses different terminals before and after the work interruption, the work before the interruption can be continuously performed after the interruption.

  In the present embodiment, a series of work contents of the user 1 are managed by a tree structure. Thereby, even after interruption / resumption, the work of the user 1 can be traced back in units of steps or units of work flow (units of task transitions). In addition, it is possible to perform work rework in units of steps or work flow units (task transition units). Also, it is possible to go back only part of the work and proceed with another content from the middle of the flow.

  On the other hand, for example, when managing the work history with snapshots, it is difficult to trace back only a certain unit of work because the context of each unit of work is not managed between snapshots. It is also difficult to redo only a certain unit of work and to proceed with another development.

  Further, by using the tree structure management according to the present embodiment, it is possible to express processing such as merging and waiting for a plurality of tasks newly started by branching, and it can be used for resuming work.

  Further, based on the user information 10, work context information 11, task information 12, and step information 13, a series of work can be easily grasped.

  In this embodiment, since the tree structure can be traced up from the end of the tree structure, the instruction contents are reflected in the upper steps, tasks, and work contexts by giving instructions to the lower specific steps or tasks. Can be executed.

  For example, by giving an instruction to a terminal step or task, processing corresponding to the instruction can be executed for the entire work context to which the terminal step or task belongs.

  In addition, for example, based on an instruction to suspend or resume a step or task, it is possible to suspend or resume a series of tasks or an entire work context.

  Note that the program 3a according to the present embodiment can be applied to a computer by writing in the recording medium 3 such as a magnetic disk (flexible disk, hard disk, etc.), an optical disk (CD-ROM, DVD, etc.), a semiconductor memory, or the like. .

  The program 3a can also be applied to a computer by being transmitted through a communication medium. Each computer reads the program 3a, and the operation is controlled by the program 3a, thereby realizing the above functions.

  In the present embodiment, each function realized by software may be realized by hardware.

  In the work management system 2 according to the present embodiment, the program 3a may be distributed and arranged in a plurality of computers, and processing may be executed while cooperating with each other.

(Second Embodiment)
In this embodiment, as a specific example of a work context, a task, and a step, a case where a travel plan is set as a work context will be described.

  FIG. 22 is a diagram illustrating an example of a work context related to a travel planning process.

  FIG. 23 is a diagram illustrating an example of a data structure of data for managing a travel planning process.

  FIG. 24 is a block diagram illustrating an example of a logical configuration of the work management system 2 according to the present embodiment.

  The user 1 accesses the service provider SP1 existing in the back end through a client device 18 such as a mobile phone or a PDA (Personal Digital Assistant), for example, a client device 19 such as a PC (Personal Computer).

  Here, the service provider SP1 is a target site that the user 1 wants to access, such as a search service site, a news site, and a shopping site.

  The work management system 2 is interposed between the client devices 18 and 19 and the service provider SP1, and manages a series of work of the user 1.

  The work management system 2 includes a client connection unit 20, a user authentication unit 21, a user proxy management unit 22, and a work context management unit 23.

  The client connection unit 20 receives an instruction (request) from one of the client devices 18 and 19, and performs access to the service provider SP1 based on the content of this instruction.

  The client connection unit 20 includes a portal type connection unit 20a that accepts a connection from a thin client terminal having a browser with a limited function such as a mobile phone or a PDA, and a Fat Client such as a PC or WS (Work Station). A proxy type connection unit 20b that accepts a connection from a system terminal is provided.

  The user interface for causing the user 1 to perform work (operation) varies depending on the client devices 18 and 19. For this reason, in the present embodiment, a plurality of client device interfaces such as a Portal type connection unit 20a and a Proxy type connection unit 20b are prepared. In the work management system 2, the client connection unit 20 that receives input from the client devices 18 and 19 and the work context management unit 23 are made independent.

  The Portal type connection unit 20a is an interface mainly assuming a single window client, and the Proxy type connection unit 20b is an interface mainly assuming a multi-window client.

  However, depending on the configuration of the client devices 18 and 19, the proxy type connection unit 20b can be used even for a single window client, and similarly the portal type connection unit 20a is used even for a multi-window client. It is possible.

  The user authentication unit 21 performs user authentication for the user 1 who accesses the client connection unit 20 from any one of the client devices 18 and 19.

  The user proxy management unit 22 simulates the work of the user 1. The user proxy management unit 22 stores data related to the user proxy in the user proxy storage unit 24, and reads data related to the user proxy from the user proxy storage unit 24.

  The work context management unit 23 realizes work context management in the format shown in FIG. That is, the work context management unit 23 corresponds to the first to fourth management units 4 to 7 and the restart unit 8 in FIG. 1 and stores information 10 to 13 in the storage unit 9.

  In the present embodiment, the work context management unit 23 also manages information indicating the context such as “previous step ID” and “next step ID” in order to manage the context of the work.

  Below, the work performed by the user 1 through one of the client devices 18 and 19 and the work context management of the work management system 2 for this work will be described in association with each other.

  First, it is assumed that the user 1 logs into the work management system 2.

  In this case, the user authentication unit 21 performs user authentication for the user 1. The user proxy management unit 22 generates data related to the user proxy for simulating the work when the data related to the user proxy of the user 1 is not stored in the user proxy storage unit 24. On the other hand, when data related to the user proxy of the user 1 is stored in the user proxy storage unit 24, the user proxy management unit 22 reads out data related to the user proxy of the user 1 from the user proxy storage unit 24.

  Second, it is assumed that the user 1 gives an instruction to start a new work.

  In this case, the work context management unit 23 stores information on the new work context in the storage unit 9. This management state is the state shown in FIG. 7 and FIG.

  Thirdly, it is assumed that the user 1 gives an instruction to start a task.

  In this case, the work context management unit 23 stores information on the new task and the first step of the new task in the storage unit 9. This management state is the state of FIG. 9 and FIG. 10, or the state of FIG. 13 and FIG.

  Fourthly, it is assumed that the user 1 instructs task progress.

  In this case, the work context management unit 23 stores in the storage unit 9 information related to a new step for the progress target task in the work context to which the progress target task belongs. This management state is the state shown in FIGS. 11 and 12, FIG. 15 and FIG. 16, FIG. 17 and FIG.

  Fifth, it is assumed that the user 1 gives an instruction to end the task.

  In this case, the work context management unit 23 stores information indicating that the task is completed in the storage unit 9 in the work context to which the task to be terminated belongs. This management state is the state shown in FIG. 19 and FIG.

  Sixth, it is assumed that the user 1 gives an instruction to interrupt the work.

  In this case, the work context management unit 23 stores information indicating the interruption of the work context in the storage unit 9.

  Seventhly, it is assumed that the user 1 gives an instruction to resume work.

  In this case, the work context management unit 23 reads the state of the work context designated by the user 1 from the storage unit 9 and resumes (restores).

  Eighth, assume that the user 1 has logged out of the work management system 2.

  In this case, the user proxy management unit 22 stores data related to the user proxy of the user 1 in the user proxy storage unit 24.

(Third embodiment)
In the present embodiment, a detailed example of the second embodiment will be described.

  FIG. 25 is a block diagram illustrating an example of a logical configuration of the work management system 2 according to the present embodiment.

  Elements 25, 26, 20a to 20e, 21, 22a, 22b, 23a, and SP1 shown in FIG. 25 represent classes. Some classes are only rectangles and others are divided in three.

  A class name is described for a class using only a rectangle, and a class name, attributes, and processing are described from the top for a class divided into three. When classes are connected by a solid line, it indicates that there is some relationship between classes connected by a solid line.

  Below, each class of this Embodiment is demonstrated.

  The “browser (mobile / PDA)” class represents a browser used by the user when the client device is a mobile phone or a PDA.

  The “browser (PC)” class represents a browser used by the user when the client device is a PC or the like.

  The “Portal type connection unit” class represents a class that receives a request from the user when operating in the Portal type.

  The “Proxy type connection unit” class represents a class that receives a request from a user when operating in the Proxy type.

  The Portal type connection unit 20a and the Proxy type connection unit 20b request the client connection common unit 20e to execute the suspension / resume process and access to the service provider SP1.

  “Portal content rewriting” class is a class for rewriting the content of the HTTP response for Portal.

  The “Proxy content rewriting” class is a class for rewriting the content of the HTTP response for Proxy.

  The “client connection common part” class is a class in charge of the core of the processing performed by the work management system 2. The client connection common unit 20e accesses the service provider SP1 and requests the work context management 23a for processing via the user proxy 22b.

  The “service provider” class represents a provider of a service desired by a user, such as a news site, a shopping site, or a search site.

  The “user authentication unit” class is a class for performing user authentication in the work management system 2.

  The “user proxy management” class is a class for managing user proxies.

  The “user proxy” class is a class that works as a user agent in the work management system 2.

  The “work context management” class is a class for managing a work context. The targets handled in this “work context management” are user information 10, work context information 11, task information 12, and step information 13. Each information 10-13 is stored in tables 14-17, respectively. The step master table 17 has data items for representing the order of steps, such as “previous step ID” and “next step ID”.

  The user accesses the back-end service provider SP1 through one of the browsers 25 and 26 installed in the client device, and performs a series of operations.

  In this embodiment, a description will be given assuming that a task corresponds to a browser window and a step corresponds to a screen transition on each browser window.

  An operation for opening a new window from a certain window corresponds to a task branch, and an operation for closing a window corresponds to the end of a task. A group of multiple windows corresponds to a work context.

  Below, the relationship between a user's operation and the process of the work management system 2 according to it is demonstrated using a screen and a sequence diagram.

  In the sequence diagram, message passing in the case where a certain process is executed is represented with time. In the following, vertical dotted lines in the figure indicate objects belonging to the class, and horizontal lines indicate messages. Time flows from top to bottom. In this embodiment, a value (return value) returned as a result of executing a message is expressed by enclosing it in []. For example, when 1 is returned, it is represented as [1].

  FIG. 26 is a diagram illustrating an example of a login screen of the client device to the work management system 2 in a multi-window environment.

  On the screen 27A, an authentication window is displayed by the work management system 2 when the user accesses the service provider SP1.

  If there is no problem in the authentication result, the screen transitions to the screen 27B. On the screen 27B, a list of work contexts held by the user 1 is displayed. The screen 27B can also accept an instruction to start a new work context from the user.

  FIG. 27 is a sequence diagram illustrating an example of login processing of the work management system 2 at the time of transition from the screen 27A to the screen 27B.

  When the user (child A) tries to access the service provider SP1 (message numbers a1 and a2), the input is accepted, authentication and login are performed, and the user proxy is acquired (a3 to a8).

  Next, the user's work context list is acquired (a9 to a13), and the screen 27B is generated (a14 to a15).

  In the case where the data structure of FIG. 23 is used, the work context list acquired with the message number a11 acquires the work context ID of the user in the user master table 14, and based on the acquired work context ID. It is obtained by searching the work context master table and acquiring a list of work context IDs and work context names whose state is “SUSPENDED”.

  FIG. 28 is a diagram illustrating an example of a screen of a client device when a new work context is started in a multi-window environment.

  When the URL belonging to the new context is specified on the screen 27B and the mouse is clicked, the window of the specified URL ("Exploring in front of the station" in FIG. 28) and the work management system control window ("Work" in FIG. 28) Interrupt ") opens.

  The result of accessing the service provider SP1 is displayed in the specified URL window.

  However, a script for notifying the work management system 2 of the end of the step at the time of screen transition is added to the display content (content). This script does not affect the appearance.

  FIG. 29 is a sequence diagram illustrating an example of a new work start process of the work management system 2 at the time of transition from the screen 27B to the screen 27C.

  The new context start instruction is notified from the user to the work context management via various parts (b1 to b6).

  The work context management 23a stores information on the new work context (b7). Specifically, as shown in FIG. 8, a work context ID is added to the user master table 14, and new work context information 11 is added to the work context master data 15.

  The proxy connection unit 20b subsequently executes new task generation based on the URL specified by the user.

  Access to the service provider SP1 is implemented as part of the new task generation. Since new task generation will be described later, it is omitted here (b8).

  Then, based on the access result to the service provider SP1, the page immediately after the start of the work context and the work management system control window are generated and displayed (b9 to b10). In FIG. 28, the “XX Newspaper” page is displayed on the screen 27C immediately after the work context starts.

  Note that authentication (b3 in the figure) through the proxy type connection unit 20b is automatically executed based on information at the time of login, so that the user does not need to input a user name and password every time.

  FIG. 30 is a diagram illustrating an example of a screen of a client device when a work context is interrupted in a multi-window environment.

  When the “work suspension” link in the work management system control window is clicked on the screen 27D, a message shown on the screen 27E is displayed in the window.

  FIG. 31 is a sequence diagram illustrating an example of an interruption process of the work management system 2 at the time of transition from the screen 27D to the screen 27E.

  The context interruption instruction is sent to the work context management 23a (c1 to c5). The work context management 23a stores information on the work context, task, and step in the storage unit 9 when the context interruption instruction is received. Specifically, as shown in FIG. 21, the state of the corresponding work context, task, and step is “SUSPENDED”.

  FIG. 32 is a diagram illustrating an example of a screen of a client device when context is resumed in a multi-window environment.

  When a saved work context is selected on the screen 27B, the state when the work context is interrupted is reproduced. Specifically, windows for the suspended tasks are displayed, and the contents at the time of suspension are displayed in each window.

  FIG. 33 is a sequence diagram illustrating an example of resumption processing of the work management system 2 at the time of transition from the screen 27B to the screen 27D.

  A context resumption instruction is sent to the work context management 23a together with the contents specified by the user (d1 to d5).

  The work context management 23a returns information on the suspended task in the corresponding work context (d6 to d7).

  Subsequently, window generation (d8), task restart (d9), and content display (d17) are repeated for the number of suspended tasks. The information of the suspended task is obtained by acquiring the task ID based on the state “SUSPENDED” of the work context master table 15 as shown in FIG. 21 and searching the task master table 16 based on the task ID. Is done.

  In the task restart (d9), first, information on the suspended step is acquired (d10 to d13), and then each step is restarted. The information of the suspended step is obtained by acquiring the step ID based on the state “SUSPENDED” of the task master table 16 as shown in FIG. 21 and searching the step master table 17 based on the step ID. The

  Here, specifically, the restart refers to reading out information stored in the storage unit 9, processing it as content, and displaying it on a window. The display on the window is performed by the message d17.

  The screen of the client device at the start of the task in the multi-window environment is the same as the start of the new work context described with reference to FIG.

  Further, as shown in FIG. 34, a screen transition for generating a new window may be handled as a task start. Note that normally, when a screen transition occurs, two steps, the start of a step and the end of a step, are executed. The screen transition shown in FIG. 28 corresponds to the transition from the state of FIG. 7 to the state of FIG.

  FIG. 35 is a sequence diagram illustrating a first example of task start processing of the work management system 2.

  A task start instruction is sent to the work context management 23a together with the contents of the task designated by the user (e1, e2).

  The work context management 23a creates task information 12 and step information 13 (e3). The client connection common unit 20e accesses the URL designated by the user (e4), and stores information on the task in the storage unit 9 based on the access result.

  As a result, in the state shown in FIG. 10, the information related to the task and the information related to the step are updated (e5, e6).

  The proxy content rewriting 20d embeds management information (for example, a command to send a message when the window disappears) in the display information returned to the client device (e7, e8).

  In the present embodiment, the task progress work in the multi-window environment is a click on a hyperlink as an operation on the screen in the client device.

  FIG. 36 is a sequence diagram illustrating a second example of the task start process of the work management system 2. FIG. 36 shows an example in which the task to which the pre-transition page belongs is terminated and the next screen is displayed as a new task.

  When the hyperlink is clicked, task end processing and task start processing are executed. The task termination process will be described later. Moreover, since the task start process has been described above, the description thereof is omitted.

  As another example of the task progress work, when a hyperlink is clicked, a new step may be added to the task to which the pre-transition page belongs and the next screen may be displayed. The process executed in this case corresponds to the state in which the messages e1 and e2 are changed from the task start to the task progress in the process of FIG. In this case, the process corresponding to FIG. 15 to FIG. 18 is executed in the task progress of the message e2.

  FIG. 37 is a diagram illustrating an example of a screen of the client device at the end of the task in the multi-window environment.

  When the window is closed on the screen 27D, the task executed in the closed window is ended.

  FIG. 38 is a sequence diagram illustrating an example of a task end process executed by the work management system 2.

  When the user closes the window, task completion is notified to the work context management 23a (g1 to g5). The task to be ended is specified from the user ID and task information. Then, the processing corresponding to FIG. 19 and FIG. 20 is executed, and the states relating to the tasks and steps are updated.

  FIG. 39 is a diagram illustrating an example of a screen of a client device when logging in to the work management system 2 in a single window environment. FIG. 40 is a sequence diagram illustrating an example of a login process executed by the work management system 2 in a single window environment. The single window environment is the same as that in the multi-window environment.

  FIG. 41 is a diagram showing an example of a screen of the client device when logging out of the work management system 2 in a single window environment. FIG. 42 is a sequence diagram illustrating an example of logout processing executed by the work management system 2 in a single window environment.

  When a logout instruction is accepted from the user, the state of the corresponding user in the user master table 14 is changed to “logout”. Logout may be performed only when all work contexts are interrupted or terminated, or logout may be possible even when there is a work context being executed.

  FIG. 43 is a diagram illustrating an example of a screen of a client device at the start of a new work context in a single window environment. FIG. 44 is a sequence diagram illustrating an example of a new work start process executed by the work management system 2 in a single window environment. The single window environment is the same as that in the multi-window environment.

  FIG. 45 is a diagram illustrating an example of a screen of a client device at the time of starting a task in a single window environment. FIG. 46 is a sequence diagram illustrating an example of a new task start process executed by the work management system 2 in a single window environment. The single window environment is the same as that in the multi-window environment.

  In the present embodiment described above, when the user operates the client device on the ubiquitous environment, the same operational effects as those in the first embodiment can be obtained. For example, it is possible to go back to the state of the previous step in units of steps, and restart and redo in units of steps, thereby realizing effective transaction management.

  Further, in the present embodiment, in a ubiquitous environment, regardless of whether the client device is a multi-window environment or a single window environment, various series of operations performed by the user are managed together.

  Further, the work management system 2 according to the present embodiment manages the progress of a series of work. For this reason, the work management system 2 can be used as a system for analyzing and investigating work trends of users, for example. As a result, Web marketing can be performed using the work management system 2. In addition, for example, the work management system 2 can be used as a work efficiency improvement proposal tool that measures and uses the time taken to execute each step, and a system that manages and accumulates the flow of discussions and ideas in brainstorming.

  In the present embodiment, the work management system 2 may manage not only the management of the browser screen but also the data specifying the work environment. Thereby, the user can work in the same environment, for example, at the office and at home.

  Further, the data output destination by the work management system 2 is not limited to the browser. For example, the work management system 2 takes out data in a format suitable for the output environment of the user, and the user designates in a place with a machine with a small resolution. The data belonging to the work context or task or step may be automatically output on paper from the nearest printer or FAX.

  In addition, each component of the work management system 2 according to each of the above embodiments may be rearranged as long as the same action can be realized, or each component may be freely combined. The components may be deleted.

(Fourth embodiment)
In the present embodiment, a relationship between work contexts, tasks, and steps different from those in the first to third embodiments will be described.

  As a first example, a work context in which a television is purchased through online shopping is assumed.

  The purchase applicant performs, for example, the following work using a browser at a shopping site such as kakaku.com.

(WA1) The product name is input in the product search and the search is executed.

(WA2) A desired product is selected on the search result list display screen.

(WA3) Confirm the product name and price on the desired product list screen and select purchase.

(WA4) Set up a payment method and a destination on the settlement screen and perform settlement.

  In this work, each of (WA1) to (WA4) is a step. Each of these steps (WA1) to (WA4) belongs to one task.

  Between (WA2) and (WA3), there is a case where work such as checking detailed information of a certain product or checking prices at other shopping sites may be performed. In this case, the detailed information survey and the price survey at another site are other tasks branched from (WA2) or the like.

  As a second example, a work context for browsing articles on a news site is assumed.

  The reader's work is as follows, for example.

(WB1) Select an article on the heading list page.

(WB2) View details of the selected article.

(WB3) Browse the details of the next article.

  In this work, each (WB1) to (WB3) is a step. These steps (WB1) to (WB3) belong to one task.

  Between (WB2) and (WB3), there are cases in which operations such as examining related information of introduced information or examining the handling of the same news at other news sites may be performed. In this case, the investigation of related information and the investigation at another site are other tasks branched from (WB2) or the like.

  As a third example, e-learning in a company is assumed.

  The work of employees who are students is as follows, for example.

(WC1) The e-learning course is started using the PC at his / her seat and the first screen is displayed.

(WCp) The screen transition is repeated to display the p-th screen.

  In this work, each of (WC1) to (WCp) is a step. Each of these steps (WC1) to (WCp) belongs to one task.

  For example, if the student has to go out after completing the course up to (WCp), the work can be interrupted at (WCp).

  While moving outside, using a portable information terminal such as a PDA on the train, the work can be resumed from (WCp), and the work can be continued at (WCp + 1) and (WCp + 2).

  In each of the above embodiments, the case where “start of another screen at the time of browser transition” is detected is determined as the occurrence of “task branch”. However, the occurrence of “task branch” may be detected by allowing the user to explicitly designate “task branch” as the user interface.

  Further, in each of the above-described embodiments, when “explicit browser activation by user icon click or the like” is detected, it is determined that “new work context start” occurs. However, the occurrence of “start of a new work context” may be detected by explicitly specifying “start of a new work context” as a user interface.

1 is a block diagram showing an example of a work management system according to a first embodiment of the present invention. The figure which shows an example of the relationship between a user, a work context, a task, and a step. The class diagram which shows an example of the relationship between a user, a work context, a task, and a step. The data structure figure which shows an example of user management data, work management data, task management data, and step management data. The flowchart which shows an example of the operation | work which a user performs in the embodiment. The figure which shows an example of the data structure immediately after a user's login. The figure which shows an example of the state of the work context at the time of work start. The figure which shows an example of the data structure at the time of new work start. The figure which shows an example of the work context at the time of a task start. The figure which shows an example of the data structure at the time of a task start. The figure which shows an example of the work context at the time of the 1st progress of a task. The figure which shows an example of the data structure at the time of 1st task progress. The figure which shows an example of the work context at the time of new task start. The figure which shows an example of the data structure at the time of new task start. The figure which shows an example of the work context at the time of new task progress. The figure which shows an example of the data structure at the time of new task progress. The figure which shows an example of the work context at the time of the 2nd progress of a task. The figure which shows an example of the data structure at the time of the 2nd progress of a task. The figure which shows an example of the work context at the time of new task completion | finish. The figure which shows an example of the data structure at the time of new task completion | finish. The figure which shows an example of the data structure at the time of a user's work interruption. The figure which shows an example of the work context regarding the planning work of the travel plan which concerns on the 2nd Embodiment of this invention. The figure which shows an example of the data structure of the data which manage the planning work of a travel plan. The block diagram which shows an example of the logical structure of the work management system which concerns on the embodiment. The block diagram which shows an example of the logical structure of the work management system which concerns on the 3rd Embodiment of this invention. The figure which shows an example of the screen of the client apparatus at the time of login to the work management system in a multi-window environment. The sequence diagram which shows an example of the login process of the work management system in a multi-window environment. The figure which shows an example of the screen of the client apparatus at the time of the new work context start in a multi-window environment. The sequence diagram which shows an example of the new work start process of the work management system in a multi-window environment. The figure which shows an example of the screen of the client apparatus at the time of the work context interruption in a multi-window environment. The sequence diagram which shows an example of the interruption process of the work management system in a multi-window environment. The figure which shows an example of the screen of the client apparatus at the time of context resumption in a multi-window environment. The sequence diagram which shows an example of the restart process of the work management system in a multi-window environment. The figure which shows an example of the screen transition which handles the production | generation of a new window as a task start in a multi-window environment. The sequence diagram which shows the 1st example of the task start process of the work management system in a multi-window environment. The sequence diagram which shows the 2nd example of the task start process of the work management system in a multi-window environment. The figure which shows an example of the screen of the client apparatus at the time of the task end in a multi-window environment. The sequence diagram which shows an example of the task end process of the work management system in a multi-window environment. The figure which shows an example of the screen of the client apparatus at the time of login to the work management system in a single window environment. The sequence diagram which shows an example of the login process of the work management system in a single window environment. The figure which shows an example of the screen of the client apparatus at the time of logout of the work management system in a single window environment. The sequence diagram which shows an example of the logout process of the work management system in a single window environment. The figure which shows an example of the screen of the client apparatus at the time of the new work context start in a single window environment. The sequence diagram which shows an example of the new work start process of the work management system in a single window environment. The figure which shows an example of the screen of the client apparatus at the time of the task start in a single window environment. The sequence diagram which shows an example of the new task start process of the work management system in a single window environment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... User, 2 ... Work management system, TM1-TMn ... Terminal, SP1-SPm ... Service provider, 3 ... Recording medium, 3a ... Program, 4 ... 1st management part, 5 ... 2nd management part, 6 ... 3rd Management unit, 7 ... 4th management unit, 8 ... Resume unit, 9 ... Storage unit, 10 ... User management data, 11 ... Work management data, 12 ... Task management data, 13 ... Step management data, 14 ... User master table, DESCRIPTION OF SYMBOLS 15 ... Work context master table, 16 ... Task master table, 17 ... Step master table, C1 ... Context, T1, T2 ... Work context, S1-S5 ... Step, 18, 19 ... Client device, 20 ... Client connection part, 20a ... Portal type connection unit, 20b ... Proxy type connection unit, 20c ... Portal content rewriting, 20d ... Proxy content rewriting, 20 e ... Client connection common unit, 21 ... User authentication unit, 22 ... User proxy management unit, 22a ... User proxy management, 22b ... User proxy, 23 ... Work context management unit, 23a ... Work context management, 24 ... User proxy storage unit , 25, 26 ... Browser

Claims (9)

First management means for managing user information relating user identification data for identifying a user and work identification data for identifying a work by the user;
A second management unit that manages work context information that associates the work identification data with task identification data for identifying a task that represents a flow of steps in the work;
Third management means for managing task information relating the task identification data and step identification data indicating steps initiated by the user in the task;
Fourth management means for managing step information relating the step identification data and step state information indicating whether or not the step indicated by the step identification data is in an interrupted state;
Means for resuming a step in which the step state information indicates a suspended state based on the user information, the work context information, the task information, and the step information when a restart instruction and the user identification data are input; A work management system comprising: The work management system according to claim 1,
The work context information includes the user identification data,
The task information includes the work identification data,
The step management information includes the task identification data. In the work management system according to claim 1 or claim 2,
The step management system is characterized in that the step information associates the step identification data with previous step identification data indicating a previous step belonging to the same task as the step and performed before the step. In the work management system according to any one of claims 1 to 3,
The step information relates to the step identification data and post step identification data indicating a post step performed after the step belonging to the same task as the step. In the work management system according to claim 3 or claim 4,
The work management system, wherein the restarting means restarts the previous step according to an instruction. In the work management system according to any one of claims 1 to 5,
When the task branch event occurs in the work, the second management means associates the work identification data with new task identification data indicating a task branched from the task in the work context information,
The third management means manages the new task information in which the same data relation as the task identification data in the task information is associated with the new task identification data,
The fourth management means manages the new step information obtained by associating the new step identification data indicating the step started by the user in the new task with the same data relation as the step identification data in the step information. And
The resumption means is included in the new step information based on the user information, the work context information, the new task information, and the new step information when the resumption instruction and the user identification data are input. A work management system characterized by resuming a step whose suspended step state information indicates a suspended state. The work management system according to claim 6,
The task information and the new task information include parent task identification information indicating a branch source parent task and child task identification information indicating a branch destination child task. Computer
Means for managing user information relating user identification data for identifying a user and work identification data for identifying a work by the user by means of storage means;
Means for managing work context information relating the work identification data and task identification data for identifying a task representing a flow of steps in the work by the storage means;
Means for managing task information that associates the task identification data with step identification data indicating a step initiated by the user in the task by the storage means;
Means for managing step information relating the step identification data and step state information indicating whether or not the step indicated by the step identification data is in an interrupted state by the storage means;
As a means for resuming a step in which the step state information indicates a suspended state based on the user information, the work context information, the task information, and the step information when a restart instruction and the user identification data are input. A program to make it work. In a method of managing user work by a computer,
User information associated with user identification data for identifying a user and work identification data for identifying a work by the user is managed by the storage means;
The storage means manages work context information relating the work identification data and task identification data for identifying a task representing a flow of steps in the work,
The storage means manages task information that associates the task identification data with step identification data indicating a step initiated by the user in the task,
The storage means manages the step information relating the step identification data and step state information indicating whether or not the step indicated by the step identification data is in an interrupted state,
When a restart instruction and the user identification data are input, based on the user information, the work context information, the task information, and the step information, the step state information restarts the step indicating the suspended state. A featured work management method.

Images