3.4 Requirement Pattern Groups


3.4 Requirement Pattern Groups

When several requirement patterns have features in common, we can create a requirement pattern group and use it as a place to describe all of their common aspects, to save repeating them in each individual pattern. A requirement pattern group is not a requirement pattern: you can't create requirements of this type. But the definition of a group can contain any of the following sections that appear in the definition of a requirement pattern: "Extra Requirements," "Consideration for Development," and "Considerations for Testing." The rule is to include whichever of these sections in which something valuable can be said and to omit the rest. Whenever one of these sections is present in the group, it's worth including a note in the equivalent section in each pattern based on the group as a reminder to refer to it.

The difference between a domain and a requirement pattern group is that the patterns in a domain share a common theme, whereas those in a group have detailed features in common. The patterns in a group don't need to belong to the same domain. (For those familiar with Java programming, the relationship between requirement patterns and domains is akin to that between classes and packages: every class belongs to a package just as each pattern belongs to a domain. Also, a requirement pattern can build upon a pattern belonging to a different domain, just as a Java class can extend a class in a different package.)




Microsoft Press - Software Requirement Patterns
Software Requirement Patterns (Best Practices)
ISBN: 0735623988
EAN: 2147483647
Year: 2007
Pages: 110

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net