Code must be in C++ language.

Problem: The invoice-printing program has an unfortunate flaw-- it mixes "application logic", the computation of total charges, and "presentation", the visual appearance of the invoice. HYPOTHETICAL: To appreciate this flaw, imagine the changes that would be necessary to draw the invoice in HTML, for presentation on the Web. Reimplement the program, using a separate 'InvoiceFormatter' class to format the invoice. That is, the 'Invoice', 'Address', Lineltem' and 'Product classes are no longer responsible for formatting. However, they will acquire other responsibilities, because the InvoiceFormatter class needs to query them for the values that it required. It is strongly recommended that your draw a small UML for each class, and plan how it will work