Mobile Android Application Name Field Logger

Question: Discuss about the Mobile Android Application Name Field Logger. Answer: Introduction: Purpose: The purpose of developing this report is to give details of the requirement for the development of a Mobile Android Application. This report is intended to be reviewed by Professor of course as an assignment work for the fulfilment of the coursework. Scope: Field Logger-Mobile Android Application is the software for Android Mobiles to give them extended features through Application or App (Added Application in Mobile Devices). This App will help in creating a data logger to capture field data in a mobile application that stores the data in a local database . Definitions : Treatment Data: It is a page or Data Fragment , that is to be displayed when a user clicks on a Field given in the Mobile Android App. Save Log Entry: It is a Button to be given on the App , pressing this button the values will be saved Locally in the SQLD Database in the application. Show Log Entries: It is a Button to be given on the App , pressing this button a page or Data Fragment will be displayed that lists the all the date/time and treatment entries made for that field. Send all entries Item: This is an item to be given in the Menu of the application, selecting this item the data collected and stored in the local database is to be composed into an email, and sent using the built in mail app. The local database is then to be cleared of all entries. Requirement Elicitation: System overview-: We are making a project report on a software Application for Mobile Android System. This will work as an extended functionality in the Mobile Device. Functional requirements-: The software segments should work according to the expectations specified in the given assignment. All the buttons and Menu items should work properly. The functional requirements for this Android Application software are-: Product perspective-: This Android Application is to be developed for Smart Mobiles specifically. This App should easily be loaded in the system without altering the setting or features of the Mobile System. The performance of the retaining features of the application should not be affected by this App. 1. System Interfaces-: The system should consists of 2. Mobile Application Home Startup Page 3. Shed 1 to Shed 5 Data Entry Pages 4. HP 1 to HP 2, FO, MZ and Control Data and Show Field Logger Entries Pages 5. Options Menu pages 6. Profile page Operations-: We have to include Designing, coding, test cases, Product Analysis. User Interface-: As this will be an Android Mobile Application, all the functionalities must work on touch mode system based. All the features must be user friendly and easy to locate. Non Functional Requirement: Software Interfaces-: This project report has been specified in the assignment, requires to be developed on specifically Android Java development undertaken using the Eclipse ADT IDE and API's. Application Adaptation Requirements-: Browsers: The application is not intended to work for browsers. Networks The application should not need the network for functioning and therefore should not be targeted for specific networks. Devices: The list of Android platforms this application is required to be compatible are listed below: Android 6.0 Marshmallow Android 5.1 Lollipop Android 5.0 Lollipop Android 4.4 - KitKat Android 4.3 Jellybean User characteristics-: This is a Mobile Application and will be used by teenagers to adults. So the primarily the interface should not be highly complicated or highly technical. It should be user friendly. Testing Strategy For successful implementation of any application a well designed Testing Strategy is required. Testing not only intends to identify functional and non-functional errors , it also intends to check the Quality Constraints of the application. Here the Testing Strategy for Mobile Android Application - Field Logger is as follows-: Step1- Selection of mobile models and device manufacturers This application is needed to be tested on the mobile System, Before selecting a Mobile for testing this application following considerations has to be made most importantly- 1. Android Version- Like other companies Android also releases the new versions time to time, every new version retain old good features and extend new functionalities. The testing approach here is that the application developed should be compatible with the latest as well previous versions too, along with this it should be flexible to adjust in the new version release. 2. Screen Size- The mobile devices are available in different sizes of there screen sizes. The variation in screen sizes also bring variation in the pixel mode of the Mobiles. This variation in the pixel values also render the display of application differently. Mobiles with larger screen has better display system. The testing approach here is that the application should work properly in all the screen sizes mobiles. 3. Device Fragmentation- Different Android devices are available with different Device fragmentation , our testing approach will be to verify whether the application is compatible with different fragmentation devices or not. Hardware Configuration: The different mobiles have different Hardware configuration, the system should be compatible with these configuration too, the application will be tested in the different mobiles with different configuration. Testing the application on Emulators Testing the application on the different mobile devices is very time consuming, costly and tedious approach. For this an option of Emulators are available. Emulators do not provide a testing experience of real Mobile environment of testing, but it is good for collection of big sample of test data. Adhoc Testing done for the app Automated Testing: For doing the Automated testing of the application UI Monkey Exerciser that is recommended by Google as one of the few tools used for testing Android applications. This is used with combination of Emulator within Android studio. This run test script for application, by testing no bugs and errors were found. Mannual Testing- Testing steps are as follows- Test case Input Expected Output 1 Go to Home Screen The screen should display properly. 2 Select Save Log Button The values should be save locally in the application in a SQL Database 3 Select Show Log Entries button A related page (fragment) should be shown that list all the date/time and treatment entries made for that field 4 Select Send all entries item The data collected and stored in the local database is composed into an email, and sent using the built in mail app Application Commentary As part of the second assignment we made a few changes as part of the requirements specified along with a few other changes. Changes specified by the assignment: 1. Made the options menu options functional. 2. Developed the Save All Entries button to save all unsaved notes to the database. 3. Developed the Send All Entries button to send the username amended with all notes from all players along with the date and time when the note was made along with a popup dialog that allows the user to cancel out of sending the email if they intend to do so. 4. Develop the Profile options menu to create a profile with a validation that checks if the passwords match and show a message when the profile is already created. 5. Back button feature allows the user to exit either after saving the data to the database or without it and move back to the home page from the profile page. Additional suggested features The information of the location of the user when making notes can be an interesting feature to add. Other ways to share notes using the app can be developed . A feature could also be added to integrate with the calendar to record notes that are schedules. Ethical Considerations Some ethical considerations when developing any Android application which is essential to ensure the integrity is maintained is as follows: Data Privacy When collection information from the user of the application it is essential to make sure that the data is maintained with highest possible security and the privacy of the users information is made the most important priority to ensure that the data is not transmitted without the users consent. Data Collection When collecting data it is important to ensure that the data that is expected to be collected is collected and other information which though might be available to be recorded is not without the users prior consent. Code Plagiarism When developing any application it is important to ensure that when code is being reused prior permission is received. Financial Case: Potential revenue streams and costs The revenue from the application can be generated through two approaches 1. Indirect Approach: The indirect approach is the approach that is best suited to the user as it does not cost the user anything and is generated primarily using ads that generate revenue when they are clicked on. 2. Direct Approach: The direct approach is the approach that charges the user directly for the application, the user pays for the download and this is the least suited approach to the user as it needs a payment to download in terms of the charge to the user. Project Schedule: Conclusion Developing an Android application is a vast field and highly innovative. This was a simple student level approach with simple knowledge . This was a learning approach for us. No doubt the knowledge obtained will be beneficial for us. References Alford, M.W.A requirements engineering methodology for real time processing requirements, IEEE Trans .on Software Engineering Fichman,R.G and Kermrer ,C.F, Object- Oriented and convention analysis and design methodologies, IEEE computer. Jorgensen,P.C. and Erickson, C. Object-Oriented integration testing. Comm.ACM Principles of Software Engnieering Management Component Software-Beyond Object-Oriented Programming,Szyperski C; Addison-Wesley. Software Engineering, Schaums Outlines, David Gustafson, Tata Mc Graw-Hill. Tutorialpoint.com ,software Engineering, from www.tutorialpoint.com