中国留学之家，中国最优秀的留学咨询公司，全球顶尖大学申请专家！ JAVA作业，看谁有兴趣试着做做

venkatmba - 2008-6-27 22:06:00

JAVA作业，看谁有兴趣试着做做

Programming project

For this project you are to develop an object-oriented program for an online mail order bookstore.
The bookstore sells books, music CDs, DVD videos and computer software.
The following information needs to be available for each of these products:
•
Books: title, author, publisher, year published, edition, volume, SCN, price and availability.
•
Music CDs: title, artist, publisher, year published, volume, SCN, price and availability.
•
DVD videos: title, director, publisher, year published, actor(s) and/or actress(es), running time, SCN, price and availability.
•
Computer software: title, publisher, year published, version, SCN, price and availability.

SCN is the Stock Control Number, in the case of books ISBN numbers are used for the SCN while a barcode number is used in the case of music CDs, DVD videos and software.
Availability can be 24 hours, 2-3 days, 1 week, 2-3 weeks, 4-6 weeks.

There are three groups of users of the system: Customer, Shipping Clerks and Inventory managers.

Customers can be either private individuals or retailers, the following information is needed for each of these:
•
Individual: e-mail address, password, name, shipping address, billing address, telephone number and credit card details.
•
Retailers: e-mail address, password, company name, shipping address, billing address, name of contact person, telephone number and account number.
Customers are uniquely identified by their e-mail addresses.

Addresses contain the following fields: street and number, suburb, city, county and postcode.

Each customer has a shopping cart as well as zero, one or more orders.

The shopping cart is a temporary list of titles the customer intends to buy.
The list also includes the number of each title the customer intends to buy.

Orders are identified by an order number and contain:
•
List of titles (and numbers) ordered.
•
Date the order was placed.
•
Cost of all the titles ordered, postage, tax and total cost of the order.
•
Status of the order.
The status of an order is not yet shipped or shipped.

•
Expected date or actual date of shipping.

A customer would typically go through the following actions when placing an order:
•
Logon – if the customer does not have an id then (s)he would first create it.
•
Search or browse for titles.
•
While searching/browsing some titles may be selected – added to the shopping cart.
•
Once the customer is done searching (s)he displays his/her shopping cart and makes some changes.
•
The customer then confirms the order, billing address, shipping address and bank details or account number.
•
The customer then logs off.

A customer can also do the following:
•
Change any of his/her details.
•
Check existing orders.
•
Save a shopping cart for a later date and return to that shopping cart.

Shipping clerks change the status of orders from not yet shipped to shipped.
A shipping clerk can login to the system after which (s)he get a list of orders that are to be shipped.
Orders for which the order date plus the longest availability period is equal to the current date will appear on the list of orders to be shipped.
The shipping clerk would then make up a package containing the items in an order and dispatch it.
Once the order has been dispatched the shipping clerk would change the status of the order to shipped.

Inventory managers can do the following:
•
Add new products.
•
Remove products.
•
Change the price of a product.
•
Change the availability of a product.

You should aim to develop a tiered design where the three basic components:
•
Data component - that is the data in the data store
•
Business logic - the application that manipulates the data from the data store
•
User interface
are logically “de-coupled”.
It is advisable to develop your project in the sequence: first data component then logic or application and only then user interface.
Start of with a (simple!) text based or menu driven user interface and only when everything works change it to a GUI!
However, a GUI is NOT essential!

Guidance on Deliverables

•
All of your source code should have consistent indentation and a clear style.
•
Each class should have a method main that instantiates that class and tests all the methods of the class.
•
Detailed UML diagrams.
Diagrams to be included are: use case diagrams, class and object diagrams, and sequence diagrams.
Class diagrams are to contain all relationships that exist between classes.
Do not reverse engineer your code to produce the UML.
That is do not use your code as input to a piece of software that then produces UML diagrams.
Any UML diagrams created in this way will be ignored.
•
All program listings and UML diagrams are to go into the students’ logbook.
•
All source code and data files to be stored in a directory named bookstore on a disk or CD.

Marking Criteria for Programming project

The following are indicative evidence for achieving the corresponding level. You must meet ALL the criteria for a level (as well as for all the previous levels!) to have reached that level.

留学之家留学DIY社区