The second Objects lab, from the BlueJ book's second chapter.
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.
- Create a TicketMachine object on the object bench.
- Upon viewing its methods,
getBalance,getPrice,insertMoney,printTicket. - Use
getPricemethod to view the value of the price of the tickets that was set when this object was created. - Use
insertMoneymethod to simulate inserting an amount of money into the machine. - Use
getBalanceto 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
printTicketmethod. A facsimile ticket should be printed in the BlueJ terminal window.
- 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
- What value is returned if you check the machine’s balance after it has printed a ticket? Answer: 0
- Experiment with inserting different amounts of money before printing tickets.
- Do you notice anything strange about the machine’s behavior? Answer: No matter how much Balance is entered more or less than the actual Ticket cost it prints the ticket and sets the balance to 0 everytime.
- What happens if you insert too much money into the machine – do you receive any refund? Answer:No Refund the Balance is set to 0 and not the remaining Balance.
- What happens if you do not insert enough and then try to print a ticket? Answer: It still prints the ticket.
- 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
TicketMachineclass is implemented in the next section.
- Create another ticket machine for tickets of a different price.
- Buy a ticket from that machine.
- Does the printed ticket look different? Answer: The Ticket price is different.
- Write out what you think the outer wrappers of the
StudentandLabClassclasses might look like – do not worry about the inner part. Answer:
public class Student { }
public class Labs {
}
Does it matter whether we write
public class TicketMachine
or
class public TicketMachine
in the outer wrapper of a class? Answer: yes class will not compile throwing error expected.
- Edit the source of the
TicketMachineclass to make the change and then close the editor window.- Do you notice a change in the class diagram? Answer: Yes with crisscross lines.
- What error message do you get when you now press the compile button? Answer: error expected.
- Do you think this message clearly explains what is wrong? Answer: The complier expects the identifier of the TicketMachine.
- Check whether or not it is possible to leave out the word
publicfrom the outer wrapper of theTicketMachineclass.Answer: Yes possible, with no compiler error. The class will be type default.
-
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
TicketMachineclass. - Hint: There is only one constructor in the class.
Fields: price,balabce,total Constructor: TicketMachine Methods: getPrice, getBalance,insertMoney, printTicket;
- 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
- Do you notice any features of the constructor that make it significantly different from the other methods of the class? Answer: The constructor share the same name as the Class.
- What do you think is the type of each of the following fields?
private int count; Answer: type is integer.Primitive type.
private Student representative; Answer: type is Student.Reference type, where Student is a class.
private Server host; Answer: type is Server.Reference type, where Server is a class.- What are the names of the following fields?
private boolean alive; Answer: alive
private Person tutor;Answer: tutor
private Game game;Answer: gameIn the following field declaration from the TicketMachine class
private int price;does it matter which order the three words appear in? Answer: Yes
- Edit the
TicketMachineclass to try different orderings. After each change, close the editor. Answer: The class has criscross unable to compile successfully.- Does the appearance of the class diagram after each change give you a clue as to whether or not other orderings are possible?Answer: We can just write class TicketMachine instead of publice class TicketMachine but not class public TicketMachine.
- Check by pressing the compile button to see if there is an error message.Answer expected.
- Make sure that you reinstantiate the original version after your experiments!
- Is it always necessary to have a semicolon at the end of a field declaration? Answer: Yes
- Once again, experiment via the editor.
- The rule you will learn here is an important one, so be sure to remember it.
- Write in full the declaration for a field of type
intwhose name isstatus. Answer: int status;
- To what class does the following constructor belong?Answer: class Student.
public Student(String name)
- How many parameters does the following constructor have and what are their types?Answer: 2 parameters "title" which has a type String and "price" which has a type Double.
public Book(String title, double price)
- Can you guess what types some of the
Bookclass’s fields might be? Answer: noOfPages, author, publisher. - Can you assume anything about the names of its fields?Answer: No. Generally the variable name should be declared in a way that its understandable what it might be for but its not mandatory to do so.
Work all Exercises from 2.19 to 2.58 that are NOT marked Challenge exercise. READ upto and INCLUDING section 2.15 of this chapter.