Text Answered in edited READ.ME file

README.md

@@ -1,92 +1,267 @@
-# NaiveTicket
-
-The second Objects lab,from the BlueJ book's second chapter.
-
-Look for the [Chapter 2 file](./doc/BlueJ-objects-first-ch2.pdf) you need in the [doc](./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.
-
-* Exercise 2.1 Create a TicketMachine object on the object bench and take a look
-at its methods. You should see the following: getBalance, getPrice, insertMoney,
-and printTicket. Try out the getPrice method. You should see a return value containing
-the price of the tickets that was set when this object was created. Use the
-insertMoney method to simulate inserting an amount of money into the machine and
-then 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.
-* Exercise 2.2 What value is returned if you check the machine’s balance after it
-has printed a ticket?
-* Exercise 2.3 Experiment with inserting different amounts of money before printing
-tickets. Do you notice anything strange about the machine’s behavior? What happens
-if you insert too much money into the machine – do you receive any refund? What
-happens if you do not insert enough and then try to print a ticket?
-* Exercise 2.4 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.
-* Exercise 2.5 Create another ticket machine for tickets of a different price. Buy a
-ticket from that machine. Does the printed ticket look different?
-
-* Exercise 2.6 Write out what you think the outer wrappers of the Student and
-LabClass classes might look like – do not worry about the inner part.
-* Exercise 2.7 Does it matter whether we write
-`public class TicketMachine`
-or
-`class public TicketMachine`
-in the outer wrapper of a class? 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?
-What error message do you get when you now press the Compile button? Do you think
-this message clearly explains what is wrong?
-* Exercise 2.8 Check whether or not it is possible to leave out the word public
-from the outer wrapper of the TicketMachine class.
-
-* Exercise 2.9 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.
-Exercise 2.10 Do you notice any features of the constructor that make it significantly
-different from the other methods of the class?
-
-* Exercise 2.11 What do you think is the type of each of the following fields?
-```
-private int count;
-private Student representative;
-private Server host;
-```
-* Exercise 2.12 What are the names of the following fields?
-```
-private boolean alive;
-private Person tutor;
-private Game game;
-```
-* Exercise 2.13 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 reinstate the original version after your experiments!
-* Exercise 2.14 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.
-* Exercise 2.15 Write in full the declaration for a field of type int whose name is
-status.
-* Exercise 2.16 To what class does the following constructor belong?
-```
-public Student(String name)
-```
-* Exercise 2.17 How many parameters does the following constructor have and what are their types?
-```
-public Book(String title, double price)
-```
-* Exercise 2.18 Can you guess what types some of the Book class’s fields might be? Can you assume anything about the names of its fields?
-
-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.
+Naive Ticket Exercise's
+
+Exercise 2.1 
+Requested price as argument for parameter upon creating new instance of TicketMachine
+getPrice returns price entered upon initialization of object
+insertMoney requests int argument for its parameter
+getBalance returns int equal to amount entered into insertMoney's parameter
+printTicket prints price of ticket and sets balance field to 0
+
+Exercise 2.2
+getBalance method returns 0 after printTicket method is called
+
+Exercise 2.3 
+Naive TicketMachine does not validate correct amount entered, each call to printTicket will print a ticket with the listed price and set balance to 0
+
+Exercise 2.4 
+The constructor requires input to set price = ticketCost
+Balance and total are set to 0 upon initialization 
+
+Exercise 2.5 
+The only difference is the price printed on the ticket
+
+Exercise 2.6 
+?
+
+Exercise 2.7 
+Yes, order matters. Public modifier must come before class, will not successfully compile if reversed.
+
+Exercise 2.8
+Yes, there are no syntax errors if public modifier is not present
+
+Exercise 2.9 
+Constructors have no return type, they do not require a public modifier and can only be run when object is created
+
+Public class TicketMachine
+{
+	private int balance;
+	private int price;
+	private int deposit;
+	
+	public TicketMachine(int ticketCost)
+	{
+		price = ticketCost;
+		balance = 0;
+		deposit = 0;
+	}
+	public void printTicket()
+	{
+		System.out.println(*****);
+		System.out.println("Your ticket price is:");
+		System.out.println(price + " cents.");
+		
+		balance = 0;
+	}
+	public void setBalance(int newBalance)
+	{
+		balance = newBalance;
+	}
+	public int getBalance()
+	{
+		return balance;
+	}
+	public int getPrice()
+	{
+		return price;
+	}
+}
+
+Exercise 2.11 
+Int
+Student
+Server
+
+Exercise 2.12 
+Alive
+Tutor
+game
+
+Exercise 2.13 
+Yes order matters, modifier + type + name
+
+Exercise 2.14 
+It is not always necessary to have a semicolon at the end of a statement but is bad syntax to not include
+
+Exercise 2.15 
+Private int name;
+
+Exercise 2.16 
+Student
+
+Exercise 2.17 
+Two parameters of type String and double
+
+Exercise 2.18 
+?
+
+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.
+
+Exercise 2.19
+Two parameters of type String and double
+
+Exercise 2.20
+
+
+Exercise 2.21
+Public Pet(String petsName)
+{
+	name = petsName;
+}
+
+Exercise 2.23
+Only difference is the field they interact with
+
+Exercise 2.24
+Tickets cost value set when object created
+getBalance is total amount entered into machine before calling getTicket
+
+Exercise 2.25
+No, name of method being changed does not effect return statement
+
+Exercise 2.26
+Public int getTotal()
+{
+	return total;
+}
+
+Exercise 2.27
+Must return value of type int 
+
+Exercise 2.28
+Return type is main difference
+
+Exercise 2.29
+No return statements, these methods complete their statements without returning a value
+
+Exercise 2.30
+The value of the balance field changed as expected after each call
+
+Exercise 2.31
+Constructor's do not have return types
+
+Exercise 2.32
+Public void setPrice(int newPrice)
+{
+	price = newPrice;
+}
+
+Exercise 2.33
+Score = points;
+
+Exercise 2.35
+Yes, if changes field value, is a mutator
+
+Exercise 2.36
+My cat has green eyes.
+
+Exercise 2.37
+Public void prompt()
+{
+	System.out.println("Please insert the correct amount of money.");
+}
+
+Exercise 2.38
+The word price rather than the value of the variable price
+
+Exercise 2.39
+Would only print a string
+
+Exercise 2.40
+No, would only print string
+
+Exercise 2.41
+Public void showPrice()
+{
+	System.out.println("The price of the ticket is " + price + " cents.");
+}
+
+Exercise 2.42
+Each object has it's own copy of the price field and will display it's own assigned value
+
+Exercise 2.43
+You are no longer prompted for input, price variable is set at 1000 when object created
+
+Exercise 2.44
+TicketMachine()
+{
+    price = 1000;
+    balance = 0;
+    total = 0;
+}
+
+Exercise 2.45
+This method needs no parameters or return statement
+
+Exercise 2.46
+Balance is not changed if error message is printed
+
+Exercise 2.47
+No error will be thrown if 0 is entered and balance will not be changed as 0 is being added to current balance
+
+Exercise 2.48
+if(amount < )
+{
+	System.out.println("Use a positive amount rather than: " + amount);
+}
+else
+{
+	balance += amount;
+}
+
+Exercise 2.49
+
+
+Exercise 2.50
+We use conditional statements to check input and then choose an outcome base on boolean expression
+
+Exercise 2.51
+It still compiles but no action is taken if conditional statement does not evaluate to true for the if statement to run
+
+Exercise 2.52
+No, boolean expression evaluates balance and price fields to be sure balance is <= price before making changes (subtracting) from balance field
+
+Exercise 2.53
+* / %
+
+Exercise 2.54
+Saving = price * discount;
+
+Exercise 2.55
+Mean = total / count;
+
+Exercise 2.56
+if(price > budget)
+{
+	System.out.println("Too expensive");
+}
+Else
+{
+	System.out.println("Just right");
+}
+
+Exercise 2.57
+if(price > budget)
+{
+	System.out.println("Too expensive, budget is: " + budget);
+}
+Else
+{
+	System.out.println("Just right");
+}
+
+Exercise 2.58
+Balance is set to 0 before returning
+
+
+
+
+
+
+
+
+
+
+
+
+
+

bluej.pkg

@@ -1,18 +1,18 @@
 #BlueJ package file
-editor.fx.0.height=722
-editor.fx.0.width=800
-editor.fx.0.x=709
-editor.fx.0.y=113
+editor.fx.0.height=709
+editor.fx.0.width=1280
+editor.fx.0.x=0
+editor.fx.0.y=23
 objectbench.height=101
-objectbench.width=461
-package.divider.horizontal=0.6
-package.divider.vertical=0.8007380073800738
-package.editor.height=427
-package.editor.width=674
-package.editor.x=1067
-package.editor.y=119
-package.frame.height=600
-package.frame.width=800
+objectbench.width=701
+package.divider.horizontal=0.5619047619047619
+package.divider.vertical=0.8341013824884793
+package.editor.height=536
+package.editor.width=1154
+package.editor.x=0
+package.editor.y=23
+package.frame.height=709
+package.frame.width=1280
 package.numDependencies=0
 package.numTargets=1
 package.showExtends=true

package.bluej

@@ -1,18 +1,18 @@
 #BlueJ package file
-editor.fx.0.height=722
-editor.fx.0.width=800
-editor.fx.0.x=709
-editor.fx.0.y=113
+editor.fx.0.height=709
+editor.fx.0.width=1280
+editor.fx.0.x=0
+editor.fx.0.y=23
 objectbench.height=101
-objectbench.width=461
-package.divider.horizontal=0.6
-package.divider.vertical=0.8007380073800738
-package.editor.height=427
-package.editor.width=674
-package.editor.x=1067
-package.editor.y=119
-package.frame.height=600
-package.frame.width=800
+objectbench.width=701
+package.divider.horizontal=0.5619047619047619
+package.divider.vertical=0.8341013824884793
+package.editor.height=536
+package.editor.width=1154
+package.editor.x=0
+package.editor.y=23
+package.frame.height=709
+package.frame.width=1280
 package.numDependencies=0
 package.numTargets=1
 package.showExtends=true