Search

Economies around the globe have evolved into being largely service-oriented economies. Consumers no longer just want a printer or a car, they rather ask for a printing service or a mobility service. In addition, service-oriented organizations increasingly exploit new devices, technologies and infrastructures. Agility is the ability to deal with such changing requirements and environments. Agile ways of working embrace change as a positive force and harness it to the organization's competitive advantage.The approach described in this book focuses on the notion of a service as a piece of functionality that offers value to its customers. Instead of solely looking at agility in the context of system or software development, agility is approached in a broader context. The authors illustrate three kinds of agility that can be found in an agile enterprise: business, process and system agility. These three types of agility reinforce each other and establish the foundation for the agile enterprise. Architecture, patterns, models, and all of the best practices in system development contribute to agile service development and building agile applications.This book addresses two audiences. On the one hand, it aims at agile and architecture practitioners who are looking for more agile ways of working in designing and building business services or who are interested in extending and improving their agile methods by using models and model-based architectures. On the other hand, it addresses students of (enterprise) architecture and software development or service science courses, both in computer science and in business administration.

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.