MobDSL: A Domain Specific Language for multiple mobile platform deployment

D Kramer, T Clark, S Oussena

Research output: Chapter in Book/Report/Conference proceedingConference publication

Abstract

There is increasing interest in establishing a presence in the mobile application market, with platforms including Apple iPhone, Google Android and Microsoft Windows Mobile. Because of the differences in platform languages, frameworks, and device hardware, development of an application for more than one platform can be a difficult task. In this paper we address this problem by the creation of a mobile Domain Specific Language (DSL). Domain analysis was carried out using two case studies, inferring basic requirements of the language. The paper further introduces the language calculus definition and provides discussion how it fits the domain analysis, and any issues found in our approach.
Original languageEnglish
Title of host publication2010 IEEE International Conference on Networked Embedded Systems for Enterprise Applications (NESEA)
PublisherIEEE
Pages1-7
ISBN (Electronic)978-1-4244-9177-3
ISBN (Print)978-1-4244-9178-0
DOIs
Publication statusPublished - 30 Dec 2010
Event2010 IEEE International Conference on Networked Embedded Systems for Enterprise Applications (NESEA 2010) - Suzhou
Duration: 25 Nov 201026 Nov 2010

Conference

Conference2010 IEEE International Conference on Networked Embedded Systems for Enterprise Applications (NESEA 2010)
Period25/11/1026/11/10

Bibliographical note

© 2010 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.

Fingerprint Dive into the research topics of 'MobDSL: A Domain Specific Language for multiple mobile platform deployment'. Together they form a unique fingerprint.

Cite this