[Solved] CS5044 Cloud Cost Calculator

OverviewIn this assignment, you will develop your first complete class, following the techniques described in Chapter 3. You will also need to use several techniques from Chapter 4 regarding data types and arithmetic, in order to manipulate the numeric values involved, conditionals are not to be used as we have yet to go over them. You will also develop some tests to help ensure your class is working properly.

DetailsStart a new project in Eclipse for this assignment. In this project, youll develop a class called CloudCostCalculator in the edu.vt.cs5044 package that implements a simple model for tracking the costs incurred when purchasing on-demand services from a contrived cloud computing (Links to an external site.) provider. The comments in the provided file will describe all of the policies involved. A basic template of the required class file is provided to help get you started. You should assume that the methods of your class will be called by other components within some other billing system (but external to this assignment). Each methods required behavior is already described by Javadoc comments in the provided source code file; these comments act as your requirements by specifying the expected behavior for each method.

You have freedom to choose the number and types of instance variables you use, the approaches to the calculations, and other such internal design considerations. This is the most fundamental concept of encapsulation in an object-oriented system. It doesnt matter exactly how your class works, as long as it works properly whenever the public accessor and mutator methods are invoked. There are many possible designs, and there is no single right or best solution that meets all of the functional expectations.

However, youre expected to follow the idiomatic style of Java, and good design practices, so not every possible solution will earn all the available points.

Note that our CloudCostCalculator class isnt a complete stand-alone program. It cant be launched on its own, as it doesnt include a main() method. Further, no methods accept any user input, nor do any methods produce any user output. This is intentional! This class is meant to be just one small component of a much larger system.

Still, you need to execute your code somehow, to ensure that it works correctly. To do this, youll need to develop a second class called CloudCostCalculatorTester (also in the edu.vt.cs5044 package) in order to exercise your CloudCostCalculator class. Your tester class does have a main() method, and will generally use System.out.println() to display both the expected and the actual results to the console, as suggested in the textbook. A sample tester class is provided, to get you started, but youre expected to add several more test cases to this.

DownloadsCloudCostCalculator.java This class file contains all the method declarations you need, along with Javadocs describing their required behaviors, but the method implementations are all just placeholders. You will need to design and develop the method implementations, adding private instance variables as necessary. You are encouraged to add private methods as well, wherever it can help reduce redundancies in your code. Please ensure you dont add, remove, or change the headers of any of the public methods. The existing public methods represent the external interface of your class, and must be retained. Other components of the larger system (outside of this assignment) will expect to work with your class using exactly these methods.CloudCostCalculatorTester.java This class file runs some basic functional tests on CloudCostCalculator objects. Be sure to read through this file before starting the assignment, as there are many sample calculations that might help clarify some of the behavioral requirements. Youre expected to develop additional test code in this file. You must add enough tests to exercise each of the CloudCostCalculator methods at least four times each (above and beyond the existing tests).expected_output.txt This is the expected output of running the above tester code (as provided) on a properly working implementation.