Using the attached code, I need to create a single test case only with each scenario a separate method called from main. I must have at minimum code test cases to verify the major functionality of the...

Using the attached code, I need to create a single test case only with each scenario a separate method called from main.
I must have at minimum code test cases to verify the major functionality of the system:
- successfully loading account and transaction data on startup and throwing exception on errors;- Inactivating and reactivating an account

- Completing a transaction

- Adding new transaction to an account

- Removing transaction from an account

- Failing to remove a transaction from an account if status is complete

- Retrieving account using account id number

- Failing to retrieve an account if status is inactive

- Retrieving transaction using transaction id number

- Failing to retrieve a transaction if status is complete

- Changing draft transaction

- Retrieve transaction cost for a draft transaction
Make sure you use comments to document what each test case is verifying and doing. Your tests must either dynamically verify that they are successful or print data to the screen that can be manually checked to verify.
Feel free to modify the code to meet test requirements, if code is not working


OOP Project Description Requirements: You are to design and build prototype software (stand-alone application loaded on business’s local computer) to manage accounts and their transactions. Your software will be used and called by User Interface (UI) that someone else will be implementing. You will get to design the UI in software design document (SDD) but you will not be implementing it for this project. You can assume that the UI layer will be vendor’s code and packaged in a separate package than your system. Your software will load all the existing account and transactions data on startup. For this project, the data will be loaded and saved in text files on the local system (for the final product outside the scope of this project, server with database will be used) with each account and transaction saved in a separate file. UI will provide the directory of where the files will be located but the actual filename convention will be hard-coded in your Manager class and UI will not interact directly with the data storage (only through your systems’ methods). Your system will manage all the data and it has to update the files as needed to keep them current at all times. When the system starts up, UI will create an instance of your Manager class and pass it the directory where the accounts and transaction files are located. Your system will then load all the account and their corresponding transactions data. Account information will be stored with filename convention: account-id-number.txt and transactions will be stored using the filename convention of: trans-id-number-acc-id-number.txt (you can use .json or .xml extensions instead) where id-number is a unique id value for the account and for transaction ids. You can hardcode subdirectory structure and directory naming convention as you wish. After the accounts and transaction data is loaded on system startup (creation of manager instance), the user (using UI) will be able to get the list of accounts with their transactions. In addition, your system needs to provide the functionality to add new account to manager, inactivate an existing account, reactivate an account that is currently inactive, add transaction to an account, remove a transaction from an account, complete a transaction, retrieve an account for a specific id from manager, retrieve transaction from an account for a specific transaction id, and to calculate transaction cost for a draft transaction. In addition, all classes except Manager need a toString() method to return class’s formatted data that can be written to the console (or file). You can assume that the number of current accounts and transactions is small enough to load all into memory on startup. Note that UI will handle the login and authorization and access control but all are outside of the scope of the system you are designing. An account includes the following information: unique id number (String), owner information (name, mailing address, email, and phone number), list of transaction objects for that account, and status whether the account is active or inactive. When a new account is created, it must be provided id and owner information, the transaction list will be empty, and the account will be active. No duplicate accounts based on id number are allowed in manager. An account cannot be removed, only inactivated. No data can be changed for an inactive account. Once a transaction is completed, it cannot be removed from the account. The account id cannot be ever changed and status can only be changed by the inactivate/reactivate action. There are three different types of transactions allowed: purchase, travel, and rent. Each transaction object includes unique id number (String), transaction cost, date the transaction was completed (Date or Calendar) description (max 500 characters), and status (draft or completed). In addition, purchase transaction objects also have the number of items being purchased and price per item; travel transaction has the travel total cost; and rent transaction has number of days for the rental and the daily rate of the rental. Transaction object cannot exist without all the values and all values can be changed through this system except transaction id. On creation, the date of transaction is set to null, transaction cost is 0, and status is draft. These values can only be set when transaction is completed. No transaction data can be changed once transaction is completed nor can it be removed from the account and transaction cannot be reversed back to draft. Transaction cost includes a flat fee of $2.99 plus transaction specific cost calculated as follows. (1) Travel transaction: flat fee plus the travel cost (2) Purchase transaction: flat fee plus the number of items multiplied by price per item (3) Rent transaction: flat fee plus the number of days multiplied by daily rate When the account or transaction data is changed, system must update the appropriate files. It is up to you what format you use for the account and transaction files but they must be human readable text files. Your design and code must follow separation of concerns principle, so a class cannot parse nor load another classes attributes (it need to call that other classes constructor/method to do it) . You can use XML tags (you can model after Trip example) or JSON or other text formats you are familiar with or would like to use. Your system will need the following exceptions and validation to be added for the week 5 assignment: 1. When loading accounts and transactions and file(s) do not exist or there is any issue parsing file or accounts/transaction data, throw unchecked user defined exception called InvalidLoadException when violation detected. The exception will extend RuntimeException. The exception message should indicate what the detected issue was and the filename that could not be loaded or data that could not be parsed. 2. On adding account or adding transaction to an account, if duplicate account/transaction exists throw unchecked user defined exception called DuplicateObjectException when violation detected. The exception will extend RuntimeException. The generated exception message should indicate the id of the account and/or transaction and why it failed. 3. On removing transaction, if it cannot be removed for any other reason, throw unchecked user defined exception called InvalidOperationException when violation detected. The exception will extend RuntimeException. The generated exception message should indicate the id of the transaction and reason why it failed. 4. On all other issues use Java builtin exceptions such as InvalidArgumentException for parsing/validation issues and IllegalStateException with meaningful messages UI is outside the scope of your design but your system needs to have all the functionality that UI needs to satisfy the project requirements. As you design the system, you need to make sure it is consistent and it only has the interfaces (constructors, attributes and methods) that are needed by the required functionality. You cannot arbitrarily add new functionality to the system. The system you are designing will have the functionality needed to satisfy the above requirements. You will NOT be implementing the actual user interface (you will still design it though in your Software Design Document in later assignment) but you need the classes, attributes, and methods to receive and provide the information that the user interface will need. You can assume that for a complete solution there would be some other class that implements user interface (UI) with main() method and that it will call your classes/methods. Your system will not have main method except in the test class. When you implement the system, you must have at minimum code test cases to verify the major functionality of the system: successfully loading account and transaction data on startup and throwing exception on errors; successfully inactivating and reactivating an account; successfully adding new transaction to an account; successfully completing a transaction; successfully removing transaction from account and failing if already completed; successfully retrieving an account for a specific id and throwing exception if it does not exist; successfully retrieving a transaction for an account for a specific id and throwing exception if it does not exist; throwing an exception if try to update completed transaction or for inactive account; successfully changing draft transaction; retrieve transaction cost for a draft transaction; and test case to verify that files are updated when account or transaction data changes. There should be a single test class with main method and each test case scenario should be a separate method called by the main. Make sure you use comments to document what each test case is verifying and doing. Your tests must either dynamically verify that they are successful or print data to the screen that can be manually checked to verify. Week8_TBalbi_SWEN646/pom.xml 4.0.0 com.mycompany Week8_TBalbi_SWEN646 1.0-SNAPSHOT jar UTF-8 16 16 Week8_TBalbi_SWEN646/src/main/java/com/mycompany/week8_tbalbi_swen646/Account.java Week8_TBalbi_SWEN646/src/main/java/com/mycompany/week8_tbalbi_swen646/Account.java /*  * To change this license header, choose License Headers in Project Properties.  * To change this template file, choose Tools | Templates  * and open the template in the editor.  */ package com.mycompany.week8_tbalbi_swen646; import java.io.BufferedReader; import java.io.File; import java.io.FileReader; import java.io.FileWriter; import java.io.IOException; import java.util.Calendar; import java.util.Vector; import java.util.Collections; public class Account {   private String acctIdNumber;   private OwnerInformation ownerinformation;   private AccountStatus accountStatus;   private Vector  transactions;   public String toString() {       return "" + "" + acctIdNumber + "" + ownerinformation.toString() + "" + accountStatus + "" + "";   }   public int addTransaction(Transaction transaction) {       if(transaction == null)       throw new IllegalArgumentException("Parameter values cannot be null");           if(getAccountStatus().equals(AccountStatus.Inactive))       throw new IllegalStateException("Account is inactive and cannot be changed");     else     {       // check transaction number       for(Transaction t: transactions)       {         if(t.getTransIdNumber().equals(transaction.getTransIdNumber()))           throw new DuplicateObjectException("This transaction id number already exists", transaction.getTransIdNumber());       }       this.transactions.add(transaction.clone());            }     return transactions.size();   }   public Account clone() {       // create new object     Account acc_clone = new Account(getAcctIdNumber(), getOwnerInformation());     acc_clone.accountStatus = getAccountStatus();     acc_clone.transactions = getTransactions();     return acc_clone;   }   public void removeTransaction(String transIdNumber) {     if(getAccountStatus().equals(AccountStatus.Inactive))       throw new IllegalStateException("Account is inactive and cannot be changed");          Transaction transaction = null;     int index = -1;     for(Transaction t: transactions)     {       if(t.getTransIdNumber().equals(transIdNumber))       {         transaction = t;         break;       }       index++;     }     if(transaction != null)     {       // check if transaction has not been completed       if(transaction.getTransactionStatus().equals(TransactionStatus.Complete))         throw new InvalidOperationException(transIdNumber, " ", "Transaction has been completed and cannot be modified.");       transactions.remove(index);       File file = new File("trans-id-" + transaction.getTransIdNumber() + ".xml");       file.delete();     }     else       throw new IllegalArgumentException("Parameter values cannot be null");        }   public Transaction retrieveTransaction(String transIdNumber) {       if(getAccountStatus().equals(AccountStatus.Inactive))       throw new IllegalStateException("Account is inactive and cannot be changed");     for(Transaction t: transactions)     {       if(t.getTransIdNumber().equals(transIdNumber))         return t;     }     return null;   }   public void transSaveToFile(String transIdNumber) {     try     {       FileWriter writer = new FileWriter("trans-id-" + transIdNumber + "-acct-id-" + acctIdNumber + ".xml");       for(Transaction t: transactions)       {         if(t.getTransIdNumber().equals(transIdNumber))           writer.write(t.toString());       }       writer.close();     }     catch(IOException ex)     {       ex.printStackTrace();     }   }   public void completeTransaction(String transIdNumber) {     Transaction t = retrieveTransaction(transIdNumber);     if(t == null)       throw new IllegalArgumentException("Parameter values cannot be null");     if(getAccountStatus().equals(AccountStatus.Inactive))       throw new IllegalStateException("Account is inactive and cannot be changed");     t.transactionStatus = TransactionStatus.Complete;     t.finalTotalCost = t.calculateFinalTotalCost();     t.dateOfTrans = Calendar.getInstance();   }   public Vector  getTransactions() {       return transactions;   }   public Account(String acctIdNumber, OwnerInformation ownerInformation) {     // validate parameters     if(acctIdNumber == null ||ownerInformation == null)       throw new IllegalArgumentException("Parameter values cannot be null");     else     {       this.transactions = new Vector();       this.acctIdNumber = acctIdNumber;       this.ownerinformation = ownerInformation;       this.accountStatus = AccountStatus.Active;       Collections.emptyList();                   }   }   public String getAcctIdNumber() {       return acctIdNumber;   }   public OwnerInformation getOwnerInformation() {       return ownerinformation;   }   public void setOwnerInformation(OwnerInformation info) {     if(getAccountStatus().equals(AccountStatus.Inactive))       throw new IllegalStateException("Account is inactive and cannot be changed");     ownerinformation = info;   }   public AccountStatus getAccountStatus() {       return accountStatus;   }   public Account(String fileName) throws Exception {     // validate fileName     File f = new File(fileName);     if(!f.exists() ||f.isDirectory())       throw new InvalidLoadException(fileName, "Filename is not valid.");     if(getAccountStatus().equals(AccountStatus.Inactive))       throw new IllegalStateException("Account is inactive and cannot be changed");     else     {         this.transactions = new Vector();         BufferedReader reader = new BufferedReader(new FileReader(fileName));         // read first line         String line = reader.readLine();         this.acctIdNumber = line;         OwnerInformation info = new OwnerInformation (line.substring(line.indexOf("") + 10, line.indexOf("")));                                             this.ownerinformation = info;         this.accountStatus = AccountStatus.Active;         reader.close();     }        }   public void editAccount(Account account) {     if(account == null)       throw new IllegalArgumentException("Parameter values cannot be null");     if(getAccountStatus()