Information processing device, information processing method, and program

Abstract

This invention provides an information processing device that improves the visibility of the relationships between each stage of the development process and the areas requiring modification. [Solution] The information processing device comprises a data acquisition means, an analogy means, and a visualization means. The data acquisition means acquires relational information between a plurality of design tasks constituting the system's design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks. The analogy means estimates the correspondence relationships across design tasks for each part of the design results and input information based on the acquired relational information, design results, and input information. The visualization means displays the system-wide correspondence structure for the design results and input information based on the estimated correspondence relationships.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, and a program.

Background Art

[0002] In a system development project, risk management plays an important role in ensuring the success of the project. As a method for project risk assessment, a method of aggregating human evaluation values based on development documents or the like may be used (see, for example, Patent Document 1). Also, in the field of text quality analysis, a method of evaluating the quality of documents or the like by learning from good examples and bad examples using natural language processing technology has been proposed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, hierarchical dependencies exist in the development tasks of complex systems. Therefore, if there are deficiencies in the deliverables at each stage, quality risks such as going back, missing deadlines, and falling short of performance may occur. For this reason, it is necessary to improve the visibility of the relationships and correction points at each stage of the development process.

[0005] The main object of the present invention is to provide an information processing apparatus, an information processing method, and a program that contribute to improving the visibility of the relationships and correction points at each stage of the development process.

Means for Solving the Problems

[0006] According to a first aspect of the present invention, an information processing device is provided, comprising: data acquisition means for acquiring relational information between a plurality of design tasks constituting a system design flow, design results of the design tasks, and input information including at least natural language for executing the design tasks; analogy means for estimating correspondence relationships across the design tasks for each part of the design results and the input information based on the acquired relational information, design results, and input information; and visualization means for displaying a correspondence structure across the entire system for the design results and the input information based on the estimated correspondence relationships.

[0007] According to a second aspect of the present invention, an information processing device is provided that acquires relational information between a plurality of design tasks constituting a system design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks; estimates correspondences across the design tasks for each part of the design results and the input information based on the acquired relational information, design results, and input information; and displays a correspondence structure across the entire system for the design results and the input information based on the estimated correspondences.

[0008] A third aspect of the present invention is provided, which causes a computer mounted on an information processing device to perform the following processes: acquiring relational information between a plurality of design tasks constituting a system design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks; estimating correspondences across the design tasks for each part of the design results and the input information based on the acquired relational information, design results, and input information; and displaying a correspondence structure across the entire system for the design results and the input information based on the estimated correspondences. [Effects of the Invention]

[0009] According to each aspect of the present invention, an information processing device, an information processing method, and a program are provided that contribute to improving the visibility of the relationships between each stage of the development process and the areas requiring modification. However, the effects of the present invention are not limited to those described above. The present invention may produce other effects in lieu of or in conjunction with the effects described above. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a diagram illustrating the outline of one embodiment. [Figure 2] Figure 2 is a flowchart showing the operation of one embodiment. [Figure 3] Figure 3 shows an example of a schematic configuration of an information processing system according to the embodiment of this disclosure. [Figure 4] Figure 4 is a diagram illustrating the operation of an information processing system according to an embodiment of this disclosure. [Figure 5] Figure 5 shows an example of the processing configuration of an information processing apparatus according to the present disclosure. [Figure 6] Figure 6 shows an example of a data structure according to the embodiment of this disclosure. [Figure 7] Figure 7 shows an example of a screen displayed by the visualization unit according to the embodiment of this disclosure. [Figure 8] Figure 8 shows an example of a screen displayed by the visualization unit according to the embodiment of this disclosure. [Figure 9] Figure 9 shows an example of a screen displayed by the visualization unit according to the embodiment of this disclosure. [Figure 10] Figure 10 shows an example of a screen displayed by the visualization unit according to the embodiment of this disclosure. [Figure 11] Figure 11 shows an example of a data structure according to the embodiment of this disclosure. [Figure 12] Figure 12 shows an example of a screen displayed by the visualization unit according to the embodiment of this disclosure. [Figure 13] Figure 13 shows an example of a screen displayed by the visualization unit according to the embodiment of this disclosure. [Figure 14] FIG. 14 is a diagram showing an example of a screen displayed by the visualization unit according to an embodiment of the present disclosure. [Figure 15] FIG. 15 is a flowchart showing an example of the operation of the information processing apparatus according to an embodiment of the present disclosure. [Figure 16] FIG. 16 is a diagram showing an example of the processing configuration of the information processing apparatus according to an embodiment of the present disclosure. [Figure 17] FIG. 17 is a diagram showing an example of a screen displayed by the visualization unit according to an embodiment of the present disclosure. [Figure 18] FIG. 18 is a flowchart showing an example of the operation of the information processing apparatus according to an embodiment of the present disclosure. [Figure 19] FIG. 19 is a diagram showing an example of the hardware configuration of the information processing apparatus according to the present disclosure.

Mode for Carrying Out the Invention

[0011] First, an overview of an embodiment will be described. Note that the reference numerals in the drawings appended to this overview are for convenience and are appended to each element as an example to assist understanding, and the description of this overview is not intended to be limiting in any way. Also, unless otherwise specified, the blocks shown in each drawing represent a configuration in terms of functional units rather than hardware units. The connection lines between the blocks in each figure include both bidirectional and unidirectional ones. The one-way arrow schematically shows the flow of the main signal (data) and does not exclude bidirectionality. In this specification and the drawings, elements that can be similarly described may be denoted by the same reference numerals to avoid redundant description.

[0012] An information processing apparatus 100 according to an embodiment includes a data acquisition unit 101, an analogy unit 102, and a visualization unit 103 (see FIG. 1). The data acquisition unit 101 acquires relationship information between a plurality of design tasks constituting a system design flow, design results of the design tasks, and input information including at least natural language for executing the design tasks (step S1 in FIG. 2). The analogy unit 102 estimates a correspondence relationship across design tasks for each part of the design results and the input information based on the acquired relationship information, design results, and input information (step S2). The visualization unit 103 displays a correspondence structure across the entire system for the design results and the input information based on the estimated correspondence relationship (step S3).

[0013] The information processing apparatus 100 estimates a correspondence relationship across a plurality of design tasks by using relationship information between design tasks in a development process and the like. The information processing apparatus 100 visualizes and displays a correspondence structure across the entire system based on the estimated correspondence relationship. As a result, the visibility of the relationships and modification points at each stage of the development process is improved.

[0014] Specific embodiments will be described in more detail below with reference to the drawings.

[0015] [First Embodiment] The first embodiment will be described in more detail with reference to the drawings.

[0016] [Configuration and Schematic Operation of System] As shown in FIG. 3, an information processing system according to the first embodiment includes an information processing apparatus 10 and a terminal 20. [[ID=?]]

[0017] The information processing apparatus 10 is an information processing apparatus that supports system design and work product management by a user. For example, the information processing apparatus 10 is a server installed on a network (in the cloud).

[0018] The user accesses the information processing device 10 by operating terminal 20. The user inputs various information into the information processing device 10 and retrieves various information from the information processing device 10.

[0019] Figure 4 is a conceptual diagram illustrating the value provided by the information processing device 10 according to the embodiment disclosed herein. Figure 4 shows the document creation and evaluation process in a system development project. In system development, the project progresses from the creation of the "requirements definition document" on the left, through the creation of the "design document and manual" in the center, to the creation of the "code" on the right, and the execution of "tests".

[0020] In Figure 4, the documents created at each stage are represented by multiple file icons. Furthermore, the relationships and dependencies between documents are represented by arrows placed between them (multiple file icons).

[0021] In Figure 4, the "Code" section is labeled with a magnifying glass icon, indicating that the code will be examined and analyzed.

[0022] "Test" is represented by a document icon with a checkmark, indicating that the test results are being reviewed.

[0023] In the upper right corner of Figure 4, there is a box labeled "Adjustment Item A." The description "xxx→xxx" inside the box indicates that a change or modification will be made.

[0024] Furthermore, at the far right of Figure 4, two pentagonal icons are placed along with the word "Adjust." These icons represent the process of adjusting and optimizing the entire project.

[0025] Figure 4 visually represents the entire process of system development, from documentation and coding to testing and final adjustments, and concisely illustrates the relationships between each element and the workflow.

[0026] The information processing device 10 enables efficient project management by implementing the system development project management structure shown in Figure 4.

[0027] Next, we will describe the details of the information processing device 10 according to the first embodiment.

[0028] Figure 5 is a diagram showing an example of the processing configuration (processing module) of the information processing device 10 according to the embodiment disclosed herein. Referring to Figure 5, the information processing device 10 comprises a communication control unit 201, a data acquisition unit 202, an estimation unit 203, a visualization unit 204, and a storage unit 205.

[0029] The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from terminal 20. The communication control unit 201 also transmits data to terminal 20. The communication control unit 201 passes data received from other devices to other processing modules. The communication control unit 201 transmits data acquired from other processing modules to other devices. In this way, other processing modules send and receive data with other devices via the communication control unit 201. The communication control unit 201 has the function of a receiving unit that receives data from other devices and the function of a transmitting unit that transmits data to other devices.

[0030] The data acquisition unit 202 is a means of acquiring data from a database or a user.

[0031] The inference unit 203 is a means of inferring (estimating) the relationships between data from the acquired data.

[0032] The visualization unit 204 is a means of displaying the relationships between the inferred data on a terminal 20 or the like used by the user.

[0033] <Prerequisite: Overall system design> Before describing the details of each processing module of the information processing device 10, we will explain the overall system design. The data acquired by the data acquisition unit 202 is information related to the system design. Here, using the information related to the system design as a premise for explanation, we will explain the overall system development.

[0034] The system design process typically proceeds in the following order: requirements analysis, basic design, detailed design, implementation, and testing. Once testing is complete, the system process branches into two paths depending on the test results.

[0035] If the tests pass, the process proceeds directly to code release.

[0036] On the other hand, if the test is not passed, the process moves on to problem analysis.

[0037] After the problem analysis, the need for design changes is determined. If design changes are necessary, the scope of impact is identified, and the relevant parts are redesigned. This redesign returns to the detailed design phase, and the process proceeds again from there. If it is determined that design changes are not necessary, the system process returns to the implementation phase.

[0038] The above is an overview of the system design process.

[0039] <Specific examples of information related to system design> The information on system design acquired by the data acquisition unit 202 includes, for example, the deliverables from each phase of the system design process described above.

[0040] For example, in the requirements analysis phase, a requirements specification document is created that clarifies the system's purpose, functional requirements, and non-functional requirements. This document includes user stories, specific functional requirements, and performance requirements, and forms the basis for design in subsequent phases.

[0041] For example, if the design target is an "online bookstore system," the requirements specification will include user stories such as "As a user, I want to search for books by keyword" and non-functional requirements such as "The search response time should be within 1 second."

[0042] In the basic design phase, a system architecture design document is created that defines the overall system structure and major components. This document includes a system configuration diagram, a list of major components, and the selected technology stack.

[0043] The example of the online bookstore system described above includes a diagram showing the relationship between the web application, API (Application Programming Interface) server, and database, as well as defining key modules such as user management, book management, order management, and payment processing.

[0044] Furthermore, during the basic design phase, technology selections are made, such as using React.js for the frontend, Node.js for the backend, and PostgreSQL for the database.

[0045] In the detailed design phase, detailed design documents, database design documents, API specifications, and other documents are created that define the detailed specifications of each component. These documents include class diagrams, database schemas, and detailed specifications of API endpoints.

[0046] In the example of the online bookstore system described above, a class diagram is created that defines the attributes and methods of the book class, order class, and user class. Furthermore, a database schema showing the structure and relationships of the user table, book table, and order table, and an API specification defining the input parameters and response format of the / api / books / {id} (GET) endpoint are created.

[0047] In the implementation phase, the actual program code is created based on the design. The deliverables include source code and unit test code.

[0048] Specifically, this includes components such as a book search form component using React.js (BookSearchForm.js), book-related API handlers implemented in Node.js (bookController.js), and database access layer code (BookRepository.js). This code is implemented based on the detailed design document, ensuring consistency with the design.

[0049] During the testing phase, test plans, test result reports, and bug reports are created to verify the functionality and quality of the system. These documents include unit test cases, integration test scenarios, and load test results. The testing phase verifies whether the system meets the requirements outlined in the requirements specification.

[0050] For example, unit test code for the book search function, an integrated test scenario that verifies the entire process from user login to book purchase, and graphs showing the system response time when a predetermined number of clients are simultaneously connected are created.

[0051] In the final release phase, documentation is created regarding the deployment and operation of the system in the production environment. For example, deployment plans, user manuals, and operational procedures are created.

[0052] Specifically, this involves creating Terraform code to automate deployment to designated cloud services, documentation in a specified format explaining how to use the online bookstore system, and workflow diagrams detailing recovery procedures in the event of system downtime. These documents are essential for stable system operation and user support.

[0053] The data acquisition unit 202 can acquire deliverables and information from a database or the like for each of the above phases. For example, the database may store this information in a graph format based on the hierarchical structure of the system design. The designers, etc., input the information to be stored in the database into the information processing device 10.

[0054] Here, we will use Figure 6 to explain the concept of database data storage formats.

[0055] Figure 6 is a conceptual diagram showing the data structure from requirements definition to detailed design of an online bookstore system.

[0056] On the left side of Figure 6, three circles labeled "Requirements Definition," "Basic Design," and "Detailed Design" are arranged vertically, with arrows indicating their order. On the right side, a table showing the details of the requirements definition is placed.

[0057] The table shown on the right side of Figure 6 is an example of data stored in the database corresponding to the requirements definition. The table corresponding to the requirements definition consists of three columns: "Section," "ID," and "Description."

[0058] The "Section" column contains the "Overview," "Functional Requirements," "Non-Functional Requirements," and "Constraints."

[0059] The "ID" column is assigned an identifier (FR1, FR2, etc.) corresponding to each requirement.

[0060] The "Description" column contains a detailed explanation of each requirement.

[0061] The "Overview" section listed in the section column explains that the system is an online bookstore platform featuring an extensive book catalog, intuitive search functions, and a secure payment system, with the aim of creating an online community for book lovers.

[0062] The "Functional Requirements" section lists five requirements, from FR1 to FR5. These include user registration and login functionality, advanced book search functionality, personalized recommendation functionality, shopping cart functionality with support for multiple shipping addresses, and order and payment functionality with diverse payment methods.

[0063] The "Non-Functional Requirements" section lists five requirements, NFR1 through NFR5. These include requirements such as search response time, system uptime, number of concurrent users, regular data backups, and page load time.

[0064] The "Constraints" section outlines five conditions, C1 through C5. These include the development period, budget, use of designated cloud services, compliance with personal data protection laws such as GDPR (General Data Protection Regulation) and CCPA (California Consumer Privacy Act), and the need for prior approval for the use of open-source libraries.

[0065] Note that Figure 6 only shows the table data for the requirements definition phase. However, the database may similarly store data in other system development phases such as "basic design" and "detailed design."

[0066] <Example of display screen 1 (for one phase)> Based on the data structure described above, an example of a screen displayed by the visualization unit 204 will be explained.

[0067] Figure 7 shows an example of a requirements definition document presentation screen.

[0068] At the top of Figure 7, a large title is displayed: "Online Bookstore System Requirements Definition Document." This title allows users to immediately understand the nature of the document they are viewing.

[0069] Below the title are four tabs, arranged from left to right as "Overview," "Functional Requirements," "Non-Functional Requirements," and "Constraints." Users can tap these tabs to switch to the corresponding information section.

[0070] The "Overview" tab provides a concise explanation of the overall purpose and features of the online bookstore system, allowing users to grasp the general direction of the project.

[0071] Tapping the "Functional Requirements," "Non-Functional Requirements," and "Constraints" tabs will display a list of requirements (requirement items) belonging to each category.

[0072] Each requirement item consists of an identifier and a brief description of the requirement.

[0073] When a user taps an item, a detailed explanation of the requirements corresponding to that item expands and is displayed. If the user taps the same item again, the details are collapsed. In this way, the necessary information is efficiently provided to the user.

[0074] As users scroll the screen, they can view requirement items that cannot be displayed simultaneously. This layout allows users to grasp the overall picture of the requirements specification document while accessing detailed information as needed. As a result, efficient information management and viewing are achieved on mobile devices.

[0075] Figure 8 shows another example of a requirements definition document presentation screen.

[0076] Figure 8 shows the screen when "Functional Requirements" is selected from the four tabs shown in Figure 7.

[0077] The screen displays five functional requirements in a list format. Each item is collapsible, and in Figure 8, the first item, "User registration and login function (including SNS integration)," is expanded.

[0078] Other features include "advanced book search functionality," "personalized recommendation functionality," "cart functionality and support for multiple shipping addresses," and "ordering and payment functionality with diverse payment methods."

[0079] The screen shown in Figure 8 is designed to allow users to efficiently view the content of one item (functional requirement) in the requirements specification document and access detailed information as needed.

[0080] Figure 9 shows another example of a requirements definition document presentation screen.

[0081] Figure 9 shows the screen when "Non-functional requirements" is selected from the four tabs shown in Figure 7.

[0082] The screen displays five non-functional requirements in a list format. Each item is collapsible, and in Figure 9, the fourth item, "Data backups should be performed every hour," is expanded.

[0083] Other criteria include "search response time of 0.5 seconds or less," "system uptime of 99.99% or higher," "support for 10,000 concurrent users," and "total page load time of 2 seconds or less."

[0084] This screen is designed to allow users to efficiently view the content of one item (non-functional requirement) in the requirements specification document and access detailed information as needed.

[0085] Figure 10 shows another example of a requirements definition document presentation screen.

[0086] Figure 10 shows the screen when "Constraints" is selected from the four tabs shown in Figure 7.

[0087] The screen displays five constraint items in a list format. Each item is collapsible, and in Figure 10, the second item, "Budget is within 100 million yen," is expanded.

[0088] Other requirements include: "Development period must be within 6 months," "Use of designated cloud services," "Compliance with GDPR, CCPA, and the Personal Information Protection Act," and "Prior approval is required for the use of open-source libraries."

[0089] This screen is designed to allow users to efficiently view the contents of one item (constraint) in the requirements specification document and access detailed information as needed.

[0090] <Example of display screen 2 (showing correspondence with other phases)> Based on the data structure shown in Figure 6, an example of a screen in which the visualization unit 204 displays information from multiple development phases will be explained.

[0091] First, as a prerequisite, let's explain an example of the data structure to be displayed.

[0092] Figure 11 shows an example of a data structure that the data acquisition unit 202 can acquire. Figure 11 shows the relationship between the three main phases—requirements definition, basic design, and detailed design—and their related data.

[0093] Similar to Figure 6, Figure 11 has three circles arranged vertically on the left side, each representing "Requirements Definition," "Basic Design," and "Detailed Design." These circles are connected by arrows, illustrating the flow of the development process.

[0094] Two tables are located on the right side of Figure 11. The upper table shows a part of the requirements definition phase and consists of three columns: "Section," "ID," and "Description." This table lists FR3, "Personalized Recommendation Function," as an example of a functional requirement.

[0095] The table below shows the contents of the basic design phase and consists of two columns: "Item" and "Content." This table contains detailed information about the basic design of the recommendation function and includes five items: approach, data update frequency, similar user identification, similar item identification, and recommendation reason category.

[0096] Figure 11 visually illustrates how the functional requirements defined in the requirements definition are implemented in the basic design.

[0097] Figure 12 shows an example of a basic design presentation screen that displays basic design information corresponding to the requirements definition described above.

[0098] At the top of Figure 12 is the title "Online Bookstore System Requirements Definition Document." Below this title, four tabs are arranged horizontally: "Overview," "Functional Requirements," "Non-Functional Requirements," and "Constraints."

[0099] In the state shown in Figure 12, the "Functional Requirements" tab is selected, and the five functional requirements items are displayed in list format. Each item can be collapsed.

[0100] Let's consider the case where the user selects the third option, "personalized recommendation feature." The user can make this selection by clicking or dragging with a mouse or similar device.

[0101] In this case, the expanded items contain detailed information about the basic design of the corresponding function, presented in bullet points. Specifically, this includes details such as the adoption of a hybrid approach, the frequency of updates to user behavior data, methods for identifying similar users, methods for identifying similar items, and methods for displaying recommendation reasons.

[0102] In this way, the basic design presentation screen is designed to visually show the relationship between requirements definition and basic design, allowing users to efficiently view information.

[0103] Note that while Figure 12 discloses data related to requirements definition and basic design, the content presented is not limited to requirements definition and basic design. The visualization unit 204 may display information related to basic design and detailed design, as in the case of requirements definition and basic design, or it may display information about the source code that implements the detailed design.

[0104] Thus, when the visualization unit 204 displays the corresponding structure for the design results and input information, it can display an overview or detailed information. Alternatively, the visualization unit 204 accepts changes to the display range at the same level for the summarized or detailed information (for example, parallel movement such as expanding or collapsing items). In other words, the visualization unit 204 has an interface (provided to the user) for adjusting the range in which the corresponding structure is displayed (information presented to the user) in the form of summarization, detailing, and parallel movement of the display range at the same level. Furthermore, such adjustment is possible at least by clicking and dragging on the displayed predetermined area.

[0105] <Example of display screen 3 (screen that reflects user modifications)> Based on the data structure shown in Figure 6, an example of a screen that reflects the changes received by the user from the data acquisition unit 202 will be explained.

[0106] For example, consider the case shown in Figure 12 where the user changes the "personalized recommendation feature" to the "highly personalized recommendation feature."

[0107] In this case, the visualization unit 204 may enable the modification of the relevant information by displaying a screen like the one shown in Figure 13.

[0108] Figure 13 shows an example of a screen displaying the corrected parts of an online bookstore system.

[0109] At the top of the screen in Figure 13, the title "Online Bookstore System" is displayed. Below this title, the subtitle "Requirements Definition Document" is shown.

[0110] The screen shown in Figure 13 displays four tabs: Overview, Functional Requirements, Non-functional Requirements, and Constraints. In the state shown in Figure 13, the "Functional Requirements" tab is selected. Figure 13 also displays a list of functional requirements, with five items shown.

[0111] Figure 13 expands on the third item, "Highly Personalized Recommendation Function," and displays the details of its basic design in bullet points. These details include items highlighted in bold, such as "Real-time updating of user behavior data."

[0112] The items highlighted in bold are those that will need to be changed in the basic design if the user changes "personalized recommendation function" to "highly personalized recommendation function" in the requirements specification document.

[0113] Thus, when any addition, modification, or deletion of design results or input information is made, the visualization unit 204 has an interface that displays a list of other design results or input information that need to be added, modified, or deleted as a result of the addition, modification, or deletion of the design results or input information. For example, the visualization unit 204 displays a screen on the terminal 20 as shown in Figure 13. In Figure 13, a change has been made to the requirements definition document, and a list of basic designs affected by the change (each item of the basic design affected) is displayed.

[0114] Furthermore, Figure 14 illustrates another example of a screen that reflects the changes. Figure 14 shows an example of a screen that displays the impact analysis of changes to the online bookstore system.

[0115] The top section of the screen shown in Figure 14 contains a rectangular text area for entering changes. In the example in Figure 14, the text "I would like more advanced personalization features added" is entered in the text area.

[0116] Users can send system changes to the data acquisition unit 202 by entering any string of characters in the text area.

[0117] Furthermore, a rectangular "Execute Impact Analysis" button is located below the text area. When the user presses this button, the analogy unit 203 of the information processing device 10 performs an analysis of the correction policy.

[0118] The lower section of the button displays the "Change Impact Analysis Results" and includes three collapsible panels.

[0119] In the "Impact on Requirements Document" panel, under the subcategory "Functional Requirements," you will find a plus icon and the option to "Add New User Attributes," and an edit icon (an icon with a notepad and pencil) and the option to "Update User Profile Requirements."

[0120] The "Impact on Basic Design" panel contains an edit icon and the options "Modify Data Model" and a plus icon and "Add New API Endpoint" under the subcategory "System Configuration".

[0121] In the "Impact on Detailed Design" panel, under the "Database Design" subcategory, you'll find an edit icon and the option to "Update Database Schema," a plus icon and the option to "Create a New Service Class," and a minus icon and the option to "Delete Unnecessary Helper Functions."

[0122] The screen design shown in Figure 14 visually displays the impact of system changes across multiple phases. The plus icon indicates the addition of a new item, the edit icon indicates the updating of an item, and the minus icon indicates the deletion of an item.

[0123] Furthermore, the foldable panel design allows users to unfold and review only the information they need. As a result, users can efficiently analyze the impact of large-scale system changes across multiple phases and accurately identify the necessary tasks.

[0124] Thus, when a user inputs a location where they plan to add, modify, or delete design results or input information, the visualization unit 204 has an interface that displays a list of other design results or input information that will need to be added, modified, or deleted as a result of the addition, modification, or deletion of the design results or input information. For example, the visualization unit 204 uses the text area shown in Figure 14 to obtain the location where the user plans to add, modify, or delete design results or input information.

[0125] <Detailed operation of the analogy unit 203> The above is a description of the user interface according to the first embodiment.

[0126] Here, we will explain in detail the operation of the inference unit 203 for realizing the user interface described above.

[0127] The inference unit 203 infers the relationships between data from the acquired data. Specifically, the operation of the inference unit 203 mainly utilizes text analysis using machine learning models and the construction and exploration of knowledge graphs.

[0128] For example, the analogy unit 203 first applies natural language processing technology to documents such as requirements definitions, basic design documents, and detailed design documents obtained from the data acquisition unit 202 to extract important concepts and elements within each document.

[0129] For example, the analogy unit 203 extracts the functional requirement "personalized recommendation function" from the requirements definition document and identifies related design elements such as "hybrid approach" and "user behavior data update" from the basic design document.

[0130] Next, the analogy unit 203 analyzes the relationships between these extracted elements and constructs a knowledge graph. In the knowledge graph, for example, a node called "personalized recommendation function" is connected to a node called "hybrid approach" by an edge, representing design dependencies.

[0131] The analogy unit 203 uses the knowledge graph to infer how a change in one element will affect other elements.

[0132] For example, consider a case where the "personalized recommendation function" in the requirements definition document is changed to a "highly personalized recommendation function." In this case, the analogy unit 203 searches the knowledge graph for other nodes (elements of the basic design and detailed design) connected to this node (the node corresponding to "personalized recommendation function") and identifies elements that may be affected.

[0133] Furthermore, the analogy unit 203 uses a machine learning model to compare the changes with past project examples and a knowledge base of typical software development practices to evaluate the impact and importance of the changes.

[0134] For example, the inference unit 203 determines that there is a high probability that the "frequency of updating user behavior data" will need to be changed, and also estimates the impact of such change on system performance.

[0135] Based on these analysis results, the analogy unit 203 determines the areas that need to be changed and their priority, and generates the change impact analysis results as shown in Figure 14. Furthermore, during the process of generating the change impact analysis results, the analogy unit 203 constantly learns new information and updates the knowledge graph and inference model. By updating the knowledge graph and inference model, continuous improvement is made to enable more accurate analogies.

[0136] Furthermore, if the data acquired by the data acquisition unit 202 is structured data as shown in Figures 6 and 11, the inference unit 203 may simply transmit information about the structured data to the visualization unit 204. Alternatively, the method by which the visualization unit 204 estimates the relationships between data is not limited to the text analysis described above, but may also utilize a large-scale language model.

[0137] This section explains the use of Large Language Models (LLMs).

[0138] First, the data acquisition unit 202 acquires documents such as the requirements definition document, basic design document, and detailed design document.

[0139] Next, the analogy unit 203 provides these documents as input to the large-scale language model. For example, the analogy unit 203 may generate a prompt such as, "If the 'personalized recommendation function' in the requirements definition document is changed to a 'highly personalized recommendation function,' what impact will this have on the basic design and detailed design?" and input this into the large-scale language model.

[0140] Large-scale language models understand a given context based on system development information stored in a database and analyze the impact of changes by leveraging common knowledge in software development.

[0141] Large-scale language models can generate responses such as, "In the basic design, the frequency of updates to user behavior data needs to be changed in real time. In the detailed design, more advanced machine learning algorithms will need to be implemented, and the database schema should also be considered for expansion."

[0142] The analogy unit 203 analyzes the responses obtained from the large-scale language model and converts them into a structured format. For example, the analogy unit 203 converts the obtained responses into a format such as {Basic design: [Change in the frequency of user behavior data updates], Detailed design: [Enhancement of machine learning algorithms, expansion of database schema]}.

[0143] Finally, the visualization unit 204 receives the structured data from the analogy unit 203 and generates a change impact analysis results screen as shown in Figure 14.

[0144] In this way, the data acquisition unit 202 acquires relationship information between multiple design tasks that constitute the system's design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks. The relationship information between multiple design tasks is, for example, structured data as shown in Figure 11. The design results of the design tasks are, for example, deliverables in the design phase. The input information including at least natural language for executing the design tasks is, for example, information described in a requirements definition document, a basic design document, etc.

[0145] The estimation unit 203 estimates the correspondence between design tasks for each part of the design results and input information, based on the relationship information, design results, and input information acquired by the data acquisition unit 202. For example, the estimation unit 203 estimates the correspondence between important concepts and elements obtained from the requirements definition document and design elements described in the basic design document that are related to the important elements in the requirements definition document.

[0146] The visualization unit 204 displays the overall correspondence structure of the system for the design results and input information, based on the correspondence relationships estimated by the analogy unit 203. For example, the visualization unit 204 displays the above correspondence structure using a user interface as shown in Figures 12 and 13.

[0147] The memory unit 205 is a means for storing information necessary for the operation of the information processing device 10. For example, the database mentioned above is stored in the memory unit 205.

[0148] The operation of the information processing device 10 can be summarized as shown in the flowchart in Figure 15.

[0149] The data acquisition unit 202 of the information processing device 10 acquires data from a database or a user (step S01).

[0150] The inference unit 203 of the information processing device 10 infers the relationships between data from the acquired data (step S02).

[0151] The visualization unit 204 of the information processing device 10 displays the relationships between the inferred data on a display device such as a terminal 20 used by the user (visualization of estimation results; step S03).

[0152] [Terminal] A detailed explanation of terminal 20 is omitted. Examples of terminal 20 include mobile devices such as smartphones, mobile phones, game consoles, and tablets, as well as computers (personal computers, laptops), etc. Terminal 20 can be any device or equipment as long as it can receive user input and communicate with the information processing device 10.

[0153] As described above, the information processing device 10 according to the first embodiment estimates correspondences across multiple design tasks using relationship information between design tasks in the development process. Based on the estimated correspondences, the information processing device 10 visualizes and displays the overall correspondence structure of the system. As a result, the visibility of relationships and modification points at each stage of the development process is improved.

[0154] [Second Embodiment] Next, a second embodiment will be described in detail with reference to the drawings.

[0155] The information processing device 10 according to the second embodiment differs from the information processing device 10 according to the first embodiment in that it has a performance estimation unit 206 (see Figure 16). The performance estimation unit 206 of the information processing device 10 according to the second embodiment visualizes how the overall performance of the system will change as a user, who is a system developer, makes modifications.

[0156] The following will focus on explaining the differences between the first and second embodiments.

[0157] The performance estimation unit 206 is a means for estimating the performance of the result obtained by the analogy unit 203.

[0158] The visualization unit 204 according to the second embodiment can present the estimated performance to the user. Figure 17 illustrates the screen displaying the results of the performance estimation unit 206.

[0159] Figure 17 shows the system performance and configuration interface of the online bookstore system displayed by the visualization unit 204. The screen in Figure 17 is divided into three main sections.

[0160] The "Performance Trend Results" graph at the top displays the trends in response time (solid line) and throughput (dashed line) from January to June. In the top graph, response time is shown on the left axis and throughput on the right axis, with monthly fluctuations indicated.

[0161] In the central "Configurable Settings" section, three parameters—cache size (67%), number of database connections (70%), and number of worker threads (60%)—are configured to be adjustable via sliders. The system shows how changing these settings will affect system performance.

[0162] The "Estimated Performance" section at the bottom displays estimated performance values ​​based on the current settings. Specifically, this section shows an average response time of 95 milliseconds, a throughput of 1350 requests / second, and a CPU utilization of 65%. These values ​​may be dynamically updated by changes to the settings at the top.

[0163] Throughout the entire screen shown in Figure 17, system administrators can monitor performance trends, adjust settings as needed, and see the impact in real time. For example, the graph shows that throughput decreased and response time increased in March, but has been improving since April.

[0164] Furthermore, Figure 17 suggests that the current settings are moderate, and there is room for further optimization.

[0165] Thus, the screen shown in Figure 17 provides users with important information for understanding the current state of the system and for performance tuning. In other words, the information processing device 10 can show the user, who is the system developer, how the performance will change if the system is modified, via the screen shown in Figure 17.

[0166] Thus, the visualization unit 204 provides an interface that allows modification of predetermined parameters in the final system corresponding to the deliverable. For example, as shown in Figure 17, the visualization unit 204 provides an interface that allows modification of parameters such as cache size. Furthermore, the visualization unit 204 has an interface that displays a list including at least one of the performance measurement results and estimated performance (it provides an interface).

[0167] Alternatively, the visualization unit 204 may have an interface that displays design results or input information that needs to be added, modified, or deleted in response to the user inputting a desired change in at least one of the performance measurement results and estimated performance. For example, the visualization unit 204 may display the text area and change impact analysis results section shown in Figure 14 together with the screen shown in Figure 17.

[0168] <Performance estimation method> The specific method used by the performance estimation unit 206 when performing the estimation described above will now be explained.

[0169] The performance estimation unit 206 may perform the above estimation by combining multiple methods.

[0170] As an example, past system log data is used to build a machine learning model. Specifically, a regression model is trained that takes configuration parameters such as cache size, number of database connections, and number of worker threads as inputs, and outputs response time, throughput, and CPU usage.

[0171] For example, complex interactions between parameters can be captured by using ensemble learning methods such as random forests and gradient boosting.

[0172] Alternatively, the performance estimation unit 206 may utilize simulation technology to model the system's behavior under various load patterns. For example, a simulator using existing technology may be constructed, and the performance estimation unit 206 uses this simulator to predict request processing delays and resource utilization under different settings. As a result, various scenarios can be tested without placing a load on the actual system.

[0173] Alternatively, the performance estimation unit 206 may perform highly accurate and flexible estimations by integrating the methods described above.

[0174] The operation of the information processing device 10 according to the second embodiment is summarized in the flowchart shown in Figure 18.

[0175] The data acquisition unit 202 of the information processing device 10 acquires data from a database or a user (step S11).

[0176] The inference unit 203 of the information processing device 10 estimates (infers) the relationships between data from the acquired data (step S12).

[0177] The performance estimation unit 206 of the information processing device 10 estimates the performance based on the result of the analogy unit 203 (performance estimation is performed; step S13).

[0178] The visualization unit 204 of the information processing device 10 displays the estimated performance on a display device such as a terminal 20 used by the user (visualization of the estimation result; step S14).

[0179] As described above, the information processing device 10 according to the second embodiment visualizes and displays how the overall system performance changes when a user makes modifications to the design results. As a result, the user can perform efficient system development.

[0180] Next, we will describe the hardware of each device that makes up the information processing system. Figure 19 shows an example of the hardware configuration of the information processing device 10.

[0181] The information processing device 10 can be configured as an information processing device (a so-called computer), and has the configuration illustrated in Figure 19. For example, the information processing device 10 includes a processor 311, memory 312, input / output interface 313, and communication interface 314, etc. The components of the processor 311, etc. are connected by an internal bus or the like and are configured to communicate with each other.

[0182] However, the configuration shown in Figure 19 is not intended to limit the hardware configuration of the information processing device 10. The information processing device 10 may include hardware not shown, and it may not have to have an input / output interface 313 if necessary. Also, the number of processors 311 etc. included in the information processing device 10 is not intended to be limited to the example in Figure 19; for example, multiple processors 311 may be included in the information processing device 10.

[0183] The processor 311 is a programmable device such as a CPU (Central Processing Unit), MPU (Micro Processing Unit), DSP (Digital Signal Processor), TPU (Tensor Processing Unit), or GPU (Graphics Processing Unit). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs, including an operating system (OS).

[0184] Memory 312 includes RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive), SSD (Solid State Drive), etc. Memory 312 stores the OS program, application programs, and various data.

[0185] The input / output interface 313 is an interface for a display device or input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device that accepts user input such as a keyboard or mouse.

[0186] The communication interface 314 is a circuit, module, etc., that communicates with other devices. For example, the communication interface 314 includes a NIC (Network Interface Card), etc.

[0187] The functions of the information processing device 10 are realized by various processing modules. These processing modules are realized, for example, by the processor 311 executing a program stored in the memory 312. The program can also be recorded on a computer-readable storage medium. The storage medium can be a non-transitory medium such as a semiconductor memory, hard disk, magnetic recording medium, or optical recording medium. In other words, the present invention can also be embodied as a computer program product. Furthermore, the program can be downloaded via a network or updated using the storage medium on which the program is stored. Moreover, the processing module may be realized by a semiconductor chip.

[0188] In addition, terminal 20 can also be configured using an information processing device, similar to information processing device 10, and its basic hardware configuration is no different from that of information processing device 10, so its explanation will be omitted.

[0189] The information processing device 10 is equipped with a computer, and its functions can be realized by having the computer execute a program. Furthermore, the information processing device 10 executes control methods and information processing methods based on this program.

[0190] [Differentiation] The configuration and operation of the information processing system described in the above embodiment are illustrative examples and are not intended to limit the system configuration.

[0191] In the above embodiment, the information processing device 10 was described as being implemented as a server in a server-client system. However, the information processing device 10 may also be implemented as a user's terminal 20 on which a predetermined application is installed.

[0192] In the above embodiment, the case in which the database is configured inside the information processing device 10 was described, but the database may be built on an external database server or the like. In other words, some functions of the information processing device 10 may be implemented in another device. More specifically, it is sufficient that the "visualization unit (visualization means)" etc. described above is implemented in any device included in the system.

[0193] In the flowcharts (sequence diagrams) used in the above description, multiple processes (processes) are shown in order, but the execution order of the processes performed in the embodiment is not limited to the order in which they are shown. In the embodiment, the order of the illustrated processes can be changed to the extent that it does not impair the content, for example, by executing each process in parallel.

[0194] The embodiments described above are explained in detail to facilitate understanding of the disclosure, and it is not intended that all the configurations described above are necessary. Furthermore, when multiple embodiments are described, each embodiment may be used individually or in combination. For example, it is possible to replace parts of the configuration of one embodiment with those of another embodiment, or 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 one embodiment with those of another.

[0195] As described above, the industrial applicability of the present invention is clear, and it is particularly suitable for application to information processing systems that support system design by users.

[0196] [Note 1] A data acquisition means for acquiring relationship information between multiple design tasks that constitute the system's design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks. An analogy means for estimating the correspondence between each part of the design results and the input information across the design tasks, based on the acquired relational information, design results, and input information; Based on the estimated correspondence, a visualization means displays the overall correspondence structure of the system for the design results and the input information, An information processing device equipped with the following features.

[0197] [Note 2] The visualization means has an interface for adjusting the range in which the corresponding structure of the design result and the input information is displayed in the form of summarization, detailing, and parallel shifting of the display range at the same level. The information processing device described in Appendix 1, wherein the adjustment can be performed at least by clicking and dragging a predetermined location displayed.

[0198] [Note 3] The information processing device according to Appendix 1 or 2, wherein the visualization means has an interface that displays a list of other design results or input information that will need to be added, modified, or deleted in connection with the addition, modification, or deletion of the design results or input information, when the user inputs a location where either the addition, modification, or deletion of the design results or input information has been made or where either the addition, modification, or deletion of the design results or input information is planned.

[0199] [Note 4] The visualization means is a modifiable interface in the final system corresponding to the deliverable, and has an interface for displaying a list including at least one of performance measurement results and estimated performance, as described in Appendix 1 or 2.

[0200] [Note 5] The visualization means is a modifiable interface in the final system corresponding to the deliverable, and has an interface that displays design results or input information that needs to be added, modified, or deleted in accordance with the input of a desired change in at least one of the performance measurement results and estimated performance when the user inputs a desired change. This is the information processing device described in Appendix 1 or 2.

[0201] [Note 6] In an information processing device, The system acquires relationship information between multiple design tasks that constitute the system's design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks. Based on the acquired relationship information, design results, and input information, the correspondence between each part of the design results and the input information across the design tasks is estimated. An information processing method that displays the overall correspondence structure of the system for the design results and the input information based on the estimated correspondence relationship.

[0202] [Note 7] The computer installed in the information processing device, A process for obtaining relational information between multiple design tasks that constitute the system's design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks. Based on the acquired relationship information, design results, and input information, a process is performed to estimate the correspondence between each part of the design results and the input information across the design tasks. Based on the estimated correspondence, a process is performed to display the overall correspondence structure of the system for the design results and the input information. A program to execute.

[0203] Furthermore, some or all of the configurations described in Appendices 2 to 5, which are subordinate to Appendice 1 above, may also be subordinate to Appendices 6 and 7 in the same way as those described in Appendices 2 to 5. Moreover, not limited to Appendices 1, 6 and 7, some or all of the configurations described as appendices may also be subordinate to various hardware, software, various recording means for recording software, or systems, without departing from the embodiments described above.

[0204] Furthermore, each disclosure of the above-mentioned prior art documents cited herein is incorporated herein by reference. Although embodiments of the present invention have been described above, the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely illustrative and that various modifications are possible without departing from the scope and spirit of the present invention. That is, the present invention naturally includes the entire disclosure, including the claims, and various modifications and alterations that can be made by those skilled in the art in accordance with the technical idea. [Explanation of Symbols]

[0205] 10 Information Processing Devices 20 devices 100 Information Processing Devices 101 Data acquisition method 102 Analogical means 103 Visualization means 201 Communication Control Unit 202 Data Acquisition Unit 203 Analogy Section 204 Visualization section 205 Storage section 206 Performance estimation section 311 Processors 312 memory 313 Input / Output Interfaces 314 Communication Interface

Claims

1. A data acquisition means for acquiring relationship information between multiple design tasks that constitute the system's design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks. An analogy means for estimating the correspondence between each part of the design results and the input information across the design tasks, based on the acquired relational information, design results, and input information; Based on the estimated correspondence, a visualization means displays the overall correspondence structure of the system for the design results and the input information, An information processing device equipped with the following features.

2. The visualization means has an interface for adjusting the range in which the corresponding structure of the design result and the input information is displayed in the form of summarization, detailing, and parallel shifting of the display range at the same level. The information processing apparatus according to claim 1, wherein the adjustment can be performed by clicking and dragging a predetermined location displayed.

3. The information processing apparatus according to claim 1 or 2, wherein the visualization means has an interface that displays a list of other design results or input information that need to be added, modified, or deleted in connection with the addition, modification, or deletion of the design results or input information, when the user inputs a location where either the addition, modification, or deletion of the design results or input information is planned.

4. The information processing apparatus according to claim 1 or 2, wherein the visualization means is a modifiable interface in the final system corresponding to the deliverable, and has an interface for displaying a list including at least one of performance measurement results and estimated performance.

5. The information processing apparatus according to claim 1 or 2, wherein the visualization means is a modifiable interface in the final system corresponding to the deliverable, and has an interface that displays design results or input information that needs to be added, modified, or deleted in accordance with the input of a desired change in at least one of the performance measurement results and estimated performance when the user inputs a desired change.

6. In an information processing device, The system acquires relationship information between multiple design tasks that constitute the system's design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks. Based on the acquired relationship information, design results, and input information, the correspondence between each part of the design results and the input information across the design tasks is estimated. An information processing method that displays the overall correspondence structure of the system for the design results and the input information based on the estimated correspondence relationship.

7. The computer installed in the information processing device, A process for obtaining relational information between multiple design tasks that constitute the system's design flow, the design results of the design tasks, and input information including at least natural language for executing the design tasks. Based on the acquired relationship information, design results, and input information, a process is performed to estimate the correspondence between each part of the design results and the input information across the design tasks. Based on the estimated correspondence, a process is performed to display the overall correspondence structure of the system for the design results and the input information. A program to execute.

Images