Project diagnosis DB system

Abstract

Provided is a project diagnosis DB system for diagnosing whether or not a project is being run properly while the project is in progress and for providing a database in which the results of diagnoses are accumulated, wherein: a plurality of project diagnosis templates are stored, the plurality of project diagnosis templates being provided with a plurality of diagnosis items comprising diagnosis sentences based on predefined text for checking the correctness of operation of projects; a user is prompted to select a project diagnosis template for allowing the user to check the correctness of operation of the project being run; and the selected diagnosis template is registered as a project diagnosis sheet in association with information to be associated therewith.

Description

Important Notes

[0001] This specification is filed on the assumption that it will be used as a basis for claiming priority, and it is not intended that any right be granted by this specification itself. This is the applicant's own intention. [Technical field]

[0002] This invention relates to a system that provides a mechanism for accomplishing a relatively large-scale single or multiple projects with relatively reduced manpower, a mechanism for inputting and managing information for efficient resource utilization, and also to a system that can enhance the project accomplishment capabilities of the members involved in the project.In particular, the main feature is that it evaluates and diagnoses the project according to its progress. [Background technology]

[0003] Systems like the one described above have existed for some time as systems for determining whether a project is progressing smoothly. One example is disclosed in Patent Document 1. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 3-198102 Summary of the Invention [Problem to be solved by the invention]

[0005] Patent Document 1 discloses a technical idea or problem of diagnosing the probability of project success at the project progress stage.

[0006] However, in Patent Document 1, a user who wishes to perform a project diagnosis must freely consider the input contents each time they wish to perform a diagnosis, and unless the user is originally familiar with projects, it is difficult to input the information appropriately. As a result, an optimal project diagnosis cannot be performed. [Means for solving the problem]

[0007] In light of these problems, the present invention aims to develop a project diagnosis DB system that allows even those who are unfamiliar with projects to input information appropriately.

[0008] Specifically, the present invention is a project diagnostic DB system for diagnosing whether a project is being properly managed while the project is in progress and providing a database that accumulates the results, the system including a project diagnostic template storage unit that stores a plurality of project diagnostic templates each having a plurality of diagnostic items each consisting of a diagnostic statement in a predetermined sentence for checking the proper operation of the project, a project diagnostic template selection unit that allows a user to select a project diagnostic template for checking the proper operation of the project being managed, and a project diagnostic sheet registration unit that associates the selected diagnostic template with information to be associated with the template and registers it as a project diagnostic sheet. a diagnostic input receiving unit that receives diagnostic input for judging whether the project is being operated appropriately for each diagnostic item of the project diagnostic sheet; an evaluation rule storage unit that stores evaluation rules for evaluating the received diagnostic input; and an appropriate operability evaluation unit that evaluates the appropriate operability of the project based on the stored evaluation rules and the input diagnostic input. The present invention provides a project diagnosis DB system having the above-mentioned features.

[0009] The project diagnostic DB system is Compare multiple project diagnostic sheets The project diagnostic sheet comparison unit may further be provided.

[0010] The project diagnosis DB system may further include a functional unit that, after evaluating the appropriate operability of the project once, automatically evaluates the appropriate operability of the project based on data input through the schedule management, issue management, risk management, change management, or quality management functions, and outputs the improvement status.

[0011] The project diagnostic template may include at least a diagnostic statement that prompts the user to answer whether the project plan is being utilized to achieve consensus or awareness after the start of the project.

[0012] The project diagnostic template may include at least a diagnostic statement prompting the user to answer whether or not incident management is being utilized as a management indicator for the test phase and thereafter.

[0013] The project diagnostic template may include at least a diagnostic statement prompting the user to answer whether or not a master schedule is being applied to progress management of the entire project.

[0014] The project diagnostic template may include at least a diagnostic statement that prompts the user to answer the level of involvement or the degree of influence of members who are concurrently engaged in both regular work and the project.

[0015] The project diagnostic template may include a diagnostic statement that prompts the user to respond to at least whether information has been shared with the relevant parties, whether consensus has been reached with the relevant parties, or whether consensus has been reached with the relevant parties.

[0016] The project diagnostic template may include a diagnostic statement that prompts the user to answer at least whether the criteria for issues regarding which information should be shared immediately with higher-level organizations are clearly defined, whether quantitative management is performed, or whether the department and plan for dealing with the issues are clearly defined.

[0017] The project diagnostic template may include a diagnostic statement that prompts the user to respond as to whether or not the parties involved have agreed on the necessity of determining a baseline or a judgment criterion, or of taking action against a change.

[0018] The project diagnostic template may include a diagnostic statement that prompts the user to respond as to whether or not a phase can be started after clarifying at least what the deliverables are.

[0019] The project diagnostic template may include at least a diagnostic statement prompting the user to respond as to whether or not the use of a list to centrally manage requirements has reduced misunderstandings among the parties involved and improved the quality of the upstream process of the project.

[0020] The project diagnostic template may include a diagnostic statement that prompts the user to answer whether or not the creation rules for a work schedule or the progress rate settings have been clarified.

[0021] The project diagnostic template may include a diagnostic statement that prompts the user to answer whether or not the user has confirmed the consistency between the master schedule and the work schedule, or the consistency between the deliverables and the work schedule.

[0022] The project diagnostic template may include at least a diagnostic statement prompting the user to respond as to whether quality assurance is performed by clarifying who will review the deliverables, registering review tasks in a work schedule, or visualizing the progress of the review.

[0023] The project diagnostic template may include a diagnostic statement that prompts the user to answer whether or not the participation schedule of undecided members or the validity of skills and man-hours have been confirmed.

[0024] The project diagnostic template may include at least a diagnostic statement prompting the user to answer whether the meeting is being set up with consideration for reporting to higher-level personnel, whether the meeting content is being reviewed depending on the situation, or whether the planned meeting is being appropriately managed.

[0025] The project diagnostic template may include at least a diagnostic statement that prompts the user to respond as to whether an appropriate number of risks are extracted or project-specific measures are considered in risk management.

[0026] <Effect of the Invention> As a result, it is possible to provide a project diagnosis DB system that allows even those who are not familiar with projects to input information for appropriately evaluating the status of a project. Furthermore, an appropriate evaluation of the project's status is made based on the input information. [Brief description of the drawings]

[0027] [Figure 1] FIG. 1 is a diagram showing a functional configuration of a project diagnosis DB system according to a first embodiment. [Diagram 2] FIG. 1 is a diagram showing a hardware configuration of a project diagnosis DB system according to a first embodiment. [Diagram 3] FIG. 1 is a diagram showing a process flow when the project diagnosis DB system according to the first embodiment is used. [Figure 4] FIG. 13 is a diagram showing a functional configuration of a project diagnosis DB system according to a second embodiment. [Diagram 5] FIG. 13 is a diagram showing a hardware configuration of a project diagnosis DB system according to a second embodiment. [Figure 6] FIG. 11 is a diagram showing a process flow when the project diagnosis DB system according to the second embodiment is used. [Figure 7] FIG. 13 is a diagram showing a functional configuration of a project diagnosis DB system according to a third embodiment. [Figure 8] FIG. 13 is a diagram showing a hardware configuration of a project diagnosis DB system according to a third embodiment. [Figure 9] FIG. 13 is a diagram showing a process flow when the project diagnosis DB system according to the third embodiment is used. [Figure 10] FIG. 13 is a diagram showing a functional configuration of a project diagnosis DB system according to a fourth embodiment. [Figure 11] FIG. 13 is a diagram showing a hardware configuration of a project diagnosis DB system according to a fourth embodiment. [Figure 12] FIG. 13 is a diagram showing a process flow when the project diagnosis DB system according to the fourth embodiment is used. [Figure 13] FIG. 13 is a diagram showing a functional configuration of a project diagnosis DB system according to a fifth embodiment. [Figure 14] FIG. 13 is a diagram showing a hardware configuration of a project diagnosis DB system according to a fifth embodiment. [Figure 15] FIG. 13 is a diagram showing a process flow when the project diagnosis DB system according to the fifth embodiment is used. [Figure 16] FIG. 23 is a diagram showing a functional configuration of a project diagnosis DB system according to the sixth embodiment. [Figure 17] FIG. 23 is a diagram showing a hardware configuration of a project diagnosis DB system according to the sixth embodiment. [Figure 18] FIG. 23 is a diagram showing a process flow when the project diagnosis DB system according to the sixth embodiment is used. [Figure 19] FIG. 23 is a diagram showing a functional configuration of a project diagnosis DB system according to the seventh embodiment. [Figure 20] FIG. 23 is a diagram showing a hardware configuration of a project diagnosis DB system according to the seventh embodiment. [Figure 21] FIG. 23 is a diagram showing a process flow when the project diagnosis DB system according to the seventh embodiment is used. [Figure 22] FIG. 13 is a diagram showing a functional configuration of a project diagnosis DB system according to an eighth embodiment. [Figure 23] FIG. 13 is a diagram showing a hardware configuration of a project diagnosis DB system according to an eighth embodiment. [Figure 24] FIG. 23 is a diagram showing a process flow when the project diagnosis DB system according to the eighth embodiment is used. [Diagram 25] FIG. 13 is a diagram showing a functional configuration of a project diagnosis DB system according to a ninth embodiment. [Figure 26] FIG. 13 is a diagram showing a hardware configuration of a project diagnosis DB system according to a ninth embodiment. [Figure 27] FIG. 23 is a diagram showing a process flow when the project diagnosis DB system according to the ninth embodiment is used. [Figure 28] FIG. 23 is a diagram showing a functional configuration of a project diagnosis DB system according to a tenth embodiment. [Figure 29] FIG. 23 is a diagram showing a hardware configuration of a project diagnosis DB system according to a tenth embodiment. [Diagram 30] FIG. 23 is a diagram showing a process flow when the project diagnosis DB system according to the tenth embodiment is used. [Diagram 31] FIG. 23 is a diagram showing a functional configuration of a project diagnosis DB system according to an eleventh embodiment. [Diagram 32] FIG. 23 is a diagram showing a hardware configuration of a project diagnosis DB system according to an eleventh embodiment. [Diagram 33] FIG. 23 is a diagram showing a process flow when the project diagnosis DB system in the eleventh embodiment is used. [Diagram 34] FIG. 13 is a diagram showing a specific example of a diagnostic statement of a project diagnostic template. [Diagram 35] FIG. 13 is a diagram showing a specific example of a diagnostic statement of a project diagnostic template. [Diagram 36] FIG. 13 is a diagram showing a specific example of a diagnostic statement of a project diagnostic template. [Figure 37] FIG. 13 is a diagram showing a specific example of a diagnostic statement of a project diagnostic template.

[0028] Hereinafter, the embodiments of the present invention will be described with reference to the accompanying drawings. The relationship between the embodiments and the claims is as follows. The present invention should not be limited to these embodiments, and may be embodied in various forms without departing from the spirit of the present invention.

[0029] <Hardware that can constitute the present invention> The present invention is in principle an invention that utilizes an electronic computer, but it can also be realized by software, hardware, or a combination of software and hardware. The hardware that realizes all or part of each of the constituent elements of the present invention is composed of the basic components of a computer, such as a CPU, memory, bus, input / output devices, various peripheral devices, and a user interface. The various peripheral devices include storage devices, interfaces such as the Internet, devices such as the Internet, displays, keyboards, mice, speakers, cameras, videos, televisions, various sensors for grasping the production status in laboratories or factories (flow rate sensors, temperature sensors, weight sensors, liquid volume sensors, infrared sensors, shipment counters, package counters, foreign body inspection devices, defective product counters, radiation inspection devices, surface condition inspection devices, circuit inspection devices, human presence sensors, worker work status grasping devices (with video, ID, PC work volume, etc.)), CD devices, DVD devices, Blu-ray devices, USB memory, USB memory interfaces, removable hard disks, general hard disks, projector devices, SSDs, telephones, fax machines, copy machines, printers, movie editing devices, various sensor devices, etc. In addition, the present system does not necessarily have to be configured by one housing, and may be configured by connecting multiple housings by communication. In addition, communication may be LAN, WANWifi, Bluetooth (registered trademark), infrared communication, ultrasonic communication, and further, some of the systems may be installed across borders. Furthermore, each of the multiple housings may be operated by a different entity, or may be operated by a single entity. The entity operating the system of the present invention may be single or multiple. The invention may also be configured as a system including, in addition to the present system, a terminal used by a third party, and a terminal used by yet another third party. These terminals may also be installed across borders. Furthermore, in addition to the present system and the terminals, devices used to register related information of third parties, related persons, and databases for recording the contents of registration may be provided. These may be provided in the present system, or may be provided outside the present system to configure the present system so that such information can be used. <Satisfying the use of the laws of nature in the present invention> The present invention functions through the collaboration of computers, communication equipment, and software. It not only enables the processing that project participants have traditionally performed in interviews to be processed using ICT, but also includes processing unique to ICT, such as determining the effects of many complex information exchanges, procedures, authentication, and settlements related to projects using ICT, and supporting the accumulation, retention, and exchange of useful information that fulfills all the necessary requirements that would normally require skill through ICT, making it a so-called business model patent. In addition, various identification information, risk information, issue information, and task information are retained and processed in each section, and from this perspective, if the present invention is judged based on the resources such as computers in the claims and specifications and the technical common sense related to those matters, it is considered that the present invention utilizes a law of nature.

[0030] <The significance of using the laws of nature required in patent law> The use of the laws of nature required by the Patent Law is required to ensure that the invention can be used industrially and usefully, from the viewpoint that the invention must have industrial applicability and contribute to the development of industry based on the purpose of the law. In other words, it is required that the invention be industrially useful, that is, the effect of the invention declared at the time of application can be reproduced with a certain degree of certainty by implementing the invention. From this perspective, the use of the laws of nature is interpreted as the function of each of the invention-specific matters (invention constituent elements), which are the configuration of the invention for achieving the effect of the invention, being achieved by utilizing the laws of nature. Furthermore, the effect of the invention should be that it is possible to provide a predetermined usefulness to the user who uses the invention, and should not be viewed from the perspective of how the user feels or thinks about that usefulness. Therefore, even if the effect that the user obtains from this system is a psychological effect, the effect itself is not subject to the required use of the laws of nature. Embodiment 1

[0031] In this embodiment, , PThe present invention provides a project diagnostic DB system for diagnosing whether a project is being operated properly while the project is in progress and providing a database that accumulates the results, the project diagnostic DB system holds a plurality of project diagnostic templates each having a plurality of diagnostic items each consisting of a diagnostic statement in a predetermined sentence for checking the proper operation of the project, allows a user to select a project diagnostic template for checking the proper operation of the project being operated, acquires a diagnostic timing that is the timing for diagnosing the project for associating it with a project diagnostic sheet described later, acquires project identification information that is identification information of the project to be diagnosed for associating it with the project diagnostic sheet described later, registers the project diagnostic sheet including the selected diagnostic template in association with the information to be associated, accepts diagnostic input that is an input for determining whether the project is being operated properly for each diagnostic item on the project diagnostic sheet, holds evaluation rules for evaluating the received diagnostic input, and evaluates the proper operation of the project based on the held evaluation rules and the input diagnostic input.

[0032] The project diagnosis DB system according to this embodiment will be described below in terms of its functional configuration, hardware configuration, and processing flow.

[0033] FIG. 1 is a diagram showing the functional configuration of a project diagnosis DB system of the first embodiment. The project diagnosis DB system (0100) of this embodiment has a project diagnosis template holding unit (0101), a project diagnosis template selection unit (0102), a diagnosis timing acquisition unit (0103), a project identification information acquisition unit (0104), a project diagnosis sheet registration unit (0105), a diagnosis input reception unit (0106), an evaluation rule holding unit (0107), and an appropriate operability evaluation unit (0108). In addition, it may have a timing registration unit and a diagnosis timing judgment unit. The same applies to the following embodiments.

[0034] This system diagnoses whether a project is being managed appropriately while the project is in progress, and provides a database that accumulates the results, and this applies to all of the following embodiments.

[0035] The "project diagnostic template storage unit" stores a plurality of project diagnostic templates each having a plurality of diagnostic items each consisting of a diagnostic statement in a predetermined sentence for checking the proper operation of a project. The opportunity Possesses the ability. It is desirable that the "project diagnostic template" has a hierarchical structure in which a project management type, which is a mid-level management hierarchy, is made up of a plurality of diagnostic items, a knowledge area, which is a higher level hierarchy, is made up of a plurality of project management types, and the entire structure is made up of a plurality of knowledge areas. It is also desirable that the project management types of the project diagnostic template stored in the project diagnostic template storage section include at least one of a planning diagnostic management type that quantitatively diagnoses a project from the perspective of planning, an issue manageability management type that quantitatively diagnoses a project from the perspective of issue manageability, a change manageability management type that quantitatively diagnoses a project from the perspective of change manageability of the project's process, an incident manageability management type that quantitatively diagnoses a project from the perspective of incident management, a standard document manageability management type that quantitatively diagnoses a project from the perspective of standard documents, and a scope manageability management type that quantitatively diagnoses a project from the perspective of scope management, which indicates future prospects.

[0036] The "Project Diagnostic Template" is used to diagnose a project, and is intended for the person responsible for the project to fill in the information required by the template, typically configured to allow selection from pull-down menus, check boxes, drop-down forms, etc., or to determine the level and fill in or select. After examining what conditions are necessary for a project to be successful, the template was found to have the following academically appropriate configuration.

[0037] First, the project status is captured in terms of the following major items: integration, scope, schedule, cost, quality, resources, communication, risk, procurement, and stakeholder knowledge.

[0038] "Integration" should indicate the appropriate start status for the start of a project and the appropriate end status for the end of a project, and is a template area for checking whether these have been realized or will be realized. "Integration" also checks the project based on how the project execution side should respond to change requests that arise during project execution. "Integration" is a knowledge area that has a cross-sectional effect on other management areas and check areas described below, and can be said to be the most important management area. Therefore, other items in the overall project diagnostic template are configured to be affected by this integration item. "Integration" can be further subdivided into "project planning," "issue management," "change management," "incident management," and "configuration management" to more precisely execute the integration function. "Project diagnostic template" must have diagnostic functions for the above-mentioned subdivided items.

[0039] "Project Plan" , P There is a project plan, 「Information regarding the project's background, overview, process definition, master schedule, project execution structure, and project management rules must be defined, and check items related to these must be provided.

[0040] For "Issue management," the check items in the project diagnostic template need to be configured on the premise that "issue management is being implemented, issues are being added and updated regularly, and the person in charge and the planned schedule for dealing with them are clearly defined."

[0041] "Change management" is carried out on the premise that "the standards and rules for the subject of change management are clearly defined, all change requests after the baseline is determined are centrally managed, and decisions on whether or not to respond can be made based on criteria such as cost-effectiveness," and the check items in the project diagnostic template are constructed based on this premise.

[0042] "Incident management" is configured on the premise that "incident management is being implemented," and the project diagnostic template is configured on the premise that incident management is being implemented or will be implemented. Here, "incident" refers to a "disturbance event" that affects the execution of a project.

[0043] "Configuration management" is performed on the premise that configuration management of documents and programs (those for project implementation, not necessary if not present) is being performed. Therefore, the check items included in the project diagnostic template for configuration management are check items related to this configuration management.

[0044] As described above, a project diagnostic template is made up of multiple diagnostic items for diagnosing one theme, and when selecting a project diagnostic template (described later), the project manager is responsible for deciding whether or not to select it on a theme-by-theme basis. Project diagnostic templates are designed to be selected according to the project that is actually planned, and one project diagnostic sheet is made up to correspond to any project. Project types include projects to create hardware such as machinery, equipment, plants, and products (in this case, Project diagnostic templates (In this case, the diagnostic items include the process of testing and experimentation.) Project diagnostic templates (In this case, the project will include the diagnostic items performed during the requirements definition process.) Project diagnostic templates Diagnostic items that must be performed during small-scale demonstrations Includes ), and influence projects that aim to have an impact on society (in this case Project diagnostic templates Diagnostic items that are always included in the questionnaire survey Includes ), structural change projects to change the social structure to prevent disasters, epidemics, etc., or to recover from their adverse effects (in this case Project diagnostic templates Diagnostic items always carried out in opinion polls Includes ) etc. There is. Appropriate templates can be selected according to the attributes of various projects.

[0045] The final diagnostic items of the project diagnostic template are configured to have a conceptual hierarchical structure, such as major items (e.g., "integration"), medium items (e.g., "project plan"), and minor diagnostic items (e.g., "project plan is available").

[0046] " projectThe diagnostic template may be configured to be selectable on a medium-item basis, or may be configured to be selectable on a large-item basis, or may be configured to be selectable as a whole set of large items. However, since diagnostic items are mutually related, and there are also mutually related between medium items and large items, it is preferable that the project diagnostic template is configured to be selectable as a whole set of large items.

[0047] The stored "project diagnostic templates" are comprehensively prepared to accommodate a variety of projects. Multiple templates are displayed on the screen, and the contents of each template can be understood from the displayed template name and summary. Therefore, the user can select a template from the screen and choose the template that is most suitable for the project that he or she is about to start.

[0048] The present invention is characterized in that a template can be selected from a collection of templates. The selected template is configured to avoid missing any diagnosis by adopting a style of diagnosing the essential management items in a project, which are indicated by the intermediate items located above the diagnosis items, from multiple angles. Although some of these essential management items may differ depending on the type of project, essential management items corresponding to almost all types of projects constitute the project diagnosis template and are selectable.

[0049] The "project diagnostic template selection unit" has a function of allowing a user to select a project diagnostic template for checking the proper operation of a project being managed. The project diagnostic template selection is shown on the display in a table of contents format, and the interface is configured so that the contents of the template can be gradually recognized in a hierarchical structure. The lowest level of the hierarchical structure is the diagnostic items of that project diagnostic template itself. Selection is configured to be made by check boxes, pull-down menus, drop-down forms, etc. Furthermore, it is preferable that the configuration be configured so that the configuration of past project diagnostic sheets can be viewed and referenced when making a selection. This is because the suitability of a diagnosis can be judged by knowing the diagnostic contents of past successful projects.

[0050] The "project diagnosis sheet registration section" has a function of registering the selected diagnostic template as a project diagnosis sheet by associating it with the information to be associated with it. By registering it, the contents of the project diagnosis sheet are finalized.

[0051] The "diagnosis input receiving unit" has a function of receiving a diagnosis input for determining whether the project is being properly operated for each diagnosis item of the project diagnosis sheet. In addition, the diagnosis input receiving unit may have a predetermined format input receiving means configured to receive one or more of the following for the diagnosis items of the diagnostic template: selection of an option, or input of a numerical level set within a predetermined range.

[0052] The 'evaluation rule storage unit' has a function of storing evaluation rules for evaluating a received diagnostic input.

[0053] The "proper operability evaluation unit" has a function of evaluating the proper operability of the project based on the evaluation rules stored therein and the input diagnostic input.

[0054] It is preferable that the appropriate operation evaluation unit has a knowledge area evaluation means for evaluating the project in units of knowledge areas at each diagnosis timing.

[0055] In addition to the above-mentioned features, it is desirable that the proper operability evaluation unit of the present invention has a common evaluation means for evaluating each knowledge area based on a common evaluation axis even when a template included in a different project diagnosis sheet is selected and the diagnosis results are entered.

[0056] The above is the basic configuration of this system, but this system may further include a "project diagnostic sheet generation unit" that may have the function of generating a project diagnostic sheet including a selected diagnostic template based on the selected diagnostic template. By generating a project diagnostic sheet, the project diagnostic template to be used for diagnosing the project is basically determined. At this point, the selection of the project diagnostic template is completed. However, it is possible to select the project diagnostic template again after generation. diagnosis It is also possible to configure the template selection to allow the user to return to the template selection.

[0057] This system may further include a "timing registration unit" that may have a function of registering the diagnosis timing, which is the timing for diagnosing the project using the registered project diagnosis sheet, in association with the project identification information. This function is not essential, but inputting the timing allows for flexible judgment. The timing of project diagnosis is basically configured to be performed at the times of "start-up," "requirements definition," "basic design," "implementation," "integration test," "system test," "operation test," "transition," and "closure" of the project.

[0058] "Start-up" here means exactly the launch of the project, the initial point at which the project begins. At this point, the basic plan and structure of the project are solidified.

[0059] "Requirements definition" is the process of determining what is needed for a project. It is the phase in which the items necessary to achieve the project's objectives are finally decided.

[0060] "Basic design" is the phase in which procedures are defined to meet the requirements for project completion as determined in the requirements definition. This basic design will determine the implementation of the next phase.

[0061] "Implementation" refers to the process of realizing the necessary items defined in the basic design and obtaining concrete deliverables.

[0062] "Integration testing" is a process of integrating the implementation results of multiple groups and coordinating them with each other. Originally, the results of implementation are something that produce a single effect by combining multiple things, and the process of integrating the whole is called "integration testing". before In stages, the implementation deliverables are tested for their interoperability.

[0063] "System testing" is the final stage of integration testing, in which all necessary project components are integrated together to test whether they are effective in achieving the project's objectives. While integration testing involves combining parts of the implementation deliverables, system testing examines the effectiveness of the whole.

[0064] "Operational testing" involves running the system in an environment close to actual operation, to see whether the appropriate effects obtained in system testing are realized in an environment close to the actual operation.

[0065] "Transition" is the process of migrating the system to the environment in which the system operator actually operates the system, if the appropriate effect is obtained in the operational test, and porting it there. Since the system test environment and the actual operation environment are different, this is the phase in which the appropriate project effect demonstrated in the operational test can be obtained.

[0066] The "closure" phase involves confirming that the appropriate effects have been achieved after the transition, determining the conditions necessary for the effects of the designed project deliverables to be properly implemented throughout the intended period, and confirming that the necessary conditions are met, thereby ending project activities.

[0067] The optional "diagnosis timing determination unit" has a function of determining whether a registered diagnosis timing has arrived. The diagnosis timing to be registered in advance is, for example, the scheduled start date of each phase.

[0068] <Hardware configuration> 2 is a diagram showing an example of a hardware configuration in this embodiment. The hardware configuration of the project diagnosis DB system in this embodiment will be described with reference to the diagram.

[0069] As shown in this diagram, the computer is composed of a chipset, CPU, non-volatile memory, main memory, various buses, BIOS, various interfaces, real-time clock, etc., which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, etc. The various programs and data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0070] Chipset A "chipset" is a set of large-scale integrated circuits (LSIs) mounted on a computer motherboard that integrates a communication function between the CPU's external bus and the standard bus that connects memory and peripheral devices, in other words, a bridge function. There are cases where a two-chipset configuration is used, and cases where a single chipset configuration is used. The north bridge is located on the side closest to the CPU and main memory, and the south bridge is located on the side farther away and serves as an interface with the relatively slow external I / O. (North Bridge) The northbridge includes a CPU interface, memory controller, and graphics interface. Most of the functions of a conventional northbridge may be handled by the CPU. The northbridge is connected to the main memory's memory slot via a memory bus, and to the graphics card slot of the graphics card via a high-speed graphics bus (AGP, PCI Express). (South Bridge) The south bridge is connected to the PCI interface (PCI slot) via the PCI bus, and is responsible for I / O functions such as ATA (SATA) interface, USB interface, and Ethernet interface, as well as sound functions. Incorporating circuits to support PS / 2 ports, floppy disk drives, serial ports, parallel ports, and ISA buses, which do not require or are impossible to operate at high speed, can hinder the speed of the chipset itself, so they can be separated from the south bridge chip and placed in a separate LSI called a super I / O chip. A bus is used to connect the CPU (MPU) to peripheral devices and various control units. The bus is connected by the chipset. The memory bus used to connect to the main memory can instead adopt a channel structure to increase speed. A serial bus or a parallel bus can be used as the bus. While a serial bus transfers data one bit at a time, a parallel bus transmits the original data itself or multiple bits extracted from the original data as a single block and transmits it simultaneously over multiple communication paths. A dedicated line for the clock signal is set up in parallel with the data line to synchronize the data demodulation on the receiving side. It is also used as a bus to connect the CPU (chipset) to external devices, and includes GPIB, IDE / (Parallel)ATA, SCSI, PCI, etc. Since there is a limit to how fast it can be made, in PCI Express, an improved version of PCI, and Serial ATA, an improved version of Parallel ATA, the data line can be a serial bus.

[0071] CPU The CPU reads a sequence of instructions called a program in the main memory in order, interprets and executes them, and outputs information consisting of signals to the main memory. The CPU functions as the center of calculations within the computer. The CPU is composed of the CPU core, which is the center of calculations, and its peripheral parts, and includes registers, cache memory, an internal bus connecting the cache memory and the CPU core, a DMA controller, a timer, and an interface with the connection bus to the north bridge. A single CPU (chip) may have multiple CPU cores. In addition to the CPU, processing may be performed by a graphics interface (GPU) or FPU.

[0072] <Non-volatile memory> (HDD) The basic structure of a hard disk drive consists of a magnetic disk, a magnetic head, and an arm on which the magnetic head is mounted. The external interface can be SATA (previously ATA). A high-performance controller, such as SCSI, is used to support communication between hard disk drives. For example, when copying a file to another hard disk drive, the controller can read the sectors and transfer them to the other hard disk drive for writing. At this time, the host CPU's memory is not accessed. Therefore, there is no increase in the CPU load.

[0073] <Main memory> The CPU directly accesses and executes various programs in main memory. Main memory is a volatile memory that uses DRAM. Programs in main memory are expanded from non-volatile memory to main memory upon receiving a program start command. The CPU then executes the program according to various execution commands and execution procedures within the program.

[0074] Operating System (OS) An operating system is used to manage the resources on a computer so that applications can use them, to manage various device drivers, and to manage the computer itself (the hardware). Small computers sometimes use firmware as the operating system.

[0075] ≪BIOS≫ The BIOS causes the CPU to execute procedures for starting up the computer hardware and running the operating system, and is most typically the hardware that the CPU reads first when it receives a computer startup command. The addresses of the operating system stored on the disk (non-volatile memory) are written here, and the BIOS loaded into the CPU loads the operating system sequentially into main memory and makes it operational. The BIOS also has a check function that checks the presence or absence of various devices connected to the bus. The results of the check are stored in the main memory and made available to the operating system as appropriate. The BIOS may also be configured to check for external devices, etc.

[0076] The above also applies to other embodiments.

[0077] As shown in the figure, the present invention can basically be configured with a general-purpose computer program and various devices. The computer basically operates in a form in which a program recorded in a non-volatile memory is loaded into the main memory, and processing is executed by the main memory, the CPU, and various devices. Communication with the devices is performed via an interface connected to a bus line. Possible interfaces include a display interface, a keyboard, and a communication buffer.

[0078] As shown in the figure, the system includes a "project diagnostic template holding program" for holding a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project, a "project diagnostic template selection program" for allowing a user to select a project diagnostic template for checking the proper operability of a project he or she is managing, a "diagnosis timing acquisition program" for acquiring a diagnostic timing for diagnosing a project in order to associate the diagnostic timing with a project diagnostic sheet described later, a "project identification information acquisition program" for acquiring project identification information for identifying a project to be diagnosed in order to associate the project diagnostic sheet described later, a "project diagnostic sheet registration program" for registering a selected diagnostic template as a project diagnostic sheet by associating it with information to be associated with the project, a "diagnosis input reception program" for receiving a diagnostic input for determining whether a project is being properly operated for each diagnostic item on the project diagnostic sheet, an "evaluation rule holding program" for holding evaluation rules for evaluating the received diagnostic input, and a "proper operability evaluation program" for evaluating the proper operability of the project based on the evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In this computer, a non-volatile memory, a main memory, a CPU, and an interface (for example, a display, a keyboard, communication, etc.) are connected to a bus line so that they can communicate with each other.

[0079] <Processing flow> <Processing flow> FIG. 3 is a diagram showing a process flow when the project diagnosis DB system in this embodiment is used. The process flow in this embodiment is an operation method of the project diagnosis DB system, which is a computer having a project diagnosis template storage step (S0301), a project diagnosis template selection step (S0302), a diagnosis timing acquisition step (S0303), a project identification information acquisition step (S0304), a project diagnosis sheet registration step (S0305), a diagnosis input reception step (S0306), an evaluation rule storage step (S0307), and a proper operability evaluation step (S0308). In addition, a project diagnosis sheet generation step, a timing registration step, and a diagnosis timing judgment step may be included, and this is the same in other embodiments. Each step will be explained below.

[0080] The "project diagnostic template storage step" is a step of storing a plurality of project diagnostic templates each consisting of a diagnostic statement in a predetermined form for checking the proper operation of a project.

[0081] The "project diagnostic template selection step" is a stage in which the user is prompted to select a project diagnostic template for checking the proper operation of the project he or she is managing.

[0082] The "diagnosis timing acquisition step" is a stage in which the diagnosis timing, which is the timing for diagnosing the project, is acquired in order to associate it with the project diagnosis sheet described later.

[0083] The "project identification information acquisition step" is a stage in which project identification information, which is identification information for a project to be diagnosed, is acquired in order to associate the project identification information with a project diagnosis sheet, which will be described later.

[0084] The "project diagnosis sheet registration step" is a stage in which the selected diagnostic template is associated with information to be associated, such as the diagnostician and the timing of the diagnosis, and registered as a project diagnosis sheet.

[0085] The "diagnosis input receiving step" is a stage for receiving a diagnosis input for determining whether the project is being operated appropriately for each diagnosis item on the project diagnosis sheet.

[0086] The "evaluation rule storage step" is a step for storing evaluation rules for evaluating the received diagnostic input. The evaluation rules include weights for each evaluation item. For example, the "scope" and "quality" areas of the evaluation items may be given higher importance than "procurement" and "human resources."

[0087] The "proper operability evaluation step" is a stage in which the proper operability of the project is evaluated based on the stored evaluation rules and the input diagnosis results.

[0088] The "project diagnosis sheet generating step" which may be included in addition to the above is a step of generating a project diagnosis sheet including the selected diagnosis template based on the selected diagnosis template.

[0089] The "timing registration step" is a step of registering the diagnosis timing, which is the timing for diagnosing the project using the registered project diagnosis sheet, in association with the project identification information.

[0090] The "diagnosis timing determination step" is a step of determining whether the registered diagnosis timing has arrived.

[0091] In addition to the embodiment described above, this embodiment provides a project diagnosis DB system having the feature of having a function of acquiring diagnostician identification information that identifies the diagnostician who inputs the diagnosis into the diagnostic sheet in order to associate it with the project diagnostic sheet.

[0092] <Functional configuration> Fig. 4 is a diagram showing the functional configuration of this embodiment. The project diagnosis DB system (0400) of this embodiment has a project diagnosis template holding unit (0401), a project diagnosis template selection unit (0402), a project diagnosis sheet registration unit (0404), a diagnosis input reception unit (0407), an evaluation rule holding unit (0408), and an appropriate operability evaluation unit (0409) as in the first embodiment, and is characterized in that it further has a project diagnosing person identification information acquisition unit (0410). The following description will be given excluding the functions already described.

[0093] The "project diagnostician identification information acquisition unit" has a function of acquiring diagnostician identification information for identifying a diagnostician who inputs a diagnosis on a diagnostic sheet in order to associate the diagnostician with the project diagnostic sheet.

[0094] <Hardware configuration> 5 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (0510), a CPU (0501), a non-volatile memory (0503), a main memory (0504), various buses (0502a to 0502e), a BIOS (0507), various interfaces (0505, 0506, 0508), a real-time clock (0509), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0095] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0096] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnostic timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with the information to be associated and registers it as a project diagnostic sheet; a "diagnostic input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that the non-volatile memory, main memory, CPU, and interfaces (e.g., display, keyboard, communication, etc.) are connected to a bus line and can communicate with each other. In addition to the first embodiment, it is further equipped with a "project diagnostician identification information acquisition program" that acquires diagnostician identification information that identifies the diagnostician who inputs the diagnosis on the diagnostic sheet in order to associate the diagnostician with the project diagnostic sheet.

[0097] <Processing flow> Fig. 6 is a diagram showing a process flow when the project diagnosis DB system in this embodiment is used. This is an operation method of the project diagnosis DB system, which is a computer having a project diagnosis template holding step (S0601), a project diagnosis template selection step (S0602), a diagnosis timing acquisition step (S0603), a project identification information acquisition step (S0604), a project diagnosing person identification information acquisition step (S0605), a project diagnosis sheet registration step (S0606), a diagnosis input reception step (S0607), an evaluation rule holding step (S0608), and a proper operability evaluation step (S0609). Note that each step except for the project diagnosing person identification information acquisition step is the same as that of the first embodiment.

[0098] The "step of acquiring project diagnostician identification information" is a step of acquiring diagnostician identification information for identifying a diagnostician who inputs a diagnosis on the diagnostic sheet in order to associate the diagnostician identification information with the project diagnostic sheet.

[0099] In addition to the above-described embodiment, this embodiment provides a project diagnosis DB system having a feature of having a function of holding project diagnosis sheets associated with a plurality of project identification information.

[0100] <Functional configuration> Fig. 7 is a diagram showing the functional configuration of this embodiment. The project diagnostic DB system (0700) of this embodiment has a project diagnostic template holding unit (0701), a project diagnostic template selection unit (0702), a project diagnostic sheet registration unit (0703), a diagnostic input reception unit (0704), an evaluation rule holding unit (0705), and an appropriate operability evaluation unit (0706) as in the first embodiment, and is characterized in that it further has a project diagnostic sheet holding unit (0707) that holds project diagnostic sheets associated with multiple project identification information. The following description will be given excluding the functions already described.

[0101] The "project diagnosis sheet storage unit" has a function of storing project diagnosis sheets associated with a plurality of project identification information.

[0102] <Hardware configuration> Fig. 8 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (0810), a CPU (0801), a non-volatile memory (0803), a main memory (0804), various buses (0802a to 0802e), a BIOS (0807), various interfaces (0805, 0806, 0808), a real-time clock (0809), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0103] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0104] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnostic timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with the information to be associated and registers it as a project diagnostic sheet; a "diagnostic input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that the non-volatile memory, main memory, CPU, and interfaces (for example, display, keyboard, communication, etc.) are connected to a bus line and can communicate with each other. In addition to the first embodiment, the computer is further equipped with a "project diagnosis sheet holding program" for holding project diagnosis sheets associated with multiple project identification information.

[0105] <Processing flow> FIG. 9 is a diagram showing a process flow when the project diagnosis DB system in this embodiment is used. 9 01) and the project diagnosis template selection step (S0 902) and the diagnostic timing acquisition step (S0 9 03) and the project identification information acquisition step (S0 9 04) and Project Diagnostic Sheet Maintenance Step (S0 9 05) and the project diagnostic sheet registration step (S0 9 06) and the diagnostic input reception step (S0 9 07) and the evaluation rule retention step (S0 9 08) and the appropriate operation evaluation step (S0 9 09) and the like. Note that, among these, each step except for the project diagnosis sheet storage step is the same as in the first embodiment.

[0106] The "project diagnosis sheet storage step" is a step of storing a project diagnosis sheet associated with a plurality of project identification information.

[0107] In addition to the above-described embodiment, this embodiment provides a project diagnosis DB system having the feature of having a function for registering one or more of the following as the timing for accepting input of diagnosis results when the project includes system design: the timing of project start-up, the timing of project requirements definition, the timing of project basic design, the timing of project implementation, the timing of project integration testing, the timing of project system testing, the timing of project system operation testing, the timing of project system migration, and the timing of project termination.

[0108] <Functional configuration> Fig. 10 is a diagram showing the functional configuration of this embodiment. The project diagnosis DB system (1000) of this embodiment has a project diagnosis template holding unit (1001), a project diagnosis template selection unit (1002), a project diagnosis sheet registration unit (1003), a diagnosis input reception unit (1004), an evaluation rule holding unit (1005), and an appropriate operability evaluation unit (1006) as in the first embodiment, and is characterized in that it further has a timing registration unit (1007). The following description will be given excluding the functions already described.

[0109] The "timing registration unit" has a function of registering, in the case of a project including system design, one or more of the following as the timing for accepting input of diagnostic results: the timing of project start-up, the timing of project requirements definition, the timing of project basic design, the timing of project implementation, the timing of project integration testing, the timing of project system testing, the timing of project system operation testing, the timing of project system migration, and the timing of project conclusion.

[0110] <Hardware configuration> Fig. 11 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (1110), a CPU (1101), a non-volatile memory (1103), a main memory (1104), various buses (1102a to 1102e), a BIOS (1107), various interfaces (1105, 1106, 1108), a real-time clock (1109), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0111] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0112] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnostic timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with the information to be associated and registers it as a project diagnostic sheet; a "diagnostic input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that the non-volatile memory, main memory, CPU, and interfaces (for example, display, keyboard, communication, etc.) are connected to a bus line and can communicate with each other. Furthermore, in addition to the first embodiment, if the project includes a system design, a timing registration program is provided which registers one or more of the following as the timing for accepting input of the diagnosis result: project start-up timing, project requirement definition timing, project basic design timing, project implementation timing, project integration test timing, project system test timing, project system operation test timing, project system migration timing, and project termination timing.

[0113] <Processing flow> 12 is a diagram showing a process flow when the project diagnosis DB system in this embodiment is used. A project diagnosis template storage step (S1201), a project diagnosis template selection step (S1202), diagnosis This is an operation method of a project diagnosis DB system, which is a computer having a timing registration step (S1203), a diagnosis timing acquisition step (S1204), a project identification information acquisition step (S1205), a project diagnosis sheet registration step (S1206), a diagnosis input reception step (S1207), an evaluation rule storage step (S1208), and an appropriate operability evaluation step (S1209). diagnosis Each step except for the timing registration step is the same as in the first embodiment.

[0114] The "timing registration step" is a step of registering one or more of the following as the timing for accepting input of the diagnosis results, in the case where the project includes system design: the timing of project launch, the timing of project requirement definition, the timing of project basic design, the timing of project implementation, the timing of project integration test, the timing of project system test, the timing of project system operation test, the timing of project system migration, and the timing of project termination.

[0115] In addition to the above-described embodiment, this embodiment provides a project diagnosis DB system having a feature of having a function of retaining the evaluation result of the proper operability of a project in association with project identification information.

[0116] <Functional configuration> Fig. 13 is a diagram showing the functional configuration of this embodiment. The project diagnosis DB system (1300) of this embodiment has a project diagnosis template storage unit (1301), a project diagnosis template selection unit (1302), a project diagnosis sheet registration unit (1303), a diagnosis input reception unit (1304), an evaluation rule storage unit (1305), and an appropriate operability evaluation unit (1306) as in the first embodiment, and is characterized in that it further has a project evaluation result storage unit (1307). The following description will be given excluding the functions already described.

[0117] The "project evaluation result storage unit" has a function of storing the evaluation results of the appropriateness of project operability in association with project identification information.

[0118] <Hardware configuration> Fig. 14 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (1410), a CPU (1401), a non-volatile memory (1403), a main memory (1404), various buses (1402a to 1402e), a BIOS (1407), various interfaces (1405, 1406, 1408), a real-time clock (1409), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0119] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0120] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnostic timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with the information to be associated and registers it as a project diagnostic sheet; a "diagnostic input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that the non-volatile memory, main memory, CPU, and interfaces (for example, display, keyboard, communication, etc.) are connected to a bus line and can communicate with each other. In addition to the first embodiment, the computer is further equipped with a "project evaluation result storage program" that stores the evaluation result of the appropriate operability of the project in association with the project identification information.

[0121] <Processing flow> Fig. 15 is a diagram showing a process flow when the project diagnosis DB system in this embodiment is used. This is an operation method of the project diagnosis DB system, which is a computer having a project diagnosis template holding step (S1501), a project diagnosis template selection step (S1502), a diagnosis timing acquisition step (S1503), a project identification information acquisition step (S1504), a project diagnosis sheet registration step (S1505), a diagnosis input reception step (S1506), an evaluation rule holding step (S1507), a proper operability evaluation step (S1508), and a project evaluation result holding step (S1509). Note that each step except for the project evaluation result holding step is the same as in the first embodiment.

[0122] The "project evaluation result storage step" is a step of storing the evaluation result of the appropriate operation of the project in association with the project identification information.

[0123] In addition to the above-described embodiment, this embodiment provides a project diagnosis DB system having a feature of having a function of searching for other project evaluation results based on a project evaluation result. This function is a function of searching for other project evaluation results that have the same phase, scale, diagnostician, etc. as a certain project evaluation result.

[0124] <Functional configuration> Fig. 16 is a diagram showing the functional configuration of this embodiment. The project diagnosis DB system (1600) of this embodiment has a project diagnosis template holding unit (1601), a project diagnosis template selection unit (1602), a project diagnosis sheet registration unit (1603), a diagnosis input reception unit (1604), an evaluation rule holding unit (1605), and an appropriate operability evaluation unit (1606) as in the first embodiment, and is characterized in that it further has an evaluation-dependent project information search unit (1607). The following description will be given excluding the functions already described.

[0125] The "evaluation-dependent project information search unit" has a function of searching for the results of evaluation of other projects based on the results of evaluation of a project.

[0126] <Hardware configuration> Fig. 17 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (1710), a CPU (1701), a non-volatile memory (1703), a main memory (1704), various buses (1702a to 1702e), a BIOS (1707), various interfaces (1705, 1706, 1708), a real-time clock (1709), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0127] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0128] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnostic timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with the information to be associated and registers it as a project diagnostic sheet; a "diagnostic input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that the non-volatile memory, main memory, CPU, and interfaces (e.g., display, keyboard, communication, etc.) are connected to a bus line and can communicate with each other. In addition to the first embodiment, it is further equipped with an "evaluation-dependent project information search program" that searches for other project evaluation results based on the project evaluation results.

[0129] <Processing flow> Fig. 18 is a diagram showing a process flow when the project diagnosis DB system in this embodiment is used. The process flow in this embodiment is an operation method of the project diagnosis DB system, which is a computer having a project diagnosis template holding step (S1801), a project diagnosis template selection step (S1802), a diagnosis timing acquisition step (S1803), a project identification information acquisition step (S1804), a project diagnosis sheet registration step (S1805), a diagnosis input reception step (S1806), an evaluation rule holding step (S1807), a proper operability evaluation step (S1808), and an evaluation-dependent project information search step (S1809). Note that each step except for the evaluation-dependent project information search step is the same as in the first embodiment.

[0130] The "evaluation-dependent project information search step" is a step of searching for other project evaluation results based on the project evaluation results.

[0131] In addition to the above-described embodiment, this embodiment provides a project diagnosis DB system having a feature of having a function for searching for project diagnosis sheets that are held.

[0132] <Functional configuration> Fig. 19 is a diagram showing the functional configuration of this embodiment. The project diagnostic DB system (1900) of this embodiment has a project diagnostic template holding unit (1901), a project diagnostic template selection unit (1902), a project diagnostic sheet registration unit (1903), a diagnostic input reception unit (1904), an evaluation rule holding unit (1905), and an appropriate operability evaluation unit (1906) as in the first embodiment, and is characterized in that it further has a project diagnostic sheet search unit (1907). The following description will be given excluding the functions already described.

[0133] The "project diagnostic sheet search unit" has a function of searching for a stored project diagnostic sheet. This project diagnostic sheet search unit may have a diagnoser key search means for searching for a project diagnostic sheet using project diagnoser identification information as a search key. It may also have a diagnostic input key search means for searching for a project diagnostic sheet using a diagnostic input as a search key.

[0134] <Hardware configuration> Fig. 20 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (2010), a CPU (2001), a non-volatile memory (2003), a main memory (2004), various buses (2002a to 2002e), a BIOS (2007), various interfaces (2005, 2006, 2008), a real-time clock (2009), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0135] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0136] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnostic timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with the information to be associated and registers it as a project diagnostic sheet; a "diagnostic input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that the non-volatile memory, main memory, CPU, and interfaces (for example, display, keyboard, communication, etc.) are connected to a bus line and can communicate with each other. In addition to the first embodiment, it is further equipped with a "project diagnosis sheet search program" for searching for the stored project diagnosis sheet.

[0137] <Processing flow> Fig. 21 is a diagram showing a process flow when the project diagnosis DB system in this embodiment is used. The process flow of this embodiment is an operation method of the project diagnosis DB system, which is a computer having a project diagnosis template holding step (S2101), a project diagnosis template selection step (S2102), a diagnosis timing acquisition step (S2103), a project identification information acquisition step (S2104), a project diagnosis sheet registration step (S2105), a project diagnosis sheet search step (S2106), a diagnosis input reception step (S2107), an evaluation rule holding step (S2108), and a proper operability evaluation step (S2109). Note that each step except for the project diagnosis sheet search step is the same as that of the first embodiment.

[0138] The "project diagnosis sheet search step" is a step of searching for a project diagnosis sheet that has been stored.

[0139] In addition to the above-described embodiment, this embodiment provides a project diagnosis DB system having a feature of having a function for comparing project diagnosis sheets.

[0140] <Functional configuration> Fig. 22 is a diagram showing the functional configuration of this embodiment. The project diagnostic DB system (2200) of this embodiment has a project diagnostic template holding unit (2201), a project diagnostic template selection unit (2202), a project diagnostic sheet registration unit (2203), a diagnostic input reception unit (2204), an evaluation rule holding unit (2205), and an appropriate operability evaluation unit (2206) as in the first embodiment, and is characterized in that it further has a project diagnostic sheet comparison unit (2207). The following description will be given excluding the functions already described.

[0141] The "project diagnostic sheet comparison unit" has a function of comparing project diagnostic sheets. This project diagnostic sheet comparison unit may have a diagnostic input project diagnostic sheet comparison means for comparing project diagnostic sheets with diagnostic input. For example, it may have an inter-diagnostician project diagnostic sheet comparison means for comparing different project diagnostic sheets with diagnostic input between a plurality of project diagnosers. It may also have a common item project diagnostic sheet comparison means for comparing project diagnostic sheets with diagnostic input in one or more of the same knowledge area, the same project management type, and the same diagnostic item between a plurality of project diagnostic sheets with diagnostic input. It may also have an average comparison output device for outputting a comparison result using an average value of diagnostic inputs of a plurality of diagnostic sheets. The project diagnostic sheet comparison unit may also have a project diagnostic sheet comparison means for calculating average values ​​for each industry, business type, or project type based on the accumulated diagnostic performance information of a plurality of projects, and setting target values ​​classified into a high-level target value, a standard target value, and a minimum target value.

[0142] <Hardware configuration> Fig. 23 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (2310), a CPU (2301), a non-volatile memory (2303), a main memory (2304), various buses (2302a to 2302e), a BIOS (2307), various interfaces (2305, 2306, 2308), a real-time clock (2309), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0143] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0144] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnostic timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with the information to be associated and registers it as a project diagnostic sheet; a "diagnostic input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that the non-volatile memory, main memory, CPU, and interfaces (for example, display, keyboard, communication, etc.) are connected to a bus line and can communicate with each other. In addition to the first embodiment, it is further equipped with a "project diagnosis sheet comparison program" for comparing project diagnosis sheets.

[0145] <Processing flow> Fig. 24 is a diagram showing a process flow when the project diagnostic DB system in this embodiment is used. The process flow of this embodiment is an operation method of the project diagnostic DB system, which is a computer having a project diagnostic template holding step (S2401), a project diagnostic template selection step (S2402), a diagnostic timing acquisition step (S2403), a project identification information acquisition step (S2404), a project diagnostic sheet registration step (S2405), a project diagnostic sheet comparison step (S2406), a diagnostic input reception step (S2407), an evaluation rule holding step (S2408), and a proper operability evaluation step (S2409). Note that each step except the project diagnostic sheet comparison step is the same as in the first embodiment.

[0146] The "project diagnosis sheet comparison step" is a step of comparing the project diagnosis sheets.

[0147] In addition to the above-described embodiment, the present embodiment acquires the input status of a diagnostic input. function and a function to output the acquired diagnosis input status.

[0148] <Functional configuration> Fig. 25 is a diagram showing the functional configuration of this embodiment. The project diagnostic DB system (2500) of this embodiment has a project diagnostic template holding unit (2501), a project diagnostic template selection unit (2502), a project diagnostic sheet registration unit (2503), a diagnostic input reception unit (2504), an evaluation rule holding unit (2505), and an appropriate operability evaluation unit (2506) as in the first embodiment, and is characterized in that it further has a diagnostic input status acquisition unit (2507) and a diagnostic input status output unit (2508). The following description will be given excluding the functions already described.

[0149] The "diagnosis input status acquisition unit" has a function of acquiring the input status of the diagnosis input.

[0150] The "diagnosis input status output unit" has a function of outputting the acquired diagnosis input status.

[0151] <Hardware configuration> Fig. 26 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (2610), a CPU (2601), a non-volatile memory (2603), a main memory (2604), various buses (2602a to 2602e), a BIOS (2607), various interfaces (2605, 2606, 2608), a real-time clock (2609), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0152] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0153] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnosis timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with information to be associated and registers it as a project diagnostic sheet; a "diagnosis input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that the non-volatile memory, main memory, CPU, and interfaces (for example, display, keyboard, communication, etc.) are connected to a bus line and can communicate with each other. In addition to the first embodiment, it is further equipped with a "diagnostic input status acquisition program" that acquires the input status of the diagnostic input, and a "diagnostic input status output program" that outputs the acquired diagnostic input status.

[0154] <Processing flow> Fig. 27 is a diagram showing a process flow when the project diagnosis DB system in this embodiment is used. The process flow of this embodiment is an operation method of the project diagnosis DB system, which is a computer having a project diagnosis template holding step (S2701), a project diagnosis template selection step (S2702), a diagnosis timing acquisition step (S2703), a project identification information acquisition step (S2704), a project diagnosis sheet registration step (S2705), a diagnosis input reception step (S2706), a diagnosis input status acquisition step (S2707), a diagnosis input status output step (S2708), an evaluation rule holding step (S2709), and a proper operability evaluation step (S2710). Note that each step except for the diagnosis input status acquisition step and the diagnosis input status output step is the same as in the first embodiment.

[0155] The "diagnosis input status acquisition step" is a stage for acquiring the input status of the diagnostic input.

[0156] The "diagnosis input status output step" is a step of outputting the acquired diagnosis input status.

[0157] In addition to the above-described embodiments, this embodiment provides a project diagnostic DB system having a feature of having a function of searching for diagnostic templates stored in a diagnostic template storage unit.

[0158] <Functional configuration> Fig. 28 is a diagram showing the functional configuration of this embodiment. The project diagnostic DB system (2800) of this embodiment has a project diagnostic template holding unit (2801), a project diagnostic template selection unit (2802), a project diagnostic sheet registration unit (2803), a diagnostic input reception unit (2804), an evaluation rule holding unit (2805), and an appropriate operability evaluation unit (2806) as in the first embodiment, and is characterized in that it further has a diagnostic template search unit (2807). The following description will be given excluding the functions already described.

[0159] The "diagnostic template search unit" has a function of searching for diagnostic templates stored in the diagnostic template storage unit.

[0160] <Hardware configuration> Fig. 29 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (2910), a CPU (2901), a non-volatile memory (2903), a main memory (2904), various buses (2902a to 2902e), a BIOS (2907), various interfaces (2905, 2906, 2908), a real-time clock (2909), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0161] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0162] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnostic timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with the information to be associated and registers it as a project diagnostic sheet; a "diagnostic input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that the non-volatile memory, main memory, CPU, and interfaces (e.g., display, keyboard, communication, etc.) are connected to a bus line and can communicate with each other. In addition to the first embodiment, the computer is further equipped with a "diagnostic template search program" that searches for diagnostic templates stored in the diagnostic template storage unit.

[0163] <Processing flow> Fig. 30 is a diagram showing a process flow when the project diagnostic DB system in this embodiment is used. The process flow of this embodiment is an operation method of the project diagnostic DB system, which is a computer having a project diagnostic template storage step (S3001), a project diagnostic template selection step (S3002), a diagnostic timing acquisition step (S3003), a project identification information acquisition step (S3004), a project diagnostic sheet registration step (S3005), a diagnostic template search step (S3006), a diagnostic input reception step (S3007), an evaluation rule storage step (S3008), and a proper operability evaluation step (S3009). Note that each step except for the diagnostic template search step is the same as in the first embodiment.

[0164] The "diagnostic template search step" is a step of searching for a diagnostic template stored in the diagnostic template storage unit.

[0165] In addition to the above-described embodiments, this embodiment provides a project diagnosis DB system having a feature of having a function for managing project diagnosis templates.

[0166] <Functional configuration> Fig. 31 is a diagram showing the functional configuration of this embodiment. The project diagnostic DB system (3100) of this embodiment has a project diagnostic template holding unit (3101), a project diagnostic template selection unit (3102), a project diagnostic sheet registration unit (3103), a diagnostic input reception unit (3104), an evaluation rule holding unit (3105), and an appropriate operability evaluation unit (3106) as in the first embodiment, and is characterized in that it further has a project diagnostic template management unit (3107). The following description will be given excluding the functions already described.

[0167] The "project diagnosis template management unit" has a function of managing project diagnosis templates.

[0168] <Hardware configuration> Fig. 32 is a diagram showing the hardware configuration of the project diagnosis DB system in this embodiment. As shown in this diagram, the computer is composed of a chipset (3210), a CPU (3201), a non-volatile memory (3203), a main memory (3204), various buses (3202a to 3202e), a BIOS (3207), various interfaces (3205, 3206, 3208), a real-time clock (3209), and the like, which are configured on a motherboard. These operate in cooperation with an operating system, device drivers, various programs, and the like. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

[0169] The "main memory" reads out programs that perform various processes so that the "CPU" can execute them, and also provides a work area for those programs. In addition, this "main memory" and "HDD" are each assigned multiple addresses, and the programs executed by the "CPU" can exchange data between them and perform processing by identifying and accessing those addresses.

[0170] As shown in the figure, the following are stored in the system: a "project diagnostic template storage program" which stores a plurality of project diagnostic templates each consisting of a diagnostic sentence in a predetermined sentence for checking the proper operability of a project; a "project diagnostic template selection program" which allows a user to select a project diagnostic template for checking the proper operability of a project he or she is managing; a "diagnostic timing acquisition program" which acquires a diagnostic timing, which is the timing for diagnosing a project, in order to associate it with a project diagnostic sheet described later; a "project identification information acquisition program" which acquires project identification information, which is identification information of the project to be diagnosed, in order to associate it with the project diagnostic sheet described later; a "project diagnostic sheet registration program" which associates the selected diagnostic template with the information to be associated and registers it as a project diagnostic sheet; a "diagnostic input reception program" which receives a diagnostic input, which is an input for judging whether the project is being operated properly for each diagnostic item of the project diagnostic sheet; an "evaluation rule storage program" which holds evaluation rules for evaluating the received diagnostic input; and a "proper operability evaluation program" which evaluates the proper operability of the project based on the stored evaluation rules and the input diagnostic input. Based on a series of program execution commands, these programs are loaded into the main memory, and based on an operation start command, these programs are executed. In addition, this computer is configured such that a non-volatile memory, a main memory, a CPU, and an interface (for example, a display, a keyboard, communication, etc.) are connected to a bus line and can communicate with each other. In addition to the first embodiment, the computer is further equipped with a "project diagnosis template management program" for managing project diagnosis templates.

[0171] <Processing flow> Fig. 33 is a diagram showing a process flow when the project diagnostic DB system in this embodiment is used. The process flow of this embodiment is an operation method of the project diagnostic DB system, which is a computer having a project diagnostic template holding step (S3301), a project diagnostic template management step (S3302), a project diagnostic template selection step (S3303), a diagnosis timing acquisition step (S3304), a project identification information acquisition step (S3305), a project diagnostic sheet registration step (S3306), a diagnosis input reception step (S3307), an evaluation rule holding step (S3308), and a proper operability evaluation step (S3309). Among these steps, each step except the project diagnostic template management step is the same as that of the first embodiment.

[0172] The "project diagnostic template management step" is a stage for managing project diagnostic templates. In this management, the user can download the data of the project diagnostic template from the screen, modify it, and upload it. In addition, the user can reinstall or additionally install the project diagnostic template remotely.

[0173] In addition to the above-described embodiments, this embodiment provides a project diagnosis DB system having an automatic diagnosis function.

[0174] The project diagnosis DB system of this embodiment further includes a functional unit that, after evaluating the appropriate operability of the project once, automatically evaluates the appropriate operability of the project based on data input through the schedule management, issue management, risk management, change management, or quality management functions, and outputs the improvement status. <Examples of diagnostic statements in the project diagnostic template>

[0175] Figure 34 shows a diagnostic statement that asks users to answer whether they are using the project plan to achieve consensus or awareness after the start of the project. In Figure 34, in the category "1. Integration" and title "1. Project Plan," the diagnostic statement is written as follows: "Even after the project starts, do you always return to the contents of the project plan and always achieve consensus based on the project plan?"

[0176] Figure 35 shows a diagnostic statement that asks users to answer whether they are using incident management as a management indicator after the test phase. In Figure 35, in the category "1. Integration" and title "5. Incident management," the diagnostic statement is written as follows: "Are tools and formats prepared for centralized management of inquiries (task requests, questions, fault indications, etc.) after the test phase?"

[0177] Fig. 36 shows a diagnostic statement that asks the user to answer whether the master schedule is being used for progress management of the entire project. In Fig. 36, in the category "3. Schedule" and title "1. Master Schedule", the diagnostic statement "Do you use the master schedule to visualize the progress of the entire project and share it with the relevant parties?" is written.

[0178] Fig. 37 shows a diagnostic statement that prompts the user to answer the level of involvement or the degree of influence of members who are working on both regular tasks and the project. In Fig. 37, the diagnostic statement "Is the project execution being hindered due to the project members' dual roles?" is written in the category "6. Project resources" and title "3. Assignment".

[0179] The project diagnostic template may also include a diagnostic statement that prompts the user to respond as to whether information has been shared with the relevant parties, whether consensus has been reached with the relevant parties, or whether consensus has been reached with the relevant parties. Specifically, it may be a diagnostic statement classified under category "1. Integration" and title "1. Project Plan" that reads, "Have the contents of the project plan been explained to the key stakeholders of the project and have their agreement been obtained?"

[0180] The project diagnostic template may also include diagnostic statements that prompt the user to answer questions such as whether the criteria for issues regarding which information should be shared immediately with higher-level organizations are clearly defined, whether quantitative management is in place, or whether the departments and plans for dealing with the issues are clearly defined. Specifically, it may be a diagnostic statement classified under category "1. Integration" and title "2. Issue management" that reads, "Are there clear standards for sharing and communicating important issues to higher levels, such as from the team to the project, and from the project to the steering committee?"

[0181] The project diagnostic template may also include a diagnostic statement that prompts the user to respond as to whether or not the relevant parties have agreed on the determination of the baseline or judgment criteria, or the need to respond to changes. Specifically, it may be a diagnostic statement such as "Are the timing, approver, and approval method for determining the baseline clear?", which is classified under category "1. Integration" and title "3. Change Management."

[0182] The project diagnostic template may also include a diagnostic statement that prompts the user to respond as to whether or not a phase can be started after clarifying what the deliverables are. Specifically, it may be a diagnostic statement classified under category "2. Scope" and title "1. Deliverables" that reads, "Do you create a list of deliverables before the start of the phase and understand the type, number, difficulty, estimated effort, etc. of the deliverables to be created?"

[0183] The project diagnostic template may also include a diagnostic statement that prompts the user to answer whether or not the use of a list to centrally manage requirements has reduced misunderstandings among the parties involved and improved the quality of the upstream process of the project. Specifically, it may be a diagnostic statement such as "Have you prepared tools or formats for centrally managing user requirements?", which is classified under category "2. Scope" and title "2. Requirements."

[0184] The project diagnostic template may also include a diagnostic statement that prompts the user to answer whether the rules for creating a work schedule or the progress rate settings have been clearly defined. Specifically, it may be a diagnostic statement classified under category "3. Schedule" and title "2. WBS" that reads, "Are you leaving the setting of progress rate up to subjectivity, but rather have clear guidelines and standards?"

[0185] The project diagnostic template may also include a diagnostic statement that prompts the user to answer whether or not the consistency between the master schedule and the work schedule, or the consistency between the deliverables and the work schedule, is confirmed. Specifically, it may be a diagnostic statement such as "Is the WBS always consistent with the master schedule?", which is classified under category "3. Schedule" and title "5. Work Plan."

[0186] The project diagnostic template may also include a diagnostic statement that prompts the user to respond as to whether quality assurance is performed by clarifying who will review the deliverables, registering review tasks in a work schedule, or visualizing the progress of the review. Specifically, it may be a diagnostic statement such as "Are the deliverables to be reviewed and the reviewers clarified before the start of a phase?", which is classified under category "5. Quality" and title "1. Quality Assurance."

[0187] The project diagnostic template may also include a diagnostic statement that prompts the user to answer whether the participation schedule of undecided members or the validity of skills and man-hours have been confirmed. Specifically, it may be a diagnostic statement such as "If those who have not yet been assigned are included, are there any definite plans for assignment?", which is classified under "6. Project resources" and title "3. Assignment".

[0188] The project diagnostic template may also include diagnostic statements that prompt the user to answer questions about whether the meeting is being set up with consideration for reporting to higher-level personnel, whether the meeting content is being reviewed depending on the situation, or whether the planned meeting is being run appropriately. Specifically, it may be a diagnostic statement classified under category "7. Communication" and title "1. Meetings" that reads, "Are you taking care to ensure that reports from lower levels to higher levels are made in an orderly manner without any gaps in between?"

[0189] Furthermore, the project diagnostic template may include a diagnostic statement that prompts the user to answer whether an appropriate number of risks are extracted or whether project-specific measures are considered in risk management. Specifically, it may be a diagnostic statement such as "Are you able to extract an appropriate number of risks (approximately 10 to 50)?", which is classified under category "8. Risk" and title "2. Identification and Analysis." [Explanation of symbols]

[0190] CPU: 0201 System bus: 0202 Non-volatile memory: 0203 Main memory: 0204

Claims

1. A project diagnosis DB system for diagnosing whether a project is being properly managed while the project is in progress and providing a database that accumulates the results, comprising: a project diagnostic template storage unit that stores a plurality of project diagnostic templates each having a plurality of diagnostic items each including a diagnostic statement in a predetermined sentence for checking the proper operation of a project; a project diagnostic template selection unit for allowing a user to select a project diagnostic template for checking the proper operation of a project being managed; a project diagnosis sheet registration unit for registering the selected project diagnosis template as a project diagnosis sheet by associating the selected project diagnosis template with information to be associated therewith; a diagnostic input receiving unit that receives a diagnostic input for determining whether the project is being properly operated for each diagnostic item of the project diagnostic sheet; an evaluation rule storage unit that stores evaluation rules for evaluating a received diagnostic input; an appropriate operability evaluation unit that evaluates appropriate operability of the project based on a stored evaluation rule and an input diagnostic input; A project diagnosis DB system having the above.

2. A project diagnosis DB system as described in claim 1, further comprising a project diagnosis sheet comparison unit that compares multiple project diagnosis sheets.

3. 3. The project diagnosis DB system according to claim 1, further comprising a functional unit that, after evaluating the appropriate operability of the project once, automatically evaluates the appropriate operability of the project based on data input through a function of schedule management, issue management, risk management, change management, or quality management, and outputs an improvement status.

4. 4. A project diagnosis DB system as described in claim 1, wherein the project diagnosis template includes at least a diagnostic statement prompting the user to answer whether the project plan is being used to achieve consensus or awareness after the start of the project.

5. 5. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes a diagnostic statement prompting the user to answer at least whether incident management is being utilized as a management indicator after the test phase.

6. 6. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes at least a diagnostic statement prompting the user to answer whether a master schedule is being applied to progress management of the entire project.

7. 7. A project diagnosis DB system as described in claim 1, wherein the project diagnosis template includes at least a diagnostic statement prompting the user to respond to an involvement level or influence degree of a member who is concurrently engaged in both regular work and the project.

8. 8. A project diagnosis DB system as described in any one of claims 1 to 7, wherein the project diagnosis template includes a diagnostic statement prompting the user to respond as to whether information has been shared with stakeholders, whether consensus has been reached with stakeholders, or whether consensus has been reached with stakeholders.

9. 9. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes a diagnostic statement prompting the user to answer at least whether the criteria for issues for which information should be shared immediately with a higher-level organization are clearly defined, whether quantitative management is performed, or whether the department and plan for dealing with the issues are clearly defined.

10. 10. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes a diagnostic statement prompting the user to respond as to whether or not the parties involved have agreed on the establishment of a baseline or a judgment criterion, or the need to respond to a change.

11. 11. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes a diagnostic statement that prompts the user to answer whether or not the user is able to clarify what the deliverable is before starting a phase.

12. 12. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes at least a diagnostic statement prompting the user to respond as to whether or not the quality of the upstream process of the project is improved by reducing misunderstandings among the parties involved through centralized management of requirements using a list.

13. 13. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes a diagnostic statement prompting the user to answer at least whether a work schedule creation rule or a progress rate setting has been clarified.

14. 14. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes a diagnostic statement prompting the user to answer whether or not he / she has confirmed the consistency between a master schedule and a work schedule, or the consistency between a deliverable and a work schedule.

15. 15. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes a diagnostic statement prompting the user to answer at least whether, in quality assurance, the person who will review the deliverables is clarified, a review task is registered in a work schedule, or the progress of the review is visualized.

16. 16. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes a diagnostic statement prompting the user to answer whether or not the user has confirmed at least the planned participation of undecided members or the validity of skills and man-hours.

17. 17. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes at least a diagnostic statement prompting the user to answer whether the user is setting up a meeting with consideration for reporting to higher-level officials, reviewing the content of the meeting depending on the situation, or appropriately managing the planned meeting.

18. 18. The project diagnosis DB system according to claim 1, wherein the project diagnosis template includes a diagnostic statement prompting the user to answer whether or not an appropriate number of risks are extracted or project-specific measures are considered in risk management.

Images