JPH06187145A - Software quality evaluation system - Google Patents

Abstract

PURPOSE:To easily evaluate the quality of an entire software even in the case of developing the software under decentralized environments by automatically gathering quality data to a manager side successively. CONSTITUTION:The quality evaluation of the software distributed and developed respectively in plural terminal equipments 2 is executed through a host device 1 connected to the respective terminal equipments 2. First, measurement timing specifying files are transferred from the host device 1 to the respective terminal equipments 2. The respective terminal equipments 2 are provided with a quality condition monitor 20 for grasping quality information relating to respective distributed nodes, a result measured corresponding to the specification of the host device 1 is tentatively kept in the storage part 24 of the respective terminal equipments 2 and a measurement completion flag is raised. At the host device 1, after confirming the flags of the entire relating terminal equipments 2, measured result files tentatively kept in the respective terminal equipments 2 are transferred through a network to the host device 1.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software quality evaluation system for evaluating the quality of software developed by a plurality of people in a distributed environment.

[0002]

2. Description of the Related Art In recent years, software development by a plurality of people in a distributed environment is increasing. In such a development form, when trying to perform quality control during development, the administrator needs to inquire the individual development staff about the quality status and collect data, which is troublesome. However, a large amount of overhead is generated, and in some cases, the development work itself may be affected.

Further, there are few software quality evaluation systems proposed so far for such a distributed environment, and mainly the function of inputting quality control data by a human system and supporting its management. To do.

[0004]

As described above, it is difficult to execute the quality of software that has been developed in a distributed environment in the past, during development.
It has been desired to develop a software quality evaluation device capable of easily performing such quality evaluation.

The present invention has been made in response to such a conventional situation, and a software quality evaluation system capable of easily performing quality evaluation of the entire software even when software development is performed in a distributed environment. Is to provide.

[0006]

That is, the software quality evaluation system of the present invention performs quality evaluation of software distributed and developed by a plurality of terminal devices via a host device connected to each of the terminal devices. A software quality evaluation system that
Each of the terminal devices includes quality status monitor means for individually measuring the quality of the product developed by these terminal devices, and the host device specifies the quality measurement timing to each of the quality status monitor means. , A system control unit that causes these quality condition monitoring units to perform quality measurement at a predetermined quality measurement timing, and collects quality data that is the result of this quality measurement; and the quality data collected by the system control unit is aggregated. A quality data accumulating means for accommodating the quality data collected by the system control means and a quality data accumulating means for accumulating the quality data collected by the system control means and the aggregation results aggregated by the quality data aggregation means; It is characterized by comprising a quality condition presenting means for presenting.

[0007]

In the software quality evaluation system of the present invention having the above-mentioned configuration, even if software development is performed in a distributed environment, the quality data is automatically collected on the manager side one after another, so The overhead required for data collection is reduced. Also, in the past, when a quality check was determined to be necessary, the administrator checked the quality status and collected quality data.Therefore, in many cases, countermeasures were delayed, and the quality evaluation result was effective for software development. There were many cases that were not reflected in. On the other hand, in the software quality evaluation system of the present invention, since the administrator schedules in advance, the quality data at that time is automatically measured and collected, so that the development is performed in a distributed environment. However, it becomes possible for the administrator to easily check the quality status (complexity of software as a whole, ease of understanding, etc.) during development, and take measures early before problems occur. It becomes possible.

In the software quality evaluation apparatus of the present invention, from the viewpoint of software quality evaluation, the deliverables created during the software development such as the designing / creating process are targeted, and their understandability and maintenance are performed. Evaluate mainly from the viewpoint of ease and complexity.

When the product in these intermediate stages is difficult to understand or has a complicated structure, there is a high possibility that a bug will be mixed due to misunderstanding in the subsequent process, lack of understanding, and the like. In addition, it is difficult to deal with problems found in the testing process with deliverables that are difficult to maintain.
Problems such as difficulty in maintenance and modification after release occur, and as a result, the product software has a problem in terms of quality. With the software quality evaluation apparatus of the present invention, it is possible to eliminate quality problems in advance by evaluating the artifacts under development at the stage of creating them.

As the software quality index, the number of bugs related to the product software is emphasized. However, the comprehension, maintainability, complexity, etc. of the product in the course of development handled by the software quality evaluation apparatus of the present invention are considered. The early evaluation leads to improvement of quality such as preventing bugs of the product software itself in advance.

From the viewpoint of software quality, in addition to the comprehension, maintainability, and complexity of the above-mentioned products, reliability represented by the number of bugs in product software,
Alternatively, various viewpoints such as portability have been proposed. It is desirable to measure and evaluate the quality of software in a form that covers all of these points.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 shows the configuration of a software quality evaluation system according to an embodiment of the present invention. In FIG.
Reference numeral 1 is a host device, and 2 is a plurality of (n) terminal devices provided in a distributed manner and connected by the host device network.

The host device 1 includes a quality data totaling unit 11 for totaling quality data, a quality database 12 for storing each quality data, a system control unit 13, and a quality status presenting unit for providing overall quality information. 14 are provided.

The system control section 13 controls the operation of the entire system and has the following roles.

Transfer of a measurement timing designation file to the terminal device 2.

Confirmation of quality measurement status in the terminal device 2.

Sucking up the quality measurement result after the end of the quality measurement in the terminal device 2.

Quality data totaling unit 1 in host device 1
Startup control of 1.

Activation control of the quality status presentation unit after the end of the quality data aggregation in the host device 1.

Storage process control of measurement result data and total data in the quality database in the host device 1.

On the other hand, the terminal device 2 is provided with a quality status monitor 20 for grasping the quality information about each distributed node (individual). The quality status monitor 20 includes a terminal quality measurement unit 21 that measures the quality of the product developed by each person in charge, a terminal quality measurement control unit 22 that controls the operation of the entire quality status monitor 20, and a quality measurement result to the terminal. It is composed of a terminal quality monitor unit 23 that creates a quality status sheet that can be presented on the display of the device 2. The terminal device 2 also includes a measurement timing specification file, which will be described later.
A storage unit 24 that stores a measurement target file, a measurement result file, a measurement status file, and the like is provided.

In the software quality evaluation system of this embodiment having the above-mentioned configuration, the quality of the target product developed by each individual by the terminal device 2 is automatically measured in a distributed environment, but the automatic measurement is performed. As shown in FIG. 2, the target deliverables are a fixed form design document 31 described in accordance with a fixed form (flow chart, TFF, HIPO, etc.) and C language, FORTRAN, PL.
It is a source code 32 by M, ASEMBLA, or the like.

Each individual creates a measurement target file before entering the design / coding process related to one software development project, and in which the target product exists in each node (terminal device 2). To declare As shown in FIG. 3, the target file for measurement indicates in which directory of the device used by the user for actual development the fixed form design document or the source code exists. In the example of FIG.
The source code is in the \ esq \ source directory, and the fixed form design document is in \ esq \ tffdesign.

On the other hand, on the host device 1 side, the administrator creates a measurement timing designation file as shown in FIG. 4 in advance. This measurement timing specification file is
It shows at what timing the quality measurement is executed. In the example shown in FIG. 4, August 1, 1992, August 15
It indicates that the quality measurement is performed on the day, September 18, or the like.

Next, the operation of this software quality evaluation system will be described with reference to the flowchart of FIG.

First, when the system is initialized,
The above measurement timing specification file is the host device 1
Is transferred to each terminal device 2 (101).

This transfer is performed by using a network between the host device 1 and each terminal device 2 in the form of a file copy to the system execution directory of the terminal device 2 side. In order to maintain the execution environment of both the host device 1 and the terminal device 2, the initialization of this system is performed while both the host device 1 and the terminal device 2 are running.

In each terminal device 2, the terminal quality measurement control unit 22 constantly searches the measurement timing designation file transferred as described above (20).
1).

When the date by the calendar function in the terminal device 2 and the date in the measurement timing designating file match, the quality of the product is measured as follows, and the quality is measured at each designated timing. The measurement is repeatedly executed (202).

That is, first, the terminal quality measurement control unit 22 refers to the measurement target file and controls the activation of the terminal quality measurement unit 21 so as to measure the quality of the corresponding product.

For example, in the example of the measurement timing designation file shown in FIG. 4, since it is set to measure the quality of the product of the design process on September 18, 1992, the terminal quality measurement control unit 22 With reference to this measurement timing designation file, the terminal quality measuring unit 21 is activated as of September 18, 1992.

Terminal quality measuring unit 2 instructed to start
1 measures the quality of the target product existing in the designated directory. At this time, the quality is measured by quality metrics for quantitatively evaluating the complexity, maintainability, and comprehension of the fixed form design document and the source code.

At the design document level, the quality metrics include the number of modules, the number of conditions, the number of loops, the number of processes,
At the source code level, the number of modules, the number of conditions, the number of loops, the number of steps, the number of comments, the number of arguments, etc. are also used.

The results measured as described above are temporarily stored in the storage unit 24 of each terminal device 2 as a measurement result file (203).

Further, the terminal quality measurement control unit 22 is
Measurement implementation status (measurement completed, non-implementation, failure, implementation date, etc.)
Is recorded in the measurement status recording file of the storage unit 24. In this case, since the quality measurement has been executed, a measurement completion flag is set in the measurement status file (204).

Further, the terminal quality measurement control unit 22 is
The terminal quality monitor unit 23 is instructed to start, and for each terminal device 2, a quality status sheet in a form in which the measurement result can be confirmed is created. As a result, the measurement result can be confirmed on the screen or the form in each terminal device 2 as necessary (205).

In the host device 1, the system control unit 13 constantly monitors the quality measurement status of each terminal device 2 by checking the measurement completion flag of each terminal device 2 (102).

Then, in comparison with the information of the measurement timing specification file set by the host device 1, the measurement execution status of the measurement status recording file of each terminal device 2 is referred to at the specified timing, and all related terminals are referenced. After confirming that the quality measurement of the device 2 has been completed (10
3) The measurement result file temporarily stored in each terminal device 2 is transferred to the host device 1 via the network (104).

Then, in order to evaluate the quality of the entire target system based on the quality measurement result of each terminal device 2 that has been sucked up, these data are aggregated (105), and the quality value of the entire target system is calculated and evaluated. And system quality evaluation data is created (106). This system quality evaluation data is stored in the quality database unit 12.

Next, the host device 1 presents the quality status at that point in a form that can be understood by the administrator based on the quality data regarding the entire target software (107). The quality situation is presented in the form of a form and a graph, as shown in FIGS. 6 and 7, for example. This output is
Although it is automatically printed out by the printer, it can be displayed on the screen by inputting settings from the operation screen. The following items are presented as the presentation items of the quality status of the entire software.

Quality evaluation value of the entire target system Quality evaluation value of each subsystem (each terminal) configuring the target system Variation tendency of the quality evaluation value of the target system or subsystem based on the measurement results of multiple times is shown in FIG. An example is a system (system name: ***)
It shows the quality evaluation results and quality trends regarding *). In this system, based on the measured quality metric data (for example, the number of modules, the number of conditions, the number of loops, the number of processes, etc.), the quality data totaling unit 11 calculates the complexity, understandability, maintainability, etc. The data is aggregated from the viewpoint, and finally 0 for each of complexity, comprehension, and maintainability.
A score between 10 and 10 is calculated.

For example, when there is almost no problem in complexity, "complexity = 0". On the contrary, when it is considered to be very complicated and problematic, "complexity = 10" is given, and the complexity score is given. Takes a value between 0 and 10. The example shown in FIG. 6 is an evaluation example in the case of “complexity = 4”, “understandability = 6”, and “maintainability = 4”.

Further, the example of the form shown in FIG. 7 shows the variation of the quality evaluation value on the basis of the result of the periodical quality measurement by this system. In this example,
The maintainability of a system (system name: ****) is 9
What was 3 when measured on August 10, 2nd, was changed to August 8th, 1992.
It shows that the measurement on the 20th of the month is 4, the measurement on the 30th of August 1992 drops to 3, and the measurement on the 10th of September 1992 is 5.

The quality measurement result sucked up from each terminal device 2 and the system quality evaluation data totalized by the quality data totaling unit 11 are stored in the quality database unit 12.
Be stored in. The stored quality data is used as a past reference value when providing quality evaluation information. In addition,
In the quality evaluation of this system, the evaluation reference value for each quality metric is set based on the past value and used.

As described above, according to the software quality evaluation system of this embodiment, the following effects can be obtained.

That is, it becomes possible to automatically evaluate the entire quality in software development in a distributed environment. Further, since the quality measurement timing can be set in advance and the quality measurement / evaluation can be executed, the quality confirmation and the quality creation can be easily performed in the middle of development. Further, by automating the work related to the measurement / collection of quality data, the number of man-hours required for quality measurement / evaluation can be reduced, which can contribute to the improvement of software productivity.

Also, by setting the quality measurement timing in a short-term span, it is possible to confirm changes in the quality situation, so it is possible to detect trends such as quality deterioration at an early stage, and it is possible to take effective measures. Become. Further, by using the evaluation reference value based on the quality measurement result regarding the past software development, more accurate evaluation can be performed.

Although this system measures and evaluates quality data in software development in a distributed environment, the quality data totaling unit 11 and the quality status presenting unit 14
It is also possible to collect and present process control data, etc. In other words, in this system, the quality of individual work products is regularly measured at the timing specified by the measurement timing specification file. Can also be used as progress data, which allows quantitative evaluation of work progress.

[0050]

As described above, according to the software quality evaluation system of the present invention, it is possible to easily evaluate the quality of the entire software even when the software is developed in the distributed environment.

[Brief description of drawings]

FIG. 1 is a diagram showing the configuration of a software quality evaluation system according to an embodiment of the present invention.

FIG. 2 is a diagram showing an example of a target product for which quality evaluation is performed.

FIG. 3 is a diagram showing an example of a measurement target file.

FIG. 4 is a diagram showing an example of a measurement timing designation file.

5 is a diagram for explaining the operation of the system of FIG.

FIG. 6 is a diagram showing an example of presentation of quality evaluation results.

FIG. 7 is a diagram showing an example of presentation of evaluation results of quality trends.

[Explanation of symbols]

 1 Host Device 2 Terminal Device 11 Quality Data Aggregation Section 12 Quality Database 13 System Control Section 14 Quality Status Presentation Section 20 Quality Status Monitor 21 Terminal Quality Measurement Section 22 Terminal Quality Measurement Control Section 23 Terminal Quality Monitoring Section 24 Storage Section

Claims (1)

[Claims] 1. A software quality evaluation system for executing quality evaluation of software distributed and developed in a plurality of terminal devices via a host device connected to each of the terminal devices, wherein each of the terminal devices is Is provided with quality status monitor means for individually measuring the quality of the products developed by these terminal devices, and the host device specifies quality measurement timing to each of the quality status monitor means to perform the quality measurement. A system control unit that causes the status monitor unit to perform quality measurement at a predetermined quality measurement timing, and collects quality data that is the result of this quality measurement; and a quality data aggregation that aggregates the quality data collected by the system control unit. Means, quality data collected by the system control means and the quality data collection Software quality evaluation system, characterized by comprising a quality data receiving means for receiving the aggregated total result, the quality condition presenting means for presenting the summary results aggregated by the quality data tallying unit by means.