MOBILE APPLICATIONS AND WEB SERVICES - 2020/1

Module Overview

Expected prior learning:  Basic knowledge of object-oriented design and C++.  Knowledge of Java, of scripting languages, or equivalent technologies would be helpful. Having attended EEEM048 – Internet of Things will put the techniques learned in this module into a wider application context.




Module purpose:  Communication, information and entertainment applications are increasingly integrated; classical telecommunications companies become intertwined with IT service as well as media and content providers. At the same time services conceptualized for the world wide web are being adapted for mobile devices and both wired and wireless sensors. To enable this mobile provision of complex services, different approaches to service and application development are needed. Applications must be able to handle mobile connectivity, and they need to be able to access and filter data and content obtained from a variety of sources to facilitate the inclusion of mobile devices, actuators and sensors as integral part of the semantic Web. The course is an introduction to core technologies for designing and building state of the art services and applications for mobile Web environments.





 

Module provider

Electrical and Electronic Engineering

Module Leader

BARNAGHI Payam (Elec Elec En)

Number of Credits: 15

ECTS Credits: 7.5

Framework: FHEQ Level 7

Module cap (Maximum number of students): N/A

Module Availability

Semester 2

Prerequisites / Co-requisites

None.

Module content

• Introduction to the course and to the state of the art in technology applicable to design of service-oriented mobile applications


• XML: syntax, tools, applications


• XSLT, XML applications (examples of use both in Web and mobile environments)


• RDF/S: syntax, semantics, tools, applications (examples of use both in Web and mobile environments)


• OWL: syntax, semantics, tools, applications (examples of use both in Web and mobile/sensor network environments)


• Web Services, implications on mobile environments


• WSDL, SOAP, UDDI, platforms for mobile services


• Semantic Web services, connected services


• Cloud provision, Mobile Cloud and Data mining techniques

 

Assessment pattern

Alternative Assessment

Not applicable: students failing a unit of assessment resit the assessment in its original format.

Assessment Strategy

The assessment strategy for this module is designed to provide students with the opportunity to demonstrate the following.

 

The written examination will assess the knowledge, concepts and theory of key technologies, common languages, and relevant techniques in the Web Services and Mobile Web Services and Applications area. It will assess the students’ ability to analyse problems and apply common solutions and techniques to solve different uses-case scenarios in this domain. The Assignment will assess the ability to design a complete mobile Web Service using common technology and will evaluate the students’ ability to critically analyse existing work, i.e. existing examples

 

Thus, the summative assessment for this module consists of the following.

• 2 hours closed book written examination


• An assignment involving one programming exercise (including provider, client and service modules) and documentation in form of a presentation (due in Week 10).
  
  
  
  • The programming exercise comprises development of a basic mobile Web Service and implementing a series of User interfaces to a) provide and b) consume the data associate to the service. 
  
  
  • The documentation, to be submitted in the form of powerpoint presentation (a template will be provided) will describe the design choices and approach in detail and will provide information about the implementation approach and technologies chosen.
  
  
  
  

 

Any deadline given here is indicative. For confirmation of exact date and time, please check the Departmental assessment calendar issued to you.

 

Formative assessment and feedback

For the module, students will receive formative assessment/feedback in the following ways.

• During lectures, by question and answer sessions


• During tutorials/tutorial classes


• By means of unassessed tutorial problem sheets (with answers/model solutions)


• During supervised computer laboratory sessions


• Via the marking of written reports


• Via assessed coursework

Module aims

• to introduce the basic principles and technologies of and for mobile Web service development, to discuss Web service development and how they are building into and are integrated in distributed mobile and Web applications.
• introduce the mechanisms for representing, manipulating and querying structured data (XML) and semantic data (RDF/S, OWL), it also includes data mining techniques and the concept of connected services. Related toolkits and applications and their use will be learned.

Learning outcomes

Methods of Teaching / Learning

The learning and teaching strategy is designed to achieve the following aims.

This module is designed to provide current knowledge of concepts and technologies that will enhance and extend the students’ theoretical and practical skills in the related areas and will also improve their skills in systems analysis and system design.  This will be achieved through lectures and classroom practices as well as group discussions that are designed to convey and provide fundamental knowledge of the technology area. The lectures cover a range of available technologies, methods and principles, investigate use cases and common practices. Students will be able to learn the fundamental concepts and how solutions can be designed to solve related problems or how they can be adapted into related areas. Practical sessions will be conducted as lab experiments and will be complimented by a coursework assignment. The coursework comprises a programming assignment and also writing a report. Students will be expected to not only investigate the relevant literature and discuss it in a report, but also to learn practical skills and develop a basic system and demonstrate it.

Learning and teaching methods include the following.

• Lectures to provide knowledge about the basic and required technologies (3 hours lecture per week x 10 weeks)


• Class discussions to encourage interaction and partcipation (this will be a part of the activities during the lectures)


• Seminar to present and discuss the assignment approach and practical work (3 hours)


• Programming self-study and discussion (3 hours per week x 10 weeks)

 





 

Indicated Lecture Hours (which may also include seminars, tutorials, workshops and other contact time) are approximate and may include in-class tests where one or more of these are an assessment on the module. In-class tests are scheduled/organised separately to taught content and will be published on to student personal timetables, where they apply to taken modules, as soon as they are finalised by central administration. This will usually be after the initial publication of the teaching timetable for the relevant semester.

Reading list

https://readinglists.surrey.ac.uk
Upon accessing the reading list, please search for the module using the module code: EEEM042

Please note that the information detailed within this record is accurate at the time of publishing and may be subject to change. This record contains information for the most up to date version of the programme / module for the 2020/1 academic year.