Information processing program, information processing device, and information processing method

Abstract

To reduce workloads related to management of development documents in system development and to improve quality of developed products.SOLUTION: An information processing program according to the present application causes a computer to execute: an extraction step of extracting information related to development documents from deliverable record documents in response to a prescribed operation with respect to the deliverable record documents in which information related to the development documents, which are deliverables in system development, is described; and a recording step of associating and recording the information related to the development documents extracted by the extraction step. The extraction step extracts the information described in the development documents from the deliverable record documents, and the recording step associates and records the information described in the development documents extracted by the extraction step.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an information processing program, an information processing device, and an information processing method. [Background technology]

[0002] Conventionally, there are known techniques for supporting the management of documents (hereinafter sometimes referred to as "development documents") generated in each development stage of a software or system development process. For example, a technique is known that correlates design document information related to a project with discussion information related to recording project activities. Then, based on the correlated information, a technique is known that retains the page counts of software design documents created as the project progresses. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-47732 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above-mentioned conventional technology only keeps track of the number of pages in the software design documents that are created as the project progresses, and therefore does not necessarily reduce the workload associated with managing development documents in system development.

[0005] The present application aims to provide an information processing program, an information processing device, and an information processing method that can reduce the workload associated with managing development documents in system development. [Means for solving the problem]

[0006] The information processing program of the present application causes a computer to execute an extraction procedure for extracting information about a first document from a second document that describes information about a first document that is an output of system development, in response to a predetermined operation on the second document, and a recording procedure for recording the information about the first document extracted by the extraction procedure in association with the information.

[0007] The information processing program of the present application causes a computer to execute the following steps: an extraction step of extracting information about a first document from a second document that describes information about a first document that is a deliverable in system development, in response to a predetermined operation on the second document; a recording step of associating and recording the information about the first document extracted by the extraction step; and a generation step of generating, based on the information recorded by the recording step, a development progress display image that includes first progress information that indicates the current progress status of the system development.

[0008] The information processing program of the present application causes a computer to execute the following steps: an extraction step of extracting information about a first document from a second document that describes information about the first document, which is a deliverable in system development, in accordance with a predetermined operation on the second document; a recording step of associating and recording the information about the first document extracted by the extraction step; and a generation step of generating, based on the information recorded by the recording step, a development progress display image that includes information that associates second progress information that indicates the progress of the system development at each point in time in the system development with time information that indicates each point in time in the system development. [Effects of the Invention]

[0009] According to one aspect of the embodiment, it is possible to reduce the workload associated with managing development documents in system development. [Brief explanation of the drawings]

[0010] [Figure 1]FIG. 1 is a diagram illustrating an example of the configuration of an information processing system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of the information processing device according to the embodiment. [Figure 3] FIG. 3 is a flowchart showing a processing procedure performed by the information processing device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a review request operation for a development document according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of an email generated in response to an operation to request a review of a development document according to the embodiment. [Figure 6] FIG. 6 is a diagram for explaining an example of a confirmation operation of a development document according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of an email generated in response to a confirmation operation of a development document according to the embodiment. [Figure 8] FIG. 8 is a diagram showing an example of the content of a deliverable record document and information to be extracted according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the contents of a system requirement definition document and information to be extracted according to the embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the contents of the test specifications and information to be extracted according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of data stored in the development deliverable database according to the embodiment. [Figure 12] FIG. 12 is a diagram for explaining an overview of a development progress display image according to the embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a development progress display image (development function) according to the embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a development progress display image (plan / system requirements definition) according to the embodiment. [Figure 15] FIG. 15 is a diagram showing an example of a development progress display image (design) according to the embodiment. [Figure 16] FIG. 16 is a diagram showing an example of a development progress display image (approval history) according to the embodiment. [Figure 17] FIG. 17 is a diagram showing an example of a development progress display image (review indications) according to the embodiment. [Figure 18] FIG. 18 is a diagram showing an example of a development progress display image (items to be handed over) according to the embodiment. [Figure 19] FIG. 19 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of the information processing device. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an information processing program, an information processing device, and an information processing method according to the present application (hereinafter referred to as "embodiments") will be described in detail with reference to the drawings. Note that the information processing program, the information processing device, and the information processing method according to the present application are not limited to these embodiments. Furthermore, the same components in the following embodiments will be designated by the same reference numerals, and duplicated descriptions will be omitted.

[0012] (Embodiment) 1. Introduction In the past, system developers and development managers (hereinafter referred to as "development stakeholders") were overwhelmed with managing development documents (hereinafter referred to as "deliverables" or "first documents") generated at each stage of the system development process, making it difficult for them to focus on creating the development documents. Here, the development documents according to this embodiment may be direct deliverables of development, such as development plans, requirements definition documents, various design documents (screen design documents, interface design documents, program design documents, non-functional design documents), and test specifications (specifications for various tests, such as unit tests, integration tests, comprehensive tests, and acceptance tests), or indirect deliverables of development, such as minutes of development-related meetings and checklists listing items to be checked during reviews. Furthermore, the development documents may be documents written in natural language.

[0013] Specifically, tasks for managing development documents include the task of gathering information about development documents (hereinafter referred to as "gathering tasks"). For example, gathering tasks include confirmation tasks related to the approval status of development documents, the status of writing in development documents, the status of testing for functions to be developed, the status of source code, etc., as well as meetings with related organizations, internal organizations, and higher-level organizations. The tasks to be collected also include collecting information on the history of all operations performed on development documents, information on the collection of management information for development documents, information on the history of emails sent to development stakeholders, information on the confirmation history of development documents, information on the development project in general (information such as planned release date and project name), information indicating what modifications will be made at the functional level for each development project, information indicating what tests (tests) have been performed at the functional level for each development project and how many times, information indicating review findings at each development stage for each development project, information indicating items to be handed over at each development stage for each development project, information indicating the approval status from the person in charge of each approval department at each development stage for each development project, information indicating the creation status of each development document for each development project, and information indicating the creation status of design documents within each development document for each development project.

[0014] Additionally, tasks for managing development documents include the task of storing information about development documents (hereinafter referred to as "storage tasks"). For example, storage tasks include storing the information collected in the collection tasks and information (e.g., evidence) that corresponds to audits.

[0015] Additionally, tasks for managing development documents include the task of displaying information about development documents (hereinafter referred to as "displaying tasks"). For example, displaying tasks include the task of visualizing the development status, test status, system status, and audit information (for example, creating reports).

[0016] As mentioned above, the tasks involved in managing development documents involve many tasks, such as collecting, storing, and displaying documents, which places a burden on those involved in development. Furthermore, even if the tasks for managing development documents are implemented as workflows, particularly in organizations with many development projects, the workflows often focus on the approval process itself, which often results in in-depth confirmation of the contents of the development documents, potentially resulting in workflow-based management becoming a mere formality. When management becomes a mere formality, the management tasks become tasks that do not contribute to the system development process, hindering the progress of the system development process. As a result, even if the tasks for managing development documents are implemented as workflows, this can lead to a decline in productivity and quality in system development.

[0017] In response to this, the present inventors propose a technology for automating tasks for managing development documents (collecting, storing, and displaying). Specifically, an information processing program according to the present application extracts information about a development document from a deliverable record document (hereinafter sometimes referred to as a "second document"), which describes information about the development document, in response to a predetermined operation on the deliverable record document, and associates and records the extracted information about the development document. This reduces the burden on development personnel of collecting information about the development documents. Furthermore, the information processing program reduces the burden on development personnel of storing information about the development documents. Furthermore, since the information processing program reduces the burden on development personnel of collecting and storing information about the development documents, it reduces the burden on development personnel of managing development documents in system development. Furthermore, system development typically has a fixed development period and a fixed number of developers. Therefore, reducing the burden of tasks related to managing development documents in system development (so-called administrative tasks) allows developers to focus more on developing development products, such as development documents. Furthermore, if developers can focus on developing the development product, the quality of the development product will improve. In this way, the information processing program can reduce the workload related to managing development documents in system development, thereby improving productivity and quality in system development.

[0018] As described above, the deliverable record document records information related to development documents, which are deliverables created during the development process, as information in system development. Specifically, information such as the name of each development document, the process in which the development document was created, any issues raised in reviews of the development document, the approval history by the development manager, or the storage location of the development document may be recorded. Note that, for convenience of explanation, the term "document" is used, but the deliverable record document is not limited to a file format such as a document. For example, the deliverable record document may be a database that records information related to the development document.

[0019] Furthermore, an information processing program according to the present application extracts information about the development documents from the deliverable record document in response to a predetermined operation on the deliverable record document describing information about development documents in system development, associates and records the extracted information about the development documents, and generates an image (hereinafter, sometimes referred to as a "development progress display image") including first progress information indicating the current progress of the system development based on the recorded information. For example, the progress of the system development may be the creation status of the development documents (e.g., the writing status of the development documents). This allows the information processing program to reduce the workload of the development stakeholders in collecting information about the development documents. The information processing program also reduces the workload of the development stakeholders in storing information about the development documents. The information processing program also enables the development stakeholders to easily visually grasp the current progress of the system development, thereby reducing the workload of the development stakeholders in displaying information about the development documents. The information processing program also reduces the workload of the development stakeholders in collecting, storing, and displaying information about the development documents, thereby reducing the workload of the development stakeholders in managing the development documents in system development.

[0020] Furthermore, an information processing program according to the present application extracts information about the development documents from the deliverable record document in response to a predetermined operation on a deliverable record document describing information about development documents in system development, associates and records the extracted information about the development documents, and, based on the recorded information, generates an image (hereinafter, "development progress display image") including information associating second progress information indicating the progress of system development at each time point in the system development with time information indicating each time point in the system development. This allows the information processing program to reduce the workload of developers involved in collecting information about the development documents. The information processing program also reduces the workload of developers involved in storing information about the development documents. The information processing program also enables developers involved in visually and easily grasping the progress of system development at each time point in the system development, thereby reducing the workload of developers involved in displaying information about the development documents. The information processing program also reduces the workload of developers involved in collecting, storing, and displaying information about the development documents, thereby reducing the workload of developers involved in managing development documents in system development.

[0021] [2. Information Processing System Configuration] An example of the configuration of an information processing system 1 according to an embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the configuration of the information processing system 1 according to an embodiment. As shown in Fig. 1, the information processing system 1 includes a user terminal 10 and an information processing device 100. The user terminal 10 and the information processing device 100 are connected to each other via a predetermined communication network (network N) so as to be able to communicate with each other via wired or wireless communication.

[0022] The user terminal 10 is an information processing device used by a user who is involved in system development. For example, the user terminal 10 is an information processing device such as a desktop PC (Personal Computer) or a notebook PC. The user terminal 10 may also be a smart device such as a smartphone or tablet. The user terminal 10 has a screen such as a liquid crystal display, and accepts various operations from the user on display data of content (e.g., documents or images) displayed on the screen. Note that an operation performed on an area of ​​the screen where the content is displayed may be considered an operation on the content.

[0023] The user terminal 10 accepts input of information for the deliverable record document in accordance with the user's operation. The user terminal 10 also transmits the deliverable record document to the information processing device 100 in accordance with the user's operation. The user terminal 10 also accepts a predetermined operation for the deliverable record document in accordance with the user's operation. When the user terminal 10 accepts a predetermined operation, it transmits operation information related to the predetermined operation to the information processing device 100.

[0024] The information processing device 100 is an information processing device that executes an information processing program according to an embodiment. The information processing device 100 receives, from a user, a deliverable record document that describes information about development documents in system development. The information processing device 100 also receives a predetermined operation on the deliverable record document from the user. The information processing device 100 also extracts information about the development documents from the deliverable record document in response to the predetermined operation on the deliverable record document, and associates and records the extracted information about the development documents. The information processing device 100 also generates, based on the recorded information, a development progress display image that includes first progress information that indicates the progress of the system development at the current time point. The information processing device 100 also generates, based on the recorded information, a development progress display image that includes information that associates second progress information that indicates the progress of the system development at each time point in the system development with time information that indicates each time point in the system development.

[0025] 3. Configuration of Information Processing Device An example of the configuration of the information processing device 100 according to the embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of the configuration of the information processing device 100 according to the embodiment. The information processing device 100 includes a communication unit 110, a storage unit 120, and a control unit 130.

[0026] (Storage unit 120) The storage unit 120 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. Specifically, the storage unit 120 stores an information processing program according to the embodiment. The storage unit 120 also stores record table identification information for identifying a deliverable record document and information about the deliverable record document in association with each other. The information about the deliverable record document may include a system code and a system name for identifying a system to be developed. The information about the deliverable record document may include a development project number, a development project name, and a planned release date for identifying a project to be developed. The storage unit 120 also stores information about a development deliverable database 121 (see FIG. 11 ) that records information about the development process collected from development documents (described later). For example, the storage unit 120 includes the development deliverable database 121. The development deliverable database 121 is a database that records information about development. The development deliverable database 121 stores information about the development documents extracted from the deliverable record document by the extraction unit 132 in association with each other.

[0027] (Communication unit 110) The communication unit 110 is realized by a NIC (Network Interface Card), an antenna, etc. The communication unit 110 is connected to various networks by wire or wirelessly, and transmits and receives information to and from other information processing devices other than the information processing device 100, for example.

[0028] (control unit 130) The control unit 130 is a controller, and is realized, for example, by a CPU (Central Processing Unit) or an MPU (Micro Processing Unit) executing various programs stored in a storage device inside the information processing device 100 using RAM as a work area. The control unit 130 is also a controller, and is realized, for example, by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0029] The control unit 130 has a receiving unit 131, an extracting unit 132, a recording unit 133, and a generating unit 134 as functional units, and may realize or execute the information processing actions described below. Note that the internal configuration of the control unit 130 is not limited to the configuration shown in FIG. 2, and may be any other configuration that performs the information processing described below. Furthermore, each functional unit indicates a function of the control unit 130, and does not necessarily have to be physically distinct.

[0030] (Reception Department 131) The receiving unit 131 receives information about a deliverable record document that describes information about a development document, which is a deliverable in system development. Specifically, the user terminal 10 acquires necessary information from the deliverable record document, which is a spreadsheet into which data is entered in tabular format. Subsequently, the user terminal 10 transmits the information acquired from the deliverable record document to the information processing device 100. The receiving unit 131 receives information about the deliverable record document from the user terminal 10. For example, the receiving unit 131 receives information about the deliverable record document acquired from the deliverable record document, which is a spreadsheet. For example, the receiving unit 131 receives information about the deliverable record document that includes a system code and a system name that identify the system to be developed. The receiving unit 131 also receives information about the deliverable record document that includes a development project number, a development project name, and a planned release date that identify the project to be developed. When the receiving unit 131 receives information about the deliverable record document, the receiving unit 131 associates record table identification information that identifies the deliverable record document with the information about the deliverable record document and stores them in the development deliverable database 121. For example, the receiving unit 131 stores information about development documents in the development deliverable database 121 as an example of information about deliverable record documents.

[0031] The receiving unit 131 also receives a predetermined operation on the deliverable record document. Specifically, the receiving unit 131 receives operation information related to the predetermined operation on the deliverable record document from the user terminal 10. For example, the receiving unit 131 receives, as the predetermined operation, a reflection operation, which is an operation of recording information related to the development document in the development deliverable database 121 that records information related to development. For example, in the example shown in FIG. 4 , which will be described later, the receiving unit 131 receives, as the reflection operation, an operation of selecting a menu item indicating "Data Reflection" corresponding to the reflection operation from among the menu items that are displayed when a tab indicating "Document Management" displayed on the deliverable record document is selected.

[0032] (Extraction part 132) The extraction unit 132 extracts information about the development document, which is a deliverable in system development, from the deliverable record document in response to a predetermined operation on the deliverable record document in which information about the development document is described. Specifically, when the predetermined operation is accepted by the acceptance unit 131, the extraction unit 132 extracts information about the development document from the deliverable record document in response to the predetermined operation on the deliverable record document in which information about the development document is described.

[0033] Here, development documents are a general term for deliverables in system development. Specifically, development documents may include, for example, development plans, requirements definition documents, various design documents, various specifications, coding conventions, review results, or minutes created at each stage of development. For convenience of explanation, the term "documents" is used, but as mentioned above, development documents are a concept that encompasses various deliverables created as the result of system development and are not limited to documents in file format. Development documents may be data recorded in any data format (file format) as long as they are data related to deliverables in system development.

[0034] For example, the extraction unit 132 extracts information about the development document from the deliverable record document in response to a reflection operation, which is an operation of recording information about the development document in the development deliverable database 121, as a predetermined operation. Specifically, the extraction unit 132 extracts information described in the development document as the information about the development document. For example, the extraction unit 132 extracts quality metrics information from the development document as the information about the development document. For example, when the reception unit 131 receives a reflection operation, which is an operation of recording information about the development document in the development deliverable database 121, the extraction unit 132 extracts information about the development document from the deliverable record table in response to the reflection operation. For example, the extraction unit 132 extracts information about the development document specified by the user from the deliverable record document, among the development documents corresponding to each of the multiple processes displayed in each item of the deliverable list displayed in the deliverable record table. For example, in the example shown in FIG. 4 (to be described later), when the receiving unit 131 receives an operation to select a menu indicating "reflect data," the extraction unit 132 extracts, from the deliverable record document, information about development documents for which a check box corresponding to the development document is checked, as information to be extracted, among the development documents corresponding to each of the multiple processes displayed in each item of the deliverable list displayed in the deliverable record document. Note that the user's designation of a development document is not limited to checking a check box. For example, the user may designate a development document by selecting an option indicating selection from among options indicating selection (e.g., the number "1" or the character "select") and options indicating non-selection (e.g., the number "0" or the character "non-select").

[0035] Quality metrics information refers to information extracted from each development document described in the deliverable record document and used to evaluate the quality of each development document. Specifically, for example, if the development document is a requirements specification document, the quality metrics information may include a list of headings and contents for each description item, which is information used to confirm whether the items that need to be included in the requirements specification document are included. Also, for example, if the development document is a test specification document, the quality metrics information may include the number of tests, which is information used to confirm whether the test items described in the requirements specification document are covered. The above are examples of quality metrics information, and information necessary to evaluate the quality of the development documents can be selected as appropriate.

[0036] Furthermore, the extraction unit 132 extracts, as information related to the development documents, document identification information that identifies the development documents, storage location information that indicates the storage location of the development documents, process identification information that identifies the development process corresponding to the development documents, and participant identification information that identifies the participants involved in the system development. Specifically, the extraction unit 132 extracts, as information related to the development documents, document identification information that identifies the development documents, storage location information that indicates the storage location of the development documents, process identification information that identifies the development process corresponding to the development documents, and participant identification information that identifies the participants involved in the system development. For example, the extraction unit 132 extracts the document identification information, storage location information, process identification information, and participant identification information corresponding to the development documents specified by the user from among the development documents corresponding to each of the multiple processes displayed in each item of the deliverable list displayed in the deliverable record document. Here, the development documents are stored in folders on a cloud server, and the storage location information is address information or URL link information that indicates the location (location) of the development documents on the Internet. Note that the development documents do not necessarily have to be stored on a cloud server and may be local files. In the case of a local file, the path of the directory in which the file is stored may be described as the storage location information.

[0037] (Recording Unit 133) The recording unit 133 associates and records information about the development document extracted by the extraction unit 132. Specifically, when the extraction unit 132 extracts information about the development document in response to a reflection operation, the recording unit 133 associates and records the information about the development document extracted by the extraction unit 132. For example, when the extraction unit 132 extracts information about the development document in response to a reflection operation, the recording unit 133 associates and stores the information about the development document extracted by the extraction unit 132 in the development deliverable database 121.

[0038] Furthermore, the recording unit 133 associates and records the document identification information, storage location information, process identification information, and related person identification information. For example, when the extraction unit 132 extracts the document identification information, storage location information, process identification information, and related person identification information, the recording unit 133 associates and stores the document identification information, storage location information, process identification information, and related person identification information extracted by the extraction unit 132 in the development deliverable database 121.

[0039] Furthermore, the recording unit 133 records a log related to a predetermined operation. Specifically, when the receiving unit 131 receives a predetermined operation on a deliverable record document, the recording unit 133 stores a log related to the predetermined operation in the development deliverable database 121. For example, when the receiving unit 131 receives a reflection operation, the recording unit 133 stores a log including, for example, the reception date and time of the reflection operation or the completion date and time of the reflection operation in the development deliverable database 121.

[0040] Furthermore, the recording unit 133 verifies the contents of the development documents by referring to the information stored in the development deliverable database 121. Specifically, for example, the recording unit 133 may verify whether all the information that needs to be included in each development document is included.

[0041] The recording unit 133 identifies the type of each development document based on the information about the development document. Specifically, for example, the recording unit 133 may identify the type of development document based on the file name of the development document. For example, the recording unit 133 acquires first identification information that pre-associates information that can identify the type of development document with a file name (which may be a character string included in the file name) corresponding to the type of development document. Next, the recording unit 133 may identify the type of development document based on a comparison between the first identification information and the file name of the development document. Furthermore, the recording unit 133 may identify information that needs to be included in the development document based on the identified type of development document. Specifically, for example, if a field heading in the development document indicates that the field is a required field, the recording unit 133 may determine that the field is required information. Furthermore, the recording unit 133 may determine whether information is included for each field determined to require information, and calculate the percentage of fields that require information to be included (sometimes referred to as the "information fulfillment rate"). The recording unit 133 acquires second identification information that associates in advance information that can identify the type of development document with information that needs to be included in the development document. For example, the recording unit 133 acquires second identification information that associates in advance information that can identify the type of development document with required fields according to the type of development document. Next, the recording unit 133 identifies required fields in the development document based on the second identification information. Next, if the recording unit 133 identifies required fields, it determines whether information is included in the identified required fields. Next, the recording unit 133 may calculate a description sufficiency rate based on the determination result.

[0042] Furthermore, the recording unit 133 may compare the contents of the development document created in the upstream process of development with the contents of the development document created in the downstream process of development, and verify the consistency of the contents.

[0043] The recording unit 133 determines whether the information described in the development document contains a description related to a downstream process. If it determines that a description related to a downstream process exists, it acquires information about the development document for the downstream process related to that item. The recording unit 133 compares the information described in the development document for the upstream process with the information described in the development document for the downstream process to determine whether they are consistent. Specifically, for example, the recording unit 133 may determine whether a test specification, which is a development document for the downstream process, describes a test schedule for a function to be developed that is described in a requirements definition document, which is a development document for the upstream process. Furthermore, the recording unit 133 may determine consistency if the test specification includes test information for the function to be developed, and may determine inconsistency if the test specification does not include test information for the function to be developed. The recording unit 133 may also determine whether the number of tests described in the test specification is sufficient in relation to the function to be developed. For example, the recording unit 133 acquires third identification information that previously associates information that can identify the function to be developed with the number of tests to be performed for the function to be developed. Next, the recording unit 133 may determine whether the number of tests described in the test specification is sufficient in relation to the functions to be developed, based on a comparison between the number of tests described in the third identification information and the number of tests described in the test specification.

[0044] This allows the information processing device 100 to prevent omission of necessary description items in each development document and omission of necessary items in the development process, thereby improving the quality of the development documents.

[0045] (Generation unit 134) The generation unit 134 generates various data based on the information about the development documents extracted by the extraction unit 132. Specifically, the generation unit 134 generates various information based on the information about the development documents extracted by the extraction unit 132. For example, the generation unit 134 refers to the development deliverable database 121 to acquire information about the development documents extracted by the extraction unit 132. Next, the generation unit 134 generates various data based on the information about the development documents extracted by the extraction unit 132.

[0046] Furthermore, the generation unit 134 stores the various types of data generated in a predetermined storage location. Here, the predetermined storage location may be, for example, a folder on a cloud server. The user uses the user terminal 10 to access the predetermined storage location where the various types of data generated by the generation unit 134 are stored. The user terminal 10 displays the various types of data generated by the generation unit 134 on a screen. The user views the various types of data displayed on the screen of the user terminal 10.

[0047] [4. Processing Procedure] A processing procedure by the information processing device 100 according to the embodiment will be described with reference to Fig. 3. Fig. 3 is a flowchart showing the processing procedure by the information processing device according to the embodiment. In Fig. 3, the information processing device 100 acquires a deliverable record document and analyzes the contents of the deliverable record document (step S101). For example, when the information processing device 100 acquires a deliverable record document, it identifies information to be extracted from information related to the development document described in the deliverable record document.

[0048] Furthermore, the information processing device 100 extracts specific information from the deliverable record document, associates it with the information, and records it (step S102). For example, the information processing device 100 extracts information identified as the extraction target from information related to the development document described in the deliverable record document, and associates it with the information.

[0049] Furthermore, the information processing device 100 accepts a predetermined operation on the deliverable record document (step S103). For example, the information processing device 100 accepts a reflection operation.

[0050] Furthermore, the information processing device 100 extracts information related to the development document from the deliverable record document in response to a predetermined operation (step S104). For example, when the information processing device 100 receives a reflection operation, it extracts information to be extracted from the information related to the development document described in the deliverable record document.

[0051] Furthermore, the information processing device 100 executes processing in accordance with a predetermined operation (step S105). For example, when the information processing device 100 receives a reflection operation, it stores the extracted information in the development deliverable database 121 in association with the information.

[0052] Furthermore, the information processing device 100 records the processing result (step S106). For example, when the information processing device 100 associates and records the extracted information, the information processing device 100 stores, in the development deliverable database 121, information on the history of the processing in which the extracted information is associated and recorded.

[0053] Furthermore, the information processing device 100 generates an image including information on the progress of the development (step S107). For example, the information processing device 100 references the development deliverable database 121 to generate an image including information on the progress of the development.

[0054] [5. Processing deliverable review requests] An example of a review request operation for a development document according to an embodiment will be described with reference to FIG. 4. FIG. 4 is a diagram for explaining an example of a review request operation for a development document according to an embodiment. In FIG. 4, the review request operation for a development document is performed on a deliverable record document. As shown in FIG. 4, for example, the deliverable record document may be a spreadsheet into which data is entered in a tabular format.

[0055] 4, the receiving unit 131 receives, as a predetermined operation, a request operation which is an operation of requesting a review of a development document from a person involved in system development. Specifically, the receiving unit 131 receives a request operation which is an operation of requesting a review of a development document from a person involved in system development. In FIG. 4, the receiving unit 131 receives, as the request operation, an operation of selecting a menu indicating "Deliverable Review Request" corresponding to the request operation from among menus that are displayed when a tab indicating "Document Management" displayed in the deliverable record document is selected.

[0056] Furthermore, the extraction unit 132 extracts information about the development document, including storage location information indicating the storage location of the development document, from the deliverable record document in response to a request operation, which is a predetermined operation requesting a review of the development document from parties involved in the system development. Specifically, when the receiving unit 131 receives a request operation requesting a review of the development document, the extraction unit 132 extracts information about the development document from the deliverable record document in response to the request operation. For example, the extraction unit 132 extracts information about a development document specified by the user from the deliverable record document, among the development documents corresponding to each of the multiple processes displayed in each item of the deliverable list displayed in the deliverable record document. In FIG. 4, when the receiving unit 131 receives an operation to select a menu indicating "Deliverable Review Request," the extraction unit 132 extracts information about a development document, for which the checkbox corresponding to the development document is checked, from the deliverable record document, among the development documents corresponding to each of the multiple processes displayed in each item of the deliverable list displayed in the deliverable record document. In Figure 4, in response to the request operation, the extraction unit 132 extracts from the deliverable record document information indicating the "system requirements definition" entered in the "process" column corresponding to the system requirements definition document, which is a development document whose checkbox is checked (corresponding to process identification information), information indicating the "system requirements definition document" entered in the "document name" column (corresponding to document identification information), and link information of the URL entered in the "storage location" list (corresponding to storage location information).

[0057] An example of an email generated in response to a review request operation for a development document according to an embodiment will be described with reference to FIG. 5. FIG. 5 is a diagram illustrating an example of an email generated in response to a review request operation for a development document according to an embodiment. When the extraction unit 132 extracts information about the development document in response to the request operation, the generation unit 134 generates an email including information about the development document, including storage location information. Specifically, the generation unit 134 generates an email including information about the development document, including storage location information. More specifically, the generation unit 134 generates an email including the information extracted by the extraction unit 132 in response to the request operation. In FIG. 5, the generation unit 134 generates an email including information indicating a "system requirements definition" extracted by the extraction unit 132 from the "process" column of the deliverable record document in response to the request operation (corresponding to process identification information), information indicating a "system requirements definition document" extracted from the "document name" column of the deliverable record document (corresponding to document identification information), and link information of a URL extracted from the "storage location" list (corresponding to storage location information).

[0058] The generation unit 134 also references the storage unit 120 to acquire a system code and a system name that identify the system under development, which are associated with the record table identification information that identifies the deliverable record document, and generates an email including the system code and the system name that identify the system under development. The generation unit 134 also references the storage unit 120 to generate an email including a development project number, a development project name, and a planned release date that identify the project under development, which are associated with the record table identification information that identifies the deliverable record document. The generation unit 134 also generates an email including a sentence such as, "You have been requested to review the deliverable. Please check the contents." When generating an email, the generation unit 134 may send the generated email to parties involved in the system development. For example, the generation unit 134 references the storage unit 120 to acquire email addresses from a list of parties included in the deliverable record document. Then, the generation unit 134 sends the generated email to the acquired email addresses.

[0059] The generation unit 134 may generate notification information other than email. For example, the generation unit 134 may generate, as notification information other than email, a chat screen or pop-up containing the information extracted by the extraction unit 132 in response to the request operation, the system code, the system name, the development project number, the development project name, the planned release date, and a sentence such as "You have been requested to review the deliverable. Please confirm the details." Furthermore, when the generation unit 134 generates a chat screen or pop-up, the generation unit 134 may notify the user terminal 10 of the person involved in the system development of the generated chat screen or pop-up. For example, the deliverable record document may include information such as chat accounts used by the person involved as information regarding the list of people involved. For example, the generation unit 134 refers to the storage unit 120 to acquire information such as chat accounts of the list of people involved included in the deliverable record document. Then, the generation unit 134 notifies the acquired chat accounts of the generated chat screen or pop-up.

[0060] [6. Finalizing deliverables] An example of a confirmation operation of a development document according to an embodiment will be described with reference to Fig. 6. Fig. 6 is a diagram for explaining an example of a confirmation operation of a development document according to an embodiment. In Fig. 6, the confirmation operation of a development document is performed on a deliverable record document. As shown in Fig. 6, for example, the deliverable record document may be a spreadsheet into which data is entered in a tabular format, similar to Fig. 4.

[0061] In Fig. 6, the receiving unit 131 receives, as a predetermined operation, a confirmation operation, which is an operation of recording that a system development process corresponding to a development document has been completed and advancing the system development process to the next process. In other words, the confirmation operation is an operation of recording that a creation process for the development document has been completed and advancing the process corresponding to the development document to the next process. In Fig. 6, the receiving unit 131 receives, as the confirmation operation, an operation of selecting a menu indicating "Deliverable Confirmation," which corresponds to the confirmation operation, from the menu displayed when a tab indicating "Document Management" displayed in the deliverable record document is selected.

[0062] Furthermore, the extraction unit 132 extracts information about the development document from the deliverable record document in response to a confirmation operation, which is an operation of recording the completion of a system development process corresponding to a development document as a predetermined operation and advancing the system development process to the next process. Specifically, when the receiving unit 131 records the completion of a system development process corresponding to a development document and receives a confirmation operation, which is an operation of advancing the system development process to the next process, the extraction unit 132 extracts information about the development document from the deliverable record document in response to the confirmation operation. For example, the extraction unit 132 extracts information about a development document specified by a user from the deliverable record document among the development documents corresponding to each of the multiple processes displayed in each item of the deliverable list displayed in the deliverable record document. In FIG. 6, when the receiving unit 131 receives an operation to select a menu indicating "Deliverable Confirmation," the extraction unit 132 extracts information about a development document, for which the checkbox corresponding to the development document is checked, from the deliverable record document in response to the confirmation operation among the development documents corresponding to each of the multiple processes displayed in each item of the deliverable list displayed in the deliverable record document. In Figure 6, in response to the confirmation operation, the extraction unit 132 extracts from the deliverable record document information indicating the "system requirements definition" entered in the "process" column corresponding to the system requirements definition document, which is a development document whose checkbox is checked (corresponding to process identification information), and information indicating the "system requirements definition document" entered in the "document name" column (corresponding to document identification information).

[0063] An example of an email generated in response to a confirmation operation of a development document according to an embodiment will be described with reference to FIG. 7. FIG. 7 is a diagram illustrating an example of an email generated in response to a confirmation operation of a development document according to an embodiment. The generation unit 134 acquires the confirmed development document by referencing storage location information indicating the storage location of the development document described in the deliverable record document, and generates notification information related to the confirmed development document. Specifically, when the receiving unit 131 records that a system development process corresponding to the development document has been completed and receives a confirmation operation to advance the system development process to the next process, the generation unit 134 acquires the confirmed development document by referencing storage location information indicating the storage location of the development document described in the deliverable record document in response to the confirmation operation. For example, the generation unit 134 acquires the confirmed development document by referencing storage location information indicating the storage location of the development document specified by the user from among the development documents corresponding to each of the multiple processes displayed in each item of the deliverable list displayed in the deliverable record document. In the example shown in Figure 7, the generation unit 134 obtains the system requirements definition document, which is the confirmed development document, by referring to the link information (equivalent to storage location information) of the URL entered in the ``Storage location'' field corresponding to the development document whose checkbox is checked.

[0064] Next, when the generation unit 134 acquires the confirmed development document, it generates notification information related to the confirmed development document. For example, the generation unit 134 generates an email containing the confirmed development document as an attachment as the notification information. In the example shown in FIG. 7, the generation unit 134 generates an email containing a system requirements specification document, which is a confirmed development document, as an attachment as the notification information. Note that the generation unit 134 may generate notification information other than an email. For example, the generation unit 134 may generate a chat screen or a pop-up containing the confirmed development document as an attachment as the notification information. Alternatively, the generation unit 134 may generate notification information that does not contain the confirmed development document as an attachment. For example, the generation unit 134 may generate an email, a chat screen, or a pop-up containing storage location information of the confirmed development document as the notification information.

[0065] 5, the generation unit 134 references the storage unit 120 to acquire a system code and a system name that identify the system to be developed, which are associated with the record table identification information that identifies the deliverable record document, and generates notification information that includes the system code and the system name that identify the system to be developed. The generation unit 134 references the storage unit 120 to generate notification information that includes a development project number, a development project name, and a planned release date that identify the project to be developed, which are associated with the record table identification information that identifies the deliverable record document. The generation unit 134 generates notification information that includes a sentence such as, "The deliverable has been finalized. A trail file is attached." Similarly to FIG. 5, when generating notification information, the generation unit 134 may notify the generated notification information to parties involved in the system development.

[0066] [7. Data] Next, an example of each data according to the embodiment will be described with reference to FIGS.

[0067] 8 is a diagram illustrating an example of the contents of a deliverable record document and information to be extracted according to an embodiment. In the example illustrated in FIG. 8, the deliverable record document includes project information. The extraction unit 132 extracts the project information from the deliverable record document. For example, the extraction unit 132 extracts information indicating a development project number, a development project name, a system code, a system name, and a planned release date from the deliverable record document as the project information.

[0068] The deliverable record document also includes approval information. The extraction unit 132 extracts the approval information from the deliverable record document. For example, the extraction unit 132 extracts, as the approval information, information such as process identification information, document name (corresponding to document identification information), storage location (URL link) information, deliverable confirmation date, approval result, approver, and approval date from the deliverable record document.

[0069] The deliverable record document also includes review indication information. The extraction unit 132 extracts the review indication information from the deliverable record document. For example, the extraction unit 132 extracts information such as process identification information, indication classification, indication content, status, and expected completion date as the review indication information from the deliverable record document.

[0070] The deliverable record document also includes handover item information. The extraction unit 132 extracts the handover item information from the deliverable record document. For example, the extraction unit 132 extracts information such as process identification information, handover information, and status from the deliverable record document as the handover item information.

[0071] The deliverable record document also includes design information. The extraction unit 132 extracts the design information from the deliverable record document. For example, the extraction unit 132 extracts information such as function information, document name, storage location information, and status from the deliverable record document as design information. Although not shown in the figure, the deliverable record document also includes information that is not subject to extraction by the extraction unit 132. For example, the deliverable record document includes information that is not subject to extraction, such as a list of stakeholders, approval department, data reflection date, and deliverable confirmation date. For example, the deliverable record document includes, as information related to the list of stakeholders, information associating the names, email addresses, and departments of stakeholders in the system development.

[0072] Furthermore, the recording unit 133 associates and records the information extracted from the deliverable record document by the extraction unit 132. Specifically, the recording unit 133 associates and records the project information, approval information, review indication information, handover item information, and design information extracted by the extraction unit 132. For example, the recording unit 133 associates and records the project information, approval information, review indication information, handover item information, and design information in the development deliverable database 121 shown in FIG. 11 , which will be described later.

[0073] Furthermore, the extraction unit 132 extracts information described in the development document from the development document. Specifically, when a predetermined operation is received by the receiving unit 131, the extraction unit 132 extracts quality metrics information described in the development document from the development document in accordance with the predetermined operation. For example, when the receiving unit 131 receives the predetermined operation, the extraction unit 132 refers to the deliverable record document and acquires storage location information for the development document specified by the user. Next, the extraction unit 132 acquires the development document stored in the storage location corresponding to the acquired storage location information, and extracts information described in the acquired development document. For example, the extraction unit 132 extracts information described in a system requirements definition document or a test specification document as the development document. Furthermore, the recording unit 133 associates and records the information described in the development document extracted by the extraction unit 132. Specifically, the recording unit 133 associates and records the information described in the development document extracted by the extraction unit 132. For example, the recording unit 133 associates and records information described in the system requirement definition document extracted by the extraction unit 132. The recording unit 133 also associates and records information described in the test specification extracted by the extraction unit 132.

[0074] 9 is a diagram illustrating an example of the contents of a system requirements definition document according to an embodiment and information to be extracted. In the example illustrated in FIG. 9, the system requirements definition document includes table of contents information. The extraction unit 132 extracts the table of contents information from the system requirements definition document. For example, the extraction unit 132 extracts information such as the table of contents item names, subjects to be described, and remarks as the table of contents information.

[0075] The system requirements definition document also includes development function information. The extraction unit 132 extracts the development function information from the system requirements definition document. For example, the extraction unit 132 extracts, as the development function information, function information related to functions to be developed and modification information indicating whether the functions to be developed are newly added functions or modified functions.

[0076] Furthermore, the recording unit 133 associates and records the information extracted from the system requirements definition document by the extraction unit 132. Specifically, the recording unit 133 associates and records the table of contents description information and development function information extracted by the extraction unit 132. For example, the recording unit 133 associates and records the table of contents description information and development function information in the development deliverable database 121 shown in FIG. 11, which will be described later.

[0077] 10 is a diagram illustrating an example of the contents of a test specification and information to be extracted according to an embodiment. In the example illustrated in FIG. 10, the test specification includes test information for a function to be developed. The extraction unit 132 extracts the test information from the test specification. For example, the extraction unit 132 extracts information such as the number of unit tests, the number of internal tests, and the number of external tests as the test information.

[0078] Furthermore, the recording unit 133 associates and records the information extracted from the test specifications by the extraction unit 132. Specifically, the recording unit 133 associates and records the test information extracted by the extraction unit 132. For example, the recording unit 133 associates and records information such as the number of unit tests, the number of internal connection tests, and the number of external connection tests in the development deliverable database 121 shown in FIG. 11, which will be described later.

[0079] Fig. 11 is a diagram showing an example of data stored in the development deliverable database 121 according to the embodiment. In the example shown in Fig. 11, the development deliverable database 121 stores information extracted by the extracting unit 132 from a deliverable record document (see Fig. 8), information extracted from a system requirements definition document (see Fig. 9), and information extracted from a test specification document (see Fig. 10) in association with each other.

[0080] FIG. 12 is a diagram illustrating an overview of a development progress display image according to an embodiment. The generation unit 134 generates a development progress display image including first progress information indicating the current progress of system development based on the information recorded by the recording unit 133. Specifically, the generation unit 134 generates a development progress display image including first progress information indicating the current progress of system development based on the information recorded by the recording unit 133. For example, the generation unit 134 generates a development progress display image including information corresponding to multiple different types of items, such as project information, development functions, plan / system requirements definition, design, approval history, review findings, and handover items, as the first progress information, based on the information recorded in the development deliverable database 121 by the recording unit 133. FIG. 12 also illustrates that when the development progress display image is displayed on the screen of the user terminal 10, information corresponding to each item is displayed in chronological order in the following order: project information, development functions, plan / system requirements definition, design, approval history, review findings, and handover items.

[0081] 13 is a diagram showing an example of a development progress display image (development function) according to an embodiment. The development progress display image (development function) shown in Fig. 13 displays a table showing the number of tests for each classification of development function, such as patch function, external interface function, report function, and screen function, and a pie chart showing the proportion of the number of tests for each classification of development function.

[0082] In the following, we will explain an example in which a development progress display image is generated for each development process, but a development progress display image may also be generated for each development project. Furthermore, the development progress display image only needs to be expressed in a form that allows the progress of the development process to be visually grasped, and various display formats such as pie charts, bar graphs, progress bars, etc. can be used.

[0083] The development progress display image (development function) may include information about the description fulfillment rate and / or the consistency determination result. Specifically, for example, the development progress display image (development function) may display the description fulfillment rate in various display modes, such as a pie chart, a bar graph, or a progress bar. Furthermore, for example, the development progress display image (development function) may distinguish between development documents determined to be consistent and development documents determined to be inconsistent as the consistency determination result, using various display modes, such as text, color, font, or icon. Specifically, for example, the development progress display image (development function) may display the number of scheduled tests as the consistency determination result, and items with a value of 0 may be displayed in red shading. Note that the other graphs that will be introduced later may also be displayed in various display modes, such as a pie chart, a bar graph, or a progress bar.

[0084] 14 is a diagram showing an example of a development progress display image (plan / system requirements definition) according to an embodiment. The development progress display image (plan / system requirements definition) shown in FIG. 14 displays a table indicating whether or not the description corresponding to each item in the table of contents of the system requirements definition document is a description target, and a bar graph indicating the description rate, which indicates the percentage of items in the table of contents that have information written on them.

[0085] Fig. 15 is a diagram showing an example of a development progress display image (design) according to an embodiment. The development progress display image (design) shown in Fig. 15 displays a table showing the classification of functions to be designed (screen functions in Fig. 15), the names of development documents related to the functions to be designed, storage location information for the development documents, and the status of the development documents (in progress or completed), and a pie chart showing the ratio of development documents that have been completed and development documents that are currently being worked on.

[0086] 16 is a diagram showing an example of a development progress display image (approval history) according to an embodiment. The development progress display image (approval history) shown in Fig. 16 displays the names of development documents corresponding to each of all stages of system development, storage location information for the development documents, a table showing the approval results and confirmation dates for the development documents, and a pie chart showing the ratio of approved development documents to unapproved development documents.

[0087] Fig. 17 is a diagram showing an example of a development progress display image (review indications) according to an embodiment. The development progress display image (review indications) shown in Fig. 17 displays a table showing the indication date, indication classification, indication content, and status (in progress or completed) for each process that was the subject of a review indication, a bar graph showing the ratio of indications in progress and indications that have been completed for each process, and a pie chart showing the ratio for each type of indication classification.

[0088] Fig. 18 is a diagram showing an example of a development progress display image (handover items) according to an embodiment. The development progress display image (handover items) shown in Fig. 18 displays a table showing the degree of impact (small impact or large impact) of the handover items for each process that has a handover item, the contents of the handover item, and the status (in progress or completed), a bar graph showing the ratio of handover items in progress and completed for each process, and a pie chart showing the ratio for each magnitude of the impact (small impact or large impact) of the handover items.

[0089] Furthermore, the recording unit 133 records information related to the development documents at each time point in the system development in association with time information indicating each time point in the system development. The generating unit 134 generates a development progress display image including information in which second progress information indicating the progress of the system development at each time point in the system development is associated with time information indicating each time point in the system development, based on the information recorded by the recording unit 133. Specifically, the generating unit 134 generates a development progress display image including information in which the second progress information indicating the progress of the system development at each time point in the system development is associated with time information indicating each time point in the system development, based on the information recorded by the recording unit 133. For example, the generating unit 134 may generate a development progress display image including information in which, as second progress information, information corresponding to each of a plurality of different types of items, such as project information, development functions, plan / system requirements definition, design, approval history, review findings, and handover items at each time point in the system development is associated with time information indicating each time point in the system development, based on the information recorded by the recording unit 133 in the development deliverable database 121.

[0090] [8. Effects] As described above, the information processing device 100 according to the embodiment includes the extraction unit 132 and the recording unit 133. The extraction unit 132 extracts information about a first document (a development document in the embodiment), which is a deliverable in system development, from a second document (a deliverable recording document in the embodiment) in response to a predetermined operation on the second document in which information about the first document is described. The recording unit 133 records the information about the first document extracted by the extraction unit 132 in association with the information.

[0091] As a result, the information processing device 100 can reduce the workload of development personnel in collecting information about development documents. Furthermore, the information processing device 100 can reduce the workload of development personnel in storing information about development documents. Furthermore, because the information processing device 100 can reduce the workload of development personnel in collecting and storing information about development documents, it can reduce the workload of managing development documents in system development. Furthermore, because the information processing device 100 can reduce the workload of managing development documents in system development, it can contribute to achieving Goal 9 of the Sustainable Development Goals (SDGs), "Build resilient infrastructure, promote inclusive and sustainable development, and promote inclusive and sustainable industrialization." Furthermore, as described above, reducing the workload of managing development documents in system development (so-called administrative work) allows developers to focus more on developing development documents and other development products. Furthermore, allowing developers to focus more on developing development products leads to improved quality. In this way, the information processing device 100 can reduce the workload of managing development documents in system development, thereby improving productivity and quality in system development.

[0092] Furthermore, the extracting unit 132 extracts, from the first document, quality metrics information described in the first document for evaluating the quality of the first document. The recording unit 133 records the quality metrics information extracted by the extracting unit 132 in association with the quality metrics information.

[0093] As a result, the information processing device 100 can reduce the burden on development-related personnel of collecting information described in development documents and improve the quality of the development product.

[0094] Furthermore, the extraction unit 132 extracts information about the first document from the second document in response to a reflection operation, which is a predetermined operation that records information about the first document in a database that records information about development.

[0095] As a result, the information processing device 100 can reduce the burden of work for developers involved in accumulating information about development documents and can improve the quality of the development product.

[0096] The information processing device 100 further includes a generation unit 134. The generation unit 134 generates an email. In response to a request operation, which is a predetermined operation requesting a review of the first document from a person involved in system development, the extraction unit 132 extracts information about the first document, including storage location information indicating a storage location of the first document, from the second document. The generation unit 134 generates an email including information about the first document, including the storage location information.

[0097] As a result, the information processing device 100 can reduce the workload of development personnel involved in requesting a review of a development document and improve the quality of the development product. Furthermore, even if the information processing device 100 does not use a workflow for requesting a review of a development document, it can leave a history of approval requests and approval results for the development document through the history of email transmission and reception, thereby leaving a trail of evidence for the development document. Therefore, the information processing device 100 can also comply with various audits such as J-SOX.

[0098] The information processing device 100 further includes a generating unit 134. The generating unit 134 generates notification information. The extracting unit 132 records, as a predetermined operation, that the system development process corresponding to the first document has been completed, and extracts information related to the first document from the second document in response to a confirmation operation, which is an operation for advancing the system development process to the next process. The generating unit 134 acquires the confirmed first document by referring to storage location information indicating the storage location of the first document described in the second document, and generates notification information related to the confirmed first document.

[0099] As a result, the information processing device 100 can reduce the workload of development participants in notifying other development participants of the finalization of a development document and improve the quality of the development product. Furthermore, even if the information processing device 100 does not use a workflow for notifying other development participants of the finalization of a development document, it can leave a history of the finalization of the development document by recording the history of sending and receiving notification information, thereby leaving a trail of the development document. Therefore, the information processing device 100 can also comply with various audits such as J-SOX.

[0100] Furthermore, the recording unit 133 records a log relating to a predetermined operation.

[0101] This allows the information processing device 100 to keep a history of operations related to reflecting development documents, operations for requesting reviews of development documents, and operations for finalizing development documents, thereby reducing the burden on development personnel of accumulating information related to development documents and improving the quality of the development product. Therefore, the information processing device 100 can also comply with various audits such as J-SOX.

[0102] Furthermore, the extraction unit 132 extracts, as information related to the first document, document identification information that identifies the first document, storage location information that indicates the storage location of the first document, process identification information that identifies the development process corresponding to the first document, and related party identification information that identifies related parties involved in the system development. The recording unit 133 records the document identification information, storage location information, process identification information, and related party identification information in association with each other.

[0103] This allows the information processing device 100 to grasp, for each development document, the storage location, progress status, or development personnel of the development document.

[0104] Furthermore, information processing device 100 has an extraction unit 132, a recording unit 133, and a generation unit 134. Extraction unit 132 extracts information about a first document, which is a deliverable of system development, from a second document in response to a predetermined operation on the second document in which information about the first document is described. Recording unit 133 records the information about the first document extracted by extraction unit 132 in association with the information. Based on the information recorded by recording unit 133, generation unit 134 generates a development progress display image including first progress information that indicates the current progress status of system development.

[0105] As a result, the information processing device 100 can reduce the workload of development personnel who collect information about development documents. The information processing device 100 can also reduce the workload of development personnel who store information about development documents. Furthermore, the information processing device 100 can easily visually grasp the current progress of system development, thereby reducing the workload of development personnel who display information about development documents. Furthermore, the information processing device 100 can reduce the workload of development personnel who collect, store, and display information about development documents, thereby reducing the workload of development document management in system development. Furthermore, the information processing device 100 can reduce the workload of development document management in system development, thereby contributing to the achievement of Goal 9 of the Sustainable Development Goals (SDGs), "Build resilient infrastructure, promote inclusive and sustainable industrialization, and build resilient technological infrastructure." Furthermore, the information processing device 100 can reduce the workload of development document management in system development, thereby improving productivity and quality in system development.

[0106] The information processing device 100 also has an extraction unit 132, a recording unit 133, and a generation unit 134. The extraction unit 132 extracts information about the first document, which is a deliverable of the system development, from the second document in response to a predetermined operation on the second document in which information about the first document is described. The recording unit 133 records the information about the first document extracted by the extraction unit 132 in association with the information. The generation unit 134 generates, based on the information recorded by the recording unit 133, a development progress display image including information in which second progress information indicating the progress of the system development at each time point in the system development is associated with time information indicating each time point in the system development.

[0107] As a result, the information processing device 100 can reduce the workload of development personnel who collect information about development documents. The information processing device 100 can also reduce the workload of development personnel who store information about development documents. Furthermore, the information processing device 100 can visually and easily grasp the progress of system development at each point in time during system development, thereby reducing the workload of development personnel who display information about development documents. Furthermore, the information processing device 100 can reduce the workload of development personnel who collect, store, and display information about development documents, thereby reducing the workload of development document management in system development. Furthermore, the information processing device 100 can reduce the workload of development document management in system development, thereby contributing to the achievement of Goal 9 of the Sustainable Development Goals (SDGs), "Build resilient infrastructure, promote inclusive and sustainable industrialization, and build resilient technological infrastructure." Furthermore, the information processing device 100 can reduce the workload of development document management in system development, thereby improving productivity and quality in system development.

[0108] [9. Hardware Configuration] The information processing device 100 according to the embodiment described above is realized by, for example, a computer 1000 configured as shown in Fig. 19. Fig. 19 is a hardware configuration diagram showing an example of a computer that realizes the functions of the information processing device 100. The computer 1000 includes a CPU 1100, a RAM 1200, a ROM 1300, an HDD 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F) 1700.

[0109] The CPU 1100 operates and controls each unit based on programs stored in the ROM 1300 or the HDD 1400. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 starts up, programs that depend on the hardware of the computer 1000, and the like.

[0110] The HDD 1400 stores programs executed by the CPU 1100, data used by these programs, etc. The communication interface 1500 receives data from other devices via a predetermined communication network and sends the data to the CPU 1100, and transmits data generated by the CPU 1100 to other devices via the predetermined communication network.

[0111] The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and a mouse, via the input / output interface 1600. The CPU 1100 acquires data from the input devices via the input / output interface 1600. The CPU 1100 also outputs generated data to the output devices via the input / output interface 1600.

[0112] Media interface 1700 reads a program or data stored in recording medium 1800 and provides it to CPU 1100 via RAM 1200. CPU 1100 loads the program or data from recording medium 1800 onto RAM 1200 via media interface 1700 and executes the loaded program. Recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase Change Rewritable Disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

[0113] For example, when the computer 1000 functions as the information processing device 100 according to the embodiment, the CPU 1100 of the computer 1000 executes programs loaded onto the RAM 1200 to realize the functions of the control unit 130. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, the CPU 1100 may obtain these programs from another device via a predetermined communication network.

[0114] Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be implemented in other forms that include the embodiments described in the Disclosure of the Invention section and that have been modified and improved in various ways based on the knowledge of those skilled in the art.

[0115] [10. Other] Furthermore, among the processes described in the above embodiments and modifications, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0116] Furthermore, the components of each device shown in the figure are conceptual functional components and do not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0117] Furthermore, the above-described embodiments and modifications can be combined as appropriate within the scope of not causing any contradiction in the processing content. [Explanation of symbols]

[0118] 1. Information Processing Systems 10 User terminal 100 Information processing device 110 Communications Department 120 Storage section 121 Development artifact database 130 control section 131 Reception 132 Extraction part 133 Recording Department 134 Generation part

Claims

1. a receiving step of receiving a request operation, which is an operation for requesting a review of a first document from a person involved in the system development, as a predetermined operation on a second document describing information about the first document that is a deliverable of the system development; an extraction step of extracting a plurality of pieces of information related to the first document from the second document when the request operation is accepted by the acceptance step; a recording step of recording the plurality of pieces of information related to the first document extracted by the extracting step in association with each other; An information processing program that causes a computer to execute the above.

2. A reception procedure for receiving a confirmation operation, which is a predetermined operation for a second document that describes information about a first document that is a deliverable in system development, to record that the system development process corresponding to the first document has been completed and to advance the system development process to the next step; an extraction step of extracting a plurality of pieces of information related to the first document from the second document when the confirmation operation is accepted by the acceptance step; a recording step of recording the plurality of pieces of information related to the first document extracted by the extracting step in association with each other; An information processing program that causes a computer to execute the above.

3. The extraction procedure comprises: extracting, from the first document, quality metrics information described in the first document for evaluating the quality of the first document; The recording procedure includes: Associating and recording the quality metrics information extracted by the extraction procedure; 3. The information processing program according to claim 1.

4. The extraction procedure comprises: extracting information about the first document from the second document in response to a reflection operation, which is an operation of recording information about the first document in a database that records information about development; 3. The information processing program according to claim 1.

5. causing the computer to further perform a generating step to generate an email; The extraction procedure comprises: extracting, in response to the request operation, information about the first document, including storage location information indicating a storage location of the first document, from the second document; The generating procedure includes: generating an email containing information about the first document including the storage location information; The information processing program according to claim 1 .

6. further causing the computer to execute a generating step of generating notification information; The extraction procedure comprises: extracting information about the first document from the second document in response to the confirmation operation; The generating procedure includes: acquiring the confirmed first document by referring to storage location information indicating a storage location of the first document described in the second document, and generating the notification information regarding the confirmed first document; The information processing program according to claim 2 .

7. The recording procedure includes: Recording a log relating to the predetermined operation; 3. The information processing program according to claim 1.

8. The extraction procedure comprises: extracting, as information related to the first document, document identification information that identifies the first document, storage location information that indicates a storage location of the first document, process identification information that identifies a development process corresponding to the first document, and participant identification information that identifies participants involved in the system development; The recording procedure includes: The document identification information, the storage location information, the process identification information, and the person involved identification information are recorded in association with each other.

3. The information processing program according to claim 1.

9. A generation procedure for obtaining first progress information indicating the current progress of the system development from the first document, and generating a development progress display image including the first progress information; 3. The information processing program according to claim 1, further comprising:

10. A generation procedure for obtaining second progress information indicating the progress of the system development at each point in time of the system development from the first document, and generating a development progress display image including information correlating the second progress information with time information indicating each point in time of the system development; 3. The information processing program according to claim 1, further comprising:

11. a receiving unit that receives a request operation, which is an operation for requesting a review of a first document that is a deliverable of a system development, from a person involved in the system development as a predetermined operation on a second document that describes information about the first document; an extracting unit that extracts a plurality of pieces of information related to the first document from the second document when the request operation is accepted by the accepting unit; a recording unit that records the plurality of pieces of information related to the first document extracted by the extraction unit in association with each other; An information processing device comprising:

12. A reception unit that receives a confirmation operation, which is a predetermined operation on a second document that describes information about a first document that is a deliverable in system development, and is an operation that records that the system development process corresponding to the first document has been completed and advances the system development process to the next process; an extracting unit that extracts a plurality of pieces of information related to the first document from the second document when the accepting unit accepts the confirmation operation; a recording unit that records the plurality of pieces of information related to the first document extracted by the extraction unit in association with each other; An information processing device comprising:

13. An information processing method realized by a program executed by an information processing device, a receiving step of receiving a request operation, which is an operation for requesting a review of a first document from a person involved in the system development, as a predetermined operation on a second document describing information about the first document that is a deliverable of the system development; an extraction step of extracting a plurality of pieces of information related to the first document from the second document when the request operation is accepted by the accepting step; a recording step of recording the plurality of pieces of information related to the first document extracted in the extracting step in association with each other; An information processing method including:

14. An information processing method realized by a program executed by an information processing device, comprising: a receiving step of receiving a confirmation operation, which is a predetermined operation on a second document describing information about a first document that is a deliverable in the system development, for recording that the process of the system development corresponding to the first document has been completed and for advancing the process of the system development to the next step; an extraction step of extracting a plurality of pieces of information related to the first document from the second document when the confirmation operation is accepted by the accepting step; a recording step of recording the plurality of pieces of information related to the first document extracted in the extracting step in association with each other; An information processing method including:

Images