JP2010256949A - Stakeholder extraction/management device, method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce an extraction failure of a stakeholder, and to present the stakeholder to be checked for specification change. <P>SOLUTION: A stakeholder extraction/management device 100 includes: a stakeholder model generation section 110 which structures organization information; a goal model generation section 120 which structures a goal; a business process model generation section 130 which connects a business process with the goal and the stakeholder of a customer and keeps them; a development process model generation section 140 which connects a development process with the stakeholder of a system and keeps them; a various pieces of stakeholder information storage section 150 which keeps stakeholder information; a retrieval section 160 which retrieves the stakeholder in connection with the goal based on a retrieval condition; and an indirect stakeholder extraction processing section 170 which indirectly extracts the stakeholder in connection with the goal through decision making, review, etc. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a stakeholder extraction / management apparatus, method, and stakeholder extraction / management program, and more particularly to a stakeholder extraction / management apparatus, method, and stakeholder extraction / management program capable of managing a customer strategy in association with a stakeholder.

  In this specification, “customer” means “customer for a vendor who provides information systems and services”, and specifically refers to companies, government offices, local governments, and the like.

  Conventionally, system vendor system development has been based on system proposals for Request for Proposal (RFP) after requirements have been established. Therefore, customer stakeholder extraction and requirement definition were the role of the customer's information system department. However, in order to discover issues from the customer's strategy and make proposals for introducing IT, it is necessary to grasp the customer's stakeholders and extract the requirements without omission.

  In the development of information systems and services, technologies that support customer strategy development and requirement definition are known.

  In Patent Document 1, the stakeholders related to the information system are classified for each stakeholder type based on the related information that characterizes the stakeholder including the stakeholder's background and the announcement document, and by presenting the stakeholder type necessary for the requirement definition, Supports requirements confirmation.

  In Patent Document 2, by clarifying management issues of strategic customers who are partners of providing information systems, value information to be provided, business processes that create provided value, and information / IT requirements that support business processes, Supports strategic planning to maximize the value provided to the end customer, the strategic customer.

  In Patent Document 3, information representing the correspondence between each object in a project and its related stakeholder is stored in a stakeholder database. When a change occurs in the object, the database is searched to find all related stakeholders. Extracting.

JP 2008-217480 A JP 2006-209444 A Japanese Patent Laid-Open No. 2004-240486

  In system and service development, when system integrators provide a system to achieve customer's strategic goals and improve customer value, fully understand stakeholders (stakeholders) and make requests without omissions. It is important to extract. However, in recent years, the purpose of systemization has become diversified and complicated, and customers themselves have not been able to grasp the purpose and stakeholder of the system. As a result, new stakeholders have appeared later, and demands have changed frequently.

  For this reason, when acquiring requests from customers, consensus building with customers, and reviewing deliverables, it is a problem that the stakeholders are not sufficiently grasped.

  In patent document 1, the stakeholder type required for the requirement confirmation can be presented at the stage of completing the requirement definition. However, in Patent Document 1, a necessary stakeholder cannot be extracted in the first place when acquiring a request.

  In Patent Document 2, stakeholders are captured in a large framework of a strategic customer that provides a system and a final customer that is a customer of the strategic customer at the stage of supporting the customer's strategy formulation. However, Patent Document 2 cannot extract and manage stakeholders related to business processes and requirements of strategic customers.

  In Patent Document 3, when a change occurs in an object, a stakeholder database is searched to extract all related stakeholders. However, in Patent Document 3, customer strategies and requirements are not managed in association with stakeholders.

  In this specification, “goal” means an item to be achieved in the system to be developed. Specifically, a goal means a strategic goal, a measure to realize this strategic goal, a business requirement necessary to execute this measure, and a system requirement necessary to systematize this business requirement. To do.

  An object of the present invention is to provide a stakeholder extraction / management apparatus, method, and program capable of reducing stakeholder extraction omission and presenting a stakeholder whose specification change should be confirmed.

  The stakeholder extraction / management apparatus of the present invention is a stakeholder model generation unit that models a stakeholder and manages the role of an organization, a goal model generation unit that structures and manages a customer goal, a customer business process model and a goal, A business process model generation unit that associates and manages a stakeholder, a development process model generation unit that associates and manages a system development process and a stakeholder, a stakeholder model generation unit, a goal model generation unit, a business process model generation unit, and a development Various stakeholder information storage units for storing stakeholder information structured by the process model generation unit, a search unit for searching related stakeholders from various stakeholder information storage units using the input goal as a search condition, Using the information stored in Kuhoruda information storage unit comprises an indirect stakeholder extraction processing unit which extracts the stakeholders involved indirectly to the goal, the.

  The effect of the present invention is to reduce the stakeholder extraction omission and to present a stakeholder whose specification change should be confirmed.

It is a block diagram which shows the structure of the stakeholder extraction / management apparatus which concerns on one embodiment of this invention. It is a figure which shows the relationship between the data of various stakeholder information. It is a flowchart which shows the operation | movement which extracts a stakeholder directly in the stakeholder extraction and management apparatus shown in FIG. It is a flowchart which shows the operation | movement which extracts the indirect stakeholder in the stakeholder extraction and management apparatus shown in FIG. It is a flowchart which shows the operation | movement which searches the stakeholder relevant to the strategy and requirement (goal) in the stakeholder extraction / management apparatus shown in FIG. It is a figure which shows an example of a stakeholder model. It is a figure which shows an example of a goal model. It is a figure which shows an example of a business process model. It is a figure which shows an example of a development process model. It is a figure which shows a response | compatibility of the role of a customer organization, and four viewpoints of BSC. It is the figure which showed the example of the item put into a map. It is a figure which shows an example of a financial viewpoint map. It is a figure which shows an example of a BSC strategy score card. It is a figure which shows the example of preparation of the business goal relevance map in a goal model production | generation part. It is a figure which shows the example which produces a business target adaptability map with respect to each stakeholder in a stakeholder model production | generation part. It is a figure which shows the example of calculation of a relevance degree. It is a figure which shows an example which input "goal" as a search condition from a search condition input part. It is a figure which shows an example which produces | generates a development process model in a development process model production | generation part. It is a figure which shows an example which produces | generates a business process model in a business process model production | generation part.

  Next, embodiments for carrying out the invention will be described in detail with reference to the drawings.

  Referring to FIG. 1, a stakeholder extraction / management apparatus 100 according to an embodiment of the present invention includes a stakeholder model generation unit 110, a goal model generation unit 120, a business process model generation unit 130, and a development process model generation unit. 140, various stakeholder information storage unit 150, search unit 160, and indirect stakeholder extraction processing unit 170.

  The information input sources of the stakeholder model generation unit 110, the goal model generation unit 120, the business process model generation unit 130, and the development process model generation unit 140 are the various information input units 200.

  The stakeholder model generation unit 110 forms a tree-structured organization chart as shown in FIG. 6 from the inputted organization information (name, role, association between organizations) and stores it in various stakeholder information storage units 150. The stakeholder model generation unit 110 structures customer organization information in a tree structure, and weights items that each organization places importance on. The stakeholder model generation unit 110 models a stakeholder and manages the role of the organization. The stakeholder model generation unit 110 holds the organization name of the customer, the role of the organization, and the relationship between the organizations, and creates a business goal fitness map for each organization as will be described later.

  The goal model generation unit 120 forms a tree-shaped goal model as shown in FIG. 7 and stores it in various stakeholder information storage units 150. As shown in FIG. 7, the goal model generation unit 120 takes a customer's strategic goal as a root, measures for realizing the strategic goal as child nodes of the strategic goal, and business requirements necessary for executing the measure System requirements necessary for systematizing child nodes and business requirements are child nodes of business requirements. In addition, the goal model generation unit 120 manages the strategy (goal) by dividing it into four viewpoints of Balanced Scorecard (BSC). The goal model generation unit 120 structures customer strategy / requirement (goal) information in a tree structure, and weights elements important for each strategy (goal). The goal model generation unit 120 structures and manages customers' strategic goals and requirements (goals). The goal model generation unit 120 manages the customer's strategy (goal) by dividing it into four viewpoints of Balanced Scorecard (BSC), and generates a business target fitness map for each strategy (goal) as will be described later.

  The business process model generation unit 130 configures a business process model as shown in FIG. 8 in which the business process is a single block and is connected so that the execution order and branching can be understood. The business process model generation unit 130 sets a relationship between a business process and a stakeholder and a relationship between a business process and a strategy (goal) and stores them in various stakeholder information storage units 150. Here, “business process” means a task of a customer's business such as “confirm inventory” and “deliver goods”. The business process model generation unit 130 structures the business process with a graph structure and sets a relationship with a stakeholder and a strategy / requirement (goal). The business process model generation unit 130 associates and manages a customer's business process model, a strategy (goal), and a stakeholder.

  The development process model generation unit 140 configures a development process model as shown in FIG. 9 in which blocks in which system development processes and stakeholder responsible for the processes are set are connected in a list form, and the various stakeholder information storage unit 150 stores the development process model. Store. Here, “development process” means each phase such as “requirement definition” and “system design” of system development. The development process model generation unit 140 sets a development process and stakeholders involved in the development process as a set, and structures the list structure. The development process model generation unit 140 associates and manages system development processes and stakeholders.

  The various stakeholder information storage unit 150 stores information structured by the stakeholder model generation unit 110, the goal model generation unit 120, the business process model generation unit 130, and the development process model generation unit 140. The various stakeholder information storage unit 150 stores stakeholder information structured by the stakeholder model generation unit 110, the goal model generation unit 120, the business process model generation unit 130, and the development process model generation unit 140. The various stakeholder information storage unit 150 stores stakeholder model information 151, goal model information 152, business process model information 153, and development process model information 154. The various stakeholder information storage unit 150 also stores other related information.

  The search unit 160 searches information stored in the various stakeholder information storage units 150 based on the search conditions input from the search condition input unit 210 and displays the results on the display unit 220. The search unit 160 searches for a stakeholder related to a strategy / requirement (goal) based on the input search condition. The search unit 160 searches for related stakeholders using the input strategy / requirement (goal) as a search condition.

  The indirect stakeholder extraction processing unit 170 extracts stakeholders that are indirectly related to the customer's strategy (goal) based on the stakeholder information and the strategy (goal) information stored in the various stakeholder information storage units 150, and various stakeholder information. Store in the storage unit 150. The indirect stakeholder extraction processing unit 170 performs a process of extracting a stakeholder involved in decision making and review of a strategy and requirements (goals) based on information weighted by the stakeholder model generation unit 110 and the goal model generation unit 120. The indirect stakeholder extraction processing unit 170 uses the information stored in the various stakeholder information storage units 150 to extract stakeholders that are indirectly related to the strategy / requirements (goals). The indirect stakeholder extraction processing unit 170 calculates the degree of association between the strategy / requirement (goal) and the stakeholder based on the information created by the stakeholder model generation unit 110 and the goal model generation unit 120, as described later. Present in order from the stakeholder with the highest relevance to the requirement (goal).

  FIG. 2 is a diagram showing the relationship among the business process model information 153, the stakeholder model information 151, the development process model information 154, and the goal model information 152.

  The stakeholder model information 151 is composed of an organization chart of a tree structure from inputted organization information and related information between organizations. The organization information includes a stakeholder name, a role of the stakeholder, and a business goal conformity map. The stakeholder name must be set for all organizations, but the role and the business goal fitness map need not be set.

  The goal model information 152 constitutes a tree-shaped goal model from the input goal information and the related information between the goals. The goal information includes a goal name, four viewpoints of the BSC, and a business target suitability map. The four perspectives of BSC are one of “finance perspective”, “customer perspective”, “business process perspective”, and “learning and growth perspective”. When the top goal perspective is set, the perspectives of the lower goals are all the same.

  The business process model information 153 includes a business process model having a directed graph structure from the input business process information and related information between business processes. The business process information includes a business process name, a stakeholder name related to the business process, and a goal name related to the business process.

  The development process model information 154 comprises a development process model having a list structure from the input development process information. Development process information consists of a development process name and a related stakeholder name.

  The business process model generation unit 130 constitutes business process model information 153, and stores goal / business process related information and business process / stakeholder related information in various stakeholder information storage units 150.

  The development process model generation unit 140 constitutes development process model information 154 and stores information related to the development process and stakeholders in various stakeholder information storage units 150.

  Next, the operation of the stakeholder extraction / management apparatus 100 will be described with reference to the flowcharts of FIGS.

  First, with reference to FIG. 3, a method (operation) for extracting stakeholders directly related to system development and business processes (hereinafter referred to as “direct stakeholders”) will be described.

  The goal model generation unit 120 creates a goal model as shown in FIG. 7 based on the information input from the various information input units 200 (step S111). In step S111, only the customer's strategic goal and information on the measure against it are input and stored in various stakeholder information storage units 150.

  In the goal model shown in FIG. 7, “strategic goals”, “measures”, “business requirements”, and “system requirements” are structured in a tree structure. In the illustrated example, the strategic goal is “reduction of logistics costs”. Measures to realize this strategic goal consist of “reduction of finished product logistics costs” and “reduction of production and procurement logistics costs”. The business requirements necessary to implement such measures are “improving the accuracy of sales forecasts” and “improving the logistics network” to reduce logistics costs for finished products, as well as reducing production and procurement logistics costs. It consists of “Improvement of production and procurement plan”. The system requirements necessary to systematize such business requirements are “sales forecasts based on past results” for improving the accuracy of sales forecasts, and “collaboration with order management systems” for improving the logistics network. And “Create a plan by simulation” to improve the production / procurement plan.

  The business process model generation unit 130 creates a business process model as shown in FIG. 8 related to the strategic goal input in step S111 (step S112), and inputs stakeholder information related to each business process (step S113). In addition, the business process model generation unit 130 selects a business process associated with each measure among them, and associates the measure with the business process (step S114).

  The business model shown in FIG. 8 includes a sales department, a procurement department, a subcontractor, a production factory, a sales base, a store, and a customer. The sales department makes a sales plan. Based on this sales plan, the procurement department makes a procurement plan and, based on this procurement plan, orders parts from a subcontractor. Based on this order, the subcontractor sends the parts to the production plant. At the production plant, products are manufactured from parts and shipped to sales bases. The sales base accepts a shipment request from the production factory.

  On the other hand, the customer places an order with the store, and the store receives the order. Based on this order, the store checks the inventory. If there is a stock, the store delivers the product to the customer and the customer receives the product. On the other hand, if there is no stock, the store requests shipping to the sales base. Based on this shipping request, the sales bases ship the products to each store. Thereby, the store delivers the product to the customer, and the customer receives the product.

  When the user of the stakeholder extraction / management apparatus 100 determines that the business process needs to be further subdivided (step S115), the business process model generation unit 130 creates a subdivided business process model (step S116), Information on stakeholders involved in the process is input (step S117). If it is determined that subdivision is no longer necessary, the goal model generation unit 120 adds the business requirement for the measure to the goal model (step S118).

  When the user of the stakeholder extraction / management apparatus 100 determines that the business requirement needs to be further subdivided (step S119), the goal model generation unit 120 subdivides the business requirement and adds it to the goal model (step S120). If it is determined that subdivision is no longer necessary, the goal model generation unit 120 defines system requirements within the range of business requirements that can be systematized and adds them to the goal model (step S121). If further subdivision of the system requirements is necessary (step S122), the goal model generation unit 120 subdivides the system requirements and adds them to the goal model (step S123).

  When there is no need for subdivision, the development process model generation unit 140 creates a development process model (step S124), and inputs stakeholder information involved in the development process (step S125). The goal model information 152, business process model information 153, development process model information 154, and stakeholder model information 151 input in this way are stored in various stakeholder information storage units 150.

  Next, referring to FIG. 4, a method of extracting stakeholders (hereinafter referred to as “indirect stakeholders”) that are not directly related to the development process or business process but are involved in the strategic goal through decision making, review, etc. ).

  The stakeholder model generation unit 110 inputs customer organization information and creates a stakeholder model as shown in FIG.

  The stakeholder shown in FIG. 6 is divided into a customer side, a vendor side, and others. Customer side stakeholders include “directors”, “stores”, “sales offices”, “customer service centers”, “production departments”, “procurement departments”, “accounting”, and “general affairs”. Directors include “President”, “Vice President A”, and “Vice President B”. The stores include “XX store manager” and “XX store manager”. The production department includes “Production Plan” and “Production Factory”. General affairs includes the “Information System Department”. Vendor side stakeholders include “sales”, “SE”, and “project manager”. The sales include “XX sales representative” and “XX sales representative”. Other stakeholders include “subcontractors” and “customers”.

  At this time, the stakeholder model generation unit 110 classifies the organization to which each stakeholder belongs, and roughly associates it with a strategy (goal) (step S211). Further, the stakeholder model generation unit 110 receives the business target suitability map information of the stakeholder and calculates the importance (step S212).

  The goal model generation unit 120 inputs business goal suitability map information for each strategy (goal) and calculates the importance (step S213). The goal model generation unit 120 stores the created business target suitability map in various stakeholder information storage units 150.

  The indirect stakeholder extraction processing unit 170 calculates the strength of association between the strategy (goal) and the stakeholder based on the business goal relevance map information (step S214), and displays the stakeholders in order of strong association with the strategy (goal). (Step S215). The user selects a stakeholder related to the strategy (goal) from the list, and the related information on the strategy (goal) and the stakeholder is stored in various stakeholder information storage units 150 (step S216).

  Next, a method (operation) for searching for a stakeholder related to a strategy or a requirement (goal) will be described with reference to FIG.

  The search condition input unit 210 inputs search conditions such as strategies and requirements (goals) (step S311). The retrieval unit 160 retrieves related stakeholder information from the various stakeholder information storage units 150 based on the condition (step S312), and displays the retrieval result on the display unit 220 (step S313).

  In the illustrated example, the search condition is “goal”, but in addition to this, “development process” and “business process” may be selected.

  Next, the stakeholder classification method in step S211 of FIG. 4 will be described in detail.

  Stakeholder roles include strategy execution processes, innovation processes, supply chain processes, customer relation processes, and support processes. Stakeholders who determine and execute the company's strategy, such as the president, directors, and business division heads, are responsible for the strategy execution process. The innovation process is a process that creates products, businesses, and technologies, such as research, development, product planning, and business planning. The supply chain process is a process related to production and distribution of products such as production, procurement, and logistics. The customer relation process is a process that is closely related to customers, such as sales, sales promotion, and public relations. The support process corresponds to accounting, human resources, general affairs, etc. that support these processes. The classified roles are associated with the four BSC viewpoints as shown in FIG.

  The four viewpoints of the BSC shown in FIG. 10 include a “financial viewpoint”, a “customer viewpoint”, a “business process viewpoint”, and a “learning and growth viewpoint”. From the financial point of view, the strategy execution process and the support process correspond. The customer relationship process and the innovation process correspond to the customer perspective. Supply chain processes correspond to business process perspectives. The support process corresponds to the viewpoint of learning and growth.

  Next, the business target fitness map in step S212 and step S213 in FIG. 4 will be described.

  There are three types of business goal suitability maps, a financial perspective map, a customer perspective map, and an organizational perspective map, and the items in the first column and the first row are different. This item is an evaluation item for evaluating strategies (goals) and stakeholders. A list of evaluation items is shown in FIG.

  The evaluation items shown in FIG. 11 include a “financial viewpoint map”, a “customer viewpoint map”, and an “organization viewpoint map”. The financial perspective map consists of expanding sales volume, increasing customer value, reducing costs, and improving capital efficiency. The customer perspective map consists of quality (functionality, efficiency, reliability, usability, maintainability, portability), speed, price, brand image, information provision ability, and customer service. The organizational perspective map consists of employee awareness (working environment, morals), capability development (business skills, IT skills, basic skills), and knowledge management.

  The goal model generation unit 120 and the stakeholder model generation unit 110 create a business target suitability map as shown in FIG. The business goal relevance map is in the form of a table. In each of the financial viewpoint map, customer viewpoint map, and organization viewpoint map, the same items are displayed in the first column and the first row. The business target suitability map shown in FIG. 12 shows an example of a financial viewpoint map.

  In the business target suitability map (financial perspective map) shown in FIG. 12, the items in the first column and the first row are “expansion of sales volume”, “improvement of customer value”, “cost reduction”, and It consists of “improving capital efficiency”.

  The goal model generation unit 120 generates a business goal fitness map for a strategy (goal). At that time, the financial viewpoint strategy (goal) uses a financial viewpoint map, the customer viewpoint strategy (goal) uses a customer viewpoint map, and the learning and growth viewpoint strategy (goal) uses an organizational viewpoint map.

  The stakeholder model generation unit 110 generates a business goal suitability map for the stakeholders. At that time, by using the business goal relevance map, weighting is performed on what is important for stakeholders and strategies (goals). After that, the stakeholder model generation unit 110 compares the weights of elements important to the stakeholder and the strategy (goal), and excludes the stakeholder having a small weight and a low relation by the threshold value.

  According to the stakeholder extraction / management apparatus 100 according to the present embodiment, it is possible to easily acquire an explicit / implicit request from a customer at an early stage of the information system solution proposal process. This is because, in the early stage of the proposal, stakeholders that appear and are related in the process of consensus formation can be extracted in advance. In addition, according to the stakeholder extraction / management apparatus 100 according to the present embodiment, it is possible for information system and service vendors to easily grasp the stakeholders involved in the agreement / review of requirements (goals) during the development process. Can do. The reason is that it is possible to search for a stakeholder on the condition of a strategy or requirement (goal).

  The stakeholder extraction / management apparatus 100 according to the embodiment of the present invention can be realized as a stakeholder extraction / management method. Further, the stakeholder extraction / management apparatus 100 according to the embodiment of the present invention may be executed by a computer using a stakeholder extraction / management program.

  Next, the operation of the mode for carrying out the present invention will be described using specific examples.

  Assume that the customer has created a BSC strategic scorecard as shown in FIG.

  In the BSC strategy scorecard shown in FIG. 13, there are “finance viewpoint”, “customer viewpoint”, “business process viewpoint”, and “learning and growth viewpoint” as viewpoints. For each of these viewpoints, a “strategic goal”, “performance evaluation index (KPI)”, “target value”, “measure”, and “responsible department” are set. In FIG. 13, the performance evaluation index (KPI) and the target value are omitted.

  The strategic goal from a financial point of view is “reducing logistics costs”. Strategic objectives from the customer's perspective are “sell products tailored to customers” and “understand customer potential needs”. Strategic objectives from the perspective of business processes are “reducing inventory of finished products”, “reducing delivery times”, and “expanding build-to-order production”. Strategic objectives in terms of learning and growth are “to apply best practices” and “to enhance organizational learning”.

  The measures to achieve the strategic goal of “reducing logistics costs” are “reducing finished product logistics costs” and “reducing production and procurement logistics costs”. The responsible departments in that case are the production department, procurement department, logistics department, and sales department.

  The measure for achieving the strategic goal of “selling products tailored to customers” is “start of order-to-order manufacturing (BTO) service”, and the responsible departments in that case are the sales department and the information system department. The measure to achieve the strategic goal of “Understanding the potential needs of customers” is “Implementation of questionnaire”, and the responsible departments in that case are the sales department and the marketing department.

  The measures to achieve the strategic goal of “reducing the inventory of finished products” are “application of build-to-order production” and “reduction of the number of inventory”, and the responsible departments in that case are the production department and the sales department. Measures to achieve the strategic goal of “reducing delivery time” are “reduction of waiting products” and “reduction of waiting for parts”. In this case, the responsible departments are the production department, procurement department, logistics department, and sales department. Department. The measure for achieving the strategic goal of “expanding custom production” is “promotion of custom production”, and the responsible departments in that case are the production department and the sales department.

  The measure for achieving the strategic goal of “applying best practices” is “confirmation of information transmission”, and the responsible departments in that case are the production department, procurement department, logistics department, and sales department. The measure for achieving the strategic goal of “enhancing the learning ability of the organization” is “Implementation of Web education”, and the responsible departments in that case are the personnel department and the information system department.

  Using such customer strategy information as an input, the goal model generation unit 120 creates a goal model as shown in FIG. In this case, the strategic goal of the scorecard is the top goal, and the measure is its subgoal. For other strategic goals that need to be systematized, a similar goal model is created.

  The business process model generation unit 130 creates a business process model that is involved when executing the strategic goal. An example is shown in FIG. In this way, the business process is associated with the stakeholder that executes it. In addition, business processes and measures will be linked to further refine the business processes as necessary.

  The development process model generation unit 140 creates a development process model as shown in FIG. 9 and associates the development process with stakeholders.

  In the development process model shown in FIG. 9, “requirement analysis”, “overview design”, “detailed design”, “implementation”, “unit test”, “integration test”, “system test”, and “operation” are developed as development processes. There is. Each of these development processes has associated stakeholders as described below.

  The “request analysis” development process is associated with stakeholders of “vendor sales”, “vendor SE”, and “customer information system department”. The “design overview” development process is associated with stakeholders of “vendor SE” and “customer information system department”. The “detailed design” development process is associated with stakeholders of “vendor SE” and “development subsidiary”. The “implementation” development process is associated with the “development subsidiary” stakeholder. The “unit test” development process is associated with the stakeholders of the “development subsidiary”. The “integration test” development process is associated with stakeholders of “vendor SE” and “development subsidiary”. The “system test” development process is associated with stakeholders of “vendor SE” and “customer information system department”. The “operation” development process is associated with stakeholders of “vendor SE” and “customer information system department”.

  The stakeholder model generation unit 110 creates an organization chart as shown in FIG. 6 and classifies the stakeholders by role. The method of classification will be described later. Of these four viewpoints and BSC viewpoints, the financial viewpoint, the customer viewpoint, and the learning and growth viewpoint are associated.

  The goal model generation unit 120 and the stakeholder model generation unit 110 create a business target suitability map as shown in FIG. As described above, the business target suitability map in FIG. 12 is a financial viewpoint map.

  In the example of FIG. 12, “Increase in sales quantity” is entered in the first row and “Increase in customer value” is entered in the second column. If the increase in sales volume is more important, enter an integer from 2 to 9, if it is equivalent, enter 1 and if the improvement in customer value is more important, enter the reciprocal from 2 to 9 . When the row item and the column item have the same contents, 1 is input. After filling in the numbers, calculate the geometric mean of each row. The sum is set to 1 and converted into a ratio is defined as the importance.

  As shown in FIG. 14, the goal model generation unit 120 creates a business target suitability map for a strategy (goal) that is a top goal. If it is a strategy (goal) from a financial perspective, a financial perspective map is used. As shown in FIG. 15, the stakeholder model generation unit 110 creates a business target suitability map for each stakeholder. At this time, which business target fitness map is used depends on the stakeholder classification. In the example of FIG. 15, “general affairs” corresponds to the financial viewpoint of the BSC in the support process, and therefore shows a case where the financial viewpoint map is used as the business target suitability map. On the other hand, for example, the “sales department” corresponds to the BSC customer's viewpoint in the customer relation process, and therefore uses the customer viewpoint map as the business target conformity map.

と、下記の数２で表されるステークホルダの重要度

とに基いて、間接ステークホルダ抽出処理部１７０は、戦略（ゴール）とステークホルダとの関連度Ｒを算出する。Ｒの算出式は下記の数３のとおりである。 A calculation example of the indirect stakeholder extraction processing (S214 in FIG. 4) in the indirect stakeholder extraction processing unit 170 will be described. The importance of the strategy (goal) expressed by the following number 1

And the importance of the stakeholder expressed by Equation 2 below

Based on the above, the indirect stakeholder extraction processing unit 170 calculates the degree of association R between the strategy (goal) and the stakeholder. The formula for calculating R is as follows.

ここで、ｉは項目の番号、ｎは項目数を表している。

Here, i represents the item number, and n represents the number of items.

  The higher the degree of relevance, the stronger the relation with the strategy (goal). In the example of FIG. 16, when the degree of relevance is obtained from the importance 300 for the strategy (goal) “reduction of distribution costs” and the importance 310 for the stakeholder “president”, the following equation 4 is obtained.

  Similarly, when calculating the degree of association for other stakeholders, the result is 320 in FIG. 16, and the relationship with the strategy (goal) is strong in the order of president, vice president B, accounting, vice president A, general affairs, and personnel. become.

  Next, the indirect stakeholder extraction processing unit 170 excludes the stakeholder below the set threshold from the indirect stakeholder. For example, if the threshold is set to 0.400, the indirect stakeholders are the president, vice president B, and accounting.

  The search unit 160 receives input of search conditions from the search condition input unit 210. For example, in the input screen as shown in FIG. 17, the user selects one of the strategy / requirement (goal) selection unit 330 to search for a related stakeholder from the strategic goal, measure, business requirement, and system requirement, and performs the search. When the execution button 350 is pressed, the search unit 160 extracts stakeholder information that matches the search conditions selected from the various stakeholder information storage units 150, and the stakeholder and the indirect stakeholder are directly displayed on the display unit 340. .

  The example of FIG. 17 shows an example in which the measure “reduction of production / procurement logistics costs” is selected and the search execution button 350 is pressed. In this case, the display unit 340 displays “subcontractor”, “procurement department”, “production factory”, “vendor SE”, “vendor sales”, and “information system department” as direct stakeholders, and as indirect stakeholders. , “President”, “Vice President B”, and “Accounting” are displayed.

  An example of generating a development process model in the development process model generation unit 140 will be described with reference to FIG. The development process is input on the screen 330. One box contains the name of the development process, and the bottom part contains the stakeholders. Stakeholders are selected from the list on screen 340. In the example of FIG. 18, the user inputs “system test” on the screen 330 and selects from the vendor side stakeholders displayed on the display unit 340. When the selection of the stakeholder is completed, the selected stakeholder enters the lower part of the box of the screen 330 by pressing the save button 350.

  An example of generating a business process model in the business process model generation unit 130 will be described with reference to FIG. A business process is entered on screen 330 and a stakeholder is selected on screen 340. The selected stakeholder is displayed at the top of the screen 330. A goal is input on the screen 360. In the example of FIG. 19, by selecting “Store” from the customer side stakeholder displayed on the screen 340 and pressing the save button 350, the selected “Store” is input at the top of the screen 330. . In addition, the screen 360 shows an example in which “reduction of distribution cost” is input as a goal.

  Below, the aspect of this embodiment is demonstrated.

  The stakeholder extraction / management apparatus according to the first aspect of the present invention includes a stakeholder model generation unit that models a stakeholder and manages the role of an organization, a goal model generation unit that structures and manages customer goals, and a customer business. Business process model generation unit for managing process models, goals, and stakeholders in association with each other; Development process model generation unit for managing system development processes in association with stakeholders; stakeholder model generation unit, goal model generation unit, business process model The stakeholder information storage unit that stores the stakeholder information structured by the generation unit and the development process model generation unit, and the search that searches the related stakeholders from the various stakeholder information storage units using the input goal as a search condition. Comprising a part, by using the information stored in various stakeholder information storage unit, and the indirect stakeholder extraction processing unit which extracts the stakeholders involved indirectly to the goal, the.

  In the stakeholder extraction / management apparatus according to the first aspect of the present invention, the search unit may further input a development process as a search condition and search for related stakeholders from various stakeholder information storage units. The search unit may further input a business process as a search condition and search for related stakeholders from various stakeholder information storage units. The stakeholder model generation unit may include means for maintaining a customer organization name, an organization role, and an association between the organizations and generating a business goal fitness map for each organization. The goal model generation unit may include means for managing a customer goal divided into four viewpoints of Balanced Scorecard (BSC) and generating a business target fitness map for each goal. The indirect stakeholder extraction processing unit calculates a degree of association between the goal and the stakeholder based on the information created by the stakeholder model generation unit and the goal model generation unit, and presents in order from the stakeholder having the highest degree of association with the goal. May include.

  The stakeholder extraction / management method according to the second aspect of the present invention includes a stakeholder model generation stage for modeling stakeholders and managing the role of an organization, a goal model generation stage for structuring and managing customer goals, and customer business. Business process model generation stage for managing process models, goals and stakeholders in association with each other, Development process model generation stage for managing system development processes in association with stakeholders, stakeholder model generation stage, goal model generation stage, business process model Various stakeholder information storage stages that store stakeholder information structured in the generation stage and development process model generation stage, and related stakeholders from the various stakeholder information storage stages using the input goal as a search condition. It comprises a search step of searching for the holder, and indirect stakeholders extraction step of extracting stakeholders involved indirectly in the goal with the information stored in various stakeholder information storage means.

  In the stakeholder extraction / management method according to the second aspect of the present invention, the search stage may further input a development process as a search condition and search for related stakeholders from various stakeholder information storage stages. In the search stage, a business process may be further input as a search condition, and related stakeholders may be searched from various stakeholder information storage stages. The stakeholder model generation step may include a step of maintaining a customer organization name, an organization role, and a relationship between organizations, and generating a business goal fitness map for each organization. The goal model generation step may include a step of managing a customer goal divided into four viewpoints of Balanced Scorecard (BSC) and generating a business target fitness map for each goal. The indirect stakeholder extraction processing stage includes calculating the degree of association between the goal and the stakeholder based on the information created in the stakeholder model generation stage and the goal model generation stage, and presenting in order from the stakeholder having the highest degree of association with the goal May include.

  A stakeholder extraction / management program according to a third aspect of the present invention includes a computer, a stakeholder model generation unit that models a stakeholder and manages the role of an organization, and a goal model generation unit that structures and manages customer goals. , Business process model generating means for managing the business process model of the customer in association with the stakeholder, development process model generating means for managing the system development process in association with the stakeholder, stakeholder model generating means, goal model generating means Various stakeholder information storage means for storing stakeholder information structured by the business process model generation means and the development process model generation means, and various stakeholder information storage using the input goal as a search condition. The search means for searching for related stakeholders from the means, and the indirect stakeholder extraction processing means for extracting the stakeholder indirectly related to the goal using the information stored in the various stakeholder information storage means. is there.

  In the stakeholder extraction / management program according to the third aspect of the present invention, the search means further inputs a development process as a search condition, and further executes a process for searching related stakeholders from various stakeholder information storage means. You may let me. The search means may further input a business process as a search condition and cause the computer to further execute a process of searching for related stakeholders from various stakeholder information storage means. The stakeholder model generation means may hold the organization name of the customer, the role of the organization, and the relationship between the organizations, and cause the computer to execute a process of generating a business goal fitness map for each organization. The goal model generation means may manage a customer's goal by dividing it into four viewpoints of Balanced Scorecard (BSC), and cause the computer to execute a process of generating a business target fitness map for each goal. The indirect stakeholder extraction processing means calculates the degree of association between the goal and the stakeholder based on the information created by the stakeholder model generation means and the goal model generation means, and performs a process of presenting in order from the stakeholder having the highest degree of association with the goal. It can be executed by a computer.

  The present invention has been described above with reference to the embodiments (and examples), but the present invention is not limited to the above embodiments (and examples). Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

  The system according to the present invention helps a service business based on customer requirement definition (business model) development support. In addition, we will strengthen the activities of facilitators including IT service coordinators.

DESCRIPTION OF SYMBOLS 100 Stakeholder extraction / management apparatus 110 Stakeholder model production | generation part 120 Goal model production | generation part 130 Business process model production | generation part 140 Development process model production | generation part 150 Various stakeholder information storage part 151 Stakeholder model information 152 Goal model information 153 Business process model information 154 Development process Model information 160 Search unit 170 Indirect stakeholder extraction processing unit 200 Various information input unit 210 Search condition input unit 220 Display unit

Claims (18)

A stakeholder model generator that models stakeholders and manages the role of the organization;
A goal model generator for structuring and managing customer goals;
A business process model generation unit for managing a business process model of a customer in association with the goal and the stakeholder;
A development process model generation unit that manages and associates a system development process with the stakeholders;
Various stakeholder information storage units for storing stakeholder information structured by the stakeholder model generation unit, the goal model generation unit, the business process model generation unit, and the development process model generation unit;
A search unit for searching for related stakeholders from the various stakeholder information storage units using the input goal as a search condition;
An indirect stakeholder extraction processing unit for extracting a stakeholder indirectly related to the goal using information stored in the various stakeholder information storage units;
A stakeholder extraction / management device characterized by comprising:   The stakeholder extraction / management apparatus according to claim 1, wherein the search unit further inputs a development process as the search condition and searches for related stakeholders from the various stakeholder information storage units.   The stakeholder extraction / management apparatus according to claim 1, wherein the search unit further inputs a business process as the search condition and searches for related stakeholders from the various stakeholder information storage units.   The said stakeholder model production | generation part hold | maintains the organization name of a customer, the role of an organization, and the relationship between organizations, and contains the means to produce | generate the business target conformity map for every organization, Any one of Claim 1 thru | or 3 characterized by the above-mentioned. The stakeholder extraction / management apparatus according to any one of the above.   The goal model generation unit includes means for managing the goal of a customer by dividing it into four viewpoints of Balanced Scorecard (BSC) and generating a business target fitness map for each of the goals. 4. The stakeholder extraction / management apparatus according to any one of 1 to 3.   The indirect stakeholder extraction processing unit calculates a degree of association between the goal and the stakeholder on the basis of information created by the stakeholder model generation unit and the goal model generation unit, and from a stakeholder having a high degree of association with the goal 6. The stakeholder extracting / managing apparatus according to claim 1, further comprising means for presenting in order. A stakeholder model generation stage that models stakeholders and manages the role of the organization;
A goal model generation stage to structure and manage customer goals;
A business process model generation stage for managing a business process model of a customer in association with the goal and the stakeholder;
A development process model generation stage for associating and managing a system development process and the stakeholder;
Various stakeholder information storage stages for storing stakeholder information structured by the stakeholder model generation stage, the goal model generation stage, the business process model generation stage, and the development process model generation stage;
A search stage for searching for related stakeholders from the various stakeholder information storage stages, using the input goal as a search condition;
An indirect stakeholder extraction step of extracting a stakeholder indirectly related to the goal using information stored in the various stakeholder information storage means;
A stakeholder extraction / management method characterized by comprising:   The stakeholder extraction / management method according to claim 7, wherein the search stage further inputs a development process as the search condition and searches for related stakeholders from the various stakeholder information storage stages.   The stakeholder extraction / management method according to claim 7, wherein the search stage further inputs a business process as the search condition and searches for related stakeholders from the various stakeholder information storage stages.   10. The stakeholder model generation step includes a step of maintaining a customer organization name, organization role, and association between organizations, and generating a business goal fitness map for each organization. The stakeholder extraction / management method according to any one of the above.   8. The goal model generation step includes the step of managing the goal of a customer by dividing it into four viewpoints of Balanced Scorecard (BSC), and generating a business goal fitness map for each of the goals. The stakeholder extraction / management method according to any one of 1 to 9.   In the indirect stakeholder extraction processing step, the degree of association between the goal and the stakeholder is calculated based on the information created in the stakeholder model generation step and the goal model generation step, and the stakeholder having a high degree of association with the goal The stakeholder extraction / management method according to any one of claims 7 to 11, further comprising a step of presenting in order. Computer
Stakeholder model generation means for modeling stakeholders and managing organizational roles;
Goal model generation means to structure and manage customer goals,
Business process model generation means for managing a business process model of a customer in association with the goal and the stakeholder;
Development process model generation means for managing a system development process and the stakeholder in association with each other;
Various stakeholder information storage means for storing stakeholder information structured by the stakeholder model generation means, the goal model generation means, the business process model generation means, and the development process model generation means;
Search means for searching related stakeholders from the various stakeholder information storage means using the input goal as a search condition;
An indirect stakeholder extraction processing means for extracting a stakeholder indirectly related to the goal using information stored in the various stakeholder information storage means;
Program for stakeholder extraction and management to function.   The stakeholder extraction / management program according to claim 13, wherein the search means inputs a development process as the search condition and causes the computer to further execute a process of searching for related stakeholders from the various stakeholder information storage means.   The stakeholder extraction / management program according to claim 13, wherein the search means inputs a business process as the search condition and causes the computer to further execute a process of searching for related stakeholders from the various stakeholder information storage means.   14. The stakeholder model generation means holds a customer organization name, an organization role, and an association between organizations, and causes the computer to execute a process of generating a business goal fitness map for each organization. A program for stakeholder extraction / management according to any one of 1 to 15.   The goal model generation means manages the customer's goal divided into four viewpoints of Balanced Scorecard (BSC), and causes the computer to execute a process of generating a business target fitness map for each goal. The stakeholder extraction / management program according to any one of claims 13 to 15.   The indirect stakeholder extraction processing means calculates the degree of association between the goal and the stakeholder based on the information created by the stakeholder model generation means and the goal model generation means, and from the stakeholder having a high degree of association with the goal The stakeholder extraction / management program according to any one of claims 13 to 17, which causes the computer to execute processing presented in order.

Images