<p>E-business provides important opportunities of trade for businesses, and the supporting business system must handle this environment efficiently. One current trend in business systems is to move business logic, such as business processes and business rules, out from the application logic and into separate support systems. The reason to make this separation is to increase the agility of the business, to make the system able to change more rapidly when the business situation changes.</p><p>This report focus on business rules enforced in business rule engines. Specific interest is on how such rule engines meet the requirements of the e-business domain. The report presents an overview of business rule engines. Five general categories of characteristics are proposed. The proposed characteristics are then used in a comparison of three business rule engines.</p>

The main goal of this thesis is to develop a new help-desk ticket management system for the Etnetera Company. The chosen platform is Java. A secondary objective is to test a suitability of using a rule engine system for this type of applications. The first part of the thesis contains a theoretical introduction to business rule systems, which is followed by a part evaluating and presenting in a detail three such systems. The chosen system used for the implementation is JBoss Drools. A project environment, description of the current situation and reasons for the development of the new system are listed in the next part. The following chapter deals with the analysis of the requirements and the next-to-last chapter describes the design and implementation of the new system. The last chapter contains documentation. The main benefit of the work is a newly developed system that optimally supports the process of processing a request and other related processes at the Etnetera Company, thereby reducing the amount of unnecessary administrative work. Another benefit is a practical demonstration and deployment of business rule system for developing similar applications.

Après avoir défini l’Architecture d’Entreprise, en tant que discipline, son contexte de transformation, puis ses principaux cadres et méthodes (la méthode Praxeme surtout), cette thèse décrit les besoins en modélisation, notamment pour représenter les processus métier et les prises de décision opérationnelles.Après un état de l’art des langages et notations existants pour la modélisation des processus métier, des prises de décisions et des règles métier, tant dans le monde académique quand dans le monde industriel, les langages et notations standards sont présentés en détail. Cette thèse démontre les limites des langages et notations pour modéliser les processus métier à représenter les prises de décisions opérationnelles.Puis, elle évalue le nouveau langage DMN (Decision Model and Notation), proposée par l’OMG (Object Management Group) et sujet de recherche principal de cette thèse, afin de vérifier qu’elle constitue une solution alternative mieux adaptée, en appliquant le principe de séparation des préoccupations.Le modèle DMN obtenu est composé d’un diagramme et de tables de décision. Les expérimentations avec un démonstrateur, mises en oeuvre dans cette thèse, montrent qu’il est possible d’automatiser les prises de décisions opérationnelles ainsi modélisées. Plusieurs solutions techniques seront détaillées puis comparées, à la lumière de la MDA (Model Driven Architecture).Enfin, plusieurs perspectives intéressantes de l’utilisation de DMN sont développées dans la conclusion. / After defining the Enterprise Architecture, as a discipline, its context of transformation, and then its main frameworks and methods (the Praxeme method above all), this thesis describes the modeling needs, notably to represent the business processes and the operational decisions.After a state of the art of existing languages and notations for the modeling of business processes, decision-making and business rules, both in the academic world and in the industrial world, the standard languages and notations are presented in detail.This thesis demonstrates the limitations of the languages for modeling business processes to represent operational decision-making.It then evaluates the new DMN language (Decision Model and Notation), proposed by the OMG (Object Management Group) and the main research subject of this thesis, in order to verify that it is a better adapted alternative solution, applying the separation of concerns principle.The resulting DMN model is composed of a diagram and decision tables. The experiments with a demonstrator, implemented in this thesis, show that it is possible to automate the operational decision-making and modeled. Several technical solutions will be detailed and compared in light of the MDA (Model Driven Architecture).Finally, several interesting perspectives of the DMN use are developed into the conclusion.

The purpose of this project was to create a requirement repository using a methodology, which is being developed in the department of Information Systems of Kaunas University of Technology. The implementation would raise the methodology to the higher level enabling its use in practice. Using the implementation one could either prove or disprove the main idea behind the methodology - the simplification of the stakeholder-analyst dialogue during the IS requirements specification. For that, the experiment was conducted. The purpose of the experiment was to specify requirements for the real-world IS using implemented requirement repository, and compare the results to other similar software.

E-business provides important opportunities of trade for businesses, and the supporting business system must handle this environment efficiently. One current trend in business systems is to move business logic, such as business processes and business rules, out from the application logic and into separate support systems. The reason to make this separation is to increase the agility of the business, to make the system able to change more rapidly when the business situation changes. This report focus on business rules enforced in business rule engines. Specific interest is on how such rule engines meet the requirements of the e-business domain. The report presents an overview of business rule engines. Five general categories of characteristics are proposed. The proposed characteristics are then used in a comparison of three business rule engines.