Microsoft Word - Document1 Building a bubble level application that integrates with sensors In this assignment you will be required to build a bubble level (sometimes known as a spirit level)...

View Document had submitted this before but the expert wasn't well, tell me if it can be done or not in the start itself.


Microsoft Word - Document1 Building a bubble level application that integrates with sensors In this assignment you will be required to build a bubble level (sometimes known as a spirit level) application. The idea is that this allows an android device to measure how flat, level, or vertical surfaces are. You will be required to use the sensors on the device to determine the orientation of the device and to display one of two custom views for the application. Using a flat table as the reference plane you will need the following views.: • The device is lying at on the table. It should show a circular bubble level with the bubble able to move in two dimensions. A bubble in the exact centre indicates a perfectly level surface. • The device is perpendicular to the table in either portrait or landscape. It should show a single bubble level. The bubble may only move left or right. A bubble in the exact middle indicates a surface that is either perfectly at or perfectly vertical. The score for your application will depend on: 1. How fully featured, complete, and robust your code is. Along with how well your UI is thought out 2. How well documented is your code 5 Coding Brackets (80%) 1. Bracket 1 (10%) • Basic layout that is responsive to changes in orientation. • Basic shell of both custom views. 2. Bracket 2 (20%) • Addition of listener(s) that will collect the necessary sensor data to determine the orientation of the device. • Last 500 samples of sensor data is kept in a datastructure and main- tained. 3. Bracket 3 (30%) • Working bubble level custom view for the 1D case (device in land- scape or portrait mode) that has a range of [-10, 10] degrees. 4. Bracket 4 (40%) • Working bubble level custom view for the 2D case that has a range of [-10, 10] in both directions. 5. Bracket 5 (50%) • UI elements that show the maximum and minimum values encoun- tered in the last 500 samples for the 1D case. • UI elements that show the maximum and minimum values encoun- tered in the last 500 samples for the 2D case in both directions. 6. Bracket 6 (60%) • Add in a line to the 2D bubble showing where North is. 7. Bracket 7 (70%) • Add in UI controls for the 2D bubble to alter the direction the line is pointing. 8. Bracket 8 (80%) • UI design: well thought out UI and custom view that is easy and intuitive to use. 6 Documentation Brackets (20%) NOTE: Documentation should be around 1,700 words in length total 9. Bracket 9 (15%): Document every method in your code from a high level perspective. i.e. give an overview of what the method does. Do not copy and paste code you will be penalised for this. 10. Bracket 10 (20%): Document every datastructure and database design you have used in your code and why you chose them. You do not need to provide an E-R diagram for database designs.