Skip to main content
ABSTRACT
ABSTRACT MD2 is a framework for cross-platform model-driven mobile development. It consists of a domain-specific language for describing business apps concisely and of generators that automatically create complete iOS and Android apps... more
ABSTRACT MD2 is a framework for cross-platform model-driven mobile development. It consists of a domain-specific language for describing business apps concisely and of generators that automatically create complete iOS and Android apps from this specification. Designers. MD2 has been created as a research prototype at the Department of Information Systems,University of Münster. Henning Heitkötter and Tim A. Majchrzak, both interested in cross-platform approaches and mobile applications in general, supervised the implementation, which was mainly carried out by master students Sören Evers, Klaus Fleerkötter, Daniel Kemper, Sandro Mesterheide, and Jannis Strodtkötter.
Many software developments projects fail due to quality problems. Software testing enables the creation of high quality software products. Since it is a cumbersome and expensive task, and often hard to manage, both its technical... more
Many software developments projects fail due to quality problems. Software testing enables the creation of high quality software products. Since it is a cumbersome and expensive task, and often hard to manage, both its technical background and its organizational implementation have to be well founded. We worked with regional companies that develop software in order to learn about their distinct weaknesses and strengths with regard to testing. Analyzing and comparing the strengths, we derived best practices. In this paper we explain the project's background and sketch the design science research methodology used. We then introduce a graphical categorization framework that helps companies in judging the applicability of recommendations. Eventually, we present details on five recommendations for tech-nical aspects of testing. For each recommendation we give im-plementation advice based on the categorization framework.
ABSTRACT Due to the heterogeneity of different platforms, it is an expensive endeavor to provide a mobile application (app) for several of them. Cross-platform development approaches can solve this problem. Existing cross-platform... more
ABSTRACT Due to the heterogeneity of different platforms, it is an expensive endeavor to provide a mobile application (app) for several of them. Cross-platform development approaches can solve this problem. Existing cross-platform approaches have severe limitations and typically work on a low-level of abstraction. Our model-driven cross-platform approach MD2 focuses on the domain of business apps and, hence, reaches a high-level of abstraction while maintaining a platform-specific look and feel. A textual model written in an MVC-based DSL is automatically transformed into native apps for Android and iOS. The present paper focuses on new extensions of MD2, namely device-specific layout, extended control structures, and offline computing.
Research Interests:
We propose a business rule management system that is used to optimize the dispatchment on a mass casualty incident. Using geospatial information from available ambulances and rescue helicopters, a business rule engine calculates an... more
We propose a business rule management system that is used to optimize the dispatchment on a mass casualty incident. Using geospatial information from available ambulances and rescue helicopters, a business rule engine calculates an optimized transportation plan for injured persons. It automatically considers special needs like ambulances equipped for baby transportation or special decontamination equipment, e.g. to deal with an accident in a chemical factory. The rules used in the system are not hardcoded; thus, it is possible to redefine them on the fly without changing the program's source code. It is possible to load and save a rule set in case of a catastrophe. Furthermore, it is possible to automatically recalculate an already planned operation if it becomes clear that the rescue vehicles assigned are needed by a person with life-threatening injuries.
ABSTRACT Only a few years after their advent, smartphones and tablets are now used routinely by many people. While this has been bolstered by the fast innovation cycles of the hardware, mobile devices become versatile due to the... more
ABSTRACT Only a few years after their advent, smartphones and tablets are now used routinely by many people. While this has been bolstered by the fast innovation cycles of the hardware, mobile devices become versatile due to the applications developed for them. These apps are increasingly used for business purposes. In a research project we investigated whether apps are interesting for all businesses, how and for which activities they plan to use apps, and what kinds of challenges and problems they perceive. To this end, we conducted an interview-based survey with regional companies. Thoroughly analyzing the transcripts enabled us to draw conclusions on the status quo of apps. In this article we present the results from the project, including a set of early best practices. We also discuss our findings to derive directions for future research.
Dieser Arbeitsbericht fasst die Beiträge des 16. Kolloquium 'Programmiersprachen und Grundlagen der Programmierung (KPS'11)' zusammen, das vom 26. bis 28. September 2011 auf Schloss Raesfeld im Münsterland in Deutschland... more
Dieser Arbeitsbericht fasst die Beiträge des 16. Kolloquium 'Programmiersprachen und Grundlagen der Programmierung (KPS'11)' zusammen, das vom 26. bis 28. September 2011 auf Schloss Raesfeld im Münsterland in Deutschland stattgefunden hat. -- This proceedings volume contains the work presented at the 16th Kolloquium 'Programmiersprachen und Grundlagen der Programmierung (KPS'11)' at Schloss Raesfeld, Münsterland, Germany from September 26th to 28th, 2011.
ABSTRACT Mobile applications usually need to be provided for more than one operating system. Developing native apps separately for each platform is a laborious and expensive undertaking. Hence, cross-platform approaches have emerged, most... more
ABSTRACT Mobile applications usually need to be provided for more than one operating system. Developing native apps separately for each platform is a laborious and expensive undertaking. Hence, cross-platform approaches have emerged, most of them based on Web technologies. While these enable developers to use a single code base for all platforms, resulting apps lack a native look & feel. This, however, is often desired by users and businesses. Furthermore, they have a low abstraction level. We propose MD2, an approach for model-driven cross-platform development of apps. With MD2, developers specify an app in a high-level (domain-specific) language designed for describing business apps succinctly. From this model, purely native apps for Android and iOS are automatically generated. MD2 was developed in close cooperation with industry partners and provides means to develop data-driven apps with a native look and feel. Apps can access the device hardware and interact with remote servers.
ABSTRACT Many software development projects fail to reach their goals or are aborted. This results in economic problems, lost welfare, and may even endanger humans. In many cases, an improper choice of the software development methodology... more
ABSTRACT Many software development projects fail to reach their goals or are aborted. This results in economic problems, lost welfare, and may even endanger humans. In many cases, an improper choice of the software development methodology (SDM)--or not following an ideology towards development at all--can be identified as the root problem. Choosing an adequate methodology is no trivial attempt, though. Conflicting aims of classical methodologies and agile approaches add further complexity. We identify common characteristics that can be found in each SDM and present a structured approach for classification. We also present a mapping to existing methodologies to underline the applicability of our approach. This helps to compare fundamental, integrated, and agile SDMs. Furthermore, we discuss our findings and highlight their implications for choosing an SDM. We thereby contribute to the theoretical body of knowledge and provide advice for businesses at the same time.

And 20 more