Software Requirements Model 02

It is necessary to define requirements of the same type in a consistent manner. For example, for a report requirement, we can use the
report requirement mode to define, of course, additional requirements can be added in this process. A requirement pattern needs to describe when to use the pattern,
how to write a requirement based on the pattern, and how to implement and test that requirement. In each requirement pattern, the following elements are included: 1. Basic details, the declaration of the pattern, its own domain,
2. The applicability of the pattern, under what circumstances can the pattern be used? Under what circumstances can it not be used? 3. Discuss, how to write this type of requirement? What needs to be considered for this type of requirement
? 4. Content? What does this type of requirement have to describe? What additional things might be described? 5. The starting point for writing this requirement? 6. Example, one or more typical requirements using this pattern
7. Additional requirements. What requirements does this requirement typically follow? 8. Development Considerations. Prompts the software designer how to implement this type of requirement. 9. Testing Considerations: What must be kept in mind when deciding how to test this type of requirement?