Agile IT Architecture

I will publish this month the Agile Business Rule Development plug-in for the Eclipse Process Framework. This plugin presents a pragmatic approach to the development of a Business Rule Application using Rule Engine and Business Rules Management System (BRMS) technology such as ILOG JRules , Rules for .Net or any other Rule Engine and BRMS on the market. Business rules are an expression of business policy in a form that is both comprehensible to business users and executable by a rule engine. From a business perspective, a business rule is a precise statement that describes, constrains, or controls some aspect of the business. Let’s illustrate this with a simple example coming from the lending industry. The following business policy can be established to limit the purchase of loans by a bank or lender: Only prime loans are eligible for purchase This policy may be split into two rules, one defining what a prime loan is and the second taking the decision on purchasing i

This blog is about discussing Agile IT Architecture and sharing best practices - comments, how tos with IT architects, project managers, developers. Working from personal experience, experience of people working with me, and articles on the web I hope this blog will be used by people to get good information on this interesting subject. I'm author of a methodology used internally at my company, ILOG , but I'm in the final process to publish and share a piece of this methodology as an open source project part of Eclipse Process Framework. ( EPF ) I'm also in relationship with a nice initiative around sustainable architecture which promotes restructuring of IT architecture by focusing on reference data, process and business rules and the methodology to do so. There is a real need to share knowledge and experience on those subjects. Agile IT architecture is about designing IT architecture that supports the quick changes in the business goals. Business users wants to run the