BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Business Rules Engines Content on InfoQ

Articles

RSS Feed
  • Lightweight External Business Rules

    Complex enterprise applications usually come with varying business logic. Such conditions and subsequent system actions, known as rules, are ever varying and demand involvement of domain specific knowledge more than technology and programming. The rules must reside outside the codebase, authored by people with core domain expertise with minimal tech knowledge.

  • A collaborative approach for real-world BPM

    Bernd Ruec​ker explores how to achieve a better Business-IT alignment when developing BPM solutions. He describes a methodology which uses BPMN-based process model as center for collaboration where users can discuss and link requirements, business rules or other artifacts, visualize development status, specify business driven test scenarios and much more.

  • Book Excerpt and Review: OSWorkflow

    OSWorkflow by Diego Adrian Naya Lazo discusses the open-source OSWorkflow, a Java-based workflow engine. The book's publisher, Packt Publishing, also provided InfoQ with an excerpt from Chapter 4 of the book, entitled Using OSWorkflow in your Application. InfoQ spoke with Naya Lazo about the areas that the book covers and about OSWorkflow in general.

  • Case study: A new approach to integrating architectures post-merger at Lawson

    The merger of Lawson and Intentia in 2006 left developers with an important problem to solve - the integration and presentation of legacy applications and business services that are constructed in Java, .NET, and other technologies. This case study looks under the hood at the new architecture at Lawson and how they got there.

  • Implementation of business rules and business processes in SOA

    Boris Lublinsky and Didier Le Tien discuss how business process engines and business rule engines differ, where their respective strengths are and when to use what in an SOA context. They discuss commonalities and differences between business rules and business processes and present some guidelines on positioning business rules in SOA implementation and appropriate usage of each technology.

  • Agile Business Rules

    James Taylor looks at the challenge that arises when the new requirements are not really requirements at all, but new or changed business rules. Aren't business rules the same as requirements? Taylor says: no, not really; and looks at how to make an agile development processes work just as well for business rules as they do for other kinds of requirements.

  • Real-World Rule Engines

    For many developers, rule engines are buzzwords, or black boxes on an architectural diagram: something to be feared or admired from afar, but not understood. In this article, Geoffrey Wiseman shares his practical experience with rule engines and with Drools in particular to support in-market solutions for financial services.

BT