This exercise will familiarize you with using polymorphic containers and text processing in Java.We will use the idea of “form letter processing” to convey these ideas.Form letters are a way of combining a form letter template (text and placeholders for substitution) with a data collection (say, names and addresses) and some computed variables (such as the date) to create a useful result (say, a personalized business letter).In this exercise we will create the structures for the template, and show that we can process the template to produce the appropriate results.In the followup exercise for next week, the data collections and output will use files rather than internal storage.What to Hand InPlease hand in a listing for each program requested, formatted in an easy-to-read style. Ensure your name, and the name of the file is available in a comment at the top of the file. You do not need to submit files from the homework starter files that are unchanged. Also, ensure that you have a sample of the output from the program. If your program fails to compile, hand in your error listing as your output. For electronic submission, “zip” your submission together into a single file, to ensure nothing is missing; For each question asked, provide one or two sentences summarizing your answer. Please be both complete and succinct.ProblemsCreate and Test a Form Letter Start with the homework starter files. These will give you a good framework for creating your FormLetterTemplate.Examine the FormLetterEntry abstract class, and create the two derived classes TextEntry and DataItemEntry. Be sure to implement all the abstract methods in each derived class.Add fields and methods to the FormLetter class. These should include a container for FormLetterEntrys, appropriate constructors, and the methods outlined in the class starter.Compile and run the FormLetterHello program. When you have implemented the above, it should compile and run.Capture the output of your test run for your submission.Create a new class called MyFormLetter, which represents another example of a form letter. It must contain at least one TextEntry and at least one DataItemEntry. Compile it, run it, and same the output of your test run for your submission.Optional: Run the JUnit tests and make them all pass (this might take minor changes to your classes). You will need to ensure the JUnit libraries are on your classpath. If you submit this optional part, be sure to capture the output showing the JUnit tests passed and include with your submission.Question: Describe why these files will not compile as they are. Be specific, and display some confirmation for your description. The answer may be stored in a text file, or incorporated as comments in your code.NotesYou can put the sample classes into your NetBeans environment by putting all the files except FormLetterTest.java into the source directory, and this remaining file into the test directory. Similar instructions for Eclipse. Or, you can also simply use ant with the provided build.xml file.While you could create the TextEntry and DataItemEntry at the bottom of the FormLetterEntry.java, please instead create them as separate, public classes.Note that while doing input and output in this framework, you should always use the out instance passed in as a parameter, rather that System.out. This will ensure that all your output happens properly.Note that the FormLetter class must store an ordered list of FormLetterEntrys. This is best handled by using one of the Collections classes in the java.util package. Various methods in your FormLetter class will iterate through the collection. For example, a List of FormLetterEntry would be a reasonable collection, instantiated by, say, a LinkedList or ArrayList of FormLetterEntry. Because your ordered list stores FormLetterEntry instances, it will be able to store TextEntry objects and DataItemEntry objects.Note that the Properties can contain things that might change for each letter (e.g., name) as well as computable things (e.g., date).Your addTextEntry method creates a new TextEntry using the provided text and adds it to your listYour addDataItemEntry method creates a new DataItemEntry using the provided name and adds it to your listYour doFormLetter method should first go through each item on your list, and invoke its doProcess method, providing the Properties it needs for substitution. Afterward, it should invoke formLetterString() to place the result on the provided output stream.FormLetterHello is the simplest test program using this set of classes, so try running it first.You must also be sure not to add extra spaces when printing the templates or FormLetter, and finally when printing out the template, you must print out DataItemEntrys as <name>. That is, a less-than, the name of the data item, and then a greater-than.

Task 1 is to create subject class and test its properties, Task 2 is to create a number of classes and then test their properties, Task 3 is to display a frame using GUI, and Task 4 is to investigate on various programming paradigm.Task 1Value: 8 marksFor this task you will create a Subject class, whose instances will represent the subjects for study at a university. A subject will have a name, just a String (for example, Programming in java 1), and a subject code (for example, ITC206), which is a six-character String. The first three characters of a subject code are alphabetic and the last three are numeric. The first three characters define the subject's discipline area. A subject code must be unique.You will also write a TestSubject class to test the use of your Subject class. In particular this will maintain an array of subjects. In order to manage the uniqueness of the subject codes, your program will need to display information about existing subject codes as well as checking that any new subject code supplied by the user is not the same as any existing subject code.The following state and functionality should be provided for the Subject class:Two fields will hold the subject’s name and the six-character subject code.A constructor will allow a name and a new, validated subject code to be provided when a new subject is created.Getters will provide access to the attributes i.e. subject name and subject code.An accessor method called getDiscipline will return a string containing the first three characters of the subject code (for example ITC from ITC206 subject code).Another accessor method called codeMatches will return a boolean value indicating if the subject's code matches the string argument provided. "Matches" is used here in the same sense as for the matches method of the String class.A toString method will return a string containing the subject code and subject name.To assist with managing subject codes and their uniqueness you will provide the Subject class with some class methods as follows:An allDisciplines method will accept an array of Subject objects. It will return an array containing the different 3-character discipline codes represented in the array of subjects in alphabetically order. A codesPerDiscipline method will accept an array of Subject objects and a 3-character discipline code. It will return an array containing the different subject codes represented in the array of subjects for the particular discipline.An isValidCode method will accept a string that is a possible new subject code, and return a boolean indicating whether it satisfies the structural requirements for a subject code.A codeExists method will accept an array of Subject objects and a possible new subject code. It will return a boolean indicating whether that code has already been allocated to one of the subjects in the array.A sortDisciplines method will accept an array of Subjects objects. It will return the sorted array of subjects in alphabetically order (you may sort based on the subject code only). Your TestSubject program will perform the following sequence of actions, using good design techniques such as in the appropriate use of methods:An initial array of Subject objects will be created from any data in a file that was previously saved by the program. Then you need to read Subject objects from the file and store in appropriate array using your java program.The user interaction will then proceed to allow the user to add one or more new subjects to the array. If the user wishes to add new subjects, the discipline areas of existing subjects should be displayed in alphabetically order. The user will then enter a discipline code to which the program will respond by displaying any existing subject codes in that discipline. This procedure simplifies the user’s task of choosing subject codes that do not already exist, but does not prevent user mistake. Each subject code entered by the user should be checked. The user can enter any new subjects in that discipline (or indeed in other disciplines). The user should be given the choice of repeating the processing for other discipline areas.When the user has finished adding subjects, and only if subjects have indeed been added, the program will overwrite the data file with the updated data.Note:You may use an ArrayList to implement an array if you prefer and it is appropriate.Task 2Value: 5 marks(a) Define an abstract class called Textbook with the following fields and methods: ·Fields: title, author, pages representing the title, author and the number of pages of a textbook for a given book respectively. Encapsulation should be used to protect these fields against intentional or accidental, direct modification·Constructors: a no-args default constructor, and an overloaded constructor to initialise the fields to appropriate values when the instances of the class are created·Methods: a toString() method to print a string representation of the objects, get and set methods to provide access to each of the three fields(b) Define a subclass of the Textbook class called ProgrammingTextbook with the following additional field and methods: ·Field: language representing the particular language the programming textbook uses. Again, encapsulation should be used to protect this field against intentional or accidental, direct modification·Constructors: a no-args default constructor, and an overloaded constructor to initialise the fields to appropriate values when the instances of the class are created·Methods: a toString() method to print a string representation of the objects, additional get and set methods as required to provide access to the field(c) Define another subclass of the Textbook class called EngineeringTextbook with the following additional field and methods:·Field: subject representing the particular engineering subject the textbook teaches. Again, encapsulation should be used to protect this field against intentional or accidental, direct modification·Constructors: a no-args default constructor, and an overloaded constructor to initialise the fields to appropriate values when the instances of the class are created·Methods: a toString() method to print a string representation of the objects, additional get and set methods as required to provide access to the field(d) Finally, define another class called TestTextbooks with a main() method to perform necessary testing for the classes defined in the previous sections. In the main method, write the code to create at least two objects of the ProgrammingTextbook class and at least two other objects of the EngineeringTextbook class. Create an ArrayList object to store references to these objects and then test various methods of the objects using loop(s) and methods as necessary. Ensure that the program is appropriately documented throughout and thoroughly tested to demonstrate its correct operation.Task 3Value: 4 marksWrite a Java program using JavaFX that displays five playing cards. In the first row display three playing cards (randomly selected from the first 52 cards). In the second and third rows display a Joker card at 45 degree and 90 degree angles respectively. The image icons used in the questions are available in the Resource folder of Interact2. You may need to use HBox and/or VBox Pane. Task 4Value: 3 marksInvestigate the imperative programming paradigm, as exemplified by procedural programming and object-oriented programming, and the declarative programming paradigm, as exemplified by functional programming and logic programming.The Reading from Brookshear, 2012 will form a starting point for your investigation. For further investigation, remember that you should not reference Wikipedia items in an essay, so make sure to find articles that you can reference.Write an essay, of approximately 800 words, based on your investigation, which provides answers to the following questions:What are the essential differences between the paradigms?What are some of the programming languages used for these different paradigms?What specific advantages are provided by these different programming approaches?Your essay should be referenced using the APA referencing style.Rationaleto interpret and evaluate design requirements expressed in Unified Modelling Language (UML) (objective 2);to apply inheritance and aggregation patterns in the design and implementation of programs (Objective 3);be able to compare and critically evaluate different programming paradigms (Objective 6);to manipulate file operations through Java programming; (objective 7);to use object-oriented techniques and Java resources to develop small applications consisting of a number of classes (objective 4);to implement Graphical User Interface) (GUI )components using Java (objective 8).Marking criteriaThese criteria will be used to evaluate Assignment 3:The tasks are performed as specified and the assignment is submitted as requiredAppropriate understanding of the subject area is demonstrated, including correct use of approriate techniquesExplanations and discussions are cogent and use clear and correct English expressionReferencing is used where appropriatePresentationMaterial to submit for Task 11.You need to submit the java and class files2.You also need to submit a doc/pdf file with following information:a.Analysis: Describe the problem including input and output in your own words (not more than 400 words)b.Testing: Describe how you test this program (not more than 400 words)c. Output: Copy and paste a snapshot of the program outputMaterial to submit for Task 21.You need to submit the java and class files2.You also need to submit a doc/pdf file with following information:a.Analysis: Describe the problem including input and output in your own words (not more than 400 words)b.Testing: Describe how you test this program (not more than 400 words)c. Output: Copy and paste a snapshot of the program outputMaterial to submit for Task 31. You need to submit the java and class files2. You also need to submit a doc/pdf file with following information:a. Analysis: Describe the problem including input and output in your own words (not more than 400 words)b. Testing: Describe how you test this program (not more than 400 words)c. Output: Copy and paste a snapshot of the program output Material to submit for Task 41. You need to submit a doc/pdf file which includes the easy.RequirementsTo complete this assignment you might need to have covered material up to and including the topic Inheritance and Polymorphism, abstract classes and interfaces, Thinking of Objects, GUI basics, and UML in the Text Book and module.

This assignment provides you the opportunity to work with fractions as a new abstract data type! You should be able to help third and fourth graders with their homework when you complete this exercise!What to hand in:Please hand in code listings and output that are legible and formatted for ease of reading.Canvas submission instructions:Please combine multiple files into a single "zip" archive, and save it in a location that you will remember. When you are ready to submit the assignment, open the assignment you are submitting a solution for, and attach your file.Problems:Derive a new kind of Number called Fraction. Give it appropriate methods to add, subtract, multiply and divide fractions. Also, provide the required methods for a Number (to be sortable, it should also implement Comparable<Fraction>).Determine some appropriate way to convert a Fraction to a String, and implement the appropriate method. Simply outputting the double equivalent is not a satisfactory answer.You must provide a method (which could be private) to simplify your Fraction into lowest terms. That method could be used after every operation changing the Fraction, and certainly is required to provide a reasonable comparison operation.Make sure to implement equals so you have a way to compare Fractions.Create a main method or test class with a main method with adequate number of test cases to demonstrate that your Fraction behaves appropriately.Notes:A fraction has a numerator and a denominator (the part above the line and the part below the line).The denominator may not be zero (0).If the denominator is one (1), the Fraction represents the integer in the numerator, and should be converted to a String just like an integer.Remember the rules for addition, subtraction, multiplication, and division of fractions:To simplify a Fraction, one divides the numerator and denominator by the greatest common divisor, which is the largest number that divides each of them evenly.If you are not using BigInteger, you can use the following gcd method. It can be modified to use long instead of int:/* As a static method using int */public static int greatestCommonDivisor (int int1, int int2){ int temp; if ( int1 < 0 ) int1 = -int1; if ( int2 < 0 ) int2 = -int2; while ( int2 != 0) { temp = int1 % int2; // % is the modulus operator int1 = int2; int2 = temp; } return int1;}Additionally, one should ensure the denominator is positive. If you are using BigInteger to represent the components, you compare to zero with compareTo and use negate to reverse the sign.Once you simplify, you can compare Fractions by manipulating denominators and numerators. Hint: For compareTo you can subtract them and look at the result.If you use BigInteger to represent these components, you will get a gcd method to go along with it!BigInteger also provides a satisfactory set of name expectations for the operations one might expect on a Fraction. These are worth consulting!To create fractions, it is sensible to have a String constructor. A sample constructor is provided below (this one uses the BigInteger data members; a somewhat simpler, but similar one would work with long data members):public Fraction (String fractionString) throws NumberFormatException { String[] parts = fractionString.split("/"); denominator = BigInteger.ONE; numerator = BigInteger.ZERO; // The BigInteger constructor may throw NumberFormatExceptions if ( parts.length == 0 || parts.length > 2 ) { throw new NumberFormatException("Illegally formatted Fraction"); } numerator = new BigInteger(parts[0].trim()); if ( parts.length == 2 ) { BigInteger d = new BigInteger(parts[1].trim()); if ( d.equals(BigInteger.ZERO)) throw new NumberFormatException("Fraction may not have zero denominator"); denominator = d; } simplify();}Remember: Delegate, delegate, delegate!Evaluation Criteria:CriteriaWeightCreation of the Fraction type and its components, including a String constructor.20Add, Subtract, Multiply, and Divide operations20All required Number methods20simplify and toString methods10Method for comparison of Fractions (equals, compareTo)10Main program with an adequate number of test cases to demonstrate the above20