Agile Business Rule Development: Process, Architecture, and JRules Examples - Tapa blanda

Acerca del autor

Jérôme Boyer is senior solutions architect at IBM labs services, delivering business solution using business rule technology and BPM. He has been working  with ILOG/IBM BRMS since 2001 and is a member of a service engineering team dedicated to managing best practices and defining solution implementation methodologies. He is the leading developer of the first open source methodology for business rules: Agile Business Rule Development. He holds an MSc in computer science from Nice University, France.

Hafedh Mili has been training, mentoring, and consulting as a rule analyst, developer, architect, and PM for ILOG/IBM on business rules since 1996. He is also a professor of computer science at the University of Quebec in Montreal. He has written extensively about knowledge-based systems, object-oriented design, and software reuse. He holds an engineering diploma from the Ecole Centrale de Paris (1984) and a PhD in computer science from the George Washington University (1988).>

De la contraportada

Business rules are everywhere. Every enterprise process, task, activity, or function is governed by rules. However, some of these rules are implicit and thus poorly enforced, others are written but not enforced, and still others are perhaps poorly written and obscurely enforced. The business rule approach looks for ways to elicit, communicate, and manage business rules in a way that all stakeholders can understand, and to enforcethem within the IT infrastructure in a way that supports their traceability and facilitates their maintenance.

Boyer and Mili will help you to adopt the business rules approach effectively. While most business rule development methodologies put a heavy emphasis on up-front business modeling and analysis, agile business rule development (ABRD) as introduced in this book is incremental, iterative, and test-driven. Rather than spending weeks discovering and analyzing rules for a complete business function, ABRD puts the emphasis on producing executable, tested rule sets early in the project without jeopardizing the quality, longevity, and maintainability of the end result. The authors presentation covers all four aspects required for a successful application of the business rules approach: (1) foundations, to understand what business rules are (and are not) and what they can do for you; (2) methodology, to understand how to apply the business rules approach; (3) architecture, to understand how rule automation impacts your application; (4) implementation, to actually deliver the technical solution within the context of a particular business rule management system (BRMS). Throughout the book, the authors use an insurance case study that deals with claim processing.

Boyer and Mili cater to different audiences: Project managers will find a pragmatic, proven methodology for delivering and maintaining business rule applications. Business analysts and rule authors will benefit from guidelines and best practices for rule discovery and analysis. Application architects and software developers will appreciate an exploration of the design space for business rule applications, proven architectural and design patterns, and coding guidelines for using JRules.