Business Rules Friendly or not so Business Rules Friendly Business Concepts Modelling - Early Experiences from a Business Rules Project on a Digital Vaccination Recommendation Service

WHO estimated in 2002 that 1.4 million children in the world would die from preventable diseases (World Health Organization, 2010). Each child is, or should be, immunized according to their national immunization schedule, which regulates i.e. vaccines and doses. Problems emerge when immigrant children should be transferred from one national vaccination schedule into another. This problem is quite evident in Sweden (Statistics Sweden, 2010). Vaccination practitioners have a hard time figuring out how to immunize an immigrant child. As a remedy for this situation, the VacSam project develops a Business Rules (BR) centric digital service through principles of (BR Approach), for providing unique vaccination recommendations. The service is designed using a commercial BRMS (BR Management Systems), which require a business concepts model. Thus, the paper presents early findings on how a business concepts model could be designed more or less BR-friendly. We have discovered, by designing, that a rigid, relational model approach is not BR-friendly. Instead, the concepts model should be de-signed to provide rule clarity and understandability. Thus, we draw the conclusion that a con-cepts model designed for persistent data storing, favouring a good quality relational model, is not rule friendly

Business rules based legacy system evolution towards service-oriented architecture.

Enterprises can be empowered to live up to the potential of becoming dynamic, agile and real-time. Service orientation is emerging from the amalgamation of a number of key business, technology and cultural developments. Three essential trends in particular are coming together to create a new revolutionary breed of enterprise, the service-oriented enterprise (SOE): (1) the continuous performance management of the enterprise; (2) the emergence of business process management; and (3) advances in the standards-based service-oriented infrastructures. This thesis focuses on this emerging three-layered architecture that builds on a service-oriented architecture framework, with a process layer that brings technology and business together, and a corporate performance layer that continually monitors and improves the performance indicators of global enterprises provides a novel framework for the business context in which to apply the important technical idea of service orientation and moves it from being an interesting tool for engineers to a vehicle for business managers to fundamentally improve their businesses

Enterprise modelling framework for dynamic and complex business environment: socio-technical systems perspective

The modern business environment is characterised by dynamism and ambiguity. The causes include global economic change, rapid change requirements, shortened development life cycles and the increasing complexity of information technology and information systems (IT/IS). However, enterprises have been seen as socio-technical systems. The dynamic complex business environment cannot be understood without intensive modelling and simulation. Nevertheless, there is no single description of reality, which has been seen as relative to its context and point of view. Human perception is considered an important determinant for the subjectivist view of reality. Many scholars working in the socio-technical systems and enterprise modelling domains have conceived the holistic sociotechnical systems analysis and design possible using a limited number of procedural and modelling approaches. For instance, the ETHICS and Human-centred design approaches of socio-technical analysis and design, goal-oriented and process-oriented modelling of enterprise modelling perspectives, and the Zachman and DoDAF enterprise architecture frameworks all have limitations that can be improved upon, which have been significantly explained in this thesis. [Continues.

Uma proposta para rastreabilidade no desenvolvimento de software

Orientador: Mario JinoTese (doutorado) - Universidade Estadual de Campinas, Faculdade de Engenharia Elétrica e de ComputaçãoResumo: Rastreabilidade tem sido um tópico de pesquisa no desenvolvimento de software por pelo menos 40 anos, sendo adicionada a muitos padrões, como o DOD-STD-2167A e o IEEE 830-1998. Este último, por exemplo, afirma que uma boa especificação de requisitos de software deve ser rastreável. A rastreabilidade fornece muitos benefícios para projetos de software, tais como: identificação das razões para decisões de design, prevenção de problemas de dependência, identificação de responsabilidades em um projeto, estimação de impacto e de custo de modificações, e medição do progresso de desenvolvimento. Sucintamente, a rastreabilidade permite a geração de um produto de melhor qualidade. Dois principais focos surgiram na literatura nos últimos anos: desenvolvimento baseado em modelo e geração automática de rastros. O primeiro trata da modelagem de rastreabilidade, definindo relações e elementos de um projeto; o segundo trata da descoberta automática de relações entre elementos. Vários conceitos foram definidos até agora, como rastreabilidade bidirecional, rastreabilidade de especificações pré e pós-requisitos, rastreabilidade horizontal e vertical, e rastreabilidade explícita e implícita. Embora haja um consenso geral sobre a maioria dos conceitos relacionados a rastreabilidade, há uma falta de consenso sobre como, e o quê, deve ser rastreado; não há consenso sobre: quais relações são relevantes para os projetos de desenvolvimento de software, quais elementos devem ser rastreados, como as mudanças nos elementos de um projeto afetam as relações existentes, ou como atualizar as relações dadas certas mudanças. Os modelos de rastreabilidade visam responder a essas questões fornecendo um padrão para ser usado como uma guia em projetos de desenvolvimento de software; entretanto, não há consenso sobre o que um modelo deve conter. Existe uma variedade de modelos, cada um considerando diferentes tipos de relações, elementos, e possuindo diferentes focos. Além disso, a maioria dos modelos possui problemas que tornam o seu uso difícil, ou até mesmo impossível; por exemplo, existem modelos que não descrevem - suficientemente ou em nada - as ligações de rastreabilidade que propõem. Este trabalho visa a ajudar nesta questão, fornecendo uma contribuição dupla: um modelo de referência para criar e avaliar modelos de rastreabilidade, e um metamodelo abrangente, construído em cima do modelo de referência, para adicionar rastreabilidade a projetos de desenvolvimento de software. Nosso Modelo de Referência para rastreabilidade define os elementos básicos em um modelo de rastreabilidade e define conjuntos básicos de: ações, tipos de ligações, tipos de artefatos, e processos. Propriedades necessárias para o conjunto de tipos de ligações e o conjunto de tipos de artefatos também são fornecidas. Nosso Metamodelo para rastreabilidade é composto por: um modelo conceitual descrevendo e organizando os elementos de rastreabilidade; um conjunto de tipos de artefatos representando as atividades definidas no Modelo de Referência, além de um conjunto de tipos de artefatos criados para registrar decisões de design; um conjunto de tipos de ligações que modelam diferentes relações de rastreabilidade; e um conjunto de processos para garantir a consistência de projetosAbstract: Traceability has been a topic of research in software development for at least 40 years, being added to many standards, such as the DOD-STD-2167A and the IEEE 830-1998. The latter, for instance, states that a good software requirements specification should be traceable. Traceability provides many benefits to software projects, such as: identification of the reasons for design decisions, avoidance of dependency issues, identification of accountability in a project, estimation of impact and cost of modifications, and measurement of development progress. Succintly, traceability allows the generation of a better quality product. Two main focuses have emerged in the literature in recent years: model-based development and automated trace generation. The former concerns modeling traceability by defining relations and elements in a project; the latter concerns automatic discovery of relations between elements in a project. Several concepts have been defined so far, such as bidirectional traceability, pre and post-requirements specification traceability, horizontal and vertical traceability, and explicit and implicit traceability. While there is general consensus on most concepts related to traceability, there is a lack of consensus on how, and what, should be traced; there is no consensus on which relations are relevant for software development projects, which elements should be traced, how changes in elements of a project affects existing relations, or how to update relations given certain changes. Traceability models aim to answer these questions by providing a standard to be used as a guide in software development projects; however, there is no consensus on what a model should contain. There is a variety of models, each considering different types of relations, elements, and having distinct focuses. Also, the majority of models have issues which makes them difficult or even impossible to use; for instance, there are models which do not describe - sufficiently or at all - traceability links which they propose. This work aims to help in this issue by providing a twofold contribution: a reference model for creating and evaluating traceability models, and a comprehensive metamodel, built on top of the reference model, to add traceability to software development projects. Our Reference Model for traceability defines the basic elements in a traceability model and defines basic sets of: actions, link types, artifact types, and processes. Necessary properties for the sets of link types and artifact types are also provided. Our Metamodel for traceability is composed of: a conceptual model describing and organizing the elements of traceability; a set of artifact types representing the activities of the Reference Model, plus a set of artifact types created to record design decisions; a set of link types modeling different traceability relations; and a set of processes to ensure project consistencyDoutoradoEngenharia de ComputaçãoDoutor em Engenharia Elétrica1142618CAPE

Ein Konzept auf der Basis von Ontologien und Petri-Netzen

In der Dissertation wird das Themenfeld der Modellierung kooperativer Informationssysteme behandelt. Zu diesem Zweck wird ein Ansatz für die Modellierung kooperativer Informationssysteme entwickelt, der zum einen auf Ontologien und zum anderen auf Petri-Netzen basiert. Beide Konzepte werden vom Verfasser zu so genannten „Ontologie-Netzen“ zusammengeführt. Seit einigen Jahren werden Ontologien in unterschiedlichsten Wissenschaftsdisziplinen untersucht. Das Interesse an Ontologie ist nicht zuletzt auf die jüngsten Entwicklungen im Bereich des Semantic Web zurückzuführen. Auch über webbasierte Applikationen hinaus werden Ontologien in Szenarien untersucht, in denen Akteure mit unterschiedlichen Sprach- und Wissenshintergründen in Kommunikation miteinander treten. Während nämlich traditionelle Modellierungsmethoden lediglich die Ex-Ante Vorgabe eines Begriffsystems unterstützen, können mit Ontologien darüber hinaus auch Ex-Post Harmonisierungen unterschiedlicher Begriffswelten angestrebt werden. Darüber hinaus verfügen Ontologien in der Regel über eine Inferenzkomponente, die die Erschließung von „implizitem“ Wissen erlaubt. Die abstrakte Spezifikation regelartiger Zusammenhänge in einer Ontologie kann somit bei konkreter Anwendung in einer Domäne zur Explikation von Fakten führen, die ansonsten nicht berücksichtigt werden könnten. Aus dem Blickwinkel der Wirtschaftswissenschaften haben Ontologien eine besondere Bedeutung aufgrund ihres Leistungspotenzials für Zwecke der Unternehmensmodellierung. Insbesondere für Organisationsformen, die unter das Spektrum zwischenbetrieblicher Kooperationen fallen, könnten sich Ontologien als effektivitäts- und effizienzsteigernde Methoden der Unternehmensmodellierung erweisen. Es sind nämlich gerade Organisationsformen, an denen Akteure aus unterschiedlichen Hintergründen für Zwecke der gemeinschaftlichen Leistungserstellung zusammenkommen, bei denen sich bestehende Sprachbarrieren negativ auf die Geschäftsprozesse auswirken. Darüber hinaus erlauben Ontologien mit ihrer Inferenzkomponente die formale Spezifikation von „Business Rules“ die bei der gemeinschaftlichen Leistungserstellung zu gelten haben. Ontologien beschränken sich allerdings auf die rein statischen Aspekte, da sie nur für die Repräsentation deklarativen Wissens verwendet werden können. Daher haben Ontologien auch nur eine deklarative Semantik. Sie äußert sich z.B. darin, dass die Reihenfolge der (Teil-)Spezifikationen für ihre Bedeutung irrelevant ist. Dadurch kann immer nur ein bestimmter Zustand der Realität modelliert werden. Von Methoden zur Modellierung zwischenbetrieblicher Kooperationen wird allerdings vermehrt gefordert, sowohl statische als auch dynamische Aspekte erfassen zu können. Unter dem Paradigma der „Geschäftsprozessorientierung“ haben sich daher vermehrt solche Methoden durchgesetzt, die sowohl statische als auch dynamische Aspekte der Realität zu Erfassen in der Lage sind. Mit dem integrativen Modellierungskonzept wird in der vorliegenden Arbeit ein Ansatz vorgestellt, der es erlaubt, Ontologien um dynamische Aspekte zu erweitern. Hierzu werden Ontologien in eine Klasse höherer Petri-Netze eingebunden. Letztgenannte haben sich nämlich in der Vergangenheit bei der Ausweitung formaler Spezifikationen um dynamische Aspekte als äußerst fruchtbar erwiesen. Dabei wird die Kompatibilität der beiden Ansätze über ihre gemeinsame prädikatenlogische Basis gewährleistet. Darüber hinaus erfreuen sich Petri-Netze sowohl in theoretischen Ausarbeitungen als auch in praktischen Umsetzungen einer hohen Beliebtheit. Die noch relativ jungen Forschungsarbeiten zu Ontologien könnten durch einen solchen Ansatz in ihrer Akzeptanzrate erhöht werden