Download Researchfinal doc and more Essays (university) Computer Programming in PDF only on Docsity!
Research in Object-Oriented System and
Development
By:
ABHISHEK LOKA
Fall 2008
CS 5335
Submitted to Professor: Dr. C. J. Hwang
Date: 12/05/
Texas State University
Contents
- Introduction 1.1 Project Motivation ------------------------------------------------------------------- 4 1.2 Project Description ------------------------------------------------------------------- 5 1.3 Summary of Interview/knowledge Acquisition ---------------------------------- 7 1.4 Business Forms ------------------------------------------------------------------- 11
- Use Cases of the Project 2.1 Scenarios and Use Cases ------------------------------------------------------------ 31 2.2 Use “Use Cases” diagram to Illustrate the System Model of this Project -------------------------------------------------------------- 34
PAGE * MERGEFORMAT 1
Registered user
2.3 Problem Statements for the Project, and Selected Good Classes ------------------------------------------------------------------- 37
- Class Model (Object Class Model) of the Project 3.1 Object Instances Diagram ------------------------------------------------------------ 41 3.2 Object Class Definitions, Class Attributes Descriptions and Association Description --------------------------------------------------------- 43 3.3 Final Class Model Diagram --------------------------------------------------------- 44 3.4 Method Descriptions or Pseudo Code Algorithms and Functional Specification of Each Major Method ------------------------------------------------ 45
5 Diagram Model
4
5
- State Model Diagram ---------------------------------------------- 61
- Activity Diagram ------------------------------------- 65
- Event Description Diagram -------------------------------------- 66
6 Implementation of the Project
6
7
5
5.1. Objects to Relational Databases --------------------------------- 88 5.2. Queries for the Application ---------------------------------------------- 90 5.3. Source Code---------------------------------------------------------------- 91
INTRODUCTION
1.1 Project Motivation:
This project attempts creating a new Internet bookstore called The Online Bookstore. The main idea behind this project is to implement the pre-defined patterns of an
Online Book Store Site, which aims at shopping the books over the internet easy.
The website will be similar in structure to Amazon.com, the current Internet
bookstore leader. In addition, we laid an emphasis in establishing a relation between
User and Author of the book thus making the site interactive. This project is divided into
five modules viz., Author module, Books module, Reader module, Check-out module and
Administrator module.
This project has been implemented by using HTML, JSP as front-end and
Microsoft Access as back-end under Windows environment. Javascript has been used for
Client-side validation
The Internet offers some significant advantages to the users and is becoming
increasingly popular. It gives access to books and their information which are not
available in the local store. It can save time and helps to avoid crowds. It saves money, as
some kinds of books are substantially cheaper in other countries. This site brings an
innumerable amount of books right to the home. Besides this it also allows an author to
place his book readily in the site thus exhibiting his books to the world in an easy
manner. The user can place his comments to the site and about the author on his views on
the books and thus makes him interactive with the site.
1.2 Project Description
CLIENT FUNCTIONALITY
This section describes how our user interface will work and how customers will view and be able to interact with our web site. A more detailed description of how different pages work internally will be discussed in following sections. We start by going over the types of users on our system. There are two different classes:
1. Users
Users can create their own account and can login with the account created. Once users have logged in from a previously created account, they have the rights to use our site. The users can view 8 types of pages:
- Home Page
- Search Page
- Book Information Page
- Account Creation Page
- Shopping Basket
- Login Page
- Help/Information Page
- Checkout Page
Common to All Pages Every page will have a menu bar at the top. This will allow users to move Fluidly around our system from any page making their task easier .The menu bar will offer the following options
Q1: What is the main Objective of your project?
I would like to develop an online bookstore system which maintains a vast database of books, makes different users (customers) to buy the books through internet. I should be able to view/update/delete all the details of the books and also capable of keeping track of present status of the stock which enables me to add those books which fall into shortage.
Q2: Do you have a search option for books? If so, what details of the book has to be provided? We do provide a search form which enables the system to search for all the available books online. For this purpose, the customer has to provide the following details of the book.
- Book title
- (^) Book author
- Book ISBN
Customers may search for books by specifying either any of these fields or with the combination any one or two fields.
Q3: What kinds of details are given to the customer after registration?
After undergoing registration process, each customer can start their shopping. Once the customer is done with buying, he/she is given the order number which keeps track of all the books he/she has purchased and can be able to view the details of the purchases in every visit of the site. Q4: Do you provide any unique identities for the clients?
Yes. Each customer is provided with a unique username and password after they complete their registration process. So, an old customer has to provide his/her username and password to continue shopping every time he visits our site. These details can be managed/updated/modified according to their own preferences.
Q5: Do you want to have any kind of payment information stored?
Yeah that would be better if I can store customer credit cards transactions and dates of payments. But if you want to store customer’s credit card information it will demand a lot more security than usual. You will also need to have a card reader and a secure and fast connection to a merchant bank server. Setting up of credit card transactions requires lots of infrastructure. You should be prepared for that. The software accordingly will need to have the ability to cope with that.
Q6: Do you need to have the details of the customer before he/she starts shopping? If so, what details should be provided?
Yes, it is mandatory for a customer to register before doing shopping. Once the customer registers for the first time, all his personal details are stored in our database and he/she can directly start shopping for the next visits. The registration process includes of entering the following personal details:
- Name and Address.
- Contact telephone.
- Sex and date of birth.
- Date of birth
- Credit card details
- Card Number
- Card Type
- Expiry date
- Email address.
then select express mail which is a bit expensive and the other two services takes more than 3 days comparatively less expensive.
Q10: Can we return the books?
Of course, you can. Separate forms are designed for the customers who want to return their books. For this, they need to provide book details like book title, ISBN no etc. and can be done thru mail and the confirmation can be viewed on the system immediately after the completion of the process.
Q11: Do you provide any other options for the users?
Yeah. We are providing for the customer to give the feedback and ratings for different books they have purchased and all these details are stored.
Q12: Tell me about how you will manage the stock details?
There may be more than one administrator. So, each administrator is provided with a unique username and password and has to provide these details before surfing through his screens. Once undergone by the authentication process, we can be able to add the new stock, keep track of old stock details, order for new books etc. We can also manage our account details like changing username, passwords, updating information etc.
Business forms
The project team also assembled a set of documents describing each of the use-cases identified in the use-case diagrams shown above. In some instances, the use-cases were described informally. For the more complex use-case scenarios, a more formal structure was used. As an example, consider the following partial description of the Checkout
use-case identified in the first diagram.
A Scenario:
A scenario is a very specific sequence of actions and responses that detail how the system will interact with a user. It is useful for pinpointing vague or missing requirements, and for verifying that the system does what's expected. A complete system would have several top-level scenarios, each showing a typical interaction with the system.
- User logs on.
- System displays welcome message and requests customer ID and password.
- User enters customer ID and password.
- System validates the ID and password.
- User searches for a title by browsing or keyword search
- System displays information about the title.
- User selects a title to buy
- System adds title to the customer's shopping cart
- [Repeat 5-8 until done]
- User is done with shopping
- System displays shopping cart, shipping address, and billing address
- User confirms order and payment method.
- System processes order, notifies warehouse for shipping, and issues an electronic receipt.
- User logs off.
- Entering the website:
Use case Diagram:
Logs on
User
2. System displays welcome message and requests customer ID and password.
The user visits the website at the homepage He can either enter username and password if he is registered user or register if he is new user.
Logs on
(Customer)
