ISYS40151 Mobile Interactive application and Report

{`MODULE CODE  	: 	ISYS40151 
MODULE TITLE   	: 	Mobile Interactive Systems 
TITLE 	 	: 	Mobile Interactive application & Report 
`}

I. Assessment Requirements

• An electronic copy of your zipped Android project file.
• A separate document containing all of the java code, in either word or PDF format. This should be submitted as a separate document, NOT within a zip file.
• A report (in word or pdf format) should be submitted as a separate document, NOT within a zip file.

The report must be 7 pages long (font to be used is verdana, 11 point). If you include either a front cover sheet, list of tables, or reference / bibliography pages these will not count towards the size of the report. Only pages dedicated to the following sections will count towards the 8 page limit:

1. Introduction and background (1page)

2. Design(2pages):
   1. The problem statement as to what your application is intending to achieve.
   2. What key features your applications going to provide including those that go beyond what was asked for in the scenario.
   3. The design of what your system is going to do through the use of flow charts or pseudo code detailing the complexity of the application (i.e. the technical features that you will be implementing). You are required to explain your decisions for your choices in your design.
   4. How you intend to test the application to make sure it works correctly. You must describe a number of tests and determine what the outcome of the tests will be (e.g. using one of android testing methods). These tests will then be used to show that your system is working correctly in section 3.

3. Implementation (2pages):
   1. You are required to describe your implementation. To do this, short listings of code can be included within this section but the code must be fully described and you must justify why it should be discussed. The description must detail the features and complexity that you encountered when writing the code (for example what problems you encountered and how you solved them).
4. Testing (1page, organised in a table):
   1. You must discuss and detail how the application satisfies the testing procedure described in section 1. This requires you to show, by referencing from section:
   2. What the test is ii. The expected result iii. The actual result
5. Critique (one page):

What worked and didn’t work and what could have been done to make it better.

II. Assessment Scenario/Problem

You will design and implement a program using Java on Android platform and based on an idea proposed by you and agreed with the lab tutor.

During week five, two hours interactive session will be dedicated to brainstorming and generation of ideas using examples from previously developed applications and research projects. By the end of week 5. Project proposals should be submitted to DropBox, with a brief description of the application goals, contents and requirements. Also the tutor will present some seed ideas and will make some phones, sensors, tags, electronic and wireless components available for this session. This session will take place in a one of our new group focused teaching room.

Each project should have at least two interactive mobile development features, here are some features which you can choose from:

• Graphics: writing interactive graphics applications with fast and smooth animation for applications such as games.
• Drawing, or access to camera.
• Connecting and populating a database.
• Utilising sensor inputs: audio, camera, gesture, motion (tilt, accelerometer).
• Location-based applications, GPS, CellID or WIFI. And integration with mapping services such as Google maps Localization and mapping using GPS,
• Wireless connectivity: it could be Bluetooth, NFC or WIFI or connection.
• Handling audio and video.

You could also suggest other interactive features for your project, the selection of the two features has to be agreed with the tutor.

The application can be developed for Android phones, smart watches, VR systems or/and Google Glasses.

The application must be demonstrated on a real Android device. Demonstration based on the emulator will not be accepted.

A compulsory demo for each student based on submission will take place during the next tutorial session after the submission. Failure to turn up in the demo will result in awarding only 30% of the marks achieved for the submission.

It is the responsibility of each student to make sure that during the demo the code runs properly in the lab used during the demo, i.e. you should make sure in advance (allow enough time before the demo day) that everything is running properly in the machine you will be using. If you developed code at your home computer, it is your responsibility that you port it to the lab in advance, before the demo. Marks will be awarded based on the demo and excuses of the type “it used to run - don’t know what happened since last time” will not be accepted.

Make sure you backup your work all the time.

Note that Dropbox will allow to make a submission multiple times. Make sure before submitting, that all the files you want to submit are contained there (or in the zip file you submit).

In the case of more than one submissions, only your last submission before the deadline given to you will be marked, so make sure that all the files are included in the last submission attempt and the last attempt is before the coursework deadline.

III. Assessment Criteria

1. Feedback Opportunities

Formative (Whilst you’re working on the coursework)

You will frequently be given informal verbal or written feedback regarding your (or the class’s) performance on tasks relating to the coursework assessment during the seminar and/or laboratory sessions. Attendance is therefore important for your development and thus coursework success.

Summative (After you’ve submitted the coursework)

You will receive specific feedback regarding your coursework submission together with your awarded grade when it is returned to you. Clearly, feedback provided with your coursework is only for developmental purposes so that you can improve for the next assessment or subject-related module.

1. Moderation

The Moderation Process

All assessments are subject to a two-stage moderation process. Firstly, any details related to the assessment (e.g., clarity of information and the assessment criteria) are considered by an independent person (usually a member of the module team). Secondly, the grades awarded are considered by the module team to check for consistency and fairness across the cohort for the piece of work submitted.