Keywords:
Astract: Nowadays, an increasing amount of data is stored in the cloud. At the same time, companies start using mobile applications to operate and improve their business processes. However, mobile applications offered by the cloud-storage providers do not satisfy the needs of such companies. The following three problems have been identified which prevent the usage of these applications. First of all, the feature set of these applications is definite. Therefore, companies are not able to extend the applications to meet their requirements to handle their business processes. In addition, the applications do not enable the companies to apply their corporate identity on the user interface. And, finally, companies want to have control over the distribution of their applications and decide which users are allowed to download and use their applications. The different kinds of variability encountered result from the various requirements of each company. The solution for these problems is to systematically deal with variability in such applications. Therefore, this thesis applies concepts from product line engineering to the domain of mobile applications. Hence, this thesis defines a feature model corresponding to the users requirements. Furthermore, concepts and techniques have been developed for implementing variability mechanisms in Objective-C. Consequently, a software product line has been created using these developed tools and the corresponding feature model. This allows the efficient derivation of customized products based on the software product line. The resulting approach based on software product lines allows to create a flexible application which is extendable with custom modules and components requested by users. Through this customization and extension the application's features are adapted to the company's business processes.

Keywords:
Astract: Current business document standards, such as EDIFACT, are defined in an all-embracing manner and, thus, usually include several thousands of elements. This is due to the fact that a standardized document type represents a superset of all data elements required in any industry, in any geopolitical region, etc. Furthermore, standardized document types are defined as stand-alone documents, similar to paper-based documents, comprising all information from previous process steps. In other words, standardization neglects the notion of processes by repeating information in different documents of the same process. In this paper, we propose a methodology for assessing redundancies in business document exchanges and evaluate different real-world industry message implementation guidelines (MIGs) with respect to their efficiency in reducing complexity and redundancies. Insights on redundancies can help companies and standardization committees to improve designs of MIGs and entire EDI standards. Furthermore, one can use the concepts presented in this paper to compare different MIGs with regard to their (dis)similarities, which might be useful when two organizations are to be merged and their IT systems consolidated.

Keywords:
Astract: Business Process Management (BPM) has gained significant adoption in practice for enabling organizations to increase their effectiveness, efficiency, and flexibility. This broad adoption has not only been fostered by a rich and wellestablished theory to model, analyze, simulate, and enact business processes, but also by internationally accepted standards and mature technologies. Caused by the ever increasing speed and volatility of markets and the dynamics of new technologies, such as cloud infrastructures and mobile communications, we face a new generation of business processes, which we refer to as living inter-organizational processes. Such processes are not in control of one single organization; instead, they are enacted by multiple organizations, where no participating party possesses full control over the entire process. Such processes often involve a high number of actors that might even be unknown in advance. These actors require various degrees in participation, they are acting in heterogeneous environments. Moreover, such processes are often weakly structured or designed in an ad-hoc manner, and have to be continuously subject to evolution. Unfortunately, existing theories, methodologies, and technologies cannot cope with this challenging combination of aspects, which all have to be considered when dealing with living inter-organizational processes. The state of the art typically addresses singular aspects in isolation. However, a holistic approach to these challenges bears a tremendous potential. This paper aims to contribute towards a holistic approach to living inter-organizational processes. To this end, we describe different perspectives on inter-organizational processes and identify challenges for making them living processes.

Keywords:
Astract: One and the same inter-organizational business process - such as e-procurement - may be executed differently in different industries, geopolitical regions, etc. Thus, a standardized reference model for inter-organizational business process must be customized to the specific business context (industry, region, etc.). In order to share, search, and (partially) re-use context specific adaptations it is essential not only to store the adaptations, but also a business context model where these adaptations are valid. Therefore, we present our ontology based business context model and explain how it can be applied to generic models of semantically interoperable data blocks, so-called Core Components. Core Components are standardized by the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT), and their adaptations are exchanged between business partners in the course of inter-organizational business processes. If we could assign a business context to a business process, we could prevent negative trends in today's business, such as interoperability issues, inconsistencies and heterogeneous interpretations of the interchanged electronic business documents.

Keywords:
Astract: Today, business processes are modeled without taking into deeper consideration the context of the business environment where they will be later executed. As a consequence, initiation, management and delayed adjustments of business processes are demanding, time-consuming and very often impossible tasks. In this paper we summarize crucial advantages and disadvantages of different Context modeling approaches, and we define the Context related to the scope of the business environment particularly. If we could assign a Business Context to a business process, we could undermine negative trends in today's business, such as interoperability issues, inconsistencies and heterogeneous interpretations of different business processes.