Reference no: EM13754663

 The use of standard Java input and output mechanisms

· The use of complex arithmetic expressions

· The use of modular design (methods)

· The use of one-dimensional arrays

As always, be sure to properly document your code. Consult the Java Coding Guidelines document for proper coding standards. Use good design principles and design the solution before attempting to write code.

Emptying a Water Tank

Water catchment systems are a critical source of water in many parts of the world. These systems collect rainwater and distribute it to a house, lodging, or neighborhood using a series of gravity-propelled plumbing. Such systems can also act as a reservoir by which local populations can "fill up" containers and transport the water to other locations.

Assume we have a full water catchment tank, shaped like a cylinder. How long would it take to empty that cylinder, if we "unscrewed" an output nozzle on the bottom? Determining the rate at which the cylinder would empty out would require knowledge of the height of the tank, the radius of the tank, and the radius of the output nozzle. Once we had this knowledge, we could apply a few simple math equations to get an approximate answer. This information would be helpful to measure the amount of water that would be used for various household uses (e.g. showers).

Exercise #1: Create a Java class called WaterTank.java. This program will simulate thedraining of a cylindrical water catchment tank. Your program will need to show how the rate at which water would exit the tank, assuming an output nozzle two inches (2") in diameter. Your inputs are as follows:

		Variable			Meaning			Valid Range
	height_of_tank				The height of the cylindrical tank, in inches		[72-240]
	radius_of_tank				The radius of the cylindrical tank, in inches		[2-36]

Note that the values above will be input from the user only once. Both inputs are double values.

Once the input is finished, your program will display an output table with three columns: time (in seconds), volume lost, and fluid height (i.e. the height of the water in the cylindrical tank). Assuming a constant flow, the volume of water in the tank will decrease to zero over time (i.e. the tank will be empty). For example, a 36-inch high cylinder with a radius of 6 inches will produce the following table:

Intial Volume: 4071.50 cubic inches.

Time	Volume Lost	Fluid Height
====	===========	============
0	0.00	36.00
1	604.69	30.65
2	1115.97	20.79
3	1378.45	8.60
4	1182.06	-1.85

Note that the last value - and only the last value - for fluid height may be less than zero. Youshould assume the tank is initially full with water. Your table should compute one value for each second, starting at zero and ending when the tank runs dry (i.e. volume of fluid in the tank is ≤ 0).

The following constants and formulas will be helpful in your calculations (r = radius, h = height):

PI (π):

3.14159265

Initial Volume of a Cylinder (i.e. the water tank):

Velocity of Outward Flow Through the Nozzle:

Volume Lost From a Cylinder At Time t:

Height of Fluid in the Cylindrical Tank at Time t:

Note that you will first need to calculate the volume of the cylinder when it is full, and output it to the screen. For each time step, you will need to calculate the volume lost. Remember that the volume lost requires you to first calculate the velocity of flow. Once calculated, the volume lost is subtracted from that initial "full" volume. Afterwards, the new height of the fluid can be calculated from this new volume. When the volume in the tank reaches zero (or less), your program should stop its calculations. Your program may use the value of PI (π) shown here for testing purposes, or use the Math.PI constant.

Your numerical output should be precise to two decimal places on the right of the decimal for all real-number data. Your ability to modularize your solution is essential (i.e. break the program into methods). You must use arrays in your solution - at least two arrays are recommended to store the volume lost and fluid height values. Be sure to properly document your code and use good design principles