Process quality is important to business

29/11/2017

 

If the process quality is good, the software can be done as planned.

The word process is a Japanese word for procedures and rules. And the process required for software development is roughly divided into the development process and the management process . What makes you happy if these processes are good, that is, the process quality is good? In fact, the process quality is good, always planned functionality and quality of the software as planned in the schedule of coming finished so, business earlier on to promote the prediction goes you really happy because. In this classification, we will introduce how to judge the quality of the process and how to improve the process quality.

Product quality and process quality

In guaranteeing and evaluating the quality of software, Father Gutara was always aware of whether it was product quality or process quality . There are various aspects to software quality, so it was difficult to understand unless we organized and thought about it based on some rough concept.

The concept of product quality and process quality is not very widely used, but it is a fairly easy-to-use concept for organizing software quality. Simply put, product quality is the quality of the software itself , and process quality is the quality of the process that develops the software .

Therefore, when we usually refer to software quality, we mean product quality. On the other hand, when judging the quality of a product or trying to develop software with a good product quality, the quality of the process is also involved. In the first place, I would like to introduce what Gutara’s father understands what process quality is, so please refer to it. Product quality For, this article refer to .

 

What is process quality?

Process quality is the quality of the process of developing software . Is the process the closest to the work procedure when translated into Japanese ? For example, the process of design review is the work procedure for carrying out design review. Let’s think about process quality a little more based on this design review.

To give an example of the work procedure of design review, a) decide whether to carry out design review, b) prepare the design document to be reviewed, and c) review whether to hold the review in a meeting or in the material circulation. Decide the method of, d) decide the participants of the review, e) carry out the review, f) record the points that were pointed out in the review, g) respond to the points that were pointed out, and so on. I think that each organization has a set procedure for such a design review, and this series of work procedures is the process of design review .

The quality of the design review process What is the, if evaluate any item, the design review process quality of quality do you can determine, again Consider the example. For example, when deciding whether to carry out the review in a), (1) the design review is always carried out when there are corrections or additions in the design document, and (2) when the corrections or additions are 1 page or more. Suppose that there are cases where a design review is carried out, and there are cases where ③ a design review is carried out as necessary. In case of (1), a design review is always carried out when there is an addition or change in the design document, but in case of (3), many design reviews may be omitted due to an unclear judgment that it is necessary. Therefore, as a process for developing high quality software, it can be said that the quality is good in the order of ①> ②> ③.

Simply put, a more effective process for making software with good product quality is a good development process. Unfortunately, there is still no good and easy way to quantify the status of process quality and compare it to absolute values, so process quality can be a relative assessment that that process is better than this one. Mostly. However, there are still good and bad process qualities, so it’s best to adopt a development process of the best possible quality. The CMMI method can be used to quantify the maturity of the development process, but it takes a lot of man-hours , so it is a bit heavy to use in software development audits.

Development and management processes

By the way, when considering the process quality of software, Father Gutara divided it into a development process and a management process . The development process is the process for actually developing software, such as requirement specification design, basic design, detailed design, implementation, and testing . On the other hand, a management process is a process for managing software development work , such as work progress management, review implementation management, and test management .

If the development process is not good, you will not be able to produce software with good product quality. If the management process is not good, software that meets the required functions, performance, and quality will not be available even if the delivery date is set.

Why does the development process judge quality?

There are various development processes from design to testing along with the actual software development work, but how do you judge the quality of each process ? The development process is a work procedure. The work procedure is based on the premise that a person does something. The procedure is for people to collect / think / make decisions as a result. And since it is done by people, there is a risk that mistakes and mistakes will be mixed in.

Therefore, a high- quality development process is a process that has been devised to reduce human error as much as possible. Well, to put it simply, a process that makes the following things as clear as possible is a good quality process.

  • Criteria for deciding whether to carry out the process or skip it are clear
  • The content of preparations for carrying out the process is clear
  • The work procedure of the process is clear
  • The timing and method of reviewing the process is clear
  • The deliverables of the process are clear
  • There is a clear way to judge the quality of the deliverables of the process

If these things are clear, we can reduce human mistakes to a certain degree , so I think that is a good development process.

Why does the management process judge quality?

Management is the work of setting plans and goals, monitoring the status of work to achieve those plans and goals, and implementing countermeasures to keep the plans and goals if they deviate from the plans and goals . It is a thing. Plans and goals to be observed in software development include various plans and goals such as delivery time, development cost, required functions, performance, and quality. In response to these plans and goals, management processes such as process management, requirement management, and test management occur as activities to protect them.

So what do you see and how do you judge whether the management process is good or bad ? Management is the work to minimize the deviation from the plan, so in simple terms, it can be said that a process in which the following things are as clear as possible is a process of good quality.

  • How to make a plan is decided concretely
  • The way to review the plan you made is clear
  • It is clear how to collect performance data corresponding to the plan
  • It is clear how to check the difference between the plan and the actual result
  • It is clear how to deal with deviations from the plan

If these items are clear about the management process, and if the management work is carried out according to the management process, measures to find the deviation from the plan and correct it will be effectively implemented, and as a result, the plan will be implemented. I think that the development project can be completed with little deviation from. That’s what you call a quality management process.

Did you get an overview of process quality?

I have introduced an overview of the process quality that Father Gutara thinks. It may be different from the process quality in general, but I hope you can read it with such a way of thinking. 

If I have a little more time, I will add more concrete content about the process quality that Father Gutara thinks in another article. Once you have written an article, you will see a list of specific articles below, so please refer to it if you are interested.

Posted by グータラ親父