The second Objects lab, from the BlueJ book's second chapter.

First you need to FORK this repo into your account, then you need to CLONE that foreked repo, the one in your account. When you are finished with your code, be sure to ADD/COMMIT and PUSH your code to your repo.

Use the URL from your repo as the submission to the portal.

Look for the Chapter 2 file you need in the doc folder. There is 35 pages of reading and exercises in the chapter.

Work through all these exercises. You edit this file with your answers for these exercises.

• X Create a TicketMachine object on the object bench.
• X Upon viewing its methods, getBalance, getPrice, insertMoney, printTicket.
• X Use getPrice method to view the value of the price of the tickets that was set when this object was created.
• X Use insertMoney method to simulate inserting an amount of money into the machine.
• X Use getBalance to check that the machine has a record of the amount inserted.
  • You can insert several separate amounts of money into the machine, just like you might insert multiple coins or notes into a real machine. Try inserting the exact amount required for a ticket. As this is a simple machine, a ticket will not be issued automatically, so once you have inserted enough money, call the printTicket method. A facsimile ticket should be printed in the BlueJ terminal window.

• What value is returned if you check the machine’s balance after it has printed a ticket? 0

• Experiment with inserting different amounts of money before printing tickets.
  • Do you notice anything strange about the machine’s behavior? It lets you put in nonsense values or too big or too small and still prints the ticket anyway.
  • What happens if you insert too much money into the machine – do you receive any refund? Ticket price printed is wrong. No refund.
  • What happens if you do not insert enough and then try to print a ticket? It will still print a ticket even though you didn't pay enough.

• X Try to obtain a good understanding of a ticket machine’s behavior by interacting with it on the object bench before we start looking at how the TicketMachine class is implemented in the next section.

• Create another ticket machine for tickets of a different price.
  • X Buy a ticket from that machine.
  • Does the printed ticket look different? The price is different.

• Write out what you think the outer wrappers of the Student and LabClass classes might look like – do not worry about the inner part.

• public class Student

• {

• }

  public class LabClass {

  }

Does it matter whether we write
public class TicketMachine
or
class public TicketMachine
in the outer wrapper of a class? Yes, it has to be written in a certain order or will give an error

• Edit the source of the TicketMachine class to make the change and then close the editor window.
  • Do you notice a change in the class diagram? Yes, has a reddish pattern on it
  • What error message do you get when you now press the compile button?
  • Do you think this message clearly explains what is wrong? Error(s) found in class expected

• Check whether or not it is possible to leave out the word public from the outer wrapper of the TicketMachine class. Yes, it is possible

• From your earlier experimentation with the ticket machine objects within BlueJ you can probably remember the names of some of the methods – printTicket, for instance.
  • Look at the class definition in Code 2.1 and use this knowledge, along with the additional information about ordering we have given you, to try to make a list of the names of the fields, constructors, and methods in the TicketMachine class.
  • Hint: There is only one constructor in the class. Fields: price, balance, total, ticketNumber Constructors: TicketMachine Methods: getPrice, getTicketNumber, getBalance, insertMoney, calculateTotal, incrementTicketNumber, printTicket

• Do you notice any features of the constructor that make it significantly different from the other methods of the class? All it does it set the fields equal to a value. It does not return anything like the other methods.

• What do you think is the type of each of the following fields?

private int count;			Primitive
private Student representative;		Object
private Server host;			Object

• What are the names of the following fields?

private boolean alive;			alive	
private Person tutor;			tutor
private Game game;			game

In the following field declaration from the TicketMachine class

private int price;

does it matter which order the three words appear in?

• Edit the TicketMachine class to try different orderings. After each change, close the editor.
  • Does the appearance of the class diagram after each change give you a clue as to whether or not other orderings are possible?
  • Check by pressing the compile button to see if there is an error message.
  • Make sure that you reinstantiate the original version after your experiments! Yes, the order does matter. It will throw errors if not in correct order.

• Is it always necessary to have a semicolon at the end of a field declaration?
• Once again, experiment via the editor.
• The rule you will learn here is an important one, so be sure to remember it. Yes, it will give an error if you don't.

• Write in full the declaration for a field of type int whose name is status. private int status;

• To what class does the following constructor belong?

public Student(String name)

Student

• How many parameters does the following constructor have and what are their types?

public Book(String title, double price)

two - their types are String and double

• Can you guess what types some of the Book class’s fields might be? Mostly likely String and double as that's what the parameter types are
• Can you assume anything about the names of its fields? Maybe the same or similar to the names of the parameters

READ upto and INCLUDING section 2.15 of this chapter.