Programming Exercise II:
An Online Bookstore Using an Object-Relational Database

(Industry-Level, Second-to-None Comprehensive Specifications)

---

Absolutely no copying others’ works
Development Requirements
When start developing the exercise, follow the three requirements below:

• Have to use the Oracle 12c (an object-relational database management system) and object-relational SQL.
• The exercise has to be Internet-enabled (a trend of current IT systems).
• The system entry page must be located at http://undcemcs02.und.edu/~user.id/513/2/ and all pages must be hosted by http://undcemcs02.und.edu/~user.id/ .
• The systems have to be active even after being graded until the end of this semester. They will be re-checked for plagiarism from time to time.

---

Due Date and Submission Methods
Due on or before Thursday, November 09, 2023. Send an email to the instructor at wenchen@cs.und.edu including

• the password for displaying the source code online (only one password for all interfaces and all exercises),
• the SQL create commands used, and
• an appointment to demonstrate your exercise to the instructor individually, so misunderstanding would be minimized. The instructor will prepare a set of test data to be used by all students. The instructor’s Zoom ID is https://und.zoom.us/j/2489867333 .

^†Note that you are allowed to use any languages and tools for this exercise, but the exams will focus on JDBC and Oracle technologies unless otherwise specified.

Objectives Database-driven web sites are a must for companies nowadays. This exercise has students design and implement a simple database-driven online bookstore by using Oracle 12c, an object-relational database, from the ground up.

Requirements
The bookstore includes the following features:

• The data of a book includes
  
  
  • a unique ISBN (10 characters),
  • a title, and
  • a price.


• The data of a customer includes
  
  
  • a unique ID (assigned by the system automatically after signing up),
  • a name, and
  • an account including
    
    
    • a list of purchased, unique books with an accumulative quantity each and
    • a total amount spent on the purchased books (one amount per customer).


• (System reset: 05%) The system can be reset, which is to clear all data stored in the database and files, so the instructor can test the system by using only his own test data. That is the system has to include a button such as “Clear system” on the system entry page.


• (Input: 10%)
  Enter books one by one for the one (and only one) system administrator.


• (Output: 30% total)
  For both administrator and customers:
  
  
  • (Listing all data: 10%) Both can display all hyperlinked book titles and only administrator can display all hyperlinked customer names.
  
  
  • (Listing book data: 10%) List all data of a specific book by clicking its hyperlinked title (including an ISBN, a title, a price, and a total number of this book sold).
  
  
  • (Listing customer’s data: 10%) List all data of a specific customer by clicking her/his hyperlinked account (including an ID, a name, the books purchased, a quantity for each book, and the total amount paid). A customer can only list his/her own data.
  
  
• (Customers: 45% total)
  For each customer:
  
  
  • (Customer signing up, in, and out: 15%)
    Customers can sign up, in, and out. The instructor will use multiple browsers, tabs, or computers to test your exercise at the same time.
  
  
  • (Searching for books: 15%)
    List the book if its price falls within a range:
    
          all   [$0 .. $10]   ($10 .. $20]   ($20 .. $30]   ($30 .. $∞]
    
    The search results are a list of hyperlinked book titles, checkboxes, and input fields for quantities.
  
  
  • (Purchasing books: 15%)
    Purchase the selected books in the search results at the same time. The quantities in the account are accumulative.


• (Instructor’s requirements: 10% total)
  Other than the above system requirements, the instructor has the following requirements:
  
  
  • (User-friendliness: 05%) User-friendliness will be heavily considered when grading. In the past, some exercises were awkward, which made the grading or browsing difficult. For example, it is considered not user-friendly if the system repeatedly asks users to enter their names/IDs/passwords.
  
  
  • (Plagiarism checking: 05%) It is for the instructor to find any plagiarism. Each interface includes a button “Display source,” which is to list ALL the source code for implementing the functions of this interface. Only one password is for all exercises and interfaces. The system will be highly suspected if fail to implement this button.

---

An Example of Web Page Display
Note that this example is not related to this exercise. It is only to show how to display web interfaces.


Evaluations
The following features will be considered when grading:

• Specifications:
  • The instructor (or your assumed client) has given the exercise specifications as many details as he possibly can. If you are confused about the specifications, you should ask in advance. Study the specifications very carefully. No excuses for misunderstanding or missing parts of the specifications after grading.
  • The specifications are not possible to cover every detail. You are free to implement the issues not mentioned in the specification, but the implementations should make sense. Implemented functions lacking of common sense may cause the instructor to grade your exercise mistakenly, and thus lower your grade.
  • The exercise must meet the specifications. However, exercises with functions exceeding the specifications will not receive extra credits.
  
  
• Grading:
  • This exercise will not be graded if the submission methods are not met. Students take full responsibility if the web site is not working.
  • A set of test data will be used by all students. The grades are primarily based on the results of testing. Other factors such as performance, programming styles, algorithms, and data structures will be only considered minimally.
  • Before submitting the exercise, test it comprehensively. Absolutely no extra points will be given after grading.
  • The total weight of exercises is 40% of the final grade, 12% for this exercise (RDB), 12% for Exercise II (ORDB), and 16% for Exercise III (embedded DB).
  • Multiple browser tabs, browsers, or computers will be used to test the systems at the same time to make sure the multi-processing is working well.
  • If not specified, no error checking is required; i.e., you may assume the input is always correct for that case. For example, the ISBN entered will always be a unique key of 10 characters.
  • Feel free to design your own interfaces; user-friendliness will be heavily considered; each function/button will be tested extensively; and from the source code submitted, the programs will be examined.
  • The newest Firefox browser will be used to grade exercises. Note that Internet Explorer, Edge, Chrome, and Firefox are not compatible. That is your exercises may work on the IE, Edge, or Chrome but not Firefox.
  • The instructor will inform you the exercise evaluations by emails after grading.


• Databases:
  • An object-relational database has to be used and try to perform the tasks by using SQL as much as possible because SQL, a non-procedural language, can save you a great deal of programming efforts.
  • The SQL DDL commands such as “create” have to be submitted, where SQL is Structured Query Language and DDL is Data Definition Language.
  • From the source code submitted, the database design and programs will be examined. Poor database design or uses will result in a lower grade.
  • (-10%) if the object-relational database Oracle 12c is NOT used.
  • (-10%) if any of the following Oracle 12c features is NOT used (i) collection types, (ii) user-defined types, and (iii) at least two non-trivial member methods using PL/SQL (like 10+ lines each method).
  • (-10%) if the database design is NOT optimal.
  • (-05%) if the SQL create commands of database implementation is NOT submitted.
  • There are many advantages of using databases. If database is not used, the problems caused by not-using-transaction must be considered. For example, if two customers are enrolled at the same time, an ID may be assigned to different customers if databases are not used.


• Comments:
  • Make the exercise work first. Do not include extra features, such as user passwords, in the beginning. By the way, you will not receive credits for the extra features.
  
  
  • Time management is critical for software development. If you are not able to complete the exercise, display whatever you have accomplished, so the instructor can give partial credit to your exercise.
  
  
  • Many times, simplicity is the same as user-friendliness.
  
  
  • One way to build a complex web system from scratch is to design the user interfaces first and then implement the system button by button. By doing this way, it could simplify the construction. The recommended construction steps are
    
    
    1. Examining the specifications very carefully,
    2. Designing the databases,
    3. Implementing the databases (SQL),
    4. Building the interfaces (HTML, CSS, and JavaScript),
    5. Implementing the system button by button (JDBC), and
    6. Testing the exercise thoroughly.