Assignment InstructionsComplete the following steps for this assignment: List the employee IDs and names for all employees. List all the product information including name, descriptions, and category names. List all the orders for a specific customer based on the order date. List all the customers ordered by last name. List all product names that have been ordered. Count the number of orders processed for each employee. Insert a new unique customer. Insert a new order for three units of some product. Update the database to subtract 3 from the quantity available for the previously ordered product. Take screen shots of your MySQL Workbench screens showing the results of each of the above tasks. SQL: EXERCISES USING SELECT, INSERT, UPDATEOverviewOnce you have data in the database, it is important to be able to query the database using SQL statements to retrieve and modify information from the database. Some of these queries will be for reporting, while others can be used to create dynamic input fields such as drop-down boxes. The SQL SELECT statement in its basic structure has the mandatory SELECT clause and the FROM clause. However, many other clauses can be used, including the WHERE and GROUP BY clauses. In addition, you can perform various functions on the columns. The SQL INSERT statement provides a way to add data to a table in a database. The SQL UPDATE statement provides a way to modify data that already exist in a database table. You need to gain some experience using these SQL statements so that you are prepared to use them in your Capestra application.In this assignment, you will create various SQL statements to interact with the database. These statements (queries) will reflect functionality to be implemented within your application. Use the MySQL Workbench to do all the work in this assignment. Use the provided CreateOES.sql MySQL script to create an ‘orderentrysystem’ database. Use this script and the database that it creates as the base for the following tasks and for all remaining work in this course. This script replaces the one that you developed in Week 5.

https://classroom.udacity.com/nanodegrees/nd002/pa...OverviewIn this project, you will make use of Python to explore data related to bike share systems for three major cities in the United States—Chicago, New York City, and Washington. You will write code to import the data and answer interesting questions about it by computing descriptive statistics. You will also write a script that takes in raw input to create an interactive experience in the terminal to present these statistics.Bike Share DataOver the past decade, bicycle-sharing systems have been growing in number and popularity in cities across the world. Bicycle-sharing systems allow users to rent bicycles on a very short-term basis for a price. This allows people to borrow a bike from point A and return it at point B, though they can also return it to the same location if they'd like to just go for a ride. Regardless, each bike can serve several users per day.Thanks to the rise in information technologies, it is easy for a user of the system to access a dock within the system to unlock or return bicycles. These technologies also provide a wealth of data that can be used to explore how these bike-sharing systems are used.In this project, you will use data provided by Motivate, a bike share system provider for many major cities in the United States, to uncover bike share usage patterns. You will compare the system usage between three large cities: Chicago, New York City, and Washington, DC.The DatasetsRandomly selected data for the first six months of 2017 are provided for all three cities. All three of the data files contain the same core six (6) columns:Start Time (e.g., 2017-01-01 00:07:57)End Time (e.g., 2017-01-01 00:20:53)Trip Duration (in seconds - e.g., 776)Start Station (e.g., Broadway & Barry Ave)End Station (e.g., Sedgwick St & North Ave)User Type (Subscriber or Customer)The Chicago and New York City files also have the following two columns:GenderBirth YearData for the first 10 rides in the new_york_city.csv fileThe original files are much larger and messier, and you don't need to download them, but they can be accessed here if you'd like to see them (Chicago, New York City, Washington). These files had more columns and they differed in format in many cases. Some data wrangling has been performed to condense these files to the above core six columns to make your analysis and the evaluation of your Python skills more straightforward. In the Data Wrangling course that comes later in the Data Analyst Nanodegree program, students learn how to wrangle the dirtiest, messiest datasets, so don't worry, you won't miss out on learning this important skill!Statistics ComputedYou will learn about bike share use in Chicago, New York City, and Washington by computing a variety of descriptive statistics. In this project, you'll write code to provide the following information:#1 Popular times of travel (i.e., occurs most often in the start time)most common monthmost common day of weekmost common hour of day#2 Popular stations and tripmost common start stationmost common end stationmost common trip from start to end (i.e., most frequent combination of start station and end station)#3 Trip durationtotal travel timeaverage travel time#4 User infocounts of each user typecounts of each gender (only available for NYC and Chicago)earliest, most recent, most common year of birth (only available for NYC and Chicago)The FilesTo answer these questions using Python, you will need to write a Python script. To help guide your work in this project, a template with helper code and comments is provided in a bikeshare.py file, and you will do your scripting in there also. You will need the three city dataset files too:chicago.csvnew_york_city.csvwashington.csvAll four of these files are zipped up in the Bikeshare file in the resource tab in the sidebar on the left side of this page. You may download and open up that zip file to do your project work on your local machine.Some versions of this project also include a Project Workspace page in the classroom where the bikeshare.py file and the city dataset files are all included, and you can do all your work with them there.

DescriptionIn this assignment, you will update the Money, Date, Bill, and ArrayList classes from previous homeworks - (I have this available) - using new ideas that we have discussed in class, and you will create an ExpenseAccount class extending your ArrayList. Build a driver that will fully check the functionality of your classes and include the driver with your submission.Fix any privacy (and other) errors that were noted in your comments for the previous iteration of this homework.Modify the Money, Date, and Bill class to implement the Comparable interface. Remember that compareTo takes an Object parameter and you should check to make sure that the object that comes in is actually the correct class for the comparison, as appropriate. (How could the CompareTo method be implemented for Bill? If you were sorting a collection of Bills, how would you want them sorted? Make a reasonable choice and document your choice.)Modify the Money, Date, and Bill classes to implement the Cloneable interface. Note that Money and Date can simply copy their private instance variables, since they store only primitive and immutable types. However, you will need to override the clone method, to make it public, since it is protected in the Object class. The Bill class will need to do more, since it incorporates the Money and Date classes, which are mutable. Note that it can (and should) use the clone methods of those classes. Be sure to remove any use of the copy constructor for Money, Date, and Bill in the rest of the code (the definition can exist, but don’t use it in other classes; use the clone method instead).Build a class ExpenseAccount that extends your ArrayList. (Reminder: you are using YOUR ArrayList, not the built in Java one.) You should remove the limit on the number of bills that can be placed in an account by making your ArrayList dynamically resize itself. (You may do this either by resizing an internal array, or by implementing your ArrayList as a linked list. If your ArrayList is implemented as a linked list (for instance, by inheriting from the general List class that you made in the "Linked Lists, Stacks & Queues" homework), then make sure to include any of these other classes when you turn in this assignment.) The ExpenseAccount class is essentially an ArrayList of Bills. Your ExpenseAccount must include AT LEAST one method that you don't just inherit from the ArrayList class. What should it have? What would be useful for an expense account to have? That's for you to answer!Modify Money, Bill, and Date to implement the Serializable interface.(See for example: http://tutorials.jenkov.com/java-io/serializable.html (Links to an external site.) and https://www.tutorialspoint.com/java/java_serialization.htm (Links to an external site.) )OPTIONAL, FOR 3 POINTS OF EXTRA CREDIT: Have your ArrayList class implement the Iterable interface. Implement the Java 7 specification, not later specifications like Java 8. That is, see: http://docs.oracle.com/javase/7/docs/api/java/lang/Iterable.html The Java 8 specification includes resources to support functional programming and lambda expressions which is out of the scope of this class. Make sure your driver tests the iterable aspects of your class. (For example, you should be able to use a for each loop with your ArrayList.) If you are doing this, please submit a Canvas comment with your submission to the effect of "Extra credit: my ArrayList implements the Iterable interface", so my grader knows to check for it. Note: this is not necessarily easy. None of the students were able to figure it out last time I taught this.Build a driver that will fully check the functionality of all your classes and include the driver with your submission.Hints, Etc.Remember to follow the Coding Style Guidelines.Make sure you comment all methods and the class with javadoc comments. This includes constructors, getters, setters, etc. If you have files based on code someone else has written (e.g., is based on a skeleton), you have to javadoc comment the methods someone else wrote also. You cannot receive full-credit for the rubric's commenting criterion if you do not have a javadoc comment for every method, no matter how small. All methods should have pre- and post-conditions as well.Your code should not depend on absolute path specifications or any other environment-specific specifications. The program should not ask for user input from the console.The description for this assignment is much briefer than in some previous assignments. In particular, not much detail is given regarding what methods to have, etc. It is purposely open-ended. By this point, you should be able to design an appropriate interface to your classes as well as create an appropriate driver filled with tests. My advice is not to scrimp on the interface; include all methods one would reasonably expect objects of that class would be able to do.Classes whose names are given in this assignment description should be given that name. If you submit multiple versions, Canvas will rename your files with a "-1", etc. suffix, but that's okay. We can handle that change. But the base name of your class has to be as described.An example of questions to ask when defining an interface (for the ExpenseAccount class): What kind of data and methods should go into an ExpenseAccount class? What would you use an ExpenseAccount for? What would you want to inquire of an expense account? (If you don't know what an expense account is, do some web searches to find out.) For instance, you might be interested in knowing the total amount of expenses that is outstanding in the ExpenseAccount. You might be interested in knowing which expense is next due and unpaid and how much it is. And so on ... these are just two examples of questions you might ask of an expense account. It depends on the use cases you want the expense account to satisfy. These kinds of questions can also be asked for Bill, etc.What to turn in: Money.javaDate.javaBill.javaExpenseAccount.javaArrayList.javaany other classes you need to implement the aboveDriver.java