Development of Online Auctioning System for organization

8/12/2019 Development of Online Auctioning System for organization

1/52

1

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 ownplace. 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 in-

turn be eitherBuyers (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

soldonce 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/52

2

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 mentionedby 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 theprescribed 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.


3/52

3

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 byproviding 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 asthere 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 auctionsite.

It provides security for data storage thus preventing data loss or mismanagement ofdata.

The bidding process has a limit which is specified by the auctioneer by mentioning thelast 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 blocksfraudulent users by enabling registration for authentication of users so as to participate

in the auction.


4/52

4

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. Requirement

Essential/

Desirable

Description of the

Requirement Remarks

RS1 The system should

have a user login page

Essential A login box should be

there in the home

page

A registered user

can only login.

RS2 The login id is locked

if wrong password is

entered 3 times

consecutively.

Essential Robustness feature is

enhanced.

Locked system

cannot be

accessed for

login


have a user registration

page.

Essential The user profile

should be stored in

the database

Only registered

users can access

the auction site

and the user

details are stored

in the database

RS4 Essential information

of user to be filled

should be marked by

asterisk (*) in the

registration form and

information provided

should be validated.

Essential The valid information

should be

compulsorily entered

by the user without

which registration

process is incomplete.

Upon not

entering the

essential valid

details, dialog

box appears with

a message.


have a change

password option.

Essential If old pass word is

leaked, registered user

should be able to

change password

For security

purpose and

flexibility of

registered user.


5/52

5

RS6 User should be able to

browse through the

various categories of

items.

Essential A click on the

category should direct

the user to a new page

relevant to the

category

The categories

can be created or

merged.

RS7 The system shouldprovide a form on the

sales of an article.

Essential The sales formprovides details

regarding the items on

sale.

The details arestored in the

database.

RS8 A search option should

be provided for

efficient and quick

search to find an

article.

Essential The search results

should be accurate

and should match

with the requirements

of the user.

The search

results will

display whether

the item can be

found or not.

RS9 Seller should be able toedit the info about item

and also upload option

should be provided for

images and relevant

details.

Essential The info about itemand bid price and

increments will be

viewed by the

customers

The buyers candecide whether to

bid or not based

on the info of the

item and bid

details.

RS10 Item should be

described in a video by

the seller

Desirable The item can be

clearly understood.

This is to

facilitate the

buyer regarding

product bidding.

RS11 System should allow

adding a new category

if list of categories not

available

Essential Seller can use this

option to add his

required item in the

newly created

category

For convenience

of sellers to list

their products

RS12 Seller should be able to

extend the closing bid

date

Essential The auction date of

the item can be

extended by seller to

get the desired price

This is to involve

more buyers for

bidding the item

and to increase

the bid price.

RS13 Auction closing

notifications must be

sent to the mails and

mobiles of the bidders

Essential Sms alerts and mails

will notify the bidders

regarding the closing

date so as to bid or

not.

The notifications

are sent by the

administrator of

the site.

RS14 Buyer and seller both

should be able to view

the bid history.

Essential This gives the

information regarding

the previous bids.

This gives the

information about

the previous bids.


6/52

6

RS15 Bid notifications also

must be sent to the

bidders once a bid is

incremented, product

goes on sale

Essential This is done so as to

make all the bidders

aware of the bid price

and the product.

The notifications

may be sent to

both buyer and

seller in the form

of sms alerts andmails

RS16 User should be able to

change his profile

details.

Essential This is done generally

to update the details

in-case of transfer or

change of address or

mobile number.

Changing the

details in-case of

emergencies is

must to maintain

accurate and

valid

information.

RS17 System should provide

item home page.

Essential Contains item name,

description, uploadedimages, 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

All the

information

regarding item

should be put by

the seller.

RS18 The user should be

able to auction several

items in one login

session.

Essential The user can be buyer

or seller. Buyer can

bid for more than one

item and seller can

auction more than an

item

This facilitates

the participation

of users in more

than one auction

of an item.

RS19 The user should be able

to select an Item

Essential The Item home page

can be reached either

by search or by

clicking on an Item

while browsing

categories.

Information

about the item is

displayed.

RS20 The user should be able

to place bid price on

the items.

Essential The bid price or bid

amount can be placed

in the text box

provided in item

home page.

The bid amount

should match

certain criteria of

minimum bid

price and bid

increment and

should be

validated by theadmin


7/52

7


have an admin module

Essential The admin is

responsible for

validations of the user

details and the

product on auctionbesides blocking

fraudulent users.

The admin is also

responsible for

profile

management and

secure payment.


provide a feature of

special auctions

Desirable Rare articles may be

withheld by seller

with the permission of

admin to be thrown

open in special

auctions.

These are held by

the auction site to

increase bid

values of the item

on sale.

RS23 System should provide

logout option.

Essential The account session

of the registered user

will be terminated as

soon as the user logs

out of the site

This option

enhances security

on a shared

system.

RS24 System should enforce

a security module and

provide block option.

Essential Administrator should

be able to block

fraudulent users from

using the system.

The fraudulent

users are blocked

and cannot access

the auction items.


provide an option formessages

Desirable Messages can be sent

by other users or thesystem.

User can view

message, delete amessage, reply a

message.

RS26 System can provide the

types of auction for the

user to choose.

Desirable The user can select

best offers, special

auctions or silent

auctions.

Auctions are

decided based on

the bid price,

product quality

etc

RS27 A discussion forum can

be provided

Desirable The users can share

their views regardingthe product and bid

price.

This facilitates

interactionbetween various

users.

RS28 The customer who

wins the auction should

transact the amount

online and the order by

customer should be

confirmed and

authenticated

Essential Customer should

confirm the order and

provide the credit

card number for

authentication

Credit card

number should be

authenticated

before processing

the order. In case

of fraud, an email

should be sent to

the customer.


8/52

8

3.2 OPERATING ENVIRONMENT

3.2.1 Software Requirements :

Serial

Number

TYPE DESCRIPTION Alternatives (If

available)

1 Operating System Windows XP/2000/2007 Linux

2 Database Oracle 10g MS-SQL / MySQL

3 Web Server

Deployment

Tomcat5 JBoss

4 Programming

Language

Java (JDK 1.4)

5 User Interface HTML, CSS

6 Client-side Script

languages

Javascript

7 Web Applications JDBC, JSP ASP

3.2.2 Hardware/System Requirements:

Serial

Number

TYPE DESCRIPTION Alternatives (If

available)

1 Processor Pentium IV Intel I3 core processor

2 RAM 512MB Acceptable if>512MB also

3 HardDisk 2 GB Acceptable if

>2GB also

4 Input Device Keyboard, Mouse

5 Output Device Monitor


9/52

9

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 TableTo store the details about the item (item name, item id, bid status)

User TableTo store the details about the user (user name, password, items

Uploaded for selling )

Admin TableTo 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.

Field Name Range of valid

values for the

field

Remarks

1 Item_Name 1 to 100 This is the key field of the

database as it is unique for an

Course.2 Item_Description Up to 4000

characters in length.

Gives information regarding

the item

3 Item_Id 1 to 1000 A unique id for the Item

4 Bid_Status A or I Active or Inactive

5 Bid_StartDate Date The date the bidding process

starts.

6 Bid_EndDate Date The date the bidding process

ends.

7 Bid_Increment Any positive value

not so large.

It can be incremented by any

amount depending on the

value of the item8 Min_bidprice Any positive value

assigned as

minimum value

Provided by either the admin

or the seller of the item

9 Category_Id 1to 1000 The category to which the

item belongs

10 Category_Description Upto 4000

characters in length

Gives information regarding

the category of items.

11 Upload Type {Doc, Image,

Video}

The type of upload

(document/image/video of the

item that is uploaded)

12 Item_Status S or P Sold or Pending


10/52

10

User Table

Serial

No.

Field Name Range of valid values

for the field

Remarks

1 First_Name Upto 20 characters in

length.

This is the first name of the

user

2 Second_Name Upto 20 characters in

length.

This is the second or middle

name of the user (probably

the last name or the surname)

3 User_Name Upto 20 characters in

length.

This is the login name of the

user which is the key field of

the database as it is unique

4 password Upto 10 characters in length Does not contain any special

characters and provides

security.

5 Date_of_birth Date Dob provided by the user

6 Gender M or F Male or Female

7 Phone_no Upto 10digits Mobile or landline number of

user should be provided

8 Email_id Upto 25 characters in

length

Checking if provided mail-id

is valid or not.

9 City/Town Upto 20 characters in length The city in which the user

lives should be mentioned by

the user

10 District Upto 20 characters in length The district to which the user

belongs should be mentioned

11 State Upto 20 characters in length The state to which the userbelongs should be mentioned

12 Country Upto 20 characters in length The country to which the user

belongs should be mentioned

13 Address Upto 400 characters in

length

The valid or permanent

address of user must be

provided for contact purpose

14 Pincode Upto 10 digits Verify if pincode is valid or

not.


11/52

11

15 Qualification Upto 5 characters in length The degree upto where the

user holds is mentioned

16 Occupation Upto 20 characters in length The financial and working

condition of the person ismentioned

17 Question Upto 50 characters in length Security question incase of

account recovery

18 Answer Upto 10 characters in length Security answer incase of

account recovery

19 Message Upto 50 characters in length Messages are sent between

users

20 Sender Upto 20 characters in length Sender of the message

21 Receiver Upto 20 characters in length Receiver of the message

Admin Table

Serial

No.

Field Name Range of valid

values for the field

Remarks

1 Admin_id Upto 10 digits Unique id for the admin

2 Customer_id Upto 10 digits Unique id for the

customer/buyer/bidder

3 Seller_id Upto 10 digits Unique id for the seller4 Bid_winner Upto 20 characters in

length

The name of the bidder who

won the auction

5 Card_type Upto 20 characters in

length

The type of the card (whether

credit or debit) the bidder

wants to perform transaction

6 Bank_name Upto 20 characters in

length

The name of the bank to

which the card belongs.

7 Branch_name Upto 20 characters in

length

The name of the bank branch

where the amount is deducted8 Payment_mode Upto 20 characters in

length

DD or cash or online.

9 Transaction_date

Date

The date amount has been

received from buyer and sent

to seller

10 Card_number Upto 20 characters in

length

The unique id of the card

11 Seller_status R or P Received amount or Pending

Transaction

12 Bidwinner_status R or P Received product or Pendingtransaction


12/52

12

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.

TESTCASE

TITLE

DESCRIPTION EXPECTED

OUTCOME

TheRequirement

in RS that is

being tested

UT1 Successful User

loginVerification

The login to the

system should be tried

with the username

assigned by the admin

and the correct

password

Login should be

successful and

the user should

enter into the

system

RS1

UT2 Unsuccessful

User Verification

Login to the system

with a wrong

password

Login fails with

an error Invalid

Password

RS1

UT3 Unsuccessful

User Verification

Login to the system

with a wrong

username

Login fails with

an error Invalid

username

RS1

UT4 Insufficient

information in

registration page

Essential information

to be provided by user

is missing

A dialog box

indicating to fill

complete

details.

RS4

UT5 Mismatch of

passwords in

registration form

User provides

different passwords

for both in the

textboxes for

password and confirm

password

A dialog box

stating

mismatch of

passwords so

enter password

again

RS3

UT6 Displaying selling

form by clicking

on the sell button

User who puts an item

for auction fills the

selling form by

clicking on sell button.

Selling form

details will be

displayedRS7


13/52

13

UT7 User auctioning

more than one

item in one login

session

User bids on several

items in the same

session

System should

allow the user

to bid on

several items.

RS18

UT8 Viewing the bid

history

It shows all the

biding information

The History of

the bids isdisplayed

RS14

UT 9 Adding a new

category

A new category has to

be added to the

category list.

System should

allow to add a

new category

RS11

UT 10 Seller extends

close date

Seller of the item can

extend the close date

of the auction

Close date is

successfully

updated

RS12

UT 11 User tries to

extend the close

date

User other than the

seller is trying to


System should

not allow the

user to extend

the close date

RS12

UT 12 Selecting an item

by clicking on the

item in the

category

User can select the

desired item.

Desired items

home page is

displayed

RS19

UT 13 Selecting an item

by using search

field

User can select the

desired item.

Desired items

home page is

displayed

RS8

UT 14 Displaying item

home page

User selects an item

and the desired items

home page isdisplayed

items home

page is

displayed

RS17

UT 15 User changes his

details.

User changes his

personal details.

System should

allow the user to

change 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

The search

results should

display all the

items which

matched the

search criteria

RS8

UT 17 Searching an

invalid item

User tries to search an

item that is not present

System should

display no

results found.

RS8

UT 18 Searching the

available

category.

User enters a category

name to search

All the items

under the

category must

be displayed.

RS8

UT 19 Searching a new

category

User searches for a

new category

System need to

display category

not found

RS8


14/52

14

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 andtested 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

IT1 Successful User

Verification

The login to the

system should be tried

with the login

assigned by the admin

and the correct

password

Login

should be

successful

and the user

should enter

in to the

system

RS1

IT 2 Unsuccessful User

Verification due to

wrong password

Login to the system

with a wrong

password

Login

should fail

with an

error

Invalid

Password

RS1

IT 3 Unsuccessful User

Verification due to

invalid login id

Login to the system

with a invalid login id

Login

should fail

with an

errorInvalid

user id

RS1

IT4 User enters valid

information in the

registration page.

All the essential

details are filled in the

registration page.

User is

successfully

registered

and

information

is stored in

thedatabase.

RS3


15/52

15

IT5 User enters wrong

mail id

User enters invalid

email id

System

should not

accept and

display

wrongemail id.

RS4

IT6 Successful customer

authentication

Verifying the email id

and

Credit card number by

an administrator

The

customer

can interact

with the

service

provided by

the server

RS4

IT7 Successful mail

sending to

customer

Information is sent to

the customer through

mails.

Customer

gets the

information

in the form

of mails

successfully

RS15

IT8 Checking the

messages

The user can check his

mails

User can

view

message.

RS25

IT 9 Sending a message toa valid user

User can sendmessages to other

valid user

Messagesare

successfully

sent

RS25


16/52

16

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 canbid 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 hisproducts 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 themif 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.


17/52

17

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 details7. Process the transaction8. Settle the transaction within time9. 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.

2. 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.


18/52

18

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 browsingHe 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 performspecific 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 ModuleThis 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 ModuleThis 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.


19/52

19

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 processaspects. 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:


20/52

20

Authenticated users:

DFD showing the functionalities of buyer:


21/52

21

DFD for seller:

DFD for administrator:


22/52

22

Connection between various persons involved in Online Auction

Online Auction Process:-


23/52

23

4.2.2 UML Diagrams:

Class Diagram:


24/52

24

Use-Case Diagrams:

System Use Case Diagram:

Admin Use Case Diagram:

System

Admin

Customer

OnLine Auctioning System

Admin

View Customers

View Bid Items

New Auction Items Today

Auction Items Endday

ViewProfile


25/52

25

Buyer/ Seller (Customer) Use Case Diagram:

Sequence Diagrams:

Buyer/ Seller (Customer) Sequence Diagram:

Customer

Registration

Login

Items

Buy

Sell

ViewProfile

New Auction Items today

New Auction Items EndDay

Customer Login BuyItem SellItemAuction Items Today Auction Item EndToday

1 : enterLogin()

2 : validate()

3 : loginSuccess()

4 : bidTheItem()

5 : sellTheItem()

6 : viewAuctionItemsToday()

7 : viewAuctionItemsEndToday()


26/52

26

Administrator Sequence Diagram:

Admin Login Customers BidItems ActionItems

1 : login()

2 : validate()

3 : AdminHome()

4 : viewCustomers()

5 : viewBidItems()

6 : viewAuctionItemsToday()

7 : viewAuctionItemsEndDay()


27/52

27

Activity Diagram:

Administrator Activity Diagram:

Admin

Login

Home Item Categories BiddingInfo LogOut

Add Items View Items Add Categories View Categories Add BiddingInfo View BiddingInfo

Enter Username,password

Success

Fail


28/52

28

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

OwnerOf Article

Login


View Items View Categories View BiddingInfo


Success

Fail

Update Items delete Items Update Bidding Info Delete Bidding Info


29/52

29

Buyer (Registered Bidder or customer) Activity Diagram:

Registered Bidder

Login


View Items View Categories View BiddingInfo


Success

Fail


30/52

30

Component Diagram:


31/52

31

4.3. Database Design:

4.3.1 List of Tables:

Tables Description

Admin_login: This table maintains login details like login name,

password, question, answer of admin.

Customer_master: This table maintains login details like login name,

password, question, answer of users.

Category_details: This table maintains category name, categoryabbr

and categorydesc.

Listofitems: This table maintains prodid, itemname,

categoryname, itemdesc, price, begin and end

date.

Bid_details: This table contains prodid, loginname, bamount,

dateofbid.

Temp_details: This table maintains prodid

Mesg: This table contains message, sender, receiver.

Payments: This table contains payment details like

ddnumber, drawn date, card holder name and

number.

4.3.2 Table Fields:

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

Admin_login

No Field name Range of valid

values for the Field

Remarks

1 Aid Up to 5 digits

2 Firstname Up to 20 characters

3 Lastname Up to 20 characters

4 Login_name Up to 20 characters Primary key

5 Password Up to 15 characters

6 DOB Date

7 Address Up to 255characters

8 City Up to 20 characters

9 State Up to 20 characters

10 Email Up to 24 characters

11 Occupation Up to 15 characters

12 Question Up to 50 characters Security question

13 Answer Up to 24 characters Security answer


32/52

32

Customer_table

No. Field name Range of valid


Remarks

1 Cid Up to 5 digits

2 Firstname Up to 20 characters3 Lastname Up to 20 characters

4 Login_name Up to 30 characters Primary key

5 Password Up to 20 characters

6 DOB Date

7 Address Up to 255characters

8 City Up to 20 characters

9 State Up to 20 characters

10 Email Up to 30 characters

11 Occupation Up to 15 characters12 Question Up to 50 characters Security question

13 Answer Up to 20 characters Security answer

Category_details

No. Field name Range of valid


Remarks

1 Categoryname Up to 20 characters Primary key

2 Categoryabbr Up to 20 characters

3 Categorydesc Up to 20 characters

Listofitems

No.

Field name Range of valid


Remarks

1 Prodid Up to 5 digits Primary key

2 Itemname Up to 30 characters

3 Categoryname Up to 30 characters Foreign key

4 Price number

5 Auc_begindate date

6 Auc_enddate date


33/52

33

7 Description Up to 30 characters

8 Login_name Up to 30 characters Foreign key

9 Timeleft Up to 3 digits

10 Status Up to 10 characters

Bid_details

No.



Remarks

1 Prodid Up to 5 digits Foreign key

2 Bid_amount Number


4 Dateofbid date

5 Status Up to 10 characters

Temp_details

No.



Remarks


Mesg

No.



Remarks

1 Message Up to 60 characters

2 Admin_sender Up to 15 characters Foreign key

3 Sender Up to 15 characters Foreign key

4 Recv Up to 15 characters


34/52

34

Payments

No.



Remarks



3 Pay_mode Up to 10 characters

4 Dd_no Up to 12 characters

5 Drawn_date Up to 12 characters

6 Payable_at Up to 20 characters

7 Card_holder_name Up to 25 characters

8 Card_number Up to 16 characters

9 Card_type Up to 8 characters


35/52

35

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.


36/52

36

No. Test case

Title

Description Observed

Outcome

The

requirement

in RS that is

being tested

Result

UT1 Insufficientinformation

provided in the

registration

form.

User does not giveentire information

some essential

information might

be missing.

A message isdisplayed saying to

fill the complete

details.

RS4

Passed

UT2 Displaying

selling form

by clicking on

the sell button

User who puts an

item for auction fills

the selling form by

clicking on sell

button.

selling form details

will be displayed

RS7 Passed

UT3 Filling

incomplete

details in the

selling form

User ignores some

essential details like

name & category.

System should

display incomplete

details.

RS9 Passed

UT4 Browsing

categories by

clicking on the

category name

on the page.

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.

The user can

chooses the efficient

browsing categories

The entire details of

chosen categories are

displayed in new

page

RS6 Passed

UT6 Updating the

selling form

by a valid user

The seller of the

item only, can

update the

information in the

selling form

The changes like

editing item.

Uploading new

image are done

successfully

RS9 Passed

UT7 User

auctioning

more than one

item in one

login session

User bids on several

items in the same

session

System should allow

the user to bid on

several items.

RS18 Passed


37/52

37

UT8 Viewing the

bid history

It shows all the

biding information

The History of the

bids is displayed

RS14 Passed

UT 9 Adding a new

category

A new category has

to be added to the

category list.

System should allow

to add a new

category

RS11 Passed

UT

10

Seller extends

close date

Seller of the item

can extend the close

date of the auction

Close date is

successfully updated

RS12 Passed

UT

11

User tries to

extend the

close date

User other than the

user is trying to


System should not

allow the user to


RS12 Passed

UT

12

Selecting an

item by

clicking on the

item in the

category

User can select the

desired item.

Desired items home

page is displayed

RS15 Passed

UT

13

Selecting an

item by using

search field

User can select the

desired item.

Desired items home

page is displayed

RS8 Passed

UT

14

Displaying

item home

page

User selects an item

and the desired

items home page is

displayed

items home page is

displayed

RS17 Passed

UT

15

User changes

his details.

User changes his

personal details.

System should allow

the user to change

his details

RS16 Passed

UT

16

Searching a

valid item by

entering a

valid name in

search field.

User searches the

item by giving its

name

The search results

should display all the

items which matched

the search criteria

RS8 Passed

UT

17

Searching an

invalid item

User trys to search

an item that is not

present

System should

display no results

found.

RS8 Passed

UT

18

Searching the

available

category.

User enters a

category name to

search

All the items under

the category must be

displayed.

RS8 Passed

UT

19

Searching a

new category

User searches for a

new category

System need to

display category not

found

RS8 Passed


38/52

38

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 propertest 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 caseTitle

Description Observed

Outcome

Therequirement

in RS that is

being tested

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 should be

successful and

the user should

enter in to the

system

RS1 Passed

IT 2 UnsuccessfulUser

Verification

due to wrong

password

Login to the systemwith a wrong password

Login shouldfail with an error

Invalid

Password

RS1 Passed

IT 3 Unsuccessful

User

Verification

due to invalid

login id

Login to the system

with a invalid login id

Login should

fail with an error

Invalid user id

RS1 Passed

IT4 User enters

valid

information in

the registration

page.

All the essential details

are filled in the

registration page.

User is

successfully

registered and

information is

stored in the

database.

RS3 Passed

IT5 User enters

wrong mail id

User enters invalid

email id

System should

not accept and

display wrong

email id.

RS4 Passed


39/52

39

IT6 Successful

customer

authentication

Verifying the email id

and

Credit card number by

an administrator

The customer

can interact with

the service

provided by the

server

RS4 Passed

IT7 Successful

mail sending to

customer

Information is sent to

the customer through

mails.

Customer gets

the information

in the form of

mails

successfully

RS15 Passed

IT8 Checking the

messages

The user can check his

mails

User can view

message.

RS25 Passed

IT 9 Sending a

message to a

valid user

User can send

messages to other valid

user

Messages are

successfully sent

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 isencountered 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 theexceptions. To overcome this scenario, proper connectivity must be maintained.


40/52

40

6. Screen Shots:

Home page:

Registration page:


41/52

41

Visitor searching items using search field:

Login page:


42/52

42

Customer home page:

Displaying customer profile details:


43/52

43

Item selling form:

Viewing items placed for auction:


44/52

44

Updating item page:

Customer browsing through categories:


45/52

45

Customer changing password:

Bidding items page:


46/52

46

Payments page:

Bidding on an item:


47/52

47

Customer viewing new items:

Viewing watchlist:


48/52

48

Admin home page:

Admin adding new category:


49/52

49

Admin modifying category:

Admin viewing customers:


50/52

50

Admin sending message to customers:

Logout screen:


51/52

51

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 easyway 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 andbid 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.


52/52

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-HillInternational Edition

The Complete Reference JAVA byHerbert Schildt. HTML Black book by Steven Holzner.
https://campusconnect.infosys.com/https://campusconnect.infosys.com/http://www.w3schools.com/http://www.w3schools.com/http://www.wikepedia.com/http://www.wikepedia.com/http://www.onlineautions.com/http://www.onlineautions.com/http://www.ebay.com/http://www.ebay.com/http://www.amazon.com/http://www.amazon.com/http://www.amazon.com/http://www.ebay.com/http://www.onlineautions.com/http://www.wikepedia.com/http://www.w3schools.com/https://campusconnect.infosys.com/

Development of Online Auctioning System for organization

Documents

Transcript of Development of Online Auctioning System for organization