"Software requirement mode" Reading Note II

Once you understand what a requirement is and what a demand pattern is, you should learn how to use and write demand patterns. We are not only to understand the meaning of the demand pattern, but also to learn under what circumstances to use the demand model. There are two scenarios for using demand mode during the definition of the system: 1. When defining a requirement, see if there is a pattern that can guide how to define this requirement. 2. When considering whether the system needs are complete, browse through the whole set of patterns covered by the topic-see if there are omissions, or if you need to add something. 3. When reviewing requirements specifications, patterns can help examine the quality of requirements, determine which topics are not defined, and understand the meaning and connotation of specific requirements. 4. When assessing the size of the system and the amount of work required to develop it, usage patterns can have a more accurate sense of the complexity of the implementation, based on demand. 5. When the need is fulfilled, the pattern allows you to understand the intent of the demand more profoundly. 6. When testing requirements, the method used to recommend testing this requirement. The demand model is not able to meet all the needs, the use of patterns just as much as possible to do better.

How to write patterns is what we pay more attention to and learn from. First, we should learn to discover the potential demand pattern, and the search pattern in the completed requirements is the first step in capturing the demand pattern. There are two ways to find a goal: systematization-systematically investigating a field, checking out most of the goals, and opportunistic-capturing any target that is stumbled upon. The book also describes how to create a new area, which is the beginning of writing a demand pattern. The so-called is the beginning of everything difficult, this is the same reason. The beginning of everything is always the hardest, but also the most important. A good beginning is half the success.

To write a pattern: 1. Whether it is of sufficient value; 2. Build the skeleton of the model; 3. The "Applicability" section of the authoring model; 4. Collection of demand instances; 5. Check the requirement example; 6. Describe the information that the requirement may contain; 7. Writing the requirements template; 8. Writing the remaining "discussions" and "content" 9. Develop a list of potential additional requirements instances; 10. Identify candidate themes for additional requirements; 11. Preparation of the "Additional requirements" section; 12. Preparation of the "Development Considerations" section; 13. Write the "Test Considerations" section; 14. Is it worthwhile? 15. Review mode. Although the steps to write a demand pattern are there, we still have to depend on the situation in the actual project, not scripted, nor mechanically copied. Each stage needs to be put into earnest thinking.

The book introduces 37 requirements patterns. is divided into 8 areas. When writing requirements specifications, it is useful to have a list of all the requirements patterns that are being defined for such a system, which is more convenient to find. Not all models can be applied to all systems, so it is worthwhile to build a list of patterns related only to your own system.

"Software requirement mode" Reading Note II