Module Descriptors
MOBILE APPLICATIONS DEVELOPMENT
COSE70628
Key Facts
Faculty of Computing, Engineering and Sciences
Level 7
15 credits
Contact
Leader: Nicholas Shulver
Hours of Study
Scheduled Learning and Teaching Activities: 36
Independent Study Hours: 114
Total Learning Hours: 150
Assessment
  • ASSIGNMENT weighted at 70%
  • CLASS-TEST weighted at 30%
Module Details
Module Indicative Content
Applications programming and development for mobile devices.
A critical study of key application areas for which mobile computing provides a supporting infrastructure.
Key mobile computing technologies.
Design issues for mobile systems.
Database issues in mobile computing.
Mobile Systems integration.
Review trends and developments in mobile technology.
Module Additional Assessment Details
Coursework (design and staged development of an interactive software application) - 70% (assessing Learning outcome 1 and 2)
Test 1 hour (time contrained practical) - 30% (assessing Learning outcomes 1 and 3)
Module Learning Strategies
The material will be presented through a combination of lectures, practical exercises, tutorials and directed and self-study as appropriate for each topic. Where appropriate, Virtual Learning Environments will be used as part of the delivery. Delivery will be 1 lecture and 2 practicals/tutorials per week.
(1:n) (1:20)2
Module Special Admissions Requirements
Knowledge of either Java, C++ and/or C# is required
Module Texts
Mobile Applications Architecture, Design and Development, Valentino Lee et al., Hewlett-Packard professional books, Prentice Hall, 2004, ISBN/ISSN: 0131172638

Website: http://developer.android.com
Learning Android, Marko Gargentia, O'Reilly Media, April 2011, ISBN: 978-1-4493-9050-1
Hello Android, Ed Burnette, Pragmatic Bookshelf, July 2010, ISBN: 978-1-934356-56-2 or equivalent texts for alternative Mobile Operating Systems
Module Resources
Access to the library, journals and web-based resources.
Appropriate mobile software development kits/environments, e.g. Eclipse IDE with Android plug-ins and SDK.
At least one physical device available per lab session.