Resources the Final Project Overview and the Final Project Interv.docx

Resources: the Final Project Overview and the Final Project
Interview documents.
Select a religion that is not your own and interview a person of
that faith. If possible, visit a place of worship and interview a
person of that institution. As an alternative, the interview may
be conducted by telephone, written communication (e.g., email
exchange) or, web/video conference.
Write a 1,050- to 1,400-word informative paper on world
religions.
Compare your selected religion with the other religions studied
in this class.
· What characteristics does your chosen religions share with the
others? What makes it unique?
· How is religion in general, and your chosen religions
specifically, responding to challenges of the modern world?
Include a summary of your interview containing the following
elements:
· Introduction of the religion, including the history
· Date, time and method of interview
· Name of the person interviewed
· Name, location and review of the site if applicable.
· Interview summary
· References
Cite at least five references in addition to the textbook.
Format your paper consistent with APA guidelines.
Submit your assignment using the Assignment Files tab above.
Grading Matrix:
This assignment is worth a total of 10% of your final grade and
will be marked out of 100 points.
Content (75 points)
· Length (1050 - 1400 words) - 5 points
· Comparison - 25 points
· Site visit and interview summary - 25 points

· History of the religion - 10 points
· Introduction - 5 points
· Conclusion - 5 points
Mechanics (25 points)
· Writing style, grammar, and spelling - 5 points
· Following APA guidelines (title page, font, font size, etc) - 5
points
· Minimum 5 references with correct format - 5 points
· Proper use and format of citations. Citations should be
provided for all numbers (dates, statistics, etc) and for little
known facts. If there are no citations you will receive a zero
(0) on this part of the assignment - 10 points.
Copyright © 2012 by University of Phoenix. All rights reserved.
All trademarks are property of their respective owners. See the
li
© 2014 Laureate Education, Inc. Page 1 of 5
Amusement Park Programming Project
Project Outcomes
1. Use the Java selection constructs (if and if else).
2. Use the Java iteration constructs (while, do, for).
3. Use Boolean variables and expressions to control iterations.
4. Use arrays or ArrayList for storing objects.
5. Proper design techniques.
Project Requirements

Your job is to implement a simple amusement park information
system that
keeps track of admission tickets and merchandise in the gift
shop. The
information system consists of three classes including a class to
model tickets, a
class to model gift shop merchandise, the amusement park, and
the amusement
park tester. The gift shop supports access to specific
merchandise in the park’s
gift shop and to purchase the merchandise or to order new
merchandise for the
gift shop. The UML diagram for each class (except the tester
class) is given
below.
1) Develop a simple class that models admission tickets. Each
admission is
described by several instance fields:
a. A ticket number as a long integer to identify the unique
ticket,
b. A ticket category represented as a String to store the category
of the
ticket (i.e. adult, child, senior),
c. A ticket holder represented as a String to store the name of
the person
who purchased the ticket,
d. A date represented as a Date to store the admission date for
the ticket,
e. A price represented as a double to store the price of the
ticket,
f. A purchase status represented as a boolean to indicate if the

ticket has
been purchased (or is reserved).
Ticket
-number : long
-category : String
-holder : String
-date : Date
-price : double
In addition to these fields, the class has the following
constructors and
methods:
a. A parameterized constructor that initializes the attributes of a
ticket.
b. setPrice(double price) to change the price of a textbook.
c. changePurchaseStatus(boolean newStatus) to change the
purchase status of the ticket.
d. Accessor methods for all instance fields.
e. toString() to return a neatly formatted string that contains all

the
information stored in the instance fields.
2) Develop a simple class that models merchandise available in
the gift shop
such as t-shirts, sweatshirts, and stuffed animals. The class has
several
instance fields:
a. An ID as a long integer to identify the specific merchandise
item,
b. A category as a String to store the specific type of
merchandise,
c. A description as a String to store the description of the
merchandise,
d. A price represented as a double to store the price of the
merchandise,
e. An instock as a boolean to indicate if the merchandise is
instock or on-
order.
Valid values for category include "T-Shirt", "Sweatshirt", and
"Stuffed Animal",
as well as any additional category you choose to support. If
invalid values are
entered, an error message must be printed and the category
instance field
must be set to "UNKNOWN".
In addition to these attributes, the class has the following
constructors and
methods:
f. A parameterized constructor that initializes the attributes of a

merchandise item.
g. setPrice(double price) to change the price of the merchandise.
h. setInstock(boolean newStatus) to change the status of the
merchandise item.
i. Accessor methods for all instance fields.
j. toString() to return a neatly formatted string that contains all
the
information stored in the instance fields.
+Ticket (String, String, Date, double, boolean)
+setPrice(double)
+changePurchaseStatus(boolean)
+getNumber() : long
+getCategory() : String
+getHolder() : String
+getDate() : String
+getPrice() : double
+toString() : String

Merchandise
-id : long
-category : String
-description : String
-price : double
-inStock : boolean
+Merchandise(String, String, String, double, boolean)
+setPrice(double)
+setInstock(boolean)
+getId() : String
+getCategory() : String
+getDescription() : String
+getPrice() : double
+getInstock() : boolean
+toString() : String
3) Develop class AmusementPark that keeps track of tickets and

gift shop
inventory. The AmusementPark uses two ArrayLists to store
Ticket and
Merchandise objects. The AmusementPark provides several
methods to
add merchandise to the gift shop and to access merchandise.
The following
UML diagram describes the class, the constructor, and the
methods:
AmusementPark
-tickets : ArrayList<Ticket>
-merchandise : ArrayList<Merchandise>
-name : String
+AmusementPark(String)
+getName() : String
+getTicketDates() : ArrayList<Date>
+getTickets(Date date) : int
+getTicket(long id) : Ticket
+getMerchandise() : ArrayList<Merchandise>
+getMerchandise(String category) : ArrayList<Merchandise>

+getMerchandise(long id) : Merchandise
+addTicket(Ticket)
+addMerchandise(Merchandise)
+buyMerchandise(String id)
+buyTicket(String id)
a. The class has three instance fields:
a. name, the name of the bookstore
b. tickets, an ArrayList<Ticket> storing Ticket objects
c. merchandise, an ArrayList<Merchandise> storing
Merchandise objects
b. getName() returns the name of the bookstore.
c. getTicketDates() returns an ArrayList<Date> of all the dates
for which tickets are still available. If there are no tickets
available, an
empty list is returned.
d. getTickets (Date date) returns an integer indicating the
number

of tickets available for the specified date.
e. getTicket(long id) returns the Ticket that matches the
specified id. If there is no Ticket matching the given id, null is
returned.
f. getMerchandise()returns an ArrayList<Merchandise> of all
the inventory (in-stock and ordered). This method must create a
separate copy of the ArrayList before it returns the list. If there
are
no merchandise items in the AmusementPark, an empty list is
returned.
g. getMerchandise(String category) returns a list of
Merchandise objects whose category matches the specified
category. For example, if called with "T-shirt" the method
returns all
Merchandise objects with the category "T-shirt" as a new list.
This
method must create a new copy of an ArrayList that stores all
the
matched Merchandise objects. If no items in the
AmusementPark
match the given name, an empty list is returned.
h. getMerchandise(long id) returns the merchandise item that
matches the specified id. If there is no merchandise item

matching the
given id, null is returned.
i. addTicket(Ticket) adds a new Ticket to the inventory of the
AmusementPark.
j. addMerchandise(Merchandise) adds a new Merchandise to the
inventory of the AmusementPark.
k. buyMerchandise(String id) removes a Merchandise object
from the list of merchandise of the AmusementPark. If the id
does not
match any Merchandise object in the list, an exception is
thrown.
l. buyTicket(String id) removes a Ticket object from the list of
ticket items of the AmusementPark. If the id does not match any
Ticket object in the list, an exception is thrown.
4) Design a tester class called AmusementParkTester. The tester
class has a
main() method and tests the functionality of the class
AmusementPark as
follows:
a. Create AmusementPark and name it "Walden Amusement
Park".

b. Create a minimum of three Ticket objects and add them to the
bookstore.
c. Create Apparel objects, at least two of each category, and add
them
to the AmusementPark.
d. Set up a loop to:
i. Display a short menu that allows a user to perform different
actions in the gift shop such as looking up tickets or
merchandise or purchasing items. Use all of the accessor
methods in the AmusementPark to access specific items. Use
the given methods to make purchases.
ii. Prompt the user for a specific action.
iii. Depending on the specific action prompt the user for
additional
input such as the id of a ticket or merchandise category, etc.
You might want to use static methods in main() to handle each
menu item separately.
iv. Perform the action and display results such as the list of
merchandise that the user has requested. Use the toString()
method to display AmusementPark items on the screen.

v. Prompt the user for continued access to the AmusementPark
or to end the program.
Your program should handle input errors gracefully. For
example, if a particular
ticket is searched and not found, the program should display a
message such as
"Selected ticket not found." Feel free to experiment with the
tester program in
order to develop a more useful program.
Implementation Notes:
1) All accessor methods in AmusementPark must create a new
ArrayList
to copy objects into the new list. This requires loops to access
objects
from the corresponding instance fields and adding them to the
new
ArrayList.
2) Proper error handling is essential for this project.
3) Javadoc must be used to document AmusementPark, Ticket,
and
Merchandise.
Submission Requirements:
1. Your project submission should have four files for this
assignment:

a. Ticket.java - The Ticket class,
b. Merchandise.java - The Merchandise class,
c. AmusementPark.java - The AmusementPark class,
d. AmusementParkTester.java - A driver program for testing
your
AmusementPark class.
2. Remember to compile and run your program one last time
before you
submit it
Retail Transaction Programming Project
Project Requirements:
1. Develop a program to emulate a purchase transaction at a
retail store. This
program will have two classes, a LineItem class and a
Transaction class. The
LineItem class will represent an individual line item of
merchandise that a
customer is purchasing. The Transaction class will combine
several LineItem
objects and calculate an overall total price for the line item
within the transaction.

There will also be two test classes, one for the LineItem class
and one for the
Transaction class.
2. Design and build a LineItem class. This class will have three
instance variables.
There will be an itemName variable that will hold the
identification of the line item
(such as, "Colgate Toothpaste"); a quantity variable that will
hold the quantity of
the item being purchased; and a price variable that will hold the
retail price of the
item. The LineItem class should have a constructor, accessors
for the instance
variables, a method to compute the total price for the line item,
a method to
update the quantity, and a method to convert the state of the
object to a string.
Using Unified Modeling Language (UML), the class diagram
looks like this:
LineItem
- itemName : String
- quantity : int
- price : double
+ LineItem( String, int, double )

+ getName( ) : String
+ getQuantity( ) : int
+ getPrice( ) : double
+ getTotalPrice( ) : double
+ setQuantity( int )
+ setPrice( double )
+ toString( ) : String
a. The constructor will assign the first parameter to the instance
variable
itemName, the second parameter to the instance variable
quantity, and
the third parameter to the instance variable price.
b. The class will have three accessor methods—getName( ),
getQuantity( ),
and getPrice( )—that will return the value of each respective
instance
variable.
c. The class will have two mutator methods, setQuantity( int )
and setPrice(
double ), that will update the quantity and price, respectively,
of the item

associated with the line of the transaction.
d. The method getTotalPrice( ) handles the conversion of the
quantity and
price into a total price for the line item.
e. The method toString( ) allows access to the state of the object
in a
printable or readable form. It converts the variables to a single
string that
is neatly formatted.
Note: Refer to the textbook for a discussion of escape
sequences. These
are characters that can be inserted into strings and, when
printed, will
format the display neatly. An escape sequence for the tab
character can
be inserted to get a tabular form when printing. This tab
character is "t".
The LineItem class will have a toString( ) method that
concatenates
itemName, quantity, price, and total price—separated by tab
characters—and returns this new string. When printing an
object, the
toString( ) method will be implicitly called, which in this case,
will print a
string that will look something like:

Colgate Toothpaste qty 2 @ $2.99 $5.98
3. Build a Transaction class that will store information about
the items being
purchased in a single transaction. It should include a
customerID and
customerName. It should also include an ArrayList to hold
information about
each item that the customer is purchasing as part of the
transaction.
Note: You must use an ArrayList, not an array.
4. Build a TransactionTest class to test the application. The test
class should not
require any interaction with the user. It should verify the
correct operation of the
constructor and all methods in the Transaction class.
Specific Requirements for the Transaction Class
1. The Transaction class should have a constructor with two
parameters. The first
is an integer containing the customer’s ID and the second is a
String containing
the customer’s name.
2. There should be a method to allow the addition of a line item
to the transcript.
The three parameters for the addLineItem method will be (1) the
item name, (2)
the quantity, and (3) the single item price.
3. There should be a method to allow the updating of a line item

already in the
transaction. Notice that updating an item means changing the
quantity or price
(or both). The parameters for the updateItem method are also
(1) the item name,
(2) the quantity, and (3) the single item price. Notice that the
updating of a
specific line item requires a search through the ArrayList to
find the desired
item. Anytime a search is done, the possibility exists that the
search will be
unsuccessful. It is often difficult to decide what action should
be taken when such
an "exception" occurs. Since exception handling is not covered
until later in this
textbook, make some arbitrary decisions for this project. If the
item to be updated
is not found, take the simplest action possible and do nothing.
Do not print an
error message to the screen. Simply leave the transaction
unchanged.
4. The transaction class needs a method called getTotalPrice to
return the total
price of the transaction.
5. There should also be a method to return information about a
specific line item. It
should return a single String object in the same format

described for the
LineItem class:
Again, the possibility exists that the search for a specific line
item will fail. In this
instance, you should return a string containing a message
similar to this:
Colgate Toothpaste not found.
6. The final method needed is a toString method. It should
return the transaction
information in a single String object. It should use the
following format:
Customer ID : 12345
Customer Name : John Doe
Bounty Paper Towels qty 1 @ $1.49 $1.49
Kleenex Tissue qty 1 @ $2.49 $2.49
Transaction Total $9.96
Notice that a newline character "n" can be inserted into the
middle of a string.
Ex.

int age = 30;
String temp = "John Doe n is " + age + "n" + " years
old";
The output would be:
John Doe
is 30
years old
Notice also that "n" is a single character and could actually go
inside single or
double quotes, depending on the circumstances.
Here is a UML diagram for the Transaction class as described
above. Notice that
private instance variables and methods may be added, as
needed. For all public
methods use exactly the name given below.
Transaction
- lineItems : ArrayList<LineItem>

- customerID : int
- customerName : String
+ Transaction( int, String )
+ addLineItem( String, int, double )
+ updateItem( String, int, double )
+ getTotalPrice( ) : double
+ getLineItem( String ) : String
+ toString( ) : String

Resources the Final Project Overview and the Final Project Interv.docx

Recommended

Recommended

More Related Content

Similar to Resources the Final Project Overview and the Final Project Interv.docx

Similar to Resources the Final Project Overview and the Final Project Interv.docx (14)

More from debishakespeare

More from debishakespeare (20)

Recently uploaded

Recently uploaded (20)

Resources the Final Project Overview and the Final Project Interv.docx