Mobile Applications代写-Web Services代写

Semantic Sensor/Device/Event Description System

EEEM042-Mobile Applications and Web Services

Coursework- Spring Semester 2018

Mobile Applications代写 When a user clicks on the publish (or save) button the form element data will be read via a server-side program.

Main specification

− To create a web page (suitable for mobile platforms) for an online system that will be accessible via a URL (this can be a local host):

− For example: http://localhost/app/index.html

− The system will allow users to add/annotate sensor/device/events descriptions based on a simple model

(i.e. an ontology) and publish the descriptions in a semantic repository.

− Users will have access to a simple query interface that will supports simple queries based on device/sensor attributes.

Description model Mobile Applications代写

− You need to develop a simple device/sensor description model that includes attributes such as ID, Name, Location,Type, etc.

− The description model should be represented in XML and also at least one of OWL,RDF or JSON (or JSON-LD) formats.

Device/Sensor or Event Registration Page

− A user can access an online form to add the descriptions (in text or numerical form) or select possible options from a selection list.

− The form should be implemented using HTML FORM elements.

− When a user clicks on submit (register) button, the values from the HTML FORM elements will be transformed to an intermediary XML format.

A Sample Description Form

Intermediary XML Format

− When a user clicks on the publish (or save) button the form element data will be read via a server-side program.

−The program will read the form values,

−will create an XML or OWL/RDF/JSON file according to the description model that is designed in the first part,

−will store this XML document in an in-memory object or in a temporary storage.

−The intermediary XML document will include attribute name and values;

−e.g. <attribute_name>value</attribute_name>

A Sample Intermediary XML Form

Transforming intermediary XMl Document to the description model format

− The next step after creating intermediary XML document will be using XSLT to transform the XML document to a description format according to the description model that you have designed in the first step.

− For this you will need to:

−Design a suitable XSL template

−Use a server-side program to run XSLT transformation method to transform the intermediary XML document tothe form of your description model (it can still be XML or it can be an OWL/RDF/JSON document or any other suitable representation form).

A Sample Representation of description data in RDF form

Simple Query Interface

− After creating the description format according your model,you can store the document as a file.

− The next, and final step, will be providing a simple interface that users can run queries.

− The query interface can directly support at least one of XPath or SPARQL or JSON query languages.

A Sample Query Interface

Required Pages

− You need to develop at least the following web pages:

−Device/Sensor/Event Description Page (The optimised HTML design for mobile platforms, layout and style design are important).

−Confirmation page: to acknowledge storing the description and to show the representation (you need to consider navigation, layout and ease of access to the options in your system).

−A simple query from (the query form should provide at least one query template – sample- and allow a user to write and submit other queries).

Implementation

− The outcome will be a web-based system, optimised for mobile browsers and mobile platforms.

− You do not need to add/implement security features (secure connection,…).

− You can use .NET, J2EE, Python, Node.JS or any other suitable technologies to implement the system.

Requirements Mobile Applications代写

− For this project you need to use a development IDE (e.g. Eclipse, NetBeans) and a run-time environment – depending on the development technology – (e.g. Apache Tomcat).

− If you plan to use Java/J2EE, here are some useful links:

−Eclipse (http://www.eclipse.org/)

−NetBeans (http://netbeans.org/)

Some related technologies/components

− If you plan to use use Java and RDF data: you can use Jena or Sesame to handle RDF data

−http://jena.apache.org/

−http://www.openrdf.org/

−You can use Apache Tomcat (if you are using Java) to host your application

−http://tomcat.apache.org/16

Web Service Support

− It is recommended that you implement a Web Service to provide access to some of the functionalities of your code(e.g. a query API as a web service).

− If you implement a web service, this will be considered as a complete advance feature (please check the marking scheme).

Project submission Mobile Applications代写

− The source files and a running version.

− A brief report (maximum 5 pages)- The report should include the main design (UML or illustration diagrams), describe the key features and provide an overview of the technologies used in the system.

− No need for code documentation but the modularity,flexibility and readability of your code is important.

− Marking will be based on the submitted documents and code and an interview.

Marking Criteria

− Correct functionality

− Code and program design

− User interface

− Implemented features

− Design Decisions

− System Explanation

− The complete marking scheme and Feedback form is available on SurreyLearn (Assignment Section).

Marking Scheme Mobile Applications代写

− User interface design (10%)

− Suitability for mobile devices, use of style-sheets, readability and overall presentation

− Usability of the system (10%)

− Menu, page navigation, ease of use and clarity of the forms and buttons.

− Correct functionality (35%)

− Ability to publish data, correct XML and RDF or JSON data and ability of query the published data for multiple published items;

− Explanation of choices made in design and system presentation (25%)

− Being able to describe the components of the system, quality of the report and effectives choices suitable for mobile environments in developing the system

− Advance features (20%)

− Innovation and adding novel features, e.g. web service implementation

When?

− Staring date:

Monday, 5 February, 2018.

− Submission deadline:

Tuesday, 8 May, 4:00pm.

Sample Code Mobile Applications代写

− A running sample is available at:

− On Campus:

−http://iot1.ee.surrey.ac.uk/MAWS/index.jsp

− Off Campus:

−http://iot.ee.surrey.ac.uk/MAWS/index.jsp

− A run-time bundle is available at:

− http://personal.ee.surrey.ac.uk/Personal/P.Barnaghi/teaching/EEEM042/MAWS.war

− You can directly deploy it on a Tomcat server and it should work.

− The source code in Java:

− http://personal.ee.surrey.ac.uk/Personal/P.Barnaghi/teaching/EEEM042/MAWS.zip

Important notes

− Please note that there are some issues with the given sample code that you need to fix it (if you decide to use the given sample):

− The sample code includes some logical errors in the code (e.g. it overwrites the previously published data).

− It does not support publishing events (e.g. if someone wants to report an event).

− The page is not tested for mobile browsers (you should test/fix it).

− The webpages do not have any stylesheet or style formatting.

− The system is developed as a web application and not a web service.

− The web service implantation (at least for some parts) will be considered a complete advance feature.

合作平台：essay代写论文代写写手招聘英国留学生代写