It took some time to achieve the product I was looking for, but we eventually got there. I do feel like a lot of hard work was put into this, and it even exceeded the page requirement. I'm pretty pleased overall. I give my thanks.
you are designing an application that will help keep track of sales for your company. This sales data may be shared with potential clients. There are three types of accounts that track sales for your company: supplies, services, and paper. All sales accounts will have an account id. You will need attributes to keep track of the number of hours and rate per hour of services provided. You will need attributes to keep track of the number of pounds of paper sold and the price per pound. You should also keep track of the total sold in supplies. In addition to the following required attributes for supplies, services and paper account classes, feel free to include additional attributes that you think are appropriate. Your management wants the application to be easy to maintain and to promote code reuse as much as possible. You propose that this can be best achieved by utilizing object-oriented design principles and you want to incorporate an inheritance hierarchy with the account types. The first step of your design process is to design and present to the team an Account inheritance hierarchy. Create a class diagram for the Account inheritance hierarchy. Your subclasses should be Supplies, Services, and Paper. Explain your class diagram and answer the following: How does this inheritance hierarchy promote code reuse? How does this inheritance hierarchy make the application easier to maintain? If in the future, if another type of account is needed, what are the steps for adding this new account type to your design?
Using NetBeans/Java , implement your previous class diagram. Your application will use the Accounts inheritance hierarchy . There are three types of sales accounts that track sales for your company: supplies, services, and paper. Create a test class that tests each subclass’s constructor and display each instance created. Override the toString() method so that your object data is printed.
For now, include your pseudocode, UML class diagram and verbiage that explains your design
Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.
You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.Read more
Each paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.Read more
Thanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.Read more
Your email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.Read more
By sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.Read more