Page 1 of 5 Assignment 2 — Mobile Android application Due date: 5:00pm AEST, Friday Week 10 ASSESSMENT Weighting: 30% Length: Less than 50 MB 2 Objectives This assessment item relates to the learning outcome 1, 2 and 3. More specifically, to design and implement a complex mobile application. The objective of this assignment is for students to: • Develop, test and maintain a mobile application using an integrated suite of mobile software development tools. More specifically Android Java development is undertaken using the Eclipse ADT IDE and API's. Introduction You are assigned the task of creating a data logger to capture field data in a mobile application that stores the data in a local database. The app has fields to record data for each of five different fields, representing different treatment to be investigated. If a field is selected, a page (fragment) is shown to add data entries for that field. An entry consists of treatment data. When the Save Log Entry button is pressed these values are saved locally in the application in a SQLDatabase. When the Show Log Entries button is pressed a related page (fragment) is shown that list all the date/time and treatment entries made for that field. When the Send all entries item in the profile menu is selected, the data collected and stored in the local database is composed into an email, and sent using the built in mail app. The local database is then cleared of all entries. Appropriate messages are to be sent during this interaction. We will refer to our app as FieldLogger. More details of these pages will be given in the sections below. You should also consult the weekly lecture/tutorials on the Moodle website for help and more information on completing the assignment. The tutorials contain step-by-step procedure for working through the assignment as well as some tips and extra help. So make sure you read the lecture/tutorials on the Moodle website. Mobile Application Home Startup Page The application start-up is unchanged from assignment 1. Shed 1 to Shed 5 Data Entry Pages These pages are unchanged from assignment 1. HP 1 to HP 2, FO, MZ and Control Data and Show Field Logger Entries Pages These pages are unchanged from assignment 1. Options Menu pages The Options Menu options is unchanged from assignment 1 except for the Send all entries option. The Send all entries will be used for sending the field data database to the employer and to clear the current database of any entries, see figure. Page 2 of 5 If the OK button is pressed the DialogProgress class is used to send the email and show the progress of the action, e.g. An email message is composed containing each fields' log entries during the ProgressDialog event using an Intent object and the built in Mail app. The username given in the preferences is to be contained on the first line of the email. Each date / time and Field logger entry is put on its own line in the email, e.g. Page 3 of 5 When the email is sent all the Field logger entries are deleted. To test this feature send the email to yourself. Include a copy of any such emails in the documents you submit for the assignment. Profile page The Profile fragment is unchanged from assignment 1. Other Features These are unchanged from assignment 1. Required Documentation You are also to prepare a Word document. Your document should include an appropriate title page. Your document should have two sections that address the software requirements, testing and application commentary given below. Plan for a Testing Strategy for your Mobile Web Site Your document should: • Create and review a list of mobile devices, and versions of Android targeted by the app. • Discuss whether testing is required on actual devices and what part emulators/simulators and desktop browsers can play in this process • Review the kind of ad-hoc testing that may be used to help frame your device testing strategy. Networking your APP Discuss how you would use networking and JSON web services to send your data to the organization. Assume the organisations' http address is www.cpws.cqu.edu.au. Page 4 of 5 Financial Case & Application Commentary Your document should: • List the features you successfully implemented and those you were unable to successfully implement; you should describe the problem in a few sentences and also briefly describe anything you attempted to do to get it to work. Your approach to identifying and attempting to fix these bugs may gain you some partial credit for those features you were unable to implement. • A description of any additional functionality you believe would be useful to add to this Website should be included. Explain what the features are and how they would help to improve the Website. • Are there any ethical considerations in making this kind of service available? • Discuss the economic/financial case for an extension of the proposed system that would allow you to customise the record keeping features of the app. Identify potential revenue streams and costs. How much would these costs be for your proposed user base? How would you show that you are achieving this user base? Given how long it has taken you to develop what do you estimate technical development costs to be in hours? How would you promote your app and what kind of marketing should be employed? . Submission You are required to submit your assignment electronically via the Moodle course website. The deliverable is a rar or zipped directory containing all the code and resources needed for testing. You must rar or zip together: • Use the export option on your project to produce a zip file that can be imported back into Eclipse to re-create your project. • Your Word document • Copies of emails from your app The resulting rar or zip file should be submitted on the course website. Please note that you should use your student number as the name for your rar or zip file when uploading to Moodle. Page 5 of 5 Assessment criteria Assignment Component Criteria Marks Total Location UI - Field logger data copied to email - Message sent asynchronously using thread - ProgressDialog displayed and email received 6 Testing Strategy - Discuss the selection of mobile models and Android versions for your testing process - Discussion of whether testing is required on actual devices and what part emulators/simulators and desktop browsers play in the process 2 2 Networking your App - Discussion of using HTTP connection - Discussion on downloading text content 4 Financial Case & Commentary - Discussion of the economic/financial case for the proposed system - Identification of potential revenue streams and costs - Evaluation of costs for your proposed user base - Showing how you achieve this user base - Estimation of technical development costs in hours - Discussion of how you would promote and market your app. 12 General - Feedback given as required - Use appropriate naming conventions - Adequate commenting - Correct grammar - Citation of references, copyright use 4 Penalties Total 30 Lecturer Comments Lecturer's Signature Date: