Magistriniame darbe tiriami sąveikumo sprendimai bei specifiniai verslo taisyklių suderinimo metodai, smulkaus ir vidutinio verslo (toliau - SVV) įmonių valdymo informacinėse sistemose, nagrinėjamos šio suderinimo problemos bei galimybės. Pagrindinis tyrimo objektas yra verslo taisyklių suderinimo problemų ir sprendimų apžvalga ir analizė. Remiantis analizės rezultatais darbe bus siekiama sukurti metodiką, leisiančią efektyviau suderinti verslo taisykles įmonių sąveikumo sprendimuose. Darbo tikslas - ištirti egzistuojančių verslo taisyklių suderinimo metodus, jų apribojimus ir galimybes bei pasiūlyti metodiką, gebančią efektyviau suderinti dviejų ar daugiau įmonių derybų taisykles. Naudojant pasiūlytą metodiką išspręsti automatinių derybų problemą, kai dvejų ar daugiau partnerių iš anksto suformuluotos derybų taisyklės automatiškai suderinamos ir pritaikomos perduodamiems verslo dokumentams, minimaliai dalyvaujant žmonėms. Tyrimo poreikį sąlygojo išaugusi SVV konkurencija, poreikis gerinti įmonių tarpusavio sąveikumą vykdant užsakymus bei siekis pasiūlyti kokybiškesnes ir operatyvesnes paslaugas. Darbą sudaro įvadas, šeši skyriai ir išvados. Pirmosiose keturiose skyriuose paaiškinamas problemos aktualumas, formuluojami darbo tikslas ir uždaviniai, supažindinama su tyrimo struktūra, pateikiama išsami esamų sprendimų apžvalga ir analizė, apibrėžiama siekiamo sprendimo koncepcija bei nurodoma reikalavimų specifikacija. Pateikiamas sistemos projektas atitinkantis... [toliau žr. visą tekstą] / This paper investigates the interoperability solutions and specific methods of the reconciliation of business rules, small and medium-sized business (hereinafter referred to as SMB) management in information systems, as well as the problems and opportunities related to such reconciliation. The main objective of the research is to review and analyse the problems of business rules reconciliation and their solutions. The paper will attempt to create a method based on results, which will allow users to reconcile business rules in enterprise interoperability solutions more effectively. The goal of the paper is to investigate existing reconciliation methods of business rules, their limitations and possibilities, as well as offer a method which will be more effective in reconciling negotiation rules of two or more companies. Utilising the proposed method, the paper aims to find solutions to the problems related to automated negotiations where previously outlined negotiation rules between two or more parties are automatically reconciled and applied to the exchanged business documents with a minimal participation of people. The need for such research arose from the increased competition between SMBs, the necessity to enhance companies’ interoperability when fulfilling orders, as well as the pursuit to offer more effective, better quality services. The paper consists of the introduction, six parts and the conclusion. The first four parts encapsulate the relevance of the problem, the... [to full text]

Šiandienos įmonės susiduria su labai greitai besikeičiančia aplinka ir negali laikytis numatyto ilgalaikio veiklos modelio. Įmonės veikla ir jos veiklos modelis turi būti dinamiški. Viena didžiausių problemų verslo taisyklių panaudojimui yra jų kiekis ir sunkiai nuspėjama tarpusavio sąveika. Taisyklėms veikiant kartu atsiranda įvairūs konfliktai. Taisyklių konfliktų aptikimui ir logiškumui bei nuoseklumui patikrinti galima naudoti logika pagrįstus mechanizmus tokius kaip išvedimas. Darbe atlikta dalykinės srities literatūros apžvalga, suformuluotas metodas, leidžiantis XML atvaizduotas verslo taisykles transformuoti į predikatus bei komponuoti į verslo taisyklių rinkinius siekiant tuos rinkinius panaudoti duomenų analizei programų sistemoje. Verslo taisykli�� rinkinys turi būti išsamus ir neprieštaraujantis. Tam naudojama išvedimo mašina. / One of the greatest problems using business rules are their quantity and difficulty in foreseeing of their interplay. Conflicts become apparent when rules are used in conjunction. A logic based derivation mechanism can be used for detection of rule incongruence and to analyze their logical and chronological sequence. This paper presents a review of related works and method for transformation of the business rules represented in XML into predicate set for use in inference engine and business rules driven rule set consistency check and use of such a complete rule set in data analysis system.

Pagrindinis darbo tikslas – sukurti struktūrizuotų ribojimų įvedimo į informacinių sistemų modelius įskiepį. Išbandyti struktūrizuotus ribojimus buvo pasirinkta MagicDraw UML sistema, kuriai sukurtas veiklos taisyklių įvedimo įskiepis. Įskiepis remiasi pagrindiniais šablonizuoto įvedimo principais ir dalinai užtikrina įvedamų duomenų teisingumą, kadangi aprašant ribojimus galima pasirinkti modelio elementus pagal jų navigavimo ryšius. Pasiūlytas prototipas skirtas sistemų analitikui, kuris aprašo sistemos reikalavimus. Sukurtas prototipas pasiekia užsibrėžtus darbo tikslus ir gali būti tobulinamas ateityje. Ribotos natūraliai kalbai artimos kalbos šablonai gali būti kuriami panaudojant TBEProfile modulį. Įskiepio pagalba sukurtos veiklos taisyklės yra struktūrizuotos ir nesunkiai suprantamos. Tai padidina projekto kūrimo automatizavimo lygį. Vartotojas naudojantis prototipu gali specifikuoti veiklos taisykles UML klasių, protokolų būsenų, būsenų mašinų, sekų ir veiklos diagramose. Įskiepis buvo sukurtas JAVA programavimo kalba ir naudojantis „MagicDraw UML“ OpenApi dokumentacija. / The main goal of this project was to develop template based business rules plug-in for CASE tool. We have chosen to create plug-in for CASE tool “Magic Draw UML”. This plug-in extends “Magic Draw UML” abilities of constraints creation, because system partially ensures the correctness of constraint elements. Plug-in was developed for system analysts, who precisely specify requirements for systems. The prototype we made successfully embodies main goals of project and can be improved in the future. Limited natural language templates can be specified using TBEProfile module. Business rules created with plug-in are formatted and clear to understand. It helps to improve project engineering level of automation. User using prototype is able to specify business rules in UML class, state protocol, state machine, sequence and activity diagrams. System was created using JAVA programming language and “Magic Draw UML OpenAPI”.

Today’s business’s more and more depend on information systems to give them edge on competition and keep double digit growth rates needed to satisfy shareholders. And information systems, serving their needs, have to keep up with changing business requirements. Business Rules Approach [10] seems to be the answer to their demands, but not many service and solution providers can satisfy their needs, because there is no standard based software engineering process to efficiently provide solution to customers. This works provides methodology of integrating business rules approach into existing and time proven software development process as well as providing needed infrastructure to creating solution specification and integrating externalized business rules with created system specification. This work concentrates on tasks: 1. Creating business rules management model; 2. Selecting software development process, adaptable to business rules approach; 3. Integrating business rules management model into selected software development process; 4. Relating externalized business rules with specification entities; 5. Providing comparison of unmodified software process with provided proposal.

Today's business world is very dynamic and organizations have to quickly adjust their internal policies to follow the market changes. Such adjustments must be propagated to the business logic embedded in the organization's information systems, that are often legacy applications not designed to represent and operationalize the business logic independently from the technical aspects of the programming language employed. Consequently, the business logic buried in the system must be discovered and understood before being modified. Unfortunately, such activities slow down the modification of the system to new requirements settled in the organization policies and threaten the consistency and coherency of the organization business. In order to simplify these activities, we provide amodel-based approach to extract and represent the business logic, expressed as a set of business rules, from the behavioral and structural parts of information systems. We implement such approach for Java, COBOL and relational database management systems. The proposed approach is based on Model Driven Engineering,that provides a generic and modular solution adaptable to different languages by offering an abstract and homogeneous representation of the system.

Há mais de uma década, BPM vem sendo introduzida nas organizações devido suas vantagens tais como documentação, gerenciamento, monitoração e melhoria contínua de seus processos de negócio. Na abordagem BPM, normalmente, os processos de negócio da organização são executados sob o controle de um Sistema Gerenciador de Processos de Negócio. Estes sistemas executam os processos de negócio, coletando informações úteis para organização. Por exemplo, através destes sistemas é possível identificar as atividades que mais demoram ou consomem mais recursos humanos. Desta forma, é possível redesenhar os processos de maneira ágil, garantido a evolução contínua do negócio. Entretanto, para se beneficiar da tecnologia BPM, a organização deve mapear seus processos de negócio e modelá-los no Sistema Gerenciador de Processos de Negócio. Normalmente, esse trabalho é realizado por especialistas humanos, que observam e identificam o funcionamento da organização, definindo, em detalhes, os fluxos de trabalho realizados para cumprir determinadas metas de negócio. Contudo, na maior parte das organizações os processos de negócio encontram-se implementados em sistemas de informações legados. Tais sistemas possuem pouca documentação, foram desenvolvidos com uso de tecnologias obsoletas e os processos de negócio, neles contidos, foram programados implicitamente no seu código fonte. Deste modo, além das entrevistas com usuários-chave da organização, os analistas precisam também entender o funcionamento dos sistemas legados a fim de identificar os processos de negócio da organização. Geralmente, os analistas de negócio fazem este trabalho manualmente, interpretando os algoritmos escritos no código fonte legado e identificando os fluxos de trabalho nele escritos. Esse trabalho é complexo, demorado e suscetível a erros, pois depende do nível de conhecimento que os analistas de negócio têm sobre o código fonte legado. Pensando neste problema, essa tese apresenta um método que automatiza a descoberta de processos de negócio implementados implicitamente no código fonte de sistemas legados. O método propõe uma técnica híbrida, que usa análise estática do código fonte e análise dinâmica (mineração de processos) para descobrir os processos de negócio codificados em sistemas legados. A tese apresenta os passos para aplicação do método, definindo para cada passo, um conjunto de ferramentas capazes de automatizar a descoberta de informações no código fonte legado. Este trabalho também mostra três estudos de caso, onde o método foi aplicado com sucesso e comparado a outras técnicas existentes na literatura. / For over a decade, BPM is being introduced in organizations due to its advantages such as documentation, management, monitoring and continuous improvement of its business processes. In BPM approach, business processes of the organization are executed under the control of a Business Processes Management System. These systems monitor the execution of the processes and measuring the operational efficiency of the organization through, for example, of the identification of activities those are slower or consume more resources. Thus, the organization can redesign their business processes in an agile and fast mode, thereby ensuring the continued evolution of your business. However, to take advantage of BPM technology, the organization must map their business processes and model them in the Business Processes Management System. Typically, organizations execute the business process mapping through manual techniques, such as interviews, meetings with users, questionnaires, document analysis and observations of the organizational environment. However, in most organizations business processes are executed in legacy systems information. Such systems have not documentation, have been developed with obsolete technologies and the business processes are programmed implicitly in its source code. Thus, in addition to interviews with expert users of the organization, analysts must also understand the working of legacy systems in order to identify the business processes of the organization. Generally, business analysts do this work manually, interpreting algorithms written in legacy source code and identifying workflows written in the source code. This work is complex, time consuming and error prone, since it depends on the knowledge level that business analysts have about the legacy source code. Thinking about this problem, this thesis presents a method that automates the discovery of business processes implemented implicitly in the source code of legacy systems. The method proposes a hybrid technique that uses static analysis of the source code and dynamic analysis (mining process) to discover business processes encoded in legacy systems. The thesis presents the steps for applying the method, defining for each step, a set of tools that automate the discovery of information in the legacy source code. This work also shows three case studies where the method was successfully applied and compared to other existing techniques in the literature.

Há mais de uma década, BPM vem sendo introduzida nas organizações devido suas vantagens tais como documentação, gerenciamento, monitoração e melhoria contínua de seus processos de negócio. Na abordagem BPM, normalmente, os processos de negócio da organização são executados sob o controle de um Sistema Gerenciador de Processos de Negócio. Estes sistemas executam os processos de negócio, coletando informações úteis para organização. Por exemplo, através destes sistemas é possível identificar as atividades que mais demoram ou consomem mais recursos humanos. Desta forma, é possível redesenhar os processos de maneira ágil, garantido a evolução contínua do negócio. Entretanto, para se beneficiar da tecnologia BPM, a organização deve mapear seus processos de negócio e modelá-los no Sistema Gerenciador de Processos de Negócio. Normalmente, esse trabalho é realizado por especialistas humanos, que observam e identificam o funcionamento da organização, definindo, em detalhes, os fluxos de trabalho realizados para cumprir determinadas metas de negócio. Contudo, na maior parte das organizações os processos de negócio encontram-se implementados em sistemas de informações legados. Tais sistemas possuem pouca documentação, foram desenvolvidos com uso de tecnologias obsoletas e os processos de negócio, neles contidos, foram programados implicitamente no seu código fonte. Deste modo, além das entrevistas com usuários-chave da organização, os analistas precisam também entender o funcionamento dos sistemas legados a fim de identificar os processos de negócio da organização. Geralmente, os analistas de negócio fazem este trabalho manualmente, interpretando os algoritmos escritos no código fonte legado e identificando os fluxos de trabalho nele escritos. Esse trabalho é complexo, demorado e suscetível a erros, pois depende do nível de conhecimento que os analistas de negócio têm sobre o código fonte legado. Pensando neste problema, essa tese apresenta um método que automatiza a descoberta de processos de negócio implementados implicitamente no código fonte de sistemas legados. O método propõe uma técnica híbrida, que usa análise estática do código fonte e análise dinâmica (mineração de processos) para descobrir os processos de negócio codificados em sistemas legados. A tese apresenta os passos para aplicação do método, definindo para cada passo, um conjunto de ferramentas capazes de automatizar a descoberta de informações no código fonte legado. Este trabalho também mostra três estudos de caso, onde o método foi aplicado com sucesso e comparado a outras técnicas existentes na literatura. / For over a decade, BPM is being introduced in organizations due to its advantages such as documentation, management, monitoring and continuous improvement of its business processes. In BPM approach, business processes of the organization are executed under the control of a Business Processes Management System. These systems monitor the execution of the processes and measuring the operational efficiency of the organization through, for example, of the identification of activities those are slower or consume more resources. Thus, the organization can redesign their business processes in an agile and fast mode, thereby ensuring the continued evolution of your business. However, to take advantage of BPM technology, the organization must map their business processes and model them in the Business Processes Management System. Typically, organizations execute the business process mapping through manual techniques, such as interviews, meetings with users, questionnaires, document analysis and observations of the organizational environment. However, in most organizations business processes are executed in legacy systems information. Such systems have not documentation, have been developed with obsolete technologies and the business processes are programmed implicitly in its source code. Thus, in addition to interviews with expert users of the organization, analysts must also understand the working of legacy systems in order to identify the business processes of the organization. Generally, business analysts do this work manually, interpreting algorithms written in legacy source code and identifying workflows written in the source code. This work is complex, time consuming and error prone, since it depends on the knowledge level that business analysts have about the legacy source code. Thinking about this problem, this thesis presents a method that automates the discovery of business processes implemented implicitly in the source code of legacy systems. The method proposes a hybrid technique that uses static analysis of the source code and dynamic analysis (mining process) to discover business processes encoded in legacy systems. The thesis presents the steps for applying the method, defining for each step, a set of tools that automate the discovery of information in the legacy source code. This work also shows three case studies where the method was successfully applied and compared to other existing techniques in the literature.

Context. Automation of conversion of business rules into source code in software development project can reduce time and effort in phase of development. In this thesis we discuss automatic conversion of behavioral business rules defined in Semantics of Business Vocabulary and Rules (SBVR) standard, to fragments of Unified Modeling Language diagrams: activity, sequence and state machine. It is conversion from Computation Independent Model (CIM) into Platform Independent Model (PIM) levels defined by Model Driven Architecture (MDA). PIM in MDA can be further transformed into Platform Specific Model which is prepared for source code generation. Objectives. Aim of this thesis is to initially explore field of automatic conversion of behavioral business rules - conversion from SBVR representation to fragments of UML diagrams. It is done by fulfilment of objectives defined as following: -To find out properties of SBVR behavioral rule which ensure that the rule can be automatically converted to parts of UML behavioral diagrams (activity, sequence, state machine). -To propose mapping of SBVR contructs to constructs of UML behavioral diagrams. -To prepare guidelines which help to specify SBVR behavioral business rules in such way that they can be automatically transformed into fragments of selected UML behavioral diagrams. Methods. Expert opinion and case study were applied. Business analysts from industry and academia were asked to convert set of SBVR behavioral business rules to UML behavioral diagrams: activity, sequence and state machine. Analysis of the set of business rules and their conversions to UML diagrams was basis for fulfilment of objectives. Results. 2 syntax and 3 semantic properties were defined. Conversion rules which define mapping for SBVR behavioral business rules constructs to UML constructs were defined: 5 rules for conversion to activity diagram, 6 for conversion to sequence diagram, 5 for conversion to state machine diagram. 6 guidelines which are intended to help in specification of behavioral business rules that can be automatically transformed into UML diagrams according to the presented conversion rules, were defined. Conclusions. Research performed in this thesis is initial study of automatic conversion of behavioral business rules from SBVR notation to UML behavioral diagrams notation. Validation of defined properties, conversion rules and guidelines can be done in industry as future work. Re-execution of research for larger and more diverse set/sets of behavioral business rules taken from industry projects, sufficiently broad access to business analysts from industry and academia could help to improve results.

Há mais de uma década, BPM vem sendo introduzida nas organizações devido suas vantagens tais como documentação, gerenciamento, monitoração e melhoria contínua de seus processos de negócio. Na abordagem BPM, normalmente, os processos de negócio da organização são executados sob o controle de um Sistema Gerenciador de Processos de Negócio. Estes sistemas executam os processos de negócio, coletando informações úteis para organização. Por exemplo, através destes sistemas é possível identificar as atividades que mais demoram ou consomem mais recursos humanos. Desta forma, é possível redesenhar os processos de maneira ágil, garantido a evolução contínua do negócio. Entretanto, para se beneficiar da tecnologia BPM, a organização deve mapear seus processos de negócio e modelá-los no Sistema Gerenciador de Processos de Negócio. Normalmente, esse trabalho é realizado por especialistas humanos, que observam e identificam o funcionamento da organização, definindo, em detalhes, os fluxos de trabalho realizados para cumprir determinadas metas de negócio. Contudo, na maior parte das organizações os processos de negócio encontram-se implementados em sistemas de informações legados. Tais sistemas possuem pouca documentação, foram desenvolvidos com uso de tecnologias obsoletas e os processos de negócio, neles contidos, foram programados implicitamente no seu código fonte. Deste modo, além das entrevistas com usuários-chave da organização, os analistas precisam também entender o funcionamento dos sistemas legados a fim de identificar os processos de negócio da organização. Geralmente, os analistas de negócio fazem este trabalho manualmente, interpretando os algoritmos escritos no código fonte legado e identificando os fluxos de trabalho nele escritos. Esse trabalho é complexo, demorado e suscetível a erros, pois depende do nível de conhecimento que os analistas de negócio têm sobre o código fonte legado. Pensando neste problema, essa tese apresenta um método que automatiza a descoberta de processos de negócio implementados implicitamente no código fonte de sistemas legados. O método propõe uma técnica híbrida, que usa análise estática do código fonte e análise dinâmica (mineração de processos) para descobrir os processos de negócio codificados em sistemas legados. A tese apresenta os passos para aplicação do método, definindo para cada passo, um conjunto de ferramentas capazes de automatizar a descoberta de informações no código fonte legado. Este trabalho também mostra três estudos de caso, onde o método foi aplicado com sucesso e comparado a outras técnicas existentes na literatura. / For over a decade, BPM is being introduced in organizations due to its advantages such as documentation, management, monitoring and continuous improvement of its business processes. In BPM approach, business processes of the organization are executed under the control of a Business Processes Management System. These systems monitor the execution of the processes and measuring the operational efficiency of the organization through, for example, of the identification of activities those are slower or consume more resources. Thus, the organization can redesign their business processes in an agile and fast mode, thereby ensuring the continued evolution of your business. However, to take advantage of BPM technology, the organization must map their business processes and model them in the Business Processes Management System. Typically, organizations execute the business process mapping through manual techniques, such as interviews, meetings with users, questionnaires, document analysis and observations of the organizational environment. However, in most organizations business processes are executed in legacy systems information. Such systems have not documentation, have been developed with obsolete technologies and the business processes are programmed implicitly in its source code. Thus, in addition to interviews with expert users of the organization, analysts must also understand the working of legacy systems in order to identify the business processes of the organization. Generally, business analysts do this work manually, interpreting algorithms written in legacy source code and identifying workflows written in the source code. This work is complex, time consuming and error prone, since it depends on the knowledge level that business analysts have about the legacy source code. Thinking about this problem, this thesis presents a method that automates the discovery of business processes implemented implicitly in the source code of legacy systems. The method proposes a hybrid technique that uses static analysis of the source code and dynamic analysis (mining process) to discover business processes encoded in legacy systems. The thesis presents the steps for applying the method, defining for each step, a set of tools that automate the discovery of information in the legacy source code. This work also shows three case studies where the method was successfully applied and compared to other existing techniques in the literature.

Companies today are required more and more to interconnect their information systems with partners and suppliers in order to be competitive in a global marketplace. A problem of how to compare a security policy between two different companies when they need to agree upon a single security policy has been raised. Can a comparison of two access control policies made through Semantic of Business Vocabulary and Business Rules (SBVR) be more appropriate than the traditional way of intuitively comparing two information security policies? In this research, a case study has been conducted along with the questionnaires as a data collection approach. In the case study, a calculation for a degree of policy statement similarity of Company A’s and Company B has been done. Both calculations were based on the questionnaire results of the Company A and Company B in form of SBVR and traditional policy statements separately. This research has revealed that SBVR applied policy is more appropriate for comparing two company policies than a traditional written policy. By applying SBVR to the policy statements, Company A and Company B had their policy in the same structure, which is in the SBVR format. They could get a very clear similar part of the policy statements (70% calculated by the results of the second questionnaire in this case study) agreed by both companies.