Towards Consistency Management for a Business-Driven Development of SOA

The usage of the Service Oriented Architecture (SOA) along with the Business Process Management has emerged as a valuable solution for the complex (business process driven) system engineering. With a Model Driven Engineering where the business process models drive the supporting service component architectures, less effort is gone into the Business/IT alignment during the initial development activities, and the IT developers can rapidly proceed with the SOA implementation. However, the difference between the design principles of the emerging domainspecific languages imposes serious challenges in the following re-design phases. Moreover, enabling evolutions on the business process models while keeping them synchronized with the underlying software architecture models is of high relevance to the key elements of any Business Driven Development (BDD). Given a business process update, this paper introduces an incremental model transformation approach that propagates this update to the related service component configurations. It, therefore, supports the change propagation among heterogenous domainspecific languages, e.g., the BPMN and the SCA. As a major contribution, our approach makes model transformation more tractable to reconfigure system architecture without disrupting its structural consistency. We propose a synchronizer that provides the BPMN-to-SCA model synchronization with the help of the conditional graph rewriting

Threats Management Throughout the Software Service Life-Cycle

Software services are inevitably exposed to a fluctuating threat picture. Unfortunately, not all threats can be handled only with preventive measures during design and development, but also require adaptive mitigations at runtime. In this paper we describe an approach where we model composite services and threats together, which allows us to create preventive measures at design-time. At runtime, our specification also allows the service runtime environment (SRE) to receive alerts about active threats that we have not handled, and react to these automatically through adaptation of the composite service. A goal-oriented security requirements modelling tool is used to model business-level threats and analyse how they may impact goals. A process flow modelling tool, utilising Business Process Model and Notation (BPMN) and standard error boundary events, allows us to define how threats should be responded to during service execution on a technical level. Throughout the software life-cycle, we maintain threats in a centralised threat repository. Re-use of these threats extends further into monitoring alerts being distributed through a cloud-based messaging service. To demonstrate our approach in practice, we have developed a proof-of-concept service for the Air Traffic Management (ATM) domain. In addition to the design-time activities, we show how this composite service duly adapts itself when a service component is exposed to a threat at runtime.Comment: In Proceedings GraMSec 2014, arXiv:1404.163

Integration of BPM systems

New technologies have emerged to support the global economy where for instance suppliers, manufactures and retailers are working together in order to minimise the cost and maximise efficiency. One of the technologies that has become a buzz word for many businesses is business process management or BPM. A business process comprises activities and tasks, the resources required to perform each task, and the business rules linking these activities and tasks. The tasks may be performed by human and/or machine actors. Workflow provides a way of describing the order of execution and the dependent relationships between the constituting activities of short or long running processes. Workflow allows businesses to capture not only the information but also the processes that transform the information - the process asset (Koulopoulos, T. M., 1995). Applications which involve automated, human-centric and collaborative processes across organisations are inherently different from one organisation to another. Even within the same organisation but over time, applications are adapted as ongoing change to the business processes is seen as the norm in today’s dynamic business environment. The major difference lies in the specifics of business processes which are changing rapidly in order to match the way in which businesses operate. In this chapter we introduce and discuss Business Process Management (BPM) with a focus on the integration of heterogeneous BPM systems across multiple organisations. We identify the problems and the main challenges not only with regards to technologies but also in the social and cultural context. We also discuss the issues that have arisen in our bid to find the solutions

Bridging the Gap Between Business Process Models and Service Composition Specifications

Fundamental goals of any Service Oriented Architecture (SOA) include the flexible support and adaptability of business processes as well as improved business-IT alignment. Existing approaches, however, have failed to fully meet these goals. One of the major reasons for this deficiency is the gap that exists between business process models on the one hand and workflow specifications and implementations (e.g., service composition schemes) on the other hand. In practice, each of these two perspectives has to be regarded separately. In addition, even simple changes to one perspective (e.g. due to new regulations or organizational change) require error-prone, manual re-editing of the other one. Over time, this leads to degeneration and divergence of the respective models and specifications. This aggravates maintenance and makes expensive refactoring inevitable. This chapter presents a flexible approach for aligning business process models with workflow specifications. In order to maintain the complex dependencies that exist between high-level business process models (as used by domain experts) and technical workflow specifications (i.e., service composition schemas), respectively, (as used in IT departments) we introduce an additional model layer – the so-called system model. Furthermore, we explicitly document the mappings between the different levels (e.g., between business process model and system model). This simplifies model adoptions by orders of magnitudes when compared to existing approaches

A service oriented architecture to implement clinical guidelines for evidence-based medical practice

Health information technology (HIT) has been identified as the fundamental driver to streamline the healthcare delivery processes to improve care quality and reduce operational costs. Of the many facets of HIT is Clinical Decision Support (CDS) which provides the physician with patient-specific inferences, intelligently filtered and organized, at appropriate times. This research has been conducted to develop an agile solution to Clinical Decision Support at the point of care in a healthcare setting as a potential solution to the challenges of interoperability and the complexity of possible solutions. The capabilities of Business Process Management (BPM) and Workflow Management systems are leveraged to support a Service Oriented Architecture development approach for ensuring evidence based medical practice. The aim of this study is to present an architecture solution that is based on SOA principles and embeds clinical guidelines within a healthcare setting. Since the solution is designed to implement real life healthcare scenarios, it essentially supports evidence-based clinical guidelines that are liable to change over a period of time. The thesis is divided into four parts. The first part consists of an Introduction to the study and a background to existing approaches for development and integration of Clinical Decision Support Systems. The second part focuses on the development of a Clinical Decision Support Framework based on Service Oriented Architecture. The CDS Framework is composed of standards based open source technologies including JBoss SwitchYard (enterprise service bus), rule-based CDS enabled by JBoss Drools, process modelling using Business Process Modelling and Notation. To ensure interoperability among various components, healthcare standards by HL7 and OMG are implemented. The third part provides implementation of this CDS Framework in healthcare scenarios. Two scenarios are concerned with the medical practice for diagnosis and early intervention (Chronic Obstructive Pulmonary Disease and Lung Cancer), one case study for Genetic data enablement of CDS systems (New born screening for Cystic Fibrosis) and the last case study is about using BPM techniques for managing healthcare organizational perspectives including human interaction with automated clinical workflows. The last part concludes the research with contributions in design and architecture of CDS systems. This thesis has primarily adopted the Design Science Research Methodology for Information Systems. Additionally, Business Process Management Life Cycle, Agile Business Rules Development methodology and Pattern-Based Cycle for E-Workflow Design for individual case studies are used. Using evidence-based clinical guidelines published by UK’s National Institute of Health and Care Excellence, the integration of latest research in clinical practice has been employed in the automated workflows. The case studies implemented using the CDS Framework are evaluated against implementation requirements, conformance to SOA principles and response time using load testing strategy. For a healthcare organization to achieve its strategic goals in administrative and clinical practice, this research has provided a standards based integration solution in the field of clinical decision support. A SOA based CDS can serve as a potential solution to complexities in IT interventions as the core data and business logic functions are loosely coupled from the presentation. Additionally, the results of this this research can serve as an exemplar for other industrial domains requiring rapid response to evolving business processes