ABM2 — ABM2 TASK 1: MOBILE APPLICATIONDEVELOPMENT
MOBILE APPLICATION DEVELOPMENT — C196
PRFA — ABM2
COMPETENCIES
4026.01.4
:
Saving Data
The graduate explains ways to save data in a mobile application, and creates a data base in a mobileapplication.
4026.01.5
:
Sharing Information
The graduate explains how to share information in mobile applications and creates a user-defi ned contentprovider.
4026.01.6
:
Supporting Different Devices
The graduate describes how to utilize the available hardware and services available in different devices.
4026.01.7
:
Deploying Mobile Application
The graduate describes mobile application deployment and prepares and application for deployment.
INTRODUCTION
As a competent mobile application developer, your understanding of mobile application structure and designwill help you to develop applications to meet customer requirements. The following project to develop astudent scheduler/student progress tracking application, will help you to apply these skills in a familiar, real-world scenario. This task will allow you to demonstrate your ability to apply the skills learned in the course.
You will develop a multiple-screen mobile application for a student to track terms, courses associated witheach term, and assessment(s) associated with each course. The application will allow students to enter, edit,and delete term, course, and assessment data. It should provide summary and detailed views of courses foreach term and provide alerts for upcoming performance and objective assessments. This application will usea SQLite database.
REQUIREMENTS
Your submission must be your original work. No more than a combined total of 30% of the submission and nomore than a 10% match to any one individual source can be directly quoted or closely paraphrased fromsources, even if cited correctly. The similarity report that is provided when you submit your task can be usedas a guide.
You must use the rubric to direct the creation of your submission because it provides detailed criteria thatwill be used to evaluate your work. Each requirement below may be evaluated by more than one rubric
TASK OVERVIEW
SUBMISSIONS
EVALUATION REPORT
aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course.
Tasks may
not
be submitted as cloud links, such as links to Google Docs, Google Slides, OneDrive, etc., unlessspecifi ed in the task requirements. All other submissions must be fi le types that are uploaded and submittedas attachments (e.g., .docx, .pdf, .ppt).
Note
: The assessment must be submitted in an Android Studio project using Java as the programminglanguage. External plugins and libraries are not allowed in the project.
Note
: Submit your performance assessment by including all Android project fi les, APK, and signed apk fi les inone zipped.zip fi le.
Note
: The zip fi le submission must also keep the project fi le and folder structure intact for the Android StudioIDE.
A. Create an Android mobile application, compatible for Android 8.0 and higher. The application mustinclude the following functional requirements:
1. Create a user option to enter term titles (e.g., Term 1, Term 2, Spring Term), start dates, and end datesfor
each
term.
2. Create features that allow the user to add as many terms as needed.
3. Implement validation so that a term cannot be deleted if courses are assigned to it.
4. Create features that allow the user to do the following for
each
term:
a. Add as many courses as needed
b. Display a list of courses associated with
each
term
c. Display a detailed view of the term title (e.g., Term 1, Term 2, Spring Term), the start date, and theend date for
each
term
5. Include the following details for
each
course:
• The course title
• The start date
• The end date
• The status (in progress, completed, dropped, plan to take)
• The course instructors’ names, phone numbers, and e-mail addresses
6. Include features that allow the user to do the following for
each
course:
a. Add as many assessments as needed.
b. Add a minimum of one optional note per course.
c. Enter, edit, and delete course information.
d. Display optional notes.
e. Display a detailed view of the course, including the end date.
f. Set alerts for the start and end date, that will trigger when the application is not running.
g. Share notes via a sharing feature (either e-mail or SMS) that automatically populates with thenotes.
7. Include features that allow the user to do the following for
each
assessment:
a. Add performance and objective assessments for
each
course, including the titles and end dates ofthe assessments.
b. Enter, edit, and delete assessment information.
c. Set alerts for start and end dates, that will trigger when the application is not running.
B. Design the following screen layouts, including appropriate GUI (graphical user interface) elements (e.g.,navigation, input, and information) for
each
layout:
• home screen
• list of terms
• list of courses
• list of assessments
• detailed course view
• detailed term view
• detailed assessment view
C. Implement a scheduler within your application from Part A and include the following elements:
• an ArrayList
• an intent
• navigation capability between multiple screens using activity
•
three
activities
• events (e.g., a click event)
• the ability to work in portrait and landscape layout
• interactive capability (e.g., the ability to accept and act upon user input)
• a database to store and retrieve application data
• an application title and an icon
• notifi cations or alerts
• the use of both declarative and programmatic methods to create a user interface
1. Include the following interface requirements in the application from part C:
• the ability to scroll vertically
• an action bar
•
two
layouts
• input controls
• buttons
D. Create a storyboard to demonstrate application fl ow that includes
each
of the menus and screens frompart B.
E. Provide screen shots of generating the signed APK to demonstrate that you have created a deploymentpackage.
Note: Verify that all the required functions of your application are working by executing the apk fi le.
F. Refl ect on the creation of your mobile application by doing the following:
1. Explain how your application would be different if it were developed for a tablet rather than a phone,including a discussion of fragments and layouts.
2. Identify the minimum and target operating system your application was developed under and iscompatible with.
3. Describe
(suggested length of 1–2 paragraphs)
the challenges you faced during the development ofthe mobile application.
4. Describe
(suggested length of 1–2 paragraphs)
how you overcame
each
challenge discussed in part F3.
5. Discuss
(suggested length of 1–2 paragraphs)
what you would do differently if you did the projectagain.
6. Describe how emulators are used and the pros and cons of using an emulator versus using adevelopment device.
G. Acknowledge sources, using APA-formatted in-text citations and references, for content that is quoted,paraphrased, or summarized.
H. Demonstrate professional communication in the content and presentation of your submission.
File Restrictions
File name may contain only letters, numbers, spaces, and these symbols: ! – _ . * ‘ ( )
File size limit: 200 MB
File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, fl v, asf, mpeg,wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z
RUBRIC
A
:
MOBILE APPLICATION VERSION
A1
:
TERM FUNCTIONAL REQUIREMENTS
A2
:
TERM ADDITION FEATURE
A3
:
VALIDATION IMPLEMENTATION
NOT EVIDENT
An Android mobile application isnot provided.
APPROACHINGCOMPETENCE
The Android mobile applicationis not version 8.0 or higher, ordoes not load properly, or theAndroid project fi les, APK, andsigned apk fi les are not in onezipped.zip fi le.
COMPETENT
The Android mobile applicationis a version 8.0 or higher, loadsproperly, and all Android projectfi les, APK, and signed apk fi lesare in one zipped.zip fi le.
NOT EVIDENT
The mobile application does notallow the user to enter any in-formation for any term.
APPROACHINGCOMPETENCE
The mobile application does notallow the user to enter term ti-tles, or all the start and enddates for each term.
COMPETENT
The mobile application allows theuser to enter all term titles andall start and end dates for eachterm.
NOT EVIDENT
The features included in the mo-bile application do not allow theuser to add terms.
APPROACHINGCOMPETENCE
The features included in the mo-bile application are coded to al-low the user to add a limitednumber of terms.
COMPETENT
The features included in the mo-bile application are coded to al-low the user to add an unlimitednumber of terms.
NOT EVIDENT
APPROACHINGCOMPETENCE
COMPETENT
A4A
:
COURSE ADDITION
A4B
:
LIST OF COURSES
A4C
:
TERM DETAILS
A5
:
COURSE DETAILS
The mobile application does notallow the user to delete anyterms.
The mobile application includesvalidation that allows the userto delete a term, regardless ofwhether that term has coursesassigned to it.
The mobile application includesvalidation to prevent the userfrom deleting a term when cour-ses have been assigned to thatterm.
NOT EVIDENT
The mobile application does notallow the user to add courses toany term.
APPROACHINGCOMPETENCE
The mobile application is codedso that the user can only add alimited number of courses toeach term.
COMPETENT
The mobile application is codedso that the user can add an un-limited number of courses toeach term.
NOT EVIDENT
The mobile application does notallow the user to display a list ofcourses.
APPROACHINGCOMPETENCE
The mobile application allowsthe user to display a list of cour-ses, but the courses are not as-sociated with any terms.
COMPETENT
The mobile application allows theuser to display a list of coursesassociated with each term.
NOT EVIDENT
The mobile application does notallow the user to display a de-tailed view of any terms.
APPROACHINGCOMPETENCE
The mobile application allowsthe user to display a view ofeach term, but the view does notinclude the term title, the startdate, and the end date for eachterm.
COMPETENT
The mobile application allows theuser to display a detailed view ofeach term and the view includesthe term title, the start date, andthe end date for each term.
NOT EVIDENT
The mobile application does notallow the user to enter anycourse details.
APPROACHINGCOMPETENCE
The mobile application does notallow the user to enter 1 ormore of the given details foreach course.
COMPETENT
The mobile application allows theuser to enter all the given detailsfor each course.
A6A
:
ASSESSMENT ADDITION
A6B
:
OPTIONAL NOTES ADDITION
A6C
:
COURSE INFORMATION
A6D
:
OPTIONAL NOTES DISPLAY
A6E
:
DETAILED VIEW
NOT EVIDENT
The mobile application does notallow the user to add any assess-ments to any course.
APPROACHINGCOMPETENCE
The mobile application is codedso that the user can add be-tween 1 and 4 assessments toeach course.
COMPETENT
The mobile application is codedso that the user can add as manyas 5 assessments to each course.
NOT EVIDENT
The mobile application does notallow the user to add optionalnotes.
APPROACHINGCOMPETENCE
The mobile application allowsthe user to add optional notes,but the notes are not within anycourse, or the optional notes canonly be added to some of thecourses.
COMPETENT
The mobile application allows theuser to add optional notes withineach course.
NOT EVIDENT
The mobile application does notallow the user to enter, edit, ordelete course information forany course.
APPROACHINGCOMPETENCE
The mobile application only al-lows the user to enter, or edit, ordelete parts of each course’sinformation.
COMPETENT
The mobile application allows theuser to enter, edit, and delete anyinformation for each course.
NOT EVIDENT
The mobile application does notallow the user to display op-tional notes.
APPROACHINGCOMPETENCE
The mobile application allowsthe user to display optionalnotes, but the notes are notwithin any course.
COMPETENT
The mobile application allows theuser to display optional noteswithin each course.
NOT EVIDENT
The mobile application does notallow the user to display a view
APPROACHINGCOMPETENCE
COMPETENT
The mobile application allows theuser to display a detailed view of
A6F
:
ALERTS FOR COURSES
A6G
:
SHARING FEATURES
A7A
:
ASSESSMENTS FOR EACH COURSE
A7B
:
ASSESSMENT INFORMATION
of the course information.
The mobile application allowsthe user to display a view of thecourse information, but not foreach course, or the view for acourse does not include the enddate.
the course information for eachcourse, including the end date foreach.
NOT EVIDENT
The mobile application does notallow the user to set any alerts.
APPROACHINGCOMPETENCE
The mobile application allowsthe user to set alerts for eitherthe start or the end date of eachcourse, or the alerts do not trig-ger when the application is notrunning.
COMPETENT
The mobile application allows theuser to set alerts for both thestart and end date of each courseand the alerts can trigger whenthe application is not running.
NOT EVIDENT
The mobile application does notallow the user to share notes.
APPROACHINGCOMPETENCE
The mobile application allowsthe user to share messages oremails, but the information doesnot automatically populate fromthe notes.
COMPETENT
The mobile application allows theuser to share messages or emailthat automatically populateswith the notes.
NOT EVIDENT
The mobile application does notallow the user to add anyassessments.
APPROACHINGCOMPETENCE
The mobile application allowsthe user to add performanceand objective assessments foreach course, but cannot includethe title of the assessment andthe end date for eachassessment.
COMPETENT
The mobile application allows theuser to add performance and ob-jective assessments for eachcourse, including the title of theassessment and the end date foreach assessment.
NOT EVIDENT
The mobile application does notallow the user to modify in any
APPROACHINGCOMPETENCE
The mobile application allowsthe user to either enter, edit, or
COMPETENT
The mobile application allows theuser to enter, edit, and delete all
A7C
:
ALERTS FOR GOAL DATES
B
:
SCREEN LAYOUTS
C
:
STUDENT SCHEDULER AND PROGRESS TRACKING APPLICATION
C1
:
INTERFACE REQUIREMENTS
D
:
STORYBOARD
way, information for anyassessments.
delete information for each as-sessment, but not all three.
assessment information.
NOT EVIDENT
The mobile application does notallow the user to set any alerts.
APPROACHINGCOMPETENCE
The mobile application allowsthe user to set alerts for eitherthe start or the end dates foreach assessment.
COMPETENT
The mobile application allows theuser to set alerts for all start andend dates for each assessment.
NOT EVIDENT
A design of any screen layouts isnot provided.
APPROACHINGCOMPETENCE
The screen designs include thelayout for each given screen, butnot as described, or does not in-clude appropriate GUI elementsfor each layout.
COMPETENT
The screen designs include thelayout for each given screen, asdescribed, and includes appropri-ate GUI elements for each layout.
NOT EVIDENT
A scheduler is not included.
APPROACHINGCOMPETENCE
The mobile application includesa scheduler but does not includethe 11 given implementationrequirements.
COMPETENT
The mobile application includes ascheduler that incorporates all ofthe 11 given implementationrequirements.
NOT EVIDENT
The mobile application does notinclude any of the given inter-face requirements.
APPROACHINGCOMPETENCE
The mobile application includesup to 4 of the given interfacerequirements.
COMPETENT
The mobile application includesall 5 of the given interfacerequirements.
NOT EVIDENT
COMPETENT
E
:
SCREENSHOTS
F1
:
MOBILE APPLICATION DEVELOPMENT
F2
:
OPERATING SYSTEM
F3
:
DESCRIPTION OF CHALLENGES
A storyboard is not provided.
APPROACHINGCOMPETENCE
The storyboard demonstratesthe fl ow of the mobile applica-tion but includes only some ofthe menus and screens frompart B.
The storyboard demonstratesthe fl ow of the mobile applicationand includes all of the menus andscreens from part B.
NOT EVIDENT
Screenshots are not provided.
APPROACHINGCOMPETENCE
The screenshots provided donot demonstrate the creation ofa deployment package.
COMPETENT
The screenshots provideddemonstrate the creation of adeployment package.
NOT EVIDENT
An explanation of how the appli-cation would be different is notprovided.
APPROACHINGCOMPETENCE
The explanation of how the ap-plication would be different ifdeveloped for a tablet includes adiscussion of either fragmentsor layouts, not both. Or thereare errors in the explanation.
COMPETENT
The explanation of how the appli-cation would be different if de-veloped for a tablet includes bothan accurate discussion of bothfragments and layouts.
NOT EVIDENT
The identifi cation of the mini-mum and target operating sys-tem is not provided.
APPROACHINGCOMPETENCE
The response identifi es eitherthe minimum SDK or the targetSDK, but not both.
COMPETENT
The response identifi es both theminimum and the target SDK.
NOT EVIDENT
A description of challengesfaced is not provided.
APPROACHINGCOMPETENCE
The response includes chal-lenges but not specifi cally re-
COMPETENT
The response describes chal-lenges faced, specifi cally duringthe development of theapplication.
F4
:
SOLUTIONS TO CHALLENGES
F5
:
DIFFERENCES
F6
:
EMULATORS
G
:
APA SOURCES
lated to the development of theapplication.
NOT EVIDENT
A description of how challengeswere overcome is not provided.
APPROACHINGCOMPETENCE
The description of how chal-lenges were overcome is not re-lated to the challenges listed inF2.
COMPETENT
The description of how eachchallenge was overcome is re-lated to the challenges listed inF2.
NOT EVIDENT
A discussion of what would bedone differently is not provided.
APPROACHINGCOMPETENCE
The response discusses at leastone aspect of the project thatwould be done differently, butdoes not specifi cally identify thechanges that would be made.
COMPETENT
The response discusses thechanges that would be made toat least one aspect of the project,were it to be done again, andspecifi cally identifi es the changesthat would be made.
NOT EVIDENT
A description of how emulatorsare used, and the pros and consof their use, is not provided.
APPROACHINGCOMPETENCE
The description of the use ofemulators but does not includethe pros and cons of using anemulator versus using a devel-opment device, or describes thepros and cons without describ-ing the use of emulators.
COMPETENT
The description of the use of em-ulators includes the pros andcons of using an emulator versususing a development device.
NOT EVIDENT
The submission does not includein-text citations and referencesaccording to APA style for con-tent that is quoted, paraphrased,or summarized.
APPROACHINGCOMPETENCE
The submission includes in-textcitations and references for con-tent that is quoted, paraphrased,or summarized but does notdemonstrate a consistent appli-cation of APA style.
COMPETENT
The submission includes in-textcitations and references for con-tent that is quoted, paraphrased,or summarized and demon-strates a consistent applicationof APA style.
H
:
PROFESSIONAL COMMUNICATION
NOT EVIDENT
Content is unstructured, is dis-jointed, or contains pervasiveerrors in mechanics, usage, orgrammar. Vocabulary or tone isunprofessional or distracts fromthe topic.
APPROACHINGCOMPETENCE
Content is poorly organized, isdiffi cult to follow, or containserrors in mechanics, usage, orgrammar that cause confusion.Terminology is misused orineffective.
COMPETENT
Content refl ects attention to de-tail, is organized, and focuses onthe main ideas as prescribed inthe task or chosen by the candi-date. Terminology is pertinent, isused correctly, and effectivelyconveys the intended meaning.Mechanics, usage, and grammarpromote accurate interpretationand understanding.
