JAVA PROGRAM

This project is the first time youll create your own objects, along with private data, methods, etc. This isnt a complete working system with a user interface; its just a chance for you to create classes, then instantiate and test them. Youll create two supplier classes that interact with each other (through a has a relationship).

Here are UML Class Diagrams for the objects you are to create. Pay attention to the diagram notation indicating whether methods are public (+) or private (-); ask questions if you need clarification. Understanding the model is of critical importance here.

Student		Department
(you figure out the private data needed)		(you figure out the private data needed)
Constructors +Student(firstName : String, lastName : String, id : String) +Student(firstName : String, lastName : String, id : String, csc110 : Boolean, csc142 : Boolean, csc143 : Boolean) Accessors +getFirstName() : String +getLastName() : String +getID() : String +getCSC110() : Boolean +getCSC142() : Boolean +getCSC143() : Boolean +getBalance() : Double +toString() : String Mutators +setCSC110(csc110 : Boolean) +setCSC142(csc142 : Boolean) +setCSC143(csc143 : Boolean)		Constructors +Department() +Department(totalStud110 : Integer, totalStud142 : Integer, totalStud143 : Integer, totalBalance : Double) Accessors +getTotalCSC110 () : Integer +getTotalCSC142 () : Integer +getTotalCSC143 () : Integer +getTotalStudents() : Integer +getTotalBalance() : Double +getTotalGr110() : Integer +getTotalGr142() : Integer +getTotalGr143() : Integer +toString() : String Other Methods +addStudent(newStudent : Student) : void

3 Constraints and Assumptions

Create no static methods except for the test methods.

Mark each instance variable and each method as either public or private; follow the UML where it gives guidance and make smart decisions where it doesnt.

Use exactly the method names shown. Look carefully at the parameter data types and the return data types; they give you clues.

Departments addStudent method maintains the appropriate total students of each group and the total balance.

Departments getTotalGr methods calculate how many groups need for each class (28 students in the class).

The toString method should do their best to summarize the state of the object instance in questions; include newlines in the strings to make the result displayable and attractive.

Create a test method for each class that checks every constructor and every method except toString.

One credit equals 5, and one credit costs $110.

Throw an IllegalArgumentException if any of these preconditions are violated:

o A first name, last name, and ID can't be empty.

o Total students of each group can't be negative.

The testing required here is significant. You may spend as much time writing your tests as you do writing the entire rest of the code. Your test code needs to test everything (or nearly everything), your object can do; dont treat it lightly. Dont forget to test constructors and preconditions. And dont forget test code is still code and can have bugs, so be suspicious if everything passes miraculously the first time, i.e., test that you can induce failures and get the appropriate error messages shown.

Dont duplicate code; avoid this wherever possible. As an example, dont forget its legal for one constructor to call another constructor; this is good practice and helps avoid duplication and the creation of extra code paths to test.

There is an example of the output:

The name: Name LastName ID: 123456789 The chosen class: CSC142 Credits: 5 Credit Price: 110.0 The balance: 550.0

Total students in CSC110: 98 in 4 groups Total students in CSC142: 51 in 2 groups Total students in CSC143: 27 in 1 groups Total students of the department: 176 Total Balance: $96800.0