A Credit Card Information Inquiry System (CCIIS) must be created and include inheritance and class hierarchies (a super class and subclasses). The program(s) must include inheritance concepts and applications for credit to be given for the assignment. The CIIS will allow the input of credit card data, process of the credit card data, and output of the credit card information.
More detailed info in the attached doc
OVERALL INFORMATION – CREDIT CARD INFORMATION INQUIRY SYSTEM (CCIIS) A Credit Card Information Inquiry System (CCIIS) must be created and include inheritance and class hierarchies (a super class and subclasses). The program(s) must include inheritance concepts and applications for credit to be given for the assignment. The CIIS will allow the input of credit card data, process of the credit card data, and output of the credit card information. References: Students may want to review the HealthPlans.zip at the Sample Programming Models link, as well as the chapter ten on inheritance in our textbook to help with this assignment. Credit Card Company – Superclass The credit card company superclass should include the banking account routing number, the banking branch number, banking company name, the branch banking company address, city, state, zip code, company e-mail address, and the company telephone number. Credit Card Holder – Subclass* A credit card holder subclass should include the banking account routing number, the banking branch number, credit card account holder’s account number, credit card holder account name, address, city, state, zip code, e-mail address, and the credit card holder’s telephone number. Credit Card Holder Financial Data – Subclass (public abstract class) The credit card holder financial data subclass should include the credit card account holder’s account number, type of credit card account (Business and or Personal), credit card account holder’s credit limit, previous balance, new purchases, payments, and credits/returns. The class should include abstract methods (signature header only) for the finance charge, new balance, new payment amount, as well as the credit limit check. Credit Card Holder Business Credit Card Financial Data – Subclass The credit card holder business credit card should define the abstract methods (with overriding) to calculate the interest charged, new balance, new payment amount, as well as the credit limit check. Use simple interest at an annual rate of 16 %. Be sure to define the interest rate as a final constant in the class. The new payment amount will be 3% of the new balance. If the new balance is equal to or less than zero, the finance charge, as well as the new payment amount should be zero. Also, if after all of the calculations are performed and the customer is over their credit limit, a twenty-dollar over credit limit fee should be added to the new balance. Credit Card Holder Personal Credit Card Financial Data – Subclass The credit card holder personal credit card should define the abstract methods (with overriding) to calculate the interest charged, new balance, new payment amount, as well as the credit limit check. Use simple interest at an annual rate of 13 %. Be sure to define the interest rate as a final constant in the class. The new payment amount will be 2% of the new balance. If the new balance is equal to or less than zero, the finance charge, as well as the new payment amount should be zero. Also, if after all of the calculations are performed and the customer is over their credit limit, a ten-dollar over credit limit fee should be added to the new balance. *I could have included other credit data fields, but I wanted to simplify the CCIIS. Note that the customer could have both a business, as well as a personal credit card but your program only has to check for only one type of account at a time. Additionally, I included fields (primary and foreign keys) to allow for future database application interfacing but this will not be a requirement for this assignment or this course. THE CREDIT CLASSES CONSIDERATIONS Your classes representing the credit card must include inheritance, the data fields, final constants, constructor(s), accessor and mutator methods, as well as all of the methods (in the appropriate classes) to handle all of the credit card calculations. The appropriate credit card classes should also include abstract, overloading (to handle the data coming into the credit card classes as either a String and/or int/float), as well as overriding methods. The credit card classes should not contain any programming code relating to inputting of the data or outputting or displaying of the information for this should be handled by the GUI (Graphical User Interface). In other words, no GUI programming code should be contained in any of the credit card class (.java) files. Students may want to create the UML (Unified Modeling Language) for each of the credit card classes. GRAPHICAL USER INTERFACE PROGRAM(S) Students are to create GUI programming techniques via a separate class (.java file). You can design more than one GUI .java file but only is required to interface with the credit card .java classes. All of the Java statements must be written by the student. In other words, students are NOT allowed to use an interface in an IDE (Interactive Development Environment) that generates the Java code automatically. Also, students are NOT allowed to use the API (Application Programming Interface) classes Scanner or JOptionPane for input. Students are permitted to use the JOptionPane class to display all of the credit card information. Students can use labels, button(s), radio button(s), check box(es), menus, sliders, etc., to create the GUI. Keep in mind that the GUI class must be a separate .java file from the credit card .java classes. Assume there will be multiple credit card inquiries. INPUT DATA via the GUI For the credit card classes, you GUI must be able to accept the data from the user’s screen and interface with the credit card classes. The input data to the CCIIS classes should include the credit card company data, the credit card account holder data, as well as all of the financial data. It might be helpful to draw a sketch of the screen of the input data as well. You could also consider maybe using two radio buttons on the screen to indicate whether the credit card is a Business type or Personal type as well. And depending on which radio button is clicked will determine if a Business or Personal credit card object is created. You could incorporate data validation programming techniques (try and catch, for example) but this is not required for this assignment. Make up test data when inputting the data for each credit card object. OUTPUT DETAILED INFORMATION (for each credit card object) via the GUI For each credit card information system inquiry, your program should output the following detailed information: banking account routing number, the banking branch number, banking company name, credit card account holder’s account number, credit card holder account name, address, city, state, zip code, type of credit card account (B for Business or P for Personal), credit card account holder’s credit limit, previous balance, new purchases, payments, and credits/returns, interest finance charge, new balance, new payment amount, as well as the over credit limit fee if any. If the customer is over their credit limit, a message should indicate that the customer is over their credit limit as well. Be sure to verify your program results prior to submitting your work. Students can use the JOptionPane class to display the individual credit card information. Your CCIIS should allow the user to continue to generate individual credit card statements for each credit card inquiry until the user decides to stop the program (the user clicks the EXIT button in the GUI, for example). OTHER PROGRAMMING INFORMATION You can use an internet search engine to find the correct formulas to perform the calculations, as well as to help in resolving problems you may encounter as you are working on your solution. DOCUMENTATION VIA IDE Students may want to generate documentation of the Credit class file(s) contents via the IDE (for example, in jGRASP, use File, Generate Documentation and in NetBeans, use Run, Generate JavaDoc) for their reference only. You do not have to submit the generated documentation with this assignment.