Information processing device and information processing method
Patent Information
- Application Number
- PCT/JP2025/005764
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-20
- Publication Date
- 2026-08-27
Smart Images

Figure JP2025005764_27082026_PF_FP_ABST
Abstract
Description
Information Processing Apparatus and Information Processing Method
[0001] The present invention relates to an information processing apparatus and an information processing method.
[0002] Consideration for the environment has become an essential element for companies. Therefore, consideration for the environment is required in all decision-making processes, such as management, research and development, business strategy, marketing, and consulting.
[0003] As a conventional technology related to such an environment, Patent Document 1 can be cited. In Patent Document 1, a power source management device capable of promoting environmental activities is disclosed. Specifically, a technology for controlling the ratio of renewable energy power to the received power of equipment is disclosed.
[0004] Japanese Patent Application Laid-Open No. 2020-170484
[0005] Patent Document 1 is a technology related to ESG (Environment, Social, Governance). However, currently, decision-making in ESG-related technology development has become more difficult than before. The reason is that the requirements for ESG differ for each stakeholder surrounding the company and are changing rapidly.
[0006] That is, the required specifications are dispersed, making it difficult to make unified judgments, and it currently takes a lot of time for ESG-related decision-making across companies and industries. However, Patent Document 1 does not consider this point.
[0007] Therefore, an object of the present invention is to provide a technology capable of shortening the time required for ESG-related decision-making.
[0008] To solve the above problems, one representative information processing apparatus of the present invention is an information processing apparatus including a database, a display device, an input device, and a processing device. The processing device acquires a plurality of data and formats stored in the database, displays the plurality of data and formats on the display device, receives information to be entered in the format displayed on the display device via the input device, and displays a framework created based on the information on the display device.
[0009] According to the present invention, the time required for ESG-related decision-making can be reduced.
[0010] Other issues, configurations, and effects not mentioned above will be clarified by the following description of the embodiments.
[0011] This is a diagram showing an example of the system configuration of Example 1. This is a block diagram showing an example of the computer hardware configuration. This is a flowchart showing an example of the processing performed by the system of Example 1. This is a diagram showing an example of the screen displayed on the computer display device of Example 1. This is a diagram showing an example of a use case map. This is a diagram showing an example of a requirements list. This is a diagram showing an example of a stakeholder map. This is a diagram showing an example of a legend for a stakeholder map. This is a diagram showing an example of the format of a requirements organization framework. This is a diagram showing an example of a requirements organization framework. This is a diagram showing an example of the system configuration of Example 2. This is a flowchart showing an example of the processing performed by the system of Example 2. This is a diagram showing an example of the screen displayed on the computer display device of Example 2. This is a flowchart showing an example of the processing performed by the system of Example 3. This is a diagram showing an example of the screen displayed on the computer display device of Example 3. This is a diagram showing an example of the screen displayed on the computer display device of Example 3.
[0012] The following examples will be described with reference to the drawings.
[0013] Figure 1A shows an example of the system configuration of Example 1.
[0014] The system 100 (information processing device) of Embodiment 1 includes a computer 101 and a database 102. The database 102 is located on a server connected via a network, and the computer 101 can communicate with this database 102.
[0015] Database 102 stores a use case map 301 (first information), a request list 401 (second information), a stakeholder map 501 (third information), and a format 601. Database 102 may also store a request organization framework 701.
[0016] Use case map 301 is a diagram showing the progress of measures and systems that address ESG-related requirements. Requirements list 401 is a diagram showing system requirements for each scope of carbon dioxide emissions or greenhouse gases. Stakeholder map 501 is a diagram showing the relationships between stakeholders.
[0017] The requirements organization framework 701 is a diagram that organizes multiple pieces of ESG-related information. Format 601 is a format for creating the requirements organization framework 701, and the requirements organization framework 701 is created by filling in information in Format 601 by referring to the use case map 301, the requirements list 401, and the stakeholder map 501.
[0018] Computer 101 can retrieve or update necessary information from database 102. Operator 103 can operate computer 101, for example, while interacting with customer 104, and display the data retrieved from database 102 on computer 101's display device. Operator 103 can also modify the data displayed on the display device.
[0019] The software for rendering the requirements organization framework 701, described later, is either installed and runs on computer 101, or runs in a cloud environment outside of computer 101. In other words, the service in this embodiment may be provided as SaaS (Software as a Service).
[0020] Figure 1B is a block diagram showing an example of the hardware configuration of computer 101.
[0021] Computer 101 is a server or computer configured by interconnecting a processing unit 111, memory 112, storage device 113, communication interface 114, input device 115, and display device 116 via an internal communication path 117.
[0022] The processing unit 111 is a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), etc., and implements the necessary functions by executing programs stored in memory 112 (or storage device 113).
[0023] Memory 112 is the main memory used by the processing unit 111 when executing processing, and is composed of volatile memory elements such as RAM (Random Access Memory).
[0024] The storage device 113 is an auxiliary storage device for storing input data provided to the processing device 111 and output data output from the processing device 111, and is composed of non-volatile storage elements such as an SSD (Solid State Drive).
[0025] The communication interface 114 is an interface used by the computer 101 to communicate with an external device (for example, a database 102), and is composed of a network adapter, a communication module, etc. The communication interface 114 is connected to a network (for example, the Internet) and communicates with the external device via the network.
[0026] The input device 115 is an interface that receives input from the user (operator), and is composed of a mouse, keyboard, touch panel, or voice input device, etc.
[0027] The display device 116 is an interface for displaying data and is composed of a display or the like.
[0028] The internal communication channel 117 is a communication path for exchanging data between the various components of the computer 101.
[0029] Figure 2A is a flowchart showing an example of a process performed by the system 100 of Example 1. Figure 2B is a diagram showing an example of a screen displayed on the display device 116 of the computer 101 of Example 1.
[0030] In step S201, when the processing unit 111 of the computer 101 receives the business information of the customer 104 from the worker 103 via the input device 115, it accesses the database 102 and obtains data related to the entered business information (use case map 301, request list 401, stakeholder map 501, format 601).
[0031] Business information refers to, for example, the business segment to which customer 104 belongs, such as "healthcare," "logistics," or "vehicles." The use case map 301, the requirements list 401, and the stakeholder map 501 are provided with information (e.g., metadata) to retrieve data related to the entered business information.
[0032] In step S202, the processing unit 111 divides the display screen of the display device 116 into four sections, as shown in Figure 2B, for example, and displays the data acquired in step S201 (use case map 301, request list 401, stakeholder map 501, format 601) in each section. This allows the processing unit 111 to display multiple data simultaneously on the display device 116, enabling the worker 103 and customer 104 to make quick decisions while comparing this information.
[0033] Operator 103 can view the use case map 301, request list 401, and stakeholder map 501 displayed on the display device 116 and modify this data on the screen as needed. Therefore, this data does not need to be saved in a complete state from the beginning. Rather, in today's rapidly changing times, it is necessary to reflect the current information if there have been changes since the last time information was entered. Furthermore, by managing the version history in system 100, the content before modification can be saved.
[0034] Furthermore, the worker 103 can create the requirements organization framework 701, described later, by referring to the use case map 301, requirements list 401, and stakeholder map 501 displayed on the display device 116 while discussing with the customer 104, and by entering the results of the discussion into the format 601 displayed on the display device 116.
[0035] Returning to Figure 2A, in step S203, the processing unit 111 determines whether or not it has received a data change (modification of the use case map 301, request list 401, stakeholder map 501, or entry of format 601) via the input device 115.
[0036] If the processing unit 111 accepts a data change in step S203, in step S204, the processing unit 111 accesses the database 102 and updates the data. Also, if the processing unit 111 accepts an entry into format 601 and a new request organization framework 701 is created, the created request organization framework 701 is stored in the database 102.
[0037] Then, returning to step S202, the processing unit 111 displays the modified data on the display device 116.
[0038] On the other hand, if the processing unit 111 has not accepted the data change in step S203, in step S205, the processing unit 111 determines whether or not it has received a termination instruction via the input device 115.
[0039] If the processing unit 111 receives a termination instruction in step S205, it terminates the display of data on the display device 116 and ends this process. On the other hand, if the processing unit 111 does not receive a termination instruction in step S205, it returns to step S202 and repeats the process.
[0040] Figure 3 shows an example of a use case map 301.
[0041] The use case map 301 is a diagram that represents the progress of measures and systems corresponding to requirements related to ESG (Environment, Social, Governance). In the use case map 301, the horizontal axis represents information related to the supply chain and value chain, and the vertical axis represents the classification of ESG-related requirements. In FIG. 3, as an example of the supply chain and value chain, "raw materials", "capital goods", etc. are described, and as an example of ESG-related requirements, "visualization", "reduction" are described.
[0042] On this use case map 301, figures 302, 303, 304 representing information on the progress of measures, and figures 305, 306, 307 representing information on the progress of systems are arranged. Figures 302, 303, 304 respectively represent that the measure is "in concept", "in execution", "not implemented after consideration", and figures 305, 306, 307 respectively represent that the system is "in planning", "under construction", "completed construction". These figures 302 to 307 are distinguished by the color of the figure, the pattern of hatching, the type of frame line, etc.
[0043] FIG. 4 is a diagram showing an example of the requirement list 401.
[0044] The requirement list 401 is a diagram that represents system requirements for each scope of carbon dioxide emissions or greenhouse gas.
[0045] The scope 402 of carbon dioxide emissions or greenhouse gas (GHG) is classified into three categories: scope 1, scope 2, and scope 3 based on the emission source.
[0046] The requirement content 403 describes the content of ESG-related requirements (e.g., "visualization", "reduction" such as carbon dioxide emissions).
[0047] The specific content 404 of the requirement describes specific requirement content regarding the calculation of carbon dioxide emissions and reduction measures (e.g., "Submission of carbon dioxide emissions at the company level is required").
[0048] The next-generation factory maturity model Lv405 describes indicators for evaluating the progress of factory smartification (e.g., evaluated in 6 levels from LV.1 to LV.6).
[0049] The total value of requirement level classification 406 is the total value obtained by summing up the numerical values of requirement level classification for each business when the company is engaged in multiple manufacturing industries (businesses) (e.g., when a company has a printer business and a medical device business, the numerical values of requirement level classification for each business are calculated and summed up).
[0050] The systemization status, use case, issues, etc. 407 describe the following three pieces of information. The systemization status describes the progress of systemization (e.g., "system not introduced", "introduced in some processes", "fully operational"). The use case describes the specifications and functions of the introduced system (e.g., "analyze the collected data on the cloud and visualize the carbon dioxide emissions for each department"). The issues describe the issues in systemization (e.g., "high introduction cost and difficult to deploy across the entire factory").
[0051] The countermeasure direction and new use case proposal 408 describe the content of countermeasures against the issues described in the systemization status, use case, issues, etc. 407 and the proposals for newly considered use cases.
[0052] The requirement level classification 409 describes an indicator for evaluating the level of requirements (e.g., evaluated in 5 levels: 0: no opinion, 1: nice to have, 2: useful, 3: important, 4: essential).
[0053] The requester 410 describes the department or organization that has made a request to the self-department (e.g., "customer", "environmental department").
[0054] The response classificationFigure 5A shows an example of a stakeholder map 501. Figure 5B shows an example of a legend for the stakeholder map 501.
[0057] The stakeholder map 501 is a diagram that shows the relationships between stakeholders. The stakeholder map 501 includes areas that describe the supply chain and value chain, such as Corporate 502, Stakeholders 503, Society (Global) 504, Upstream Supply Chain Companies 505, Our Company 506, Downstream Supply Chain Companies 507, Customer Companies 508, and User Use, Collection, and Reuse 509.
[0058] In the corresponding area on this stakeholder map 501, a figure representing the stakeholder is placed according to the stakeholder legend 511 in the legend 510 of Figure 5B. The importance of the stakeholder is distinguished by the color of the figure, the hatching pattern, the type of border, etc.
[0059] Furthermore, the relationships between each stakeholder are represented by lines, according to the requirements of Legend 510 and related Legend 512. The importance of the requirements is distinguished by the color and type of the lines.
[0060] Note that the stakeholders listed in the stakeholder map in Figure 5A are not limited to those shown; for example, "consumers" may be added.
[0061] Figure 6 shows an example of the format 601 of the requirements organization framework 701.
[0062] The information included in the Requirements Framework 701 includes (1) stakeholder trends (e.g., requirements, guidelines, evaluation systems), (2) context (the company's surrounding environment), (3) system requirements, and (4) company activities (e.g., ongoing activities, existing systems, development themes).
[0063] In format 601, the horizontal axis (first axis) is set with items related to stakeholders, and the vertical axis (second axis) is set with items related to the company's surrounding environment and / or items related to system requirements.
[0064] Format 601 includes, for example, a title field 602, a corporate mission / brand purpose field 603, a stakeholder field 604, an importance field 605, a context field 606, a system requirements definition field 607, a domain entry field 608, and a legend field 609.
[0065] The worker 103 uses the input device 115 to enter the title of the framework and the corporate mission / brand purpose in the title field 602 and the corporate mission / brand purpose field 603 of the format 601.
[0066] Furthermore, worker 103 may arbitrarily change the contents of the Stakeholder field 604, the Context field 606, and the System Requirements Definition field 607, and enter the importance level of each stakeholder in the Importance field 605.
[0067] Furthermore, worker 103 creates a requirements organization framework 701 by referring to the use case map 301, the requirements list 401 displayed on the display device 116, and the stakeholder map 501, and entering information about the stakeholders' requirements in the area entry field 608 according to the legend 609. Specifically, shapes are placed in the corresponding areas on this format 601 according to the legend 609. The type of information is distinguished by the color of the shapes, the hatching pattern, the type of border lines, etc.
[0068] Figure 7 shows an example of a requirements organization framework 701.
[0069] The requirements organization framework 701 is a diagram that organizes multiple pieces of information related to ESG.
[0070] The information entered on the requirements organization framework 701 includes, for example, currently underway 703, the scope currently covered by the activities underway 704, potential for future consideration 705, current requirements 706, future requirements 707, supplementary issues 708, and characteristic areas 709.
[0071] On the requirements organization framework 701, for example, information 710 and 711 of the requester (current) are placed, and a dotted arrow 712 is drawn to indicate that information 710 influences information 711.
[0072] Furthermore, for example, information 713 indicating the possibility of future consideration is placed on the requirements organization framework 701, and a solid arrow 714 is drawn to indicate that information 710 and information 713 are related.
[0073] This requirements organization framework 701 allows the worker 103 to understand which stakeholders' requirements are related to which context or system requirements, and to determine how to scale ongoing design activities or existing systems. As a result, the time required for ESG-related decision-making can be reduced.
[0074] Regarding the use case map 301 (first information), the requirements list 401 (second information), and the stakeholder map 501 (third information), these three are not mandatory, and you can choose any one of these three or any other information.
[0075] According to Example 1, by organizing and visualizing multiple pieces of ESG-related information, the time required for ESG-related decision-making can be shortened.
[0076] Next, Example 2 will be described. In Example 2, the same reference numerals are used for components identical to those in Example 1, and only the different parts will be described.
[0077] Figure 8 shows an example of the system configuration of Example 2.
[0078] The system 100 of Example 2 differs from Example 1 in that it includes a generation AI unit 801 that can communicate with a computer 101 and a database 102. The generation AI unit 801 retrieves data from the database 102 according to prompts input from the computer 101 and generates a requirements organization framework 701 based on the retrieved data (use case map 301, requirements list 401, stakeholder map 501).
[0079] The generation AI unit 801 may be artificial intelligence capable of recognizing and analyzing images. This allows for the generation of a requirements organization framework 701 based on the use case map 301, requirements list 401, and stakeholder map 501, which are stored as images.
[0080] The generation AI unit 801 is also sometimes referred to as the LLM (Large Language Models) unit, the large-scale language model unit, or the generation model unit.
[0081] Furthermore, the generation AI unit 801 includes multiple reinforcement learning agents that operate in parallel. These reinforcement learning agents enable not only "understanding" the data but also "thinking" about it.
[0082] The hardware configuration of the computer 101 in Example 2 is the same as that of Example 1 shown in Figure 1A.
[0083] Figure 9A is a flowchart showing an example of a process performed by the system 100 of Example 2. Figure 9B is a diagram showing an example of a screen displayed on the display device 116 of the computer 101 of Example 2.
[0084] In step S901, when the processing unit 111 of the computer 101 receives the prompt 911 input from the worker 103 via the input device 115, it transmits it to the generation AI unit 801.
[0085] Prompt 911 can be entered as text or voice. An example of a prompt 911 entered here is: "Access the database to obtain the use case map, requirements list, stakeholder map, and format. Fill in the format based on the contents of the use case map, requirements list, and stakeholder map."
[0086] In step S902, the generation AI unit 801 receives a prompt 911 sent from the computer 101.
[0087] In step S903, the generation AI unit 801 accesses the database 102 in accordance with the prompt 911 received in step S903 and obtains the necessary data (use case map 301, request list 401, stakeholder map 501).
[0088] In step S904, the generation AI unit 801 understands and processes the data acquired in step S904, and based on the results, generates an output message 912 and a requirements organization framework 701. An example of the output message 912 generated here is, "Based on the acquired data, the following format has been filled in."
[0089] In step S905, the output message 912 and the request sorting framework 701 are sent as a response to the computer 101.
[0090] In step S906, the processing unit 111 of the computer 101 receives the response transmitted from the generation AI unit 801.
[0091] In step S907, as shown in Figure 9B, the processing unit 111 displays the output message 912 and the request sorting framework 701 received in step S907 on the display device 116, and then terminates the process.
[0092] Alternatively, one or more samples of the requirements organization framework 701 may be pre-stored in the database 102, and the generation AI unit 801 may be instructed by prompt 911 to refer to these samples when generating the requirements organization framework 701. This allows the generation AI unit 801 to generate the requirements organization framework 701 in the format intended by the operator 103.
[0093] Furthermore, the generation AI unit 801 can be instructed to extract feature regions from the data and add the feature regions 709 to the requirements organization framework 701, as shown in Figure 7. An example of a prompt 911 input to the generation AI unit 801 at this time is, "Please add the feature regions to the generated requirements organization framework."
[0094] Furthermore, additional information such as global affairs can be input along with the prompt 911 to the generation AI unit 801, causing the generation AI unit 801 to predict future request sources based on the additional information and to add the request source (future) 707 to the request organization framework 701. Global affairs include, for example, the contents of COP (Conference of the Parties) resolutions and the trends of PRI (Principles for Responsible Investment).
[0095] Furthermore, based on the large amount of data accumulated in the database 102, the generation AI unit 801 can be made to analyze data trends, and the analysis results can be displayed as an output message 912 on the display device 116 of the computer 101. An example of a prompt input to the generation AI unit 801 at this time is: "Access the database and obtain all use case maps, requirements lists, stakeholder maps, and requirements organization frameworks related to healthcare. Based on the obtained data, consider what trends can be seen in ESG-related requirements in the healthcare industry."
[0096] Based on the feature area 709, the request source (future) 707, and the output message 912 added by the generation AI unit 801, the worker 103 and the customer 104 can further discuss and consider the matter.
[0097] In Example 2, an external service may be used as the generation AI unit 801. When using an external generation AI service, the computer 101 in this embodiment inputs a prompt 911 to the external generation AI service, receives the request organization framework 701 generated by the generation AI service, and displays it on the display device 116. In other words, the generation AI unit 801 is not an essential component of this embodiment.
[0098] According to Example 2, by having the generation model unit generate a requirements organization framework, the time required for ESG-related decision-making can be further reduced.
[0099] Next, Example 3 will be described. In Example 3, the same reference numerals are used for components identical to those in Example 2, and only the different parts will be described.
[0100] The system configuration of Example 3 is the same as that of Example 2 shown in Figure 8.
[0101] Figure 10A is a flowchart showing an example of a process performed by the system 100 of Example 3. Figures 10B and 10C are examples of screens displayed on the display device 116 of the computer 101 of Example 3.
[0102] The system 100 of Embodiment 3 differs from Embodiment 2 in that the generation AI unit 801 expands the use case map 301, the requirements list 401, and the stakeholder map 501 from the requirements organization framework 701 according to the prompt 911 input from the computer 101. The generation AI unit 801 can also consolidate the use case map 301, the requirements list 401, and the stakeholder map 501 into the requirements organization framework 701.
[0103] In step S1001, when the processing unit 111 of the computer 101 receives the prompt 911 and the pre-created request organization framework 701 from the worker 103 via the input device 115, it transmits the prompt 911 and the request organization framework 701 to the generation AI unit 801.
[0104] An example of a prompt 911 sent at this point is, "Please develop the use case map, requirements list, and stakeholder map based on the requirements organization framework you entered."
[0105] In step S1002, the generation AI unit 801 receives the prompt 911 and the request organization framework 701 sent from the computer 101.
[0106] In step S1003, the generation AI unit 801, in accordance with the prompt 911 received in step S1002, understands and processes the requirements organization framework 701, and based on the results, generates an output message 912 and data (use case map 301, requirements list 401, stakeholder map 501). An example of the output message 912 generated here is, "Based on the input requirements organization framework, the following use case map, requirements list, and stakeholder map have been developed."
[0107] In step S1004, the output message 912 and data (use case map 301, request list 401, stakeholder map 501) are sent as a response to the computer 101.
[0108] In step S1005, the processing unit 111 of the computer 101 receives the response transmitted from the generation AI unit 801.
[0109] In step S1006, as shown in Figure 10B, the processing unit 111 divides the display screen of the display device 116 into four sections and displays the output message 912 and data (use case map 301, request list 401, stakeholder map 501) received in step S1005, respectively.
[0110] The worker 103 discusses with the customer 104 while referring to the use case map 301, the requirements list 401, and the stakeholder map 501 displayed on the display device 116, and modifies this data on the screen based on the results of the discussion.
[0111] In step S1007, the prompt 911 from the worker 103 and the modified data (use case map 301, request list 401, stakeholder map 501) are received via the input device 115 and transmitted to the generation AI unit 801.
[0112] An example of a 911 prompt sent at this point is, "Please consolidate the entered use case map, requirements list, and stakeholder map into the requirements organization framework."
[0113] In step S1008, the generation AI unit 801 receives the prompt 911 and the modified data sent from the computer 101.
[0114] In step S1009, the generation AI unit 801 understands and processes the data according to the prompt 911 received in step S903, and based on the results, generates an output message 912 and a requirements organization framework 701. An example of the output message 912 generated here is, "The input data has been summarized into the following requirements organization framework."
[0115] In step S1010, the output message 912 and the request sorting framework 701 are sent as a response to the computer 101.
[0116] In step S1011, the processing unit 111 of the computer 101 receives the response transmitted from the generation AI unit 801.
[0117] In step S1012, the processing unit 111 displays the output message 912 and the request sorting framework 701 received in step S907 on the display device 116, as shown in Figure 10C.
[0118] The worker 103 discusses with the customer 104 while referring to the requirements organization framework 701 displayed on the display device 116, and modifies the requirements organization framework 701 on the screen based on the results of the discussion. The worker 103 may repeat this process and have the generation AI unit 801 develop the data again based on the modified requirements organization framework 701, or the process may be terminated at this point.
[0119] In step S1013, the processing unit 111 determines whether or not it has received an input of a termination instruction or prompt 911 via the input device 115.
[0120] If the processing unit 111 receives a termination instruction in step S1013, it terminates the display of data on the display device 116 and ends this process. On the other hand, if it receives input for prompt 911 in step S1013, it returns to step S1001, and the processing unit 111 sends prompt 911 and the request organization framework 701 to the generation AI unit 801.
[0121] In this way, by repeatedly going through the cycle of steps S1001 to S1013, the accuracy of the use case map 301, the requirements list 401, the stakeholder map 501, and the requirements organization framework 701 can be improved.
[0122] The processing unit 111 stores the generated use case map 301, request list 401, stakeholder map 501, and request organization framework 701 in the database 102, and accesses the database 102 to update this data when it is modified on the screen.
[0123] Furthermore, if the requirements organization framework 701 is already stored in the database 102, in step S1001, a prompt 911 such as "Access the database and obtain the requirements organization framework. Based on the requirements organization framework, develop the use case map, requirements list, and stakeholder map" may be input to the generation AI unit 801. In this case, before step S1003, the generation AI unit 801 accesses the database 102 and obtains the requirements organization framework 701.
[0124] In Example 3, an external service may be used as the generation AI unit 801, similar to Example 2. When using an external generation AI service, the computer 101 in this embodiment inputs a prompt 911 to the external generation AI service, receives the use case map 301, request list 401, and stakeholder map 501 generated by the generation AI service, and displays them on the display device 116. In other words, the generation AI unit 801 is not an essential component of this embodiment.
[0125] According to Example 3, the accuracy of the data can be improved by modifying the data, expanding the requirements organization framework to multiple data points in the generation model unit, and then aggregating the multiple data points into the requirements organization framework.
[0126] The embodiments of the present invention have been described above. For example, if environmental law A is changed to law B as a change in system requirements, operating costs may increase. The present invention makes it possible to understand the degree of impact by visualizing the impact of the change in law. Furthermore, the traceability of system changes accompanying the change in law is also improved.
[0127] Furthermore, to improve traceability, managing the first information regarding use cases, the second information regarding system requirements, the third information regarding stakeholders, the format, or the created framework using distributed ledger technology as a blockchain or other representation is also within the scope of this disclosure.
[0128] For example, a stakeholder map at a given time can be treated as a blockchain block. If the stakeholder map is modified, the hash value representing the original stakeholder map, along with a timestamp, is stored in the data of the modified stakeholder map (e.g., the header). This improves tamper resistance and enhances traceability. While this example uses a stakeholder map, this concept can also be applied to use case maps, request lists, formats, or frameworks.
[0129] The present invention is not limited to the embodiments described above, but can also be applied to other fields, such as the examination of safety and social requirements.
[0130] It should be noted that the present invention is not limited to the embodiments described above, and various modifications are included. For example, the embodiments described above are described in detail to make the present invention easier to understand, and are not necessarily limited to those having all the configurations described. Furthermore, it is possible to replace parts of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add configurations from other embodiments to the configuration of one embodiment. In addition, it is possible to add, delete, or replace parts of the configuration of each embodiment with other configurations.
[0131] 100: System 101: Computer 102: Database 103: Worker 104: Customer 301: Use Case Map 401: Requirements List 501: Stakeholder Map 601: Format 701: Requirements Organizing Framework
Claims
1. An information processing apparatus comprising a database, a display device, an input device, and a processing device, wherein the processing device acquires a plurality of data and formats stored in the database, displays the plurality of data and the formats on the display device, receives information to be entered into the formats displayed on the display device via the input device, and displays a framework created based on the information on the display device.
2. An information processing device according to claim 1, wherein the plurality of data includes at least one of first information relating to a use case, second information relating to a system request, and third information relating to a stakeholder.
3. An information processing apparatus according to claim 2, wherein the processing apparatus is an information processing apparatus that simultaneously displays the plurality of data and the format on the display device.
4. An information processing device according to claim 2, wherein the format is such that items relating to the stakeholders are set on a first axis, and items relating to the company's surrounding environment and / or items relating to system requirements are set on a second axis intersecting the first axis.
5. An information processing device according to claim 2, wherein the first information is a diagram showing the progress of measures or systems corresponding to a request.
6. An information processing device according to claim 2, wherein the second information is a diagram representing system requirements for each scope of carbon dioxide emissions or greenhouse gases.
7. An information processing device according to claim 2, wherein the third information is a diagram representing the relationships between the stakeholders.
8. An information processing apparatus according to claim 2, wherein the processing apparatus causes the generation model unit to acquire the plurality of data from the database, generates the framework based on the plurality of data, and displays the framework on the display device.
9. An information processing device according to claim 8, wherein the processing device causes the generation model unit to extract feature regions based on the plurality of data, and adds the feature regions to the framework.
10. An information processing device according to claim 8, wherein the processing device inputs additional information to the generation model unit, causes the generation model unit to make a prediction based on the plurality of data and the additional information, and adds the result of the prediction to the framework.
11. An information processing device according to claim 8, wherein the processing device causes the generation model unit to acquire the plurality of data from the database, to analyze the trend of the data based on the plurality of data, and displays the result of the analysis on the display device.
12. An information processing device according to claim 2, wherein the processing device inputs the framework to the generation model unit, causes the generation model unit to generate the first information, the second information, and the third information based on the framework, and displays the first information, the second information, and the third information on the display device.
13. An information processing device according to claim 2, wherein the processing device inputs the plurality of data into the generation model unit, causes the generation model unit to generate the framework based on the plurality of data, and displays the framework on the display device.
14. An information processing device according to claim 2, wherein the processing device causes the generation model unit to acquire the framework from the database, generates the first information, the second information, and the third information based on the framework, and displays the first information, the second information, and the third information on the display device.
15. An information processing method for an information processing apparatus comprising a database, a display device, an input device, and a processing device, wherein the processing device acquires a plurality of data and formats stored in the database, displays the plurality of data and the formats on the display device, receives information to be entered into the formats displayed on the display device via the input device, and displays a framework created based on the information on the display device.