How to effectively implement software requirement management-4

[This article is "How to effectively implement software demand management"Article 4,(Article 1,Article 2,Article 3,Article 4,Article 5, Article 6, Article 7, Article 8 )]

 

 

 

 

Stage 2: Demand Analysis and Design (how to do it)

 

Now that the requirement has been obtained, that is to say, the customer has already told us what to do or some of the features we have come up with to do. Now, we are truly in the demand management stage.

 

The first step is the demand analysis stage. The so-called demand analysis simply analyzes the obtained requirements to see if they are what the customer thinks and whether our products can do it. Sometimes a requirement is the customer's sentence, but it cannot be solved in one sentence. Therefore, you may need to confirm with the customer to understand their true intentions. (The following figure shows a typical requirement analysis error. I mentioned it when I was in college. I borrowed it when I happened to see it again)

 

 

For a requirement, it is not a simple function operation. It may be a performance requirement or a security and confidentiality requirement, there may even be user interface requirements, cost consumption requirements, and reliability requirements. Therefore, in the demand analysis stage, it is not to say that you can fully clarify this requirement by talking a few words with the customer, and even if you have figured out this requirement, it is impossible to think clearly at once.

 

Therefore, in order to solve this problem, various demand analysis methods are also generated accordingly. If you have studied software engineering in college, you may remember methods such as structured analysis methods, data flowcharts, data dictionaries, and decision tables, maybe you had to carry back the exam in a hurry, and now you should have forgotten it. Even if you carefully read it and understood it, I believe that you do not really understand what is actually used in your work.

 

However, if you want to work on demand analysis, I can tell you that this knowledge is still useful and needs to be used for demand analysis, of course, most of the time you should not directly use these theories, but they always indirectly use tools that reflect their ideas. (For example, UML modeling)

 

Today we are talking about demand management. So I will not talk about how to do this technical activity of requirement analysis. As I mentioned earlier, this article cannot be taught, I want to really teach me a book, huh, huh. Therefore, I will focus on how to manage the entire process, including the demand analysis stage, as well as the subsequent demand design and requirements.

 

When modeling is mentioned above, someone may ask why modeling is required and what are the advantages of modeling. Well, I didn't want to answer this question, but someone is always asking.

 

On the one hand, we are developing software or hardware, but it is impossible for you to immediately show the customer what this product is like after you get the requirement. Therefore, it is necessary to make a model so that the customer can see what it looks like, is it in line with their requirements? This is simple modeling. For hardware, you can show the scaled version to the customer. for software, you can take the software architecture into consideration, the functions, data streams, program streams, and so on can be listed for customers to see;

 

On the other hand, in actual development, there may be a lot of places that cannot be actually verified. We need to simulate verification through modeling, such as atomic bomb explosion, it is impossible for us to bomb an atomic bomb every day to verify whether it meets the design. Instead, it is verified through simulation. The input data is the same as the physical data of the real atomic bomb, then, combined with the actual physical and chemical logic, a tool is used to simulate the explosion.

 

The requirement analysis and modeling tools that our company often uses areFreemindBased on the Mind Map principle, it is quite easy to use. The reason we used it before was the requirement management tool.
TechexcelOfDevspecIt comes with this tool. It is easy to use and can be used. In fact, it has been used before.VisioIt's also good, but white cat and Black Cat, it's good to catch a mouse, as long as it fits. (The following is freemind, which is very powerful)

 

 

 

Stage 3: Demand Review (whether or not it can be done well or not)

 

This stage is put in the third stage. In fact, I want to cooperate with this article. The review of actual requirements appears in many stages of the entire demand process. For example, you need to review the requirements after obtaining them, I think this requirement is necessary. After you have analyzed the demand, you should also review it to see the feasibility and time and cost. After you design the demand, you still need to review it, check whether the design is reasonable ..., therefore, the review process starts from the beginning to the end of the review and needs. Only after review can you ensure that your products are on a healthy path.

 

Stage 4: demand implementation (start/let people do it)

 

In fact, this stage is not strictly in the demand process, but in the development stage. However, because it is always to let the Development implement the demand, it is more or less related, so I also put it in, however, this stage may be rarely mentioned later.

 

 

(To be continued)