1.

ABSTRACT :

This project aims at developing an Online Auctioning System which can be used as an easy way to buy and sell articles over the internet, sitting comfortably at your own place. There are two types of users in the system a) Normal user and b) Administrator. The normal users of the system need to register to the site and login in order to access the Auction items in the site and participate in the auction. Unregistered persons (or) visitors can only view the common pages of the site. The registered users can inturn be either Buyers (customers/bidders) or Sellers (auctioneers). Sellers can create an Item for sale providing the item-name, description of the item, an image of the item, minimum bid price, bid increment, bid closing date etc. A separate auction will be held for each item. The buyers can bid by providing a bid amount (which should be greater than the previous bid) which is in consideration with the bid increment mentioned by the seller. The customer who bids the maximum amount for the product within the particular date assigned by the auctioneer will win the product, he bid in the auction. The payment can be done in person or via online using credit and debit cards.

The system will have an administration module administered by the administrator, to administer the categories of the shop as well as to block fraudulent users. The administrator will set up the Categories of the items. A category is a logical subdivision of Category of similar products (eg: Furniture, Electronic Accessories, Books etc) . Administrator should be able to create categories, merge category etc. There will be a Search by which users can browse through the provided categories and search for items up for sale. The notifications also should be provided to the buyers and sellers once the auction is complete and the product at the site should no longer be available (or) should be marked as sold once the payment is done by the customer who bid the most.

Thus the highly user-friendly application of online auctioning system is much beneficial to both customers, sellers for purchasing and selling products in an efficient and easy manner without any extra marketing costs. In this application, any kind of product can be auctioned and provide value-added services to the bidders and the sellers. The products will be authenticated and the site provides a safe environment for online users.

2. SYSTEM ANALYSIS

2.1 Existing System:

The existing system is a very old manual method which focusses on the active presence and participation of people in the auction. Prior to each auction, the date and time of auction, the venue and the items on auction are announced through publicity by news or media. The persons who are willing to take part in the auction have to arrive at the venue on the mentioned date by the prescribed time. It is advisable for the bidders to arrive much before so as to get registered to actively participate in the auction for the items on auction. The rules and regulations of the auction are stated and the minimum bid price is mentioned by the auctioneer (seller) who conducts the auction. The amount is incremented by the bidders each time. There is no time limit for this kind of auction because when no one bids, the auctioneer gives some three or four chances for the last bid amount to be the final one. If some person or party interrupts and increments, then the bidding process again goes on, else the item is won by the last bidder whose amount would be the maximum bid amount for the item.

Disadvantages :

This system requires the participants in the auction to be present in the fixed venue at the prescribed time before the bidding starts which may be difficult under some circumstances for both the customers and auctioneers. It does not provide secure registration and profile management of all the customers. It does not provide efficient account management and payment for the item on auction. It provides less security for data storage thus leading to data loss due to mismanagement of data. The persons who have missed the whereabouts of auction are unaware of the auction. The bidding process may go on at any limit thus leading to difficulty in financial settlement of both buyers and sellers. It does not provide the facility of sharing data among the users. The reliability and information about the product cannot be validated as they are known just before the start of auction.

2.2 Proposed System:

The proposed system aims to develop an online auctioning system whose main goal is to provide an easy way for buying and selling products over the web. The normal users of the system need to register to the site and login in order to access the Auction items in the site and participate in the auction. The registered users can in-turn be either Buyers or Sellers. Sellers can create an Item for sale providing the item-name, description of the item, an image of the item, minimum bid price, bid increment, bid closing date etc. A separate auction will be held for each item. The buyers can bid by providing a bid amount (which should be greater than the previous bid) . The system will have an administration module administered by the administrator, to administer the categories of the shop as well as to block fraudulent users.

Advantages:
The proposed system does not require the presence of the participants in auction as there is no venue and the process takes place over the internet, accessible to everyone who registers to the site. It provides secure registration and profile management of all the users. It provides efficient account management and payment for the item on auction. Periodic alerts or notifications are sent regarding the bidding to both buyers and sellers regarding the item on auction. Easy access to the users is provided by the availability of search option in the auction site. It provides security for data storage thus preventing data loss or mismanagement of data. The bidding process has a limit which is specified by the auctioneer by mentioning the last date for bidding, at the time of putting the product on sale thus leading to easier and faster financial settlement of both buyers and sellers. It provides the facility of sharing data among the users by maintaining discussion forums for their interaction regarding products value and originality thus leading to better reliability of the product. Administrator maintains the various categories of items in the auction site and blocks fraudulent users by enabling registration for authentication of users so as to participate in the auction.

3. REQUIREMENTS SPECIFICATION

Requirements Specification is a comprehensive description of the intended purpose and environment for application under development. It fully describes what the software will do and how it will be expected to perform. It minimizes the time and effort required by developers to achieve desired goals and also minimizes the development cost.

3.1 Functional Requirements :

No.
RS1

Requirement
The system should have a user login page The login id is locked if wrong password is entered 3 times consecutively. The system should have a user registration page.

Essential/ Description of the Desirable Requirement

Essential A login box should be there in the home page Robustness feature is enhanced.

Remarks
A registered user can only login. Locked system cannot be accessed for login Only registered users can access the auction site and the user details are stored in the database Upon not entering the essential valid details, dialog box appears with a message. For security purpose and flexibility of registered user.

RS2

Essential

RS3

Essential

The user profile should be stored in the database

RS4

RS5

Essential information of user to be filled should be marked by asterisk (*) in the registration form and information provided should be validated. The system should have a change password option.

Essential

The valid information should be compulsorily entered by the user without which registration process is incomplete. If old pass word is leaked, registered user should be able to change password

Essential

RS6

User should be able to browse through the various categories of items. The system should provide a form on the sales of an article. A search option should be provided for efficient and quick search to find an article. Seller should be able to edit the info about item and also upload option should be provided for images and relevant details. Item should be described in a video by the seller System should allow adding a new category if list of categories not available Seller should be able to extend the closing bid date

Essential

RS7

Essential

RS8

Essential

RS9

Essential

RS10

Desirable

RS11

Essential

RS12

Essential

RS13

Auction closing notifications must be sent to the mails and mobiles of the bidders Buyer and seller both should be able to view the bid history.

Essential

RS14

Essential

A click on the category should direct The categories the user to a new page can be created or relevant to the merged. category The sales form The details are provides details stored in the regarding the items on database. sale. The search results The search should be accurate results will and should match display whether with the requirements the item can be of the user. found or not. The info about item The buyers can and bid price and decide whether to increments will be bid or not based viewed by the on the info of the customers item and bid details. The item can be This is to clearly understood. facilitate the buyer regarding product bidding. Seller can use this For convenience option to add his of sellers to list required item in the their products newly created category The auction date of This is to involve the item can be more buyers for extended by seller to bidding the item get the desired price and to increase the bid price. Sms alerts and mails The notifications will notify the bidders are sent by the regarding the closing administrator of date so as to bid or the site. not. This gives the This gives the information regarding information about the previous bids. the previous bids.

RS15

Bid notifications also must be sent to the bidders once a bid is incremented, product goes on sale User should be able to change his profile details.

Essential

This is done so as to make all the bidders aware of the bid price and the product.

RS16

Essential

This is done generally to update the details in-case of transfer or change of address or mobile number.

RS17

System should provide item home page.

Essential

RS18

The user should be able to auction several items in one login session.

Essential

RS19

The user should be able to select an Item

Essential

RS20

The user should be able to place bid price on the items.

Essential

Contains item name, description, uploaded images, documents, seller name, min, current bid price, link to view the history of previous bids, bid increment. A button with a text box adjacent to put new bid The user can be buyer or seller. Buyer can bid for more than one item and seller can auction more than an item The Item home page can be reached either by search or by clicking on an Item while browsing categories. The bid price or bid amount can be placed in the text box provided in item home page.

The notifications may be sent to both buyer and seller in the form of sms alerts and mails Changing the details in-case of emergencies is must to maintain accurate and valid information. All the information regarding item should be put by the seller.

This facilitates the participation of users in more than one auction of an item. Information about the item is displayed.

The bid amount should match certain criteria of minimum bid price and bid increment and should be validated by the admin
6

RS21

The system should have an admin module

Essential

RS22

The system should provide a feature of special auctions

Desirable

RS23

System should provide logout option.

Essential

RS24

System should enforce a security module and provide block option. The system should provide an option for messages System can provide the types of auction for the user to choose.

Essential

RS25

Desirable

The admin is responsible for validations of the user details and the product on auction besides blocking fraudulent users. Rare articles may be withheld by seller with the permission of admin to be thrown open in special auctions. The account session of the registered user will be terminated as soon as the user logs out of the site Administrator should be able to block fraudulent users from using the system. Messages can be sent by other users or the system. The user can select best offers, special auctions or silent auctions. The users can share their views regarding the product and bid price. Customer should confirm the order and provide the credit card number for authentication

The admin is also responsible for profile management and secure payment.

These are held by the auction site to increase bid values of the item on sale. This option enhances security on a shared system. The fraudulent users are blocked and cannot access the auction items. User can view message, delete a message, reply a message. Auctions are decided based on the bid price, product quality etc This facilitates interaction between various users. Credit card number should be authenticated before processing the order. In case of fraud, an email should be sent to the customer.
7

RS26

Desirable

RS27

A discussion forum can be provided

Desirable

RS28

The customer who wins the auction should transact the amount online and the order by customer should be confirmed and authenticated

Essential

3.2 OPERATING ENVIRONMENT

3.2.1 Software Requirements : Serial Number

1 2 3 4 5 6 7

TYPE
Operating System Database Web Server Deployment Programming Language User Interface Client-side Script languages Web Applications

DESCRIPTION
Windows XP/2000/2007 Oracle 10g Tomcat5 Java (JDK 1.4) HTML, CSS Javascript JDBC, JSP

Alternatives (If available)

Linux MS-SQL / MySQL JBoss

ASP

3.2.2 Hardware/System Requirements:

Serial Number
1 2 3 4 5

TYPE
Processor RAM HardDisk Input Device Output Device

DESCRIPTION
Pentium IV 512 MB 2 GB Keyboard, Mouse Monitor

Alternatives (If available)

Intel I3 core processor Acceptable if >512MB also Acceptable if >2GB also

3.3 DATABASE FIELD SPECIFICATION

This contains the specification of various database fields in the database. Following tables might be needed to serve the application. Item Table To store the details about the item (item name, item id, bid status) User Table To store the details about the user (user name, password, items Uploaded for selling ) Admin Table To store the details about the sellers and bidders(bidder name, seller name, last bid price, person who won the bid, payment etc)

Item Table

Serial No.
1

Field Name

Range of valid values for the field

1 to 100

Remarks

Item_Name

2 3 4 5 6 7

Item_Description Item_Id Bid_Status Bid_StartDate Bid_EndDate Bid_Increment

Up to 4000 characters in length. 1 to 1000 A or I Date Date Any positive value not so large. Any positive value assigned as minimum value 1to 1000 Upto 4000 characters in length {Doc, Image, Video} S or P

Min_bidprice

This is the key field of the database as it is unique for an Course. Gives information regarding the item A unique id for the Item Active or Inactive The date the bidding process starts. The date the bidding process ends. It can be incremented by any amount depending on the value of the item Provided by either the admin or the seller of the item The category to which the item belongs Gives information regarding the category of items. The type of upload (document/image/video of the item that is uploaded) Sold or Pending
9

9 10 11

Category_Id Category_Description Upload Type

12

Item_Status

User Table Serial Field Name No.

Range of valid values for the field

Remarks

1 2

First_Name Second_Name

Upto 20 characters in length. Upto 20 characters in length. Upto 20 characters in length. Upto 10 characters in length

This is the first name of the user This is the second or middle name of the user (probably the last name or the surname) This is the login name of the user which is the key field of the database as it is unique Does not contain any special characters and provides security. Dob provided by the user Male or Female Mobile or landline number of user should be provided Checking if provided mail-id is valid or not. The city in which the user lives should be mentioned by the user The district to which the user belongs should be mentioned The state to which the user belongs should be mentioned The country to which the user belongs should be mentioned The valid or permanent address of user must be provided for contact purpose Verify if pincode is valid or not.

User_Name

password

5 6 7 8 9

Date_of_birth Gender Phone_no Email_id City/Town

Date M or F Upto 10digits Upto 25 characters in length Upto 20 characters in length

10 11 12 13

District State Country Address

Upto 20 characters in length Upto 20 characters in length Upto 20 characters in length Upto 400 characters in length Upto 10 digits

14

Pincode

10

15 16

Qualification Occupation

Upto 5 characters in length Upto 20 characters in length

The degree upto where the user holds is mentioned The financial and working condition of the person is mentioned Security question incase of account recovery Security answer incase of account recovery Messages are sent between users Sender of the message Receiver of the message

17 18 19 20 21

Question Answer Message Sender Receiver

Upto 50 characters in length Upto 10 characters in length Upto 50 characters in length Upto 20 characters in length Upto 20 characters in length

Admin Table Serial Field Name No.

1 2 3 4 5 Admin_id Customer_id Seller_id Bid_winner Card_type

Range of valid values for the field

Upto 10 digits Upto 10 digits Upto 10 digits Upto 20 characters in length Upto 20 characters in length Upto 20 characters in length Upto 20 characters in length Upto 20 characters in length Date

Remarks
Unique id for the admin Unique id for the customer/buyer/bidder Unique id for the seller The name of the bidder who won the auction The type of the card (whether credit or debit) the bidder wants to perform transaction The name of the bank to which the card belongs. The name of the bank branch where the amount is deducted DD or cash or online. The date amount has been received from buyer and sent to seller The unique id of the card Received amount or Pending Transaction Received product or Pending transaction
11

6 7 8 9

Bank_name Branch_name Payment_mode Transaction_date

10 11 12

Card_number Seller_status Bidwinner_status

Upto 20 characters in length R or P R or P

3.4 TEST PLAN:

3.4.1 UNIT TEST PLAN:
This test focuses on verification effort on the smallest unit of software module. Using the detailed design and the process specifications , testing is done to uncover errors within the boundary of the module. All the modules must be successful in the unit test before the integration testing begins. In this project each service is a module like Login, Admin etc. Each module has to be tested by giving different sets of inputs. The inputs are validated while accepting from user.

Serial No.
UT1

TESTCASE TITLE
Successful User loginVerification

DESCRIPTION

The EXPECTED Requirement OUTCOME in RS that is being tested

Login should be successful and the user should enter into the system Login fails with an error Invalid Password Login fails with an error Invalid username A dialog box indicating to fill complete details. A dialog box stating mismatch of passwords so enter password again Selling form details will be displayed RS1

UT2

Unsuccessful User Verification Unsuccessful User Verification Insufficient information in registration page Mismatch of passwords in registration form

UT3

UT4

The login to the system should be tried with the username assigned by the admin and the correct password Login to the system with a wrong password Login to the system with a wrong username Essential information to be provided by user is missing

RS1

RS1

RS4

UT5

UT6

User provides different passwords for both in the textboxes for password and confirm password Displaying selling User who puts an item form by clicking for auction fills the on the sell button selling form by clicking on sell button.

RS3

RS7

12

UT7

UT8

User auctioning more than one item in one login session Viewing the bid history Adding a new category Seller extends close date User tries to extend the close date Selecting an item by clicking on the item in the category Selecting an item by using search field Displaying item home page

User bids on several items in the same session It shows all the biding information A new category has to be added to the category list. Seller of the item can extend the close date of the auction User other than the seller is trying to extend the close date User can select the desired item.

UT 9

UT 10

UT 11

UT 12

System should allow the user to bid on several items. The History of the bids is displayed System should allow to add a new category Close date is successfully updated System should not allow the user to extend the close date Desired items home page is displayed Desired items home page is displayed items home page is displayed System should allow the user to change his details The search results should display all the items which matched the search criteria System should display no results found. All the items under the category must be displayed. System need to display category not found

RS18

RS14

RS11

RS12

RS12

RS19

UT 13

User can select the desired item. User selects an item and the desired items home page is displayed User changes his personal details.

RS8

UT 14

RS17

UT 15

User changes his details.

RS16

UT 16

Searching a valid item by entering a valid name in search field.

User searches the item by giving its name

RS8

UT 17

Searching an invalid item Searching the available category. Searching a new category

User tries to search an item that is not present User enters a category name to search

RS8

UT 18

RS8

UT 19

User searches for a new category

RS8

13

3.5 Integration Test Plan:

Integration testing (sometimes called integration and testing, abbreviated I&T) is the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before validation testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.

No.

Test case Title

Description

Expected Outcome

The requirement in RS that is being tested

RS1

IT1

Successful User Verification

The login to the system should be tried with the login assigned by the admin and the correct password Login to the system with a wrong password

IT 2

Unsuccessful User Verification due to wrong password

IT 3

Unsuccessful User Verification due to invalid login id

Login to the system with a invalid login id

IT4

User enters valid information in the registration page.

All the essential details are filled in the registration page.

Login should be successful and the user should enter in to the system Login should fail with an error Invalid Password Login should fail with an error Invalid user id User is successfully registered and information is stored in the database.

RS1

RS1

RS3

14

IT5

User enters wrong mail id

IT6

Successful customer authentication

IT7

Successful mail sending to customer

IT8

Checking the messages

System should not accept and display wrong email id. Verifying the email id The and customer Credit card number by can interact an administrator with the service provided by the server Information is sent to Customer the customer through gets the mails. information in the form of mails successfully The user can check his User can mails view message. User can send messages to other valid user Messages are successfully sent

User enters invalid email id

RS4

RS4

RS15

RS25

IT 9

Sending a message to a valid user

RS25

15

4. DESIGN

4.1 HIGH-LEVEL DESIGN:

In high-level design, the project is divided into modules and brief description about each module is given. The different modules in this project are mainly the administrator module, user module, message module and security module.

ADMINISTRATOR MODULE : The admin module has to verify all the details given by both the buyer and seller. It also provides complete information related to products on sale and the buyers can bid for the products and can own them. All this has to be provided and maintained by the admin because the complete auction process is to be kept under control till the product sale gets confirmed and the bidding process ends. USER MODULE: As mentioned earlier there are two types of registered users who access the auction site. They come under the category of either buyers or sellers Sellers- who put the product on sale. In the seller module, the seller can display all his products and put them on sale and can call the people for the auction then after receiving the final bidding whichever is the highest that highest bidder owns the product. Seller can have the benefits directly without any third people involvement. Buyers- Generally they are the bidders who bid for the product on sale and later buy them if they win the auction. In this application buyer can buy any product from any part of the world at a very best competitive price and own the product. Buyer has to just furnish their details and can participate in the bidding to acquire the product, which is for sale. There may also be visitors who do not participate in the auction process but visit the application online, register themselves and keep track of the auctioning activities and have the information of various products on sale. If unregistered, they may see only static pages of the home page. MESSAGE MODULE: In this module, administrator and the users can post and receive messages according to their need. SECURITY MODULE: Security and authentication is provided in the form of login and registration of the users. Login checks for a unique username and password.

16

4.2 LOW-LEVEL DESIGN:

In low-level design, we specify the functionality of every module in depth.

ADMINISTRATOR MODULE : The administrator has to log on to the system with his user id and password in order to perform his responsibilities. The responsibilities of the administrator are as follows:1. Manage the users of the system like seller and buyer. 2. Manage the fraud data; if admin detects any fraud data entered by any user then he can block those fraudulent users from accessing the site. 3. Add categories for the product. 4. Merge the product categories. 5. View transaction reports. 6. View auction process details 7. Process the transaction 8. Settle the transaction within time 9. Send sms and email alerts . 10. Organize special auctions.

USER MODULE: The various functionalities of the users, i.e, sellers and buyers are as follows:1. Seller: Register himself and provide the product details: Once registered, a user can post an item for sale. He would be seller of the item. He gives all information related to product and puts product to auction. Edit item details: Seller can edit details of the items like extending auction end date, decreasing the bid amount, uploading new image, changing the description. Edit users account page: He can change his account details like changing contact information. Messages: He can send messages to other registered users and see his own mails. Buyer: Category browsing: He can browse through various categories through search field or by clicking on the category link. Select an item: Bidder can select an item by clicking on item link.

2.

17

 View bidding history: Bidder can view the bidding history made on the product. Place new bid: Bidder can bid on an item by clicking on the image. Then he can enter the new bid value in the item home page. Payment details: Once the bidder wins the auction he enters the payment details like bank account number and other details. Visitor Module: Category browsing He can browse through various categories through search field or by clicking on the category link.

SECURITY & AUTHENTICATION MODULE: 1. Login security: Users need to login for selling and bidding on the product. Login page verifies the username and checks the password. 2. Validate users: Any user can view the site but only registered users can sell or bid the products. Fraudulent users are not allowed to access the site. Only valid users can perform specific functions.

MESSAGE MODULE: In this module, different users and administrator can post and receive messages according to their need.

In additional there may be optional modules like : Bid Status Module This module fully concentrates on interaction between the bidder and customer based on the bid price. The bid status is informative for a customer when he bids a price that is it shows maximum price from the time of auction started. Based on this information only bidder will decide for this customer to sell this product. Report Module This module will be helpful for administrator to know current situation what is going on between bidder and customer. So each every transaction is been monitored and reported in this module.

18

4.2.1Data Flow Diagrams:

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modeling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated. DFDs can also be used for the visualization of data processing (structured design). A DFD shows what kinds of information will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel (which is shown on a flowchart).

Following are the data flow diagrams of the various people like sellers , buyers , administrators etc., involved in the system.

Functions of a normal user:

19

Authenticated users:

DFD showing the functionalities of buyer:

20

DFD for seller:

DFD for administrator:

21

Connection between various persons involved in Online Auction

Online Auction Process:-

22

4.2.2 UML Diagrams:

Class Diagram:

23

Use-Case Diagrams:

System Use Case Diagram:

System

Admin

OnLine Auctioning System

Customer

Admin Use Case Diagram:

View Customers

View Bid Items

New Auction Items Today

Admin Auction Items Endday

ViewProfile

24

Buyer/ Seller (Customer) Use Case Diagram:

Registration

Login

Buy

Items Sell

Customer ViewProfile

New Auction Items today

New Auction Items EndDay

Sequence Diagrams:

Buyer/ Seller (Customer) Sequence Diagram:

Customer Login BuyItem SellItem Auction Items Today Auction Item EndToday

1 : enterLogin()

2 : validate()

3 : loginSuccess() 4 : bidTheItem() 5 : sellTheItem() 6 : viewAuctionItemsToday() 7 : viewAuctionItemsEndToday()

25

Administrator Sequence Diagram:

Customers BidItems

Admin

Login

ActionItems

1 : login()

2 : validate()

3 : AdminHome() 4 : viewCustomers()

5 : viewBidItems() 6 : viewAuctionItemsToday() 7 : viewAuctionItemsEndDay()

26

Activity Diagram:
Administrator Activity Diagram:

Admin

Login Fail

Enter Username,password

Success

Home

Item

Categories

BiddingInfo

LogOut

Add Items

View Items

Add Categories

View Categories

Add BiddingInfo

View BiddingInfo

27

Seller (Owner of the Article or customer) Activity Diagram:

OwnerOf Article

Login Fail

Enter Username,password

Success

Home

Item

Categories

BiddingInfo

LogOut

View Items

View Categories

View BiddingInfo

Update Items

delete Items

Update Bidding Info

Delete Bidding Info

28

Buyer (Registered Bidder or customer) Activity Diagram:

Registered Bidder

Login Fail

Enter Username,password

Success

Home

Item

Categories

BiddingInfo

LogOut

View Items

View Categories

View BiddingInfo

29

Component Diagram:

30

4.3. Database Design:

4.3.1 List of Tables: Tables
Admin_login: Customer_master: Category_details: Listofitems:

Description
This table maintains login details like login name, password, question, answer of admin. This table maintains login details like login name, password, question, answer of users. This table maintains category name, categoryabbr and categorydesc. This table maintains prodid, itemname, categoryname, itemdesc, price, begin and end date. This table contains prodid, loginname, bamount, dateofbid. This table maintains prodid This table contains message, sender, receiver. This table contains payment details like ddnumber, drawn date, card holder name and number.

Bid_details: Temp_details: Mesg: Payments:

4.3.2 Table Fields:

Table Field gives the fields related to each table of database.

Admin_login
No
1 2 3 4 5 6 7 8 9 10 11 12 13

Field name
Aid Firstname Lastname Login_name Password DOB Address City State Email Occupation Question Answer

Range of valid values for the Field

Up to 5 digits Up to 20 characters Up to 20 characters Up to 20 characters Up to 15 characters Date Up to 255characters Up to 20 characters Up to 20 characters Up to 24 characters Up to 15 characters Up to 50 characters Up to 24 characters

Remarks

Primary key

Security question Security answer

31

Customer_table
No. 1 2 3 4 5 6 7 8 9 10 11 12 13 Field name Cid Firstname Lastname Login_name Password DOB Address City State Email Occupation Question Answer Range of valid values for the Field Up to 5 digits Up to 20 characters Up to 20 characters Up to 30 characters Up to 20 characters Date Up to 255characters Up to 20 characters Up to 20 characters Up to 30 characters Up to 15 characters Up to 50 characters Up to 20 characters Remarks

Primary key

Security question Security answer

Category_details
No. 1 2 3 Field name Categoryname Categoryabbr Categorydesc Range of valid values for the Field Up to 20 characters Up to 20 characters Up to 20 characters Remarks Primary key

Listofitems
Field name No. 1 2 3 4 5 6 Prodid Itemname Categoryname Price Auc_begindate Auc_enddate Range of valid values for the Field Up to 5 digits Up to 30 characters Up to 30 characters number date date Foreign key Remarks

Primary key

32

7 8 9 10

Description Login_name Timeleft Status

Up to 30 characters Up to 30 characters Up to 3 digits Up to 10 characters Foreign key

Bid_details
Field name No. 1 2 3 4 5 Prodid Bid_amount Login_name Dateofbid Status Range of valid values for the Field Up to 5 digits Number Up to 30 characters date Up to 10 characters Foreign key Remarks

Foreign key

Temp_details
Field name No. 1 Prodid Range of valid values for the Field Up to 3 digits Remarks

Foreign key

Mesg
Field name No. 1 2 3 4 Message Admin_sender Sender Recv Range of valid values for the Field Up to 60 characters Up to 15 characters Up to 15 characters Up to 15 characters 33 Remarks

Foreign key Foreign key

Payments
Field name No. 1 2 3 4 5 6 7 8 9 Prodid Login_name Pay_mode Dd_no Drawn_date Payable_at Card_holder_name Card_number Card_type Range of valid values for the Field Up to 5 digits Up to 30 characters Up to 10 characters Up to 12 characters Up to 12 characters Up to 20 characters Up to 25 characters Up to 16 characters Up to 8 characters Remarks

Foreign key Foreign key

34

5. Testing:

Introduction:
Testing is defined as the process in which defects are identified, isolated, subjected for rectification and ensured that product is defect free in order to produce the quality product and hence customer satisfaction. Quality is defined as justification of the requirements Testing performs a very critical role for quality assurance and for ensuring the reliability of software. The results of testing are used later on during the software maintenance.

Testing begins then unit level and works outward toward the integration of the entire system. Different testing techniques are appropriate at different points of software development cycle.

Testing Types:
There are mainly two types mainly corresponding to the development of any application. The two different types of testing are: Unit testing Integration testing

5.1 Unit Testing:

This test focuses on verification effort on the smallest unit of software module. The first level of testing is the Unit Testing which is done during the development of the system. It is laid on each module of the project so that each module works individually according to the specification. Unit testing is essential for verification of the code produced during the coding phase. Errors have been noted and corrected immediately and the program clarity has been increased. At the end of the unit testing, bug fixation is triggered and on completion of fixation and confirmation, the software under development passes to next level of testing. In the developed system the unit testing is performed by testing each module. Using the detailed design and the process specifications testing is done to uncover errors within the boundary of the module. All the modules must be successful in the unit test before the start of the integration testing begins. In this project each service is a module like Login, Forms etc. Each module has to be tested by giving different sets of inputs. The inputs are validated when accepting from user.

35

No.

Test case Title

Insufficient information provided in the registration form. Displaying selling form by clicking on the sell button

Description

Observed Outcome
A message is displayed saying to fill the complete details.

The requirement in RS that is being tested

Result

UT1

User does not give entire information some essential information might be missing. User who puts an item for auction fills the selling form by clicking on sell button. User ignores some essential details like name & category.

Passed RS4

UT2

selling form details will be displayed

RS7

Passed

UT3

Filling incomplete details in the selling form Browsing categories by clicking on the category name on the page.

System should display incomplete details.

RS9

Passed

UT4

The user can chooses the efficient browsing categories

The entire details of chosen categories are displayed in new page

RS6

Passed

UT5

Browsing categories by entering the category name in search field. Updating the selling form by a valid user

The user can chooses the efficient browsing categories

The entire details of chosen categories are displayed in new page

RS6

Passed

UT6

The seller of the item only, can update the information in the selling form User bids on several items in the same session

The changes like editing item. Uploading new image are done successfully System should allow the user to bid on several items.

RS9

Passed

UT7

User auctioning more than one item in one login session

RS18

Passed

36

UT8

Viewing the bid history Adding a new category

It shows all the biding information A new category has to be added to the category list. Seller of the item can extend the close date of the auction User other than the user is trying to extend the close date User can select the desired item.

The History of the bids is displayed System should allow to add a new category Close date is successfully updated

RS14

Passed

UT 9

RS11

Passed

UT 10

Seller extends close date

RS12

Passed

UT 11 UT 12

UT 13 UT 14

User tries to extend the close date Selecting an item by clicking on the item in the category Selecting an item by using search field Displaying item home page User changes his details. Searching a valid item by entering a valid name in search field. Searching an invalid item Searching the available category. Searching a new category

System should not allow the user to extend the close date Desired items home page is displayed

RS12

Passed

RS15

Passed

User can select the desired item. User selects an item and the desired items home page is displayed User changes his personal details. User searches the item by giving its name

Desired items home page is displayed items home page is displayed

RS8

Passed

RS17

Passed

UT 15 UT 16

System should allow the user to change his details The search results should display all the items which matched the search criteria System should display no results found. All the items under the category must be displayed. System need to display category not found

RS16

Passed

RS8

Passed

UT 17 UT 18 UT 19

User trys to search an item that is not present User enters a category name to search User searches for a new category

RS8

Passed

RS8

Passed

RS8

Passed

37

5.1.2 Integration Testing:

The second level of testing includes Integration Testing. It may not be the case that software packages whose modules when run individually and showing perfect results, will show perfect results when running as a whole. The various modules after being tested individually are combined for proper test result in integration testing. After the unit testing the integration of modules has to be done and then integration testing can be done. The goal here is to see if modules can be integrated properly, the emphasis being on testing interfaces between different modules.

No.

Test case Title

Description

Observed Outcome

The requirement in RS that is being tested

RS1

Result

IT1

Successful User Verification

The login to the system should be tried with the login assigned by the admin and the correct password Login to the system with a wrong password

Login should be successful and the user should enter in to the system Login should fail with an error Invalid Password Login should fail with an error Invalid user id

Passed

IT 2

IT 3

IT4

Unsuccessful User Verification due to wrong password Unsuccessful User Verification due to invalid login id User enters valid information in the registration page. User enters wrong mail id

RS1

Passed

Login to the system with a invalid login id

RS1

Passed

All the essential details are filled in the registration page.

User is successfully registered and information is stored in the database. System should not accept and display wrong email id.

RS3

Passed

IT5

User enters invalid email id

RS4

Passed

38

IT6

Successful customer authentication

Verifying the email id and Credit card number by an administrator Information is sent to the customer through mails.

IT7

Successful mail sending to customer

IT8

Checking the messages Sending a message to a valid user

The user can check his mails User can send messages to other valid user

The customer can interact with the service provided by the server Customer gets the information in the form of mails successfully User can view message. Messages are successfully sent

RS4

Passed

RS15

Passed

RS25

Passed

IT 9

RS25

Passed

Bugs:
A software bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's source code or its design, or in frameworks and operating systems used by such programs, and a few are caused by compilers producing incorrect code. A program that contains a large number of bugs, and/or bugs that seriously interfere with its functionality, is said to be buggy. Reports detailing bugs in a program are commonly known as bug reports, defect reports, fault reports, problem reports, trouble reports, change requests, and so forth.

The bugs encountered while developing this application may be,

1) Failure in inserting values into the database will generate a null pointer exception. 2) Another usual exception we come across is the data type mismatch, this exception is encountered when the data type of the value entered differs from the type with which it is declared. 3) Improper connection establishment between the front end and the back end will provoke the exceptions. To overcome this scenario, proper connectivity must be maintained.

39

6. Screen Shots:
Home page:

Registration page:

40

Visitor searching items using search field:

Login page:

41

Customer home page:

Displaying customer profile details:

42

Item selling form:

Viewing items placed for auction:

43

Updating item page:

Customer browsing through categories:

44

Customer changing password:

Bidding items page:

45

Payments page:

Bidding on an item:

46

Customer viewing new items:

Viewing watchlist:

47

Admin home page:

Admin adding new category:

48

Admin modifying category:

Admin viewing customers:

49

Admin sending message to customers:

Logout screen:

50

7. Conclusion:

This developed application provides a user-friendly auctioning environment where any kind of product can be auctioned. It reduces errors due to human intervention. It provides an easy way for finding all the items of sale. It also provides value-added services to the bidders and the sellers. Currently consumers are much more likely to shop on the Internet than businesses. A

business is taking a much bigger risk if they purchase from an auction since the value of the purchase is generally much more than a consumer purchase. It is our belief, however, that, as businesses try to trim expenses, they will turn to online auctions for commodity products

Limitations of the system:

Advanced techniques are not used to check the authorization. Customer cannot add additional images, documents and videos (if any) to the items. A user is unable to search other users.

Future Enhancements:
It is not possible to develop a system that makes all the requirements of the user. User requirements keep changing as the system is being used. Some of the future enhancements that can be done to this system are: A user can specify the areas in which he is interested to participate for auction. A user can select a particular users items and bid for the same. Rating mechanism for users can be implemented. Advanced authorization techniques can be implemented for restricting fraudulent users. Sms and email alerts can be sent to users on arrival of new items.

51

8. Bibliography:
https://campusconnect.infosys.com www.w3schools.com http://www.wikepedia.com www.onlineautions.com www.ebay.com www.amazon.com Database Management System, by Raghu Ramakrishnan, Johannes Gehrke, Mc Graw-Hill International Edition Software Engineering by Roger S.Pressman,1977, (Fourth Edition), McGraw-Hill International Edition The Complete Reference JAVA by Herbert Schildt. HTML Black book by Steven Holzner.

52