<br><font size=2 face="sans-serif">Call for Papers</font>
<br>
<br><font size=2 face="sans-serif">The Second International Workshop on
Software Development Lifecycle for Mobile (DeMobile 2014)</font>
<br><font size=2 face="sans-serif"> </font><a href=http://sysrun.haifa.il.ibm.com/hrl/demobile2014/index.shtml><font size=2 color=blue face="sans-serif">http://sysrun.haifa.il.ibm.com/hrl/demobile2014/index.shtml</font></a>
<br><font size=2 face="sans-serif">Nov 17, 2014</font>
<br><font size=2 face="sans-serif">Hong Kong </font>
<br><font size=2 face="sans-serif">Co-located with FSE </font><a href=http://fse22.gatech.edu/><font size=2 color=blue face="sans-serif">http://fse22.gatech.edu</font></a>
<br>
<br><font size=2 face="sans-serif">Our excellent keynotes will be given
by</font>
<br><font size=2 face="sans-serif">Yannick Pellet Vice President of the
Advanced Software Platform Lab at Samsung Research America </font>
<br><font size=2 face="sans-serif">Greg Truty, IBM Distinguished Engineer
and Chief Architect, IBM Mobile Platform, IBM Software Group </font>
<br>
<br><font size=2 face="sans-serif">Mobile application usage and development
is experiencing exponential growth. According to Gartner, by 2016 more
than 300 billion applications will be downloaded annually. The mobile domain
presents new challenges to software engineering1. Mobile platforms are
rapidly changing, including diverse capabilities as GPS, sensors, and input
modes. Applications must be omni-channel and work on all platforms. </font>
<br><font size=2 face="sans-serif">Activated on mobile platforms, modern
applications must be elastic and scale on demand according to the hardware
abilities. Applications often need to support and use third-party services.
Therefore, during development, security and authorization processes for
the dataflow must be applied. Bring your own device (BYOD) policies bring
new security data leaks challenges. </font>
<br><font size=2 face="sans-serif">Developing such applications requires
suitable practices and tools e.g., architecture techniques that relate
to the complexity at hand; improved refactoring tools for hybrid applications
using dynamic languages and polyglot development and applications; and
testing techniques for applications that run on different devices.</font>
<br><font size=2 face="sans-serif">This workshop aims at establishing a
community of researchers and practitioners to share their work and lead
further research in the mobile development area.</font>
<br>
<br><font size=2 face="sans-serif">Goal of the Workshop</font>
<br><font size=2 face="sans-serif">The workshop has several goals. First,
we want to develop and create a vibrant research community of researchers
and practitioners for sharing work and leading further research in the
area of mobile software development. Second, we want to identify the most
important research problems in the mobile application development space.</font>
<br><font size=2 face="sans-serif">The workshop also has a set of specific
technical goals:</font>
<br><font size=2 face="sans-serif">* Investigating new directions of model-driven
development in the context of mobile software development </font>
<br><font size=2 face="sans-serif">* Examining the lifecycle of mobile
software development and how it relates to the software engineering lifecycle</font>
<br><font size=2 face="sans-serif">* Exploring and evaluating existing
techniques, patterns, and best practices of mobile software development</font>
<br><font size=2 face="sans-serif">* Bringing together people from both
academia and industry to talk and learn about real-world problems facing
mobile software engineering</font>
<br>
<br><font size=2 face="sans-serif">Topics</font>
<br><font size=2 face="sans-serif">The topics include, but are not limited
to:</font>
<br><font size=2 face="sans-serif">* Mobile development environments and
tools</font>
<br><font size=2 face="sans-serif">* Mobile testing</font>
<br><font size=2 face="sans-serif">* Agile development for mobile applications</font>
<br><font size=2 face="sans-serif">* Empirical studies and metrics</font>
<br><font size=2 face="sans-serif">* Maintenance and evolution</font>
<br><font size=2 face="sans-serif">* Mobile patterns, frameworks, and product
lines</font>
<br><font size=2 face="sans-serif">* Mobile software refactoring, restructuring,
and renovation</font>
<br><font size=2 face="sans-serif">* Mobile program transformation and
optimization</font>
<br><font size=2 face="sans-serif">* Practice and experience reports</font>
<br><font size=2 face="sans-serif">* Management of mobile applications</font>
<br><font size=2 face="sans-serif">* User experience of mobile applications
</font>
<br><font size=2 face="sans-serif">* Hybrid versus native applications</font>
<br><font size=2 face="sans-serif">* Model-driven development for mobile
</font>
<br><font size=2 face="sans-serif">* Application security</font>
<br><font size=2 face="sans-serif">* Mobile operating system and middleware
security</font>
<br><font size=2 face="sans-serif">* Secure application development methodologies
</font>
<br><font size=2 face="sans-serif">* Cloud support for mobile security</font>
<br><font size=2 face="sans-serif">* Static and dynamic analysis of mobile
applications</font>
<br><font size=2 face="sans-serif">* Mobile optimization debugging techniques
and tools</font>
<br><font size=2 face="sans-serif">* Research challenges in mobile software
engineering</font>
<br>
<br><font size=2 face="sans-serif">Submission Guidelines</font>
<br><font size=2 face="sans-serif">We solicit contributions of three types:
</font>
<br><font size=2 face="sans-serif">1. Research papers up to 8 pages that
describe original work in the area of mobile software engineering. Since
we wish to create a vibrant significant community, we will not have official
proceedings thus accepted authors will be able to submit their work to
other venues. </font>
<br><font size=2 face="sans-serif">2. Short papers up to 4 pages of emerging
ideas and on research in progress. </font>
<br><font size=2 face="sans-serif">3. Extended abstracts up to 2 pages
on in-practice experience. </font>
<br>
<br><font size=2 face="sans-serif">Your paper must conform to the ACM
format (</font><a href="http://www.acm.org/sigs/publications/proceedings-templates"><font size=2 color=blue face="sans-serif">http://www.acm.org/sigs/publications/proceedings-templates</font></a><font size=2 face="sans-serif">).
Submit your paper in Adobe PDF via EasyChair </font>
<br><font size=2 face="sans-serif">(</font><a href="https://www.easychair.org/conferences/?conf=demobile14"><font size=2 color=blue face="sans-serif">https://www.easychair.org/conferences/?conf=demobile14</font></a><font size=2 face="sans-serif">
).</font>
<br>
<br>
<br><font size=2 face="sans-serif">Important dates </font>
<br><font size=2 face="sans-serif">* Paper submission: July 1, 2014</font>
<br><font size=2 face="sans-serif">* Notification of acceptance: August
3th, 2014</font>
<br><font size=2 face="sans-serif">* Camera-ready submission: August 15,
2014</font>
<br>
<br>