Many initiatives in IT are treated as projects with defined start dates and delivery dates. At the beginning of a typical project, everyone is bursting with enthusiasm, and by the end of it they are only too eager to get out. The deliverables are handed over to someone else, enabling the original team to move on to the next project. I have witnessed a number of business rules projects that follow this pattern and have come to the conclusion that "projectizing" the business rules approach in this way may not always yield the desired results. Projects dealing with business rules can work out well if they are individual components of a coordinated strategy. However, problems seem to arise when business rules projects exist in isolation with no linkages between them.

A common business rules project is to choose a business domain, or subdomain, and then go after all the business rules in it. Capturing and documenting the rules can take a lot of effort, but we now have tools, methodologies, and consultants that can assist in the process. Barring unusual factors, we can be pretty confident that a typical project of this kind will be a success. The results may be immediately useful to the sponsoring organization. Here is a typical list:

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access