Model-Driven Development of Mobile Information Systems

Model-Driven Development of Mobile Information Systems

Ralf Bruns (Hannover University of Applied Sciences and Arts, Germany) and Jürgen Dunkel (Hannover University of Applied Sciences and Arts, Germany)
DOI: 10.4018/978-1-4666-4301-7.ch013
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

Significant improvements in the development of business applications for mobile devices have been made in recent years. However, the state of the art in software development is for mobile computing still not as mature as it is for conventional information systems on desktop computers. Therefore, declarative and code generation approaches should be preferred instead of manually coding. In the BAMOS project an architecture has been designed and implemented for the generic and flexible development of mobile information systems. The architecture is based on the declarative description of the available services and enables the access to service-oriented architecture (SOA) systems for mobile devices. In this chapter, the authors present a model-driven approach for generating almost the complete source code of mobile services. By applying model-driven development, a new service can be conveniently modeled with a graphical modeling tool and the graphical models are then used to generate the corresponding XML descriptions of the mobile user interface and the workflow specification. In order to use such a service no specific source code has to be implemented on the mobile device. In addition, an alternative modeling approach based on a textual representation of the models using a formal grammar expressed in EBNF is presented.
Chapter Preview
Top

Architecture Of Mobile Applications

An indispensable prerequisite for applying model-driven development is a powerful architectural base providing the target platform for code generation. The BAMOS platform enables the development of mobile applications by providing two software components. The first component is a so-called Adhoc Client that – similar to a Web browser – enables the mobile device to access information services in spontaneous networks. The second component is a so-called Service Broker that – similar to a Web Server – serves as an interface between the Adhoc Client and the services available in the network.

With the BAMOS platform a mobile device can use different services in diverse local networks. The Adhoc Client is a generic software component that does not require any information about the specific services. It loads the declarative descriptions of the services at run-time and generates a service-specific graphical user interface. The core concept underlying this generic approach is the declarative description of the process flow as well as of the graphical user interface.

Complete Chapter List

Search this Book:
Reset