MBL 402 ENTIRE COURSE


Ask a Question

MBL 402 ENTIRE COURSE

Regular price $50.00

MBL 402   ENTIRE COURSE
 
 
WEEK  1


MBL 402 Week 1 Individual Assignment Week1App

 

Instructions: Please read this instruction, and section 5 and 6 in particular, CAREFULLY as it affects all future programming assignments.

 

  1. Setup Android Studio Development Environment 1.1 Download necessary packages using SDK Manager (ToolsAndroid-SDK Manager), making sure at least the following items are included (check "Show Package Details" to see detailed package items) 1.1a. SDK Platforms: Android 8.0 (Android SDK Platform 26, Google API Intel x86 Atom System Image) 1.1b. SDK Tools:  Recommended to install all packages (with the latest version for each package)   1.1c Note that when you open projects from other sources (sample projects, projects from the textbook etc), you may be prompted to install additional dependent packages and tools.

 

1.2 Install Intel HAXM if your CPU supports it. (Note that if your machine is not based on HAXM supporting Intel CPU, you may not be able to run Emulator).

 

  1. Create an Android Virtual Device (AVD name MBL402 recommended) with the following configuration, using AVD Manager (Tools-Android-AVD Manager) (Note: this will serve as the virtual device all future programming projects should be tested on, unless explicitly specified otherwise) - Device Profile: Phone/Nexus 5 - System Image Android Intel x86 with Google API - API Level 26 - Other default settings

 

  1. (Optional) Test your development environment by importing some Android code sample (e.g. BorderlessButton) (you may need to install additional packages) or open some project downloaded from the textbook. Make sure you can run/debug the project on the AVD created. Experiment with this play project and see if it behaves as expected on the AVD.

 

  1. Develop your first Android App.

 

4.0 Start a new Android Studio project by adding an blank activity template (which should display a "hello world" message on the screen), with the following settings (note that naming convention and settings MUST be applied to all future assignments). This is to ensure your submitted package name is unique. Assignment: Week1App Android Studio Project Settings: - Application Name: Week1App<first-char-of-first-name-uppercase><first-char-of-last-name-upper-case><last-4-digits-IRN>    for example, Week1AppCL3456 - Company Domain: mbl402.phoenix.edu - Automated populated Package Name: edu.phoenix.mbl402.<application-name-in-lower-case> - Leave "Include C++ Support" option unchecked. - Project Location: Choose a local directory to hold project files. - Target Android Device: Phone and Tablet/Minimum SDK = API 17 (default) - Activity Template: Empty Activity - Accept default names for Activity (MainActivity) and Layout (activity_main). Accept backward compatibility support (AppCompat) After the auto gradle build is complete, click Run-RunApp and make sure the "Hello World" message appears on the Emulator's screen.

 

4.1 Now modify the project to meet the following requirements: a. Change the display text to:  "Hello Android, my name is <your full name>." (1.5 pts) b. Change the text color to green. (1.5 pts) c. Implement an "add message" menu item. When selected, some new message will be shown below the exiting texts on the screen. (2 pts)

 

  1. Assignment Submission Instructions (apply to all future

Individual Dec 04, 2017 11:59 PM 5

programming assignments, including the team project) Once you have developed and tested the application on the AVD, gather the following THREE (3) items for review/grading. 5.1 Project Report File: 5.1a File Name/format: <ApplicationName>Report.doc/Microsoft Word 5.1b File Content: includes the following sections (please refer to AppReportSample file for detail): - At a glance summary on the implementation status of each requested feature and honest self-assessment of points to be earned. - For each feature, include all relevant app screenshots with narratives to prove the app works as expected. One should be able to look at this report to determine how well you implemented the requested feature (and the points/grade earned). - Reference and credits to source that was used for the app. 5.2 app-debug.apk file (typically generated under the app-build-outputsapk directory of the project workspace, if build is successfully). The apk must be installable and runnable to be considered for credit for the whole project. Additional note about the .apk file: To verify you can install and run the apk file onto the emulator, do the following: - Run the emulator (if not already running) - Drag and drop the apk file onto the emulator's window. Alternatively, in command prompt, go to <sdk-directory>/platform-tools, run "adb install <full-path-to-apk-file>" (you may want to set the PATH env variable so that you can run adb command from any location). -  If successful, you should be able to locate the newly installed app on the emulator and start it. - if you can run the app in Android Studio but the app would crash when installed from apk file, try build the apk file via build->build apk menu and try again. 5.3 src.zip: Clean (Build->Clean) the project. Make a copy of the project's directory (see ProjectSourceTreeStructure material). Delete the following two directories from the copy: <project>-build and <project>-app-build. Then zip the project's directory into a src.zip file. This is to ensure your src.zip file has minimum size (usually it should be less than 1MBs). Make sure that when the src.zip is unzipped, you should be able to open it in Android Studio.

 

Zip the above THREE (3) files into a single .zip file for submission. All 3 files must be included to earn any credit. Also you must have an installable and working .apk file included to earn any points. In another word, you will receive 0 point if your app doesn't build. But you will receive partial credit for successfully implementing some of the requested features. So plan your time accordingly.

 

  1. Assignment Submission Check: Please bear in mind that it's your responsibility to submit your work with the requested files in a timely manner. Here are some additional tips and instructions for double checking your submission before and after submission.

 

6.0 Make sure your apk file comes from the source and the project test reports comes from the apk file. If these items are found to mis-match, incidents of "academic dishonesty" may be reported to the University. 6.1 Make sure you include all three files.

6.2 Make sure you can manually install and run the apk on the specified AVD. 6.3 Make sure src.zip file is no more than 1MB. If your source zip is over-size due to large image files, please use smaller ones. Large files make it very difficult, if not impossible, for me to download your assignments in a batch fashion. 6.4 Make sure you have submitted the correct files. Download your own submisson and veridy if necessary. No excuse whatsoever will be accepted for wrong submissions.

.

MBL 402 Week 1 Learning Team Assignment Charter

 

Instructions: After you are assigned to a learning team, complete the learning team charter

 

 
WEEK  2

 MBL 402 Week 2 Individual Assignment Week2App


Instructions: Create an Android™ app to show others a collection of five to eight items that you intend to sell through your app. Choose any items you desire. Include the following features and functions in your app:   

  • An opening screen that displays the names of your list of the items with a button to select the ones you want to buy (4pts)
  • A second screen that displays an explanation or description of the item and the price when the user selects an item (4 pts)
  • Functionality allowing the user to place items into a shopping cart (2 pts)

 


 MBL 402 Week 2 Learning Team Assignment Report

 

Instructions: Brainstorm an app that uses at least the following Android™ features:   

  • Multiple activities
  • Multiple controls
  • Location and mapping service
  • Sqlite database services The team then should do the following:
  • Detailed features of this app (Team<team>App)
  • Design a coherent look and feel and navigation.
  • Develop a plan to outline the tasks and the milestones.
     

WEEK  3

MBL 402 Week 3 Individual Assignment Week3App

 
Instructions: Create an Android™ app to showcase location and mapping services using Android™ Studio.

You are expected to learn the following three programming elements with is project: - Android's new permission model with API 23 and above - Making app location aware (starting point for location based service). - Google API service (using google Map service as an example)

 

Preparation (recommended): Start a new Android project with "MapsActivity" as the activity template. Then follow the following steps:   

  1. Review "res\values\google_maps_api_xml" file.
  2. Create Google Maps API key per the instructions.
  3. Fill in the API key in "google_maps_api_xml" file.
  4. Run the app. If there are errors, you may need to compile this with a lower version of google services. You can change this is in "Build.gradle" and alter to a version such as "com.google.android.gms:play-services:8.1.0".
  5. Make sure you have a running app on the AVD. New features request: Add/change the basic map application with the following new features:
  6. Having "zoom in" and "zoom out" controls on the screen (3 pts)
  7. Having at least "normal" and "satellite" views of the map via menu selection. (3 pts)
  8. Showing a "marker" on the current location of the device. Marker automatically moves to new location upon change of location. (2 pts)
  9. Info Window of the marker shows current location's "city, state/provivence, country and zipcode". (2 pts)

 

Review Week 1 Individual project for application development, testing and submission instructions.

 

Note that emulator does not have GPS. But for testing purpose, you can set it to a geo location via the "More/Extended Control" button on the emulator (the "..." button to the side of the emulator). Set it to different locations to simulate change of location.


 
MBL 402 Week 3 Learning Team Assignment Report

 
Instructions: Refine the design to finalize the look and feel and navigation. Develop a means of integrating a Google Map™ into the final App. Decompose the app into pieces to be developed by each team member. Develop an integration plan to integrate these pieces to form a single app. Start delevelop the assigned component by each team member


 


WEEK  4

MBL 402 Week 4 Individual Assignment Week4App

 
Instructions: Create an Android™ app to store and display car information for a dealership showing the customer name, car make, car model, and purchase cost. Include the following fields in the SQLite Database:   

  • A Database name of "CARDEALER.db".
  • A Table_ name of "CUSTOMER_TABLE". The table should contain the following fields:
  • ID (PRIMARY KEY INTEGER auto Increment)
  • CUSTOMER FIRST NAME (TEXT)
  • CUSTOMER LAST NAME (TEXT)
  • CAR MAKE (TEXT)
  • CAR MODEL (TEXT)
  • COST (NUMERIC) Complete the following steps (3 pts each)

 

  1. Create a button named, "ADD" to allow a user to add the customer first and last name, car make/model, and cost.
  2. Create a second button named, "VIEW" to display all customer data held in the SQLite DB on the screen.
  3. Create a third button named, "UPDATE" that will allow the user to update the customer name, car make. model, and cost fields that are held on the database. Users should not be allowed to change the ID field.
  4. Create a fourth button named, "DELETE" to allow the user to delete an existing customer on the screen and remove them from the database. Review Week 1 Individual project for application development, testing and submission instructions.

 

MBL 402 Week 4 Learning Team Report

 

Instructions: The team should have all the individual pieces developed and ready for testing at a preintegrated level (unit testing). Develop sqlite database code for the app. Develop a test plan for each piece and test with different team members.

 

 

WEEK  5

MBL 402 Week 5 Individual Assignment Final App Project

 

Instructions: Part I Create an Android™ app that will be used to enter student grades for college courses. Develop three screens as follows:   

  • The first screen should allow the entry of a student id, first name, last name, class id, and class name.  •  The second screen should allow the entry of a grade for each student and class that they took. The grade entry will be a number which can range from 0 - 100.   
  • The third screen should show the student name and overall letter grade for the semester based on the classes that they took.

 

Design the database using the following fields and criteria:

  • Student ID VARCHAR (8),
  • First Name varchar (20),
  • Last name varchar (20),
  • Class ID varchar (20),
  • Grade Integer (3),
  • Letter grade Varchar (2)

 

Part II Prepare a 5-slide presentation to present the app, including speaker's notes. Create the content for the presentation. The following are examples of appropriate content:   

  • The best uses of Google Cloud™ messaging
  • The best uses of Google Maps™ API and where it can be best used.

 

MBL 402 Week 5 Learning Team Assignment Application

 

Instructions: Complete a working mobile app based on the work done since Week Two. This app has pieces and modules developed by individual team members that run together as a single app. Integrate the pieces from the previous weeks, into a working mobile app that runs as a single app.

Review Week 1 Individual project for application development, testing and submission instructions.



MBL 402 Week 5 Learning Team Assignment Project Presentation

 

Instructions: Write a 1-page paper discussing what professional organizations might you join, and what websites might you visit that would provide insight into a career that includes responsibility for creating, working with, testing, and publishing mobile applications? Format your paper according to APA guidelines.

 

 

 

 

Questions & Answers

Have a Question?

Be the first to ask a question about this.

Ask a Question