Are business rules part of requirements
I was speaking to Barbara von Halle after she returned from an address to requirements people in Connecticut recently, and she told me how surprised she was that the folks at her talk did not see business rules as part of their activities. I wonder whether participants in RQNG believe that business rules are an integral part of requirements gathering...
I wonder...
I would be rather perplexed by the overall sentiment that the business rules are not considered "part of their activities".
I wonder then, what do they use to define the level of detail at which the requirements can be used by the design team to satisfy many of the contextual questions?
Business rules are critical to offering the level of detail the requirements need to support the entire user need, and not just satisfy an open request for functionality in an open context. Solving the business needs will require at best a minimal elicitation of the business as it is applied, thus the rules.
I would be open to hearing how the detail is captured by those who do not feel the business rules are part of the process, but business rules are easy to elicit, and offer a very traceable method across the requirements landscape.