CompetencyIn this project, you will demonstrate your mastery of the following competency:Develop and launch a fully functional mobile applicationScenarioYour app UI design has been received positively by the client, which means you are now ready to proceed to the final stages of the development process. The client is eager to see the completed product ready for launch. To make this happen, you know that most of your time will need to be spent creating functional, error-free code that will run the app.However, you also know there are further steps that must be completed after the coding in order for the app to be made widely available. To support your client with this part of the process, you will need to create a recommended launch plan that details how to successfully reach the client’s intended users.DirectionsBegin by reviewing any feedback you received on your previous Project One and Project Two work. Next, open the Android Studio project where you developed the UI for your app in Project Two. Before you begin coding, be sure you have incorporated necessary changes to your UI design as this will help enable your success moving forward. You will be using the Android Studio Editor Window to view and write your Java code.App Code DesignDevelop code that allows a user to log in. As you develop your code, use the Android Emulator feature of Android Studio to test your code. Your app should work for users that both do and do not have accounts. This means you should focus on the following functionality:The app should check the username and password against the database when the user attempts to log in.If the user has never logged into the application before, the user should be able to create a new login and password. The application needs to save these to a table in the database.Develop code to create a database shell and display that database’s information on a user’s screen using a grid. The SQLLite database you create will depend on the option you selected in Project One and will store either inventory items, event details, or daily weight. Any information needed for your application to function correctly should be held in the database, but remember you are only creating the shell for the database so its contents can later be populated by a user. Note that you will need tables in the database to store user information when it is not being displayed in the grid. This database will be persistent so no user information is lost when the app is closed. Be sure to test your code often with the Android Emulator. Your completed database should allow a user to accomplish the following:Create: The user should be able to add items to a database.Delete: The user should be able to remove items from a database.Update: The user should be able to change the value associated with individual database items (e.g. the number of a specific item in an inventory or the date of an event).Read: The user should be able to view all of the database items displayed as a grid.Develop code that prompts users for permission to send SMS messaging notifications and makes the app function based on the individual user's response. Keep in mind that the user of your application might deny access to the permissions needed for sending text messages via SMS. If they do, your application should still continue to function, just without this feature. Test both possible options for user response by using the Android Emulator. When you do, you will be looking for the following outcomes:If the user grants permissions, the application should send alerts to the user as SMS messages. The alerts correspond to the specific notification trigger of the application you chose (low inventory, an upcoming event, or reaching a goal weight).If the user denies permission, then the rest of the application should still continue to function without the SMS messaging notification feature.Employ industry standard best practices such as in-line comments and appropriate naming conventions to enhance readability of code. This should be evident throughout all of the code you create for this project and will be assessed comprehensively. Some things to ask yourself as you code are:Have I kept my classes concise?Is my style consistent throughout the code?Would my naming conventions make sense to anyone else who looked at my code?Do my in-line comments contain enough useful information?App Launch PlanDetermine a plan for launch of the application that outlines all necessary components to support your app. Once you have completed the code for your app, there are a few more steps required to bring your app to the market. In this project you will not actually have to launch your app in the app store but you will need to outline a comprehensive plan for launch that will prepare you to bring your app to market. Later in this course you will have the opportunity to officially launch your app, if you choose, since it will be an excellent accomplishment to share as you progress along your professional pathway. For now, address the following questions as you write your plan:What will be included in your app’s description and what kind of icon will best represent your app once it is made available in the app store?Which version(s) of Android will your app successfully run on? Have you included the most current version? Note that with each version of Android, new components are introduced that add considerations and challenges in the development.What permissions will your app ask for? Be sure these are only permissions that are necessary for your app to run. For example, does your manifest ask for permission to record phone audio when your app does not use it?What is your plan for monetization of the app? Consider whether your app will include ads, require a one-time payment, both, or neither.What to SubmitTo complete this project, you must submit the following:App Code DesignSubmit a ZIP file of the completed Android Studio project folder for your fully functional, error-free application. Your professor will grade your work in the ZIP file but you may also compile and submit an APK file. This would be useful to you because if there are any issues with the code, Android Studio will not generate the APK file. Therefore you can use the APK file to check your work and demonstrate overall functionality to your instructor.App Launch PlanSubmit your completed launch plan as a Microsoft Word document of 2-3 pages in length. Use double spacing, 12-point Times New Roman font, and one-inch margins. The file name should include your name and the app option you have been using for the projects.

Read through the whole project before beginning.  Based on the information provided below, you will be creating Database Design Language and Entity Relationship Diagram. Database Design Language (DBDL) Use Word to create the DBDL. When creating the DBDL, list out all relations in 3NF.  On each relation, create functional dependencies to make sure all relations are in 3NF!! Entity Relationship Diagram (ERD) An ERD is the visually representation of the database structure.  Draw the diagram for the scenario using LucidChart. When drawing the objects, be sure to use the correct shapes and syntax. List out all alternate keys, secondary keys, and foreign keys under the relation using the correct syntax.   An online movie database keeps tracks of information on movies, actors, directors, the genre of movies, and the characters portrayed by each actor in the movie.  The specific data requirements for the database is summarized as follows: Each movie is identified by a unique number.  Other information kept on each movie is the name of the movie, length of the movie, release date and parental rating. An actor is identified by a unique number, first name, last name, date of birth and gender.  A director is identified by a unique number, first name, last name, date of birth and gender. A character is identified by a unique number, first name, and last name.  A genre is identified by a unique number and the description of the genre. A Movie has multiple actors (or none at all). An Actor can play multiple roles in a movie. A character must be associated with a movie and an actor.  A character can be in multiple movies. (i.e. Sequels) A character can be portrayed by multiple actors in a movie. (i.e. Character in a movie has a younger and older version – two actors need to play the part). A Movie can have multiple directors (or none at all). A movie must have at least one genre (or could have many).

InstructionsThis assignment has two parts:Hands-on labCourse projectPart I—Hands-on LabWrite the following SQL statements in Microsoft Access by using the Books database from Week 2 Assignment 2. Once complete, copy and paste the SQL statements in a Microsoft Word document:Write SQL statements:To update the publisher name from READ WITH US to READ FOR USTo verify the updated name field for the publisher with ID 6To make the following updates to the Publisher table (be careful with WHERE):Make Contact="John Travolta" for publisher with ID number 4Make Phone=888-999-7777 for TEXT AND MORETo list the customer numbers and names of all individuals who have purchased books in the information systems categoryTo identify the book written by an author with the last name Cain. Perform the search by using the author nameTo produce a list of all the customers who live in the state of Indiana and have ordered books on information systemsTo display a list of all the books in the Books table. If a customer has ordered a book, list the corresponding order number and the state in which the customer residesTo identify the authors of the books ordered by Sheila Smith. Perform the search by using the customer nameTo list the customer numbers and names of all the individuals who have purchased books in the children categoryTo add the following items to the Books table:ISBNTitleAuthorPubDateCostRetailCategoryPubID1234567890A Good BookJohn Jeffries10/11/200513.515.00Non-Fiction72314569874Trains for EveryoneCorey Berkey12/15/201110.2525.25Children81598745682Eating InSusan Smythe09/09/201220.0030.50Cooking699954123654Another Vampire StoryAnn Oats09/05/201011.2313.52Fiction41025874159Databases are Fun!Tony Stevens01/01/20134.125.23Information Systems9To delete the last record addedTo update the name Susan Smythe to Susan Smythe-BrownPart II—Course ProjectCourse Project Part 3—E-R ModelingNow that you have defined your E-R model and project description in the project you started and worked on in Weeks 1 and 2, start converting your logical E-R model to a physical model.In this week, complete the following tasks:In a Microsoft Excel spreadsheet, define columns with the following headings:Primary KeyName of ColumnNull (NorY)DatatypeDescriptionForeign KeyForeign Key TableEach row will contain your rows for this table.Fill out the columns row-wise.Using Microsoft Visio or Microsoft Paint, create an E-R model of the six tables from your spreadsheet for developing the business requirements and constraints that will maintain the business logic for your database.The E-R model should be readable and should map to the spreadsheet and the project description.It should have all the cardinality and optionality defined.Assignment DeliverableAfter you complete the lab and course project, collate the information from both in a 3- to 4-page report in a Microsoft Word document.Submission DetailsName your report SU_ITS3102_W3_A2_LastName_FirstInitial.doc.Name your Excel spreadsheet SU_ITS3102_W3_A2_LastName_FirstInitial.xls.If you use Microsoft Paint to draw your E-R diagram, name your E-R diagram file SU_ITS3102_W3_A2_LastName_FirstInitial.bmp.If you use Microsoft Visio to draw your E-R diagram, name your E-R diagram file SU_ITS3102_W3_A2_LastName_FirstInitial.vsd.Submit your report, spreadsheet, and E-R diagram to the Submissions Area by the due date assigned.