WO2015162879A1 - タスク特定装置、タスク特定方法および記録媒体 - Google Patents
タスク特定装置、タスク特定方法および記録媒体 Download PDFInfo
- Publication number
- WO2015162879A1 WO2015162879A1 PCT/JP2015/002094 JP2015002094W WO2015162879A1 WO 2015162879 A1 WO2015162879 A1 WO 2015162879A1 JP 2015002094 W JP2015002094 W JP 2015002094W WO 2015162879 A1 WO2015162879 A1 WO 2015162879A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- task
- model
- interest
- activity
- stakeholder
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06316—Sequencing of tasks or work
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0635—Risk analysis of enterprise or organisation activities
Definitions
- the present invention relates to a task specifying device applied to a system development process.
- IT vendor companies are expected to respond quickly and flexibly to system development.
- system development using agile development and iterative development has been performed.
- the system development is different from the project management method divided into each stage such as process-based development.
- collaborative work within the IT vendor company and between the IT vendor company and the user company is performed. is important.
- consensus building and information transmission based on communication between each stakeholder.
- “stakeholder” means a decision maker involved in the development process. Specifically, it refers to planners and budget managers in the planning phase, and design managers in the design phase.
- Non-Patent Document 1 discloses a technology related to SEMAT (Software Engineering Method and Theory), which is one of software development methods.
- SEMAT Software Engineering Method and Theory
- the technology disclosed in Non-Patent Document 1 is not for managing software development by process, but for the purpose of managing by tasks corresponding to each interest based on several kinds of concerns that cross the development process. Yes.
- Patent Document 1 describes an apparatus for analyzing organizational communication logs. Patent Document 1 discloses a technique for determining factors of activation and deactivation of organizational communication by combining qualitative information using an electronic mail and an electronic bulletin board that can be analyzed quantitatively.
- Patent Document 2 uses WBS (Work Breakdown Structure) to extract the components of the team's work, tasks, and deliverables, thereby managing the progress of multiple tasks associated with each of the multiple components.
- WBS Work Breakdown Structure
- Non-Patent Document 1 defines three items.
- the three items are seven concerns that cross the development process, Kernel Alpha indicating the status of each of these concerns, and inspection items for examining the achievement level of Kernel Alpha.
- development is managed using each card written about three defined items. Cards are arranged in chronological order according to the contents of Kernel Alpha based on their interests. The position of the card varies depending on whether or not the inspection items written in the card have been performed. Confirmation of the inspection items written on the card is performed among the stakeholders involved at that time.
- SEMAT development can be managed on a task basis, but it is not possible to clarify the interests among the stakeholders. In other words, it is not possible to identify tasks that are lacking in recognition among stakeholders involved in development.
- Patent Document 1 the cause of the activation and inactivation of the organization communication is determined by analyzing the communication log in the organization, but the cause of the difference in recognition of each stakeholder that is the basis of the communication is specified. I can't do it.
- Patent Document 2 a WBS is essential for managing the progress of a task, and a project cannot be managed without a WBS. Further, similarly to Patent Document 1, it is not possible to specify the cause of the difference in recognition of each stakeholder.
- the present invention has as its main object to provide a task identification device and the like that can identify a task that is necessary for consensus formation and information transmission in collaboration between stakeholders, but is missing from the recognition of each stakeholder.
- the task identification device has the following configuration.
- the interests of each stakeholder are composed of activities that constitute the interests, and tasks that are detailed to a level at which this activity can be executed.
- the first aspect of the present invention is: An interest task model generating means for generating an interest task model in which the relationship between the activity included in the stakeholder information indicating the action content of the stakeholder, the interest to which the activity belongs, and the task that details the activity is structured; , Tasks that generate a task-specific model that structures the relationship between the interests required at any point in the development process, the activities to be achieved corresponding to the required interests, and the tasks detailing the activities Specific model generation means; It is a task specifying device provided with a task extracting unit that compares a task of an interest task model with a task of a task specifying model and extracts a difference.
- an interest task model that structures the relationship between the activities included in the stakeholder information indicating the stakeholder's behavior, the interests to which the activity belongs, and the task that details the activity
- Generate a task-specific model that structures the relationship between the interests required at any point in the development process, the activities to be achieved corresponding to the required interests, and the tasks detailing the activities
- This is a task identification method that compares a task of an interest task model with a task of a task identification model and extracts a difference.
- It is explanatory drawing which represented typically the communication between stakeholders at the time of a development process. It is a figure which shows the data structure of stakeholder information (input information). It is a figure which shows the data structure of a roll interest correspondence list
- FIG. 19 is an explanatory diagram abstractly showing a series of processes for collating stakeholder input information with the accomplished activity list shown in FIG. 18.
- FIG. 18
- FIG. 11 is an explanatory diagram abstractly showing a series of processes for generating a main concern model in step S308. It is explanatory drawing which shows an example of a main interest model.
- FIG. 10 is an explanatory diagram abstractly showing a series of processes for generating a task identification model using a main interest model and a standard task list in steps S309 to S311. It is explanatory drawing which shows an example of a task specific model. It is a flowchart which shows the operation
- FIG. 1 is a block diagram showing a configuration of a task identification device 1 according to the first embodiment of the present invention.
- the task identification device 1 includes an interest task model generation unit 110, a main interest model generation unit 120, a task identification model generation unit 130, a task extraction unit 140, an interest related information storage unit 200, a task model storage unit 210, and various stakeholders.
- An information input unit 300, a search condition input unit 310, and a display unit 320 are provided.
- the stakeholder information input by the operation of the operator or the like is output to the interest-related information storage unit 200.
- the stakeholder information includes information about the role (hereinafter referred to as “role”) and information about the activity (hereinafter referred to as “activity”).
- the role means a stakeholder's mission (role), and the activity means an action necessary to fulfill the mission.
- various stakeholder information input units 300 are used in the interested task model generating unit 110, the main interested model generating unit 120, and the task specific model generating unit 130.
- the search condition input unit 310 transmits the search condition (role and activity included in each stakeholder information) input by the operation of the operator or the like to the task extraction unit 140.
- the interested task model generation unit 110 is based on the stakeholder information input from the various stakeholder information input units 300, and the interested task model 211 configured by a tree structure of the information extracted from the interested related information storage unit 200 (see FIG. 5). Is generated. Concern is the work that each stakeholder is particularly interested in (careful) at any point in the development process.
- the stakeholder information includes an activity (first activity) indicating the action content of the stakeholder.
- the information extracted from the interest-related information storage unit 200 is information indicating interests, activities, and tasks.
- the interested task model generation unit 110 stores, in the task model storage unit 210, information in which the roles and activities included in the stakeholder information input from the various stakeholder information input units 300 are associated with the generated interested task model 211. Details of the structure of the interest task model 211 will be described later.
- the main interest model generation unit 120 generates a main interest model 213 (see FIG. 6) in which the correspondence between the plurality of activities input from the interest related information storage unit 200 and each interest to which the activity belongs is structured. To do.
- the main interest model generation unit 120 manages information in which main interests are associated with roles and activities included in the stakeholder information input from the various stakeholder information input units 300. Details of the structure of the main concern model 213 will be described later.
- the task identification model generation unit 130 is structured as a task identification model 212 (FIG. 7) in which a concern related to a certain main concern, an activity related to the concern, and a correspondence relationship between tasks related to the activity are structured in a tree structure. Reference).
- the interest is an interest constituting the main concern model 213 at a certain time generated by the main interest model generation unit 120.
- the output task is a task acquired from the interest-related information storage unit 200 based on the activity information of the main interest model 213.
- the activity related to the interest here is an activity to be achieved (second activity) corresponding to each interest.
- the task specific model generation unit 130 stores, in the task model storage unit 210, information in which the roles and activities included in the stakeholder information input from the various stakeholder information input unit 300 are associated with the generated task specific model 212. Details of the structure of the task identification model 212 will be described later.
- the task extraction unit 140 searches the information stored in the task model storage unit 210 based on the search condition input from the search condition input unit 310, and displays the search result on the display unit 320.
- the task extraction unit 140 uses the roles and activities included in each input stakeholder information as a search condition to search the interested task model 211 and the task identification model 212 included in each related stakeholder information. Search in the model storage unit 210.
- the task extraction unit 140 compares the task of the interested task model 211 of each stakeholder and the task of the task identification model 212, which are search results, and extracts a task difference.
- the task extraction unit 140 outputs the extracted task difference information and the interested task model 211 and the task identification model 212 of each stakeholder as search results to the display unit 320.
- the interest related information storage unit 200 includes a storage device (not shown) such as a memory, and the role interest correspondence list 201, the standard activity list 202, the standard task, which are defined or created in advance by the user or the like in the storage device.
- a list 203 and an accomplished activity list 204 are stored.
- the interested-related information storage unit 200 is based on input information (from stakeholder information (see FIG. 3A)) input from various stakeholder information input units 300, and from the stored lists 201 to 204, the interested task model generation unit 110
- the main interest model generation unit 120 searches for information necessary for model generation and outputs the information to the generation units 110 and 120.
- the interested-related information storage unit 200 collates the role included in the stakeholder information with the role-interest correspondence list 201 (see FIG. 3B). Extract multiple corresponding interests.
- the interest-related information storage unit 200 compares the extracted plurality of interests with the standard activity list 202 (see FIG. 3C), and extracts a plurality of activities constituting each interest.
- the interest-related information storage unit 200 collates the extracted activities with the activities included in the stakeholder information input from the various stakeholder information input units 300, and determines the interests to which the activities included in the input stakeholder information belong. Identify.
- the interest-related information storage unit 200 outputs information relating the identified interest and the role included in the stakeholder information to the interest task model generation unit 110.
- the interested-related information storage unit 200 collates the standard task list 203, extracts the tasks corresponding to the activities included in the stakeholder information, and extracts them.
- the task and the role included in the stakeholder information are associated with each other and output to the interested task model generation unit 110.
- the interest-related information storage unit 200 adds “interests” and “tasks” extracted from the lists 201 to 204 stored by itself based on the stakeholder information input from the various stakeholder information input units 300.
- Information related to “role” and “activity” included in the stakeholder information is output to the interested task model generation unit 110.
- the interested-related information storage unit 200 collates the achieved activity list 204 (see FIG. 4). As a result of the collation, the interest-related information storage unit 200 sends, to the main interest model generation unit 120, information that associates the interest that the activity belongs to the activity determined to be unachieved and the input stakeholder information. Output.
- the interest-related information storage unit 200 determines whether or not the activity is registered in the achieved activity list 204 as an accomplished activity based on the activity included in the input stakeholder information. Further, the interest-related information storage unit 200 determines whether there is an unachieved activity that should be achieved before the activity. After the determination, the interest-related information storage unit 200 outputs information on the activity determined as unachieved to the main interest model generation unit 120. Furthermore, the interest-related information storage unit 200 registers the activity determined as unachieved in the achieved activity list 204 as an accomplished activity.
- the interested-related information storage unit 200 performs the above-described processing for the number of pieces of stakeholder information input from the various stakeholder information input units 300.
- the task model storage unit 210 stores the interested task model 211 and the task specifying model 212 (see FIG. 1).
- the task model storage unit 210 further stores information associated with the models generated by the interested task model generation unit 110 and the task identification model generation unit 130. Details of the information will be described later.
- the interest task model generation unit 110 inputs the interest, activity, and task information extracted from the interest related information storage unit 200 while inputting the stakeholder information from the various stakeholder information input unit 300 to the interest related information storage unit 200. Temporarily store.
- the display unit 320 displays the search result input from the task extraction unit 140. Specifically, the difference information of the extracted tasks acquired from the task extraction unit 140 and the interested task model 211 and the task identification model 212 of each stakeholder, which are search results, are displayed.
- the interested task model generation unit 110, the main interest model generation unit 120, the task specific model generation unit 130, the task extraction unit 140, the interest related information storage unit 200, various stakeholder information input units 300, and a search condition input unit 310 Is realized by, for example, a computer that operates according to a task identification program.
- a computer program storage device (not shown) stores the task identification program.
- the CPU reads the task specifying program, and according to the program, the interested task model generating unit 110, the main interested model generating unit 120, the task specifying model generating unit 130, the task extracting unit 140, the interested related information storage unit 200, various stakeholders. It operates as the information input unit 300 and the search condition input unit 310.
- the interest task model generation unit 110 the main interest model generation unit 120, the task identification model generation unit 130, the task extraction unit 140, the interest related information storage unit 200, various stakeholder information input units 300, and a search condition input unit 310 May be realized by separate hardware.
- the task model storage unit 210 is realized by a storage device such as an optical disk device, a magnetic disk device, or a memory included in the task identification device 1, for example.
- FIG. 2 is an explanatory diagram schematically showing communication between stakeholders (A and B) at a certain point in the development process.
- Stakeholders A and B basically have one roll (roll A or roll B). Stakeholders A and B may have a plurality of rolls.
- the roles A and B here are a combination of the development phase in which the stakeholders A and B are involved and the areas in charge in that phase. For example, “risk manager in planning phase”, “planning planner in planning phase”, “budget officer in design phase”, and the like.
- the concern A “risk management” shown in FIG. 2 represents the interest of the stakeholder A
- the concern B “project planning” represents the interest of the stakeholder B.
- Concern is a matter of concern in the development phase in which stakeholder A is based on role A and stakeholder B is based on role B and both are involved. Consists of things.
- the concerns here include “quality assurance”, “security assurance”, “method design”, “system integration test”, etc., in addition to “risk management” and “project planning” shown in FIG.
- the activity for the concern “risk management” is “risk management plan”.
- the activity for the concern “project planning” is “development of project execution plan”.
- An activity is an action that is taken into consideration based on the viewpoint of a stakeholder role, and is composed of one or a plurality of activities for one interest.
- the activity here refers to the development phase involving stakeholders, such as “Risk Management Plan”, “Project Execution Plan Formulation” and “Summary Design Plan” shown in FIG. 2, and the actions in that phase. Is.
- “Selection of manager” and “quantification of risk” shown in FIG. 2 represent tasks constituting the activity “risk management plan”. Further, “technological trend investigation” and “business environment analysis” shown in FIG. 2 represent tasks constituting the activity “development of project execution plan”.
- a task is a detail of an activity to an executable level. One activity is basically composed of one or more tasks. When all of the tasks that make up the activity are completed, the activity is considered accomplished. Tasks here are the activities that stakeholders are concerned about, such as “selection of manager”, “documentation of process”, “schedule adjustment”, and “estimate work amount” shown in FIG. It is an indispensable matter to do.
- the role interest correspondence list 201 is a list that defines the correspondence relationship between the role of a stakeholder and one or more interests that this role cares about from the viewpoint of the role. By comparing the role included in the stakeholder information with the role interest correspondence list 201, a plurality of interests corresponding to the role can be specified.
- the standard activity list 202 is a list that defines the correspondence between the interests and the activity groups that constitute the interests. Concerns consist of groups of activities that are needed across the development process.
- the activity groups are arranged in chronological order (t) from left to right (from left to right in FIG. 3), and it is assumed that the order to be achieved by the items on the left is earlier.
- activities constituting each interest can be identified. Activities in the standard activity list 202 are associated with the interests to which the activity belongs.
- By comparing the activity specified by the comparison with the standard activity list 202 and the activity included in the stakeholder information it is possible to specify the interest to which the activity included in the stakeholder information belongs.
- the standard task list 203 is a list that defines the correspondence between activities and tasks that have been refined to a level where the activities can be executed.
- a task can be extracted by collating the standard task list 203 based on an activity that is stakeholder information.
- FIG. 4 is an explanatory diagram showing an example of the accomplished activity list 204.
- the achieved activity list 204 is a list in which each activity is added or not added to the standard activity list 202 based on the standard activity list 202.
- the interests defined in the achieved activity list 204 and the activity group constituting the interests have the same contents as the standard activity list 202.
- the activity group constituting the interest has a time-series (t) order relationship from left to right (left side to right side in FIG. 4), and the items on the left side are achieved.
- the power order should be fast.
- FIG. 5 is an explanatory diagram showing the structure of the interested task model 211.
- an activity that refines the interest to the content of the action is a child node of the interest
- a task that refines the activity to the execution content is the child node of the activity. It is a model structured by a tree structure.
- the interest task model 211 can structure the interests, activities, and tasks recognized by each stakeholder.
- FIG. 6 is an explanatory diagram showing an example of the main concern model 213 at an arbitrary point in the development process.
- the primary concern is the concern at any point in the development process, identified based on information on activities that have been achieved.
- the main concern is an interest that includes unachieved activities that should be achieved at any point in the development process (hereinafter referred to as “required activities”) as a component.
- the main interest model 213 may be created for a plurality of main interests.
- the main interest model 213 is a model that includes one or more main interests, one or more interests corresponding to the main interests, and a required activity corresponding to each concern. By using the main concern model 213, it is possible to grasp information on achievement activities required for each stakeholder at a certain point in time.
- FIG. 7 is an explanatory diagram showing the structure of the task identification model 212.
- the task identification model 212 structures each information of the main interest in the main interest model 213, one or more interests corresponding thereto, activities corresponding to each interest, and tasks corresponding to each activity. Model.
- the task information is extracted from the interest-related information storage unit 200. By using the task identification model 212, it is possible to grasp each information of main interest, interest, activity, and task at a certain point in the development process.
- FIG. 8 is a flowchart showing an operation of identifying a task lacking from the recognition of each stakeholder in the task identification device 1 shown in FIG.
- step S101 an operator or the like inputs each stakeholder information (role and activity). Based on this, the interested task model generation unit 110 generates the interested task model 211 (see FIG. 5) based on each information extracted from the role interested correspondence list 201, the standard activity list 202, and the standard task list 203. Generate. The interested task model generation unit 110 associates the generated interest task model 211 with the role information included in the stakeholder information and stores it in the task model storage unit 210. Details of the processing in step S101 will be described later.
- the main interest model generation unit 120 Based on this, the main interest model generation unit 120 generates the main interest model 213 at a certain point in the development process based on the information in the achieved activity list 204 of the interest related information storage unit 200. Then, the main interest model generation unit 120 associates the generated main interest model 213 with the role information included in the stakeholder information, and outputs it to the task identification model generation unit 130.
- step S ⁇ b> 103 the task identification model generation unit 130 stores the main concern model 213 (see FIG. 6) input from the main interest model generation unit 120 in step S ⁇ b> 102 and the standard stored in the interest related information storage unit 200. Based on the information in the task list 203 (see FIG. 3D), a task specifying model 212 (see FIG. 7) is generated. Then, the task specification model generation unit 130 associates the generated task specification model 212 with the role information included in the stakeholder information and stores the information in the task model storage unit 210. Details of the process of generating the task specifying model 212 in steps S102 and S103 will be described later.
- step S104 the task extraction unit 140 extracts the interested task model 211 and the task identification model 212 related to each stakeholder stored in the task model storage unit 210 based on the search condition input from the search condition input unit 310. And displayed on the display unit 320.
- step S104 Necessary for consensus building and information sharing by comparing the tasks constituting the interested task model 211 of each stakeholder displayed on the display unit 320 with the tasks constituting the task specifying model 212 by the operation of an operator or the like. In addition, it is possible to identify a task whose necessity is missing from the recognition of each stakeholder. Details of the processing in step S104 will be described later.
- FIG. 9 is a flowchart showing the operation of generating the interested task model 211 of each stakeholder in the task identification device 1 (operation of step S101 in FIG. 8).
- step S201 stakeholder information is input to various stakeholder information input unit 300 by an operation of an operator or the like.
- the various stakeholder information input unit 300 outputs the input stakeholder information to the interest-related information storage unit 200.
- stakeholder information shown in FIG. 10 is input.
- the role of the stakeholder X is “risk manager in planning phase”
- the activity is “preparation for risk management”.
- the role of stakeholder Y is “planning manager in the planning phase”
- the activity is “development of an execution plan”.
- the interest-related information storage unit 200 collates with the role interest correspondence list 201 based on the role included in the input stakeholder information.
- the interest related information storage unit 200 identifies the same role as the role included in the input stakeholder information from the roles in the role interest correspondence list 201, and extracts the interest group constituting the identified role.
- the role interest correspondence list 201 has the contents shown in FIG.
- the role included in the stakeholder information is “risk manager in the planning phase”
- the interest group to be extracted is “risk management, risk assurance, information management, quality assurance, product assurance, etc.”.
- the group of interests to be extracted is “project planning, human resource management, operation management, etc.”.
- the interest-related information storage unit 200 collates each of the interest groups extracted in step S202 with the standard activity list 202 (see FIG. 13).
- the interest-related information storage unit 200 extracts an interest having the same name as each interest group extracted in step S202 from the standard activity list 202, and extracts an activity group constituting the extracted interest.
- the standard activity list 202 has the contents shown in FIG. 13 and the interest groups extracted in step S202 are “risk management” and “planning for a new system”.
- the extracted activity group is “risk management preparation ⁇ risk management plan ⁇ risk management analysis ⁇ risk management evaluation” for “risk management”.
- “New system planning” is “preparation of new system planning ⁇ planning of new system concept ⁇ approval of new system concept ⁇ evaluation of new system concept”.
- the interest-related information storage unit 200 collates the extracted activity group with the activity included in the input stakeholder information, and specifies the interest to which the activity included in the stakeholder information belongs. For example, the extracted activities and the interests they belong to ⁇ "Interest: Risk management Activity group: Risk management preparation ⁇ Risk management plan ⁇ Risk management analysis ⁇ Risk management evaluation” ⁇ "Interest: Planning new system Activity group: Preparing new system planning-> Creating new system concept-> Approving new system concept-> Evaluating new system concept” The activity included in the stakeholder information is “Preparation for risk management”. Suppose that In this case, the interest-related information storage unit 200 identifies the interest to which the activity included in the stakeholder information belongs as “risk management”.
- step S204 the interest-related information storage unit 200 collates with the standard task list 203 (see FIG. 14) based on the activity included in the input stakeholder information.
- the activity in the standard task list 203 and the same activity as the activity included in the input stakeholder information are specified, and a task group constituting the specified activity is extracted.
- the extracted task group is “identification of related departments, targeting related departments”. And documented survey results ”.
- step S205 the interest task model generation unit 110 uses the activities included in the input stakeholder information and the interests and tasks extracted by the interest related information storage unit 200 in steps S202 to S204.
- a task model 211 is generated.
- -The stakeholder X activity (see Figure 10) included in the stakeholder information is "Preparation for risk management”
- the interest extracted in steps S202 to S204 is “risk management” (see FIGS. 11 and 13)
- the task group is “identification of related departments, hearing for related departments, documentation of survey results” (see FIG.
- ⁇ "Risk management” is a node
- ⁇ "Preparation for risk management” activity which is the child node of interest
- ⁇ Activity child nodes are task groups such as “identification of related departments, hearings for related departments, and documenting survey results”.
- the interested task model generation unit 110 generates the tree-related interested task model 211.
- the interested task model generation unit 110 stores, in the task model storage unit 210, information in which the stakeholder information (role and activity) used for model generation is associated with the interested task model 211 generated in step S205. To do. For example, if the model generated by the interested task model 211 has the tree structure shown in FIG. 15A, the information to be stored includes the role “risk manager in the planning phase” and the activity “risk management” shown in FIG. Information ".
- the interested-related information storage unit 200 and the interested-task model generation unit 110 repeat the above steps S201 to S206 for the number of activities included in the stakeholder information. Then, as shown in FIG. 16, the interested task model generation unit 110 generates the interested task model 211 for the number of times of processing, and stores it in the task model storage unit 210. For example, when the present embodiment is executed for the stakeholder X and the stakeholder Y in FIG. 10, the number of activities is “preparation for risk management” and “formation of execution plan”, so steps S201 to S206 are performed. This process is executed twice. Then, a concern task model 211 shown in FIG. 15A is generated based on the activity “preparation for risk management”, and a concern task model 211 shown in FIG. 15B is generated based on the activity “formation of an execution plan”.
- FIG. 17 is a flowchart showing an operation of generating the task identification model 212 (operation of step S104 in FIG. 8) in the task identification device 1 according to the first embodiment of the present invention.
- step S301 stakeholder information is input to various stakeholder information input units 300 by an operation of an operator or the like.
- the various stakeholder information input unit 300 outputs the input stakeholder information to the interest-related information storage unit 200.
- the stakeholder information is a role and activity that each stakeholder has (see FIG. 10).
- step S302 the concern-related information storage unit 200 collates each activity included in the stakeholder information with the completed activity list 204 (see FIG. 4). Then, the interest-related information storage unit 200 specifies the same activity as the activity included in the input stakeholder information in the achieved activity list 204. At this time, the concern-related information storage unit 200 determines whether the identified activity is an accomplished activity or an unachieved activity in the achieved activity list 204. If the input activity is “achieved” as a result of the determination (YES in step S302), the concern-related information storage unit 200 moves the process to step S303. On the other hand, when the input activity is “not achieved” (NO in step S302), the concern-related information storage unit 200 moves the process to step S304.
- step S ⁇ b> 303 the interest-related information storage unit 200 selects the interests to which activities that have not been achieved and that should be achieved before the activities included in the input stakeholder information belong to the activities in the achieved activity list 204.
- the activity to be achieved first refers to an activity whose time series (t) is newer than the activity included in the stakeholder information.
- the activity list 204 in FIG. 4 indicates an activity that exists on the right side of the activity included in the input stakeholder information.
- the interest-related information storage unit 200 associates the interests to which the extracted activities belong and stakeholder information, and stores them in the main interest model generation unit 120.
- FIG. 18 is an explanatory diagram of an example of the achieved activity list 204.
- FIG. 19 is an explanatory diagram that abstractly shows a series of processes for collating the input stakeholder information with the achieved activity list 204 shown in FIG.
- verification A and verification B indicate verification of the activities of stakeholders X and Y, respectively.
- the activity of the stakeholder X is “preparation for risk management”, and “preparation for risk management” is “achieved” when collated with the achieved activity list 204 (see FIG. 18). That is, in the case of collation A, it determines with YES in step S302.
- step S303 in order to extract an activity that needs to be achieved next to “preparation for risk management”, the activity is on the right side (right side in FIG. 19) from “preparation for risk management” and is “not achieved”. Identify an activity.
- the activity “plan of risk management” corresponds to the activity on the right side of “preparation of risk management” and “not achieved”.
- the interest-related information storage unit 200 extracts the “risk management plan”, associates the “risk management” information, which is the concern to which the “risk management plan” belongs, with the stakeholder information, and generates the main interest model generation unit 120. Further, the interest-related information storage unit 200 changes “unachieved” corresponding to the activity stored in the main interest model generation unit 120 in the achieved activity list 204 to “achieved”.
- step S304 the interest-related information storage unit 200 has an activity whose time series (t) is older than the activity included in the stakeholder information, which is the basis of the determination in step S302, in the activity group of the achieved activity list 204. Determine if there is any.
- the interest-related information storage unit 200 determines whether there are any unachieved activities on the left side of the activities included in the stakeholder information. If the interest-related information storage unit 200 determines that there is an activity that needs to be achieved before the activity included in the input stakeholder information (YES in step S304), the process proceeds to step S306. . On the other hand, when the interest-related information storage unit 200 determines that there is no activity that needs to be achieved before the input stakeholder activity (NO in step S304), the process proceeds to step S305.
- step S305 the interest-related information storage unit 200 extracts the activity included in the stakeholder information that is the basis for the determination in step S302, associates the interest information to which the activity belongs with the stakeholder information, and This is stored in the thing model generation unit 120.
- the interest-related information storage unit 200 changes the corresponding part of the extracted activity in the achieved activity list 204 from “not achieved” to “achieved”.
- step S306 the interest-related information storage unit 200 performs the achieved activity shown in FIG. 4 rather than the activity included in the stakeholder information, which is the basis of determination in step S302, in the corresponding activity group in the achieved activity list 204. Activities that are on the left side in the list 204 and are not achieved are extracted. As a result of the extraction, the interest-related information storage unit 200 associates the interest to which the extracted activity belongs and the stakeholder information, and associates the activity included in the stakeholder information with the information of the interest to which the activity belongs. The information is stored in the main interest model generation unit 120.
- step S306 a specific example of the processing in step S306 will be described with reference to FIG.
- the activity of the stakeholder Y is “execution plan formulation”, and as a result of collating this activity with the achieved activity list 204, “execution plan formulation” is “not achieved”. That is, in the case of collation B in FIG. 19, YES is determined in the step S304.
- step S306 in order to determine whether or not there is an activity that needs to be achieved prior to “development of execution plan”, it is on the left side (left side in FIG. 19) of “development of execution plan” and Identify activities that are “achieved”.
- the activity “joint review of the plan” corresponds to the activity on the right side of “formation of execution plan” and “not achieved”. Therefore, the interest-related information storage unit 200 extracts information on activities of both “joint review of plan” and “formation of execution plan”, and information on “project planning” that is an interest to which these activities belong.
- the stakeholder information is associated and stored in the main concern model generation unit 120. Further, the interest-related information storage unit 200 changes “unachieved” corresponding to the activity stored in the main interest model generation unit 120 in the achieved activity list 204 to “achieved”.
- step S307 the concern-related information storage unit 200 determines whether there is unprocessed stakeholder information input to the interest-related information storage unit 200 in step S301. If there is unprocessed stakeholder information (YES in step S307), the concern-related information storage unit 200 returns the process to step S302. Then, the interested-related information storage unit 200 repeats the processes of steps S302 to S307 until the processing of all input stakeholder information is completed. On the other hand, if there is no unprocessed stakeholder information (NO in step S307), the concern-related information storage unit 200 moves the process to step S308.
- step S ⁇ b> 308 the main interest model generation unit 120 models the interest at an arbitrary point in the achieved activity list 204 acquired from the interest related information storage unit 200 and each stakeholder information.
- a model 213 (see FIG. 6) is generated.
- FIG. 20 is an explanatory diagram abstractly showing a series of processes for generating the main concern model 213 in step S308.
- the main interest model generation unit 120 inputs the generated main interest model 213 to the task specific model generation unit 130.
- the main interest model generation unit 120 displays the interest corresponding to the main interest, the activities constituting the interest, and the activities extracted in steps S301 to S307.
- the activity that constitutes the interest is the activity that needs to be achieved.
- Stakeholder information from which activities are extracted is roles and activities.
- step S309 the task identification model generation unit 130 collates the information of each activity constituting the main interest model 213 acquired from the main interest model generation unit 120 with the standard task list 203 (see FIG. 3D). .
- the task identification model generation unit 130 “plans for risk management”, which is the activity of the main interest model 213. Is input to the interest-related information storage unit 200. Then, the task identification model generation unit 130 collates the input activity “risk management plan” with the standard task list 203 shown in FIG.
- the task identification model generation unit 130 obtains “management policy definition” and “approval request for management policy”, which are information of the task that details the “risk management plan” from the interest-related information storage unit 200. "Process documentation”, “Role of process performer”, “Selection of risk manager” are extracted as tasks.
- step S310 the task identification model generation unit 130 determines whether there is activity information of the main interest model 213 that is not collated with the standard task list 203 of the interest related information storage unit 200. If there is unmatched activity information (YES in step S310), task specifying model generation unit 130 returns the process to step S309. Then, the task specifying model generation unit 130 repeats the processes of steps S309 to S310 until the matching process of the activities constituting the main concern model 213 is completed. On the other hand, if there is no unmatched activity (NO in step S310), task specifying model generating unit 130 moves the process to step S311.
- step S311 the task identification model generation unit 130 generates a task identification model 212 (see FIG. 7) using the main concern model 213 generated in steps S301 to S308 and the task extracted in step S309. . Then, the task identification model generation unit 130 associates the activity, which is the stakeholder information of the main concern model 213, with the activity of the task identification model 212.
- the task extracted in step S309 is -Tasks corresponding to the activity "Preparation of risk management”"Definition of management policy, request for approval of management policy, process documentation, division of roles of process performers, selection of risk manager", -Tasks corresponding to the activity "Formulation of execution plan”"Detailed work contents, work amount estimation, schedule, quantification of execution risk, selection of person responsible for execution, request for approval of plan", ⁇
- the task identification model generation unit 130 generates a task identification model 212 at an arbitrary point in the development process based on the main interest model 213 and information on the tasks in the standard task list 203.
- FIG. 22 shows a series of processes for generating the task identification model 212 (see FIG. 7) using the main concern model 213 (see FIG. 6) and the standard task list 203 (see FIG. 3D) in steps S309 to S311.
- FIG. 22 shows a series of processes for generating the task identification model 212 (see FIG. 7) using the main concern model 213 (see FIG. 6) and the standard task list 203 (see FIG. 3D) in steps S309 to S311.
- FIG. 23 is an explanatory diagram showing an example of the task specifying model 212.
- the task identification model 212 is ⁇ Nodes are the main concerns at any point in time, "risk management” and “project”, ⁇ The child nodes of the main concern are the activities “risk management plan”, “development of execution plan” and “joint review of plan”, The child nodes of each activity are assigned to the following tasks: “Defining management policies, requesting approval for management policies, documenting processes, assigning roles of process performers, selecting risk managers” "Detailed work details, work amount estimation, schedule, quantification of execution risk, selection of person responsible for execution, request for approval of plan”, “Definition of review methods, selection of reviewers, schedule”, This is a model structured with a tree structure.
- step S312 the task specific model generation unit 130 stores, in the task model storage unit 210, information in which the roles and activities included in the stakeholder information are associated with the task specific model 212 generated in step S311.
- FIG. 24 is a flowchart showing an operation in which the task identification device 1 according to the present embodiment searches the interested task model 211 and the task identification model 212.
- step S401 stakeholder information, which is a search condition, is input to the search condition input unit 310 through an operation of an operator or the like.
- the search condition input unit 310 passes the input stakeholder information to the task extraction unit 140. For example, when the tasks related to the stakeholder X and the stakeholder Y shown in FIG. 10 are extracted, the role “risk manager in the planning phase” and the activity “risk management plan” are input. Further, the role “planning manager in the planning phase” and the activity “form the execution plan” of the stakeholder Y are input.
- step S402 the task extraction unit 140 searches the task model storage unit 210 based on the stakeholder information input from the search condition input unit 310, and the interested task model 211 and the task specific model related to the search condition. 212 is extracted. Then, the task extraction unit 140 compares the task of the interested task model 211 with the task of the task identification model 212 based on the task identification model 212, and extracts the difference (difference task). The extraction result is a task that is missing from the concern task model 211. Then, the task extraction unit 140 outputs the extracted task information and the information on the interested task model 211 and the task identification model 212 related to the search condition to the display unit 320.
- the information of the stakeholder X and the stakeholder Y shown in FIG. 10 is input as a search condition, and the interested task model 211 shown in FIGS. 15A and 15B and the task identification shown in FIG. Assume that the model 212 is extracted.
- the task lacking from the recognition of the stakeholder X and the stakeholder Y is “definition of review method, selection of reviewer, schedule” belonging to the activity “joint review of the plan”.
- step S403 when the display unit 320 inputs from the task extraction unit 140 each of the interested task models 211 of each stakeholder, the task identification model 212, and the task that is missing from the recognition of each stakeholder, the contents are displayed. Display the information shown. An example of the display screen is shown in FIG. FIG. 25 is a diagram illustrating an example of a screen that displays the contents of the difference task.
- a task recognized by each stakeholder related to a development process at a certain arbitrary point is compared with an unachieved task of the development process at that point, and the difference is extracted. Based on this difference extraction, at any point of development, identify tasks that are necessary for consensus building and information transfer in collaborative work between stakeholders in service development and system development, and missing from the recognition of each stakeholder To do. Thereby, consensus formation and information transmission between each stakeholder can be promoted.
- task-based management is possible instead of process-based development techniques. This makes it easier to guide and manage development involving collaboration among stakeholders such as repeated development and agile development.
- a task specifying device 1a shown in FIG. 26 is a block diagram of a minimum configuration of the task specifying device 1 shown in FIG.
- the task specifying device 1a includes an interested task model generating unit 11 (corresponding to the interested task model generating unit 110 shown in FIG. 1), a task specifying model generating unit 13 (corresponding to the task specifying model generating unit 130 shown in FIG. 1), and A task extraction unit 14 (corresponding to the task extraction unit 140 shown in FIG. 1) is provided.
- the interest task model generation unit 11 generates an interest task model in which the relationship between the activity included in the stakeholder information indicating the action content of the stakeholder, the interest to which the activity belongs, and the task that details the activity is structured. Generate.
- the task specific model generation unit 13 structures the relationship between the interests required at an arbitrary point in the development process, the activities to be achieved corresponding to the required interests, and the tasks that detail the activities. Generate a task specific model.
- the task extraction unit 14 compares the task of the interested task model with the task of the task specific model and extracts a difference.
- a task recognized by each stakeholder in a development process at a certain arbitrary point is compared with an unachieved task in the development process at that point, and the difference is extracted. Based on this difference extraction, at any point of development, identify tasks that are necessary for consensus building and information transfer in collaborative work between stakeholders in service development and system development, and missing from the recognition of each stakeholder To do. Thereby, consensus formation and information transmission between each stakeholder can be promoted.
- this embodiment further A search condition input unit (corresponding to the search condition input unit 310 shown in FIG. 1); A task model storage unit (corresponding to the task model storage unit 210 shown in FIG. 1) for storing the interested task model and the task identification model; The task extraction unit 14 may extract a task difference between the interested task model and the task identification model searched from the task model storage unit based on the search condition input to the search condition input unit.
- the search target can be arbitrarily changed by an operation of an operator or the like, and a necessary task can be more accurately specified by consensus formation or information transmission in a collaborative work between stakeholders. .
- the present embodiment further includes a display unit (corresponding to the display unit 320 shown in FIG. 1) that displays information indicating a task difference between the interested task model extracted by the task extracting unit 14 and the task specifying model. May be provided.
- a display unit corresponding to the display unit 320 shown in FIG. 1 that displays information indicating a task difference between the interested task model extracted by the task extracting unit 14 and the task specifying model. May be provided.
- a difference between a task recognized by each stakeholder related to a development process at an arbitrary point in time and an unachieved task of the development process at that point is recognized via a display device such as a display.
- a display device such as a display.
- FIG. 27 is a block diagram showing a modification example of the task identification device according to the second exemplary embodiment of the present invention.
- a modification example of the task identification device of this embodiment is Interest task model generation unit 11 (corresponding to the interest task model generation unit 110), Main interest model generation unit 12 (corresponding to main interest model generation unit 120), Task specific model generation unit 13 (corresponding to task specific model generation unit 130) Interest-related information storage unit 20 (corresponding to interest-related information storage unit 200), task extraction unit 14 (corresponding to task extraction unit 140), Is provided.
- the interest task model generation unit 11 generates a model in which the relationship between the activity indicating the stakeholder's action content, the interest to which the activity belongs, and the task that details the activity to the execution content is structured.
- the main interest model generation unit 12 generates an interest task model in which the interests constituting the main interest and the activities constituting the interests are structured at an arbitrary point in the development process.
- the task identification model generation unit 13 is structured to identify an interest that constitutes a main interest, an activity that constitutes the concern, and a task that details the activity at an arbitrary point in the development process. Is generated.
- the interested-related information storage unit 20 holds information necessary for model generation in the interested task model generation unit 11, the main interest model generation unit 12, and the task specific model generation unit 13.
- the task extraction unit 14 compares the task of the interested task model of each stakeholder with the task of the task specific model, and extracts a difference.
- the task recognized by each stakeholder involved in the development process at an arbitrary development point is compared with the unachieved task of the development process at that point, and the difference is extracted. Based on this difference extraction, at any point of development, identify tasks that are necessary for consensus building and information transfer in collaborative work between stakeholders in service development and system development, and missing from the recognition of each stakeholder can do. Thereby, consensus formation and information transmission between each stakeholder can be promoted.
- the modified example of this embodiment is further
- the interest related information storage unit 20 includes a role interest correspondence list (corresponding to the role interest correspondence list 201 shown in FIG. 1), a standard activity list (corresponding to the standard activity list 202), and a standard task list (standard task list 203). Equivalent) and an accomplished activity list (equivalent to the accomplished activity list 204),
- the interest task model generation unit 11 generates an interest task model based on the role interest correspondence list, the standard activity list, and the standard task list based on the roles and activities included in the stakeholder information
- the main interest model generation unit 12 generates a main interest model based on the achieved activity list
- the task specific model generation unit 13 may generate a task specific model based on the main concern model at an arbitrary point in the development process and the standard task list.
- the present invention can be applied to various types of service development or system development. Can be applied.
- the modified example of this embodiment is further A search condition input unit (corresponding to the search condition input unit 310 shown in FIG. 1); A task model storage unit (corresponding to the task model storage unit 210) for storing the interested task model and the task identification model;
- the task extraction unit 14 may extract a task difference between the interested task model and the task identification model searched from the task model storage unit based on the search condition input to the search condition input unit.
- the modified example of the present embodiment further includes a display unit (corresponding to the display unit 320 shown in FIG. 1) that displays information indicating a task difference between the interested task model extracted by the task extracting unit 14 and the task specifying model. You may have.
- a display unit corresponding to the display unit 320 shown in FIG. 1 that displays information indicating a task difference between the interested task model extracted by the task extracting unit 14 and the task specifying model. You may have.
- a difference between a task recognized by each stakeholder related to a development process at an arbitrary point in time and an unachieved task of the development process at that point is recognized via a display device such as a display. .
- a display device such as a display.
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Operations Research (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Educational Administration (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
Description
ステークホルダの行動内容を示すステークホルダ情報に含まれるアクティビティと、当該アクティビティが属する関心事と、当該アクティビティを詳細化したタスクとの関係を構造化した関心事タスクモデルを生成する関心事タスクモデル生成手段と、
開発プロセスの任意の時点において必要となる関心事と、当該必要となる関心事に対応する達成すべきアクティビティと、当該アクティビティを詳細化したタスクとの関係を構造化したタスク特定モデルを生成するタスク特定モデル生成手段と、
関心事タスクモデルのタスクと、タスク特定モデルのタスクとを比較し、差分を抽出するタスク抽出手段と
を備えるタスク特定装置である。
ステークホルダの行動内容を示すステークホルダ情報に含まれるアクティビティと、当該アクティビティが属する関心事と、当該アクティビティを詳細化したタスクとの関係を構造化した関心事タスクモデルを生成し、
開発プロセスの任意の時点において必要となる関心事と、当該必要となる関心事に対応する達成すべきアクティビティと、当該アクティビティを詳細化したタスクとの関係を構造化したタスク特定モデルを生成し、
関心事タスクモデルのタスクと、タスク特定モデルのタスクとを比較し、差分を抽出するタスク特定方法である。
コンピュータに、
ステークホルダの行動内容を示すステークホルダ情報に含まれるアクティビティと、当該アクティビティが属する関心事と、当該アクティビティを詳細化したタスクとの関係を構造化した関心事タスクモデルを生成する処理と、
開発プロセスの任意の時点において必要となる関心事と、当該必要となる関心事に対応する達成すべきアクティビティと、当該アクティビティを詳細化したタスクとの関係を構造化したタスク特定モデルを生成する処理と、
関心事タスクモデルのタスクと、タスク特定モデルのタスクとを比較し、差分を抽出する処理
とを実行させるためのタスク特定プログラムを格納する記録媒体である。
以下、本発明の第1の実施形態を、図面を参照して説明する。図1は、本発明の第1の実施形態に係るタスク特定装置1の構成を示すブロック図である。
・「関心事:リスク管理
アクティビティ群:リスク管理の準備→リスク管理の計画→リスク管理の分析→リスク管理の評価」
・「関心事:新システムの企画
アクティビティ群:新システム企画の準備→新システム構想の立案→新システム構想の承認→新システム構想の評価」
であり、ステークホルダ情報に含まれるアクティビティが
・「リスク管理の準備」
であるとする。この場合、関心事関連情報保管部200は、ステークホルダ情報に含まれるアクティビティが属する関心事は「リスク管理」と特定する。
・ステークホルダ情報に含まれるステークホルダXのアクティビティ(図10参照)が「リスク管理の準備」、
・ステップS202~ステップS204で抽出された関心事が「リスク管理」(図11および図13参照)、
・タスク群が「関連部門の識別、関連部門を対象としたヒヤリング、調査結果の文書化」(図14参照)、
であるとする。この場合、
・関心事である「リスク管理」をノード、
・関心事の子ノードをアクティビティである「リスク管理の準備」、
・アクティビティの子ノードをタスク群である「関連部門の識別、関連部門を対象としたヒヤリング、調査結果の文書化」、
とした木構造の関心事タスクモデル211を、図15Aに示すように、関心事タスクモデル生成部110は生成する。
・アクティビティ「リスク管理の準備」に対応するタスク「管理方針の定義、管理方針への承認依頼、プロセスの文書化、プロセス実施者の役割分担、リスク管理責任者の選定」、
・アクティビティ「実行計画の策定」に対応するタスク「作業内容の詳細化、作業量の見積もり、スケジュール、実行リスクの定量化、実行責任者の選定、計画書への承認依頼」、
・アクティビティ「計画の共同レビュー」に対応するタスク「レビュー方法の定義、レビュー者の選定、スケジュール」、
である。タスク特定モデル生成部130は、主関心事モデル213と標準タスクリスト203内のタスクの情報に基づき、開発プロセスの任意の時点におけるタスク特定モデル212を生成する。図22は、ステップS309~S311における、主関心事モデル213(図6参照)と標準タスクリスト203(図3D参照)を用いてタスク特定モデル212(図7参照)を生成する処理の一連の流れを抽象的に表した説明図である。
・ノードを、任意の時点における主関心事である「リスク管理」と「プロジェクト」、
・主関心事の子ノードを、アクティビティ「リスク管理計画」、「実行計画の策定」および「計画の共同レビュー」、
・各アクティビティの子ノードを、以下のタスク
「管理方針の定義、管理方針への承認依頼、プロセスの文書化、プロセス実施者の役割分担、リスク管理責任者の選定」、
「作業内容の詳細化、作業量の見積もり、スケジュール、実行リスクの定量化、実行責任者の選定、計画書への承認依頼」、
「レビュー方法の定義、レビュー者の選定、スケジュール」、
とする木構造で構造化したモデルである。
次に、本発明の第2の実施形態に係るタスク特定装置1aについて説明する。図26に示すタスク特定装置1aは、図1に示すタスク特定装置1の最小構成のブロック図である。タスク特定装置1aは、関心事タスクモデル生成部11(図1に示す関心事タスクモデル生成部110に相当)、タスク特定モデル生成部13(図1に示すタスク特定モデル生成部130に相当)およびタスク抽出部14(図1に示すタスク抽出部140に相当)を備える。
検索条件入力部(図1に示す検索条件入力部310に相当)と、
関心事タスクモデルとタスク特定モデルとを記憶するタスクモデル記憶部(図1に示すタスクモデル記憶部210に相当)とを備え、
タスク抽出部14は、検索条件入力部に入力された検索条件を基にタスクモデル記憶部から検索した、関心事タスクモデルとタスク特定モデルとのタスクの差分を抽出してもよい。
関心事タスクモデル生成部11(関心事タスクモデル生成部110に相当)、
主関心事モデル生成部12(主関心事モデル生成部120に相当)、
タスク特定モデル生成部13(タスク特定モデル生成部130に相当)
関心事関連情報保管部20(関心事関連情報保管部200に相当)、および
タスク抽出部14(タスク抽出部140に相当)、
を備える。
関心事関連情報保管部20は、ロール関心事対応リスト(図1に示すロール関心事対応リスト201に相当)、標準アクティビティリスト(標準アクティビティリスト202に相当)、標準タスクリスト(標準タスクリスト203に相当)および、達成済アクティビティリスト(達成済アクティビティリスト204に相当)とを保持し、
関心事タスクモデル生成部11は、ステークホルダ情報に含まれるロールとアクティビティに基づいて、ロール関心事対応リストと、標準アクティビティリストと、標準タスクリストと、をもとに関心事タスクモデルを生成し、
主関心事モデル生成部12は、達成済アクティビティリストをもとに主関心事モデルを生成し、
タスク特定モデル生成部13は、開発プロセスの任意の時点における主関心事モデルと、標準タスクリストとをもとに、タスク特定モデルを生成してもよい。
検索条件入力部(図1に示す検索条件入力部310に相当)と、
関心事タスクモデルとタスク特定モデルとを記憶するタスクモデル記憶部(タスクモデル記憶部210に相当)とを備え、
タスク抽出部14は、検索条件入力部に入力された検索条件をもとにタスクモデル記憶部から検索した、関心事タスクモデルとタスク特定モデルとのタスクの差分を抽出してもよい。
11、110 関心事タスクモデル生成部
12、120 主関心事モデル生成部
13、130 タスク特定モデル生成部
14、140 タスク抽出部
20、200 関心事関連情報保管部
201 ロール関心事対応リスト
202 標準アクティビティリスト
203 標準タスクリスト
204 達成済アクティビティリスト
210 タスクモデル記憶部
211 関心事タスクモデル
212 タスク特定モデル
213 主関心事モデル
300 各種ステークホルダ情報入力部
310 検索条件入力部
320 表示部
Claims (7)
- ステークホルダの行動内容を示すステークホルダ情報に含まれるアクティビティと、当該アクティビティが属する関心事と、当該アクティビティを詳細化したタスクとの関係を構造化した関心事タスクモデルを生成する関心事タスクモデル生成手段と、
開発プロセスの任意の時点において必要となる関心事と、当該必要となる関心事に対応する達成すべきアクティビティと、当該アクティビティを詳細化したタスクとの関係を構造化したタスク特定モデルを生成するタスク特定モデル生成手段と、
前記関心事タスクモデルのタスクと、前記タスク特定モデルのタスクとを比較し、差分を抽出するタスク抽出手段とを備えた
タスク特定装置。 - 前記関心事タスクモデル生成手段が生成する前記関心事タスクモデル内のアクティビティは、当該アクティビティの実行内容を詳細化したタスクが含められ、
前記タスク特定モデル生成手段が生成する前記タスク特定モデルには、一つ以上の前記必要となる関心事から構成される関心事群の上位概念である主関心事が含められ、
前記タスク抽出手段は、複数の前記ステークホルダに対応する前記関心事タスクモデルのタスクと、前記タスク特定モデルのタスクとを比較し、差分を抽出し、
更に、
前記主関心事と、前記主関心事に関する1つ以上の前記必要となる関心事と、当該必要となる関心事を構成するアクティビティを構造化した主関心事モデルを生成する主関心事モデル生成手段と、
前記関心事タスクモデル生成手段、前記主関心事モデル生成手段および前記タスク特定モデル生成手段におけるモデル生成に必要な情報を保持する関心事関連情報保管手段と、
を備える請求項1に記載のタスク特定装置。 - 前記関心事関連情報保管手段は、ロール関心事対応リスト、標準アクティビティリスト、標準タスクリストおよび達成済アクティビティリストを保持し、
前記関心事タスクモデル生成手段は、前記ステークホルダ情報に含まれるロールと前記アクティビティを用いて、前記ロール関心事対応リスト、前記標準アクティビティリストおよび前記標準タスクリストから前記関心事タスクモデルを生成し、
前記主関心事モデル生成手段は、前記達成済アクティビティリストを基に前記主関心事モデルを生成し、
前記タスク特定モデル生成手段は、開発プロセスの任意の時点における前記主関心事モデルと、前記標準タスクリストとを基に、前記タスク特定モデルを生成する
請求項1又は請求項2に記載のタスク特定装置。 - 検索条件入力手段と、
前記関心事タスクモデルと前記タスク特定モデルとを記憶するタスクモデル記憶手段とを備え、
前記タスク抽出手段は、前記検索条件入力手段に入力された検索条件をもとに前記タスクモデル記憶手段から検索した、前記関心事タスクモデルと前記タスク特定モデルとのタスクの差分を抽出する
請求項1から請求項3のうちのいずれか1項に記載のタスク特定装置。 - 前記タスク抽出手段が抽出した前記関心事タスクモデルと前記タスク特定モデルとのタスクの差分を示す情報を表示する表示手段、
を更に備える、請求項1乃至請求項4のいずれか1項に記載のタスク特定装置。 - ステークホルダの行動内容を示すステークホルダ情報に含まれるアクティビティと、当該アクティビティが属する関心事と、当該アクティビティを詳細化したタスクとの関係を構造化した関心事タスクモデルを生成し、
開発プロセスの任意の時点において必要となる関心事と、当該必要となる関心事に対応する達成すべきアクティビティと、当該アクティビティを詳細化したタスクとの関係を構造化したタスク特定モデルを生成し、
前記関心事タスクモデルのタスクと、前記タスク特定モデルのタスクとを比較し、差分を抽出する
タスク特定方法。 - コンピュータに、
ステークホルダの行動内容を示すステークホルダ情報に含まれるアクティビティと、当該アクティビティが属する関心事と、当該アクティビティを詳細化したタスクとの関係を構造化した関心事タスクモデルを生成する処理と、
開発プロセスの任意の時点において必要となる関心事と、当該必要となる関心事に対応する達成すべきアクティビティと、当該アクティビティを詳細化したタスクとの関係を構造化したタスク特定モデルを生成する処理と、
前記関心事タスクモデルのタスクと、前記タスク特定モデルのタスクとを比較し、差分を抽出する処理
とを実行させるためのタスク特定プログラムを格納する記録媒体。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016514701A JPWO2015162879A1 (ja) | 2014-04-21 | 2015-04-16 | タスク特定装置、タスク特定方法およびタスク特定プログラム |
US15/129,458 US20170103357A1 (en) | 2014-04-21 | 2015-04-16 | Task-specifying device, task-specifying method, and recording medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014-087444 | 2014-04-21 | ||
JP2014087444 | 2014-04-21 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015162879A1 true WO2015162879A1 (ja) | 2015-10-29 |
Family
ID=54332058
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/002094 WO2015162879A1 (ja) | 2014-04-21 | 2015-04-16 | タスク特定装置、タスク特定方法および記録媒体 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20170103357A1 (ja) |
JP (1) | JPWO2015162879A1 (ja) |
WO (1) | WO2015162879A1 (ja) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6701160B2 (ja) * | 2017-12-28 | 2020-05-27 | 株式会社日立製作所 | プロジェクト支援システム及び方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH09259181A (ja) * | 1996-03-19 | 1997-10-03 | Hitachi Ltd | ワークフロー管理システム |
JP2003242318A (ja) * | 2002-02-13 | 2003-08-29 | Ricoh Co Ltd | マネージメントコンサルティング方法、マネージメントコンサルティング支援システム、そのサーバ、クライアント端末、そのプログラム、及びそのプログラムを記録した記録媒体 |
JP2008217480A (ja) * | 2007-03-05 | 2008-09-18 | Fujitsu Ltd | 要件確認支援プログラム、要件確認支援方法、及び要件確認支援装置 |
JP2012238069A (ja) * | 2011-05-10 | 2012-12-06 | Mitsubishi Electric Corp | 進捗管理装置、進捗管理システム、進捗管理方法および進捗管理プログラム |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB9322137D0 (en) * | 1993-10-27 | 1993-12-15 | Logical Water Limited | A system and method for defining a process structure for performing a task |
AUPN773496A0 (en) * | 1996-01-25 | 1996-02-15 | Task Solutions Pty Ltd | Task management system |
US7330822B1 (en) * | 2001-05-29 | 2008-02-12 | Oracle International Corporation | Methods and systems for managing hierarchically organized and interdependent tasks and issues |
US7590971B2 (en) * | 2003-08-01 | 2009-09-15 | Idx Investment Corporation | Enterprise task manager |
US7848942B2 (en) * | 2004-12-28 | 2010-12-07 | Sap Aktiengesellschaft | Distribution of integrated business process models |
US7739137B2 (en) * | 2005-02-04 | 2010-06-15 | Suresh Jagtiani | Project management software |
US8027861B2 (en) * | 2006-06-05 | 2011-09-27 | Lee Page Brintle | Systems and methods for shared task management |
US7870499B2 (en) * | 2007-03-16 | 2011-01-11 | Sap Ag | System for composing software appliances using user task models |
EP2012261A1 (en) * | 2007-06-13 | 2009-01-07 | Sap Ag | Processing and exchanging data of collaborative tasks |
US8549520B2 (en) * | 2007-07-31 | 2013-10-01 | Sap Ag | Distributed task handling |
JP5270209B2 (ja) * | 2008-03-31 | 2013-08-21 | インターナショナル・ビジネス・マシーンズ・コーポレーション | 複数のタスクの進捗を管理するためのコンピュータ・システム、並びにその方法及びコンピュータ・プログラム |
US8645178B2 (en) * | 2011-04-28 | 2014-02-04 | Accenture Global Services Limited | Task management for a plurality of team members |
CN110264074B (zh) * | 2014-03-19 | 2023-07-11 | 日产自动车株式会社 | 电动汽车共享确定方法以及电动汽车共享系统 |
-
2015
- 2015-04-16 US US15/129,458 patent/US20170103357A1/en not_active Abandoned
- 2015-04-16 WO PCT/JP2015/002094 patent/WO2015162879A1/ja active Application Filing
- 2015-04-16 JP JP2016514701A patent/JPWO2015162879A1/ja active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH09259181A (ja) * | 1996-03-19 | 1997-10-03 | Hitachi Ltd | ワークフロー管理システム |
JP2003242318A (ja) * | 2002-02-13 | 2003-08-29 | Ricoh Co Ltd | マネージメントコンサルティング方法、マネージメントコンサルティング支援システム、そのサーバ、クライアント端末、そのプログラム、及びそのプログラムを記録した記録媒体 |
JP2008217480A (ja) * | 2007-03-05 | 2008-09-18 | Fujitsu Ltd | 要件確認支援プログラム、要件確認支援方法、及び要件確認支援装置 |
JP2012238069A (ja) * | 2011-05-10 | 2012-12-06 | Mitsubishi Electric Corp | 進捗管理装置、進捗管理システム、進捗管理方法および進捗管理プログラム |
Also Published As
Publication number | Publication date |
---|---|
JPWO2015162879A1 (ja) | 2017-04-13 |
US20170103357A1 (en) | 2017-04-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
El Mokadem | The classification of supplier selection criteria with respect to lean or agile manufacturing strategies | |
Houy et al. | BPM-in-the-Large–Towards a higher level of abstraction in Business Process Management | |
Aguirre et al. | Combination of process mining and simulation techniques for business process redesign: a methodological approach | |
US20110313932A1 (en) | Model-based project network | |
Erich | DevOps is simply interaction between development and operations | |
Wiesner et al. | Requirements engineering | |
Adler et al. | Improving risk management: moving from risk elimination to risk avoidance | |
Brillinger | Mapping business model risk factors | |
Cull et al. | A hybrid approach to workflow modelling | |
Marques et al. | A Survey of Failures in the Software Development Process. | |
Hernandez-Resendiz et al. | Merging event logs for inter-organizational process mining | |
Kravchenko et al. | A brief IT-project risk assessment procedure for business data warehouse development | |
Elzamly et al. | Classification and identification of risk management techniques for mitigating risks with factor analysis technique in software risk management | |
Johannsen et al. | A Six Sigma approach for integrated solutions | |
Avdoshin et al. | Software risk management: using the automated tools | |
Mechrez et al. | Modeling design-time variability in business processes: existing support and deficiencies | |
Leite et al. | Ownership relevance in aspect-oriented business process models | |
Astromskis et al. | Continuous CMMI assessment using non-invasive measurement and process mining | |
WO2015162879A1 (ja) | タスク特定装置、タスク特定方法および記録媒体 | |
Kang et al. | Discrete event simulation to reduce the effect of uncertainties on project planning | |
Delias et al. | Business process analytics: a dedicated methodology through a case study | |
García et al. | A discrete-event simulation metamodel for obtaining simulation models from business process models | |
Araújo et al. | Selecting a notation to modeling business process: a systematic literature review of technics and tools | |
Friedland et al. | Conducting a model based systems engineering tool trade study using a systems engineering approach | |
das Chagas Santos et al. | Lean Office and Digital Transformation: A Case Study in a Services Company |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15783625 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016514701 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15129458 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15783625 Country of ref document: EP Kind code of ref document: A1 |