JP2001265580A - Review supporting system and review supporting method used for it - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a review supporting method capable of supporting from the designing/preparing stages to post processing of a review efficiently and precisely by preventing the omission of a check item. SOLUTION: At a step S1, information characteristic to the project is inputted to a database on the side of a client computer, and a similar project is retrieved from the database housing information on a past project on the side of a server computer based on this, is decided and registered in a database on the side of the client computer. At the step S2, the check item is decided by each stage from a database on the side of a server computer and registered in the database on the side of the client computer. Individual check items are decided at a step S3, the review is carried out in accordance with the check items at a step S4 and a problem point is extracted at a step S5. At a step S6, a dealing method is decided by referring to correcting and dealing examples.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a review support system and a review support method used therewith, and more particularly, to a review support method implemented to improve design quality at each step of software product development.

[0002]

2. Description of the Related Art Conventionally, software product development processes are roughly divided into product planning, basic design, functional design, detailed design, coding, unit evaluation, combination / functional evaluation, comprehensive / system evaluation, shipping, etc. The review process is implemented at the boundaries of these processes, and collects and checks necessary information and knowledge on the process design output, its design method and design procedure, and improves the design quality. It has been done.

[0003] In such a review process, a review check sheet that summarizes review items is created before a review is performed, so that the next process can be performed accurately and efficiently without omission of checks. It manages the implementation and the problems / treatments respectively.

[0004]

In the above-described conventional review process, information on reviews, check sheets, and the like are mostly managed on paper for each project, and the check items are common to all software product projects. Check items to be checked, project-type check items, and project-specific check items are not distinguished, so these tasks can be performed efficiently when examining the contents of check items and setting the number of check items Not only that, but also information on past projects and information on previous processes is difficult to use / diverte, so there is a high possibility of causing omission of check items.

In the above-mentioned review process, information such as review results is managed for each project.
As a result of the review, the determination of the correction / treatment method for the extracted problem does not use the past information, so that the treatment cannot be performed efficiently.

Accordingly, an object of the present invention is to solve the above-mentioned problems, prevent omission of check items, and efficiently and accurately support from a review design / preparation stage to post-processing of problems. It is an object of the present invention to provide a review support system and a review support method used therefor.

[0007]

SUMMARY OF THE INVENTION A review support system according to the present invention is a review support system for improving the design quality of a project for developing a software system / product at each step of the project. A review support system that provides support, a server computer that manages all information on development projects in the past and in development, and a plurality of client computers that manage only information on development projects under development,
A first database provided in the server computer and storing / managing information of the past development projects in project units; and a checklist provided in the server computer and used in the review process. A second database for storing / managing check items that can be used in common regardless of the above, and similar to the development project provided in each of the plurality of client computers and retrieved from the first database upon completion of a development plan. And a fourth database provided in each of the plurality of client computers and storing unique information of the development project input when the development plan is completed.

A review support method according to the present invention is a review support method for supporting a review process implemented to improve the design quality of a project for developing a software system / product at each step of the project. A server computer that manages all information on development projects in the past and in the past and a plurality of client computers that manage only information on development projects under development by connecting each other with a communication line; A first database that configures a server system and stores / manages information of the past development projects in project units, and check items that can be commonly used regardless of the project in a checklist used in the review process To a second database to store / manage A third database provided on the server computer for storing information of a project similar to the development project retrieved from the first database when the development plan is completed, and unique information of the development project input when the development plan is completed And a fourth database for storing the client database is provided for each of the plurality of client computers.

That is, the review support system of the present invention determines the check items necessary for reviewing the design output to be performed at the break of the software product development process, creates a checklist, and performs the review in accordance therewith. This is a review support system that determines a method of correcting the extracted problem with reference to past cases and takes action.

In order to solve the above-mentioned problems, the review support system according to the present invention, in the above configuration, has a project name, a development purpose, an outline of development items and functions, a system / product type, a development scale, and an operation of the project. environment,
Means for inputting the unique information of the project including the development man-hour into the database of the client computer;
A means to search and extract similar projects from past projects registered in the database of the server computer based on the input information, and a check common to all software products for each process based on the input information A means for searching and deciding from the database of the server computer check items to be considered for each type based on items, system and product features, a means for extracting check items related to system and product type from information on similar projects, A unique check item for checking the consistency of output with respect to input, etc. in each process unit, integrating all check items determined so far and inputting them to the database of the client computer; Use a checklist A means for inputting the results of the review into the database of the client computer, a means for searching for the problems identified as a result of the review from information on similar projects to help determine corrective / corrective measures, and a means for solving the problems, etc. Means for inputting information into the database of the client computer and registering the information in the database of the server computer.

The review support system of the present invention has a client / server system including a plurality of client computers each having the above-described means and a database, and a server computer.

[0012] With the above configuration, information on project reviews is collectively managed for each process in each project, and information is shared to prevent omission of check items, and from the review design / preparation stage. It is possible to efficiently and accurately support up to post-processing such as a problem.

[0013]

Next, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a client / server system according to one embodiment of the present invention. In FIG. 1, a client / server system according to an embodiment of the present invention is operated in an organization, and manages all information on development projects in the past and past, and information on development projects under development. A plurality of client computers 2-1 to 2-n that manage only the client computers are connected by a LAN line 100. Plural client computers 2-1
.About.2-n are prepared for each project so as to always be accessible from some project groups.

FIG. 2 is a block diagram showing the configuration of the server computer 1 of FIG. 2, the server computer 1 includes a server computer main body 11, a keyboard 12, a display 13, a project information database 14, and a checklist information database 15.

The project information database 14 stores and manages information on development projects performed in the organization in the past in units of projects, and stores information on past projects in the master project information table 1 for each project.
4a.

Checklist information database 1
5 is related to the project in the checklist used in the review performed in each development process divided according to the standard project life cycle model generally applied in the organization, for example, ROYCE's waterfall model. Check items that can be used in common are stored / managed, and their information is stored as a master checklist information table 15a.

FIG. 3 is a diagram showing a configuration example of the master project information table 14a of FIG. In FIG.
The master project information table 14a is provided for each of the projects A, B, C,... For example, in the case of an A project in an organization that develops software using a life cycle model of a waterfall model, A project specific information 41, A project basic design process checklist 42, A project function design process checklist 43, A project detailed design process checklist 44, A project coding process checklist 45, A project test process checklist 46, It is composed of Although not shown, the master project information table 14a for the projects B, C,... Has the same configuration as described above.

FIG. 4 shows the A project specific information 41 of FIG.
FIG. 3 is a diagram showing an example of the configuration. In FIG. 4, the A project specific information 41 indicates information in the case of the A project. The development purpose (the purpose of the development, the background of the development, the effect at the time of providing the function) 411, the development item and the function summary (function and performance) , Reliability and security, scalability) 412, system / product type [classify based on system and product features (select from type list)] 413, and development scale [number of screens to be developed, number of forms, Number of source lines, etc. (shown on a whole scale)] 414, operating environment (environment of systems and products, operation and maintenance form, technical characteristics) 415, and development man-hours [man hours, man days, man years, etc. required for development] (Indicated by the whole scale)] 416. still,
Although not shown, the project-specific information of the projects B, C,... Has the same configuration as described above.

Here, the development purpose 411 indicates the purpose of the development, the background of the development, and the effect of the provided function. The development items and function outline 412 are for functions and performance, reliability and safety,
2 illustrates the concept of extensibility. System / Product Type 41
Reference numeral 3 denotes a system / product type that is determined by selecting a type of a system or a product to be developed such as a database or communication control from a type list registered in advance by an organization using the review support system according to the present embodiment. .

The development scale 414 indicates the amount of development design such as the number of design documents, the number of screens to be designed, and the number of lines of a coded source file. The operating environment 415 indicates hardware and software environments that guarantee the operation of the product to be developed, typical modes of operation and maintenance, and technical characteristics. The development man-hour 416 indicates the time required for the entire development process.

FIG. 5 is a diagram showing a configuration example of the A project basic design process check list 42 in FIG. In FIG. 5, the project A basic design process checklist 42
Is composed of information of a basic design process common check item 421, a basic design process type common check item 422, and a basic design process A project individual check item 423, and each check item 424 is [check contents].
(Contents to be checked), [Pass / Fail Judgment Result] {Pass / Fail Judgment Result (Pass, Fail, Conditional Pass, Not Applicable)}, [Problem] (Problem content, cause category,
Creation process, importance, problem occurrence location),
Disposition method] {Contents of modification and disposition method, modification location (page number, specification item number, function name, line number)}, [Correction check] (Modification completion date, modification completion Rev) I have. Although not shown, the project basic design process checklists for projects B, C,... Have the same configuration as described above.

Here, basic design process common check item 4
Reference numeral 21 is a collection of common check items in the basic design process of the waterfall model regardless of the system or product to be developed. The basic design process type common check item 422 is a collection of check items depending on the type of system or product to be developed, such as a database and communication control. The basic design process A project individual check item 423 is a collection of check items specific to the A project.

FIG. 6 is a diagram showing a configuration example of the A project function design process check list 43 in FIG. In FIG. 6, an A project function design process checklist 43
Is composed of information of a common check item 431 for function design process, a common check item 432 for function design process type, and a check item 433 for individual project of function design process A, and each check item 434 is [check contents].
(Contents to be checked), [Pass / Fail Judgment Result] {Pass / Fail Judgment Result (Pass, Fail, Conditional Pass, Not Applicable)}, [Problem] (Problem content, cause category,
Creation process, importance, problem occurrence location),
Disposition method] {Contents of modification and disposition method, modification location (page number, specification item number, function name, line number)}, [Correction check] (Modification completion date, modification completion Rev) I have. Although not shown, the project function design process checklists for projects B, C,... Have the same configuration as described above.

FIG. 7 is a diagram showing an example of the configuration of the project A detailed design process checklist 44 in FIG. In FIG. 7, the A project detailed design process checklist 44
The detailed design process common check item 441, the detailed design process type common check item 442, and the detailed design process A project individual check item 443 are each configured, and each check item 444 is [check content].
(Contents to be checked), [Pass / Fail Judgment Result] {Pass / Fail Judgment Result (Pass, Fail, Conditional Pass, Not Applicable)}, [Problem] (Problem content, cause category,
Creation process, importance, problem occurrence location),
Disposition method] {Contents of modification and disposition method, modification location (page number, specification item number, function name, line number)}, [Correction check] (Modification completion date, modification completion Rev) I have. Although not shown, the project detailed design process checklists of the projects B, C,... Have the same configuration as described above.

FIG. 8 is a diagram showing an example of the configuration of the A project coding process check list 45 in FIG. FIG.
In the A project coding process checklist 45, coding process common check items 451
And coding process type common check item 452,
Coding process A project individual check item 45
3 and each check item 45
4 is [check contents] (contents to be checked), [pass / fail judgment result] {pass / fail judgment result (pass, fail, conditional pass, not applicable)}, [problem] (problem content,
Cause category, creation process, importance, location of problem occurrence), [Correction / action method] ｛Contents of correction / action method,
Correction (page number, specification item number, function name, line number)｝, [correction confirmation] (correction completion date, correction completion R)
ev). Although not shown, the project coding process check list for the projects B, C,... Has the same configuration as described above.

FIG. 9 is a diagram showing a configuration example of the A project test process check list 46 in FIG. In FIG. 9, the A project test process check list 46 is composed of test process common check items 461, test process type common check items 462, and test process A project individual check items 463, and each check item 464. Are [Check Contents] (Contents to be checked), [Pass / Fail Judgment Result] {Pass / Fail Judgment Result (Pass, Fail, Conditional Pass, Not Applicable)}, [Problem] (Problem content, cause classification, creation Process,
Importance, problem occurrence location), [Correction / action method] ｛
It consists of the fields of the content of the correction / treatment method, correction location (page number, specification item number, function name, line number), and [correction confirmation] (correction completion date, correction completion Rev). Although not shown, the project test process checklists of the projects B, C,... Have the same configuration as described above.

FIG. 10 is a diagram showing the configuration of the master checklist information table 15a of FIG. In FIG. 10, the master checklist information table 15a is a basic design process master checklist 51, a functional design process master checklist 52, and a detail if the organization develops software in the life cycle of the waterfall model. Design process master checklist 53,
It comprises a coding process master checklist 54 and a test process master checklist 55.

FIG. 11 is a diagram showing the configuration of the basic design process master checklist 51 of FIG. In FIG. 11, since the basic design process master checklist 51 mainly develops a system / product of a database system and a communication control system in the case of the above organization, a basic design process common master check item 511 and a basic Design process database (DB) system type common master check item 512 and basic design process communication control system type common master check item 513
And each check item 514
Is [Check Contents] (contents to be checked), [Pass / Fail Judgment Result] {Pass / Fail Judgment Result (Pass, Fail, Conditional Pass, Not Applicable)}, [Problem] (Content of problem,
Cause category, creation process, importance, location of problem occurrence), [Correction / action method] ｛Contents of correction / action method,
Correction (page number, specification item number, function name, line number)｝, [correction confirmation] (correction completion date, correction completion R)
ev). In addition, [Pass / Fail judgment result], [Problem], [Correction / treatment method], [Correction confirmation]
Are written after the check.

FIG. 12 is a diagram showing the structure of the functional design process master checklist 52 of FIG. In FIG. 12, the function design process master / checklist 52 includes a function design process common master check item 521 and a function design process database (DB) system type common master check item 5.
22 and the function design process communication control system type common master check item 523, and each check item 524 is [check content] (content to be checked), [pass / fail judgment result] ｛pass / fail judgment result (pass) , Fail, Conditional Pass, Not Applicable)｝, [Problem] (Content of problem, cause classification, build process, importance,
Problem location), [Correction / Troubleshooting] {Contents of correction / treatment, corrections (page number, specification item number, function name, line number)}, [Correction check] (Correction completion date,
The column is composed of each column of “Correction completion Rev). still,
[Pass / Fail Judgment Result], [Problem], [Correction / Treatment Method],
Each column of [Correction Confirmation] is written after the check.

FIG. 13 is a diagram showing the configuration of the detailed design process master checklist 53 of FIG. In FIG. 13, the detailed design process master checklist 53 includes a detailed design process common master check item 531 and a detailed design process database (DB) system type common master check item 5.
32, and a detailed design process communication control system type common master check item 533, and each check item 534 is [check contents] (contents to be checked), [pass / fail judgment result] ｛pass / fail judgment result (pass) , Fail, Conditional Pass, Not Applicable)｝, [Problem] (Content of problem, cause classification, build process, importance,
Problem location), [Correction / Troubleshooting] {Contents of correction / treatment, corrections (page number, specification item number, function name, line number)}, [Correction check] (Correction completion date,
The column is composed of each column of “Correction completion Rev). still,
[Pass / Fail Judgment Result], [Problem], [Correction / Treatment Method],
Each column of [Correction Confirmation] is written after the check.

FIG. 14 is a diagram showing the structure of the coding process master checklist 54 of FIG. In FIG. 14, the coding process master checklist 54
Is a coding process common master check item 541,
Coding process database (DB) system type common master check item 542 and coding process communication control system type common master check item 543 are configured, and each check item 544 is [check contents].
(Contents to be checked), [Pass / Fail Judgment Result] {Pass / Fail Judgment Result (Pass, Fail, Conditional Pass, Not Applicable)}, [Problem] (Problem content, cause category,
Creation process, importance, problem occurrence location),
Disposition method] {Contents of modification and disposition method, modification location (page number, specification item number, function name, line number)}, [Correction check] (Modification completion date, modification completion Rev) I have. Note that the columns of [Pass / Fail Judgment Result], [Problem], [Correction / Treatment Method], and [Correction Confirmation] are written after the check.

FIG. 15 is a diagram showing the structure of the test process master checklist 55 of FIG. In FIG. 15, a test process master check list 55 includes a test process common master check item 551 and a test process database (DB) system type common master check item 552.
And test process communication control system type common master check items 553, and each check item 554 includes [check contents] (contents to be checked),
[Pass / Fail Judgment Result] {Pass / Fail Judgment Result (Pass, Fail, Conditional Pass, Not Applicable)}, [Problem] (Problem Content, Cause Classification, Creation Process, Importance, Problem Occurrence Location), [ Correction / Treatment Method] ｛Contents of correction / treatment method, correction points (page number, specification item number, function name
Line number) @, [Correction confirmation] (Modification completion date, Modification completion Rev). Note that the columns of [Pass / Fail Judgment Result], [Problem], [Correction / Treatment Method], and [Correction Confirmation] are written after the check.

FIG. 16 is a block diagram showing the configuration of the client computers 2-1 to 2-n in FIG. FIG.
6, the client computers 2-1 to 2-
n is composed of a client computer main body 21, a keyboard 22, a display 23, a printer 24, a similar project information database 25, and the project information database 26.

Similarity / Project Information Database 25
At the time when the development plan is completed, the project members (preferably the project leader or a similar one), based on the project information registered in the project information table 26a of the project information database 26, Server computer 1
A similar project is searched from the project information database 14 of the other project, and is determined as a similar project of the relevant project. For example, if the A project, the D project, and the E project are determined as similar projects, the similar / project information It is stored as a table 25a. In addition,
The project information database 26 stores the project information table 26a.

FIG. 17 is a diagram showing the configuration of the similar / project information table 25a of FIG. 17, a similarity / project information table 25a is provided for each of the projects A, D, E,...
1 and A project basic design process checklist 42
A project function design process checklist 43
A project detailed design process checklist 44
And A project coding process checklist 4
5 and an A project test process checklist 46.

Although not shown, project D,
The similar / project information table 25a of E,... Has the same configuration as described above, and the respective configuration contents of the similar / project information table 25a are the same as those in FIGS.

FIG. 18 is a diagram showing the configuration of the project information table 26a of FIG. In FIG. 18, the project information table 26a includes the project specific information 71, the project basic design process checklist 72, the project function design process checklist 73, and the project detailed design process checklist 74. , The project coding process checklist 75, and the project test process checklist 76.

This project information table 26
The information stored in a is input by a project member (preferably a project leader or equivalent) when the development plan is completed.

FIG. 19 is a diagram showing the structure of the project-specific information 71 of FIG. In FIG. 19, the project-specific information 71 includes the development purpose (the purpose of development, the background of the development, the effect at the time of providing the function) 711 and the development item and the function summary (the function and the performance, the reliability and the safety,
(Extensibility) 712, system / product type [classify from system or product features (select from type list)] 713, development scale [number of screens to be developed, number of forms, number of source lines, etc. (total scale) 714] and operating environment (system and product environment, operation and maintenance form,
(Technical characteristics) 715 and development man-hours [man hours, man days, man years, etc. required for development (shown on a whole scale)] 716.

FIG. 20 is a diagram showing the structure of the relevant project basic design process check list 72 of FIG. In FIG. 20, the project basic design process checklist 72 is a basic design process common check item 721.
, A basic design process type common check item 722, and a basic design process pertinent / project individual check item 723. Each check item 724 includes [check content] (contents to be checked), [pass / fail judgment result]. ] {Pass / Fail Judgment Results (Pass, Fail, Conditional Pass, Not Applicable)}, [Issues]
Cause category, creation process, importance, location of problem occurrence), [Correction / action method] ｛Contents of correction / action method,
Correction (page number, specification item number, function name, line number)｝, [correction confirmation] (correction completion date, correction completion R)
ev).

FIG. 21 is a diagram showing the structure of the project function design process check list 73 of FIG. In FIG. 21, the project function design process check list 73 is a function design process common check item 731.
, A functional design process type common check item 732, and a function design process pertinent / project individual check item 733, and each check item 734 includes [check contents] (contents to be checked), [pass / fail judgment results]. ] {Pass / Fail Judgment Results (Pass, Fail, Conditional Pass, Not Applicable)}, [Issues]
Cause category, creation process, importance, location of problem occurrence), [Correction / action method] ｛Contents of correction / action method,
Correction (page number, specification item number, function name, line number)｝, [correction confirmation] (correction completion date, correction completion R)
ev).

FIG. 22 is a diagram showing the structure of the relevant project detailed design process checklist 74 of FIG. In FIG. 22, the project detailed design process checklist 74 is a detailed design process common check item 741.
And detailed design process type common check items 742 and detailed design process pertinent / project individual check items 743. Each check item 744 includes [check contents] (contents to be checked), [pass / fail judgment results]. ] {Pass / Fail Judgment Results (Pass, Fail, Conditional Pass, Not Applicable)}, [Issues]
Cause category, creation process, importance, location of problem occurrence), [Correction / action method] ｛Contents of correction / action method,
Correction (page number, specification item number, function name, line number)｝, [correction confirmation] (correction completion date, correction completion R)
ev).

FIG. 23 is a diagram showing the structure of the project coding process check list 75 of FIG. In FIG. 23, the project coding process check list 75 is composed of information of a coding process common check item 751, a coding process type common check item 752, and a coding process pertinent project check item 753. Item 754 includes [check contents] (contents to be checked), [pass / fail judgment result] 結果 pass / fail judgment result (pass,
(Fail, conditional pass, not applicable) 該当, [problem]
(Details of problem, cause category, creation process, importance, location of problem occurrence), [Correction / action method] ｛Contents of correction / action method, correction location (page number, specification item number, function name, line) No.)｝, [Correction Confirmation] (Modification Completion Date, Modification Completion Rev).

FIG. 24 is a diagram showing the structure of the project test process checklist 76 shown in FIG. FIG.
In 4, the project test process check list 76 is composed of test process common check items 761, test process type common check items 762, and test process pertinent / project individual check items 763. Reference numeral 764 denotes [check contents] (contents to be checked), [pass / fail judgment results] {pass / fail judgment results (pass, fail, conditional pass, not applicable)], [problem] (problem content, cause classification,
Creation process, importance, problem occurrence location),
Disposition method] {Contents of modification and disposition method, modification location (page number, specification item number, function name, line number)}, [Correction check] (Modification completion date, modification completion Rev) I have.

FIG. 25 is a flowchart showing the operation of the review support system according to one embodiment of the present invention.
6 is a flowchart showing a similar project determination operation of the review support system according to one embodiment of the present invention;
FIG. 27 is a flowchart showing an operation of determining a check item in each step of the review support system according to one embodiment of the present invention.

FIG. 28 is a flowchart showing an operation of selecting / determining check items in each step of the review support system according to one embodiment of the present invention, and FIG. 29 is a review of the review support system according to one embodiment of the present invention. FIG. 30 is a flowchart showing an operation of determining a correction / treatment method for a problem extracted by the above-described method. FIG. 30 is a flowchart showing an operation of updating each database (the project information database 14 and the checklist information database 15) of the server computer 1 in FIG. It is. These FIGS. 1-3
The operation of the review support system according to one embodiment of the present invention will be described with reference to FIG.

First, when the project development plan is completed, the pertinent / project specific information 71 is input to the pertinent / project information table 26a of the pertinent / project information database 26 on the client computer 2-1 to 2-n side. Based on this, similar projects are searched and determined from the project information database 14 which stores information on past projects on the server computer 1 side, and the client computers 2-1 to 2-1.
It registers in the similar / project information database 25 on the 2-n side (step S1 in FIG. 25).

Subsequently, common check items and type common check items are determined for each process from the check list information database 15 of the server computer 1, and after reviewing all check items (contents), the client computer 2- The information is registered in the relevant project information database 26 on the 1-2-n side. Here, when the common check item and the type common check item are corrected / added as a result of the review, the check list information database 15 of the server computer 1 is updated (FIG. 25).
Step S2).

At the time when the work of each process is started, individual check items for checking the consistency of the output with respect to the input are determined with reference to the information on the similarity / project determined at the time of completion of the development plan (step S in FIG. 25).
3).

After that, when the review planned for each process is performed, a review is performed according to the check items (step S4 in FIG. 25), and problems are extracted (step S5 in FIG. 25). Referring to a correction / treatment example for a similar problem from the similar / project information, a method of treating the extracted problem is determined, and a measure is taken (FIG. 25).
Step S6).

After all the problems have been solved, the operation shifts to the operation of the next process (step S7 in FIG. 25).
The information in the project information database 26 is stored in the server
It is registered in the project information database 14 of the computer 1 (step S8 in FIG. 25).

Next, the individual operations described above will be described in detail. As shown in FIG. 26, when the project development plan is completed, the member of the project (preferably a project leader or a person similar thereto), as shown in FIG. n of the relevant / project information tables 26a of the relevant / project information database 26
The development purpose 711, development items and function outline 712, system / system
Product type 713, development scale 714, operating environment 715,
Each information of the development man-hour 716 is input (step S11 in FIG. 26).

However, the system / product type 713 in each of the above information is determined by selecting from a list of types previously registered and registered by the organization using the review support system according to the present embodiment.

The entered project-specific information 71
The project information database 14 of the server computer 1 is searched using each piece of information as a key, and similar / projects (2 or 3 if there is more than one) are determined by the operator.
Project) (step S12 in FIG. 26).

Further, similar project information stored in the master project information table 14a of the project information database 14 of the server computer 1 and determined is transmitted to the client computers 2-1 to 2-n.
For example, if the determined similar projects are the A project, the D project, and the E project, they are registered in the similarity / project information table 25a of the similarity / project information database 25 as shown in FIG. 17 (step S13 in FIG. 26). .

As shown in FIG. 27, the processing in step S2 is a basic design process master checklist 51 constituting the master checklist information table 15a of the checklist information database 15 of the server computer 1 first. From among the checklists of the functional design process master checklist 52, the detailed design process master checklist 53, the coding process master checklist 54, and the test process master checklist 55, a system developed for each process is provided. A common master check item that collects common check items irrespective of products, and a type common master check item that collects check items dependent on the type of system or product to be developed, such as a database or communication control, are determined.

The type common master check item is determined by selecting an item suitable for the project. Assuming that the project is a database project, in the case of the basic design process, the basic design process common master check item 511 and the basic design process database type common master check item 512, which are the components of the basic design process master checklist 51. In the case of the function design process, the function design process master check item 521 and the function design process database system type common master check item 5 which are constituent elements of the function design process master checklist 52
22, in the case of the detailed design process, a detailed design process common master check item 531 and a detailed design process database type common master check item 532 which are components of the detailed design process master checklist 53, and in the case of the coding process, coding Coding process common master check item 541 and coding process database system type common master check item 542 which are components of process master checklist 54, and test process which is a component of test process master checklist 55 in the case of test process Common master check item 551 and test process database type common master check item 55
2 are selected and determined (step S2 in FIG. 27).
1).

The determined check items are the relevant project information table 26 of the relevant project information database 26 of the client computers 2-1 to 2-n.
The relevant project basic design process checklist 72, the relevant project function design process checklist 73, the relevant project detailed design process checklist 74, the relevant project coding process checklist 75, the relevant project test process It is registered as a common check item and a type common check item in the check list for each process in the check list 76.

For example, in the case of the basic design process, the basic design process common master check item 511 and the basic design process database system type common master check item 512
The basic design process common check item 721 and the basic design process type common check item 722 of the project basic design process check list 72 are registered.

In the case of the function design process, the function design process common master check item 521 and the function design process database system type common master check item 522 are replaced with the function design process common check item 731 of the relevant project function design process check list 73. And registered in the function design process type common check item 732.

In the case of the detailed design process, the detailed design process common master check item 531 and the detailed design process database system type common master check item 532 are replaced with the detailed design process common check item 741 of the relevant project detailed design process check list 74. And the detailed design process type common check item 742.

In the case of the coding process, the coding process common master check item 541 and the coding process database system type common master check item 542
Is registered in the coding process common check item 751 and the coding process type common check item 752 of the project coding process check list 75.

In the case of the test process, the test process common master check item 551 and the test process database system type common master check item 552 are included in the project test process check list 76. The test process common check item 761 and the test process type common check Item 7
62 (step S22 in FIG. 27).

Thereafter, the client computer 2
-1 to 2-n similar project information database 2
A review is performed within the group with respect to the check items common to the processes and the types common to each process registered in the check list for each process in the similar / project information table 25a of FIG. 5 (step S23 in FIG. 27).

As a result of the above-described review, if there is a correction / addition to the check item (step S24 in FIG. 27), the check item is reexamined to correct the content or add an excess or deficiency (step S25 in FIG. 27).

When the check items are corrected or added after the review is completed, the master check list information table 15a of the check list information database 15 of the server computer 1 and the client computer 2-
The relevant project information database 26 for 1-2-n
With respect to the common checklist and type common checklist for each process in the relevant / project information table 26a, the corresponding check items are modified / added and updated.

As described above, the master list of the checklist information database 15 of the server computer 1 is timely obtained.
By updating the checklist information table 15a,
The know-how is quickly and horizontally developed to another project that is simultaneously progressing in the organization (step S26 in FIG. 27).

In the process of step S3, as shown in FIG. 28, at the time of work in each step, a check item is determined from an input in order to check consistency between an input and an output.

At this time, the client computer 2-
Similarity / Project Information Database 25 of 1-2-n
The individual check items related to the similarity / project registered in the similarity / project information table 25a, for example, when the A project is determined as the similarity / project, it is a component of the A project basic design process checklist 42 in the basic design process. The basic design process A project individual check item 423, the function design process A project individual check item 433 which is a component of the A project function design process checklist 43 in the function design process, and the A project detailed design process checklist 44 in the detailed design process Detailed design process A which is a component
The project individual check item 443, the coding process A project individual check item 453 which is a component of the A project coding process checklist 45 in the coding process, and the test process A project individual component of the A project test process checklist 46 which is a component in the test process Since each of the check items 463 is registered in the similarity / project information table 25a of the similarity / project information database 25 of the client computers 2-1 to 2-n, they are referred to (step S31 in FIG. 28).

The determined check items are stored in the relevant project information table 26 of the relevant project information database 26 of the client computers 2-1 to 2-n.
A is registered as a project-specific check item in the check list for each process in a.

In the basic design process, it is a component of the basic design process pertinent / project individual check item 723 which is a component of the relevant / project basic design process checklist 72, and in the function design process, it is a component of the relevant / project function design process checklist 73. The function design process pertinent / project individual check item 733, the detailed design process pertinent / project individual check item 743 which is a component of the relevant project pertinent project detailed design process checklist 74, 75, a coding step pertaining to the coding process pertaining to the project individual check item 753; Respectively registers the check item 763 (FIG. 28 step S32).

Client computers 2-1 to 2-
n of the project information database 26
In the check list for each process in the project information table 26a, all the individual check items registered so far are reviewed in the group (step S33 in FIG. 28).

As a result of the review, if there is a correction / addition to the check item (step S34 in FIG. 28), the check item is reexamined, and the content is corrected and excess / short is added (FIG. 2).
8 steps S35).

When the check items are corrected or added after the review is completed, the client computers 2-1 to 2-1
2-n, the individual check items for each process in the relevant project information table 26a of the relevant project information database 26 are corrected.
It is updated by adding (step S36 in FIG. 28).

As shown in FIG. 29, each of the above-described steps S4, S5, S6, and S7 is performed by first executing the relevant project in the relevant project information database 26 of the client computers 2-1 to 2-n. Checklist of each process registered in the information table 26a, the relevant project basic design process checklist 72, the relevant project function design process checklist 73, the relevant project detailed design process checklist 74, the relevant project coding process checklist 75 Then, based on the project test process checklist 76, a review planned for each process is performed (step S41 in FIG. 29).

After the review, the reviewer registers the review result (including the pass / fail judgment) in the project information table 26a of the project information database 26 of the client computers 2-1 to 2-n.

For example, in the basic design process, with respect to all the check items of the basic design process pertaining to the project, which are components of the pertinent / project basic design process check list 72, [pass / fail judgment result] of each check item 724, Register [Problem].

In the function design process, regarding all the check items of the function design process pertaining to the project, which are constituent elements of the relevant project function design process checklist 73, [pass / fail judgment result] of each check item 734,
Register [Problem].

In the detailed design process, regarding all check items of the detailed design process pertaining to the project, which are constituent elements of the pertinent project detailed design process checklist 74, [pass / fail judgment result] of each check item 744,
Register [Problem].

In the coding process, regarding all the check items of the coding process pertaining to the project, which are constituent elements of the relevant project coding process checklist 75, the “pass / fail judgment result” and “problem” of each check item 754 are described. register.

In the test process, with respect to all check items of the test process pertaining to the project, which are components of the relevant project test process checklist 76, the items [pass / fail judgment result] and [problem] of each check item 764 are registered. (Step S42 in FIG. 29).

If there is a problem (step S43 in FIG. 29), the client computers 2-1 to 2-n
The similarity / project information table 25a of the similarity / project information database 25 is searched for a similar problem in the past (step S44 in FIG. 29).

Then, with reference to the searched correction / correction method of the problem, a method of processing the problem that occurred in the project concerned is examined, and as a result of reviewing the contents, a processing method is determined, and the processing is performed. (Step S4 in FIG. 29)
5).

If there is no problem here (step S46 in FIG. 29), finally, the client computer 2
-1 to 2-n of the relevant project information database 2
6, the correction / treatment method and correction confirmation are registered in the relevant / project information table 26a.

For example, in the basic design process, regarding all check items of the basic design process pertaining to the project, which are components of the relevant project basic design process checklist 72, [correction / treatment method], [ Correction] is registered.

In the functional design process, regarding all check items of the function design process pertaining to the project, which are constituent elements of the relevant project / functional design process check list 73, [correction / treatment method] and [correction confirmation] of each check item 734 ] Is registered.

In the detailed design process, regarding all check items of the detailed design process pertinent / project which are components of the pertinent / project detailed design process checklist 74, [correction / treatment method] and [correction confirmation] of each check item 744 are described. ] Is registered.

In the coding process, [correction / treatment method] and [correction confirmation] of each check item 754 are registered for all check items of the coding process pertaining to the project, which are components of the relevant project coding process checklist 75. I do.

In the test process, “correction / treatment method” and “correction confirmation” of each check item 764 are registered for all the check items of the relevant test process / project which are constituent elements of the relevant / project test process checklist 76. I do. Thereafter, the process proceeds to the next process (step S47 in FIG. 29).

As shown in FIG. 30, at the stage of completion of all the processes at the end of the development, all the problems extracted up to that point are analyzed as shown in FIG. A new check item is determined for (step S51 in FIG. 30).

Here, when correction / addition occurs in each of the common check item, the type common check item, and the individual check item of each process, the master check list information of the check list information database 15 of the server computer 1 is used. The checklist of each process of the project information table 26a of the project information database 26 of the table 15a and the project information database 26 of the client computers 2-1 to 2-n is corrected and added (step S52 in FIG. 30).

Finally, the client computer 2-
The relevant project information database 26 for 1-2-n
Of the project information table 26a of
It is registered in the project information database 14 of the server computer 1 and used for the next development project (step S53 in FIG. 30).

As described above, a plurality of client computers 2-1 constituting the client / server system
By providing a database for storing project review information in each of .about.2-n and the server computer 1, project review information can be centrally managed.

Further, since past information and data are also stored in these databases, checklists should be considered.
At the time of creation, it is possible to improve the efficiency of work by diverting data and prevent omission of check items, and when correcting problems after review, promptly refer to past correction cases, so that correction / The effect is that the decision can be made quickly.

Therefore, according to the present embodiment, it is possible to prevent omission of check items, and it is possible to efficiently and accurately support from a review design / preparation stage to post-processing such as problems. It should be noted that the present invention is not limited to the description of the above-described embodiment, and it is apparent that the present embodiment can be appropriately modified within the scope of the technical idea of the present invention.

[0096]

As described above, according to the present invention, it is possible to support a review process performed to improve the design quality of a project at each step of a project for developing a software system / product. In a review support system to be implemented, a server computer that manages all information on development projects in the past and past and a plurality of client computers that manage only information on development projects under development are connected to each other by a communication line A first database that configures a server system and stores and manages information on past development projects on a project basis and stores check items that can be commonly used regardless of the project in a checklist used in the review process / Server database with the second database to be managed Provided on the over data, the first at the time of the development plan completed
A third database for storing information on a project similar to a development project retrieved from the database of the first and a fourth database for storing information specific to the development project input upon completion of the development plan; , It is possible to prevent omission of check items, and review design /
There is an effect that the process from the preparation stage to post-processing such as a problem can be efficiently and accurately supported.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a client / server system according to an embodiment of the present invention.

FIG. 2 is a block diagram showing a configuration of a server computer of FIG.

FIG. 3 is a diagram showing a configuration example of a master project information table of FIG. 2;

FIG. 4 is a diagram showing a configuration example of A project specific information of FIG. 3;

FIG. 5 is a diagram showing a configuration example of an A project basic design process check list in FIG. 3;

FIG. 6 is a diagram showing a configuration example of an A project function design process check list in FIG. 3;

FIG. 7 is a diagram showing a configuration example of an A project detailed design process check list in FIG. 3;

8 is a diagram illustrating a configuration example of an A project coding process check list in FIG. 3;

FIG. 9 is a diagram showing a configuration example of an A project test process check list in FIG. 3;

FIG. 10 is a diagram showing a configuration of a master checklist information table in FIG. 2;

11 is a diagram showing a configuration of a basic design process master check list in FIG.

FIG. 12 is a diagram showing a configuration of a functional design process master check list of FIG. 10;

FIG. 13 is a diagram showing a configuration of a detailed design process master checklist of FIG. 10;

FIG. 14 is a diagram showing a configuration of a coding process master checklist of FIG. 10;

FIG. 15 is a diagram showing a configuration of a test process master check list in FIG. 10;

FIG. 16 is a block diagram showing a configuration of a client computer of FIG.

FIG. 17 is a diagram showing a configuration of a similarity / project information table of FIG. 16;

18 is a diagram showing the configuration of the project information table of FIG.

19 is a diagram showing a configuration of the project-specific information in FIG. 18;

20 is a diagram showing a configuration of a relevant / project basic design process check list in FIG. 18.

FIG. 21 is a diagram showing a configuration of a project function design process check list in FIG. 18;

FIG. 22 is a diagram showing a configuration of a relevant / project detailed design process check list in FIG. 18.

FIG. 23 is a diagram showing a configuration of the project coding process check list of FIG. 18.

FIG. 24 is a diagram showing a configuration of the project test process check list in FIG. 18.

FIG. 25 is a flowchart showing the operation of the review support system according to one embodiment of the present invention.

FIG. 26 is a flowchart showing a similar project determining operation of the review support system according to an embodiment of the present invention.

FIG. 27 is a flowchart showing an operation of determining a check item in each step of the review support system according to an embodiment of the present invention.

FIG. 28 is a flowchart showing a check item selection / determination operation of each step of the review support system according to an embodiment of the present invention.

FIG. 29 is a flowchart showing an operation of determining a method of correcting / treating a problem extracted by a review of the review support system according to an embodiment of the present invention.

FIG. 30 is a flowchart showing an update operation of each database of the server computer of FIG. 2;

[Explanation of symbols]

1 server computer 2-1 to 2-n client computer 11 server computer body 12, 22 keyboard 13, 23 display 14 project information database 14a master project information table 15 checklist information database 15a master checklist information table 21 Client computer body 24 Printer 25 Similar / project information database 25a Similar / project information table 26 Related / project information database 26a Related / project information table 41 A project specific information 42 A project basic design process check list 43 A project function design process check List 44 A Project Detailed Design Process Checklist 45 A Project Project coding process checklist 46 A project test process checklist 51 basic design process master checklist 52 functional design process master checklist 53 detailed design process master checklist 54 coding process master checklist 55 test design process master checklist 71 Applicable / project specific information 72 Applicable / project basic design process checklist 73 Applicable / project function design process checklist 74 Applicable / project detailed design process checklist 75 Applicable / project coding process checklist 76 Applicable / project test process checklist 100 LAN line

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B042 HH11 5B049 AA06 BB07 CC23 DD01 DD05 EE05 FF09 GG02 GG04 GG07 5B075 ND03 ND04 ND23 NK04 NK06 PP12 PP22 PP28 PQ05 PQ32 UU40 5B076 EC09 EC10

Claims (9)

[Claims] 1. A review support system for supporting a review process performed to improve the design quality of a project at each step of a project for developing a software system / product, which is under development. A server computer that manages all the information of the past development projects, and a plurality of client computers that manage only the information of the development project under development; and A first database for storing / managing on a project basis; and a second database for storing / managing check items provided in the server computer and commonly usable regardless of the project in a check list used in the review process. Two databases and the plurality of A third database provided on each client computer and storing information on a project similar to the development project retrieved from the first database upon completion of the development plan; and provided on each of the plurality of client computers; A review support system comprising: a fourth database for storing information specific to the development project input when the development plan is completed. 2. The review support system according to claim 1, wherein said server computer and said plurality of client computers are mutually connected by a communication line to constitute a client / server system. 3. The unique information of the development project includes at least a project name, a development purpose, a development item and a function outline, a system / product type, a development scale, an operation environment, and a development man-hour. Or the review support system according to claim 2. 4. Using the first to fourth databases, determine check items necessary for reviewing design outputs to be implemented at the breaks in the software product development process, create a checklist, and create a checklist accordingly. The review support system according to any one of claims 1 to 3, wherein a review is performed, a method of correcting the extracted problem is determined with reference to past cases, and a measure is taken. 5. A means for inputting the unique information of the development project into the fourth database, and a similar project is identified from the information of the past development project registered in the first database based on the unique information. Means for searching; means for searching for the commonly usable check item from the second database based on the unique information; means for determining a check item relating to a system or a product type from information of the searched similar project. Means for determining a unique check item for checking the consistency of the output with respect to the input in each process unit of the development project, integrating all the check items determined so far, and inputting them to the third database. , Using the checklist of the integrated check items Means for inputting into the fourth database, means for searching for the problem extracted from the result of the review from the information on the similar project, and determining a correction / treatment method for the development project, and solving the problem The review support system according to any one of claims 1 to 4, further comprising: means for registering final information in the fourth database and the first database. 6. A review support method for supporting a review process performed to improve the design quality of a project at each step of a project for developing a software system / product, which is under development. And a client / server system comprising a server computer that manages all information of past development projects and a plurality of client computers that manage only information of development projects under development via a communication line. A first database for storing / managing the past development project information on a project basis and a second database for storing / managing check items that can be commonly used regardless of the project in a check list used in the review process; 2 is provided on the server computer, A third database for storing information on a project similar to the development project retrieved from the first database when the development plan is completed, and a fourth database for storing development project specific information input upon completion of the development plan
A review support method, wherein the database is provided in each of the plurality of client computers. 7. The development project specific information comprises at least a project name, a development purpose, a development item and a function outline, a system / product type, a development scale, an operation environment, and a development man-hour. The described review support method. 8. Using the first to fourth databases, determine check items required for review of design output to be executed at the break of the software product development process, create a checklist, and create a checklist accordingly. 8. The review support method according to claim 6, wherein a review is performed, a method of correcting the extracted problem is determined with reference to past cases, and a measure is taken. 9. A step of inputting the unique information of the development project into the fourth database; and a step of inputting a similar project from the information of the past development project registered in the first database based on the unique information. A step of searching; a step of searching for the commonly usable check item from the second database based on the unique information; and a step of determining a check item relating to a system or a product type from information of the searched similar project. Determining a unique check item for checking the consistency of the output with respect to the input in each process unit of the development project, and integrating all the check items determined so far and inputting them to the third database; , Use that integrated checklist checklist Inputting the result of the review into the fourth database; searching for a problem extracted from the result of the review from the information on the similar project to determine a correction / treatment method for the development project; 9. The review support method according to claim 6, further comprising a step of registering final information having solved points in the fourth database and the first database.