For 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, and a subject code, 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. ◦ An accessor method called getDiscipline will return a string containing the first three characters of the 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. 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. ◦ 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.
You'll get a 2.8KB .ZIP file.