CS 360 Southern New Hampshire University Development in Android Studio Java Project In the documents provided, I am tasked to create a Campsite Locator app

CS 360 Southern New Hampshire University Development in Android Studio Java Project In the documents provided, I am tasked to create a Campsite Locator app in Android Studio version 3.6 using the Java programming language. In the attached documents, there is a rubric with the project requirements, a document that showcases what my application needs to incorporate, and a document with my Wireframing, which is generally what I need the application to basically look like. It can look a little different, or more detailed – what I have in that document is just a rough sketch/skeleton. I need the user to be able to open the app, log into their account, and then be able to use the app to: search for campsites using a map and searching/filtering abilities, “favorite” their preferred campsites, share campsites via Instagram/social media, manage their settings, contact and rate the application, and log out. The details of all these are within the three documents. If you have any questions regarding specifics, let me know! CS 360 Final Project Requirements and Selection
Overview: The final project for this course is the creation of an Android Mobile application with annotated source code. This document contains the
requirements for your final project. Some of the requirements are very specific, while others give you the opportunity to think creatively and implement
your own design ideas, given the requirements provided. Do not hesitate to contact your instructor with any questions or uncertainties you have.
During Module One, you will select one of the four fictitious business requirements as well as select specific functionality using the associated
requirements matrix. The process of selecting your mobile app project is as follows:
Step One: Review all four fictitious business requirements.
Step Two: Select one of the four fictitious business requirements. Once you make your selection, you will use that set of requirements to inform your
mobile app design and development work throughout the term, culminating in the final project.
Step Three: Review the requirements matrix for the mobile app project you selected.
Step Four: Make the appropriate annotations on the requirements matrix to reflect your selections. If you neglect to make a selection in any of the given
sections, your instructor will make your selections for you. Any changes to your selections must be approved by your instructor.
Step Five: Submit your updated requirements matrix.
Fictitious Business Requirements: Campsite Locator (CSL)
Description: CSL Inc. wants a mobile application that can be used to locate and review campsites.
Target Audience: Campers, glampers, and boondockers
Required Functionality
• Users should be able to search for campsites based on name, city, and feature.
• Users should be able to rate sites and change their own ratings.
• Users should be able to search for sites in their area based on their current location.
• Users should be able to search for sites near a user-entered location.
• Users should be able to add/remove sites from their “favorites.”
• Users should be able to add new sites to the database.
Required Features
• Intuitive user interface
• Consistent user experience
• SQLite database for campsites (hard code at least 12 fictitious or real sites)
• Secure user authentication with credentials stored on local device
• Social media integration
• Additional functionality (see requirements matrix for options)
Requirements Matrix
Campsite Locator (CSL)
Student name: Esmeralda Dodd
Date submitted: 03/08/2020
Section One: Core Functionality (All Required)
• Android app for phone and tablet
• User-specific “favorites” feature
• SDK 24: Android 7.0 (Nougat)
• “About the App” functionality
• Robust search capabilities (see project details)
• “Contact Us” functionality
• Campsite database
• “Rate Us” functionality
Section Two: Maps API Integration (All Required)
• Interface with database search results
• Location services
Section Three: Data Storage (All Required)
• SQLite database for campsite data
• Local storage for login information
Section Four: Social Media Integration (Select One)
☐ Facebook
☐ Twitter
☐ Pinterest
☒ Instagram
Section Five: Additional Functionality (Select One)
☐ Camera integration
☐ Live internet search
☐ Photo gallery
☐ Microphone integration
☐ Calendar integration
☐ Motion sensor
☐ Bluetooth
☐ Media player
☒ In-app advertising
Section Five Details: Provide specifics regarding design and implementation of the selected “additional functionality.” Alternatively, you can
propose additional functionality not listed above (subject to instructor approval). Provide specifics regarding design and implementation
plans.
There will be a login screen to access the application once it is opened where a user will input their username and password. If they log in
unsuccessfully for more than five times, they will no longer be able to log in.
Notes from student:
This will be a challenge for me as I am currently unsuccessfully
running programs using Android Studio on my personal computer. I
will continue attempting to correct the issues that are arising but
would like some assistance in the matter.
Notes from instructor:
Fictitious Business Requirements: Local Coffee Shop (LCS)
Description: LCS Inc. wants a mobile application so their customers can order items for pickup.
Target Audience: Teen and adult coffee drinkers in local area (relevant to LCS Inc.)
Required Functionality
• Users should be able to browse available items.
• Users should be able to order items.
• Orders, including quantity, should be editable.
• Submitted orders should be viewable.
• There should be simulated order fulfillment.
• There should be simulated payment.
Required Features
• Intuitive user interface
• Consistent user experience
• SQLite database for coffee shop e-commerce items (hard code at least 12 different items)
• Secure user authentication with credentials stored on local device
• Social media integration
• Additional functionality (see requirements matrix for options)
Requirements Matrix
Local Coffee Shop (LCS)
Student name:
Date submitted:
Section One: Core Functionality (All Required)
• Android app for phone and tablet
• “Check on Order” feature
• SDK 24: Android 7.0 (Nougat)
• “About Us” feature
• Simulated e-commerce (see project details)
• “Contact Us” feature
• E-commerce database
• “Rate Us” feature
• Order review/edit/submission
• “Find Us” feature
Section Two: Maps API Integration (All Required)
• “Get Directions” function
• Location services
Section Three: Data Storage (All Required)
• SQLite database for e-commerce data and orders
• Local storage for login information
Section Four: Social Media Integration (Select One)
☐ Facebook
☐ Twitter
☐ Pinterest
☐ Instagram
Section Five: Additional Functionality (Select One)
☐ Camera integration
☐ Live internet search
☐ Photo gallery
☐ Microphone integration
☐ Calendar integration
☐ Motion sensor
☐ Bluetooth
☐ Media player
☐ In-app advertising
Section Five Details: Provide specifics regarding design and implementation of the selected “additional functionality.” Alternatively, you can
propose additional functionality not listed above (subject to instructor approval). Provide specifics regarding design and implementation
plans.
Notes from student:
Notes from instructor:
Fictitious Business Requirements: Ancestry Archive App (AAA)
Description: AAA Inc. wants a mobile application so users can create, store, and share their personal ancestry tree.
Target Audience: Teenagers and adults interested in their family genealogy
Required Functionality
• Users should be able to create, read, update, and delete data.
• Users should be able to view their ancestry tree data (does not have to be graphical).
• Uses should be able to obtain map data for each ancestor’s location.
• Users should be able to obtain driving directions to each ancestor’s location.
Required Features
• Intuitive user interface
• Consistent user experience
• SQLite database for ancestry
• Secure user authentication with credentials stored on local device
• Social media integration
• Additional functionality (see requirements matrix for options)
Requirements Matrix
Student name:
Ancestry Archive App (AAA)
Date submitted:
Section One: Core Functionality (All Required)
● Android app for phone and tablet
● CRUD database functionality
● SDK 24: Android 7.0 (Nougat)
● “About the App” functionality
● Ancestry capabilities (see project details)
● “Contact Us” functionality
● Ancestry database
● “Rate Us” functionality
Section Two: Maps API Integration (All Required)
● Show location of ancestor
● Location services
● “Get Directions” functionality
Section Three: Data Storage (All Required)
● SQLite database for ancestors
● Local storage for login information
Section Four: Social Media Integration (Select One)
☐ Facebook
☐ Twitter
☐ Pinterest
☐ Instagram
Section Five: Additional Functionality (Select One)
☐ Camera integration
☐ Live internet search
☐ Photo gallery
☐ Microphone integration
☐ Calendar integration
☐ Motion sensor
☐ Bluetooth
☐ Media player
☐ In-app advertising
Section Five Details: Provide specifics regarding design and implementation of the selected “additional functionality.” Alternatively, you can
propose additional functionality not listed above (subject to instructor approval). Provide specifics regarding design and implementation
plans.
Notes from student:
Notes from instructor:
Fictitious Business Requirements: Personal Portfolio App (PPA)
Description: PPA Inc. wants a mobile application so users can create, edit, and share an ePortfolio consisting of text, images, and videos.
Target Audience: Late-teens and adults that want to compile an ePortfolio for showcasing their skills
Required Functionality
• Users should be able to create, read, update, and delete data.
• Users should be able to play any playable media in their ePortfolio.
• Users should be able to obtain map data for a job interview.
• Users should be able to obtain driving directions to the job interview site.
Required Features
• Intuitive user interface
• Consistent user experience
• SQLite database for ePortfolio assets
• Secure user authentication with credentials stored on local device
• Social media integration
• Additional functionality (see requirements matrix for options)
Requirements Matrix
Personal Portfolio App (PPA)
Student name:
Date submitted:
Section One: Core Functionality (All Required)
• Android app for phone and tablet
• CRUD database functionality
• SDK 24: Android 7.0 (Nougat)
• “About the App” functionality
• Robust ePortfolio capabilities (see project details)
• “Contact Us” functionality
• ePortfolio asset database
• “Rate Us” functionality
Section Two: Maps API Integration (All Required)
• Show location of job interview
• Location services
• “Get Directions” functionality
Section Three: Data Storage (All Required)
• SQLite database for ePortfolio assets
• Local storage for login information
Section Four: Social Media Integration (Select One)
☐ Facebook
☐ Twitter
☐ Pinterest
☐ Instagram
Section Five: Additional Functionality (Select One)
☐ Camera integration
☐ Live internet search
☐ Photo gallery
☐ Microphone integration
☐ Calendar integration
☐ Motion sensor
☐ Bluetooth
☐ Media player
☐ In-app advertising
Section Five Details: Provide specifics regarding design and implementation of the selected “additional functionality.” Alternatively, you can
propose additional functionality not listed above (subject to instructor approval). Provide specifics regarding design and implementation plans.
Notes from student:
Notes from instructor:
CS 360 Final Project Requirements and Selection
Overview: The final project for this course is the creation of an Android Mobile application with annotated source code. This document contains the
requirements for your final project. Some of the requirements are very specific, while others give you the opportunity to think creatively and implement
your own design ideas, given the requirements provided. Do not hesitate to contact your instructor with any questions or uncertainties you have.
Fictitious Business Requirements: Campsite Locator (CSL)
Description: CSL Inc. wants a mobile application that can be used to locate and review campsites.
Target Audience: Campers, glampers, and boondockers
Required Functionality
• Users should be able to search for campsites based on name, city, and feature.
• Users should be able to rate sites and change their own ratings.
• Users should be able to search for sites in their area based on their current location.
• Users should be able to search for sites near a user-entered location.
• Users should be able to add/remove sites from their “favorites.”
• Users should be able to add new sites to the database.
Required Features
• Intuitive user interface
• Consistent user experience
• SQLite database for campsites (hard code at least 12 fictitious or real sites)
• Secure user authentication with credentials stored on local device
• Social media integration
• Additional functionality (see requirements matrix for options)
Requirements Matrix
Campsite Locator (CSL)
Student name:
Date submitted:
Section One: Core Functionality (All Required)
• Android app for phone and tablet
• User-specific “favorites” feature
• SDK 24: Android 7.0 (Nougat)
• “About the App” functionality
• Robust search capabilities (see project details)
• “Contact Us” functionality
• Campsite database
• “Rate Us” functionality
Section Two: Maps API Integration (All Required)
• Interface with database search results
• Location services
Section Three: Data Storage (All Required)
• SQLite database for campsite data
• Local storage for login information
Section Four: Social Media Integration (Select One)
☐ Facebook
☐ Twitter
☐ Pinterest
☒ Instagram
Section Five: Additional Functionality (Select One)
☐ Camera integration
☐ Live internet search
☐ Photo gallery
☐ Microphone integration
☐ Calendar integration
☐ Motion sensor
☐ Bluetooth
☐ Media player
☒ In-app advertising
Section Five Details: Provide specifics regarding design and implementation of the selected “additional functionality.” Alternatively, you can
propose additional functionality not listed above (subject to instructor approval). Provide specifics regarding design and implementation
plans.
There will be a login screen to access the application once it is opened where a user will input their username and password. If they log in
unsuccessfully for more than five times, they will no longer be able to log in.
Notes from student:
Notes from instructor:
Esmeralda Dodd
CS 360: Stepping Stone 2: Wireframes
Below is what the user will see when they first open the application. It will prompt them to enter a
username and password, and then click on the arrow button to initiate signing in.
Below is the list that comes up when the user clicks on the arrow within the circle. This is the menu that
they can select from, consisting of Favorites, Locate Campsites, About Campsite Locator, Contact Us,
Rate Us, Settings, and Log Out.
The below/next six images represent the pages when the user selects any of the options from the menu.
Below is the image of what the user will see when they have entered in location preferences when
searching for campsites. They will be able to see a map, as well as a list of local/corresponding
campsites, and will also be able to edit their search. After clicking on a campsite, they will be able to
save it to their Favorites, where they can also share that campsite as a post to Instagram.

Purchase answer to see full
attachment