Information processing program, information processing method, and information processing apparatus

Abstract

The present invention provides an information processing program, an information processing method, and an information processing device that can consistently modify related materials. [Solution] The information processing program is a program that can cause a computer to execute the following functions: a function to manage the linking of multiple documents based on multiple categories arranged in a hierarchical structure for classifying documents and multiple items that define the content of the documents; and a function to obtain the change results of each document that is classified into a lower category than the category of the document linked to the target document, based on the fact that the target document among the multiple documents has been changed, from a generation model.

Description

Technical Field

[0001] Embodiments of the present invention relate to an information processing program, an information processing method, and an information processing apparatus.

Background Art

[0002] In a system development project for developing software or the like, it proceeds through a plurality of processes such as requirement definition, design, development, and testing. For example, in the development stage, when a change occurs in requirements or design, the man-hours in the development stage increase in response to the change.

[0003] Patent Document 1 describes storing information indicating the association between a functional specification document and a test design document or the like, and presenting a modification proposal for the associated test design document or the like when there is a change in the functional specification document.

[0004] Patent Document 2 describes registering the correspondence between business design information and system information, and presenting the fluctuation scale or the like of each of the business design information and the system information from the change history sequentially accumulated in the past.

[0005] Patent Document 3 describes searching for related specification documents that change due to a change in specifications, calculating the impact degree of the project based on the quantitative evaluation score of each searched related specification document and the quantitative evaluation indicating the scale of the change in the specifications, and calculating a risk value for changing the specifications.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Patent Document 2

Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0007] In the invention disclosed in Patent Document 1, it is possible to propose modifications to relevant parts in response to changes in the specifications, but it is not possible to modify the related documents in response to the changes.

[0008] In the invention disclosed in Patent Document 2, while it is possible to predict the magnitude of fluctuations from past change history, it is not possible to change the related materials in response to the changes.

[0009] In the invention disclosed in Patent Document 3, it is possible to calculate the risks resulting from specification changes, but it is not possible to change the related materials in accordance with the changes.

[0010] This invention was made in view of the above circumstances and aims to provide an information processing program, an information processing method, and an information processing device that can consistently modify related materials. [Means for solving the problem]

[0011] In one embodiment, the information processing program is a program that can cause a computer to execute the following functions: a function to manage the linking of multiple documents based on multiple categories arranged in a hierarchical structure for classifying documents and multiple items that define the content of the documents; and a function to obtain the change results of each document that is classified into a lower category than the category of the document linked to the target document, based on the fact that the target document among the multiple documents has been changed, from a generation model. [Effects of the Invention]

[0012] According to the embodiment, the relevant materials can be consistently modified. [Brief explanation of the drawing]

[0013] [Figure 1] Figure 1 is a block diagram illustrating an information processing system according to an embodiment. [Figure 2]FIG. 2 is a diagram showing an example of the relevance of materials according to the embodiment. [Figure 3] FIG. 3 is a diagram showing an example of the material structure according to the embodiment. [Figure 4] FIG. 4 is an ER diagram showing an example of the relevance of materials according to the embodiment. [Figure 5] FIG. 5 is a diagram showing an example of a table of materials according to the embodiment. [Figure 6] FIG. 6 is a diagram showing an example of the hierarchical structure of materials according to the embodiment. [Figure 7] FIG. 7 is a block diagram showing an example of the functional configuration of the management server according to the embodiment. [Figure 8] FIG. 8 is a sequence diagram illustrating the procedure of information processing by the information processing system according to the embodiment. [Figure 9] FIG. 9 is a diagram showing an example of a display example of visualization information of the amount of change according to the embodiment. [Figure 10] FIG. 10 is a diagram showing another example of a display example of visualization information of the amount of change according to the embodiment. [Figure 11] FIG. 11 is a diagram showing yet another example of a display example of visualization information of the amount of change according to the embodiment. [Figure 12] FIG. 12 is a diagram showing yet another example of a display example of visualization information of the amount of change according to the embodiment.

BEST MODE FOR CARRYING OUT THE INVENTION

[0014] (Embodiment) Hereinafter, the embodiment will be described with reference to the drawings. In each drawing, the same reference numerals are given to the same components as much as possible, and redundant explanations are omitted.

[0015] (Configuration Example) FIG. 1 is a block diagram illustrating an information processing system S according to the embodiment. Information processing system S is a system for managing documents related to changes in design documents in projects such as system development. The developer may include multiple members. These multiple members may belong to one organization, such as a single company, or to multiple different organizations. The developer is responsible for the development work of the project. The project is mainly software. The project includes, for example, the development of a website that provides web services, and the development of applications.

[0016] A project involves multiple stages. These stages include, for example, requirements definition, design, development (implementation), and testing. The stages are carried out sequentially, from higher-level stages to lower-level stages, in the order described above. The stages progress from higher-level stages to lower-level stages. Higher-level stages are also called preceding stages. Lower-level stages are also called subsequent stages. Each stage is interrelated. For example, if changes occur in the design documents of a preceding stage even though the project has progressed to the development stage, it will affect the development effort in the subsequent stage, impacting the progress of the project. For example, in the case of a large system, it is difficult to determine the scope of impact of changes in the requirements definition or design stage on the entire project. In such cases, it may take time for the requirements definition to converge, or omissions may occur, causing delays in the development stage. Therefore, in order to understand the impact of changes in requirements definition or design on the entire project, it is necessary to manage changes in the design documents in the preceding stages of development. Design documents refer to, for example, documents that document the technical specifications and structure necessary for the implementation of the system based on the requirements definition. The information processing system S may manage changes in the design documents. The information processing system S may also be a system that provides management services for managing design documents. These management services are also called document management services.

[0017] The information processing system S includes a management server 1, user terminals 2, and a generation AI (Artificial Intelligence) system 3. The management server 1, user terminals 2, and generation AI system 3 are connected to each other via a network so that they can communicate with one another. For example, the network NW is the internet. The network may include a wireless network or a wired network. Note that the information processing system S may also refer to a system that includes at least two of the devices among the management server 1, user terminals 2, and generation AI system 3.

[0018] Management Server 1 is a device that collects and processes data. The device includes a computer. Management Server 1 provides, for example, management services. Management Server 1 is connected to User Terminal 2 and Generation AI System 3 via a network. Management Server 1 receives various data from User Terminal 2 and Generation AI System 3 and outputs various data to User Terminal 2 and Generation AI System 3. Management Server 1 may also be an API server that provides an API (Application Programming Interface). Management Server 1 manages design documents. Management Server 1 is an example of an information processing device. An example configuration of Management Server 1 will be described later.

[0019] User terminal 2 is a device capable of communicating with other devices. User terminal 2 can be a PC (Personal Computer), smartphone, or tablet device, etc. The user of user terminal 2 is, for example, a developer responsible for project development work. The user of user terminal 2 accesses the management service application, etc., and uses the management service. For example, if the user of user terminal 2 makes changes to design documents, etc., they may output the changed documents to management server 1. In the following explanation, "output" can be read as "send," "upload," or "return." The user of user terminal 2 may also be a project administrator, etc. User terminal 2 is an example of an information processing terminal.

[0020] The Generative AI System 3 is a device that generates and outputs information in response to input information. The Generative AI System 3 is connected to the Management Server 1 and the User Terminal 2 via a network. The Generative AI System 3 includes a generative model. The generative model is, for example, a generative AI equipped with a language model. The language model is, for example, a model that outputs natural language in response to natural language input such as ChatGPT (Generative Pretrained Transformer). The language model includes language models such as Transformers including BERT (Bidirectional Encoder Representations from Transformers) and BART (Bidirectional and Auto-regressive Transformer), and Recurrent Neural Networks (RNNs).

[0021] Generative models include, for example, natural language generation models or natural language processing models. Generative models include general-purpose natural language processing learning models such as Large Language Models (LLMs) that have been trained on vast amounts of data. Generative models may also be language models that have been fine-tuned for the management of design documents. Generative models may also be language models that can handle various tasks without fine-tuning. Generative models are not limited to those described above. Generative models may also be a combination of text generation AI and image processing AI.

[0022] A generative model generates a response to a task based on an instruction. The generative model may perform additional learning based on feedback on the generated response.

[0023] The generation AI system 3 receives, for example, a command statement (prompt) related to a task from the management server 1. The generation AI system 3 receives a string of design documents from the management server 1. The generation AI system 3 receives related information from the management server 1. The related information is information that indicates the relationships between each document included in the design documents. The information indicating relationships includes, for example, information that indicates the category and items of the design documents. The generation AI system 3 generates a response to the command statement related to the task. The generation AI system 3 outputs the response to the command statement to the management server 1.

[0024] Furthermore, the generation AI system 3 may be connected to the management server 1 via a network such as a local area network within the organization where the information processing system S is operated, enabling communication. The generation AI system 3 may also function as an API service provided by the management server 1.

[0025] This section describes an example configuration for management server 1. The management server 1 is a device that includes a processor 11, main memory 12, auxiliary storage device 13, and communication interface (I / F) 14. Each component of the management server 1 is connected to each other so that signals can be input and output. In Figure 1, the interface is labeled "I / F".

[0026] The processor 11 corresponds to the central part of the management server 1. The processor 11 is an element that constitutes the computer of the management server 1. The processor 11 includes one or more processors. For example, the processor is a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), but is not limited to these. The processor may be composed of various circuits. The processor 11 loads a program that is pre-stored in the main memory 12 or auxiliary storage device 13 into the main memory 12. The program is a program that allows the processor 11 of the management server 1 to execute processing by each part described later. The processor 11 performs various operations by executing the program loaded into the main memory 12. The processor 11 is an example of a processing circuit.

[0027] Main memory 12 corresponds to the main memory portion of the management server 1. Main memory 12 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area of ​​main memory 12, the operating system or programs are stored. Main memory 12 uses the volatile memory area as a work area where data is rewritten as needed by the processor 11. For example, main memory 12 includes ROM (Read Only Memory) as a non-volatile memory area. For example, main memory 12 includes RAM (Random Access Memory) as a volatile memory area. Main memory 12 stores programs.

[0028] The auxiliary storage device 13 corresponds to the auxiliary storage portion of the management server 1. The auxiliary storage device 13 is an EEPROM (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive), etc. The auxiliary storage device 13 stores the above-mentioned program, data used by the processor 11 in performing various processes, and data generated by the processing of the processor 11. The auxiliary storage device 13 stores the above-mentioned program.

[0029] The communication interface 14 includes various interfaces that enable the management server 1 to communicate with other devices via a network, in accordance with a predetermined communication protocol.

[0030] The hardware configuration of management server 1 is not limited to the configuration described above. Management server 1 may, as appropriate, omit or change the above-mentioned components and add new components.

[0031] The design documents managed by the information processing system S will be explained with reference to Figures 2 to 6. Figure 2 shows an example of the relationships between materials according to this embodiment.

[0032] Figure 2 is a table showing the relationships between multiple design documents included in the project. The table includes categories and items for classifying the design documents.

[0033] For example, multiple design documents can be classified into several categories: "business requirements," "non-functional requirements," "data requirements," "functional requirements," and "screen requirements." Multiple design documents can be associated with each category. Multiple design documents can be identified by requirements. Requirements are classified into several levels, such as requirement level and design level. These levels are hierarchical, ranging from higher levels to lower levels. Requirements at the requirement level include, for example, "changes to business flow" and "changes to business rules." Requirements at the design level include, for example, "changes to data structure" and "simplification of functionality." The requirements are just examples of items.

[0034] In Figure 2, the required items for the documents included in each category are indicated by circles. For example, documents classified under the category "Business Requirements" include the required items "Changes to business flow," "Changes to business rules," "Changes to service KPIs," and "Changes to compete with competing products." Documents classified under the category "Non-functional Requirements" include the required items "Enhanced security," "Improved performance," etc.

[0035] Documents containing the requirement item "Changes to business flow" fall into multiple categories: "Business Requirements," "Data Requirements," "Functional Requirements," and "Screen Requirements." For example, among documents classified into multiple categories such as "Business Requirements," "Data Requirements," "Functional Requirements," and "Screen Requirements," documents containing the requirement item "Changes to business flow" are related to each other. For example, Figure 2 shows that if a document classified under the category "Business Requirements" that contains the requirement item "Changes to business flow" is changed, it will affect other documents classified under "Data Requirements," "Functional Requirements," and "Screen Requirements" that also contain the requirement item "Changes to business flow." Furthermore, documents containing the requirement item "Changes to business flow" are not related to documents classified under "Non-Functional Requirements." Figure 2 shows that if a document classified under the category "Business Requirements" that contains the requirement item "Changes to business flow" is changed, it will not affect documents classified under "Non-Functional Requirements."

[0036] For example, Figure 2 shows a hierarchical structure of categories. For instance, the category "Business Requirements" is the highest-level category. The category "Non-Functional Requirements" is at the same hierarchical level as the category "Business Requirements". The category "Data Requirements" is a lower-level category than the category "Non-Functional Requirements". The category "Functional Requirements" is a lower-level category than the category "Data Requirements". The category "Screen Requirements" is a lower-level category than the category "Functional Requirements". Changes to documents in higher-level categories only affect documents in lower-level categories. For example, consider the case in Figure 2 where the document for the requirement item "Changes to Business Flow" in the category "Data Requirements" is changed. In this case, the documents containing the requirement item "Changes to Business Flow" in "Functional Requirements" and "Screen Requirements," which are lower-level categories of "Data Requirements," will be affected. The documents containing the requirement item "Changes to Business Flow" in "Business Requirements," which is a higher-level category of "Data Requirements," will not be affected. Here, an impact means that a change is necessary.

[0037] The table in Figure 2 shows the relationships between design documents included in a category and the scope of the impact of changes. Note that one category may contain multiple requirements. One design document is classified into one category. One design document may contain multiple requirements. The inclusion of requirements in a design document indicates that the design document contains information about those requirements. Multiple design documents may contain information about requirements common to other design documents. Multiple design documents containing common requirements are also called related design documents. Related design documents are also called related documents.

[0038] Figure 3 shows an example of a document structure according to the present invention. Figure 3 shows the hierarchical structure of the multiple categories shown in Figure 2. Figure 3 is a diagram showing the multiple categories in a tree structure. Figure 3 shows the relationships of the entire design document.

[0039] For example, the top-level node represents the top-level category, "Business Requirements." Below "Business Requirements," nodes for categories related to the requirements of "Business Requirements," such as "Data Requirements," "Functional Requirements," and "Screen Requirements," are linked. For example, if a document containing the requirement item "Changes to Business Flow" within "Business Requirements" is modified, it will indicate that the documents classified under the lower-level nodes "Data Requirements," "Functional Requirements," and "Screen Requirements" also need to be modified sequentially.

[0040] In Figure 3, for example, if a document classified under business requirement a1 is changed, the documents classified under data requirements c1 and c2, which are subcategories of business requirement a1, may also be changed. Based on the changes to data requirements c1 and c2, the documents classified under functional requirements d1, d2, and d3, which are subcategories of data requirements c1 and c2, may also be changed. Based on the changes to functional requirements d1, d2, and d3, the documents classified under screen requirements e1, e2, e3, and e4, which are subcategories of functional requirements d1, d2, and d3, may also be changed.

[0041] Thus, if a document classified in a higher category is changed, related documents classified in lower categories must also be sequentially checked for changes. When a document classified in a higher category is changed, related documents classified in lower categories that require changes will be updated sequentially. On the other hand, even if a document classified in a higher category is changed, related documents classified in lower categories that do not require changes will not be updated.

[0042] Figure 4 is an ER diagram showing an example of the relationships between materials according to this embodiment. The project master contains the project ID (projectId) as its primary key (PK). The project ID is a unique identifier assigned to each project to identify it individually. The project master also contains the project name (projectName), which is the name of the project. The project master also contains the edit count, which indicates the total number of changes to the design documents for the entire project. For example, if a change in a higher-level design document results in a change in a lower-level design document, this series of related document changes is counted as one edit count. The project ID in the project master has a one-to-n relationship (where n is an integer greater than or equal to 1) with the project ID in the design document master. The project ID in the project master also has a one-to-n relationship with the project ID in the category master. The project ID in the project master also has a one-to-n relationship with the project ID in the item master.

[0043] The category master includes a category ID (categoryId) as its primary key (PK). The category ID is a unique identifier assigned to each category to identify it individually. A category is, for example, a group used to classify design documents. The category master also includes a project ID (projectId) and an item list (itemIdList) as foreign keys (FK). The item list is a list of requirement items included in each category. The item list includes, for example, an item ID. The item ID is a unique identifier assigned to each requirement item to identify it individually. The category master also includes levels. Levels are classifications used to hierarchically organize categories. Levels may also be, for example, level names. Level names may be, for example, "Requirements Level" or "Design Level". Levels may also be values ​​indicating hierarchy. For example, levels may represent levels 1 through 5. Levels differ for each category. In this example, "Business Requirements" corresponds to "Level 1," "Non-Functional Requirements" to "Level 2," "Data Requirements" to "Level 3," "Functional Requirements" to "Level 4," and "Screen Requirements" to "Level 5." The category IDs in the category master have a one-to-many relationship with the category IDs in the design document master.

[0044] The field master contains the field ID as the primary key (PK). The field master contains the project ID as the foreign key (FK). The field master contains fields. A field is, for example, a field name. A field name is the name of the required field. The field IDs in the field master have a one-to-many relationship with the field list in the category master.

[0045] The design document master includes the document ID (documentId) as the primary key (PK). The document ID is a unique identifier assigned to each design document to identify it individually. The design document master also includes the project ID and category ID as foreign keys (FK). The design document master also includes the document name (documentName), content, and version. The document name is the name of the design document. Design documents may include design documents, specifications, rules, regulations, etc. Content indicates the content of the design document. Content may also be information that shows an overview of the design document. Version is information that indicates the number of changes for each design document.

[0046] Figure 5 shows an example of a table of materials according to the present invention. Figure 5 shows a table based on the ER diagram shown in Figure 4. Figure 5 shows the category table, item table, and design document table.

[0047] The category table includes a category ID, category name, item list, and level. A category ID is, for example, "C1," "C2," etc. A category name is, for example, "Business Requirements," "Non-Functional Requirements," etc. The item list is a list of item IDs for the items included in each category. For example, the category "Business Requirements" includes "I1, I2, I3, I4" in its item list. The level indicates the hierarchy for each category. For example, the category "Business Requirements" is "Level 1." Levels increase in ascending order, for example, from 1 to any maximum value. The minimum level is the highest level, and the maximum level is the lowest level. For example, in the example in Figure 5, "Level 1" is the highest level, and "Level 5" is the lowest level. Levels decrease sequentially from the highest level to the lowest level. Higher-level categories are also called higher categories. Lower-level categories are also called lower categories.

[0048] The item table includes item IDs and item names. Item IDs are, for example, "I1," "I2," etc. Item names are, for example, "Change in Business Flow," "Change in Business Rules," etc. The item table includes design document requirements that fall into multiple categories.

[0049] The design data table includes document ID, category ID, document name, content, and version. The document ID is, for example, "D1", "D2", etc. The category ID corresponds to the category ID in the category table.

[0050] For example, the design document with document ID "D1" has the document name "Requirements Definition Document" and contains "Details of the Requirements Definition Document" as its content. Furthermore, the design document with document ID "D1" recorded as version "1" indicates that it has been modified once. If the design document with document ID "D1" is subsequently modified, it will now have been modified twice, and therefore its version will be "2". In this way, the design document table contains information that shows the history of changes to the design documents. Design documents are, for example, classified into one of several categories. A design document is a document that describes at least one item included in the classified category.

[0051] Figure 6 shows an example of the stepwise structure of the material according to the present invention. Figure 6 shows the structure of the documents shown in Figure 3, arranged from higher level to lower level. For example, "business requirements" are related to "data requirements," "functional requirements," and "screen requirements." "Business requirements" is the highest level, and the lowest level of "business requirements" is "data requirements." The lowest level of "data requirements" is "functional requirements." The lowest level of "functional requirements" is "screen requirements." "Screen requirements" is the lowest level. In this example, changes to the higher-level design documents affect all related documents at the lower levels. For example, if the design document for "business requirements" is changed, the related documents classified as "data requirements," "functional requirements," and "screen requirements" at the lower levels will be changed. If the design document for "data requirements" is changed, the related documents classified as "functional requirements" and "screen requirements" at the lower levels will be changed.

[0052] For example, "non-functional requirements" are related to "data requirements," "functional requirements," and "screen requirements." "Non-functional requirements" are at the highest level, and the lowest level of "non-functional requirements" is "data requirements." The lowest level of "data requirements" is "functional requirements." The lowest level of "functional requirements" is "screen requirements." "Screen requirements" are at the lowest level. In this example, changes to the higher-level design documents affect all related documents at the lower levels. For example, if the design document for "non-functional requirements" is changed, the related documents classified as "data requirements," "functional requirements," and "screen requirements" at the lower levels will be changed. If the design document for "data requirements" is changed, the related documents classified as "functional requirements" and "screen requirements" at the lower levels will be changed.

[0053] Figure 7 is a block diagram showing an example of the functional configuration of the management server 1 according to this embodiment. The management server 1 includes a control unit 110 and a storage unit 120.

[0054] The storage unit 120 includes a data storage area 1201, a related information storage area 1202, and a change amount storage area 1203. The storage unit 120 stores or updates data in the data storage area 1201, the related information storage area 1202, and the change amount storage area 1203 according to instructions from the control unit 110. Here, an example is described in which the management server 1 includes the data storage area 1201, the related information storage area 1202, and the change amount storage area 1203, but the data storage area 1201, the related information storage area 1202, and the change amount storage area 1203 may be included in a device other than the management server 1.

[0055] The data storage area 1201 stores design documents. Design documents include, for example, multiple interrelated design documents. Design documents may be managed on a project-by-project basis. For example, multiple design documents may be associated with a single project. Design documents are an example of documents. In the following description, design documents will also be simply referred to as documents. Design documents are classified into multiple categories. Categories are structured in a hierarchical manner. The hierarchical structure includes a tiered structure that links higher-level structures to lower-level structures. The hierarchical structure includes a tree structure that links higher-level structures to lower-level structures in a tree-like manner. Categories include, for example, business requirements, non-functional requirements, data requirements, functional requirements, and screen requirements. Categories may be arbitrarily defined by the user. Design documents include at least one item. Design documents include, for example, descriptions for at least one item. An item is an element for defining the content of the design document. An item may also be an element that shows an overview of the content of the design document. An item is, for example, a requirements item. An item may include items common to multiple categories. The items may be arbitrarily defined by the user. Design documents can be defined by multiple categories and multiple items. Multiple design documents can be linked based on multiple categories and multiple items.

[0056] Design documents may include information indicating the category, document name, content, and version information. The category information is information that identifies the category. Examples of such information include the category name or category ID. Design documents may also include information that identifies the target project. Examples of such information include the project ID. Data in document storage area 1201 is updated when documents are added, updated, or deleted.

[0057] The related information storage area 1202 stores related information. Related information is information that indicates the relationships between multiple design documents. Related information includes information that indicates the category of the design document and information that indicates the items of the design document. Information that indicates the category includes, for example, information that indicates the hierarchical structure of multiple categories. For example, the hierarchical structure of multiple design documents is defined by the information that indicates the category. Information that indicates the category may also include an item list and information that indicates the level. An item list is, for example, a list of items included in the design document. An item list may also be a list of item IDs. Information that indicates the level is information that indicates the level corresponding to the category. For example, if the level corresponding to the category "Requirements Definition" is "Level 1", then the information that indicates the level for the design document classified as "Requirements Definition" is "Level 1". Information that indicates the category may also include information that can identify the target project.

[0058] The information indicating an item may include information indicating at least one item contained in each design document. For example, the information indicating an item in a design document classified as requirements definition may include information indicating items such as "changes in business flow" and "changes in business rules." The information indicating an item includes information that can identify the item. Information that can identify an item is, for example, the item name or item ID. For example, multiple design documents are linked by common items. Design documents linked based on category information and item information are also called related documents. Related information is information for identifying the hierarchical structure and relationships of multiple design documents. For example, based on related information, the management server 1 can identify other design documents related to a particular document from among the design documents classified in a lower category of that particular document. The data in the related information storage area 1202 is updated by adding, updating, or deleting related information.

[0059] The change amount storage area 1203 stores the change amount. The change amount indicates the change amount for each design document. The change amount may be, for example, the change amount from the initial version of each design document to any given version. The change amount may also be the change amount from the previous version of each design document to the current version. The change amount is, for example, a numerical value that shows the difference between the document before and after the change. The change amount may be, for example, the difference distance of strings contained in the document before the change and the document after the change. The change amount may also be a numerical value quantitatively calculated from the number of characters contained in the document before the change and the document after the change. The change amount may be updated each time the document is changed. The change amount may be stored for each version of each document. The version is, for example, the initial state of the document is the initial version, and is counted up each time a change is made. The initial version indicates the state in which the document was created. The initial version is also called version 0. For example, if document A is changed once from its initial version, the version of document A is "version 1 (V1)". The version may be counted up, for example, when at least one of the multiple documents included in a project is changed. For example, if a project includes Document A and Document B, even if only Document A has been modified once since its initial version, the versions of Documents A and B are "Version 1". In this case, the version of the project containing Documents A and B is "Version 1". The version indicates, for example, the number of changes. The amount of change includes the calculation result by the calculation unit 1103, which will be described later. The change amount storage area 1203 stores the history of the amount of change. The change amount storage area 1203 updates the history of the amount of change each time the version changes. The change amount storage area 1203 stores the calculation result of the amount of change each time the amount of change is calculated by the calculation unit 1103. The change amount storage area 1203 stores the history of the calculation results. The data in the change amount storage area 1203 is updated by additions, updates, or deletions of the amount of change.

[0060] The control unit 110 is a function realized by the management server 1 when the processor 11 executes the program described above. The control unit 110 functions as the management unit 1101, the generation processing unit 1102, the calculation unit 1103, and the display processing unit 1104 when the processor 11 executes the program described above. The control unit 110 executes a program for managing design documents.

[0061] The management unit 1101 manages design documents. The management unit 1101 manages the linking of multiple design documents based on multiple categories, which are structured in a hierarchical manner for classifying multiple design documents, and multiple items that define the content of the documents. The linking of design documents is also called the relationship between design documents. The management unit 1101 stores information classifying a design document into one of the multiple categories in the storage unit 120. The management unit 1101 stores information indicating at least one item associated with a design document in the storage unit 120. The management unit 1101 may also store information indicating the hierarchy of design documents and categories in the storage unit 120. Information indicating the hierarchy of categories is, for example, information indicating the level corresponding to a category. The management unit 1101 may also store information indicating items common to multiple design documents in the storage unit 120.

[0062] The generation processing unit 1102 performs processing with the generation AI system 3. The generation processing unit 1102 performs processing in cooperation with the generation AI system 3. The generation processing unit 1102 acquires data from the generation AI system 3 via the communication interface 14. The generation processing unit 1102 outputs data to the generation AI system 3 via the communication interface 14.

[0063] The generation processing unit 1102 generates instruction statements related to the modification of design documents and inputs the design documents and instruction statements to the generation AI system 3. The design documents may be all design documents relating to the target project. The design documents may be some of the design documents relating to the target project. The design documents may be information that identifies the design documents relating to the target project. The design documents include the target documents. The target documents indicate the modified design documents among multiple design documents. The target documents are also called modified documents. Modifications to design documents include, for example, modifications made by user operations on user terminal 2. Modifications include, for example, various modifications to design documents. Modifications include insertion, updating, deletion, etc.

[0064] The command statement may include, for example, a command statement for generating the result of modifying other design documents based on a change in the target document. The command statement may include, for example, a command statement for processing changes to each design document classified in a lower category than the category of the target document associated with the target document. The command statement may also include a command statement for identifying the changed part of the target document. The changed part may be, for example, an item that has been changed. The changed part may also be the location, line number, etc., of the text that has been changed. The command statement may also include a command statement for identifying the part of other design documents related to the changed part of the target document. The part of other design documents related to the changed part is also called the related part. The related part may be, for example, an item related to the item that has been changed. The related part may also be the location, line number, etc., of text related to the location, line number, etc., of the text that has been changed. The related part may be a part that is affected by a change in a higher category. The related part may be a part that needs to be changed as a result of a change in a higher category. The related part is included in design documents in a lower category than the target document.

[0065] The command statement may include information indicating the category of the target document. The command statement may also include information indicating the target item of the target document. The target item indicates the item that has been changed in the target document. The command statement may also include information indicating, for example, the output format of the response. The command statement is also called a question or prompt.

[0066] The generation processing unit 1102 obtains a response to the instruction from the generation AI system 3. Based on the fact that the target document among multiple design documents has been changed, the generation processing unit 1102 obtains the change results of each design document classified into a lower category than the category of the target document associated with the target document from the generation AI system 3. In the following explanation, "obtain" can be read as "receive".

[0067] The generation processing unit 1102 may, in response to a request from the generation AI system 3, collect information necessary for generating a response from the storage unit 120 or an external storage device and input it to the generation AI system 3.

[0068] The calculation unit 1103 calculates the amount of change in the target document and the design documents in categories lower than the target document's category, based on the change results. For example, the calculation unit 1103 calculates the amount of change from the initial version to the current version of the target document. The calculation unit 1103 also calculates the amount of change from the initial version to the current version of the design documents in categories lower than the target document's category, linked to the target document. The calculation unit 1103 may also calculate the amount of change based on the string difference between the initial version and the modified version of the target document. The modified version is also called the current version. The current version is also called the latest version. The calculation unit 1103 may also calculate the amount of change in the target document using, for example, the Levenshtein distance, Gestalt distance, Jalowinkler distance, etc. For example, the calculation unit 1103 may calculate the amount of change from the initial version to the current version of the target document using Equation 1. Here, the amount of change is "△S t ", the current version of the document is "S t The initial version of the documentation will be designated as "S0".

[0069]

number

[0070] The calculation unit 1103 may calculate the amount of change from the initial version to the current version of a set of multiple design documents. The set of multiple design documents may be the target document and documents of its subcategories. The set of multiple design documents may be all the design documents of the target project. The set of multiple design documents may be predetermined design documents from the design documents of the target project. The predetermined design documents represent some of the design documents of the target project. The predetermined design documents are, for example, design documents selected by the user. The set of multiple design documents is just one example of a set of multiple documents. The calculation unit 1103 may calculate the amount of change for all the design documents of the target project. The calculation unit 1103 may calculate the amount of change from the initial version of the set of multiple design documents by summing up the amount of change for all the design documents of the target project. For example, the calculation unit 1103 may calculate the amount of change from the initial version to the current version of the set of multiple design documents using Equation 2. Here, the total amount of change for all the design documents of the target project at each point in time t is given by "△S t ", the total number of changed documents is "N", the index of the document is "i", and the value of document i at time t is "S i,t ", initial value of document i "S i,0 " is the correct choice.

[0071]

number

[0072] The calculation unit 1103 may calculate the amount of changes from the initial version to the current version of a set of multiple design documents using any method. The calculation unit 1103 may also calculate the amount of changes from the previous version to the current version of a set of multiple design documents.

[0073] The calculation unit 1103 may calculate a derivative value based on the amount of change from the initial version of a set of multiple design documents. The calculation unit 1103 may also calculate a derivative value based on the amount of change for all design documents of the target project. For example, the calculation unit 1103 may calculate a derivative value based on the amount of change from the initial version to the current version of a set of multiple design documents using Equation 3. Here, the difference is "diff(f)", the amount of change in the previous version is "f(x)", and the amount of change in the current version is "f(x+△x)".

[0074]

number

[0075] The calculation unit 1103 may calculate the total amount of changes from the initial version to any version of a set of multiple design documents. The calculation unit 1103 may also calculate the amount of changes from the initial version to any version for all design documents of the target project. The calculation unit 1103 may, for example, calculate the integral of the amount of changes from the initial version to any version for all design documents. For example, the calculation unit 1103 may calculate the total amount of changes from the initial version to any version of a set of multiple design documents using Equation 4. Here, let the area be "A", the initial version be "a", and the current version be "b".

[0076]

number

[0077] The calculation unit 1103 stores the calculated change amount results in the storage unit 120, linking them to each design document. The calculation unit 1103 may also store the change amount calculation results in the storage unit 120, linking them to the version. The calculation unit 1103 may update the change amount stored in the storage unit 120 based on the calculation of the change amount for the design document. The calculation unit 1103 stores the change amount calculation results in the storage unit 120 each time the version changes.

[0078] The display processing unit 1104 outputs visualization information to the user terminal 2 via the communication interface 14, which visualizes the amount of change in at least one of the multiple design documents. The at least one design document may be the target document. The at least one design document may include documents in a subcategory of the target document. The at least one design document may be all the design documents of the target project. The visualization information may, for example, show the amount of change from the initial version of any one of the multiple design documents. The visualization information may, for example, show the amount of change from the initial version of a set of multiple design documents. The visualization information may, for example, show the derivative value based on the amount of change from the initial version of a set of multiple design documents. The visualization information may, for example, show the total amount of change from the initial version to any version of a set of multiple design documents. The visualization information may, for example, be a graph showing the amount of change. The visualization information may include information to display an alert when the amount of change exceeds a predetermined value. The predetermined value may, for example, be a value indicating a sudden change. The predetermined value may, for example, be an indicator value that shows that the amount of change has a significant impact on the project. Significant impact on the project indicates, for example, a high probability of accidents or major problems occurring during the project. The alert may also be information that displays the amount of change in question in a different manner from other changes. The display manner may include color, size, brightness or luminance, background color, background brightness or luminance, or flashing display. The alert may also include, for example, a message indicating that the amount of change exceeds a predetermined value.

[0079] (Example of operation) The procedure for processing by the information processing system S will be explained. In the following explanations focusing on Management Server 1, Management Server 1 may be read as Processor 11 or Control Unit 110. In the explanations focusing on User Terminal 2, User Terminal 2 may be read as the processor of User Terminal 2. In the explanations focusing on Generative AI System 3, Generative AI System 3 may be read as the processor of Generative AI System 3 or the generative model.

[0080] The processing procedure described below is merely an example, and each process may be modified as much as possible. Furthermore, depending on the embodiment, steps in the processing procedure described below may be omitted, replaced, or added as appropriate.

[0081] The following process assumes that the design documents are changed while the target project is in progress. The target project refers to the project in which software or other development work is carried out. For example, let's assume that the design documents are changed when the requirements definition and design of the target project are completed and the project moves into the development phase. The design documents are changed, for example, by the person in charge of the target project. The person in charge changes the design documents on user terminal 2 and then sends the changed design documents to management server 1.

[0082] The design documents are classified into several categories: "Business Requirements," "Non-Functional Requirements," "Data Requirements," "Functional Requirements," and "Screen Requirements." These categories are structured in a hierarchical manner, with "Business Requirements" being the highest-level category, as shown in Figure 3 or Figure 6. For example, "Non-Functional Requirements" is a lower-level category than "Business Requirements." Similarly, "Data Requirements" is a lower-level category than "Non-Functional Requirements." "Functional Requirements" is a lower-level category than "Data Requirements." "Screen Requirements" is a lower-level category than "Functional Requirements."

[0083] Each design document contains information on at least one item. Multiple design documents are linked based on category and item. Linked design documents are also called related documents.

[0084] User terminal 2 modifies the design document based on user operations (step S1). In step S1, for example, user terminal 2 outputs the modified design document (modified document) to management server 1 based on user operations. The modified design document is an example of the target document.

[0085] The control unit 110 of the management server 1 receives change data from the user terminal 2 via the communication interface (I / F) 14 (step S101). The processing in step S101 may also be carried out by the management unit 1101 implemented by the control unit 110. In step S101, for example, the control unit 110 receives change data via the communication interface 14 based on the user's operation on the user terminal 2. The control unit 110 may store the change data in the storage unit 120.

[0086] The control unit 110 performs a change process (step S102). The process in step S102 may also be performed by the generation processing unit 1102 implemented by the control unit 110. In step S102, for example, the control unit 110 generates an instruction statement related to the change process of the design document. The instruction statement is, for example, an instruction statement for generating a change result based on the fact that the target document has been changed. The change result is, for example, an instruction statement for generating a change result in which each document classified in a lower category than the category of the target document associated with the target document has been changed. The change result includes a design document in which related documents classified in a lower category than the target document have been changed.

[0087] The control unit 110 inputs design documents and command statements to the generation AI system 3 via the communication interface 14. The design documents include the target documents. The design documents may include all of the design documents for the target project. The design documents may include only some of the design documents for the target project. The control unit 110 inputs related information to the generation AI system 3 via the communication interface 14.

[0088] The generating AI system 3 receives design document strings and instruction statements from the management server 1. The generating AI system 3 receives related information from the management server 1. The generating AI system 3 generates change results based on the design documents and instruction statements. The change results are an example of a response to an instruction statement. The generating AI system 3 identifies the changed parts of the target document based on the target document. The generating AI system 3 identifies the relevant parts of other design documents related to the changed parts (step S201). In step S201, for example, the generating AI system 3 identifies the relevant parts of other design documents related to the changed parts based on the target document and related information. The generating AI system 3 may identify design documents that contain items related to the changed parts from among the design documents classified in a lower category than the category of the target document as related documents. The generating AI system 3 may identify the relevant parts from among the related documents.

[0089] The generating AI system 3 modifies the related documents (step S202). In step S202, for example, the generating AI system 3 modifies the relevant parts of the related documents. The generating AI system 3 modifies the relevant parts for all design documents classified into subcategories of the target document category.

[0090] The generation AI system 3 returns the change results (step S203). In step S203, for example, the generation AI system 3 outputs the design document with the relevant parts changed as the change result to the management server 1.

[0091] Steps S201 to S203 are repeated for all design documents classified into subordinate categories related to the target document. For example, in step S201, the generating AI system 3 identifies the related parts of the design documents (related documents) classified into a category one level below the target document that are related to the changed parts. In step S202, the generating AI system 3 modifies the related parts of the related documents classified into a category one level below the target document. In step S203, the generating AI system 3 returns the design document with the modified related parts as the result of the change. Then, returning to step S201, the generating AI system 3 identifies the related parts of the design documents (related documents) classified into a category one level below the modified design document, based on the change result returned in step S203. In step S202, the generating AI system 3 modifies the related parts of the related documents classified into a category one level below the modified design document. In step S203, the generating AI system 3 returns the design document as the change result, in which the relevant parts of the related documents classified in a category one level lower than the changed design document have been changed. In this way, the generating AI system 3 repeats steps S201 to S203 until the necessary changes have been made to all design documents classified in lower categories related to the target document. Alternatively, the generating AI system 3 may perform step S203 after the changes have been made to the design documents in all lower categories. In this case, in step S203, the generating AI system 3 may return the change results for all design documents in all lower categories.

[0092] The control unit 110 of the management server 1 acquires the change results from the generation AI system 3 via the communication interface 14. Based on the change results, the control unit 110 calculates the amount of change in the design documents of the target project (step S103). The processing in step S103 may also be performed by the calculation unit 1103 implemented by the control unit 110. In the first example, the control unit 110 calculates the amount of change from the initial version to the current version of the target document. The control unit 110 may also calculate the amount of change from the initial version to the current version of related documents in a subcategory of the target document. The control unit 110 may calculate the amount of change using, for example, Equation 1. In the second example, the control unit 110 calculates the amount of change from the initial version to the current version of a set of multiple design documents. The control unit 110 may also calculate the amount of change from the initial version to the current version of all design documents in the target project. The control unit 110 may also calculate the amount of change from the initial version to the current version of a predetermined design document among the design documents of the target project. The control unit 110 may also calculate the amount of change using, for example, Equation 2.

[0093] In the third example, the control unit 110 calculates a derivative value based on the amount of change from the initial version of a set of multiple design documents. The control unit 110 may also calculate a derivative value based on the amount of change from the initial version to the current version of the target document and related documents of its subcategories. The control unit 110 may also calculate a derivative value based on the amount of change from the initial version to the current version of all design documents in the target project. The control unit 110 may also calculate a derivative value based on the amount of change from the initial version to the current version of a predetermined design document among the design documents of the target project. The control unit 110 may, for example, calculate the derivative value based on the amount of change using Equation 3.

[0094] In the fourth example, the control unit 110 calculates the total amount of changes from the initial version to any given version of a set of multiple design documents. The control unit 110 may also calculate the total amount of changes from the initial version to the current version of the target document and related documents of its subcategories. The control unit 110 may also calculate the total amount of changes from the initial version to the current version of all design documents in the target project. The control unit 110 may also calculate the total amount of changes from the initial version to the current version of a predetermined design document among the design documents of the target project. The control unit 110 may calculate the total amount of changes using, for example, Equation 4.

[0095] The control unit 110 may also calculate the amount of changes from the initial version to any version of the target document or a collection of multiple design documents. The control unit 110 may also calculate the amount of changes from the previous version to the current version of the target document or a collection of multiple design documents.

[0096] The control unit 110 outputs visualization information to the user terminal 2 via the communication interface 14, which visualizes the amount of change in at least one of the multiple design documents (step S104). The processing in step S104 may also be carried out by the display processing unit 1104 implemented by the control unit 110.

[0097] User terminal 2 receives visualization information from management server 1. Based on the visualization information, user terminal 2 displays information indicating the amount of change (step S3). For example, user terminal 2 displays information indicating the amount of change for at least one design document among multiple design documents. User terminal 2 may also display information indicating the amount of change from the initial version of the target document. User terminal 2 may also display information indicating the amount of change from the initial version of a set of multiple design documents. User terminal 2 may also display information indicating the derivative value based on the amount of change from the initial version of a set of multiple design documents. User terminal 2 may also display information indicating the total amount of change from the initial version to any version of a set of multiple design documents. For example, user terminal 2 may display a graph showing the amount of change. User terminal 2 may display an alert if the amount of change exceeds a predetermined value.

[0098] In this example, the management server 1 can receive information that a part of the design document has been changed, and then have the generation AI system 3 make changes to the related documents. For example, the management server 1 can input related information of the design document of the target project into the generation model, allowing the generation model to identify the related documents and related parts of the changed document. Therefore, the management server 1 can allow the generation model to appropriately determine the scope of the changes to affect other design documents. The management server 1 can then obtain the design document with the changes appropriately reflected from the generation AI system 3. The user can then make changes to the entire design document of the target project quickly and appropriately. In this way, the management server 1 can consistently change related documents.

[0099] Furthermore, the management server 1 can calculate the amount of change based on the change results generated by the generation AI system 3. Therefore, the management server 1 can appropriately estimate the impact of design changes on project progress, which was previously predicted by project managers, etc. In addition, the management server 1 can visualize the amount of change in the design documents. Therefore, users can easily recognize the impact of design changes on project progress based on the visualized information. For example, project managers, etc. can predict the convergence of the project based on the visualized amount of change. If the amount of change does not converge, project managers, etc. can consider reviewing the project. In this way, by visualizing the amount of change in the design documents, the management server 1 can streamline the management of design documents or project management.

[0100] The visualization information for the amount of change will be explained with reference to Figures 9 to 12. Figure 9 shows an example of a display of visualization information for the amount of change according to the embodiment. Figure 9 is a graph showing the amount of changes from the initial version to the current version of the document in question. In the visualization graph shown in Figure 9, the vertical axis represents the amount of change, and the horizontal axis represents the version. For example, the graph in Figure 9 plots the amount of change calculated based on Equation 1 for each version. Figure 9 shows the amount of changes in the document in question from the initial version to the current version, with the initial version designated as "V0".

[0101] For example, Figure 9 shows that the amount of changes from the initial version to version 1 is significant in the target document. Also, Figure 9 shows that no changes were made from version 3 to version 5 in the target document. In this way, the amount of changes for each version of the target document is visualized, allowing users to easily grasp the changes visually.

[0102] Figure 10 shows another example of the display of visualization information of the change amount according to the embodiment. Figure 10 is a graph showing the amount of changes from the initial version to the current version of a collection of multiple design documents. In the visualization graph shown in Figure 10, the vertical axis represents the amount of change, and the horizontal axis represents the version. For example, the graph in Figure 10 plots the amount of change calculated based on Equation 2 for each version. Figure 10 shows the amount of changes from the initial version to the current version of the collection of all design documents for the target project, with the initial version designated as "V0".

[0103] For example, Figure 10 shows that the overall design documentation for the target project underwent significant changes from the initial version to version 1. Furthermore, while Figure 9 shows no changes between version 3 and version 5, Figure 10 incorporates changes to other design documents, resulting in an overall increase in the total amount of changes to the design documentation. In this way, the total amount of changes to the design documentation can be visualized based on the changes made to the target document. Therefore, users can easily grasp the overall amount of changes to the design documentation visually.

[0104] Figure 11 shows yet another example of the display of visualization information of the change amount according to the embodiment. Figure 11 is a graph showing the derivative value based on the amount of change from the initial version of a set of multiple design documents. In the visualization graph shown in Figure 11, the vertical axis represents the amount of change, and the horizontal axis represents the version. For example, the graph in Figure 11 plots the derivative value based on the amount of change calculated based on Equation 3 for each version. Figure 11 shows the derivative value based on the amount of change of the set of all design documents for the target project from the initial version to the current version, with the initial version designated as "V0".

[0105] For example, the graph in Figure 11 shows that as the derivative value based on the amount of change approaches zero, the project is converging. Furthermore, the graph in Figure 11 also indicates that the changes are minor as the derivative value based on the amount of change approaches zero. If the derivative value based on the amount of change does not approach zero, or if it rises sharply, it suggests a high probability that an accident or serious problem has occurred during the project. In this way, Figure 11 visually shows the degree to which changes in the design documents affect the project. Therefore, users can easily and visually grasp the impact of changes in the documents on the entire project.

[0106] Figure 12 shows yet another example of the display of visualization information of the change amount according to the embodiment. Figure 12 is a graph showing the total amount of changes from the initial version to any given version of a set of multiple design documents. In the visualization graph shown in Figure 12, the vertical axis represents the amount of change, and the horizontal axis represents the version. For example, the graph in Figure 12 plots the total amount of changes calculated based on Equation 4 for each version. Figure 12 shows the total amount of changes from the initial version to the current version of the set of all design documents for the target project, with the initial version designated as "V0".

[0107] For example, the graph in Figure 12 shows the total amount of changes as the area representing the changes from the initial version to the current version. For example, area Ar1 shows the total amount of changes from the initial version to version 4. Area Ar2 shows the total amount of changes from the initial version to version 10.

[0108] For example, the total amount of changes approximates the project's effort. Therefore, by referring to the effort based on the initial version's design documentation, it is possible to estimate the effort based on the current version's design documentation. For example, let's consider a case where the estimated effort at version 4 was 10. If the area of ​​changes from the initial version to version 10 is three times the area of ​​changes from the initial version to version 4, then the effort based on the version 10 design documentation can be estimated to be 30. In this way, Figure 12 visualizes the total amount of changes in the design documentation, visually showing the increase in effort based on the current version's design documentation. Therefore, users can easily and visually grasp the impact of changes to the target documentation on the overall effort of the project.

[0109] (effect) The information processing program in this embodiment can cause a computer to manage the linking of multiple documents based on multiple categories arranged in a hierarchical structure for classifying documents and multiple items that define the content of the documents, and to obtain the results of changes to each document classified in a lower category than the target document linked to the target document from a generation model, based on the fact that the target document among the multiple documents has been changed. For example, since the management server 1 manages design documents classified in a hierarchical category structure, it can input information to the generation AI system 3 to identify design documents in a lower category than the target document linked to the target document. As a result, the generation AI system 3 can change related documents classified in a lower category than the target document's category. By causing the generation AI system 3 to change related documents classified in a lower category than the target document's category, the management server 1 can appropriately identify the scope of the impact of the change to the target document and change the design documents within that scope. As a result, the management server 1 can simplify the change processing by the generation AI system 3. In this way, the information processing program can consistently change related documents in response to changes in design documents.

[0110] The information processing program of the embodiment can cause a computer to calculate the amount of change to the target document and the subordinate category documents linked to the target document based on the change results, and to output visualization information that visualizes the amount of change to at least one of the multiple documents. For example, the management server 1 calculates the amount of change to the target document and related documents based on the change results obtained from the generation AI system 3. Based on the calculated amount of change, the management server 1 outputs information that visualizes the amount of change to at least one of the design documents to the user terminal 2. Therefore, the management server 1 can provide the user with information that visualizes the amount of change to the target document. The user can visually recognize the amount of change to the target document. In addition, the management server 1 can provide the user with information that visualizes the amount of change to other design documents when the changes to the target document are reflected in related documents, and the amount of change to the design documents of the entire project. The user can visually recognize the amount of change not only to the target document, but also to other design documents and the entire project. Therefore, if the amount of change is converging, the user can predict the convergence of the project, and if the amount of change is expanding, the user can predict project accidents and problems. In this way, the management server 1 can provide users with information that visualizes the degree to which changes to design documents affect the project. Based on the change results generated by the generation AI system 3, the management server 1 can quickly and accurately provide information on the impact of changes to specific documents on the project.

[0111] The information processing program of the embodiment can cause a computer to output information indicating the amount of change from the initial version of any one of several documents. For example, the management server 1 can provide the user with information indicating the amount of change from the initial version to the current version of the target document. Therefore, the user can easily visually recognize the amount of change in the target document. The management server 1 can provide the user with information that allows them to easily visually recognize the amount of change for any of the multiple design documents.

[0112] The information processing program of the embodiment can cause a computer to output information indicating the amount of change from the initial version of a collection of multiple documents. For example, the management server 1 can provide the user with information indicating the amount of change from the initial version to the current version for all design documents of the target project. Therefore, the user can easily grasp the total amount of change for the entire target project visually. The user can easily grasp the impact of changes to the target documents on the entire project. The management server 1 can provide the user with information that allows them to easily recognize the amount of change for a collection of multiple design documents visually.

[0113] The information processing program of the embodiment can cause a computer to output information showing the derivative value based on the amount of change from the initial version of a set of multiple documents. For example, the management server 1 can provide the user with information showing the derivative value based on the amount of change from the initial version to the current version for all design documents of the target project. Therefore, the user can understand the impact of changes to the target documents on the project based on the derivative value. For example, the user can recognize that the change is minor as the derivative value approaches 0. The user can recognize that if the derivative value does not approach 0 or rises sharply, there is a high possibility that an accident or serious problem has occurred in the target project. In this way, the management server 1 can provide the user with information that allows for easy visual recognition of the derivative value based on the amount of change for a set of multiple design documents.

[0114] The information processing program of this embodiment can cause a computer to output information indicating the total amount of changes from the initial version to any given version of a set of multiple documents. For example, the management server 1 can provide the user with information indicating the total amount of changes from the initial version to the current version of all design documents for the target project. Therefore, the user can predict the change in man-hours corresponding to the changes based on the total amount of changes. The user can easily and visually grasp the impact that changes to the target documents have on the man-hours of the entire target project. In this way, the management server 1 can provide the user with information that allows them to easily and visually recognize the total amount of changes for a set of multiple design documents.

[0115] (Other embodiments) The above-described embodiment was explained using design documents in system development work as an example, but is not limited to this. The above-described embodiment is applicable to various tasks that manage multiple documents. In this case, design documents may be read as documents. For example, it is applicable to multiple documents such as design documents and regulations handled in various tasks such as real estate and construction. Multiple documents include documents that are related to each other. For example, multiple documents include documents classified into multiple categories arranged in a hierarchical structure. The hierarchical structure and categories can be changed depending on the task to which it is applied. Multiple items can be changed depending on the task to which it is applied.

[0116] In the embodiments described above, the information processing system S was described as including a management server 1, a user terminal 2, and a generation AI system 3, but it is not limited to this. The information processing system S may also be one in which the functions of two or more devices included in the information processing system S are realized by a single device.

[0117] The information processing system may be implemented as a single device, such as management server 1, or as multiple devices with distributed functions.

[0118] The embodiments described above may apply not only to the apparatus but also to the methods performed by the apparatus. The embodiments described above may apply to a program that can cause the computer of the apparatus to perform each function. The embodiments described above may apply to a recording medium that stores the program. The embodiments described above may apply not only to the system but also to the methods performed by multiple elements included in the system.

[0119] A processing circuit includes one or more circuits that perform multiple processes through multiple functions. For example, the circuit may be, but is not limited to, a processor, an ASIC (Application Specific Integrated Circuit), or an FPGA (Field-Programmable Gate Array).

[0120] Each of the one or more circuits that make up a processing circuit performs one or more of the multiple processes. If the processing circuit consists of a single circuit, the single circuit performs all of the multiple processes. If the processing circuit consists of multiple circuits, each of the multiple circuits performs some of the multiple processes. Some of the multiple processes may be one of the multiple processes, or two or more of the multiple processes. If the processing circuit consists of multiple circuits, the multiple circuits may be contained in a single device, or they may be distributed across multiple devices.

[0121] The program may be transferred while stored in the device, or it may be transferred without being stored in the device. In the latter case, the program may be transferred via a network, or it may be transferred while recorded on a recording medium. The recording medium is a non-temporary tangible medium. The recording medium is a computer-readable medium. The recording medium can be any medium that is capable of storing a program and is readable by a computer, such as a CD-ROM or memory card, and its form is not limited.

[0122] Although embodiments of the present invention have been described in detail above, the above description is merely illustrative in all respects of the present invention. Needless to say, various improvements and modifications can be made without departing from the scope of the present invention. In other words, when implementing the present invention, specific configurations may be adopted as appropriate depending on the embodiment.

[0123] In short, this invention is not limited to the embodiments described above, and in the implementation stage, the components can be modified and materialized without departing from the gist of the invention. Furthermore, various inventions can be formed by appropriately combining the multiple components disclosed in the embodiments. For example, some components may be deleted from all the components shown in the embodiments. Moreover, components from different embodiments may be appropriately combined.

[0124] (Note) The above-described embodiment may be represented as follows: (1) To the computer, A function to manage the linking of multiple documents based on multiple categories arranged in a hierarchical structure for classifying documents, and multiple items that define the content of the documents. Based on the fact that the target document among the aforementioned multiple documents has been changed, a function is provided to obtain from the generation model the change results for each document that is classified in a lower category than the category of the target document that is associated with the target document, An information processing program capable of executing [the specified action]. (2) To the computer, Based on the aforementioned change results, a function is provided to calculate the amount of change in the target document and the subordinate category documents linked to the target document. A function to output visualization information that visualizes the amount of change in at least one of the aforementioned multiple documents, An information processing program described in (1) that is capable of executing the above. (3) The visualization information is information that shows the amount of change from the initial version of any one of the multiple documents. (2) The information processing program described above. (4) The visualization information is information that shows the amount of change from the initial version of the collection of multiple materials. (2) The information processing program described above. (5) The visualization information is information that shows the differential value based on the amount of change from the initial version of the set of multiple materials. (2) The information processing program described above. (6) The visualization information is information that shows the total amount of changes from the initial version to any given version of the set of multiple materials. (2) The information processing program described above. (7) To manage the linking of multiple documents based on multiple categories, which are structured in a hierarchical manner for classifying documents, and multiple items that define the content of the documents, Based on the fact that the target document among the aforementioned multiple documents has been changed, the change results of each document that is classified into a lower category than the category of the target document linked to the target document are obtained from the generation model, An information processing method comprising the following: (8) A management unit that manages the linking of multiple documents based on multiple categories arranged in a hierarchical structure for classifying documents, and multiple requirement items that define the content of the documents, Based on the fact that the target document among the aforementioned multiple documents has been changed, a generation processing unit obtains the change results of each document that is classified into a lower category than the category of the target document linked to the target document from the generation model, An information processing device equipped with the following features. [Explanation of Symbols]

[0125] 1...Management server, 2...User terminal, 3...Generation AI system, 11...Processor, 12...Main memory, 13...Auxiliary storage device, 14...Communication interface, 110...Control unit, 120...Storage unit, 1101...Management unit, 1102...Generation processing unit, 1103...Calculation unit, 1104...Display processing unit, 1201...Data storage area, 1202...Related information storage area, 1203...Change amount storage area, S...Information processing system.

Claims

1. On the computer, A function to manage the linking of multiple documents based on multiple categories arranged in a hierarchical structure for classifying documents, and multiple items that define the content of the documents. Based on the fact that the target document among the aforementioned multiple documents has been changed, a function is provided to obtain from the generation model the change results for each document that is classified in a lower category than the category of the target document that is associated with the target document, An information processing program capable of executing [the specified action].

2. On the computer, Based on the aforementioned change results, a function is provided to calculate the amount of change in the target document and the subordinate category documents linked to the target document. A function to output visualization information that visualizes the amount of change in at least one of the aforementioned multiple documents, An information processing program according to claim 1 that can perform the following actions.

3. The aforementioned visualization information is information indicating the amount of change from the initial version of any one of the multiple documents. The information processing program according to claim 2.

4. The aforementioned visualization information is information indicating the amount of change from the initial version of the collection of multiple materials. The information processing program according to claim 2.

5. The aforementioned visualization information is information that shows the differential value based on the amount of change from the initial version of the set of multiple materials. The information processing program according to claim 2.

6. The aforementioned visualization information is information that shows the total amount of changes from the initial version to any given version of the set of multiple documents. The information processing program according to claim 2.

7. This involves managing the linking of multiple documents based on multiple categories structured in a hierarchical structure for classifying documents, and multiple items that define the content of the documents. Based on the fact that the target document among the aforementioned multiple documents has been changed, the change results of each document that is classified into a lower category than the category of the target document linked to the target document are obtained from the generation model, An information processing method comprising the following:

8. A management unit manages the linking of multiple documents based on multiple categories, which are structured in a hierarchical manner for classifying documents, and multiple requirement items that define the content of the documents. Based on the fact that the target document among the aforementioned multiple documents has been changed, a generation processing unit obtains the change results of each document that is classified into a lower category than the category of the target document linked to the target document from the generation model, An information processing device equipped with the following features.

Images