A major goal of the business rules movement is to capture business rules in ways that express the business logic of the rules, rather than describing the mechanics used to execute them. As Chris Date has put it, business rules should be about "what, not how." A significant problem with this goal is that many IT professionals - perhaps the majority - tend to have mind-sets that think in terms of the "how" of implementing business rules. This seems to be based primarily on the experiences of individuals as programmers, and a view that creating source code by hand is the only way to get things done in practice. Source code is, of course, procedural. That is to say it is a sequence of instructions that a computer will execute, e.g., "first do A, then B, then C and if D is true then do E, otherwise do F."
All Information Management articles are archived after 7 days. REGISTER NOW for unlimited access to all recently archived articles, as well as thousands of searchable stories. Registered Members also gain access to:
- Full access to information-management.com including all searchable archived content
- Exclusive E-Newsletters delivering the latest headlines to your inbox
- Access to White Papers, Web Seminars, and Blog Discussions
- Discounts to upcoming conferences & events
- Uninterrupted access to all sponsored content, and MORE!