Fishbone Diagram of Software Requirement Analysis

What I learned today is something nice to use for demand analysis. The notes are as follows:

I. Defining the characteristics of a problem is always affected by some factors. We work hard to find these factors and combine them with the feature values, A graph that is organized in a hierarchical and well-organized manner based on their correlations and marks important factors is called a feature map. Because its shape is like a fish bone, it is also called a fish bone diagram (hereinafter referred to as a fish bone diagram). It is an essential analysis method through phenomena.

Brain Storming-BS: A Meeting method that uses brainstorming to give full play to the wisdom of a group and identify all the causes or components of a problem from different perspectives. BS has four principles: no criticism, free run, more benefits, and free-riding.

[Edit this section]

Ii. Three types of fish bone chart

A. Sort out the problematic Fishbone Diagram (there is no reason relationship between each element and the feature value, but a structural relationship)

B. Cause-type fish bone chart (the fish head is on the right, and the feature value is usually "why ......" To write)

C. Countermeasure fish bone chart (the fish head is left and the feature value is usually "How to Improve/improve ......" To write)

(Because of the most common causes of fish bone map, this promotion focuses on the cause of fish bone map)

[Edit this section]

3. Create a fish bone chart

The creation of a fishbone chart consists of two steps: analyzing the cause/structure of the problem and drawing a fishbone chart.

1. analyze the cause/structure of the problem

A. Select the layer method (such as the human-machine material method ring) for the problem );

B. Find out all possible causes (factors) for each layer by brainstorming ).

C. classify and sort out the identified elements and clarify their subordination.

D. Analyze and select important factors.

E. Check the description of each element to make sure that the syntax is concise and the meaning is clear.

Analysis points:

A. When determining the major cause (major cause), on-site operations generally start from the "man-machine material method ring", and management problems generally start from the "personnel-time features" layer, which should be determined based on specific circumstances;

B. You must use neutral words to describe the cause (not to describe the quality or bad), and use value to judge the cause of medium or small problems (such... Poor );

C. When brainstorming, you should find out as many and all possible causes as possible, not just what you have full control of or what you are executing. The reasons for human beings should be analyzed from the perspective of action rather than the ideological attitude;

D. There must be a direct relationship between the feature value and the cause-the problem relationship, and the countermeasures should be taken directly in response to the analysis;

E. If one reason can be attributed to two or more factors at the same time, take the most relevant factors as the standard. (if necessary, consider "Three-byism": view the current things at the scene, by comparing the relative conditions, we can find out the most relevant reason for classification .)

F. when selecting an important reason, no more than 7 items should be selected, and the root cause should be identified;

Drawing Process

A. Fill in the fish head (according to the reason for poor description) and draw the primary bone

B. Draw big bones and fill in big reasons

C. Draw middle and small bones and fill in Small and Medium Quality Forum for Six Sigma

D. mark important factors with special symbols

Key points: the angle between the big bone and the primary bone should be 60 degrees while the middle bone is parallel to the primary bone.