Are business rules a new kind of "requirement" or should they be treated as something else?
This is a question that is handled differently in different organizations, but what is the right answer? Please comment on your experiences with and opinions about the following:
(1) a business rule is new kind of requirement type and should be captured in a requirements tool
(2) a business rule is a design artifact and should be captured during design phases (not requirements and analysis phases)
(3) business rules are their own artifact because they should have a shorter life cycle than other requirements, they should be captured separately from other requirements
(4) business rules are not part of an SDLC at all, but should be captured by business experts in a business-person's tool (not a requirements tool and not a modeling tool)
Groups:
Rules: My experiences and opinions by dwright
My view: a Rule is a type of Requirement by Razvan Radulian
Business Rules are they special? by kmatthews
Business Rules: Times are changing by dwright
Requirement versus Rule by chniva
Business rules need to be checked while doing something. by alidad.hamidi
