Interaction-driven definition of e-business processes

Business-to-business interaction (B2Bi) is the next step for corporate IT [1]. Business relationships become increasingly dynamic, and new requirements emerge for data and process management. Standardisation initiatives are successfully targeting business ontology [4]. Still, business agility mainly depends on the flexibility of the business processes of a company. In the B2B space, traditional approaches to process modelling and management are inadequate. Today more than ever, traditional workflow management is crucial for the internal effectiveness of a company. Internal efficiency is a prerequisite for external agility. From both a technical and a business perspective, internal workflow management relies on specific assumptions in terms of resources involved in the process, as well as the process itself [2]. Level of control, availability, reliability, and cost stability are parameters that traditional process models and technology can almost take for granted. A single authority ruling on the process definition and the total control over process execution are also basic concepts for internal workflows. From a business perspective, a big upfront investment is put in the complete definition of process specifications. A different conceptual framework is required for the definition and management of e-business processes [3, 5]. The intrinsic capability to adapt to rapidly changing business requirements becomes crucial. The line of research explored in this paper derives from an approach to process modelling and management that explicitly targets the peculiarities and dynamics of B2Bi. In the model we propose, the upfront specification of the interaction logic of a company can be limited to partially specified processes and basic interaction rules. Specific information is then gathered from the observation of actual instances of business interaction, and used to refine and extend the initial model. In addition to the enforcement of explicit business requirement, the goal is to capture and leverage implicit operational knowledge. In the following sections, we present an overview of the methodology we are currently experimenting with for the inference of complex processes from business interaction flows. For our initial experiments, we focus on business messages compliant with the RosettaNet standard [4]

Model-driven design, simulation and implementation of service compositions in COSMO

The success of software development projects to a large extent depends on the quality of the models that are produced in the development process, which in turn depends on the conceptual and practical support that is available for modelling, design and analysis. This paper focuses on model-driven support for service-oriented software development. In particular, it addresses how services and compositions of services can be designed, simulated and implemented. The support presented is part of a larger framework, called COSMO (COnceptual Service MOdelling). Whereas in previous work we reported on the conceptual support provided by COSMO, in this paper we proceed with a discussion of the practical support that has been developed. We show how reference models (model types) and guidelines (design steps) can be iteratively applied to design service compositions at a platform independent level and discuss what tool support is available for the design and analysis during this phase. Next, we present some techniques to transform a platform independent service composition model to an implementation in terms of BPEL and WSDL. We use the mediation scenario of the SWS challenge (concerning the establishment of a purchase order between two companies) to illustrate our application of the COSMO framework

Embedding Requirements within the Model Driven Architecture

The Model Driven Architecture (MDA) brings benefits to software development, among them the potential for connecting software models with the business domain. This paper focuses on the upstream or Computation Independent Model (CIM) phase of the MDA. Our contention is that, whilst there are many models and notations available within the CIM Phase, those that are currently popular and supported by the Object Management Group (OMG), may not be the most useful notations for business analysts nor sufficient to fully support software requirements and specification. Therefore, with specific emphasis on the value of the Business Process Modelling Notation (BPMN) for business analysts, this paper provides an example of a typical CIM approach before describing an approach which incorporates specific requirements techniques. A framework extension to the MDA is then introduced; which embeds requirements and specification within the CIM, thus further enhancing the utility of MDA by providing a more complete method for business analysis

Ontology-based patterns for the integration of business processes and enterprise application architectures

Increasingly, enterprises are using Service-Oriented Architecture (SOA) as an approach to Enterprise Application Integration (EAI). SOA has the potential to bridge the gap between business and technology and to improve the reuse of existing applications and the interoperability with new ones. In addition to service architecture descriptions, architecture abstractions like patterns and styles capture design knowledge and allow the reuse of successfully applied designs, thus improving the quality of software. Knowledge gained from integration projects can be captured to build a repository of semantically enriched, experience-based solutions. Business patterns identify the interaction and structure between users, business processes, and data. Specific integration and composition patterns at a more technical level address enterprise application integration and capture reliable architecture solutions. We use an ontology-based approach to capture architecture and process patterns. Ontology techniques for pattern definition, extension and composition are developed and their applicability in business process-driven application integration is demonstrated

Principles for aerospace manufacturing engineering in integrated new product introduction

This article investigates the value-adding practices of Manufacturing Engineering for integrated New Product Introduction. A model representing how current practices align to support lean integration in Manufacturing Engineering has been defined. The results are used to identify a novel set of guiding principles for integrated Manufacturing Engineering. These are as follows: (1) use a data-driven process, (2) build from core capabilities, (3) develop the standard, (4) deliver through responsive processes and (5) align cross-functional and customer requirements. The investigation used a mixed-method approach. This comprises case studies to identify current practice and a survey to understand implementation in a sample of component development projects within a major aerospace manufacturer. The research contribution is an illustration of aerospace Manufacturing Engineering practices for New Product Introduction. The conclusions will be used to indicate new priorities for New Product Introduction and the cross-functional interactions to support flawless and innovative New Product Introduction. The final principles have been validated through a series of consultations with experts in the sponsoring company to ensure that correct and relevant content has been defined

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

WEB service interfaces for inter-organisational business processes an infrastructure for automated reconciliation

For the majority of front-end e-business systems, the assumption of a coherent and homogeneous set of interfaces is highly unrealistic. Problems start in the back-end, with systems characterised by a heterogeneous mix of applications and business processes. Integration can be complex and expensive, as systems evolve more in accordance with business needs than with technical architectures. E-business systems are faced with the challenge to give a coherent image of a diversified reality. Web services make business interfaces more efficient, but effectiveness is a business requirement of at least comparable importance. We propose a technique for automatic reconciliation of the Web service interfaces involved in inter-organisational business processes. The working assumption is that the Web service front-end of each company is represented by a set of WSDL and WSCL interfaces. The result of our reconciliation method is a common interface that all the parties can effectively enforce. Indications are also given on ways to adapt individual interfaces to the common one. The technique was embodied in a prototype that we also present

Applying MDE tools to defining domain specific languages for model management

In the model driven engineering (MDE), modeling languages play a central role. They range from the most generic languages such as UML, to more individual ones, called domain-specific modeling languages (DSML). These languages are used to create and manage models and must accompany them throughout their life cycle and evolution. In this paper we propose a domain-specific language for model management, to facilitate the user's task, developed with techniques and tools used in the MDE paradigm.Fil: Pérez, Gabriela. Universidad Nacional de la Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; ArgentinaFil: Irazábal, Jerónimo. Universidad Nacional de la Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentina. Consejo Nacional de Investigaciones Científicas y Técnicas; ArgentinaFil: Pons, Claudia Fabiana. Universidad Nacional de la Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentina. Provincia de Buenos Aires. Gobernación. Comisión de Investigaciones Científicas; ArgentinaFil: Giandini, Roxana Silvia. Universidad Nacional de la Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentin

Knowledge-Intensive Processes: Characteristics, Requirements and Analysis of Contemporary Approaches

Engineering of knowledge-intensive processes (KiPs) is far from being mastered, since they are genuinely knowledge- and data-centric, and require substantial flexibility, at both design- and run-time. In this work, starting from a scientific literature analysis in the area of KiPs and from three real-world domains and application scenarios, we provide a precise characterization of KiPs. Furthermore, we devise some general requirements related to KiPs management and execution. Such requirements contribute to the definition of an evaluation framework to assess current system support for KiPs. To this end, we present a critical analysis on a number of existing process-oriented approaches by discussing their efficacy against the requirements