An Institutional Framework for Heterogeneous Formal Development in UML

We present a framework for formal software development with UML. In contrast to previous approaches that equip UML with a formal semantics, we follow an institution based heterogeneous approach. This can express suitable formal semantics of the different UML diagram types directly, without the need to map everything to one specific formalism (let it be first-order logic or graph grammars). We show how different aspects of the formal development process can be coherently formalised, ranging from requirements over design and Hoare-style conditions on code to the implementation itself. The framework can be used to verify consistency of different UML diagrams both horizontally (e.g., consistency among various requirements) as well as vertically (e.g., correctness of design or implementation w.r.t. the requirements)

Hybrid process modelling within business process management projects

Business Process Management (BPM) is still an important research topic amongst both academics and businesses. The recent recession has forced businesses to focus on cost control and efficiency in order to better cope with the economic downturn. Many companies in this situation turn to BPM software as a means of improving their efficiency and costs by reducing aspects of the business such as process lead-times and material costs. In order to identify areas of the business and its processes which require changing the business will most likely adopt a method of modelling their business processes. Because of the large number of available techniques decision makers usually struggle to decide the best approach. Recent literature has also pointed out that prevalent modelling techniques are designed to serve one specific purpose and may not be capable of modelling the whole picture. The key relationship between the information systems and the human behaviour is one example of where existing techniques are biased towards opposite ends of the scale. This paper proposes the use of a hybrid modelling notation composed of multiple existing notations in order to bridge this. The hybrid notation was applied to a BPM project at a company in the construction industry and a case study conducted with its users

Value Chain: From iDMU to Shopfloor Documentation of Aeronautical Assemblies

Competition in the aerospace manufacturing companies has led them to continuously improve the efficiency of their processes from the conceptual phase to the start of production and during operation phase, providing services to clients. PLM (Product Lifecycle Management) is an end-to-end business solution which aims to provide an environment of information about the product and related processes available to the whole enterprise throughout the product’s lifecycle. Airbus designs and industrializes aircrafts using Concurrent Engineering methods since decades. The introduction of new PLM methods, procedures and tools, and the need to improve processes efficiency and reduce time-to-market, led Airbus to pursue the Collaborative Engineering method. Processes efficiency is also impacted by the variety of systems existing within Airbus. Interoperability rises as a solution to eliminate inefficiencies due to information exchange and transformations and it also provides a way to discover and reuse existing information. The ARIADNE project (Value chain: from iDMU to shopfloor documentation of aeronautical assemblies) was launched to support the industrialization process of an aerostructure by implementing the industrial Digital Mock-Up (iDMU) concept in a Collaborative Engineering framework. Interoperability becomes an important research workpackage in ARIADNE to exploit and reuse the information contained in the iDMU and to create the shop floor documentation. This paper presents the context, the conceptual approach, the methodology adopted and preliminary results of the project

An overview of Mirjam and WeaveC

In this chapter, we elaborate on the design of an industrial-strength aspectoriented programming language and weaver for large-scale software development. First, we present an analysis on the requirements of a general purpose aspect-oriented language that can handle crosscutting concerns in ASML software. We also outline a strategy on working with aspects in large-scale software development processes. In our design, we both re-use existing aspect-oriented language abstractions and propose new ones to address the issues that we identified in our analysis. The quality of the code ensured by the realized language and weaver has a positive impact both on maintenance effort and lead-time in the first line software development process. As evidence, we present a short evaluation of the language and weaver as applied today in the software development process of ASML