Process proposal system and process proposal method

Abstract

To re-propose appropriate processes in response to changes in progress states of a project.SOLUTION: A process proposal system includes an arithmetic device that executes a program, and a storage device accessible by the arithmetic device. The arithmetic unit executes: a first step of proposing selection of business processes to be executed in carrying out a project and an execution order of the selected business processes based on data regarding the project; a second step of acquiring project information including progress states of the project; and a third step of re-proposing the selection and execution order of the proposed business processes based on the acquired project information.SELECTED DRAWING: Figure 1

Description

TECHNICAL FIELD

[0001] The present invention relates to a process proposal system that proposes processes through software tailoring.

BACKGROUND ART

[0002] In software development projects, tailoring is performed to rearrange reference processes such as standard processes into processes suitable for the characteristics of the relevant project.

[0003] Patent Document 1 addresses the problem of "preventing inconsistencies in inputs and outputs between processes and the deletion of necessary processes when tailoring is performed", and as a solution thereto, it discloses that "a project management apparatus according to one aspect of the present invention comprises: a process storage unit that stores process definition data including input deliverable data, output deliverable data, precondition data indicating preconditions defining the state of input deliverables, and postcondition data indicating postconditions defining the state of output deliverables; a verification unit that determines whether the process definition data satisfies verification conditions of the condition data, based on condition data for confirming that the precondition data, the input deliverable data, the postcondition data, and the output deliverable data are in a consistent relationship; and an output unit that outputs a portion of the process definition data that does not satisfy the verification conditions when it is determined that the process definition data does not satisfy the verification conditions" (see the abstract of Patent Document 1).

[0004] Patent Document 2 addresses the problem of "enabling tailoring of input / output relationships between files related to a process," and discloses a solution in which, upon receiving a tailoring instruction, an information processing device performs a first process in which, when it receives a tailoring instruction, it compares the identification information of a target electronic file with tailoring information, identifies other electronic files that have an input / output relationship with the target electronic file, assigns a predetermined value to the degree of necessity, and stores the predetermined value in a storage device; a second process in which it displays tailoring information in which the display color of the information of the electronic file changes in stages according to the predetermined value; and when it receives an instruction that any of the electronic files indicated by the displayed tailoring information are unnecessary, it compares the identification information of the unnecessary electronic file with the tailoring information to identify related electronic files that have an input / output relationship, receives an instruction to update the input / output relationship in the tailoring information of the related electronic files, and executes a third process in accordance with this update instruction (see abstract of Patent Document 2).

[0005] Patent Document 3 addresses the problem that "determining what process to use for development work was difficult for inexperienced managers. Therefore, organizations have defined and dealt with this by defining standard development processes. However, such development processes are designed to fit all projects in the organization and tend to be excessive for small projects." As a solution, it discloses a risk calculation unit for determining an acceptable risk rate based on risk data for each activity of the standard development process and input data that serves as the basis for the risk, and a tailoring unit that determines whether or not to incorporate each activity constituting the standard development process into the project management process based on the acceptable risk rate (see abstract of Patent Document 3).

[0006] Patent Document 4 discloses a device for supporting process changes such as tailoring of software development processes, which aims to reduce management man-hours and simplify the approval procedure for new processes, thereby enabling smooth redefinition of processes at the development site and supporting the application of appropriate development processes to realize customer requests. As a solution, it discloses a device comprising: a pattern storage unit that divides the process into appropriate granularities and stores multiple process patterns for the divided ranges; multiple pattern selection units that take characteristic information for the process as input and select an appropriate process pattern from the pattern storage unit; a process generation unit that generates a single process by combining the patterns selected by each pattern selection unit; and a rule conformance determination unit that compares the generated process with rule information related to the process and determines whether or not it conforms to the rules (see abstract of Patent Document 4). [Prior art documents] [Patent Documents]

[0007] [Patent Document 1] Japanese Patent Publication No. 2008-33815 [Patent Document 2] Japanese Patent Publication No. 2013-145462 [Patent Document 3] Japanese Patent Publication No. 2003-296528 [Patent Document 4] Japanese Patent Publication No. 2006-65521 [Overview of the project] [Problems that the invention aims to solve]

[0008] A tailored process may not be able to reconfigure prioritizing processes in response to subsequent changes in project circumstances, potentially leading to decreased project efficiency.

[0009] In the aforementioned background technologies, the project process was not reviewed or restructured after the project was launched. As a result, even when circumstances changed due to factors after the project's inception, these factors were not taken into consideration, sometimes leading to a decrease in the efficiency of project activities. Therefore, improving project efficiency through process restructuring is required.

[0010] The present invention aims to propose an appropriate process in response to changes in project progress, based on input data regarding project progress. [Means for solving the problem]

[0011] A typical example of the invention disclosed in this application is as follows: a process proposal system comprising a computing device that executes a program and a storage device accessible by the computing device, wherein the computing device performs calculations based on project-related data. The system searches for priority items in the tailoring input information and proposed process data. If the search results match, process definition data with implementation priority set is extracted as proposed process data. From the extracted proposed process data... Business processes to be executed in project execution of choice death, The first step is to propose the execution order of the selected business processes, the second step is to obtain project information including the project progress, and based on the obtained project information, If it is determined that there are factors that could cause a change in the plan, such as failure to meet project deadlines, excessive overtime, or a concentration of tasks on a specific engineer, and if any of these factors exceed a predetermined threshold, then it is determined that there are factors that could cause a change in the plan, and the proposed business processes are selected from the re-proposed process data extracted from the proposed process data, and the execution order of the selected business processes is re-proposed. The third step is characterized by performing the following. [Effects of the Invention]

[0012] According to one aspect of the present invention, projects can be carried out efficiently. Problems, configurations, and effects other than those described above will be clarified by the following description of embodiments. [Brief explanation of the drawing]

[0013] [Figure 1] This figure shows an example of a system configuration that realizes this embodiment. [Figure 2] This figure shows an example of how the output data, the proposed process data, is displayed. [Figure 3] This is a flowchart of the processes performed by the system in this embodiment. [Figure 4] This is a flowchart of the process customization and project monitoring processing in step S208. [Figure 5] This is a diagram showing an example of a screen displayed on a monitor. [Figure 6] This is a flowchart of the project status monitoring processing in step S304. [Figure 7] This is a diagram showing the content of project information. [Figure 8] This is a diagram showing the content of tailoring input information. [Figure 9] This is a diagram showing the content of project current status data. [Figure 10] This is a diagram showing re-proposed process data. [Figure 11] This is a diagram showing re-proposed process data. [Figure 12] This is a diagram showing re-proposed process data. [Figure 13] This is a diagram showing re-proposed process data. [Figure 14] This is a diagram showing the types that can be displayed in a warning display (types of warning flags). [Figure 15] This is a flowchart of the plan change factor determination processing in step S404. [Figure 16] This is a diagram showing the content of re-proposed process data when the priority is "implementation priority". [Description of Embodiments of the Invention]

[0014] Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.

[0015] [Example 1] Figure 1 is a diagram showing an example of the system configuration for implementing the present embodiment.

[0016] In the system of the present embodiment, the software of the present invention is implemented on a cloud that is connected to an operation terminal via a network. This software is used on the operation terminal to operate the system.

[0017] In this embodiment, the process proposal system 101 is composed of a computer having an input unit 104, a project information retrieval unit 105, an information storage unit 106, a calculation unit 107, a process definition unit 108, an output unit 109, and memory (not shown). The calculation unit 107 is an arithmetic unit that executes programs stored in memory. The functions provided by the process proposal system 101 are realized by the calculation unit 107 executing various programs. Note that the calculation unit 107 may have a hardware arithmetic unit (e.g., ASIC, FPGA, etc.) in addition to a processor that executes programs. The memory includes ROM, which is a non-volatile memory element, and RAM, which is a volatile memory device. ROM stores immutable programs (e.g., BIOS). RAM is a high-speed, volatile memory device such as DRAM (Dynamic Random Access Memory) and temporarily stores programs executed by the calculation unit 107 and data used when executing programs. The information storage unit 106 is, for example, a large-capacity, non-volatile auxiliary storage device such as a magnetic storage device, and stores the program executed by the arithmetic unit 107 and the data used by the arithmetic unit 107 when the program is executed.

[0018] The program executed by the arithmetic unit 107 is provided to the process proposal system 101 via removable media (such as a CD-ROM or flash memory) or a network, and is stored in a non-volatile auxiliary storage device, which is a non-temporary storage medium. For this reason, the process proposal system 101 should have an interface for reading data from the removable media.

[0019] The process proposal system 101 is a computer system that operates on a single physical computer, or on one or more logically or physically configured computers, and may operate on a virtual computer built on multiple physical computer resources. For example, each process executed by the arithmetic unit 107 may operate on a separate physical or logical computer, or multiple processes may be combined and operate on a single physical or logical computer.

[0020] When user 102 operates the input tool 103, the information necessary for tailoring is input into the input unit 104. After acquiring project information 501 and project status data 507 from the project management tool 111, the information entered into the input unit 104 is processed by the project information search unit 105, information storage unit 106, calculation unit 107, and process definition unit 108, and the proposed tailoring is output from the output unit 109 and displayed on the monitor 110.

[0021] Figure 2 shows an example of the display of the proposed process data 504, which is the output data.

[0022] The proposed process data 504 includes input information, process workflow, and definition documents / procedures / templates required for process execution, and this information is displayed on the monitor 110.

[0023] Figure 3 is a flowchart of the processes performed by the system in this embodiment. The processes shown in Figure 3 are initiated by user input at the start of the project and continue until the project is completed.

[0024] S201: The input unit 104 receives the input project number 510 entered by user 102 using the input tool 103.

[0025] S202: The project information search unit 105 uses the input project number 510 to search for a match with project number 509 in the project information 501 of the project management tool 111, and obtains data with the same project number as input data. Note that input data not managed by the project management tool 111 can also be entered into the input unit 104.

[0026] S203: The information storage unit 106 stores the acquired project information 501.

[0027] S204: The input unit 104 receives the tailoring input information 502 that the user 102 has entered into the input tool 103.

[0028] S205: The information storage unit 106 stores the input tailoring input information 502.

[0029] S206: The process definition unit 108 and the calculation unit 107 search for the priority items (quality priority / implementation priority / test priority / schedule priority) in the tailoring input information 502 and the priority items (quality priority / implementation priority / test priority / schedule priority) in the proposed process data 504. If the search results match, the process definition data in the proposed process data 504 has a circle (○) next to the priority item. 503 The process is narrowed down to definition documents, procedure manuals, and templates (work deliverables), and these are extracted as proposed process data 504.

[0030] S207: The output unit 109 outputs the extracted proposed process data 504 as a proposed process.

[0031] S208: Subsequently, the process proceeds to the process customization / project monitoring process (Figure 4), which monitors the project status, in order to allow user 102 to decide whether to customize the proposed process data 504.

[0032] Figure 4 is a flowchart of the process customization project monitoring process in step S208.

[0033] S301: The input unit 104 asks the user 102 whether to modify the proposed process data 504. If they modify it, proceed to S302. If they do not modify it, proceed to S303.

[0034] S302: The input unit 104 receives the customized process data 505 that the user 102 entered into the input tool 103.

[0035] S303: If user 102 does not change the proposed process data 504 in S301, the information storage unit 106 will set the proposed process data 504 to proposed (customized) process data 506. On the other hand, if user 102 does not change the proposed process data 504 in S301, Proposal process data If 504 is changed, the information entered in S302 Customization process data 505 will be designated as the proposed (customized) process data 506.

[0036] S304: Execute project status monitoring process (Figure 6).

[0037] S305: The calculation unit 107 determines whether the project is finished by checking whether the status of each task in the project's work plan status in the project status data 507 is "completed". If the project is ongoing, proceed to S306. If the project is finished, terminate the process customization / project monitoring process.

[0038] S306: Check the status of the warning flag controlled by the project status monitoring process in S304. If the warning flag is ON, proceed to S307. If the warning flag is OFF, proceed to S304.

[0039] S307: The output unit 109 displays warning data and re-suggestion process data 508.

[0040] Figure 5 shows an example of a screen output from the output unit 109 and displayed on the monitor 110.

[0041] The display screen shown in Figure 5 is what is output when the S304 project status monitoring process is executed while a project is currently undergoing bug fixes and the fix work is behind schedule.

[0042] The display screen shown in Figure 5 includes the date, a warning, and a proposed process. The warning indicates that the project is behind schedule. The proposed process includes the ticket name, the content of the proposed process, identification information, a template, status, the due date, and the review results (task priority). The new template proposed by the display screen shown in Figure 5 suggests a change in the process execution order. The template items have links to templates (design documents, source code, specifications, test results, etc.) whose names are displayed, and selecting a name allows access to the relevant document. The due date is the expected completion date when the process is executed using the proposed template.

[0043] Figure 6 is a flowchart of the project status monitoring process in step S304.

[0044] S401: The project information search unit 105 searches for project status data 507 using project number 509 as the key.

[0045] S402: The information storage unit 106 receives project status data 507 from the project information retrieval unit 105 and stores it.

[0046] S403: The information storage unit 106 passes the project status data and the proposed (customized) process data 506 extracted in S303 to the calculation unit 107.

[0047] S404: The process definition unit 108 and the calculation unit 107 extract warning data and re-proposed process data 508 from the project status data 507 and the proposed (customized) process data 506. The calculation unit 107 determines whether there are factors for changing the plan based on the scheduled delivery date, actual man-hours, and assigned personnel in the project status data 507. Factors for changing the plan include failure to meet the project deadline, excessive overtime, and concentration of tasks on a specific engineer. If any of these exceed a predetermined threshold, it is determined that there are factors for changing the plan. Furthermore, by using the warning data and re-proposed process data 508, it becomes possible to re-propose processes in response to changes in the number of project members, changes in the number of available terminals, and even changes in costs or the costs that can be allocated at predetermined intervals (e.g., months). In addition, by setting deadline information for the re-proposed process, it may be possible to manage deadlines for each step. In that case, the deadline information should include not only the schedule but also information such as the progress and completion rate of deliverables, target values ​​specified by the customer, and test items that need to be implemented. The project deliverables are project status data 507 and templates for completed tasks. Deadline information, along with the project status data 507, is stored in the project management tool 111 from the calculation unit 107.

[0048] Figure 15 is a flowchart of the process for determining the cause of the plan change in step S404. In Figure 15, the process of extracting warning data and re-proposal process data 508 (the process for determining the cause of the plan change) is explained using an example where the cause of the plan change was failure to meet the deadline.

[0049] S501: The calculation unit 107 obtains the project work plan status (development deadline, number of development personnel, planned total man-hours, information on each task, process type of tasks constituting the project, start date, planned delivery date, status, completion template, person in charge, planned man-hours, and actual man-hours) from the project status data.

[0050] S502: The calculation unit 107 determines from the "Individual Task Information" whether the cause of the plan change is due to failure to meet deadlines, excessive overtime, or a concentration of tasks on a specific engineer. It compares the scheduled deadline date with the current date for all tasks, and if any tasks have exceeded their scheduled deadline date, it determines that the deadline has been missed. In addition, if the daily working hours (actual man-hours ÷ (current date - start date)) from the project status data 507 exceed a predetermined time, it determines that there has been excessive overtime. Furthermore, the "Individual Task Information" in the project status data 507 contains as much individual task information as there are tasks to be performed during the development period (for example, if there are 10 tasks, there are 10 individual task information entries), and if those tasks are concentrated on the same person, it determines that there has been a concentration of tasks on a specific engineer.

[0051] S503: If it is determined that the deadline has not been met, the process and definition documents, procedures, and templates (work deliverables) designated as "implementation priority" in the re-proposed data will be compared with the task information (process type and completed template) for which the deadline has not been met. This will identify the processes and definition documents, procedures, and templates (work deliverables) that have not been implemented, and the process and definition documents, procedures, and templates (work deliverables) indicated as "implementation priority" in the re-proposed data will be proposed to be implemented in a later stage.

[0052] Figure 16 shows the contents of the resubmission process data when a resubmission is made in Figure 15. The resubmission process data includes the process identification information and name, the identification information and type of the definition document, procedure document, and template (work product), and whether an implementation priority has been set. Definition documents, procedure documents, and templates (work products) that have an implementation priority set (marked with a circle in the figure) are the ones that constitute the resubmission process data.

[0053] Return to Figure 6 and continue the explanation. S405: If there are factors that would cause the plan to change, proceed to S406. If there are no factors that would cause the plan to change, proceed to S407.

[0054] S406: Set the warning flag to ON.

[0055] S407: Set the warning flag to OFF.

[0056] Figure 7 shows the input project number 510 and the contents of project information 501 entered by the user. Project information 501 is project information stored in the project management tool and is used to check the project schedule, implementation process, and the status of definition documents, procedures, and templates (work deliverables). Project information 501 includes project number 509, project plan, and progress status (implementation process).

[0057] Figure 8 shows the contents of the tailoring input information 502. The tailoring input information 502 includes the corresponding standards / specifications, implementation process, external contractors, work effort / duration, novelty, urgency, development phase, design methodology, and priorities. The corresponding standards / specifications include A-SPICE capability level, functional safety, and cybersecurity. The tailoring input information 502 is data entered by user 102 through the operation of the input tool 103, and is the information necessary for this system to propose tailoring.

[0058] Figure 9 shows the contents of Project Status Data 507. Project Status Data 507 includes Project Number 509, the project's work plan status, the names of processes in progress, and project deadline information. The project's work plan status includes the project's development period, the number of personnel involved in the project's development, the project's planned total man-hours, and project task information. The project task information includes the process type (MAN / ACQ / SUP / SWE), the start date, the planned due date, the status (not yet implemented / in progress / completed), the completed template (work deliverable), the person in charge, the planned man-hours, and the actual man-hours. The deadline information includes the schedule, the progress and completion rate of the deliverables, the target values ​​specified by the customer, and the test items that must be performed. Project Status Data 507 is the data necessary for monitoring the project status and for this system to propose tailoring again.

[0059] Figures 10 to 13 show the re-proposal process data from the process definition data 503, proposed process data 504, and warning data / re-proposal process data 508. In each figure, the items on the horizontal axis are all the same, and 2 to 4 processes are selected on the vertical axis. User 102 operates the input tool 103 to select priorities (quality priority / implementation priority / test priority / schedule priority), thereby narrowing down the processes and definition documents / procedures / templates (work deliverables), and the results are proposed (or re-proposed) to User 102.

[0060] In addition to the processes and templates (work deliverables) shown in Figures 10 to 13, the revised proposal process data may also include development-related materials such as specifications and system / hardware-related input documents obtained from the customer.

[0061] Figure 14 shows the types of warnings that can be displayed (types of warning flags). Warning flags include unmet deadlines, excessive overtime, and task concentration on specific engineers, and each type can be set to ON or OFF.

[0062] As described above, the process proposal system 101 of this embodiment performs the following steps: a first step of proposing the selection of business processes to be executed in the execution of a project and the execution order of the selected business processes based on project information, which is data related to the project; a second step (S202) of acquiring project information 501, which is data related to the progress of the project; and a third step (S206, S207) of making a revised proposal regarding the proposed selection and execution order of business processes based on the acquired project information 501. Therefore, the project can be efficiently advanced by reconfiguring the processes to be prioritized in accordance with changes in the project status.

[0063] Furthermore, the process proposal system 101 obtains project information 501 from the project management tool based on the project number entered by the user (S201, S202). Since the system enters the project data instead of the user having to input it, user convenience is improved.

[0064] Furthermore, the process proposal system 101 includes a project plan in the project information 501, which represents the plan of the tasks that make up the project. Therefore, the progress of the tasks can be checked using the task plan obtained from the project management tool, and the progress of the initial plan and the overall project can be grasped.

[0065] Furthermore, the process proposal system 101 obtains the completion status of deliverables, including templates to be proposed according to the deliverables created in the project, from the project management tool 111. By referring to the definition document, which is a deliverable, the system can identify the next template and determine which template should be proposed.

[0066] Furthermore, the process proposal system 101 generates warnings in revised proposals that include at least one of the following: failure to meet deadlines, excessive overtime, and concentration of tasks on specific engineers, thereby alerting the user (project manager).

[0067] Furthermore, if the project's work plan is updated, the process proposal system 101 will re-propose the selection and execution order of the business processes proposed in the first step based on the updated work plan. This allows the system to grasp changes in current data due to changes in customer requirements and re-propose processes in response to customer requirements that change after the project has started.

[0068] Furthermore, since the process proposal system 101 re-proposes the process, including displaying the proposed templates, it can improve convenience by displaying changes in the definition document which differs for each project, allowing engineers to change procedures in response to schedule change proposals.

[0069] Furthermore, the process suggestion system 101 optimizes project execution by re-proposing processes, including changes to the process execution order. For example, the work workflow may be displayed as a re-proposed process.

[0070] Furthermore, since the process proposal system 101 re-proposes the process, including information on links to the proposed templates, it can present definition documents, procedure manuals, templates to be used, etc., as a set along with the re-proposed work workflow, thereby improving convenience for engineers.

[0071] Furthermore, the process proposal system 101 re-proposes the process, including the scheduled delivery date for the proposed task, enabling deadline management at each step of the re-proposed workflow.

[0072] It should be noted that the present invention is not limited to the embodiments described above, but includes various modifications and equivalent configurations within the spirit of the attached claims. For example, the embodiments described above are described in detail for the purpose of clearly illustrating the present invention, and the present invention is not necessarily limited to having all the described configurations. Furthermore, some of the configurations of one embodiment may be replaced with those of another embodiment. Furthermore, configurations of other embodiments may be added to the configuration of one embodiment. Furthermore, some of the configurations of each embodiment may be added, deleted, or replaced with those of other embodiments.

[0073] Furthermore, each of the aforementioned configurations, functions, processing units, and processing means may be implemented in hardware, for example, by designing them as integrated circuits, or they may be implemented in software by having a processor interpret and execute programs that realize each function.

[0074] Information such as programs, tables, and files that implement each function can be stored in memory, hard disks, SSDs (Solid State Drives), or other storage media such as IC cards, SD cards, and DVDs.

[0075] Furthermore, the control lines and information lines shown are those deemed necessary for explanation purposes and do not necessarily represent all control lines and information lines required for implementation. In reality, it can be assumed that almost all components are interconnected. [Explanation of Symbols]

[0076] 101...Overall Configuration of Process Proposal System 102 ···User 103... Input Tool 104...Input section 105...Project Information Retrieval Department 106... Information Storage Department 107... Arithmetic section 108...Process Definition Section 109...Output section 110... Monitor 111...Project Management Tools 501...Project Information 502... Tailoring Input Information 503...Process definition data 504...Proposal Process Data 505...Customization process data 506... Proposal (Customized) Process Data 507...Project Status Data 508...Warning data...Re-proposal process data 509...Project Number 510... Input Project Number

Claims

1. It is a process proposal system, The system includes an arithmetic unit that executes a program and a storage device that the arithmetic unit can access. The aforementioned arithmetic unit, The first step involves searching for priority items in tailoring input information and proposed process data based on project data, extracting process definition data with matching search results and implementation priority set as proposed process data, selecting business processes to be executed in project execution from the extracted proposed process data, and proposing the execution order of the selected business processes. The second step is to obtain project information, including the project's progress, Based on the acquired project information, it is determined whether there are factors that could cause a change in the plan, whether the project deadline has not been met, whether overtime has been exceeded, or whether tasks are concentrated on a specific engineer, and it is determined that there are factors that could cause a change in the plan. The third step is to select the proposed business processes from the re-proposed process data extracted from the proposed process data and re-propose the execution order of the selected business processes. A process proposal system characterized by performing the following actions.

2. A process proposal system according to claim 1, The process proposal system is characterized in that the calculation unit acquires the project information from a project management tool based on the project number entered by the user.

3. A process proposal system according to claim 2, The process proposal system is characterized in that the project information includes a project plan representing the plan of tasks that constitute the project.

4. A process proposal system according to claim 1, The process proposal system is characterized in that the calculation unit obtains the completion status of deliverables, including templates to be proposed according to the deliverables created in the project, from a project management tool.

5. A process proposal system according to claim 1, The process proposal system is characterized in that the calculation unit generates warnings in the revised proposal that include at least one of the following: failure to meet deadlines, excessive overtime, and concentration of tasks on a specific engineer.

6. A process proposal system according to claim 1, In the third step, the calculation unit, when the project's work plan is updated, re-proposes the selection and execution order of the business processes proposed in the first step based on the updated work plan, characterized in that the process proposal system.

7. A process proposal system according to claim 6, A process proposal system characterized in that the selection and re-proposal of the execution order of the aforementioned business processes includes the display of proposed templates.

8. A process proposal system according to claim 1, A process proposal system characterized in that the selection and re-proposal of the execution order of the aforementioned business processes includes changing the process execution order.

9. A process proposal system according to claim 8, A process proposal system characterized in that the selection and re-proposal of the execution order of the process includes information on links to proposed templates.

10. A process proposal system according to claim 8, A process proposal system characterized in that the selection and re-proposal of the execution order of the aforementioned processes includes the scheduled due dates for the proposed tasks.

11. A process proposal method performed by a process proposal system, The process proposal system comprises a computing device that executes a program and a storage device accessible by the computing device. The proposed process method is, The first step involves the computing device searching for priority items in tailoring input information and proposed process data based on project-related data, extracting process definition data as proposed process data if the search results match and implementation priority is set, selecting business processes to be executed in project execution from the extracted proposed process data, and proposing the execution order of the selected business processes. The second step involves the aforementioned computing device acquiring project information, including the project's progress status. The computing device, based on the acquired project information, determines whether any of the following exceed a predetermined threshold: factors causing a change in the plan, failure to meet the project deadline, excessive overtime, or concentration of tasks on a specific engineer. If it determines that there are factors causing a change in the plan, it selects the proposed business processes from the re-proposed process data extracted from the proposed process data, and re-proposes the execution order of the selected business processes in a third step. A proposed process method characterized by including the following.

Images