A Model-driven Method to Design SoaML Services from BPMN Models: Principles, Proof-of-concept, and Validation

Today's business processes are increasingly complex as they cross organizational boundaries. To execute their business processes, organizations develop software applications called Process-Aware Information System (PAIS). PAIS designers must consider complex scenarios involving multiple partners. Consequently, the architectural design of high quality PAIS is complex and requires vast amounts of knowledge and skills both in software architecture and in the business domain. This paper proposes a model-driven method to design the architecture of PAIS using the service-oriented architecture (SOA) style. The proposed method generates SOA-based design models expressed in SoaML from the specifications of collaborative business processes expressed in BPMN. We developed a prototype tool using the Eclipse Modeling Framework (EMF) ecosystem. We tested the method on a set of processes from the Enterprise Resource Planning literature to assess its effectiveness. Our results show that 80.95\% of the identified services were relevant and corresponded to what architecture specialists expected

A conceptual service oriented architecture framework for integrated flood management

Service oriented architecture (SOA) is a platform and language-independent that guide different services to work together in order to perform business process.The benefits of using SOA such as interoperability, discoverability, loose coupling, flexibility and reliability have led previous researchers to use it as their fundamental basis in designing their software architecture framework.Previous researchers also have exploit SOA and implement it into flood management domain to manage the complex systems that are distributed across the network.However, previous works do not provide the detail process of emergency management into their flood management framework.Therefore, this study aims to propose a conceptual SOA framework for an integrated flood management (IFM) in order to increase the effectiveness and efficiency of managing flood.Furthermore the feasibility of using SOA and the required process of flood management in order to construct the conceptual framework are being investigated by means of a comparative study.In addition, this study also suggests the Service oriented architecture Modeling Language (SoaML) as a technique to model the services for anIFM

MINERVA : Model drIveN and sErvice oRiented framework for the continuous improVement of business process & relAted tools

Organizations are facing several challenges nowadays, one of the most important ones being their ability to react quickly to changes either to their business process (BP) models or to the software implementing them. These changes can come from different sources: external requirements from partners or the market, or new internal requirements for the way that things are carried out by the defined BPs; they may also arise from improvement opportunities detected for the BPs defined, based on BPs execution monitoring and execution evaluation that is done by the organization, and/or its partners and customers. The increasing complexity of both BPs models and the software implementing them, requires the changes needed or the improvements to be carefully weighed against the impact their introduction will have; they ought also to be carried out in a systematic way to assure a successful development. Two key elements are to provide these requirements: the separation of BPs definition from their implementation to minimize the impact of changes in one to the other, and a process to introduce the changes or improvements in the existing BPs and/or software implementing them. Business Process Management (BPM) provides the means for guiding and supporting the modeling, implementation, deployment, execution and evaluation of BPs in an organization, based on the BP lifecycle. The realization of BPs by means of services provides the basis for separating their definition from the technologies implementing them and helps provide a better response to changes in either of the layers defined -definition and implementation of business processes- with minimum impact on the other. Modeling of both BP and services is a key aspect to support this vision, helping provide traceability between elements from one area to the other, so easing the analysis of the impact of changes, among other things. Models have proven to play an important role in the software development process, one of its key uses in the context of BP realization by means of services is that of designing services at a more abstract level than with specific technologies, also promoting reuse by separating services logic from its implementation. MINERVA: Model drIveN & sErvice oRiented framework for the continuous business process improVement & relAted tools is the framework that has been defined in this thesis work; it takes into account all the aspects mentioned, in which the SOC and MDD paradigms are applied to BPs focusing on their continuous improvement, extending an existing BP lifecycle with explicit execution measurement and improvement activities and elements. It is made up of three dimensions: i) conceptual, which defines the concepts that are managed throughout the framework. ii) methodological, which defines a methodology for service oriented development from BPs with automatic generation of SoaML service models from BPMN2 models, along with a continuous improvement process based on execution measurement of the occurrences of BPs in the organization to carry out the improvement effort. iii) tools support for the whole proposal based on several existing tools we have integrated, along with new ones we have developed. The proposals in MINERVA have been validated by means of an experiment and two case studies carried out in the context of real projects in two organizations, from which, as the main result of the applications performed, it can be concluded that MINERVA can be a useful and key guide for the continuous improvement of BPs realized by services and for the development of service oriented systems from BPs, with automatic generation of service models from BP models.Las organizaciones se enfrentan en la actualidad a varios retos, siendo uno de los más importantes su capacidad para reaccionar rápidamente a los cambios ya sea en sus modelos de procesos de negocio (PN) o en el software que los implementa. Estos cambios pueden provenir de distintas fuentes: requisitos externos de socios o del mercado, o nuevos requisitos internos para la forma en que las cosas se llevan a cabo por los PNs definidos; también pueden surgir de las oportunidades de mejora detectadas para los PNs definidos, en base al monitoreo y evaluación de la ejecución de los PNs llevada a cabo por la organización, y/o sus socios y clientes. La creciente complejidad de los modelos de PNs y del software que los implementa, requiere que los cambios o las mejoras sean sopesados cuidadosamente contra el impacto que su introducción tendrá; también deben llevarse a cabo de manera sistemática para asegurar un desarrollo exitoso. Dos elementos son clave para proveer estos requisitos: la separación de la definición de los PNs de su implementación, para minimizar el impacto de los cambios de uno en otro, y un proceso para introducir los cambios o mejoras en los PNs y/o en el software que los implementa. La Gestión de Procesos de Negocio (Business Process Management, BPM) proporciona los medios para guiar y apoyar el modelado, implementación, despliegue, ejecución y evaluación de PNs en una organización, basado en el ciclo de vida de PNs. La realización de PNs con servicios proporciona la base para la separación de su definición de las tecnologías para implementarlos, y ayuda a proporcionar una mejor respuesta a los cambios en cualquiera de las capas definidas -definición e implementación de procesos de negocio- con un impacto mínimo sobre la otra. El modelado de PNs y servicios es un aspecto clave para apoyar esta visión, ayudando a proveer trazabilidad entre los elementos de un área a la otra, por lo tanto facilitando el análisis del impacto de los cambios, entre otras cosas. Los modelos han demostrado jugar un papel importante en el proceso de desarrollo de software, uno de sus usos principales en el contexto de la realización de PNs con servicios es el de diseñar servicios a un nivel más abstracto que con tecnologías específicas, promoviendo la reutilización separando la lógica de los servicios de su implementacion. MINERVA: Model drIveN & sErvice oRiented framework for the continuous business process improVement & relAted tools es el marco que se ha definido en este trabajo de tesis, que toma en cuenta todos los aspectos mencionados, en el cual los paradigmas de Computación Orientada a Servicios (Service Oriented Computing, SOC) y Desarrollo Dirigido por Modelos (Model Driven Development, MDD) se aplican a los PNs con foco en su mejora continua, extendiendo un ciclo de vida PN existente con actividades y elementos explícitos para la medición de la ejecución y mejora de PNs. El marco se compone de tres dimensiones: i) conceptual, que define los conceptos que se manejan en todo el marco. ii) metodológica, que define una metodología para el desarrollo orientado a servicios desde PNs, con generación automática de modelos de servicio en SoaML desde modelos en BPMN2, junto con un proceso de mejora continua basado en la medición de la ejecución de las ocurrencias de los PNs en la organización para llevar a cabo el esfuerzo de mejora. iii) soporte de herramientas para la propuesta completa basado en la integracion de varias herramientas existentes, junto con otras nuevas que hemos desarrollado. Las propuestas de MINERVA han sido validadas por medio de un experimento y dos casos de estudio realizados en el marco de proyectos reales en dos organizaciones, de los cuales, como resultado principal de las aplicaciones realizadas, se puede concluir que MINERVA puede ser una guía útil y clave para la mejora continua de PNs realizados por servicios y para el desarrollo de sistemas orientados a servicios desde PNs, con generación automática de modelos de servicio a partir de modelos de PN

Integrating Safety Assessment into the Design of Healthcare Service-Oriented Architectures

Most healthcare organisations are service-oriented, fundamentally centred on critical services provided by medical and nursing staff. Increasingly, these human-centric services rely on software-intensive systems, i.e. medical devices and health informatics, for improving different aspects of healthcare, e.g. enhancing efficiency through automation and patient safety through smart alarm systems. However, many healthcare services are categorised as high risk and as such it is vital to analyse the ways in which the software-based systems can contribute to unintentional harm and potentially compromise patient safety. This paper proposes an approach to modelling and analysing Service-Oriented Architectures (SOAs) used in healthcare, with emphasis on identifying and classifying potential hazardous behaviour. The paper also considers how the safety case for these SOAs can be developed in a modular manner. The approach is illustrated through a case study based on three services: ambulance, electronic health records and childbirth services

Service-Oriented Architectures for Safety-Critical Systems

Many organisations in the safety-critical domain are service-oriented, fundamentally centred on critical services provided by systems and operators. Increasingly, these services rely on software-intensive systems, e.g. medical health informatics and air traffic control, for improving the different aspects of industrial practice, e.g. enhancing efficiency through automation and safety through smart alarm systems. However, many services are categorised as high risk and as such it is vital to analyse the ways in which the software-based systems can contribute to unintentional harm and potentially compromise safety. This thesis defines an approach to modelling and analysing Service-Oriented Architectures (SOAs) used in the safety-critical domain, with emphasis on identifying and classifying potential hazardous behaviour. The approach also provides a systematic and reusable basis for defining how the safety case for these SOAs can be developed in a modular manner. The approach is tool-supported and is evaluated through two case studies, from the healthcare and oil and gas domains, and industrial review

BPMN4SOA : A service oriented process modelling language

Service oriented architectures have become very popular the last few years. The abstraction of computer systems into a service paradigm bring many new solutions, both for cross business processes to aid interoperability and the reuse of existing legacy systems in a new network centric world. In the wake of this, service modelling has become a part of OMGs Model Driven Architecture and new modelling languages that are based on past experience for the new paradigm are emerging. BPMN 2.0 and SoaML are the newest modelling standards from OMG that focus on service modelling. They provide different approaches to the service domain where BPMN 2.0 emphasise process modelling and SoaML emphasise service architecture modelling. BPMN4SOA is a language that extends the use of BPMN 2.0, and bring more emphasis on the service modelling capability of BPMN 2.0. It does this by means of role modelling to abstract the participants and service choreographies into reusable objects. BPMN4SOA also provide modelling capability for information data for messages through implementation of UML at L0 compliance. Because BPMN4SOA is an extension of BPMN 2.0 through it’s Extension and External Relationship constructions, BPMN4SOA should be implementable in all systems fully compliant with BPMN 2.0 specification

BplSoa: framework para el desarrollo de líneas de procesos de negocios orientadas a servicios

Las organizaciones actualmente para ser competitivas requieren de procesos de negocio automatizados y flexibles para responder rápidamente a los cambios emergentes del entorno. Esta demanda de procesos de negocio flexibles exige enfoques sistemáticos para facilitar la implementación de líneas de procesos de negocio que cubran eficaz y eficientemente las necesidades de las organizaciones y sus clientes. Dos factores clave en el diseño e implementación ágil de procesos de negocios son la reutilización y la productividad. En este trabajo se describe el modelo de proceso de software denominado BplSoa (Business Processes Lines based on SOA), el cual busca facilitar el desarrollo de procesos de negocio soportados en SOA (Service Oriented Architecture). BplSoa guía sistemáticamente la implementación de líneas de procesos de negocio haciendo énfasis en la productividad a través de MDD (Model Driven Development) y en la reutilización a través de la aplicación de los principios de SPL (Software Product Lines). El principal reto de BplSoa es la integración y armonización de los enfoques de MDD y SPL para facilitar el desarrollo de líneas de procesos de negocio orientadas a servicios.Abstract. Nowadays the organizations to be competitive require automated and flexible business processes to respond quickly to emerging changes in the environment. This demand for flexible business processes requires systematic approaches to facilitate the implementation of business processes lines that effectively and efficiently meet the needs of organizations and their customers. Two key factors in the design and implementation of agile business processes are re-use and productivity. This paper describes the software process model called BplSoa (Business Processes Lines based on SOA), which seeks to facilitate the development of business processes supported by SOA (Service Oriented Architecture). BplSoa systematically guide the implementation of business processes lines emphasizing productivity through MDD (Model Driven Development) and reuse through the application of the principles of SPL (Software Product Lines). The main challenge of BplSoa is the integration and harmonization of approaches to facilitate the development of business processes lines.Maestrí

General framework for service engineering analysis and design

The research produced a General Service Engineering Framework (GSEF), a process guideline for building a service system which covers both the business and informatics aspects. The framework also defines service engineering ontologi, which collects and specifies components of service engineering and its internal relations