Annual Report 2010 - Fachgruppe Informatik an der RWTH Aachen ...

NEMO) takes place using the OPNET wireless simulator. The current work item is the
creation of test scenarios based on the requirements of Personal Area Networks (PANs) as
described in the IP Multimedia Subsystem (IMS) standardization [3GPP-22259]. Improving
the QoS in NEMO according to the requirements of IMS-PANs makes the application of such
networks using NEMO a more appealing alternative especially that it guarantees
interoperability between different brands because of the nativity of NEMO as an extension of
MIPv6.
UMIC: Software Quality Initiative
Dominik Franke, Carsten Weise, Mudassir Rasool
The growing complexity of applications, architectures, protocols and hardware in the mobile
world makes it increasingly more difficult to develop bug-free software for mobile
communication and information systems. The intention of the UMIC Quality Initiative is to
seek for methods that are applicable for mobile software to improve the quality of the software
engineering process and the quality of the products. This project aims at the development of
methods and tools for mobile development, as well as the identification and design of design
patterns and architectures for mobile applications, in order to improve the quality of the
mobile software. The first step towards this target is capturing the status quo and a clear
problem statement. This has already started in a pathfinder project for this Software Quality
Initiative project. Within the pathfinder project, it turned out that a quality model for mobile
software is basically non-existent, but is needed to clarify the problems, explain solutions, and
in the end also to measure the gains that come with the new methods and tools, design patterns
and architectures. To manage the special requirements of mobile software, one goal of this
UMIC Software Quality Initiative is to create design patterns and methods for improving
quality of massively distributed mobile software.
Another goal is the analysis and improvement of mobile application lifecycles. Since
lifecycles of mobile applications are stressed in a different way than lifecycles of desktop
applications (e.g. incoming calls or SMS) we use formal methods to analyze lifecycles of
different mobile platforms and to build tools that deal with lifecycles at development time.
The goal is to help developers to implement the lifecycle of their application correctly to
prevent data loss or inconsistencies during execution time. As a first step this topic is currently
investigated by a diploma thesis, in which we define a common model to express the different
lifecycles of different mobile platforms (Android, iOS, J2ME, …). Having a well-defined
clear model is the basis to build corresponding tools that can handle various mobile platforms.
366