Michael Weiss

Hafedh Mili

Morad Benyoucef

This book constitutes the refereed proceedings of the 6th International Conference on E-Technologies, MCETECH 2015, held in Montréal, Canada, in May 2015. The 18 papers presented in this volume were carefully reviewed and selected from 42 submissions. They have been organized in topical sections on process adaptation; legal issues; social computing; eHealth; and eBusiness, eEducation and eLogistics.

6th International Conference, MCETECH 2015, Montréal, QC, Canada, May 12-15, 2015, Proceedings

E-Technologies

Stéphane Ducasse

Sihem Ben Sassi

This book constitutes the proceedings of the 19th International Conference on Software and Systems Reuse, ICSR 2020, held in Hammamet, Tunesia in December 2020. Due to COVID-19 pandemic the Conference was held virtually. The 16 full papers and 2 short papers included in this book were carefully reviewed and selected from 60 submissions. The papers were organized in topical sections named: modelling, reuse in practice, reengineering, recommendation, and empirical analysis.

19th International Conference on Software and Systems Reuse, ICSR 2020, Hammamet, Tunisia, December 2–4, 2020, Proceedings

Reuse in Emerging Software Engineering Practices

Jérôme Boyer

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 enforce them 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.

Process, Architecture, and JRules Examples

Agile Business Rule Development

Hafedh Mili

Books

Your next favorite book is out there