The document describes the design of an online bookstore system using RMI architecture. It includes four main parts: a client program, bookstore server program, bank server program, and naming service. The client program allows users to search for books, view their shopping cart, and manage their bank account. The bookstore and bank server programs each implement remote objects and services for manipulating books and bank accounts. The naming service maps names to references of remote objects.

2. Skeleton & dispatcher on server side/proxy per remote object on client side: Dispatcher pick request from the queue of communication module and send to appropriate skeleton, It is also responsible for marshalling and unmarshalling messages. On the other hand proxy provides an interface to call methods of remote objects.

3. Remote Objects: Remote Objects are objects that can receive call from other process on different machine.

5. Part II: Bookstore Server Program

6. Part III: Bank Server Program

8. Create Bank Account

9. Create BookStore Account

10. Sign In to Bank Account

11. Sign In to BookStore Account

12. Bank Menu provides the Options below

13. Deposit

14. Withdrawal

15. Return to main menu

16. Book Store Menu Appears with the options below

17. Search Books with Title

18. Search Books By Author

19. Add Selected Books to the Shopping cart

20. Display Shopping Cart Info

21. Checkout

23. Remote Reference Module (Bookstore Servant Class).

24. Skeleton & Dispatcher

26. Remote Object

28. Search Book: This use case is responsible for searching a book in the Book Store program. Searching a book can be in two means. Search by Author name and search by title of the book.

29. Add Book: This use case is responsible for adding a book in the Shopping cart.

30. Remove Book: This use case is responsible for deleting a book from the from the shopping cart.

31. CheckOut: This use case is responsible for checkout all the purchased books from the shopping cart. All corresponding transaction will occur in this phase. We will charge the user by the amount of all books and this amount will be deducted from the user’s bank account.

32. Deposit Amount: This use case is responsible for depositing some amount in the customers bank account. The Bank remote object is associated with this transaction.

33. Withdraw Amount: This use case is responsible for withdrawing some amount in the customers bank account. The Bank remote object is associated with this transaction.

34. DeleteBankAccount: In this use case we account for the case that a customer may delete his /her bank account.

35. CreateBankAccount: In this use case we account for the case that a customer may create a bank account.

36. Calculate Price: This case is responsible for calculating the price of all book being checkout from the shopping cart.

37. Validate & Adjust Book Quantity: This use case is responsible for validating the customer as well as the quantity of the available book in the bookstore.

38. Manage Book Account: There will be one bank account for the bookstore. After purchasing a book the corresponding amount will be deducted from the user and will be added to the bookstore’s bank account.

39. Book Inventory Control: In this case, we will manage the bookstore. Like when a new book arrive we will add it to the system and when the total quantity of a book gets to zero we will delete it from the bookstore.

40. Validate Account: In this case when a user provide his/her bank account we will check whether the account really exists and he/she has available balance.

41. Manage Bank Account: In this case we will provide features to add a new bank to the central bank and remove a bank from the central bank. Adding account to a existing bank is done under this use case.Conclusion: <br />The Design so far we have done is based upon our conceptual on RMI. We think and believe that it will change as we begin to pin point more details. So far, we have tried with our best effort for the design of the program.<br />